# MCR Cloud Connectivity Overview
Source: https://docs.megaport.com/cloud/mcr/index
This help topic provides an overview of MCR cloud connectivity.
Megaport Cloud Router (MCR) provides virtual routing capabilities for on-demand private connectivity at Layer 3.
MCR is preconfigured in data centers in key routing zones around the world, enabling data transfer between:
* Multicloud and hybrid cloud environments
* Network service providers
* Cloud service providers
Without physical infrastructure, you can use cloud-to-cloud networking, private peering between leading public cloud, and providers, and direct connectivity to any provider on the Megaport software-defined network (SDN). There is no need to own and maintain equipment and no IP address or autonomous system numbers to procure.
Click a Cloud Service Provider link in the site navigation to get started.
For more information about MCR, see [MCR Overview](/mcr).
## Using a service key
You can create a service key that allows you to share your service with another Megaport account holder.
For more information, see [Setting up Service Keys](/marketplace/service-keys/).
# MVE Cloud Connectivity Overview
Source: https://docs.megaport.com/cloud/mve/index
This help topic provides an overview of MVE cloud connectivity.
Megaport’s ecosystem provides cloud on-ramps from leading cloud providers and you can instantly provision connectivity between your Megaport Virtual Edge (MVE) and a collection of leading cloud service providers (CSPs). Connectivity models vary by CSP.
Click a CSP link for an SD-WAN provider in the site navigation to get started.
For more information about MVE, see [MVE Overview](/mve).
# Common Connectivity Scenarios
Source: https://docs.megaport.com/connections/common-scenarios
This help topic describes common connectivity scenarios when using Megaport.
This topic describes eight common scenarios delivering different levels of protection at the physical layer connecting to Megaport SDN.
Customer edge device stack (switch/router/firewall) at a single Megaport Point of Presence (PoP) with a single cross connect connecting to a single Port.
**Protection at the Physical Layer**
| Component | Protection |
| - | - |
| Megaport PoP | N/A |
| Switch Chassis | N/A |
| SFP Transceiver | N/A |
| Cross Connect | N/A |
Customer edge device stack (switch/router/firewall) at a single Megaport Point of Presence (PoP) with dual cross connects connecting to two Ports in a LAG.
**Protection at the Physical Layer**
| Component | Protection |
| - | - |
| Megaport PoP | N/A |
| Switch Chassis | N/A |
| SFP Transceiver | 1 |
| Cross Connect | 1 |
Customer edge device stack (switch/router/firewall) at a single Megaport Point of Presence (PoP) with dual cross connects connecting to two Ports not in a LAG on different chassis.
You will need to discuss this option with your Sales Directors or Solutions Architect on the specific PoP location.
**Protection at the Physical Layer**
| Component | Protection |
| - | - |
| Megaport PoP | N/A |
| Switch Chassis | 1 |
| SFP Transceiver | 1 |
| Cross Connect | 1 |
Customer edge device stack (switch/router/firewall) at a single Megaport Point of Presence (PoP) with one cross connect connecting to one Port and one DC Interconnect (Campus) cross connect connecting to one Port at a different nearby Megaport PoP.
**Protection at the Physical Layer**
| Component | Protection |
| - | - |
| Megaport PoP | N/A |
| Switch Chassis | 1 |
| SFP Transceiver | 1 |
| Cross Connect | 1 |
Customer edge device (switch/router/firewall) at each of two Megaport PoPs with a single cross connect connecting to a single Port and with a separate connection between the two sites.
**Protection at the Physical Layer**
| Component | Protection |
| - | - |
| Megaport Point of Presence (PoP) | 1 |
| Switch Chassis | 1 |
| SFP Transceiver | 1 |
| Cross Connect | 1 |
Customer edge device stack (switch/router/firewall) at a single Megaport Point of Presence (PoP) with dual cross connects connecting to two Ports in a LAG and another dual DC Interconnect (Campus) cross connects to two Ports in a LAG at a different Megaport PoP.
**Protection at the Physical Layer**
| Component | Protection |
| - | - |
| Megaport PoP | N/A |
| Switch Chassis | 1 |
| SFP Transceiver | 3 |
| Cross Connect | 3 |
Customer edge device stack (switch/router/firewall) at each of two Megaport Points of Presence (PoPs) with dual cross connects connecting to two Ports in a LAG, and with a separate connection between the two sites.
**Protection at the Physical Layer**
| Component | Protection |
| - | - |
| Megaport PoP | 1 |
| Switch Chassis | 1 |
| SFP Transceiver | 3 |
| Cross Connect | 3 |
Customer edge device stack (switch/router/firewall) at each of two Megaport PoPs with dual cross connects connecting to two Ports not in a LAG on separate chassis, and with an optional separate connection between the two sites.
You will need to discuss this option with your Sales Directors or Solutions Architect on the specific Point of Presence (PoP) location.
**Protection at the Physical Layer**
| Component | Protection |
| - | - |
| Megaport PoP | 1 |
| Switch Chassis | Up to 3 (With separate connection between two sites) |
| SFP Transceiver | 3 |
| Cross Connect | 3 |
# Creating a Port
Source: https://docs.megaport.com/connections/creating-port
This help topic describes how to create a Port in the Megaport network.
This topic describes how to create a in the Megaport network. Your organization’s Port is the physical point of connection between your organization’s network and the Megaport network. You need to deploy a Port wherever you want to direct traffic.
The Megaport Portal presents the Port details, location, provider, configuration, and pricing options on a single page, with a live order summary that updates as you make selections. You can start with a single data center. For redundancy, we recommend selecting two different locations.
Before proceeding, ensure that you have set up your Megaport Portal account. For more information, see [Setting Up a Megaport Account](/setting-up).
**To create a new Port**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **Port**.
The Create Port page opens. Complete the sections on this page to configure your Port. The order summary updates as you make selections. On wider screens, the summary is displayed in a panel on the right. On narrower screens, it is displayed in a bar at the bottom of the page that you can expand.
3. In the **Details** section, specify these fields:
* **Port Name** -- Specify a name that helps you identify the Port, particularly if you plan to have more than one Port.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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 Port is not automatically updated with the Port service level reference number.
4. In the **Location** section, select your preferred data center location.\
Use the **Search** field to find a location by metro name, country, data center name, or provider name. You can also search by address details, such as a street, city, state, or postcode. Alternatively, browse the region tabs, then select a location.
5. In the **Provider** section, select a data center provider, then select a data center from the drop-down list.\
Only providers and data centers available at your selected location are listed. If your search term in the Location section matches a specific provider or data center, the Provider list narrows to that provider. If the term matches only a metro or country, the Provider list shows every provider available at that location.
6. In the **Configuration** section, specify these fields:
* **Port Speed** -- Select the required Port speed. Port capacity depends on location and service availability. Ensure that your equipment is capable of interfacing with the selected speed.
* **Port Diversity** -- If diversity is available at your selected location and speed, a **Diversity Option** drop-down list appears. You can create two diverse Ports or choose an existing Port for the new Port to be diverse from. For more information about configuring Port diversity, see [Port Diversity](/connections/port-diversity).
* **LACP & LAG Ports** -- To enable LACP, the Port speed must be 10 Gbps or higher. Enable LACP on Port if you want the Port to be a member of a LAG, then select the number of Ports in the LAG, up to a maximum of 8. For more information about LAG, see [Creating a Link Aggregation Group](/connections/lag).
7. In the **Pricing** section, specify these fields:
* **Contract Term** -- Select a contract term. Longer terms result in a lower monthly rate. *12 Months* is selected by default.
* **Contract Renewal** -- Automatically renews the contract at the same price and term length when the current term ends. This is enabled by default. If you disable it, the contract rolls over to a month-to-month term at the end of the current term, without the term discount.
For more information, see [Minimum Term Renewal](/portal-admin/auto-renew).
8. In the **Add-ons** section, review the following:
* **Cross Connect** -- If the location has Cross Connect availability, a option appears in the Add-ons section.
Enable the **Cross Connect** add-on to add a Cross Connect to your Port order. The monthly rate and one-time fee for the Cross Connect appear on the card.
For more information, see [Ordering a Cross Connect](/connections/cross-connect/).
9. In the **Resource Tags** section, add any tags you want to apply to this Port.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
The price updates dynamically based on your selections in the order summary. Note that some partner-managed accounts do not display the pricing details.
10. Review the order summary, then click **Add Port**.
The newly created Port is added to your cart, ready for checkout. If you create a service in a market that is not enabled, you are prompted to enable it first. For more information, see [Setting Up Financial Details](/setting-up/finance-basics).
11. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
12. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
13. Click **Order Now**.
In most cases the Port is provisioned immediately, but sometimes it can take longer. After the Port is provisioned, Megaport generates a Letter of Authorization (LOA) specifying the demarcation point to be applied to your service. A PDF of the LOA is sent to you by email.
14. Click the **Download LOA** link next to the new Port on the Services page.\
The **Download LOA** link appears after the Port is available. For more information about the LOA, see [Megaport Letter of Authorization](/portal-admin/loa).
15. Provide the LOA to your data center operator to establish the physical Cross Connect from your network device to your new Port.
The cost of a new cross connection and any related VXC fees are the responsibility of the customer, as outlined in [Megaport's Global Services Agreement](https://www.megaport.com/legal/global-services-agreement/).
Once the Port has been provisioned and deployed, you have access to the Megaport network and can start adding Virtual Cross Connects (VXCs) to the Port. For more information about adding VXCs, see [Creating a VXC](/connections/overview#create_vxc).
# Ordering a Cross Connect
Source: https://docs.megaport.com/connections/cross-connect
This help topic describes what a Cross Connect is and how to use it
A Cross Connect is a dedicated physical point-to-point connection that links your location within a Megaport-enabled data center to a Megaport Port. It can only be ordered with a Port on a term.
You can order a Cross Connect at the same time as you create your Port, after the Port order has been created but before the service is ordered, or after you have ordered the Port when it is in *Configured* status.
If you order a Cross Connect at the same time as a Port, whichever method you used, Megaport will process the Cross Connect order with the data center to streamline the ordering process.
When you order a Port with a Cross Connect, the Port will only be live after the Cross Connect has been deployed.
This means that the Port will not be available within seconds, as it would be without the Cross Connect, but there will be a delay while the Cross Connect is provisioned.
## Ordering a Cross Connect when creating a Port
You can order a Cross Connect during the Port creation process.
**To order a Cross Connect when creating a Port**
1. Start the process to create a Port.\
For more information about creating a Port, see [Creating a Port](/connections/creating-port).
2. In the **Location** section, select the Port location.
3. In the **Details** section, specify a Port name, then in the **Configuration** section, select the Port speed.\
If the location has Cross Connect availability, a **Cross Connect** option appears in the **Add-ons** section, allowing you to include one with your Port order.
4. Enable the **Cross Connect** add-on to include a Cross Connect with your Port order.\
The pricing for the Cross Connect appears on the card.
* **Monthly Rate** -- Displays the Cross Connect pricing in addition to the monthly Port fees. The term is the same as for the Port.
* **One-Time Fee** -- Displays installation and decommissioning charges.
If you include Link Aggregation Groups (LAGs) or Port diversity, incremental costs will be added to the Cross Connect on a per Port basis. For more information about LAGs, see [Creating a Link Aggregation Group](/connections/lag). For more information about Port diversity, see [Port Diversity](/connections/port-diversity).
5. Complete the remaining sections on the Create Port page.\
The order summary updates to include the Cross Connect monthly rate and one-time fee alongside the Port pricing.
The term discount and any other associated discount apply only to the Port.
6. Click **Add Port**.\
The total monthly cost of the Port and Cross Connect is added to your cart. The one-time fee is not included in the cart total.
7. Click **Review Order**.\
The Cross Connect pricing is summarized.\
Read the Cross Connect disclaimer with the important information on the pop-up window.
8. Click **Order Now**.
## Ordering a Cross Connect after creating a Port, but before ordering the service
If you decide you want to add a Cross Connect after creating your Port, you can add one before you click **Review Order** and deploy your service.
**To order a Cross Connect before ordering the service**
1. Create a Port.\
For more information about creating a Port, see [Creating a Port](/connections/creating-port).
2. After clicking **Add Port** to finalize the Port setup, click the gear icon next to the connection on the Services page to make changes.
If the location has Cross Connect availability, a **Cross Connect** option appears in the **Add-ons** section, allowing you to include one with your Port order.
3. Enable the **Cross Connect** add-on to add a Cross Connect to your order.\
The pricing for the Cross Connect appears on the card.
* **Monthly Rate** -- Displays the Cross Connect pricing in addition to the monthly Port fees. The term is the same as for the Port.
* **One-Time Fee** -- Displays installation and decommissioning charges.
4. Review the pricing information summary, then click **Update Port**.
5. Click **Review Order** and review the details.
6. Click **Order Now** to place your order.
## Ordering a Cross Connect when the Port is in Configured status
If you decide you want to order a Cross Connect after you have created your Port, and clicked **Review Order** and **Order Now**, you can add a Cross Connect when it is in *Configured* status.
**To order a Cross Connect in Configured status**
1. Go to the **Services** page.
You will see the Port on the **Services** page in *Deployable* status while the Port is waiting for resource allocation.
After a few seconds, the status will change to *Configured*.
2. Click the gear icon next to the connection to make changes.
If the location has Cross Connect availability, a **Cross Connect** section appears, allowing you to include one with your Port order.
3. Click **Yes** in the Cross Connect section to add a Cross Connect to your order.
The Cross Connect will be added to your Port, and the pricing will be adjusted accordingly.
The Port will remain in *Configured* status until the Cross Connect has been deployed.
## Uploading a Letter of Authorization (LOA)
Megaport cannot deploy the Megaport-provisioned Cross Connect until you provide the . After you order the Cross Connect, you will receive an email from Megaport with a case reference number and instructions to complete your order.
When the Port is in *Configured* status, an **Upload LOA** button appears on the Services page entry. Click it to open the Upload LOA screen, where you can upload a new LOA and view or download any LOA files already uploaded for the Cross Connect case.
**To upload a LOA**
1. Click **Upload LOA** for the required Port on the Services page.
2. On the Upload LOA screen, drag and drop your LOA file onto the upload area, or click **browse to choose a file** and select it.
The file must be a PDF and no larger than 5 MB.
3. Click **Upload LOA**.
The uploaded file appears in the **Uploaded LOA file(s)** list.
### Viewing and downloading uploaded LOA files
The Upload LOA screen lists any LOA files already uploaded for the Cross Connect case under **Uploaded LOA file(s)**, showing the name of each file and the date it was uploaded.
To download a file, click **Download** next to it in the list.
You cannot delete an uploaded LOA file. If you need to correct a mistake, upload a new file, and it will appear alongside the existing files in the list.
## Support Requests Portal
Megaport creates a support case for each Cross Connect order. You can use the Support Requests Portal to see more details about your Cross Connect case and to keep track of progress.\
For more information, see [Support Requests Portal](/support/support-portal).
You will be able to see these tabs:
* **Activity** - The Activity tab allows you to see the activity that has taken place on the case. You can use this page to enter comments.
* **Details** - In the Details tab, you can see the details of this Cross Connect order, including Port information and Cross Connect information. You can also add **Collaborators**, people in your organization that you want to participate in this case.
* **Attachments** - The Attachments tab is for uploading attachments, such as the LOA.
For more information, see [Support Requests Portal](/support/support-portal).
# Creating a Link Aggregation Group
Source: https://docs.megaport.com/connections/lag
This help topic describes how to work with Link Aggregation Groups within the Megaport network.
This topic describes Port link aggregation groups (LAGs), steps through how to add a Port to a LAG, and how to convert a non-LAG Port to a LAG Port.
A LAG bundles physical ports to create a single data path, where the traffic load is distributed among the ports to increase overall connection reliability. This feature provides aggregate bandwidth, enhanced resiliency, and efficient use of resources. Other terms used to describe a LAG include *port trunking*, *link bundling*, and *channel bonding*.
When you create a new Port that is 10 Gbps or higher, enabling the allows you to use it in a LAG. We recommend that you enable LACP even if you only require a single Port at that time. This prevents service interruption if later you decide to enable LACP on the Port. You can combine up to 8 physical Ports into a single LAG, and the Port price will update dynamically based on any additional Ports. All Ports within the LAG use the same Layer 2 MAC address. For more information about how to create a Port, see [Creating a Port](/connections/creating-port).
Multiple Ports in a LAG configuration with multiple physical cross-connects reduce potential single points of failure that will stop the network from working if they go down. For example, networks using small form-factor pluggable (SFP) ports or optics.
This image shows the overall design of a LAG configuration:
## Port LAG specifications
| **Specification** | **Port** |
| - | - |
| Protocol | LACP (IEEE 802.1AX or previous IEEE 802.3ad standards) |
| Interface | 10GBASE-LR (10 Gbps) or 100GBASE-LR4 (100 Gbps) |
| Maximum number of interfaces in a single LAG | 8 |
## Port LAG restrictions
* Multi-Chassis Link Aggregation (MC-LAG) across multiple devices is not supported.
* The LAG speed must be 10 Gbps or higher. 1 Gbps Ports are not supported in LAGs.
* LACP System Priority must be set to a value higher than 0 on your equipment for LACP to function correctly.
### Bandwidth limitations
The available total bandwidth of a LAG is the sum of all Ports in the LAG. Virtual Cross Connect (VXC) bandwidth is still limited to the maximum bandwidth of any single Port in the LAG. However, local Ports within the same metro area as Internet Exchange (IX) services don't have this limitation. You can configure IX services to use the total amount of bandwidth capacity from all members in a LAG.
## Configuring a LAG pair for diversity
When you create a new LAG, you can make it diverse from an existing LAG or create a diverse pair of LAGs at the same time, with one in each diversity zone. For more information about Port diversity, see [Port Diversity](/connections/port-diversity).
It is not possible to change a LAG diversity zone after placing the order. To do this, you must cancel and re-order the LAG.
**To configure a LAG pair for diversity**
1. Log in to the Megaport Portal and choose **Services**.
2. Click **Add Services**, then select **Port**.
The Create Port page opens. Complete the sections on this page to configure your Port. The order summary updates as you make selections. On wider screens, the summary is displayed in a panel on the right. On narrower screens, it is displayed in a bar at the bottom of the page that you can expand.
3. In the **Details** section, specify a **Port Name**, then in the **Location** section, select a data center location for the Port.\
Use the **Search** field to find a location by metro name, country, data center name, or provider name. You can also search by address details, such as a street, city, state, or postcode. Alternatively, browse the region tabs, then select a location.
4. In the **Provider** section, select a data center provider and data center.\
Only providers and data centers available at your selected location are listed. If your search term in the Location section matches a specific provider or data center, the Provider list narrows to that provider. If the term matches only a metro or country, the Provider list shows every provider available at that location.
5. In the **Configuration** section, specify these fields:
* **Port Speed** -- Select the required Port speed. Port capacity depends on location and service availability. Ensure that your equipment is capable of interfacing with the selected speed. If Port diversity is available at the location and speed you select, a **Diversity Option** drop-down list is enabled. If Port diversity is not available at your preferred location, contact a Megaport Sales representative for more information.
*
* **LACP & LAG Ports** -- To enable LACP, the Port speed must be 10 Gbps or higher. Enable LACP on Port to add the Port as a member of a LAG, then select the number of Ports in the LAG, up to a maximum of 8.
6. In the **Pricing** section, select a **Contract Term** and set **Contract Renewal**.
For more information, see [Port Pricing and Contract Terms](/finance/port-pricing).
7. In the **Add-ons** section, review the following:
* **Cross Connect** -- If the location has Cross Connect availability, a option appears in the Add-ons section.
Enable the **Cross Connect** add-on to add a Cross Connect to your Port order. The monthly rate and one-time fee for the Cross Connect appear on the card.
For more information, see [Ordering a Cross Connect](/connections/cross-connect/).
8. In the **Resource Tags** section, add any tags you want to apply.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
9. Review the order summary.\
The summary shows Port Diversity enabled and the diversity zones for the LAGs. The monthly charge includes both LAGs. If a Cross Connect has been ordered, the summary also shows the monthly rate and the one-time fee for the Cross Connect.
10. Click **Add Port**.\
The newly created LAGs, their diversity zones, and the monthly charges are added to your cart.
11. Click **Review Order** to deploy the new LAGs now, or click **Save** to save the configured LAGs before placing the order.
12. Click **Order Now** on the pop-up window to start provisioning your new LAGs.
After the LAGs are provisioned, Megaport generates a Letter of Authorization (LOA) specifying the demarcation point to be applied to your service.
13. Click **Download LOA** next to the new LAGs on the Services page.\
Megaport will also send you the LOA PDF by email.
14. Provide the LOA to your data center operator to establish the physical Cross Connect from your network device to your new Port.
The cost of a new cross connection and any related VXC fees are the responsibility of the customer, as outlined in [Megaport's Global Services Agreement](https://www.megaport.com/legal/global-services-agreement/).
After the LAGs have been provisioned and deployed, you have access to the Megaport network and can start adding Virtual Cross Connects (VXCs) to the LAG. For more information about adding VXCs, see [Creating a VXC](/connections/overview#create_vxc).
## Converting a non-LAG Port
To convert a non-LAG Port to a LAG, send a request to Megaport Support to manually convert the Port. Make sure to identify the Port in your request.
# Adding a Port to an Existing LAG
Source: https://docs.megaport.com/connections/lag-adding
This help topic describes how to add a Port to an existing Link Aggregation Group.
The most simple LAG configuration is a single Port LAG, which configures the device on the Megaport side to run LACP on a single channel. However, this configuration doesn’t provide any added resilience. If Port capacity or traffic status requires resilience, you can add Ports to a LAG. For example, if traffic moves from development to production, you might require additional Ports.
When you add one or more Ports to a live LAG, they are automatically assigned the same location, speed, and Megaport Marketplace visibility as other Ports in the LAG. Any Ports that you add to a diverse LAG will inherit the diversity zone of the LAG.
**To add a Port to an existing LAG**
1. Log in to the Megaport Portal and choose **Services**.
2. Select a Port that is part of a LAG and click **+Ports**.
3. Specify these details for the new Port:
* **Port Speed** -- Select the required Port speed. Port capacity depends on location and service availability. Ensure that your equipment is capable of interfacing with the selected speed. If Port diversity is available at the location and speed you select, Port diversity options are enabled. If Port diversity is not available at your preferred location, contact a Megaport Sales representative for more information.
* **Port Name** -- Specify an easily identifiable name for the Port.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Cross Connect** -- If the location has Cross Connect availability, a option appears in the Add-ons section.
Enable the **Cross Connect** add-on to add a Cross Connect to your Port order. The monthly rate and one-time fee for the Cross Connect appear on the card.
For more information, see [Ordering a Cross Connect](/connections/cross-connect/).
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Port Pricing and Contract Terms](/finance/port-pricing).
Partner and partner-managed accounts cannot view or change Port contract terms.
* **Port Diversity** -- Diversity options are displayed only if diversity is available at this location and speed.
* **LACP & LAG Ports** -- Specify the number of Ports to add to the LAG from the drop-down list. The maximum number of Ports in a LAG is 8.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
4. Click **Next**.\
The price updates dynamically based on your selections.
5. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
6. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
7. Click **Order Now**.
# Ordering a Local Loop
Source: https://docs.megaport.com/connections/local-loop
This help topic describes what a Local Loop is and how to use it
A local loop, also known as a last-mile connection, is the external circuit that links your site, which is located outside a Megaport-enabled data center, to the designated Megaport-enabled data center.
This connection is often a circuit that utilizes fiber outside the Megaport data center. The network diagram below illustrates the architecture and functionality of the local loop.
## Local loop procurement and Megaport's role
A local loop is typically procured and managed directly by you or a third-party carrier.
When a local loop is required to deliver Megaport services, Megaport provides proactive procurement support and works closely with both you and the Megaport-procured third-party carrier to streamline, speed up, and simplify the process.
However, since local loop provisioning remains a manual process, unlike Megaport's generally automated ordering system, it will require additional time to complete.
The Port will only be live after the local loop has been delivered. Therefore, when ordering a Port that includes a local loop, you should expect the Port’s availability to be delayed, as it depends on the local loop delivery timeline.
## Local loop ordering workflow
Below is a step-by-step workflow describing how you can order a local loop through Megaport.
1. Contact your Megaport Account Manager to provide the required technical details for your local loop connection.
2. After the technical details are confirmed by you, the Megaport Account Manager, and the Megaport Solutions Architect, the request will be evaluated by the Megaport technical and support teams to determine feasibility, final delivery timeline, and total cost.
3. After Megaport determines that the proposed solution is feasible, the Megaport Account Manager will provide you with a Megaport Local Loop Service Order Form (MSO) for your review and acceptance of the pricing and terms and conditions.
4. After you sign the MSO, you create a Port in the Megaport Portal with minimum term of 24 months. For more information, see [Creating a Port](/connections/creating-port).
5. Megaport orders the local loop under a contract established between the carrier and Megaport.
6. Megaport will then place a Cross Connect order to establish the physical connection between your Port and the local loop demarcation point.
7. The Megaport Account Manager and the Megaport team will coordinate with you to bring the Port to the *Live* status by monitoring the Port’s light levels. If required, a troubleshooting process might be conducted involving the Megaport Account Manager, the Megaport technical team, you, and the carrier.
## Summary of ordering a local loop
1. **Early engagement** -- If you require a local loop to connect to a Megaport-enabled data center, we recommend engaging with your Megaport Account Manager as early as possible in the planning process.
2. **Port order** -- After the local loop procurement details are finalized among you, your carrier contact, and Megaport, you can proceed to order a Port. The minimum term for a Port associated with a local loop is 24 months.
3. **Local loop order placement** -- After the Port order is created and the Port is in the *Configured* status, Megaport will order the local loop service.
## Helpful references
* [Creating a Port](/connections/creating-port)
* [Megaport Enabled Locations page](https://www.megaport.com/megaport-enabled-locations/)
* [Port Pricing and Contract Terms](/finance/port-pricing)
* [Understanding Locations](/enabled-locations)
# Moving VXCs
Source: https://docs.megaport.com/connections/move-vxc
This help topic describes how you can move one or more ends of a VXC in the Megaport Portal.
Once you have created and deployed VXCs on the Megaport network, you can move one or both ends, subject to some rules. You can move VXCs on Ports, MCRs, and MVEs. This is a useful function for reducing interruptions during maintenance and other tasks that would otherwise cause downtime.
## Which VXCs can be moved?
The following rules apply regarding which VXCs you can move:
* Any user who can change the speed of a VXC is allowed to move the VXC from any account type.
* You can move any VXC type as long as it is not locked or pending approval.
* You can move an unlocked VXC under a locked Port.
* No approval is required for Megaport Marketplace or Service Key VXCs.
* The source and destination Ports must be owned by the same customer account.
## Conditions for moving a VXC
There are conditions that must be met before moving a VXC. The following criteria must be satisfied before you can move a VXC.
* The move can only be to a service of the same type.\
For example, Port to Port, MCR to MCR, or MVE to MVE.
* You can only move to a Port within the same metro as the current Port.\
For more information about metros, see [Metro IDs](/ix/metro-ids).
* The destination Ports must have enough capacity for the selected connection.
* When a VLAN is specified, that VLAN must be available on the destination Port.
* The move must not cause a change to billing.
If a move is regarded as invalid, the connection will be greyed out and cannot be moved.
If you cancel a move, the VXC is not affected and it remains connected to its original Port.
## Moving VXCs on MVEs
Moving a VXC on an MVE supports MVEs with multiple vNICs. When moving VXCs for MVEs with multiple vNICs, you can:
* move a VXC to a different vNIC on the same MVE.
* select the required vNIC on the destination MVE when moving a VXC between different MVEs.
## Moving one or more VXCs
You can move one or more VXCs at a time. Select the service that the VXCs are to be moved from, then select the VXCs to be moved.
This example shows how to move a VXC on a Port.
**To move one or more VXCs**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.
The A-End and B-End of the VXC are shown as connections on the relevant Port. Make sure you are moving the correct end.
2. Click the **Move Connections** icon on the Port or on the VXC.
The **Move Connections** icon is greyed out if the Port or VXC is not valid. For more information, see [rules](#which) and [conditions](#conditions) above.
3. Click to select one or more connections to move. Each move is subject to the [rules](#which) and [conditions](#conditions) described above. If a connection is not valid, it will be displayed but will not be available to select.
You can select or deselect connections individually, or use the **Select All** button.
4. Select the destination Port in the Move To area.
The Port selection list is filtered by the rules described in the [rules](#which) and [conditions](#conditions) described above. If a connection is not valid, it will be displayed but will not be available to select.
You can filter the Ports by selecting a diversity zone at the top of the Move To list.
5. Click **Next**.
6. Review your selection and click **Move**.
7. On the prompt that shows the intended move, review the details again and click **Confirm**.
The Summary table shows the status of the move. It will either show a *working* hourglass, a message saying *success*, or an error message.
The *Success* status means that the request was successfully submitted and the VXC(s) have been moved.
A *Failure* message shows that the move has failed. The connections will not be moved.
# Connections Overview
Source: https://docs.megaport.com/connections/overview
This help topic describes the network connection models available through Megaport.
Megaport lets you connect to the services you need, when you need them. The process is simple and fast, and involves these basic steps:
1. Create a [Port](/connections/creating-port), [Megaport Cloud Router (MCR)](/mcr/creating-mcr), or [Megaport Virtual Edge (MVE)](/mve).
2. Deploy .
3. Use the VXCs to connect to services on the Megaport network.
VXCs are Layer 2 Ethernet circuits providing private, flexible, and on-demand connections between any of the locations on the Megaport network with 1 Mbps to 100 Gbps of capacity. Connections over 10 Gbps are available on 100 Gbps Ports.
All VXCs on the Megaport network are delivered as protected services. Each VXC is provisioned across multiple diverse fiber paths at the data center, and connections automatically fail over if an individual path becomes unavailable.
## VXC rate limits
The maximum VXC size is dynamically calculated based on network routes used to deliver the service. The VXC size cannot exceed the speed of the physical interface on which it resides.
* **Port and MCR** -- The VXC rate limit cannot exceed the speed of the lowest speed Port or MCR. This limit also applies to LAGs. For example, a 15 Gbps VXC is allowed on a 100 Gbps Port, but not on a 2 x 10 Gbps LAG.
* **MVE** -- The maximum rate limit of a standard VXC or Megaport Internet connection is controlled by the lowest of the end rates. You can adjust the speed as required after you create the VXC, in increments of 1 Mbps.
In some cases, Megaport cannot automatically provision the entered rate limit. However, we might be able to configure a higher speed for the service. To request a higher speed, submit the request form displayed below the **Rate Limit** field in the Connection Details page.
## VXC terms
You can specify an optional term for your VXC. The choices are:
* No Minimum Term
* 12 months (this is the default)
* 24 months
* 36 months
* 48 months
* 60 months
Discounts are applied depending on the term duration. For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing).
You can select No Minimum Term to pay-as-you-go at the current rack rate and adjust the rate limit as required.
You can increase the rate limit of a termed VXC during the term. For more information, see [Changing the Speed of a Termed VXC](/connections/vxc-termed-rate-change).
Deleting a VXC before the end of the term will generate early termination fees (ETF), which are also known as early termination charges (ETC). To avoid ETF, select No Minimum Term until the configuration is complete. You can update the connection at any time to opt into a term.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
## Creating a VXC
After you configure a Port, you can create VXCs to connect to services on the Megaport network. A VXC is a private point-to-point Ethernet connection between your A-End Port and a B-End destination (CSPs, Ports, Megaport Marketplace services, or IX).
For CSP and Private VXCs, when the A-End and B-End are in the same data center location, we recommend matching the Port, MCR, or MVE diversity zone color to the B-End diversity zone color. For example, A-End to B-End is recommended to be *Red to Red* or *Blue to Blue*.
**To create and deploy a VXC**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.\
If you haven't already created a Port, see [Creating a Port](/connections/creating-port).
2. Click **+Connection**.\
For CSPs, Megaport Internet, and IX, you can click the tile as a shortcut.
3. Choose your destination type.
* **Cloud** -- Connectivity to global cloud providers (CSPs), including Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform.\
For more information about connecting to CSPs, see [Cloud Connectivity](/cloud/megaport).
* **Private VXC** -- Connectivity between two locations for a single organization or service provider, traditionally called data center backhaul or Data Center Interconnect (DCI). You can use private VXCs as a core network backbone, or for connecting production and disaster recovery (DR) data centers.\
For more information about creating private VXCs, see [Creating a Private VXC](/connections/private-vxc).
* **Megaport Internet** -- A scalable, on-demand service that allows you to connect to the internet from Ports, MCRs, and MVEs. Connections are available where internet routers are deployed.\
For more information about Megaport Internet, see [Megaport Internet Overview](/megaport-internet).
* **Internet Exchange (IXs)** -- Megaport owns and operates a series of local internet peering exchanges in many global markets. IXs provide greater efficiency between networks and allow for traffic to be exchanged directly, reducing bandwidth usage on your internet connections.\
For more information about IX, see [Internet Exchange Overview](/ix) or [AMS-IX Connectivity](/ix/ams).
* **Megaport Marketplace** -- Connectivity between two different customers located in any of the Megaport Points of Presence (POPs). The Megaport Marketplace connects service providers to enterprise customers while removing the boundaries around physical location.\
For more information about the Megaport Marketplace, see [Megaport Marketplace Overview](/marketplace/overview).
* **Service Key** -- A service key is a code that is given by one Megaport account holder to another to connect two separate businesses together. Customers who have separate Megaport accounts can connect their Ports to each other across the Megaport network, enabling business-to-business VXCs.\
For more information about service keys, see [Setting up Service Keys](/marketplace/service-keys).
* **Megaport Object Storage** -- A dedicated Virtual Cross Connect (VXC) to your S3-compatible object storage provisioned with Latitude.sh.\
For more information about Megaport Object Storage, see [Megaport Object Storage Overview](/storage/object).
4. Step through the procedures to configure your VXC.\
The procedures will vary slightly depending on your destination type.
5. Add the VXC to your order and configure further VXCs or proceed through the checkout process.
**To edit a VXC**
* Click the gear icon next to the connection in the Megaport Portal.
You can modify the details on the Megaport side including the connection name, rate limit, VLAN ID, invoice reference, and contract term.
You can put the VXC on a term, or change the selected contract term.
Once submitted, those changes take effect in a few minutes.
You can change the rate limit when a VXC is on a 12, 24, 36, 48, or 60-month term. For more information, see [Changing the Speed of a Termed VXC](/connections/vxc-termed-rate-change).
# Port Diversity
Source: https://docs.megaport.com/connections/port-diversity
This help topic describes how to configure and manage diverse Ports.
This topic describes how to configure and manage .
Port diversity improves the robustness of your network by providing Port services on different physical devices at a single Megaport location. Ports are assigned to diversity zones. A diversity zone groups devices at the same location to ensure that services are provisioned on physically separate devices that always remain diverse.
Assigning Ports to diversity zones reduces the risk of service interruption due to an impacting event on a single device. For example, during scheduled maintenance, no more than one diversity zone at a given data center location will experience downtime at any moment. If a Port in a diversity zone experiences scheduled downtime, Ports in the other zone at the same location are not affected by that same scheduled maintenance.
Ports deployed at locations supporting diversity are zoned into one of two groups - red or blue. In the Megaport Portal, the Services page **List** view shows a Port's diversity zone assignment as a red or blue label once the Port is live. While a Port is in **Configured** status awaiting its physical Cross Connect, the List view shows a **Download LOA** action in place of the diversity zone label. This information is not shown in the Services page **Diagram** view.
At locations where diversity is supported, you can:
* Create a new Port on a device that is diverse from an existing Port
* Create multiple Ports or LAG bundles as a diverse pair in the same order
## Configuring a Port for diversity
When you create a new Port, you can make it diverse from an existing Port or create a diverse pair of Ports at the same time, with one in each diversity zone.
A Port ordered to a specific zone always remains in that zone. To change a Port diversity zone after placing the order, you must cancel and re-order the Port.
**To configure a Port for diversity**
1. Log in to the Megaport Portal and choose **Services**.
2. Click **Add Services**, then select **Port**.
The Create Port page opens.
3. In the **Details** section, specify a **Port Name**, then in the **Location** section, select a data center location for the Port.\
Use the **Search** field to find a location by metro name, country, data center name, or provider name. You can also search by address details, such as a street, city, state, or postcode. Alternatively, browse the region tabs, then select a location.
4. In the **Provider** section, select a data center provider and data center.\
Only providers and data centers available at your selected location are listed. If your search term in the Location section matches a specific provider or data center, the Provider list narrows to that provider. If the term matches only a metro or country, the Provider list shows every provider available at that location.
5. In the **Configuration** section, specify these fields:
* **Port Speed** -- Select the required Port speed. Port capacity depends on location and service availability. Ensure that your equipment is capable of interfacing with the selected speed. If Port diversity is available at the location and speed you select, a **Diversity Option** drop-down list is enabled. If Port diversity is not available at your preferred location, contact a Megaport Sales representative for more information.
*
* **LACP & LAG Ports** -- Enable LACP on Port if you want the Port to be a member of a LAG. To enable LACP, the Port speed must be 10 Gbps or higher. Select the number of Ports in the LAG, up to a maximum of 8. For more information about LAG, see [Creating a Link Aggregation Group](/connections/lag).
6. In the **Pricing** section, select a **Contract Term** and set **Contract Renewal**.
For more information, see [Port Pricing and Contract Terms](/finance/port-pricing).
7. In the **Add-ons** section, review the following:
* **Cross Connect** -- If the location has Cross Connect availability, a option appears in the Add-ons section.
Enable the **Cross Connect** add-on to add a Cross Connect to your Port order. The monthly rate and one-time fee for the Cross Connect appear on the card.
For more information, see [Ordering a Cross Connect](/connections/cross-connect/).
8. In the **Resource Tags** section, add any tags you want to apply.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
9. Review the order summary.\
The summary shows Port Diversity enabled and the diversity zones for the Ports. If you created a diverse pair of Ports, the monthly charge includes both Ports. If a Cross Connect has been ordered, the summary also shows the monthly rate and the one-time fee for the Cross Connect.
10. Click **Add Port**.\
The newly created Ports, their diversity zones, and the monthly charges are added to your cart.
11. Click **Review Order** to deploy the new Ports now, or click **Save** to save the configured services before placing the order.
12. Click **Create Port** to add more Ports in other locations or click **Order Now** to start provisioning your new Ports.
After the Ports are provisioned, Megaport generates Letters of Authorization (LOAs) specifying the demarcation point to be applied.
1. Click **Download LOA** next to the new Ports on the Services page.\
Megaport will also send you the LOA PDF by email.
2. Provide the LOAs to your data center operator to establish the physical Cross Connects from your network device to your new Ports.
The cost of a new cross connection and any related VXC fees are the responsibility of the customer, as outlined in [Megaport's Global Services Agreement](https://www.megaport.com/legal/global-services-agreement/).
After the Port has been provisioned and deployed, you have access to the Megaport network and can start adding Virtual Cross Connects (VXCs) to the Port. For more information about adding VXCs, see [Creating a VXC](/connections/overview#create_vxc).
# Creating a Private VXC
Source: https://docs.megaport.com/connections/private-vxc
This help topic describes how to connect a private VXC (Virtual Cross Connect) to a Port in the Megaport network.
This topic describes how to connect a private Virtual Cross Connect (VXC) to a Port in the Megaport network.
With a Port 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 Port) 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.
For more information about creating a private VXC for Megaport Cloud Router (MCR), see [Creating an MCR VXC](/mcr/mcr-vxc).
**To deploy a private VXC**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.
If you haven't already created a Port, see [Creating a Port](/connections/creating-port).
2. Select the originating Port (the A-End).
3. Click **+Connection**.
Port details including the speed, location, and diversity zone are displayed.
The diversity zone for an A-End service is visible after the service is deployed and available. The A-End diversity zone is also visible when ordering a diverse pair of Ports. When creating an order with multiple VXCs and diverse Ports, the Port diversity zone will be visible before deploying, preventing you from accidentally crossing zones. When ordering a single Port, you will not see the diversity zone until it is deployed, and not at all if the location does not support diversity.
4. Click **Private VXC**.
The **Private VXC** tile is disabled in the following scenarios:
* You only own one Port, MCR, or MVE. You cannot create a private connection with the same port at both ends.
* You have more than one Port but no MCRs or MVEs, and the other owned Ports have untagged connections.
5. Select the target Port (the B-End) then click **Next**.
For the B-End, the Port details including the speed, location, and diversity zone are displayed.
The diversity zone for a B-End service is visible after the service is deployed and available. The B-End diversity zone is also visible when ordering a diverse pair of Ports. When creating an order with multiple VXCs and diverse Ports, the Port diversity zone will be visible before deploying, preventing you from accidentally crossing zones. When ordering a single Port, you will not see the diversity zone until it is deployed, and not at all if the location does not support diversity.
6. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum VXC size is dynamically calculated based on network routes used to deliver the service. The calculation uses the Ports at each end of the VXC and bases calculations on the lowest rate.
The whole path must be able to support the VXC speed. An error will appear if you try to specify a rate limit that is too high for the path to support.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **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 Port. 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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don’t specify a value, Megaport will assign one.
You can select **Untagged** to deliver an untagged VLAN; however, this consumes the entire Port and prevents any other VXCs from being deployed on this Port.
* **Preferred B-End VLAN** -- Specify the 802.1q VLAN tag for this connection that you will receive through the B-End VLAN.
Selecting **Untagged** for the A-End and B-End provides point-to-point Ethernet connectivity between a pair of dedicated Ports, supporting the forwarding of both untagged and tagged frames (IEEE 802.1q and 802.1ad). Additionally, other protocols like MACsec (802.1ae) will also be forwarded. For supported protocols, frame types, and behaviors, see [Technical Specifications](/tech-specs).
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next** to review the VXC connection summary, including price.
8. Click **Add VXC** to save the VXC.\
Repeat these steps to configure more VXCs.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
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.
You can change the rate limit when a VXC is on a 12, 24, 36, 48, or 60-month term. For more information, see [Changing the Speed of a Termed VXC](/connections/vxc-termed-rate-change).
# Configuring Q-in-Q
Source: https://docs.megaport.com/connections/q-in-q
This help topic describes ways to connect your on-premises network equipment to a CSP that uses Q-in-Q in the Megaport network.
This topic describes ways to connect your on-premises network equipment to a Cloud Service Provider (CSP) that uses , such as Azure ExpressRoute. In addition, because some CSPs require Q-in-Q, but not all network devices support it, or the mixing of single and multiple tags on a single physical interface (“selective Q-in-Q”), this topic includes ways to configure multiple layer VLAN tag handling on network devices without native Q-in-Q support.
## Q-in-Q overview
Q-in-Q, also known as 802.1ad, is a protocol commonly used by network service providers (NSPs) to provide more Layer 2 flexibility. Q-in-Q allows multiple VLAN tags to be inserted into a single Ethernet frame. Stacking multiple VLAN tags in a frame allows isolation of routing domains, because the additional tags identify and separate customer traffic. By using a different VLAN tag for each customer, the traffic is identified within the frame and is transferred throughout the service provider network.
To differentiate the VLAN tags under the 802.1ad standard, the inner commonly uses EtherType 0x8100 and the outer uses 0x88a8. The default configuration for most network vendors' Q-in-Q is for both inner and outer EtherTypes to be 0x8100. The Megaport specification of double-tagged frames is for both inner and outer tags to be 0x8100.
With Q-in-Q, as a packet travels from an NSP or carrier network to a cloud (or other) service provider’s VLAN, inner VLAN tags (C-Tags) that identify the customer traffic are inserted inside of the outer VLAN tags (S-Tags) provided by the service provider. The S-Tag provides a single VLAN that encapsulates multiple VLANs within it. In this configuration, a single VXC may carry the multiple VLAN tags between the two network endpoints.
For more information about Q-in-Q, see [Connecting a VXC](/mcr/mcr-vxc#connectavxcmcr) and the [Megaport blog post *Q & A for Q-in-Q: Part 1*](https://www.megaport.com/blog/q-in-q-questions-answered-part-1/).
For more information about configuring Q-in-Q for Azure, see the [Megaport blog post *Q & A for Q-in-Q: Part 2*](https://www.megaport.com/blog/q-in-q-questions-answered-part-2/).
## Understanding Q-in-Q with Megaport VXCs
A Virtual Cross Connect (VXC) is a point-to-point Layer 2 circuit between two endpoints that is mapped with a VLAN ID on each end, optionally with A and B-End VLAN tags being independently mapped across the Megaport network.
This image shows an Azure ExpressRoute with private peering and Microsoft Peering enabled. A VXC connects a customer edge to a Microsoft edge on VLAN 1000 (S-Tag). The customer edge supports Q-in-Q. The private peering is running on VLAN 100 (C-Tag) and Microsoft Peering is running on VLAN 200 (C-Tag) to establish Layer 3 connections and BGP peering with Azure.
### What if my routers or switches don't support Q-in-Q?
This section describes ways to connect to a B-End service that requires Q-in-Q even when the network equipment terminating your Megaport connection doesn’t natively support it.
| **Q-in-Q Alternatives** | **Method** | **Drawbacks** |
| :- | :- | :- |
| **Single Azure peering VLAN** | You can configure the VXC so that Megaport removes the Q-in-Q requirement by remapping one of the B-End VLAN IDs for Private Peering or Microsoft Peering to the customer Megaport-facing VLAN (A-End). | You can only use a single Microsoft peering type per VXC. |
| **Untag the VXC attached to the customer Port** | You can configure the VXC as untagged to automatically remove the S-Tag. | Untagging a VLAN limits the Port to a single VXC connection. Employing this method means that your Port will only be able to configure a single B-End target, although it will receive all inner/C-Tags from that peer as single/dot1q tagged. |
| **Deploy a Megaport Cloud Router** | You can deploy a Megaport Cloud Router (MCR) to automatically manage the Q-in-Q requirements for one or both peering types. | Additional cost of the MCR and additional VXC to MCR. |
A VXC connecting to Microsoft ExpressRoute may contain one or two inner VLAN tags. These are the C-tags configured in the Microsoft Azure console for the specified peering type. Note that Q-in-Q is a requirement in this scenario, even if only a single Microsoft edge device (primary or secondary) or peering type (private or Microsoft) is employed. Network equipment that supports Q-in-Q is able to access these inner tags by stripping the outer VLAN tag (S-Tag). If your network equipment does not support Q-in-Q, it cannot access the inner tags.
Other Q-in-Q workarounds exist, such as handling at the customer side via multiple devices to de-encapsulate the Q-in-Q frames, or using loopback cables within a single device to manage this via cascading through multiple ports with different VLAN configurations for inner and outer tags. However, this is generally not recommended in production networks.
## Single Azure peering VLAN
For Microsoft Azure ExpressRoute connections, Megaport uses a Microsoft Service Key (and associated primary and secondary target endpoint selection) and provides the ability to *break out* the encapsulated C-Tag for a specified Azure peering type.
You enable this functionality by enabling the Configure Single Azure Peering VLAN in the Connection Details panel of a new ExpressRoute connection, after selecting a primary or secondary target B-End port.
We recommend using the Single Azure Peering VLAN option. This option provides full functionality and the simplest implementation. With Single Azure VLAN, you can use both private or Microsoft peering with a single ER circuit without the need for Q-in-Q capable equipment, an MCR, or an untagged port. Note, you can have only one peering type (private or Microsoft) per VXC with this option so you need two VXCs to use both peering types.
By enabling the Single Azure VLAN Peering VLAN functionality, you can specify a single Azure peering VLAN that will match with the value that you configure (in a future step) for the selected Peering type configuration for the Azure ExpressRoute configuration (via Microsoft Azure portal or other configuration method). For more information, see [Tutorial: Create and modify peering for an ExpressRoute circuit using the Azure portal](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-routing-portal-resource-manager).
If you leave the **Preferred A-End VLAN** field blank, a randomly chosen VLAN will be assigned for your VXC when you place the order, otherwise enter a VLAN and a validation check will be performed to ensure this VLAN is available.
This example shows that an Azure C-tag value of 200 (for either a Private or Microsoft peering type on the associated ExpressRoute circuit) is mapped transparently to a single-tagged VXC VLAN value of 3001. That is, the customer device attached to the physical Megaport interface need not be configured for any Q-in-Q settings, as dot1q VLAN 3001 will be conferred to the associated Microsoft facing B-End edge device as correctly labelled.
In this configuration, it is possible to use both the primary and secondary Microsoft ExpressRoute endpoints on a given ExpressRoute circuit to map to different VLAN tags on a single customer-side port. This is compliant for the purposes of the Azure ExpressRoute Service Level Agreement (SLA). However, we recommend that you employ either single site port and device (zonal) diversity, or split the primary/secondary ExpressRoute connections across two Megaport-enabled locations to ensure no single point of failure exists with the configuration.
For more information about Azure ExpressRoute SLA, see [SLA for Azure ExpressRoute](https://azure.microsoft.com/en-us/support/legal/sla/expressroute/v1_3/).
With this method, it is not possible to use more than one peering type across either of the primary or secondary ExpressRoute facing VXCs, as this tag translation may only occur once per VXC circuit path. Further workarounds are detailed in the following sections, however, note that segmentation of bandwidth between multiple peering types on a single ExpressRoute circuit pair is not currently supported by Microsoft. In most cases, it is preferred to deploy two ExpressRoute pairs to achieve this configuration goal.
The following sections describe workarounds that continue with the Microsoft ExpressRoute example. Note that these workarounds are not unique to Azure endpoints and may also be used for other connections across Megaport where the B-End might specify or require Q-in-Q to carry multiple C-Tag/inner VLANs within a single S-Tag/outer VXC VLAN. The Microsoft ExpressRoute example is used for continuity of the customer scenario.
## Configure the VXC as untagged to automatically manage the S-Tag
Using this method means that the customer Port will only be able to configure a single B-End target, though it will receive all inner/C-tags from that peer as single/dot1q tagged.
You can configure the VXC so Megaport removes the outer VLAN (S-Tag) and presents one or both of the inner VLAN (C-Tag/s) for Private Peering, Microsoft Peering, or both, to the customer Port.
Currently, this process allows only one VXC per ExpressRoute Circuit Connection (selecting from Primary or Secondary port presentation), although both peering types can be supported across this VXC as they will be presented to the customer port as one or two dot1q VLANs (Private, Microsoft Peering, or both).
The customer port will receive the inner VLAN tags as defined on the Azure portal under the specified peering type at the A-End customer port. For more information, see [Connecting to Microsoft Azure ExpressRoute](/cloud/megaport/microsoft).
* Each ExpressRoute subscription includes two port targets at the chosen Microsoft edge location. To take delivery of both the primary and secondary ExpressRoute circuits, you will require two ports from Megaport in this configuration. The Azure VNET VLAN tags are the same across both ports. Megaport cannot change the VLAN tag on the primary and secondary circuits and it cannot deliver the same VLAN twice on the same physical interface.
* If you configure only private or public peering on the Azure ExpressRoute configuration, only the VLAN associated with the ExpressRoute service key will be available on the configured VXC, mapped one-to-one with the customer port.
## Deploy a Megaport Cloud Router
The Megaport Cloud Router (MCR) supports multicloud, multi-region enablement, including support for Q-in-Q to connect to multiple cloud destinations. The S-Tags, or outer tags, belong to the A-End VLAN associated with your MCR and will transparently carry your C-Tags. The S-Tags are automatically configured when provisioning your private and public peering to Azure Cloud in the Megaport Portal. This image shows an example configuration:
When multiple Azure VXCs on an MCR populate the same VLAN 100 tag (private peering) and the same VLAN 200 tag (public peering), MCR manages the Q-in-Q tunnel for each Azure VXC that terminates on the MCR. Each Azure VLAN is still a separate logical interface.
# Shutting Down a VXC for Failover Testing
Source: https://docs.megaport.com/connections/shut-down-vxc
This help topic describes how you can temporarily shut down a VXC for failover testing in the Megaport Portal.
You can temporarily shut down a VXC for failover testing, redundancy, or network design testing purposes. This can be done when creating a VXC, or at a later time after you have created and deployed a VXC on the Megaport network.
When a VXC has been shut down, you can view the VXC service that has been shut down and re-enable the VXC service.
You can also shut down and re-enable an IX service. For more information, see [Shutting Down an IX for Failover Testing](/ix/shutting-down-an-ix).
## VXC shutdown overview
When creating and deploying a VXC on the Megaport network, you can decide whether to set the initial state of the connection to enabled (default) or shut down.
The A-End of an *Active* VXC can be shut down for failover testing and re-enabled once testing is complete. Active VXCs have a provisioning status of Configured, Live, Canceled, or Canceled\_Parent. In the Megaport Portal, the Services page shows the gear icon next to the VXC in bold when the service has been shut down, and the text (Shut Down) is displayed next to the service status.
A VXC that has been shut down can still be edited, locked, and terminated.
You can view service logs and usage reports for a VXC. In the Service Logs, the shutdown action for a VXC is recorded as an event and time stamped. In the Service Graph usage details, the service will go down when it has been shut down. For more information, see [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring).
You can also use the Megaport API to shut down and re-enable VXCs. For more information, see [Shutting Down a VXC and IX with the API](/api/api-vxc-shut-down).
* Billing is **not** suspended during the period when a VXC is shut down.
* As per any VXC speed changes, the shut down/enabled state can take up to two minutes to take effect and be updated in the Megaport Portal.
* For Megaport Marketplace connections, only the A-End company can shut down a service. The B-End can see the state but cannot change it.
## Who can shut down a VXC?
Users who have editing rights with the Company Admin, Technical Admin, and Technical Contact roles and are able to update a service can shut down and re-enable a VXC.
* If a partner shuts down the VXC of a managed account, the partner or the managed account can both re-enable the VXC.
* If a managed account shuts down their own VXC, this can be re-enabled by either the partner or the managed account.
* If a user from a direct account shuts down their own VXC, this can be re-enabled by any user with editing permissions from the same direct account.
## Shutting down a VXC
You can temporarily shut down a VXC for testing purposes. This can be done when creating a VXC or later when editing a VXC. This task describes how to shut down a VXC when editing a VXC.
**To shut down a VXC**
1. In the Megaport Portal, go to the **Services** page and locate the VXC.
2. Click the gear icon next to the connection to make changes.
The Connection Configuration page appears.
3. In the **VXC State** field, click **Shut Down**.\
A prompt appears, asking you to confirm the action.
4. Read the prompt then click **Confirm** and **Save**.\
The VXC is shut down. This can take up to two minutes to take effect and be updated in the Megaport Portal.
**To re-enable a VXC**
1. In the Megaport Portal, go to the **Services** page and locate the VXC that is shut down.
2. Click the gear icon next to the connection.
1. In the **VXC State** field, click **Enabled**.
2. Click **Save**.\
The VXC is now enabled. This can take up to two minutes to take effect and be updated in the Megaport Portal.
# Terminating a Port
Source: https://docs.megaport.com/connections/terminating-port
This help topic describes how to terminate a physical Port directly from the Megaport Portal.
You can terminate a Port directly from the Megaport Portal. Terminating a Port on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about Port contract terms, see [Port Pricing and Contract Terms](/finance/port-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate a Port**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the Port you want to terminate.
The Terminate Services window appears. Early termination fees will display here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the Port. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the Port termination, or click **No, Keep Services** to cancel.\
The Port and its associated VXCs are deleted from the Megaport network.
Terminating a Port that is configured as part of a diversity pair reverts the diversity setting of the other Port in the pairing. For example, if Port 1 is diverse from Port 2 and you terminate Port 2, Port 1 loses its diversity setting. You are prompted for confirmation.
## Terminating a diverse Port
Usually, terminating a Port that is deployed in a diversity-enabled location is the same as terminating any other Port. However, if you configure a new, unpurchased Port to be diverse from a deployed Port, and you then delete the deployed Port, the new Port will lose its diversity setting.\
For example, consider the following scenario:
* Port 1 is purchased and deployed.
* Port 2 is configured to be diverse from Port 1, but you haven't finalized the order.
In this scenario, if you terminate Port 1 then Port 2 will have its diversity setting removed after you confirm the termination. To reconfigure Port 2 to be diverse from a different Port, you must edit Port 2.
For more information about diverse Ports, see [Port Diversity](/connections/port-diversity).
# Terminating a VXC
Source: https://docs.megaport.com/connections/terminating-vxc
This help topic describes how to terminate a VXC directly from the Megaport Portal.
You can terminate a VXC directly from the Megaport Portal.
VXCs can be individually terminated or are terminated as part of terminating the attached Port, MCR, or MVE.
Terminating a VXC on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. For more information about VXC contract terms, see [VXC Pricing and Contract Terms](/finance/vxc-pricing/).
You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/aruba/terminating-mve).
**To terminate a VXC**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the VXC you want to terminate.
The Terminate Services window appears. Early termination fees will be shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the VXC. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the VXC termination, or click **No, Keep Services** to cancel.\
The VXC is deleted from the Megaport network.
# Changing the Speed of a Termed VXC
Source: https://docs.megaport.com/connections/vxc-termed-rate-change
This help topic describes how changing the rate limit on a termed Megaport Virtual Cross Connect (VXC) works.
If you have a Virtual Cross Connect (VXC) on a contract term, you can change the speed of the VXC.
When you put a VXC on a contract term, you specify a rate limit, which is called the **committed term speed**. This is the minimum speed allowed on the VXC during that contract term. The maximum VXC size is dynamically calculated based on network routes used to deliver the service. The VXC rate limit size cannot exceed the speed of the physical interface on which it resides.
There are restrictions on the changes that you can make to the rate limit of a termed VXC:
* You can increase the speed to the maximum limit allowed.
* You can reduce the speed to the committed term speed.
You can change the speed as many times as you need during a term within the restrictions.
## VXC speed change example
As an example, you create a VXC on a 12-month term with a rate limit of 5 Gbps. This is the committed term speed.\
The maximum limit allowed is calculated as 10 Gbps when you create the VXC.
If you need to increase the speed, you can set it to a value between 5 Gbps and 10 Gbps. You cannot set it to more than 10 Gbps.\
When you want to decrease the speed, you cannot decrease it to less than 5 Gbps.
## Pricing
The pricing rules for rate limit changes to a termed VXC are as follows:
* The term discount is applied as a fixed monthly amount and does not change throughout the term length, regardless of any speed changes.
* The fixed monthly discount amount is calculated off the percentage discount associated with the selected term length and original committed term speed.
This means that if you increase the speed of a VXC on term, the term discount does not increase, but remains fixed to the original discounted amount based on the original committed term speed.
* If you change the VXC speed, the service will be repriced at the current market rate.
* If minimum term renewal is enabled, the contract will renew at the same market rate and term discount applied as when the speed change was ordered.
### Pricing example
In this scenario, a 1 Gbps private VXC is created on a contract term. The table below shows the rack rate price, term discount, and total charged for each term duration.
| 1 Gbps Metro Private VXC | No Min Term | 12 Months | 24 Months | 36 Months |
| - | - | - | - | - |
| Rack Rate Price | \$120 | \$120 | \$120 | \$120 |
| Term Discount | \$0 | \$20 | \$25 | \$30 |
| Total | \$120 | \$100 | \$95 | \$90 |
If the speed of this service is increased to 10 Gbps on the 1st of the month, the following pricing will apply:
| 1 Gbps Metro Private VXC updated to 10 Gbps | No Min Term | 12 Months | 24 Months | 36 Months |
| - | - | - | - | - |
| Rack Rate Price | \$240 | \$240 | \$240 | \$240 |
| Term Discount | \$0 | \$20 | \$25 | \$30 |
| Total | \$240 | \$220 | \$215 | \$210 |
| Charge increase | \$120 ⬆ | \$120 ⬆ | \$120 ⬆ | \$120 ⬆ |
Note the rack rate price rises with the speed increase, but the term discount remains the same.
**Invoicing**
You will see two line items on your invoice:
* The service rack rate charge at the Month to Month/No Minimum Term rate.
* The Fixed Monthly Term Discount.
## Canceling the VXC
If the termed VXC is canceled, the early termination fee (ETF) is calculated based on the committed term speed, not the speed when the VXC is canceled.
## Considerations
If you need greater flexibility in terms of increasing or decreasing the VXC speed, you might benefit from ordering a VXC on term at the minimum speed you require. This way, although the term discount will be lower, you will still get a term discount, with the added benefit of being able to adjust the speed as required. If you order the VXC on No Minimum Term, you will receive no discount at all.
If you don’t anticipate the need to adjust the speed of the VXC regularly, you should order the VXC on term at the speed required to benefit from a higher term discount.
## Helpful references
* [Connections Overview](/connections/overview)
* [Creating a Private VXC](/connections/private-vxc)
* [Quoting Service Cost](/finance/creating-estimates)
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Megaport Portal Dashboard
Source: https://docs.megaport.com/dashboard/index
This help topic describes how to use the Megaport Portal dashboard with the rotating globe feature.
The Megaport Portal dashboard is an interactive experience that can show either a rotating globe or a flat projection. You can use the visualizations to see your Megaport defined network. You can also use it to add connections and services to your network.
## Dashboard views
By default, you will see the interactive globe view. To change to the flat projection, click the flat map image on the right:
For more information, see [Map controls on the right](#map-right).
## Maintenance and outage banner
At the top of the page, a banner will be displayed to inform you about any future or ongoing maintenance or outages. If there are no maintenance or outages, the banner will not be displayed.
The banner will only show events three days before the maintenance or outage is scheduled to occur.
Select **View All** to see details about the maintenance or outage.
Click **X** to close the banner.
## Map controls
There are control buttons on each side of the map, and a status bar along the bottom that summarizes your services. The buttons let you control what you see on the dashboard, and the status bar shows your service status at a glance.
Hover the mouse over each control on the map to see its purpose.
### Move the globe
To manipulate the globe view, click and drag on the globe.
* On a standard mouse, left-click and drag
* On an Apple magic mouse, click and drag
* On a tablet, touch and drag
### Advanced globe view manipulation
You can use commands to completely invert the globe. This is useful if you want to view your network in a certain way, or to take screenshots of parts of your network that can only be seen this way.
**To invert the globe view to north at the bottom**
* With a standard mouse, drag sideways while holding the right button or drag sideways while holding *ctrl* and left button
* On a keyboard, click *shift* + left or right arrows
**To restore the globe view to north at the top**
* With a standard mouse, drag sideways while holding the right button or drag sideways while holding *ctrl* and left button
* On the keyboard, click *shift* + up arrow.
### Map controls on the left
The controls on the left side of the map help you control how much information you see. Use the location filter buttons at the top of the left controls to choose which locations appear on the map.
| Control | Purpose |
| :-: | - |
| | Show all locations. Displays all location types, including installed locations (Active and Deployment), [extended locations](#extended-locations), and locations where you have services. This is the default view. |
| | Show installed locations. Displays only installed Megaport locations (Active and Deployment status) where you can order services directly. Occupied locations (locations where you have services) and extended locations are hidden. |
| | Show extended locations. Displays only [extended locations](#extended-locations). Installed locations and locations where you have services are hidden. |
| | Show locations where you have services. Displays only locations where you have deployed services, along with connection lines between them. Empty locations (where you have no services) are hidden. |
| | Filter empty locations. See [Locations](/dashboard#locations) for more information about empty locations. |
| | Map key. This explains what the icons, colors, and links mean on the map, including the distinction between installed and extended locations. |
| | Keyboard commands to control the map, including zoom and changing orientation. |
### Search
The search function allows you to search the map for:
* Any service type. For example, VXC.
* A service name
* A product ID
* Megaport enabled locations but only if you do not have this turned off in your map settings
* Any place name in the world
### Map controls on the right
The controls on the right side of the map set the screen mode (normal or full-screen), the view (globe or flat map), and the level of zoom.
| Control | Purpose |
| :-: | - |
| | Expand the map or globe to full screen. The Megaport Portal header and options are hidden. To return to normal view, click **Exit full screen**. |
| | Show the rotating globe view. |
| | Show the flat map view. |
| | Zoom in with large increments. |
| | Zoom in with small increments. |
| | Zoom out with small increments. |
| | Zoom out with large increments. |
### Service status bar
The service status bar is a full-width bar along the bottom of the map that summarizes the status of your configured services.
From left to right, the bar begins with an **All Services** tile that aggregates the up and down totals across all service types. This is followed by a tile for each service type you have. Service types with no services are not shown.
Each tile shows:
* A circular status indicator divided into segments that represent the proportion of services that are up or down.
* The total number of services for that service type.
* A status summary showing the number of services that are down (for example, *3 down*), or *all up* when none are down.
You can minimize the bar to a small pill that displays the total number of services. Click the pill to expand the bar again. Your browser remembers whether the bar was last minimized or expanded.
If you do not have any services yet, the bar shows a **No services yet** message instead of tiles.
## Locations
Each Megaport location is marked by a pin. The color of the pin indicates the location type and status:
| Pin | Status |
| :-: | - |
| | Blue for occupied. An occupied location means that you have a Port or other network component at that location, or you have a connection that terminates on someone else's Port or network component at that location. |
| | Red for installed empty. An installed (empty) location means that Megaport hardware is available at that data center, but you do not currently have any services there. You can order services directly at these locations. |
| | Black for extended empty. An [extended location](#extended-locations) is a data center where Megaport hardware is not physically present, but services are available through a private connection from a nearby installed location. |
Use the location filter buttons on the left side of the map to show or hide specific location types. For more information, see [Map controls on the left](#map-left).
### Location clusters
When you click a cluster of either occupied or empty locations, it will zoom in to show the next level of services expanded to show each service or location. The color of the icon shows the status of the service:
* Green for up and running
* Red for provisioned but not running
* Black for ports or connections that you do not own
There is also a location icon, which you can click to create services and get location details.
When you zoom out and the occupied locations are clustered, the number in the circle indicates the number of connections present in the clustered locations. The circle drawn around it shows the proportion of them that are up or down. The colors represent:
* Green for up
* Red for down
### Location functions
When a location is expanded, you can click the location icon to see a pop-up with buttons that allow you to create available services or connections at that location.
For more information about creating services, see [Provision services](/getting-started#provision-services).
### Extended locations
Extended locations are data centers in the same campus or metro area as an installed Megaport location. Megaport hardware is not physically present at extended locations, but you can access services through a private cross connect from an installed location. You can order this cross connect to the Megaport installed location from your Data Center Operator at the extended location.
To view extended locations on the map, use the location filter buttons on the left side:
* Click the **white pin** button to show all locations, including extended locations alongside installed and occupied locations.
* Click the **black pin** button to show only extended locations and hide all other location types.
Extended locations appear with black pins on the map. When you click an extended location pin, the pop-up shows:
* The data center name, metro, and country
* A banner indicating that the location is extended via private connection from installed sites
* A list of installed (parent) sites that connect to the extended location
To order services at an extended location, contact your Account Manager for assistance. Services are created from the installed (parent) locations, not directly at extended locations.
For more information about location types, see [Understanding Locations](/enabled-locations).
## Component control
When you have focus on a location, you can keep clicking down to an individual service.
You can use the map interface to see details, create, and remove services or connections. Click a service or connection icon to expand it and see the details.
### See service details
Click an icon to see the details for that service.
### Add network connections
You can add network connections from the Megaport Portal dashboard.
**To add network connections**
1. Click the Port or connection icon.
You will see a pop-up window that allows you to add a service.
2. Click **+Connection** to open the New Connection page.
For more information about creating services, see [Connections Overview](/connections/overview).
The Megaport Portal saves where you were on the map if you head off to create or view services. When you finish that process, it takes you back to where you were. The Megaport Portal also saves your view of the map and will return you to the same zoom level so you see it as you last saw it.
### Update network connections
You can use the service pop-up to change settings or delete the service.
Click the button to copy the service identifier.
## Connections
Connection lines can represent one or more connections between two locations.
The color of the connection line indicates the status of the connection:
* Green for up
* Red for down
When you click a connection icon, the pop-up displays the ends according to their relative geographic location. This means that the button on the left will take you to the Port at the geographical left and the same for the right side.
Click the A-End or B-End ports to go directly to that Port.
# Managing Connectivity with Megaport's APIs as a Service Provider
Source: https://docs.megaport.com/deployment/csp-integration/index
This help topic describes how an example service provider can integrate Megaport and automate the related tasks using Megaport APIs.
Service providers can seamlessly integrate Megaport's functionality into their platform. They can control customer access to their on-ramps, such as Ports.
Service providers can use a service key to manage customer access and secure connectivity to their on-ramps. They can set specific rate limits and segment customer traffic using VLANs.
A service key is a code that is given by one Megaport account holder to another to connect two separate businesses together. Customers who have separate Megaport accounts can connect their Ports, MCRs, MVEs, and NAT Gateways to each other across the Megaport network, enabling business-to-business VXCs.
Before allowing their customers to connect to an on-ramp using a service key, a service provider must first connect to the Megaport network. Once connected they must:
* decide which of their connections should be used as on-ramps
* map those on-ramp location to their user-defined regions or zones
* consider the capacity and diversity zones for redundancy management
This topic describes how you, as a service provider, can use Megaport APIs to reduce manual effort and enable faster provisioning of services. This will make it easier to sell private connectivity to your customers.
## Scenario
QuantumGPU is a small service provider company, headquartered in Los Angeles, California, serving as a self-service, on-demand GPU-as-a-Service (GPUaaS) platform. Empowering businesses with GPU-accelerated computing across diverse geographic locations, QuantumGPU operates the following Ports:
* 2 Ports in Los Angeles, USA (Equinix LA1 and CoreSite LA1)
* 1 Port in New York, United States (Telehouse)
* 1 Port in London, United Kingdom (Telehouse North)
* 1 Port in Osaka, Japan (Equinix OS1)
* 1 Port in Sydney, Australia (Global Switch Sydney West)
QuantumGPU needs to control how their customers connect to the Ports and automate the process with APIs.
QuantumGPU (service provider) plans to implement the following scenario:
## Related terms
Ensure that you are familiar with the following terminology used in this topic:
**Megaport Cloud Router (MCR)**
**Megaport Virtual Edge (MVE)**
**On-ramp**
An on-ramp is a direct, private connection to a service provider's available resources, for example, via a Megaport connection. To ensure fast and reliable connections, the service provider maps these resources to their regions or zones, sets rate limits, manages per-customer VLAN capacity, and so on.
**Port**
**Port diversity**
**Service key**
A service key is a code that is given by one Megaport account holder to another to connect two separate businesses together. Customers who have separate Megaport accounts can connect their Ports, MCRs, MVEs, and NAT Gateways to each other across the Megaport network, enabling business-to-business VXCs.
**Virtual Cross Connect (VXC)**
## Authenticating as an API user
Before you can use the Megaport APIs, you must authenticate with an access token. Before you can generate the access token, you must create an API key in the Megaport Portal. For more information, see [Creating an API Key](/api/api-key).
The API key consists of a client ID and a client secret. You can use it to generate the access token that is used to authenticate as an API user.
Access tokens are valid for 24 hours and must be regenerated after that time. Your integration with Megaport's API will need to take this into account. For more information, see [Generating an access token](/api/api-key#accesstoken).
## Managing on-ramps
When your customer requests a connection to you, you will need to map the region or zone of the connection to a physical on-ramp to generate the service key.
This section describes the API calls to map your users' service region or zone to your Megaport on-ramp. Megaport location and product identifiers are constant so this can be cached or stored safely without needing to refresh every time.
These instructions describe how to do this using Postman and the Megaport API collection. For more information about the Postman setup, see [Megaport API Overview](/api).
### Prerequisites
This section assumes that you:
* have integrated Megaport into your platform. For more information, see [Integrating Megaport into your platform](/deployment/csp-integration#integrating).
* are authenticated as an API user. For more information, see [Authenticating as an API user](/deployment/csp-integration#authenticating).
### Listing on-ramp locations
This task describes how you can look up and list your available on-ramp locations (Port locations in our scenario) using the location identifiers.
**To list on-ramp locations**
This example uses Ports, but you can also use MCRs and MVEs.
1. After your customer requests to connect to an on-ramp, for example, a Port, use the **Get Product List API** with `"provisioningStatus": "LIVE"`to look up all the live Ports that you own.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET /v2/products?provisioningStatus=LIVE
```
2. Filter and list the response using the **country** value.
```json {7} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"locationId": 60,
"location": "CoreSite LA1",
"locationDetail": {
"name": "CoreSite LA1",
"city": "Los Angeles",
"metro": "Los Angeles",
"country": "USA"
```
In our scenario, the list is as follows:
* USA
* UK
* Japan
* Australia
3. After your customer selects a region (USA), filter and list the response on the **metro** value.
```json {6} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"locationId": 60,
"location": "CoreSite LA1",
"locationDetail": {
"name": "CoreSite LA1",
"city": "Los Angeles",
"metro": "Los Angeles",
"country": "USA"
```
In our scenario, the list is as follows:
* Los Angeles
* New York
4. After your customer selects a region (US-West), filter and list the response on the **locationId** value.
```json {1} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"locationId": 60,
"location": "CoreSite LA1",
"locationDetail": {
"name": "CoreSite LA1",
"city": "Los Angeles",
"metro": "Los Angeles",
"country": "USA"
```
In our scenario, the list is as follows:
* "locationId": **59**
* "locationId": **60**
### Mapping an on-ramp location to a user-defined region or zone
You can use the listed location identifiers, such as **locationId**, **metro**, or **country** and map them to your predefined custom region or zone names.
By mapping the available on-ramps, like Los Angeles 1 (**"locationId": 59**) and Los Angeles 2 (**"locationId": 60**), to the predefined US-West region, your customers can select US-West on your platform and connect to an available on-ramp.
### Selecting an on-ramp
You can use APIs to identify which on-ramp to connect to, for example, to connect to the Port with the least usage. You can consider factors such as the number of connections, capacity, or utilization. Additionally, you can consider factors like diversity zones to manage redundancy.
Use the response of the filtered Ports to consider the Port attributes as follows:
| Attribute | Consider |
| - | - |
| diversityZone | Check if the current location supports diversity. For more information, see [Port Diversity](/connections/port-diversity). |
| portSpeed | Check the available speed of the Port. |
| rateLimit | The VXC rate limit cannot exceed the speed of the lowest speed Port. For more information, see [Connections Overview](/connections/overview). |
| associatedVxcs | Check if VXCs are associated with the Port and the allocated capacity. |
| maxVxcSpeed | Check the maximum VXC speed available for the Port. |
| vxcPermitted | Ensure that the **vxcPermitted** is true. If the **vxcPermitted** value is false, you cannot create a VXC to that Port. |
After considering the selected Ports, you can display a Port that meets the required criteria, for example, a Port with the least usage. For more information, see [Megaport API Overview](/api).
## Managing connections
By following best practices in managing the service keys and VLAN IDs, you can maintain organized and secure connections.
### Managing service keys
Service keys allow your customers to establish connections to your specific on-ramps.
Managing service keys involves creating, sharing, and monitoring the service keys.
This process is shown and explained in more detail below:
After you select the on-ramp service, you can create a service key to the on-ramp. Creating the service key has no extra cost to you, regardless of whether your customer uses the key or not.
Share the service key with your customer. Optionally, create a workflow for your customer, outlining the necessary steps and an indicative timeframe to use the received service key.
As a prerequisite, your customer must have an account with Megaport and have an available Port.
Using the service key, your customer can create a VXC and connect to the on-ramp based on the parameters you specified. Your customer is responsible for the VXC charges associated with the selected on-ramp location.
Use the **GET List Service Keys** API to continually monitor and keep track of the status of your service keys. For example, check if a service key you created and sent to a customer has been used. After your customer uses the service key, it becomes obsolete, and the service key ID is not kept. This means that there is no connection between the service key and the service it activated.
The service key is service-specific. To ensure redundancy and resilience in the event of failures or disruptions, we recommend that you create on-ramps located in different diversity zones. In this case, you must also create separate service keys for each on-ramp, for example:
* 1 key for Los Angeles 1 in the blue diversity zone
* 1 key for Los Angeles 2 in the red diversity zone
You can create either a single-use or a multi-use service key. With a single-use service key, the customer you share the key with can request a single connection to a specific on-ramp. With a multi-use key, the customer with whom you share the key can request multiple connections. In such instances, the system automatically allocates the next available VLAN ID.
### Managing VLAN IDs
For single-use service keys, specify a VLAN ID, which you can use to link customers to their respective VXCs. When you assign a VLAN ID to the service key, it indicates that the assigned VXC is dedicated to a specific customer. Each VXC is delivered as a separate VLAN on your on-ramp. This must be a unique VLAN ID on this on-ramp and can range from 2 to 4093.
For single-use service keys, you can also specify **untagged**, which does not allocate a VLAN ID. For more information, see [Setting up Service Keys](/marketplace/service-keys).
The image below shows that you assigned different VLAN IDs for each customer as follows:
* VLAN ID 100 assigned to Customer 1
* VLAN ID 200 assigned to Customer 2
The VLAN IDs (100 and 200) assigned by you can differ from the VLAN IDs assigned by your customers (123 and 10), or the VLAN IDs assigned to other Port connections they have, such as those to cloud service providers like AWS, Oracle, or Azure (124, 125 and 20).
For more information, see [Setting up Service Keys](/marketplace/service-keys) and [Creating a Service Key with the API](/api/api-create-servicekey).
## Summary
This topic described how you can efficiently manage customer connections to your on-ramps.
Using Megaport APIs, to look up Ports, select Ports based on capacity, diversity, and so on, you can automate the process, reducing manual effort and enabling rapid service provisioning.
### Summary of APIs used
This table shows the process and the APIs used in this scenario:
This example uses Ports, but the same process is used for MCRs and MVEs.
| Action by the service provider’s customer | Action by the service provider | API requests and values used for filtering | Result |
| - | - | - | - |
| On the service provider’s platform, request a connection to an on-ramp. | List regions with live Ports, MCRs, or MVEs. | GET /v2/products? provisioningStatus=LIVE
List `"country"` values. |
USA
UK
Japan
Australia
|
| Select a region (USA). | List cities with live Ports, MCRs, or MVEs in the USA. | GET /v2/products? provisioningStatus=LIVE \&country=USA
List `"metro"` values. |
Los Angeles
New York
|
| | List Ports in Los Angeles.
Map the available Ports for example, Los Angeles 1 ("locationId": 59) and Los Angeles 2 ("locationId": 60) to a region called US-West. Then, in your platform, your customers can connect to one of the available Ports in US-West.
Decide which on-ramp to offer to the customer. Consider capacity/usage and diversity. | GET /v2/products? provisioningStatus=LIVE \&country=USA\&metro=Los Angeles
List `"locationId"` values. |
Equinix LA1 (“locationId”: 59)
CoreSite LA1 (“locationId”: 60)
|
| Select US-West and add diversity. | Create service keys to the selected Ports.
Send the service keys back to your customer. | POST /v2/service/key
Required value: `"productUid"` | 2 separate keys are created for:
Los Angeles 1 (blue zone)
Los Angeles 2 (red zone)
Example key: "key": "106e38ae-eb59-415f-ac81-526a5299851d", |
| Create connections with the service keys. | | | |
### Integrating Megaport into your platform
For an example on how to integrate Megaport into your platform, see the demo project at [https://github.com/megaport/megaportgo](https://github.com/megaport/megaportgo).
# Megaport Global Mesh WAN Overview
Source: https://docs.megaport.com/deployment/global-mesh-wan/index
This help topic describes what Megaport Global Mesh WAN is and provides detailed information on how to order it.
Megaport Global Mesh WAN is a fully managed, cloud-ready Wide Area Network (WAN) service built for organizations with distributed locations. Unlike traditional setups that require a direct point-to-point connection between every site, Megaport Global Mesh WAN enables seamless and flexible connectivity among multiple data centers and sites.
Megaport Global Mesh WAN provides a secure, scalable, and cost-effective solution for interconnecting offices, data centers, and cloud regions globally. It effectively eliminates the complexity of traditional WAN provisioning by seamlessly integrating your Megaport services.
Leveraging its underlying Megaport mesh architecture, the service provides you with resilient, low-latency paths between all sites, alongside the flexibility to scale bandwidth on demand.
Megaport Global Mesh WAN delivers predictable performance, reduces operational overhead, and offers an affordable model designed to meet stringent security and compliance requirements.
## Key benefits of Megaport Global Mesh WAN
* **Global reach** -- Connect distributed sites, data centers, and clouds across multiple regions seamlessly.
* **Resilient architecture** -- Megaport’s mesh design and red and blue zone diversity deployment ensure high availability, redundancy, and optimized traffic flows.\
For more information about diversity zones, see [Port Diversity](/connections/port-diversity), [MCR Diversity](/mcr/mcr-mve-diversity), and [MVE Diversity](/mve/mcr-mve-diversity).
* **Scalable and elastic** -- Instantly adjust bandwidth and extend your network reach without complex re-engineering.
* **Cost-effective** -- Achieve enterprise-grade connectivity at a fraction of the cost of traditional WAN solutions.
* **Premium support** -- Access a dedicated Megaport Technical Account Manager (TAM) for proactive guidance and continuous support for your WAN environment.
## Types of Megaport Global Mesh WAN
Megaport offers these types of Mesh WAN services:
| **WAN Type** | **Deployment Strategy** |
| - | - |
| Domestic WAN | Required services are deployed in Megaport-enabled locations that are all located within the same country. This ensures localized, low-latency connectivity for national resources.
This service is currently available in Australia, Canada, and the USA. |
| Regional WAN | Required services are deployed in Megaport-enabled locations across multiple countries within the same region.
This service is available in Asia-Pacific (APAC), Europe, the Middle East, and Africa (EMEA), North America (NAM), and Latin America (LATAM) regions. |
| Trans Atlantic WAN | Required services are deployed on both sides of the Atlantic Ocean.
This service is available for routes between the US and Europe. |
| Global WAN | Required services are deployed across numerous regions worldwide, including APAC, EMEA, NAM and LATAM. Your network infrastructure is unified into a single logical mesh network. |
The following network diagram represents the fundamental concept of the Megaport Global Mesh WAN. The structure is consistently applied irrespective of the geographical scope of the four types of Global Mesh WAN. Megaport handles the entire mesh infrastructure, completely offloading your network management workload. You only need to establish connections to your chosen locations within the mesh via Virtual Cross Connects (VXCs).
## Ordering Megaport Global Mesh WAN
Below is a step-by-step workflow that describes how to order a Megaport Global Mesh WAN.
1. Contact your Megaport Account Manager or Solution Architect to discuss your requirements. We will use those requirements to design a network solution that meets your needs.
2. After you and Megaport agree on the proposed solution, your Megaport Account Manager will provide a Manual Service Order (MSO) form for your review and acceptance of pricing, terms, and conditions.
3. After you sign the MSO, your Megaport account team will configure the network as designed. If you need additional implementation support, tell your account team, and Megaport will introduce you to a Technical Account Manager (TAM) to discuss professional services.
4. You can then use these services through the Megaport Portal.
## Helpful references
* [MCR Diversity](/mcr/mcr-mve-diversity)
* [MVE Diversity](/mve/mcr-mve-diversity)
* [Port Diversity](/connections/port-diversity)
* [Understanding Locations](/enabled-locations)
# Common Multicloud Connectivity Scenarios
Source: https://docs.megaport.com/deployment/multicloud/index
This help topic describes common design scenarios using Megaport for multicloud and hybrid cloud connectivity.
This topic describes some common connectivity design scenarios using Megaport , , and . The scenarios range from a simple partially-protected network to an end-to-end highly available resilient network for and hybrid cloud.
For more information about different multicloud scenarios and defining your connectivity requirements, see the [Design Scenarios for Multicloud -- Diversity and Design Principles blog](https://www.megaport.com/blog/design-scenarios-for-multicloud/). You can also download our Multicloud Network Blueprints Infopaper at [Multicloud Network Blueprints](https://www.megaport.com/pdf/megaport_multicloud_blueprints.pdf).
To help you architect your multicloud solution, you can [download a Visio (VSDX) file](https://go.megaport.com/multicloud-vsdx-download.html) with these scenarios.
Hybrid multicloud, non-redundant.
Includes a single Port connecting to each CSP.
| Property | Value |
| - | - |
| HA design | No |
| Multicloud | Yes |
| On-premises data center (colocation) or office | Yes - 1 DC |
| On-premises geographically close to CSPs | N/A |
| Diverse regions | No |
**Prerequisites**
* Customer (on-premises) network equipment supports LX optical 1 Gbps, LR optical 10 Gbps, or LR4 100 Gbps ports
* Customer (on-premises) network equipment supports BGP
* Customer (on-premises) network equipment supports IEEE 802.1ad (Q-in-Q) -- Specifically for Microsoft Azure
If 802.1ad not supported, use Scenario 3 (MCR).
| Megaport Technology | Required | How many? |
| - | - | - |
| Port | Yes | 1 |
| Megaport Cloud Router (MCR) | No | |
| Megaport Virtual Edge (MVE) | No | |
| Virtual Cross Connect (VXC) | Yes | 4 (1 for each CSP) |
Hybrid multicloud, non-redundant.
Includes dual Ports configured as a connecting to each CSP in a HA configuration.
| Property | Value |
| - | - |
| HA design | Yes |
| Multicloud | Yes |
| On-premises data center (colocation) or office | Yes - 1 DC |
| On-premises geographically close to CSPs | N/A |
| Diverse regions | No |
**Prerequisites**
* Customer (on-premises) network equipment supports LX optical 1 Gbps, LR optical 10 Gbps, or LR4 100 Gbps ports
* Customer (on-premises) network equipment supports BGP
* Customer (on-premises) network equipment supports IEEE 802.1ad (Q-in-Q) -- Specifically for Microsoft Azure
If 802.1ad not supported, use Scenario 3 (MCR).
| Megaport Technology | Required | How many? |
| - | - | - |
| Port | Yes | 2 (in LAG) |
| Megaport Cloud Router (MCR) | No | |
| Megaport Virtual Edge (MVE) | No | |
| Virtual Cross Connect (VXC) | Yes | 8 (2 for each CSP) |
Hybrid cloud-to-cloud, non-redundant.
Includes an MCR as a hub connecting a single Port in a DC with CSPs.
| Property | Value |
| - | - |
| HA design | No |
| Multicloud | Yes |
| On-premises data center (colocation) or office | Yes - 1 DC |
| On-premises geographically close to CSPs | N/A |
| Diverse regions | No |
**Prerequisites**
* Customer (on-premises) network equipment supports LX optical 1 Gbps, LR optical 10 Gbps, or LR4 100 Gbps ports
* Customer (on-premises) network equipment supports BGP (for better path selection, not mandatory)
| Megaport Technology | Required | How many? |
| - | - | - |
| Port | Yes | 1 |
| Megaport Cloud Router (MCR) | Yes | 1 |
| Megaport Virtual Edge (MVE) | No | |
| Virtual Cross Connect (VXC) | Yes | 5 (Including 1 for each CSP) |
Hybrid multicloud, redundant (single location).
Includes a Port in each diversity zone connecting to each CSP in a HA configuration.
| Property | Value |
| - | - |
| HA design | Yes |
| Multicloud | Yes |
| On-premises data center (colocation) or office | Yes |
| On-premises geographically close to CSPs | N/A |
| Diverse regions | No |
**Prerequisites**
* Customer (on-premises) network equipment supports LX optical 1 Gbps, LR optical 10 Gbps, or LR4 100 Gbps ports
* Customer (on-premises) network equipment supports BGP
* Customer (on-premises) network equipment supports IEEE 802.1ad (Q-in-Q) -- Specifically for Azure
If 802.1ad not supported, use MCR (Scenario 6).
| Megaport Technology | Required | How many? |
| - | - | - |
| Port | Yes | 2 (4 in a LAG) |
| Megaport Cloud Router (MCR) | No | |
| Megaport Virtual Edge (MVE) | No | |
| Virtual Cross Connect (VXC) | Yes | 8 (2 for each CSP) |
Cloud-native, redundant.
Includes dual MCRs as hubs that connect CSPs in a HA configuration without requiring on-premises infrastructure.
| Property | Value |
| - | - |
| HA design | Yes |
| Multicloud | Yes |
| On-premises data center (colocation) or office | No |
| On-premises geographically close to CSPs | N/A |
| Diverse regions | No |
**Prerequisites**
* None required
| Megaport Technology | Required | How many? |
| - | - | - |
| Port | No | |
| Megaport Cloud Router (MCR) | Yes | 2 |
| Megaport Virtual Edge (MVE) | No | |
| Virtual Cross Connect (VXC) | Yes | 8 (2 for each CSP) |
Hybrid cloud-to-cloud, redundant (single location).
Includes dual MCRs as hubs that connect a DC with a Port in each diversity zone to CSPs in a HA configuration.
| Property | Value |
| - | - |
| HA design | Yes |
| Multicloud | Yes |
| On-premises data center (colocation) or office | Yes |
| On-premises geographically close to CSPs | N/A |
| Diverse regions | No |
**Prerequisites**
* Customer (on-premises) network equipment supports LX optical 1 Gbps, LR optical 10 Gbps, or LR4 100 Gbps ports
* Customer (on-premises) network equipment supports BGP (for better path selection, not mandatory).
| Megaport Technology | Required | How many? |
| - | - | - |
| Port | Yes | 2 (4 in a LAG) |
| Megaport Cloud Router (MCR) | Yes | 2 |
| Megaport Virtual Edge (MVE) | No | |
| Virtual Cross Connect (VXC) | Yes | 10 (Including 2 for each CSP) |
Hybrid multicloud, additional redundancy (multiple locations or regions).
Includes a single Port in each DC connecting to CSPs in HA configuration.
| Property | Value |
| - | - |
| HA design | Yes |
| Multicloud | Yes |
| On-premises data center (colocation) or office | Yes - 2 DCs |
| On-premises geographically close to CSPs | N/A |
| Diverse regions | Yes |
**Prerequisites**
* Customer (on-premises) network equipment supports LX optical 1 Gbps, LR optical 10 Gbps, or LR4 100 Gbps ports
* Customer (on-premises) network equipment supports BGP
* Customer (on-premises) network equipment supports IEEE 802.1ad (Q-in-Q) -- Specifically for Azure
If 802.1ad not supported, use MCR (Scenario 8).
| Megaport Technology | Required | How many? |
| - | - | - |
| Port | Yes | 2 (4 in a LAG) |
| Megaport Cloud Router (MCR) | No | |
| Megaport Virtual Edge (MVE) | No | |
| Virtual Cross Connect (VXC) | Yes | 8 (2 for each CSP) |
Hybrid cloud-to-cloud, additional redundancy (multiple locations or regions).
Includes dual MCRs as hubs that connect DCs with Ports to CSPs in a HA configuration.
| Property | Value |
| - | - |
| HA design | Yes |
| Multicloud | Yes |
| On-premises data center (colocation) or office | Yes |
| On-premises geographically close to CSPs | N/A |
| Diverse regions | Yes |
**Prerequisites**
* Customer (on-premises) network equipment supports LX optical 1 Gbps, LR optical 10 Gbps, or LR4 100 Gbps ports
* Customer (on-premises) network equipment supports BGP (for better path selection, not mandatory)
| Megaport Technology | Required | How many? |
| - | - | - |
| Port | Yes | 2 |
| Megaport Cloud Router (MCR) | Yes | 2 |
| Megaport Virtual Edge (MVE) | No | |
| Virtual Cross Connect (VXC) | Yes | 10 (2 for each CSP + 2 optional) |
Hybrid cloud-to-cloud, additional redundancy (multiple locations or regions).
Includes dual MCRs as hubs that connect DCs with Ports in different diversity zones to CSPs in a HA configuration.
| Property | Value |
| - | - |
| HA design | Yes |
| Multicloud | Yes |
| On-premises data center (colocation) or office | Yes - 2 DCs |
| On-premises geographically close to CSPs | N/A |
| Diverse regions | Yes |
**Prerequisites**
* Customer (on-premises) network equipment supports LX optical 1 Gbps, LR optical 10 Gbps, or LR4 100 Gbps ports
* Customer (on-premises) network equipment supports BGP (for better path selection, not mandatory)
| Megaport Technology | Required | How many? |
| - | - | - |
| Port | Yes | 4 |
| Megaport Cloud Router (MCR) | Yes | 2 |
| Megaport Virtual Edge (MVE) | No | |
| Virtual Cross Connect (VXC) | Yes | 12 (2 for each CSP) |
Branch-to-multicloud, not connected to data center, non-redundant.
Includes a single MVE connecting CSPs and branches.
| Property | Value |
| - | - |
| HA design | No |
| Multicloud | Yes |
| On-premises data center (colocation) or office | No |
| On-premises geographically close to CSPs | N/A |
| Diverse regions | Yes |
**Prerequisites**
* None required
| Megaport Technology | Required | How many? |
| - | - | - |
| Port | No | |
| Megaport Cloud Router (MCR) | No | |
| Megaport Virtual Edge (MVE) | Yes | 1 |
| Virtual Cross Connect (VXC) | Yes | 4 (1 for each CSP) |
Branch-to-multicloud, not connected to data center, redundant.
Includes dual MVEs connecting CSPs and branches in a HA configuration.
| Property | Value |
| - | - |
| HA design | Yes |
| Multicloud | Yes |
| On-premises data center (colocation) or office | No |
| On-premises geographically close to CSPs | N/A |
| Diverse regions | Yes |
**Prerequisites**
* None required
| Megaport Technology | Required | How many? |
| - | - | - |
| Port | No | |
| Megaport Cloud Router (MCR) | No | |
| Megaport Virtual Edge (MVE) | Yes | 2 |
| Virtual Cross Connect (VXC) | Yes | 8 (2 for each CSP) |
Branch-to-multicloud, connected to data center, non-redundant, dual underlay.
Includes a single MVE connecting CSPs, branches, and a data center via a Port.
| Property | Value |
| - | - |
| HA design | No |
| Multicloud | Yes |
| On-premises data center (colocation) or office | Yes - 1 DC |
| On-premises geographically close to CSPs | N/A |
| Diverse regions | Yes |
**Prerequisites**
* Customer (on-premises) network equipment supports LX optical 1 Gbps, LR optical 10 Gbps, or LR4 100 Gbps ports
* Customer (on-premises) network equipment supports BGP (for better path selection, not mandatory)
| Megaport Technology | Required | How many? |
| - | - | - |
| Port | Yes | 1 |
| Megaport Cloud Router (MCR) | No | |
| Megaport Virtual Edge (MVE) | Yes | 1 |
| Virtual Cross Connect (VXC) | Yes | 5 (Including 1 for each CSP) |
Branch-to-multicloud, connected to data center, redundant, dual underlay.
Includes dual MVEs connecting CSPs, branches, and data centers via Ports in a HA configuration.
| Property | Value |
| - | - |
| HA design | Yes |
| Multicloud | Yes |
| On-premises data center (colocation) or office | Yes - 2 DCs |
| On-premises geographically close to CSPs | N/A |
| Diverse regions | Yes |
**Prerequisites**
* Customer (on-premises) network equipment supports LX optical 1 Gbps, LR optical 10 Gbps, or LR4 100 Gbps ports
* Customer (on-premises) network equipment supports BGP (for better path selection, not mandatory)
| Megaport Technology | Required | How many? |
| - | - | - |
| Port | Yes | 2 |
| Megaport Cloud Router (MCR) | No | |
| Megaport Virtual Edge (MVE) | Yes | 2 |
| Virtual Cross Connect (VXC) | Yes | 10 (2 for each CSP + 2 optional) |
# Megaport On-ramp as a Service
Source: https://docs.megaport.com/deployment/onramp-as-a-service/index
This help topic describes what Megaport On-ramp as a Service is and provides detailed information on how to order it.
Megaport On-ramp as a Service (OaaS) is purpose-built for service providers to deliver private, dedicated connectivity to their end customers, helping them meet stringent security and compliance requirements.
With Megaport OaaS, the entire process is fully automated. A virtual LAN () is created automatically, IP addresses are assigned, Border Gateway Protocol () peering details are generated, and traffic is secured end-to-end. Megaport OaaS eliminates the manual back-and-forth of service key exchanges and removes the need for additional development effort from service providers.
By bypassing the risks of the public internet, Megaport OaaS provides a more secure, compliant, and reliable alternative for accessing mission-critical Software as a Service () applications, transporting sensitive data, and connecting to Security Service Edge (SSE) solutions, without the delays or complexity of manual provisioning.
## Who is it for?
Megaport OaaS is suitable for a wide range of service providers, including SSE and Secure Access Service Edge () providers, storage providers, and any SaaS application providers delivering services to end customers.
It is also well-suited for telco providers that need to deliver SSE, SASE, storage, and other SaaS services to their customers.
The following network diagram shows how service providers integrate their services into the Megaport network fabric using Megaport OaaS.
## Key benefits of Megaport OaaS
Megaport OaaS provides a platform for service providers to offer automated, secure, and private connectivity to cloud environments.
Traditional connectivity methods often depend on expensive, fixed-capacity leased lines or expose traffic to the public internet, lacking the sophisticated automation found in hyperscaler private on-ramps. As a result, service providers’ customers are frequently pushed into manual, non-standardized connection processes.
Megaport OaaS addresses this challenge by enabling service providers to deliver hyperscaler-level on-ramp automation without requiring internal development resources. The key benefits are summarized below.
* **Private on-ramp** -- Provide private, direct connectivity to cloud environments. Eliminate the need for service providers to build and maintain their own on-ramp infrastructure or dedicate resources to connection automation.
* **Automated provisioning** -- Facilitate the rapid, automated configuration of network elements. Automatically generate VLAN, IP address assignments, and Border BGP peering details within minutes, resulting in the delays and complexity of manual coordination or service key exchange processes.
* **Secure transport** -- Offer a secure, dedicated path for data transport that bypasses the public internet. Enable secure transport without requiring the engineering of Virtual Private Network ()/() tunnels or the capital investment in dedicated private circuits.
* **Global reach** – Extend network connectivity using the existing Megaport infrastructure. Allow service providers to establish connectivity in geographical regions where they lack a physical network footprint, providing a stable alternative to the public internet for global interconnection.
## Ordering Megaport OaaS
Below is a step-by-step workflow that describes how to order a Megaport OaaS.
1. Contact your Megaport Account Manager or Solution Architect to discuss your requirements. We will use those requirements to design a network solution that meets your needs.
2. After you and Megaport agree on the proposed solution, your Megaport Account Manager will provide a Manual Service Order (MSO) form for your review and acceptance of pricing, terms, and conditions.
3. After you sign the MSO, Megaport will place the order and send the connectivity details to the service provider.
## Helpful references
* [Introducing Megaport](/overview)
* [Megaport Cloud Connectivity Overview](/cloud/megaport)
* [Megaport Marketplace Overview](/marketplace/overview)
* [Understanding Locations](/enabled-locations)
# Modernizing Your MPLS Network with Megaport Solutions
Source: https://docs.megaport.com/deployment/wan-replacement/index
This help topic describes how to modernize your traditional WAN with Megaport solutions.
Megaport enables a model for enterprise WAN connectivity that can replace services or reduce dependency on traditional providers. This topic describes options and considerations for modernizing your MPLS network.
Although Megaport currently cannot replace all components of an MPLS network, Megaport can replace key parts and provide significant benefits with cost, flexibility, speed of deployment, and scalability. With the right plan, you can design a Megaport/MPLS hybrid solution and then gradually phase out more MPLS components as the Megaport product suite evolves.
## Megaport advantages
The advantages of using Megaport's software-defined network (SDN) instead of MPLS include:
* **Flexibility for optimal pricing** -- Megaport provides an extremely cost-effective solution compared to MPLS in most markets. At any time, you can add or delete services or adjust bandwidth for connections. This ensures you always have the right price, you can easily scale as your business grows, and you only pay for what you need. To take full advantage of the flexibility, you can implement tools to adjust connection speeds as required and get the full benefit of the elastic Megaport network.
* **Free of long-term contracts** -- Megaport connections do not require long-term contracts, so you don’t have to predict traffic profiles for years at a time or get locked into a commitment for a specific topology.
* **Speed of deployment** -- You can add and delete connections within minutes through the Megaport Portal or API.
* **Consistent latency** -- Direct Layer 2 connections provide consistent latency and, in many cases, lower latency between locations, improving overall performance and increasing throughput.
* **No risk** -- With no contracts and no long-term commitments to traffic profile estimates for the next several years, using Megaport lets you manage your network carefully and make adjustments as your business needs change. You are never locked into a long-term commitment or price.
* **Dependability** -- Each Megaport data center has two or more diverse fiber connections into the Megaport global network, and each VXC is protected by all available fiber paths at the data center. Each connection automatically fails over to the next.
## Considerations
There are some considerations when thinking about Megaport solutions with an MPLS network:
* **Dealing with multiple providers and data center operators** -- With MPLS, you often commit to a contract with a single network provider. But the all-or-nothing MPLS relationship has real limitations that restrict you to a single network with a fixed, hardware-based configuration, reducing your growth options. While switching providers is not the easiest task, and adding Megaport introduces a new customer-provider relationship, you gain the advantage of Megaport’s Cloud Service Provider (CSP) agnostic approach to large-scale interconnection using dynamic connections.
* **Challenging to connect Megaport to MPLS circuits** -- It can be difficult to terminate a connection from a Port to a carrier MPLS interface. MPLS providers have control of the router and are often resistant to adding Megaport details to the router and allowing access for Megaport traffic. Whether or not your MPLS provider will cooperate with Megaport needs to be a consideration in the design.
* **Procuring the last mile** -- One of the biggest challenges in moving from MPLS to SDN is procuring, managing, and paying for the “last mile” connectivity. For more information, see [Next steps with SD-WAN](/deployment/wan-replacement#nextsteps).
## Current solutions
Megaport supports hybrid networks for modular network design where you can easily deploy and manage Ports, Megaport Cloud Routers (MCR), and Virtual Cross Connects (VXCs) and integrate them with existing network infrastructure.
### Connectivity between data centers
With Megaport, you can easily connect multiple sites and data centers and replace this part of your MPLS WAN. Megaport provides extensive connectivity between data centers around the globe and can reduce costs and improve performance for connections between data centers. This connectivity model builds on SDN principles and supports a more agile, on-demand approach instead of long-term, fixed-price contracts.
By using Ports (physical ports in Megaport-enabled data centers) and VXCs, you can replace traditional point-to-point links and easily establish a secure, reliable connection between any of the global [Megaport enabled locations](https://megaport.com/megaport-enabled-locations).
You can connect two or twenty data centers, set up a hub-and-spoke model, or create a fully meshed network.
For more information about Ports and VXCs:
* [Creating a Port](/connections/creating-port)
* [Creating a VXC](/connections/overview)
### Megaport Cloud Router (MCR)
MCR is a managed virtual router service that establishes Layer 3 connectivity on the worldwide Megaport software-defined network (SDN).
Incorporating MCR into your network design lets you manage routing decisions. MCRs don’t require a physical cross connect, letting you configure them close to your data sources to minimize latency and interconnect to Ports or CSPs using VXCs.
MCR can be inserted as a hub to route traffic to multiple ports throughout the network, which optimizes traffic and reduces latency and bandwidth costs.
#### MCRs with Cloud Service Providers
MCR provides a smart way to integrate your cloud strategy with your existing MPLS network. As a virtual routing service, MCR can solve the complexities and costs that come with connecting your MPLS network to CSPs.
You can add MCR as a node, or multiple nodes, on your existing MPLS network. MCR sits on top of the Megaport SDN at Layer 3 to provide a point-to-multipoint connection model and serve as a hub between CSPs.
Your MPLS provider must support a single peer to MCR from their Provider Edge (PE) device.
For more information about MCR cloud configurations:
* [Connecting an MPLS Network to the Public Cloud](https://megaport.com/blog/connecting-an-mpls-network-to-the-public-cloud)
#### MCRs as regional hubs
You can use MCR as the primary connection point for regional branch offices, CSPs, and data centers. In this hub-and-spoke design, MCR provides the hub and connects to spokes that are organized into regions based on proximity.
The MCR hub connects your regional branches, CSPs, and data centers and VXCs connect the regional MCRs.
For more information about MCR:
* [MCR Overview](/mcr)
## Next steps with SD-WAN
The Megaport Virtual Edge (MVE) product supports replacing more MPLS functionality using Megaport to manage the connection between the customer branch and the data center. Customers no longer need to be in a multi-tenant data center to take advantage of Megaport’s interconnection capabilities. Megaport Internet gateway functionality enables internet-connected locations to access the Megaport SDN.
For more information about MVE:
* [MVE Overview](/mve)
# Understanding Locations
Source: https://docs.megaport.com/enabled-locations/index
This help topic describes how to use the Megaport Enabled Locations page.
Megaport’s global network infrastructure consists of carrier grade switching equipment hosted in data centers around the world. On the [Megaport Enabled Locations page](https://www.megaport.com/megaport-enabled-locations/), you can search for nearby Megaport Points of Presence (PoPs) where you can connect to the Megaport network.
## Using the Enabled Locations map
There are two types of locations where you can connect to Megaport’s network:
* **Installed** -- These locations contain Megaport networking hardware, and you can connect to any of them through the Megaport Portal.
* **Extended** -- These locations share the same campus or metro area as an Installed Location. Megaport hardware is not located within the Extended Location facility, but you can access it through a private intra-campus or intra-metro cross connect. You can order this cross connect to the Megaport Installed location from your Data Center Operator at the Extended Location.
Enabled Locations encompass both Installed and Extended Locations.
**To find a PoP on the Enabled Locations map**
1. On the [Megaport Enabled Locations page](https://www.megaport.com/megaport-enabled-locations/), click Find My Location.
You can also click Locations and filter by provider, geographical location, or Megaport service availability. You can search for locations where you can connect to a Megaport Virtual Edge (MVE), a 100 G Port, or a Megaport Cloud Router (MCR).
2. Enter a street address to drop a pin on the map.\
The map zooms in on your specified address to include the pin and at least one Extended Location, if available.
A red pin represents an Installed Location, or Megaport PoP. A purple pin represents an Extended Location.
When you zoom out, a black marker indicates a geographical area with a cluster of locations. The number on the black marker indicates how many red pins are located in the cluster. Click the black marker to zoom in on the locations.
To connect to an extended location, click the purple pin and then click **Enquire about this location**. After you complete an inquiry form, a Megaport sales representative will reach out to you with information on setting up the physical cross connect.
## Viewing latency times
The data used to calculate Megaport's network latency is collected from monitoring equipment in Megaport-enabled data centers worldwide, in 5-minute intervals. Monthly latency and packet delivery statistics are calculated by averaging all samples from that month.
There are two ways to view latency times for a PoP:
* On the [Megaport Enabled Locations page](https://www.megaport.com/megaport-enabled-locations/), click **View latency** on any Megaport PoP.
* On the [Megaport Network Latency page](https://www.megaport.com/network-latency/), use location filters to search for a site.
## Using location IDs for reliable configurations
In the Megaport API, data center location names and site codes might occasionally change as facilities are rebranded, merged, or updated. However, the location ID remains constant and is the most reliable way to identify a data center.
If your Terraform configurations or API scripts rely on a location name or code that changes, those integrations will fail to execute until the references are manually updated. This can lead to automation failures, deployment delays, or service disruptions.
To ensure consistency and reliability, we strongly recommend using the location ID instead of the name or site code when integrating with the Megaport API or defining resources in Terraform.
For the most up-to-date list of Megaport data center locations, see [Megaport Location IDs](/enabled-locations/location-ids).
Location IDs are also available through the [GET /v3/locations Megaport API](https://dev.megaport.com/#7c8e0706-e138-4d9a-bc4f-0419d97604cf).
## Helpful references
* [Creating a Megaport Terraform Provider Configuration File](/terraform/megaport-terraform-configuration)
* [Megaport API Overview](/api)
# Megaport Location IDs
Source: https://docs.megaport.com/enabled-locations/location-ids
This help topic lists Megaport location IDs and their details.
The table on this page is rendered dynamically using data from the Megaport Locations API. To retrieve the same data programmatically, send a `GET` request to `https://api.megaport.com/v3/locations` -- no authentication required. The response contains a `data` array where each element is a location object. The table surfaces five fields per location: `id` (integer, used in API requests), `name` (display name), `city` (from `address.city`), `metro` (metropolitan area), and `country` (from `address.country`).
# Quick Start Guide
Source: https://docs.megaport.com/getting-started/index
This help topic provides an overview of common tasks with links to related topics.
This topic describes basic workflows for you to get set up and create some of the most common configurations.
## Get your account set up
Before you can create anything with Megaport, you need to create an account and set up some administrative details. These are the essential steps.
* [Create an account](/setting-up/registering)
* [Invite users to your account](/setting-up/inviting-users)
* [Provide support contact details](/setting-up/tech-support-details)
* [Specify your billing market](/setting-up/finance-basics)
* [Set up a finance user](/setting-up/finance-basics)
* [Modify your company profile (optional)](/setting-up/company-profile)
We highly recommend that you also set up security and access policies for all users accessing the Megaport Portal. For more information, see [Multi-Factor Authentication](/setting-up/enforcing-mfa) and [Setting up Single Sign-On](/setting-up/enforcing-sso).
## Provision services
To set up network services with Megaport, you need either a Port, an MCR, or an MVE.
A Port lets you connect your equipment to Megaport through 1 G or 10 G fiber interfaces (100 G is available in some locations). With a configured Port, you can establish connections to other Ports, CSPs, or IXs.
* [Create a Port](/connections/creating-port)
MCR is a Layer 3 capable virtual router hosted by Megaport in cloud hotspot locations worldwide. An MCR does not require a Port, but you can connect to one as required.
* [Create an MCR](/mcr/creating-mcr)
MVE is an on-demand Network Function Virtualization (NFV) service that supports branch-to-cloud connectivity on SD-WAN platforms. An MVE works as a gateway to connect enterprise SD-WAN enabled sites to the Megaport ecosystem, providing cloud-neutral, direct, and secure access to its extensive platform of cloud providers and other services. An MVE does not require a Port, but you can connect to one as required.
* [Create an MVE](/mve)
NAT Gateway is a Network Address Translation (NAT) service that allows devices in your network to access the internet without requiring each device to have a public IP address. NAT Gateways connect networks, block unwanted traffic, and provide internet access for devices within your network. A NAT Gateway can connect to Ports, MCRs, MVEs, Megaport Internet, and CSPs. A NAT Gateway does not require a Port, but you can connect to one as required.
* [Create a NAT Gateway](/nat/creating-nat-gateway)
Through the Portal, you can set up your complete end-to-end configuration and add those elements to your shopping cart, then proceed to the ordering process. For more information about using the Portal to set up your services, see [Understanding the Services Page](/portal-admin/services-page).
### Port to Port connection
* [Identify locations](/enabled-locations)
* [Create a Port](/connections/creating-port)
* Create a second Port
* [Create a VXC to connect the Ports](/connections/private-vxc)
### Port to Cloud Service Provider connection
* [Identify locations](/enabled-locations)
* [Create a Port](/connections/creating-port)
* [Identify CSP](/cloud/megaport)
* Create a VXC between the Port and the CSP - see the instructions for your CSP in the [Cloud Connectivity for Ports](/cloud/megaport) navigation
* Some CSPs require additional configuration (BGP, for example)
### Port to IX connection
* [Create a Port](/connections/creating-port)
* [Add an IX connection](/ix)
### Port to Megaport Marketplace connection
* [Create a Port](/connections/creating-port)
* [Add a Megaport Marketplace connection](/marketplace/overview)
### MCR to CSP connection
* [Identify locations](/enabled-locations)
* [Create an MCR](/mcr/creating-mcr)
* Create a VXC between the MCR and the CSP - see the instructions for your CSP in the [Cloud Connectivity for MCR](/cloud/mcr) navigation
* Some CSPs require additional configuration
### MVE to CSP connection
* [Identify locations](/enabled-locations)
* [Create an MVE](/mve)
* Create a VXC between the MVE and the CSP - see the instructions for your CSP in the [Cloud Connectivity for MVE](/cloud/mve) navigation
### NAT Gateway to CSP connection
* [Identify locations](/enabled-locations)
* [Create a NAT Gateway](/nat/creating-nat-gateway)
* [Create a NAT Gateway VXC](/nat/nat-gateway-vxc)
# Video Library
Source: https://docs.megaport.com/getting-started/videos
This help topic collects all Megaport tutorial and how-to videos in one place.
This help topic collects all Megaport tutorial and how-to videos in one place. For more videos, visit the [Megaport YouTube channel](https://www.youtube.com/@megaportnetworks).
## Encryption
## Cloud Connectivity
## Megaport Cloud Router (MCR)
## Monitoring
## Portal Admin
## Terraform
## Troubleshooting
# Launchpad
Source: https://docs.megaport.com/index
This site provides detailed help and instruction on how to use, configure, and troubleshoot the Megaport network and services.
# Megaport Limits and Quotas
Source: https://docs.megaport.com/limits-quotas/index
This help topic details the limits and quotas of Megaport services and platform.
This topic summarizes the limits and quotas for the Megaport Portal and Megaport services.
## Megaport Portal
| **Name** | **Limit** | **Adjustable** | **Description** |
| - | - | - | - |
| Activity Log Retention | 6 months | No | The maximum number of days Megaport retains activity logs. To retrieve logs older than 6 months, contact [ Megaport Support](/support/contact). |
| API Key Token Expiry | The minimum is 5 minutes and the maximum is 24 hours. | No | The expiry period of access tokens ranges from a minimum of 5 minutes to a maximum of 24 hours. |
| API Key Requests | 100 API keys per company | Yes | The maximum number of API keys per company is 100. To change it, contact [ Megaport Support](/support/contact). |
| API Rate Limits | 500 requests in a rolling 5 minute period per IP address | No | The maximum number of API calls you can make every 5 minutes. |
| Resource Limits per New Customer | 5 × Port 10 × VXC 5 × MCR 5 × MVE 5 × NAT Gateway 5 × IX | Yes | The default limits apply per product and per new customer. Contact [Megaport Support](/support/contact) or your Megaport Account Team with any questions. |
| Session Token Expiry | 8 hours | No | The duration of a session token within the Portal is 8 hours. For custom integrations, you can use API keys to generate tokens that last anywhere from 5 minutes to 24 hours. |
| Service Log Displayed | 100 | No | The maximum number of most recent service log events displayed in the Portal. |
| Users | 100 | No | The maximum number of users you can add per account. |
## Port
| **Name** | **Limit** | **Adjustable** | **Description** |
| - | - | - | - |
| Diversity Zones | 2 zones | No | The number of zones available for a Port order at a location with red and blue diversity. |
| LAG | Up to 8 Ports | No | The maximum number of physical Ports you can combine into a single LAG. |
| Number of VXCs per Port | Up to 100 VXCs | No | The maximum number of VXCs per Port. |
## Virtual Cross Connect (VXC)
| **Name** | **Limit** | **Adjustable** | **Description** |
| - | - | - | - |
| Rate Limits -- Port and MCR | Cannot exceed the speed of the lowest speed Port or MCR | No | This limit also applies to LAGs. |
| Rate Limits -- MVE | Determined by the lower of the A-End or B-End rate limits | No | You can adjust the speed as required after you create the VXC, in increments of 1 Mbps. |
## Megaport Internet
| **Name** | **Limit** | **Adjustable** | **Description** |
| - | - | - | - |
| Public IPv4 Addresses | Default /31 | No | The default public IPv4 address prefix size you can use for point-to-point connections, such as those that establish BGP peering on an MCR. |
| Public IPv6 Addresses | Default /64 | No | The default public IPv6 address prefix size you can use for point-to-point connections, such as those that establish BGP peering on an MVE. |
## IP Address
| **Name** | **Limit** | **Adjustable** | **Description** |
| - | - | - | - |
| Resource Limit per Company | Customizable | Yes | The maximum number of IP Address blocks you can order. To adjust the limit, contact Megaport Support or your Customer Success Manager. |
## Megaport Cloud Router (MCR)
| **Name** | **Limit** | **Adjustable** | **Description** |
| - | - | - | - |
| Maximum Number of VXCs per MCR | 25 | No | The limit applies to all types of VXCs connected to an MCR. |
| Maximum Packet Size | 9,074 bytes | No | The value of an MCR interface. |
| Maximum Number of Routes | 30,000 | Yes | The recommended maximum number of routes per MCR. This limit applies to the total number of static and dynamic routes that an MCR can manage. Megaport may take action if any issues with neighboring MCRs are caused by routes exceeding 30,000. |
| Maximum Number of Interfaces per VXC | 5 | No | The maximum number of Interfaces per VXC. This refers to the number of Layer 3 interfaces (with IP addresses and BGP sessions or static routes) that you can configure on a single VXC connected to an MCR. |
| IP Addresses per Interface (IPv4 or IPv6) | 5 | No | The maximum number of IP addresses or subnets that can be assigned to a single network interface on an MCR. |
| Maximum Number of Static Routes per Interface | 100 | No | The maximum number of static routes per interface on an MCR. |
| Maximum Number of Static Routes per MCR | 500 | No | The maximum number of static routes per MCR. |
| Maximum Length of a Static Route Description | 100 characters | No | The maximum number of characters for a static route description. |
| Maximum IPv4 NAT Source IP Addresses | 1 | No | The maximum number of source IP addresses that can be used for NAT on an MCR. |
| Maximum Simultaneous Connections with NAT Enabled | 250,000 | No | The maximum number of concurrent, active network sessions that an MCR can manage when NAT is enabled. |
| Maximum Rate of New Connections with NAT Enabled | 1,000 per second | No | The maximum number of new network sessions per second that an MCR can establish and track when NAT is enabled. |
| Maximum Number of BGP Connections per MCR | 50 | No | The maximum number of BGP connections across all VXCs and interfaces on an MCR. |
| Maximum Length of a BGP Connection Description | 100 characters | No | The maximum length of the optional Description field for a BGP connection on an MCR. |
| Maximum Length of a BGP Password | 25 characters | No | The maximum length of the BGP Password field, which is used for MD5 authentication. |
| Maximum Number of BGP Peer Filters per BGP Connection | 25 | No | The maximum number of routing policies you can apply to a single BGP peering session. |
| Maximum BGP Connection Multi-exit Discriminator | 4,294,967,295 | No | The maximum number of BGP Connection Multi-exit Discriminator (MED) on an MCR. You can set the MED value to any number from 0 up to the maximum. |
| Maximum Number of IPsec tunnels | 30 | No | The maximum number of IPsec tunnels across all the VXCs connected to a single MCR. IPsec tunnels are available in packs of 10. To change it, contact [ Megaport Support](/support/contact). |
| Maximum Number of AS Path Prepends | 10 | No | The maximum number of times you can intentionally repeat your own ASN in a BGP route advertisement. |
| Maximum Number of Prefix Lists per MCR | 50 | No | The maximum number of distinct prefix filter lists for a single MCR instance. |
| Maximum Number of Entries per Prefix List | 200 | No | The maximum number of entries (prefixes or prefix ranges) each prefix list on an MCR can have. |
| Length of a Prefix List Description | 100 characters | No | The maximum length of the Prefix List Description field. |
| API Maximum Number of Concurrent MCR Looking Glass Requests | 2 | No | The maximum number of concurrent MCR Looking Glass API requests. |
| API Maximum Number of MCR Looking Glass Requests per Day | 200 | No | The maximum daily rate limit of MCR Looking Glass API requests. |
| Packet Filter -- Lists | 20 | No | The maximum number of unique packet filter lists a single MCR instance can have. |
| Packet Filter -- Entries per List | 50 | No | The maximum number of rules or entries each packet filter list can contain. |
| Packet Filter -- Description | 100 characters | No | The maximum number of characters for the optional Description field. |
| Maximum Ping Count | 60 | No | The maximum number of echo request packets sent to test a network connection. The default is set 3. |
| Maximum Ping Byte Size | 9186 | No | The maximum size of echo request packets sent in a ping, excluding network headers. The default is set 56. |
| Maximum Ping and Traceroute Execution Time | 90 seconds (then times out) | No | The maximum time allowed for a ping or traceroute command to complete its execution. |
| Ping and Traceroute Output Availability Window | 10 minutes after completion | No | The time frame during which the results of a ping or traceroute remain accessible. |
| Ping and Traceroute Concurrency per MCR | 1 request at a time | No | The maximum number of ping and traceroute tests that can run simultaneously per MCR. |
| Ping and Traceroute Rate Limit | 200 requests in 24hrs | No | The maximum number of ping and traceroute requests permitted within a specific timeframe. After 200, then throttled to 1 per 15 minutes per service. |
## Megaport Virtual Edge (MVE)
| **Name** | **Limit** | **Adjustable** | **Description** |
| - | - | - | - |
| Minimum Number of vNICs | 1 | No | The minimum number of vNICs on an MVE instance. |
| Maximum Number of vNICs | 5 | No | The maximum number of vNICs on an MVE instance. |
| Number of VXCs per MVE | 2 vCPU = 25 4 vCPU = 25 8 vCPU = 50 16 vCPU = 75 32 vCPU = 75 | No | The maximum number of VXCs you can connect per MVE is related to the MVE size. |
## Megaport NAT Gateway (NAT Gateway)
| **Name** | **Limit** | **Adjustable** | **Description** |
| - | - | - | - |
| IP Addresses per Interface (IPv4 or IPv6) | 5 | No | The maximum number of IP addresses or subnets that can be assigned to a single network interface on a NAT Gateway. |
| Length of a Prefix List Description | 100 characters | No | The maximum length of the Prefix List Description field. |
| Maximum Address Pools or NAT Rules | 16 pools / 16 rules | No | The maximum number of NAT rules that can be configured on a Megaport NAT Gateway. This number also applies to the number of address pools configured on the same device. |
| Maximum BGP Connection Multi-exit Discriminator | 4,294,967,295 | No | The maximum value of the BGP Connection Multi-exit Discriminator (MED) on a NAT Gateway. You can set the MED value to any number from 0 up to the maximum. |
| Maximum eBGP Multihop Count | 255 | No | The maximum hops allowed to an eBGP neighbor. |
| Maximum Length of a BGP Connection Description | 100 characters | No | The maximum length of the optional Description field for a BGP connection on a NAT Gateway. |
| Maximum Length of a BGP Password | 25 characters | No | The maximum length of the BGP Password field, which is used for MD5 authentication. The following characters are allowed: `a-z A-Z 0-9 - ! @ # ? . $ % ^ & * + = -` |
| Maximum Length of a Static Route Description | 100 characters | No | The maximum number of characters for a static route description. |
| Maximum Number of AS Path Prepends | 10 | No | The maximum number of times you can intentionally repeat your own ASN in a BGP route advertisement. |
| Maximum Number of BGP Connections per NAT Gateway | 50 | No | The maximum number of BGP connections across all VXCs and interfaces on a NAT Gateway. |
| Maximum Number of BGP Peer Filters per BGP Connection | 25 | No | The maximum number of routing policies you can apply to a single BGP peering session. |
| Maximum Number of Entries per Prefix List | 200 | No | The maximum number of entries (prefixes or prefix ranges) each prefix list on a NAT Gateway can have. |
| Maximum Number of Interfaces per VXC | 5 | No | The maximum number of interfaces per VXC. This refers to the number of Layer 3 interfaces (with IP addresses and BGP sessions or static routes) that you can configure on a single VXC connected to a NAT Gateway. |
| Maximum Number of Prefix Lists per NAT Gateway | 50 | No | The maximum number of distinct prefix filter lists for a NAT Gateway. |
| Maximum Number of Routes | 10,000 | Yes | The recommended maximum number of routes per NAT Gateway. This limit applies to the total number of static and dynamic routes that a NAT Gateway can manage. Megaport may take action if any issues with neighboring NAT Gateways are caused by routes exceeding 10,000. |
| Maximum Number of Static Routes per Interface | 100 | No | The maximum number of static routes per interface on a NAT Gateway. |
| Maximum Number of Static Routes per NAT Gateway | 500 | No | The maximum number of static routes per NAT Gateway. |
| Maximum Number of VXCs per NAT Gateway | 25 | No | The limit applies to all types of VXCs connected to a NAT Gateway. |
| Maximum Packet Size | 9074 bytes | No | The Maximum Transmission Unit (MTU) value of a NAT Gateway interface. |
| Maximum Port Translation IPs | 1024 | No | The total number of IP addresses in NAT Gateway Address pools configured on the Megaport NAT Gateway. |
| Maximum Value of a BGP Prefix Limit | 100,000,000 | No | The maximum value of a BGP prefix limit on a NAT Gateway. |
| Packet Filter – Entries per List | 50 | No | The maximum number of rules or entries each packet filter list can contain. You can specify source and destination ports as a single port value, or a range of ports. |
| Packet Filter – Description | 100 characters | No | The maximum number of characters for the optional Description field. |
| Packet Filter – Lists | 20 | No | The maximum number of unique packet filter lists a single NAT Gateway instance can have. |
| Maximum Ping Count | 60 | No | The maximum number of echo request packets sent to test a network connection. The default is set 3. |
| Maximum Ping Byte Size | 9186 | No | The maximum size of echo request packets sent in a ping, excluding network headers. The default is set 56. |
| Maximum Ping and Traceroute Execution Time | 90 seconds (then times out) | No | The maximum time allowed for a ping or traceroute command to complete its execution. |
| Ping and Traceroute Output Availability Window | 10 minutes after completion | No | The time frame during which the results of a ping or traceroute remain accessible. |
| Ping and Traceroute Concurrency per NAT Gateway | 1 request at a time | No | The maximum number of ping and traceroute tests that can run simultaneously per NAT Gateway. |
| Ping and Traceroute Rate Limit | 200 requests in 24hrs | No | The maximum number of ping and traceroute requests permitted within a specific timeframe. After 200, then throttled to 1 per 15 minutes per service. |
# Creating a Connection using a Service Key
Source: https://docs.megaport.com/marketplace/create-connection-service-key
This help topic describes how to create a service key to share your connection
A service key is a code that is given by one Megaport account holder to another to connect two separate businesses together. Customers who have separate Megaport accounts can connect their Ports, MCRs, MVEs, and NAT Gateways to each other across the Megaport network, enabling business-to-business VXCs.
This topic will help you if you have been given a service key to set up a connection to another company's service.
For more information about service keys, see [Setting up Service Keys](/marketplace/service-keys).
**Prerequisites**
Before you create a , ensure that you have:
* Access to the Megaport Portal.
* A Port, MCR, MVE, or NAT Gateway on the Megaport network.
**To create a connection with a service key**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.
In this example, we are using a Port, but you can also use an MCR, MVE, or NAT Gateway.
2. Click **+Connection** then click **Enter Service Key**.
3. Enter the service key in the **Megaport Service Key ID** field.\
Megaport validates the key and displays basic information about the key.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps, up to the maximum limit defined by the key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- You might be asked to specify an A-End vNIC. Select an available vNIC from the drop-down list.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
The **B-End VLAN** for the provider-side termination will be automatically populated based on the service key.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.\
A summary page appears that includes the monthly cost. Click **Back** to make changes or click **Add VXC** to move this configuration to your cart.
7. After ordering the key, a notification is sent to the company that you are connecting to, and the connection is completed automatically.
The service key VXC will appear in the Megaport Portal for both companies as shown below.
# Setting up Service Keys
Source: https://docs.megaport.com/marketplace/service-keys
This help topic describes how to create service keys to connect ports in separate Megaport accounts.
A service key is a code that is given by one Megaport account holder to another to connect two separate businesses together. Customers who have separate Megaport accounts can connect their Ports, MCRs, MVEs, and NAT Gateways to each other across the Megaport network, enabling business-to-business VXCs.
For example, suppose West Company wants to connect with East Company. East Company wants West Company to connect to a particular Port, MCR, MVE, or NAT Gateway that they have already deployed on the Megaport network, and they want the connection at a specific rate limit. East Company can create a service key on their Port, MCR, MVE, or NAT Gateway and share it with West Company.
You can create a service key on the Megaport Portal, or by using an API. For more information about using an API, see [Creating a Service Key with the API](/api/api-create-servicekey).
## Prerequisites
Before you create a , ensure that you have:
* Access to the Megaport Portal.
* A Port, MCR, MVE, or NAT Gateway on the Megaport network.
## Service key types
You can create either a single-use or a multi-use service key. With a multi-use key, the customer that you share the key with can request multiple connections using that key.\
With a single-use service key, the customer you share the key with can request only one connection. You can create a single-use service key with an untagged VLAN, which limits the Port to a single virtual service, or you can specify a VLAN for that connection.
For more information about the differences between single-use and multi-use service keys, see [Managing VLAN IDs](/deployment/csp-integration#managing-vlans).
## How service keys work
A service key is a 36-character UUID. It is essentially an address with some configuration. The company consuming the service key only needs to have the service key to create the connection. They do not know what kind of service they are connecting to because the service key provides all the information they need.
**To create a connection using a service key**
1. East Company creates a service key on the service they want to grant access to. In this case, they want to share a Port.
2. East Company shares the service key with West Company, using the method of their choice such as email or messaging.
3. West Company creates a connection to East Company's Port using the service key.
4. East Company receives a notification that West Company has requested access to the Port, and access is granted automatically.
5. When the request is granted, a VXC is provisioned between East Company's Port and West Company's Port. The connection is a partnership. If one company wants to change something about the configuration, the other company is notified.
### Structure and rights
**Structure**
When East Company creates the service key, the configuration they provide is the **B-End** of the VXC.
When West Company creates the connection, they define the **A-End** of the VXC.
**Rights**
The service key connection creates a partnership. The main point to note about the partnership is that **the consumer of the service key pays for the connection**. That is West Company in this instance. The consumer of the service key can also delete the service.
Each partner has certain rights to change the different parts of the connection. This table shows the viewable and editable fields for each partner.
| Owner | Port, MCR, and NAT Gateway | MVE |
| - | - | - |
| B-End only (East Company) Creator of service key |
Preferred B-End VLAN (If applicable)
All current B-End MCR or NAT Gateway fields for VXC
|
B-End vNIC
Preferred B-End VLAN (If applicable)
|
| A-End only (West Company) Consumer of service key |
Service Level Reference
Preferred A-End VLAN (If applicable)
All current A-End MCR or NAT Gateway fields for VXC
Rate limit
|
A-End vNIC (if applicable)
Preferred A-End VLAN (If applicable)
Rate limit
|
Each partner can call their connection a name relevant to them. They do not have to be the same.
### Changing connection details
If a partner changes a part of the configuration such as the VLAN, the other partner is notified and must agree to the changes before they are made.
For example, if West Company wants to change the VLAN the following process applies:
1. West Company updates the VLAN.
2. East Company receives an email informing them of the change.
3. East Company then checks their connection B-End details. There will be a box on the details window informing them of the change, with buttons that allow them to approve or deny the change.
**Updating the rate limit**
If the consumer of the service key wants to change the rate limit on the VXC, approval is not required if the rate limit is changed to below the maximum limit defined in the service key.
Only the owner of the VXC, the consumer of the service key, is allowed to change the rate limit. The creator of the service key is *not* allowed to change the rate limit.
**Connection details privacy**
Privacy is maintained between each end of the connection. Each end cannot see the other end's details.
## Creating a service key
You can create a service key for Ports, MCRs, MVEs, and NAT Gateways. They can be either a single-use or a multi-use service key. With a multi-use key, the customer that you share the key with can request multiple connections using that key.
Single-use service keys can be created untagged, or with a VLAN ID.
* You can create a single-use untagged service key only if no existing untagged connections are present on the relevant MVE vNIC or Port.
* You can only create a service key on a service after it has been provisioned. Service keys cannot be created on services that are still in design.
All service keys have an expiry date by default. While you can remove this expiry date, Megaport does not recommend it. If you do not set an expiry date, the key will remain active until you manually disable it. Megaport recommends setting an expiry date for better management, although it is not mandatory.
Once you create service keys, they cannot be removed.
**To create a service key**
1. In the Megaport Portal, go to the **Services** page and select the service you want to grant access to.
2. Click the Service Keys icon.
3. Click **Create Service Key**.
4. Enter a label (name) for the key.
5. Select **Single Use** or **Multi-Use**.
6. Enter a rate limit.
7. For single-use keys, you can specify specific information for each service type.
| Service Type | Information Required | Details |
| - | - | - |
| Port | VLAN | This is the VLAN ID for the B-End. You can set the VLAN to **Untagged**, or supply a VLAN ID. An Untagged VLAN limits the Port to one virtual service. If a VLAN ID is supplied, Megaport checks that the requested VLAN ID is available. If the VLAN ID is already in use, an error message tells you the VLAN is not available. When a customer uses this service key to create a connection, they can specify a VLAN ID for the A-End. |
| MVE | Preferred B-End VLAN | Same details as for Port. |
| MCR | B-End configuration | Click **B-End Configuration** to specify the MCR configuration details. For more information about the information required for the B-End configuration, see [Creating an MCR](/mcr/creating-mcr). |
| NAT Gateway | B-End configuration | Click **B-End Configuration** to specify the NAT Gateway configuration details. For more information about the information required for the B-End configuration, see [Creating a NAT Gateway](/nat/creating-nat-gateway). |
8. Specify how long the key will be valid.
9. Select **Active**.\
If you don't want the key to be available right away, do not select Active. You can edit this key later to change this setting.
Configuration details entered when the service key is created are stored and applied when a customer consumes the service key.
10. Click **Add** to save the key.
After you deploy a service key on a B-End, you cannot reuse the associated B-End VLAN ID if there is already a service key using that same VLAN ID on that Port.
## Viewing, copying, and editing a service key
When service keys are configured, they appear in the Portal. Click the Service Key icon for a Port to show the configured keys.
The Service Key icon will display only if the Port is available for new connections, the current user has ordering privileges, and it does not already have an untagged VXC attached.
Click the clipboard icon to copy the key, or click **Edit** to make changes.
**To deactivate a service key**
1. In the Megaport Portal, go to the **Services** page and select the service you want to use.
2. Click the Service Keys icon.
3. Click **Edit**.
4. Clear the **Active** check box.
5. Click **Update Service Key** to save the changes.
## Sharing the key
You can share the service key however you prefer, such as email or messaging.
The recipient of the service key cannot alter or modify the service key parameters.
## Creating a connection using a service key
For more information about how to set up a connection using a service key, see [Creating a Connection using a Service Key](/marketplace/create-connection-service-key).
# Configuring an MCR
Source: https://docs.megaport.com/mcr/configuring-mcr
This help topic describes how to edit and configure a Megaport Cloud Router (MCR) and Virtual Cross Connect (VXC).
This topic describes how to edit and configure a Megaport Cloud Router (MCR) and Virtual Cross Connect (VXC). Before you begin, you need to create an MCR and configure a VXC, as described in [Creating an MCR](/mcr/creating-mcr) and [Creating an MCR VXC](/mcr/mcr-vxc).
## Editing an MCR
For each MCR, you can edit any field on the MCR Configuration page, except the rate limit, which is fixed for the duration of the service. The Megaport Marketplace service availability must also be set in your Megaport Marketplace profile.
For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
You can edit the MCR ASN after deployment, but only when there are no VXCs attached. You will need to move or remove all VXCs before editing the ASN. For more information, see [Moving VXCs](/connections/move-vxc).
**To edit an MCR**
1. Log in to the Megaport Portal and choose **Services**.
2. Select the MCR you want to edit.
3. Edit any field on the MCR Configuration page as required, except for the MCR Rate Limit, Megaport Marketplace visibility, and MCR ASN (depending whether a VXC is attached).
* The **Initial BGP State** lets you 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 the Shut Down option if you are planning to add several 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 MCR Connection detail screen. For more information about overriding the BGP state for an individual connection, see [Shutting down a BGP connection](/mcr/configuring-mcr#bgpshut).
For more information, see [Creating an MCR](/mcr/creating-mcr).
4. Click **Save**.
## Editing a VXC
For each VXC connected to an MCR you can configure one or more interfaces, IP addresses, BGP connections, or static routes. You can also select a NAT source IPv4 address and specify the IP MTU value.
Depending on the VXC destination or CSP provider, the MCR connection settings might have been auto-configured during VXC creation. Follow the steps in this task to configure the connection settings as required.
If the VXC provisioning status is LIVE, CONFIGURED, or DEPLOYABLE, the connection configuration fields will be available when editing a VXC regardless of provider.
**To edit a VXC interface**
1. Select the MCR VXC you want to edit.
2. Select the VXC A-End or B-End.
3. Enter a description for the connection.
4. Enter one or more interface IP addresses and subnet masks to configure on the A-End interface.
5. (Optional) Select a NAT source IPv4 address from the **Network Address Translation (NAT)** drop-down list.\
All packets leaving this interface will have their source NAT rewritten to this address.
allows flexibility in designing a scalable and secure multi-vendor, multicloud, 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 (CSP) requirements.
For more information about how MCR performs NAT to support public peering types to cloud service providers, see [How MCR performs NAT](/mcr/mcr-nat/).
6. (Optional) Enter an value (in bytes) for the VXC.\
The IP MTU can range from 1280 to 9070 (9074 if Q-in-Q is disabled). The default value is 1500.\
For more information, see [MCR Advanced VLAN and Routing Features](/mcr/mcr-version-two/) and [Using IPsec with MCR](/mcr/ipsec-mcr/).
7. (Optional) If IPsec has been enabled on your MCR, you can configure IPsec tunnels.
Click **+ Add IPsec Tunnel Interface**.\
Add the IPsec tunnel details:
* **Description** -- Enter a description of the IPsec tunnel for your reference.
* **Source IP Address** -- Click the box and select the address from the drop-down list.\
This is a list of interface IP addresses defined on this VXC.
* **Destination IP Address** -- Add the destination IP address.\
The destination IP address of the tunnel must not be an IP address configured on the same MCR.
* **Pre-shared key** -- Add a key that is common to both the IKE2 (Internet Key Exchange version 2) initiator and responder. The length must be between 8 and 100 characters.
* **Local Identifier** (optional) -- Enter the identifier used for IKE authentication. This allows you to override the default source IP address with a non-IP address, which is required for some configurations. By default, the source IP address is used. Valid values include IPv4/IPv6 addresses, domain names, and email addresses (lowercase, 5-100 characters). For example, `megaport.com` or `user@example.com`.
* **Remote Identifier** (optional) -- Enter the identifier used for IKE authentication. This allows you to override the default destination IP address with a non-IP address, which is required for some configurations. By default, the destination IP address is used. Valid values include IPv4/IPv6 addresses, domain names, and email addresses (lowercase, 5-100 characters). For example, `megaport.com` or `user@example.com`.
* **Start Action** -- Select either active or passive. Passive indicates that the local MCR is an IPsec responder waiting for the remote to perform IKE2 initiation.
* **Phase 1 Lifetime** -- Enter a value between 300 and 604800 seconds. This is the lifetime of IKE2 session in seconds. The default value is 28800 seconds (8 hours). When it expires, rekeying will occur.
* **Phase 2 Lifetime** -- Enter a value between 300 and 86400 seconds. This is the lifetime in seconds of the IPsec Security Association (SA). The value must be less than the Phase 1 Lifetime. The default value is 3600 seconds (1 hour). When it expires, rekeying will occur.
8. Enter any details specific to the VXC type.
* For more information about configuring IPsec, see [Using IPsec with MCR](/mcr/ipsec-mcr/).
* For more information about using packet filters, see [Using Packet Filters](/mcr/packet-filters/).
* For more information about adding a BGP connection, see [Configuring BGP](/mcr/configuring-mcr/#configbgp).
* For more information about enabling Bidirectional Forwarding Detection (BFD) settings, see [Enabling the BFD protocol](/mcr/mcr-bgp-advanced/#bfd).
* For more information about adding a static route, see [Configuring static routes](/mcr/configuring-mcr/#static).
* For more information about configuring a DHCP server, see [Configuring a DHCP pool](/mcr/configuring-mcr/#dhcp).
9. Click **Save**.
## Using packet filter lists
Packet filters are used to manage the traffic that is allowed to flow through your MCR. You can apply packet filter lists to your VXC if they have been defined on the MCR. Using packet filter lists is optional.\
For more information, see [Using Packet Filters](/mcr/packet-filters).
**To apply packet filter lists**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC and select the A-End or B-End.
3. Select the packet filter lists to apply from the drop-down lists.\
You can select inbound and outbound filters.
4. Click **Save**.
## Configuring BGP
The allows dynamic route table updates from the MCR across the VXC to the port. Enable one or more BGP peers for the MCR, up to a maximum of 50.
**To configure BGP**
1. On the MCR Connection detail page, click **Add BGP Connection**.
2. Specify these values:
* **Local IP** -- Select the IP address on this interface that communicates
with the BGP peer. The drop-down menu is auto-populated based on the address
you specified in the connection detail.
* **Peer IP** -- Specify 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 2 to 4294967294. 4-byte ASNs are supported in the asplain format.
* **BGP Password** -- The shared key to authenticate the BGP peer. 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. The shared key length is from 1 to 25 characters. The key can include any of these characters:\
a-z\
A-Z\
0-9\
! @ # . \$ % ^ & \* + = - \_
Click the eye icon to see the password as you type. The view persists until you click the eye icon again to hide the password.
* **Description** (optional) -- Enter a description that will help identify this connection. The description length can range between 1 and 100 characters.
* **BGP State** -- Shuts down the connection without removing it. The initial setting will be taken from the setting on the A-End of the MCR. Enabling or shutting down the BGP state does not affect existing BGP sessions. The BGP state only affects new VXCs. This setting overrides the MCR state for an individual connection. For more information, see [Shutting down a BGP connection](#bgpshut) and [Creating an MCR](/mcr/creating-mcr).
- If you have entered multiple CIDR ranges, the IP addresses are available for selection.
- Use a CIDR calculator to ensure that all data is valid and within range.
3. Click **Add**.
4. Click **Next**.
**To edit a BGP connection**
1. Select the VXC and select MCR A-End or MCR B-End.
2. Next to the BGP connection, click **Edit**.
3. Make your changes.
4. Click **Update**.
For information on the BGP Advanced tab settings, see [Configuring BGP Advanced Settings](/mcr/mcr-bgp-advanced).
## 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.
An MCR supports up to 100 static routes.
**To add a static route**
1. Select the VXC and select MCR A-End.
2. In the MCR Connection detail page, under Static Routes, specify the IPv4 or IPv6 destination network address in CIDR notation.
3. Specify the IPv4 or IPv6 address of the next-hop router.\
The address must be in the same subnet as the interface but it cannot match the interface IP address.
4. (Optional) In the Description field, include any notes that will help identify this static route.\
The description range is from 1 to 100 characters.
5. Click **Next**.
6. Update the MCR B-End, if necessary.
7. Click **Next**.
8. Click **Update**.
To view static routes, see [Viewing Traffic Routing through the MCR Looking Glass](/mcr/mcr-looking-glass).
## Configuring a DHCP pool
You can configure a pool on an MCR VXC interface to assign IPv4 addresses to devices connected through that interface.\
When configured, the MCR acts as a for the connected network.
DHCP pools are not available on IPsec tunnel interfaces, connections to Megaport Internet, or connections to an Internet Exchange.
**To add a DHCP pool**
1. Select the gear icon on the VXC, then select MCR A-End.
2. Under DHCP Pool, click **+ Add Pool**.
3. Specify these values:
* **Network** -- The IPv4 network in Classless Inter-Domain Routing () notation for the DHCP pool. The network must be a valid IPv4 address and must be a subnet of the interface's IPv4 prefix. The minimum prefix length is /30. For example, `192.168.1.0/30`.\
For more information, see [Classless Inter-domain Routing (CIDR)](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing).
* **Start Address** -- The first IPv4 address in the range to assign to DHCP clients. The address must be within the specified network.
* **End Address** -- The last IPv4 address in the range to assign to DHCP clients. The address must be within the specified network and greater than or equal to the start address.
4. (Optional) Click **Add DNS Server** to specify one or more DNS resolver IP addresses provided to DHCP clients. You can add up to 5 DNS servers.
5. (Optional) Click **Add Default Gateway** to specify the default gateway IP address provided to DHCP clients.
6. (Optional) Click **Add Description** to enter a description for the DHCP pool. The description can be up to 100 characters.
7. Click **Save**.
**To delete a DHCP pool**
1. Select the gear icon on the VXC, then select MCR A-End.
2. Under DHCP Pool, click **Delete**.
3. Click **Save**.
## Verifying the BGP configuration
The MCR Looking Glass provides single-screen visibility into the BGP configuration. For more information, see [Viewing Traffic Routing through MCR Looking Glass](/mcr/mcr-looking-glass).
**To view the BGP status**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC.
3. Choose **Details**.\
The Configuration Details page shows the provisioning, service, and BGP status.
## Troubleshooting BGP
If the Services > Connection Detail page displays a status issue, verify these items:
1. Select the VXC and select MCR A-End or B-End.
2. Under BGP Connections, verify that the correct local ASN is in use for the A-End of the VXC.
3. Verify that the correct peer IP address is in use.
4. Verify that the correct BGP MD5 password is in use for the A-End 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
Use this setting to 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, troubleshooting, and so on.
**To temporarily disable a BGP connection**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC and select the A-End or B-End.
3. After the BGP connection details, click **Shut Down**.
4. Click **Yes** to confirm.
### Setting up MCR BGP notifications
You can receive email notifications whenever a session status changes on your MCR. These changes can include BGP going up, down, or flapping. If a session is flapping, only one email per hour will
be sent.
You can opt in or out of receiving these email notifications.
**MCR BGP notifications email specifications**
The MCR BGP notification system is designed to provide timely notifications for BGP up, down, or flapping events while minimizing alert noise.
The notification system implements rate limiting for rapidly changing status, as described below.
* The initial notification is sent immediately.
* Subsequent events within one hour are suppressed.
* The email body will indicate if the event has repeated during the suppression period.
**To receive BGP email notifications**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > User Settings > Notifications.
3. Click the Service Status notification group to view the BGP email notification types.
4. Select the notification group check box to subscribe to all notifications in that group, or subscribe to individual notification types. Any notification subscription changes are automatically saved.
## Configuring flow export
Flow export enables IP Flow Information Export () on MCR services, allowing you to export network flow records to external collectors for traffic analysis, capacity planning, and security monitoring.
You can configure up to three flow export targets for each MCR. Flow records are exported using either the UDP or TCP transport protocol.
A flow export target specifies the destination to which flow records are sent.
### Requirements
Before configuring flow export, ensure that your service meets these requirements:
* The MCR must be in a *Live* or *Configured* provisioning state.
* You must have a flow collector ready to receive IPFIX data.
* The MCR must have an active route to the collector via any attached VXC.
### Validation rules
These validation rules apply when configuring flow exporters:
* **Maximum Targets** -- Each service supports up to three flow export targets.
* **Target IP Address** -- Cannot be a reserved or loopback address (for example, 127.0.0.1).
* **Target Port** -- Must be between 1 and 65535.
* **MTU** -- If specified, must be a whole number between 512 and 9074 bytes.
* **Address Family** -- If you specify a Local IP Address, it must be the same address family (IPv4 or IPv6) as the Target IP Address.
* **Uniqueness** -- The combination of Target IP Address, Target Port, and Protocol must be unique within the service.
**To configure flow export**
1. In the Megaport Portal, go to the **Services** page.
2. Click the gear icon next to the MCR.
3. On the MCR Configuration page, select the **Flow Export** tab.
4. Click **Add Export Target**.
The Add Export Target page appears.
1. Specify the configuration details:
* **Description** -- Enter a name to identify this flow export target.
* **Local IP Address (optional)** -- The source IP address on the service for the flow export stream. Select an address configured on the service, or leave blank to use the default.
* **Target IP Address** -- Enter the IPv4 or IPv6 address of your flow collector.
* **Target Port** -- The port number of the flow collector (1-65535). Enter the port number your collector listens on.
* **Protocol** -- Select **UDP** or **TCP**.
* **MTU (optional)** -- Specify the maximum packet size, from 512 to 9074 bytes, for the flow export (IPFIX) stream. This limit is independent of the service MTU. Leave blank to use the service MTU.
2. Click **Add**.
The new flow export target configuration details are displayed in the table.
A maximum of three IPFIX export targets can be configured per service. Each target must have a unique combination of the Local IP Address and collector targets (Target IP Address, Target Port and Protocol).
**To edit a flow export configuration**
1. In the Megaport Portal, go to the **Services** page.
2. Click the gear icon next to the MCR.
3. On the MCR Configuration page, select the **Flow Export** tab.
4. In the row for the flow export configuration you want to edit, click **Edit**.
5. Update the configuration details as required.
6. Click **Save**.
**To delete a flow export configuration**
Deleting a flow export target immediately stops exporting flow records to that collector. This action cannot be undone.
1. In the Megaport Portal, go to the **Services** page.
2. Click the gear icon next to the MCR.
3. On the MCR Configuration page, select the **Flow Export** tab.
4. In the row for the flow export configuration you want to remove, click **Delete**.
5. In the confirmation prompt, click **Delete Target**.
## Helpful references
* [Creating an MCR ](/mcr/creating-mcr)
* [Creating an MCR VXC](/mcr/mcr-vxc)
* [Managing IPFIX Targets with the API](/api/api-ipfix-targets)
* [MCR Route Filtering](/mcr/route-filtering)
* [Using IPsec with MCR](/mcr/ipsec-mcr)
* [Using Packet Filters](/mcr/packet-filters)
* [Viewing Traffic Routing through MCR Looking Glass](/mcr/mcr-looking-glass)
# Creating an MCR
Source: https://docs.megaport.com/mcr/creating-mcr
This help topic describes how to create and configure a Megaport Cloud Router (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 will only be able to create MCR instances in billing markets you are registered in. For more information, see [Setting Up a Megaport Account](/setting-up).
You can configure prefix filter lists, packet filter lists, flow export, and BMP export only after the MCR is deployed. For more information, see [MCR Route Filtering](/mcr/route-filtering#filtering-by-bgp-prefix), [Using Packet Filters](/mcr/packet-filters), and [Configuring flow export](/mcr/configuring-mcr#configuring-flow-export).
**To create an MCR**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Service**, then select **Cloud Router (MCR)**.
The Create Cloud Router page opens. Complete the sections on this page to configure your MCR. The order summary updates as you make selections. On wider screens, the summary is displayed in a panel on the right. On narrower screens, it is displayed in a bar at the bottom of the page that you can expand.
3. In the **Details** section, specify these fields:
* **MCR Name** -- Specify a name that helps you identify the MCR, particularly if you plan to have more than one MCR. For example, `gcp-aws-mcr`.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Project** (optional) -- Select a project to add the MCR to, or leave the default (No Project).\
You can type in the field to search by project name. The selected project appears in the order summary, and the MCR is added to it when provisioned.
To create a project without leaving the page, select **New Project** at the bottom of the list, then specify a project name and, optionally, a description. The new project is automatically selected for the order.
You need permission to manage projects to create a project. Without this permission, the **New Project** option does not appear, but you can still select an existing project.
4. In the **Location** section, specify these fields:
* **Location** -- Select your preferred location. Use the **Search** field to find a location by metro name, country, data center name, or provider name. You can also search by address details, such as a street, city, state, or postcode. Alternatively, browse the region tabs, then select a location.
* **Mode** -- Select Auto to have Megaport automatically choose a provider and data center at the selected location. Select Manual to choose the provider and data center yourself.
* **Diversity Zone** -- Select Red or Blue, or select Auto to have Megaport select the zone for you. The selected diversity zone appears in the order summary. For more information, see [MCR Diversity](/mcr/mcr-mve-diversity).
5. If you selected Manual mode, in the **Provider** section, select a data center provider, then select a data center from the **Data Centre** drop-down list.\
Only providers and data centers available at your selected location are listed.
6. In the **Configuration** section, select the required **Rate Limit**.\
The MCR can scale from 1 Gbps to 100 Gbps. Available rate limits depend on the selected location and diversity zone. The rate limit is an aggregate capacity that determines the speed for all connections through the MCR, and is shared between all the Cloud Service Provider (CSP) connections added to it. The rate limit is fixed for the life of the service.
7. In the **BGP & ASN** section, specify these fields:
* **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 more information, see [MCR Peering Between Private Clouds](/mcr/mcr-private-cloud) and [Configuring BGP Advanced Settings](/mcr/mcr-bgp-advanced).
* **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 several 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 finish 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 more information about overriding the BGP state for an individual connection, see [Shutting down a BGP connection](/mcr/configuring-mcr#bgpshut).
8. In the **Add-ons** section, review the following:
* **IPsec** (optional) -- Turn on IPsec to add IPsec tunnels to the MCR, then select a **Number of Tunnels** (10, 20, or 30). For more information, see [Using IPsec with MCR](/mcr/ipsec-mcr).
9. In the **Pricing** section, specify these fields:
* **Contract Term** -- Select a contract term: No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate.
* **Contract Renewal** -- Automatically renews the contract at the same price and term length when the current term ends. The initial setting comes from your company default. If you disable it, the contract rolls over to a month-to-month term at the end of the current term, without the term discount. Contract Renewal is not available when you select No Minimum Term.
For more information, see [Managing Minimum Term Renewal](/portal-admin/auto-renew).
For more information about contract terms, see [MCR Pricing and Contract Terms](/finance/mcr-pricing).
10. In the **Resource Tags** section, add any tags you want to apply to this MCR.\
To add a tag, click **Add New Tag**, then specify these fields:
* **Key** -- Specify a lowercase string with a maximum length of 128 characters. Valid characters are lowercase letters, numbers, and `- . _ : / \`.
* **Value** -- Specify a string with a maximum length of 256 characters. Valid characters are letters, numbers, spaces, and `- . _ : @ / + \`.
Repeat for each tag. You can add up to 50 tags.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that identifies a person or company.
The price updates dynamically based on your selections in the order summary. Note that some partner-managed accounts do not display the pricing details.
11. Review the order summary, then click **Add MCR**.
The newly created MCR is added to your cart under Configured Services, ready for checkout.
12. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
13. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
14. Click **Order Now**.
The MCR provisioning takes approximately 59 seconds to complete.
MCR is postpaid. For example, if you place your order on January 15, your first invoice will be issued on February 1, and the charge will cover the period from January 15 to January 31.
Once the MCR has been provisioned and deployed, you can start adding Virtual Cross Connects (VXCs) 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 more information about adding VXCs, see [Creating an MCR VXC](/mcr/mcr-vxc).
## Using a service key
You can create a service key that allows you to share your service with another Megaport account holder.
For more information, see [Setting up Service Keys](/marketplace/service-keys/).
## Helpful references
* [Configuring an MCR](/mcr/configuring-mcr)
* [Creating an MCR VXC](/mcr/mcr-vxc)
* [MCR Billing](/finance/mcr-billing)
* [MCR Pricing and Contract Terms](/finance/mcr-pricing)
* [MCR Route Filtering](/mcr/route-filtering)
* [Using IPsec with MCR](/mcr/ipsec-mcr)
* [Using Packet Filters](/mcr/packet-filters)
* [Viewing Traffic Routing through MCR Looking Glass](/mcr/mcr-looking-glass)
# MCR Overview
Source: https://docs.megaport.com/mcr/index
This help topic describes the functionality and specifications of the Megaport Cloud Router (MCR).
The MCR is a managed virtual router service that establishes connectivity on the worldwide Megaport software-defined network (SDN). MCR instances are preconfigured in data centers in key global routing zones. An MCR enables data transfer between or hybrid cloud networks, network service providers, and cloud service providers.
An MCR instance is not physically cross-connected like a Port in the Megaport network. However, it can host VXC connections just like a physical Port and it can extend to any other Port in the Megaport network or another MCR.
## How it works
An MCR joins two or more independent Virtual Cross Connect (VXC) services into a single routing domain, providing connectivity between all the VXCs attached to the MCR.
Without physical infrastructure, you can use cloud-to-cloud networking, private peering between leading public Cloud, , and providers, and direct connectivity to any provider on the Megaport software-defined network (SDN). There is no need to own and maintain equipment. MCR removes the complexity of getting connected at Layer 3 and opens up new possibilities for virtualized networking.
You can use an MCR instance either with or without a physical Port in the Megaport network. If you want to configure multi-region deployments with a single Cloud Service Provider (CSP), or a multicloud deployment with multiple CSPs, MCR can enable both functionalities. Combining MCR functionality with a physical Port in the Megaport network has added benefits:
* Reduced latencies by enabling direct connections among cloud providers.
* Inter-region or inter-cloud connectivity to control and localize traffic.
For more information, see [Configuring an MCR](/mcr/configuring-mcr).
## Speed tiers
The MCR speed options are consolidated into these tiers:
| **Speed Tier** | **Symmetric Throughput** | **Asymmetric Throughput** |
| - | - | - |
| 1 Gbps | 0.5 Gbps/0.5 Gbps | 1 Gbps |
| 2.5 Gbps | 1.25/1.25 Gbps | 2.5 Gbps |
| 5 Gbps | 2.5/2.5 Gbps | 5 Gbps |
| 10 Gbps | 5/5 Gbps | 10 Gbps |
| 25 Gbps | 12.5 Gbps / 12.5 Gbps | 25 Gbps |
| 50 Gbps | 25 Gbps / 25 Gbps | 50 Gbps |
| 100 Gbps | 50 Gbps / 50 Gbps | 100 Gbps |
If higher throughput multicloud connectivity is required, please contact your Megaport Account Manager or Customer Success Manager to discuss alternative or early adopter options.
## Helpful references
* [Creating an MCR](/mcr/creating-mcr)
* [Enabling Cloud-Native VPN/Encryption Options Over Dedicated Cloud Connectivity Paths](/encryption/cloud-native-vpn-encryption)
* [Using IPsec with Megaport](/encryption/ipsec)
* [Using MACsec with Megaport](/encryption/macsec)
# Using IPsec with MCR
Source: https://docs.megaport.com/mcr/ipsec-mcr
This help topic describes how to set up and use IPsec on MCR in the Megaport Portal.
The IPsec add-on for MCR lets you create secure, encrypted tunnels from branch offices, remote sites, or cloud environments without deploying a physical Port. Extend your network with built-in encryption for public or private paths, from wherever you are.
You can enable IPsec when you create the MCR, or enable it on an existing MCR by editing the configuration. To add IPsec details, edit the MCR VXC and configure the IPsec tunnel as required.
You can configure up to 30 IPsec tunnels across all the VXCs connected to a single MCR. IPsec tunnels are available in packs of 10. Each MCR supports up to three packs, for a maximum total of 30 IPsec tunnels per MCR. If you require more than 30 IPsec tunnels, please contact the [Megaport Support team](/support/contact).
If you have an MCR with Megaport Internet in Mexico or the Netherlands, you must keep IPsec enabled. You cannot disable IPsec in these markets. For more information, see [Megaport Internet Overview](/megaport-internet).
## Supported ciphers
The MCR will offer the following ciphers to IPsec peers. At this time, the options are not configurable.
**Encryption**
* AES128-GCM-128
* AES256-GCM-128
**Integrity**
* HMAC SHA-1
* HMAC SHA-256
* HMAC SHA-384
* HMAC SHA-512
**Key Exchange (Diffie-Hellman group)**
* MODP
* Diffie-Hellman Group 2 (1024-bit)
* Diffie-Hellman Group 14 (2048-bit)
* ECP
* Diffie-Hellman Group 19 (256-bit random)
* Diffie-Hellman Group 20 (384-bit random)
* Diffie-Hellman Group 21 (521-bit random)
## IP MTU settings
IPsec packets include overhead due to encryption and encapsulation. We recommend that you configure your carefully to suit your network. The maximum value depends on the negotiated ciphers.
If you do not configure the IP MTU setting, the MCR will use the following default values:
* 96 bytes less than the parent interface IP MTU for IPv4
* 116 bytes less than the parent interface IP MTU for IPv6
These values allow for ciphers that have the largest overhead.
## Enabling and configuring IPsec on an MCR
### Enabling IPsec on an MCR
To enable IPsec when you are creating an MCR, turn on **IPsec** in the **Add-ons** section of the Create Cloud Router page. Then select the required number of tunnels.
For more information, see [Creating an MCR](/mcr/creating-mcr).
You configure the IPsec connection details on the MCR VXC, as described below.
### Configuring IPsec on an MCR
**Prerequisites**
To configure IPsec for an MCR connection, you will need:
* **A configured interface** -- For each VXC connected to an MCR, you can configure one or more interfaces.
The IPsec tunnel details are dependent on having an IP address on the interface tab. Each MCR VXC will have one interface by default, but you can add more.
For more information, see the A-End interface section of [Creating an MCR VXC](/mcr/mcr-vxc#interface).
* **Pre-shared key** -- This is a value that you provide. It is used as part of establishing the tunnel on both ends.
* The length must be between 8 and 100 characters.
* This is a required field.
* **Destination IP Address** -- The IP address of the destination endpoint in IPv4/6 format. For example, **192.168.1.2**.
**To configure IPsec on the MCR VXC**
1. Create your connection, such as a cloud or private VXC.\
For more information, see [Creating an MCR VXC](/mcr/mcr-vxc).
2. Wait for the connection to be live, then click the gear icon next to the VXC to edit the details.
3. Click **Next** or click **A-End** on the header.
4. Add a description to the **Interface** presented on the page, if required.\
This is the default interface.
5. Click **+ Add IPsec Tunnel Interface**.\
Add the IPsec tunnel details:
* **Description** -- Enter a description of the IPsec tunnel for your reference.
* **Source IP Address** -- Click the box and select the address from the drop-down list.\
This is a list of interface IP addresses defined on this VXC.
* **Destination IP Address** -- Add the destination IP address.\
The destination IP address of the tunnel must not be an IP address configured on the same MCR.
* **Pre-shared key** -- Add a key that is common to both the IKE2 (Internet Key Exchange version 2) initiator and responder. The length must be between 8 and 100 characters.
* **Local Identifier** (optional) -- Enter the identifier used for IKE authentication. This allows you to override the default source IP address with a non-IP address, which is required for some configurations. By default, the source IP address is used. Valid values include IPv4/IPv6 addresses, domain names, and email addresses (lowercase, 5-100 characters). For example, `megaport.com` or `user@example.com`.
* **Remote Identifier** (optional) -- Enter the identifier used for IKE authentication. This allows you to override the default destination IP address with a non-IP address, which is required for some configurations. By default, the destination IP address is used. Valid values include IPv4/IPv6 addresses, domain names, and email addresses (lowercase, 5-100 characters). For example, `megaport.com` or `user@example.com`.
* **Start Action** -- Select either active or passive. Passive indicates that the local MCR is an IPsec responder waiting for the remote to perform IKE2 initiation.
* **Phase 1 Lifetime** -- Enter a value between 300 and 604800 seconds. This is the lifetime of IKE2 session in seconds. The default value is 28800 seconds (8 hours). When it expires, rekeying will occur.
* **Phase 2 Lifetime** -- Enter a value between 300 and 86400 seconds. This is the lifetime in seconds of the IPsec Security Association (SA). The value must be less than the Phase 1 Lifetime. The default value is 3600 seconds (1 hour). When it expires, rekeying will occur.
6. Scroll down the page and click **Save**.
## Helpful references
* [Configuring an MCR ](/mcr/configuring-mcr)
* [IPsec Overhead Calculator](https://ipsec-overhead-calculator.netsec.us/)
* [IPsec Solutions](https://www.megaport.com/solutions/ipsec-tunnel/)
* [Using IPsec with Megaport](/encryption/ipsec)
* [What is IPsec?](https://www.megaport.com/blog/what-is-ipsec/)
# Configuring BGP Advanced Settings
Source: https://docs.megaport.com/mcr/mcr-bgp-advanced
This help topic describes how to configure advanced Border Gateway Protocol (BGP) settings in the Megaport Cloud Router (MCR).
This topic describes how to manage advanced Border Gateway Protocol (BGP) settings in the Megaport Cloud Router (MCR):
* An option to override the default autonomous system number (ASN).
* An ASN prepend option to set route advertisement priorities.
* An AS Override option to let multiple peers connected to the same MCR to use the same ASN.
* The identifies the preferred VXC used to re-route traffic after a path failure.
* The protocol detects any path failures between BGP neighbors.
* AS Override replaces the peer's ASN in the AS path with the local ASN when routing to sites that share the same ASN.
## Overriding the MCR ASN
The default assigned to the MCR is 133937. For most configurations, the default ASN is appropriate. Optionally, you can specify another local ASN to override the default ASN on a per-peer basis.
Cloud providers can have restrictions on the ASN value. See the documentation for your cloud provider before overriding the default value.
**To override the MCR ASN**
1. Select the VXC and select A-End or B-End.
2. Next to the BGP connection, click **Edit**.
3. Select the **Advanced** tab.
4. In the **Local ASN** field, enter a public or private ASN (for example, enter a number from 64512 to 65534).
The ASN range is from 2 to 4294967294, but the following ASNs are not available:
* 8074, 8075, 12076, 65515 - 65520 (reserved in Azure)
* 23456, 64496-64511, 65535 - 65551 (reserved by Internet Assigned Numbers Authority (IANA))
5. Click **Update**.
## Setting the route advertisement priority with ASN prepend
The ASN path length determines the route advertisement priority for outgoing BGP paths. The route with the shortest AS path has the highest preference, and it is preferred over any longer path advertisements. Longer path lengths have a lower priority. AS path prepending lengthens the path to lower the path priority.
Setting an ASN prepend value is optional.
**To set the path advertisement priority on an existing BGP connection**
1. Select the VXC and select the A-End or B-End.
2. Next to the BGP connection, click **Edit**.
3. Select the **Advanced** tab.
4. In the **AS Path Prepend** field, enter the number of additional times to add the local ASN to the BGP path. Enter integer(s) within the range of 1 to 10. For example, 2 prepends the ASN to the existing AS path twice, creating an AS path length of 3. Higher numbers deprioritize the path.
5. Click **Update**.
**To set the path advertisement priority on a new BGP connection**
1. Add a new BGP connection.
2. Select the **Advanced** tab.
3. In the **AS Path Prepend** field, enter the number of additional times to add the local ASN to the BGP path. Enter integer(s) within the range of 1 to 10. For example, 2 prepends the ASN to the existing AS path twice, creating an AS path length of 3. Higher numbers deprioritize the path.
4. Click **Add**.
## Enabling the BFD protocol
BGP shares network reachability information with adjacent BGP systems, which are referred to as *neighbors* or *peers*. The BFD protocol detects path failure between directly connected BGP neighbors, allowing for a faster BGP routing re-convergence time.
Enabling BFD on a VXC connection provides fast link failure detection and failover when connecting to services that support BFD on the remote neighbor. After BFD is enabled, a BGP neighbor relationship can be torn down quickly after notifications from BFD, failing over to another BGP neighbor. BFD settings apply to all BGP connections on the interface.
The BFD protocol runs independent of BGP. When BFD is enabled, failover is faster because it occurs before the BGP timer interval elapses. The default setting for the BGP timer is 3 keep-alive window failures of 60 seconds each. When not enabled, failover will only occur after the BGP timer interval elapses.
The default BFD settings cannot be maintained. These settings are configured when you enable BFD:
* : 300 milliseconds
* : 300 milliseconds
* : 3
To prevent high CPU utilization, before you enable BFD, disable the sending of Internet Control Message Protocol (ICMP) redirect messages by entering the `no ip redirect` command.
**To enable BFD**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC and select the A-End or B-End.
3. Next to the BGP connection, click **Edit**.
4. Select the **Advanced** tab.
5. Next to the **Use BFD** field, click **On**.
6. Click **Update**.
You must enable BFD on the BGP neighbor as well.
**Default BFD values by Cloud Service Provider (CSP)**
* **AWS Direct Connect** -- BFD is supported natively by AWS Direct Connect connections. Asynchronous BFD is automatically enabled for AWS Direct Connect virtual interfaces on the CSP side. However, you must enable BFD on MCR VXCs to AWS Direct Connect for your connection.
By default, the AWS BFD liveness detection minimum interval is 300 milliseconds and the multiplier is 3 packets.
Confirm support for other neighbors with your CSP, as well as specific default values.
* **Azure ExpressRoute** -- BFD is supported natively by Azure ExpressRoute on private peering. BFD is configured by default under all the newly created ExpressRoute private peering interfaces on the MSEEs. However, you must configure MCR VXCs to Azure ExpressRoute private peering for BFD to enable it for your connection. Between BFD peers, the slowest peer determines the transmission rate.
* **Microsoft Enterprise Edge (MSEE) ExpressRoute routers** -- BFD transmit and receive intervals are set to 300 milliseconds.
* **Google Cloud Services** -- In late 2021, Google Cloud Partner Interconnect announced support for enhanced features with their Interconnect service. The new features are included in Dataplane V2. BFD is one feature that is now available in V2. BFD was not supported before the launch of V2.
Google is in the process of migrating from V1 to V2 with an expected completion date of September 2022. To support the new features, including BFD, the Interconnect Location (Google Edge) and the region where Interconnect connects to Google Cloud Router must both have V2 enabled. For more information about how to confirm your Dataplane version, see [Bidirectional Forwarding Detection (BFD) for Cloud Router](https://cloud.google.com/network-connectivity/docs/router/concepts/bfd).
Before enabling BFD on MCR after May 11, 2022, you need to validate that the Megaport VXC/Google VLAN Attachment with your Partner Interconnect service has enabled V2. For more information about how to validate your Dataplane version, see [Bidirectional Forwarding Detection (BFD) for Cloud Router](https://cloud.google.com/network-connectivity/docs/router/concepts/bfd). If V2 is not enabled, you need to open a Google support case to enable it. In some cases, V2 might not be available. If your VLAN attachment does not use Dataplane V2, do not enable BFD.
MCR automatically operates in BFD single-hop mode for VXCs created after May 11, 2022. VXCs created on MCR before May 11, 2022 use BFD multihop and are not compatible with BFD. You need to **reorder** any VXCs created on MCR to Google before May 11, 2022 before you can enable BFD.
## Enabling AS Override
Each participant in a BGP session is identified by an AS number (autonomous system number). BGP has a built-in mechanism for preventing routing loops; if a router receives a route that already contains its own AS number in the path, the router rejects it.
When you enable AS Override, the replaces the peer's AS number with its own in the route advertisement, bypassing the loop-detection check of the downstream device.
For example, a company has two sites (New York and London) that use the same AS number (AS 65001) and are connected through (AS 100):
1. The New York site (AS 65001) advertises a route to the (AS 100).
2. The (AS 100) passes that route to the London site.
3. The London router (AS 65001) sees AS 65001 in the AS\_PATH and rejects the prefix.
In the same scenario with AS Override enabled:
1. The New York site (AS 65001) advertises a route to the (AS 100).
2. The (AS 100) passes that route to the London site. The replaces AS 65001 with AS 100 in the AS\_PATH.
3. The London router (AS 65001) sees AS 100 in the AS\_PATH and accepts the prefix because it doesn't match its own AS number.
You can only enable AS override on eBGP (external BGP) connections, where the Peer ASN and Local ASN are different. You cannot apply AS override to iBGP (internal BGP) connections, where the Peer ASN and Local ASN are the same.
**To enable AS override**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC, then select the A-End or B-End.
3. Next to the BGP connection, click **Edit**.
4. Select the **Advanced** tab.
5. Next to **AS Override**, click **On** to enable it.
6. Click **Update**.
7. Click **Save**.
**To disable AS override**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC, then select the A-End or B-End.
3. Next to the BGP connection, click **Edit**.
4. Select the **Advanced** tab.
5. Next to **AS Override**, click **Off** to disable it.
6. Click **Update**.
7. Click **Save**.
## Configuring a preferred route
A Multi-Exit Discriminator (MED) is a BGP path attribute that can influence a BGP
neighbor to take a preferred route when the advertising autonomous system (AS) is the same for candidate routes and there are multiple entry points for that AS. A lower MED metric is preferred over a higher metric. You can use the MED attribute to switch traffic between two VXCs and avoid ECMP (equal-cost multipath) behavior.
Other BGP attributes are taken into account before considering the MED attribute. The MED attribute breaks the tie between two routes when the weight, local preference, AS path, and origin type are the same. The exit point with the
lowest MED metric is preferred.
For example, a configuration that consists of a BGP neighbor device, R3, with a MED metric of 20 and another neighbor device, R2, with a MED metric of 10 will cause autonomous system (AS) 123 (of which device R2 and R3 are members) to prefer the path through R2 to reach ASN4.
Adding or changing an MED metric doesn't disrupt the service.
**To configure the MED**
1. Select the VXC and select A-End or B-End.
2. Next to the BGP connection, click **Edit**.
3. Select the **Advanced** tab.
4. In the **Inbound** field, specify a 32-bit integer MED metric to apply to all routes received on this BGP connection. Leave blank to use the value received from the BGP neighbor.
5. In the **Outbound** field, specify a 32-bit integer MED metric to apply to all routes transmitted by this BGP connection.
6. Click **Update**.
**Using MED with Google Cloud Platform**
Google Cloud Platform Cloud Router egress is determined by the first condition that is met:
* All egress traffic is sent to the route with the shortest AS path length.
* If routes have the same
AS path lengths, all egress traffic is sent to the route with the lowest MED value (the lowest route metric).
* If routes have the same AS path lengths and MED values (the same route metrics), egress traffic is balanced across all routes using equal-cost multipath (ECMP).
Confirm support for other neighbors with your CSP, along with any specific routing metric influences that might have a higher priority than the MED.
## Enabling AS Override
AS Override replaces the peer's autonomous system number (ASN) in the AS\_PATH attribute of outbound BGP routes with the local ASN. This feature helps connect sites that share the same ASN by allowing BGP routes to be advertised to peers that would otherwise reject them due to loop detection.
AS Override is valid only for eBGP connections. The local ASN must differ from the peer ASN to enable this option. If the local ASN equals the peer ASN (an iBGP connection), the AS Override toggle is disabled.
**To enable AS Override**
1. Select the VXC and select A End or B End.
2. Next to the BGP connection, click **Edit**.
3. Select the **Advanced** tab.
4. Next to **AS Override**, click **On**.
5. Click **Update**.
# Viewing Traffic Routing through MCR Looking Glass
Source: https://docs.megaport.com/mcr/mcr-looking-glass
This help topic describes how to view traffic routing in the Megaport Cloud Router (MCR).
This topic describes the Megaport Cloud Router (MCR) Looking Glass. The Looking Glass provides single-screen visibility into traffic routing. This visibility helps you troubleshoot connections by showing the status of protocols and routing tables in the MCR.
## MCR route selection
MCR uses Border Gateway Protocol (BGP) to exchange network reachability information with adjacent BGP systems, known as *neighbors*, or *peers*. During the process of transporting data between BGP neighbors from a source to a destination, MCR makes complex routing decisions about where to send traffic over available routes.
MCR forwards traffic on preferred routes using a combination of metrics received from BGP neighbors and settings on the MCR itself. In addition, MCR follows standard BGP policies and autonomous system (AS) routing best practices. All routes are stored in a routing table. The routing table merges all of the routes from different protocols and connected networks.
## What the Looking Glass tells you
The Looking Glass answers questions such as:
* What route is MCR currently using to send traffic?
* What are all possible routes MCR can use?
* What IP prefixes and routes have I received from my BGP neighbor(s)?
* Which routes have been advertised to my BGP neighbor(s)?
* Does a route exist in the routing table for a specific destination?
Megaport offers a public API that you can use to access the services available through the Looking Glass. For more information, see [Megaport API Overview](/api).
## Viewing the Looking Glass
The routing table information is available through the Looking Glass only after you have provisioned one or more MCRs.
**To view the Looking Glass**
1. Log in to the Megaport Portal and select Services.
2. Choose Tools > MCR/NAT Gateway Looking Glass.\
Or click the binoculars icon next to an MCR for easy access.
The Looking Glass displays the routing table entries along with the path MCR uses to arrive at a destination, the VXCs that connect the BGP neighbors, the protocols associated with the routes, and more.
* **MCR Selection** -- A drop-down list of all provisioned MCRs for an account.
* **BGP Sessions** -- This section includes all BGP sessions configured on the VXCs for the selected MCR.
* **Routing Table** -- This table provides the big picture by displaying all of the networks that MCR can reach, including static, local, connected, and BGP routes. MCR consults this table when selecting the best route for forwarding traffic to a destination.
When MCR has more than 20 route table entries, the list is paginated. You can change how many routes are displayed per page using the drop-down list at the bottom of the routing table.
The total number of entries in the routing table appears at the top and the bottom of the routing table.
## BGP sessions
BGP communicates between two neighbors using a standard TCP connection. Once connected, the BGP neighbors share routing information with each other. The connection between the neighbors is called a BGP session. The BGP Sessions list includes all BGP sessions running on the Virtual Cross Connects (VXCs) for the selected MCR.
Use this list to find all routes that have been advertised or received from BGP neighbors.
**To search for routes within a BGP session**
1. Type an IP address or text to find matches.
2. Click **Neighbour Routes** to open a new tab for that session.
The tab shows the routes advertised toward or received from that peer BGP router.
3. Select Advertised or Received to sort the routes.
You can open up to five session tabs simultaneously. Adding more than five sessions replaces the first tab selection with the latest tab selection.
**To sort the table by column**
* Click the up/down triangles next to a column heading.\
The table columns reload, if necessary.
* Click the heading again to reverse the order.\
A small up or down triangle reflects the current bidirectional sort order.
### VXC details
Status icons indicate the current BGP session status:
* A green check mark means that the session is up.
* A red x means that the session is down.
* A yellow information icon means that the session status is unknown.
**To view or edit a VXC**
* Click the VXC name.\
The Connection Details page appears.
## Routing table
The routing table includes all of the networks that MCR can reach, along with the path MCR uses to arrive at a destination.
When MCR receives a packet, it examines the packet’s destination IP address and uses the routing table to make forwarding decisions accordingly. For example, suppose MCR is selecting a route for a packet with a destination IP address of 10.0.0.3. MCR consults the routing table and considers 10.0.0.0/8 and 10.0.0.0/24 as candidates because they both cover the address range. In this example, MCR would select 10.0.0.0/24 as the best match, because it is the most specific.
### Searching the routing table
This section describes several ways to retrieve detailed information about routes.
**To view the routing table**
1. Select the **Routes Table** tab.
2. Select All Routes.
3. After Protocol, select All Types.\
The Looking Glass displays all routes. The total number of routes appears at the top and bottom of the routing table.
**To view routes by IP or network address**
1. Select Routes by IP.
2. Enter an IPv4, IPv6, or network address with an optional subnet mask.
When you enter the address, the control validates it and displays its format. For example, enter a valid IPv4 address and *IPv4* appears in the control.
The Looking Glass searches for all routes associated with the protocol and displays matching table entries.
The Looking Glass searches through the entire routing table, not just the current page you are viewing.
**To view routes by protocol**
1. Select All Routes.
2. Select a protocol.\
The Looking Glass searches for all routes associated with the protocol and displays matching table entries.
**To view routes using a text filter**
1. Select All Routes.
2. Enter text, one search term at a time. For example, type Azure or 20.\
The Looking Glass filters the table based on the search term and displays matching table entries.
This table describes the column headings and their meaning.
| **Heading** | **Description** |
| :- | :- |
| Prefix | Displays the destination network of the route. An IP network is a group of IP addresses. The network address is the prefix. For example:
IPv4 address: 192.0.2.1 IPv4 network prefix: 192.0.2.0/24 (includes 192.0.2.0 - 192.0.2.255) |
| Metric | Displays the route’s local preference. |
| Protocol | Connected - Indicates the route was learned as a result of configuring the interface and is directly connected to the interface.
Static - Indicates the route was explicitly configured as a static route.
BGP - Indicates the route was received through BGP update messages from a BGP neighbor.
Local - Indicates the route is local to MCR. |
| Distance | Displays the administrative distance assigned to the route. This value can be used during selection of the best route when there are two different routes to the same destination from two different routing protocols. The smaller the administrative distance, the higher the preference. |
| Next Hop | Displays the IP address of an adjacent router, or hop, in the remote network that tells MCR where to send the packet.
An IP address of 0.0.0.0 indicates the route is local to MCR and MCR doesn’t need a next hop address to route the traffic to its destination. |
| Next Hop VXC | Provides a link to the next hop VXC Connection Details page, so you can edit the VXC. |
**To sort the table by column**
* Click the up/down triangles next to a column heading.\
The table columns reload, if necessary.
* Click the triangle in the heading again to reverse the order. The triangle reflects the current bidirectional sort order.
## Viewing BGP routes
A BGP route is a destination consisting of an IP address prefix and other details describing the path to the destination. The BGP table page displays the BGP table that summarizes all BGP routes (not only the best routes) from all the BGP neighbors, including several routes to the same network with different attributes.
**To view the BGP table**
1. Select the **BGP Table** tab.
2. Select All Routes.
**To search for BGP routes by IP address**
1. Select the **BGP Table** tab.
2. Select Routes by IP.
3. Enter an IPv4 or IPv6 network address with an optional subnet mask.
When you enter the address, the control validates it and displays its format. For example, enter a valid IPv4 address and *IPv4* appears in the control.\
The Looking Glass searches for the prefix and displays entries from the BGP routing table.
**To view routes using a text filter**
1. Select All Routes.
2. Enter text, one search term at a time. For example, type AWS or 20.\
The Looking Glass filters the table based on the search term and displays matching table entries.
This table describes the column headings and their meaning.
| **Heading** | **Description** |
| :- | :- |
| Prefix | Displays the destination network of the route. An IP network is a group of IP addresses. The network address is the prefix. For example:
Click the Copy icon to copy the prefix to the clipboard. |
| Best Route | For each prefix in the routing table, when there are two or more next-hop routers advertising a path to that destination network, MCR selects the preferred route. MCR uses the metrics and distance values from the received route advertisements to determine the best route to a destination.
A check mark indicates that MCR considers this route to be the best when choosing between two routes to the same destination.
An X indicates that MCR does not prefer this route when choosing between two routes to the same destination. |
| Next Hop | Displays the IP address of this particular hop in the remote network. A blank space indicates that this route is Local or Connected and doesn’t need another router to reach it. |
| Next Hop VXC | Provides a link to to edit the VXC used to reach the next hop. |
### BGP route details
BGP routes have several associated attributes that MCR can consider to select the best route. Looking Glass retrieves the values for the BGP attributes directly from MCR. They can either be values that MCR has received, or they can be values that MCR has set.
**To view BGP route details**
* Select the down arrow next to a prefix.
This table describes the attributes and their meaning.
| **Attribute** | **Description** |
| :- | :- |
| AS path | Displays a list of all autonomous system numbers (ASNs) through which the route has passed. For example:
132863 58941 58941 4826
Each ASN identifies an individual BGP network.
Shorter AS paths are preferred because a shorter path can indicate a closer destination. |
| Local Preference | Displays the preference used within an autonomous system. The highest local preference is preferred. The default value is 100. |
| Multi-Exit Discriminator | Displays the Multi-Exit Discriminator (MED) value that is considered while selecting the preferred traffic route.
MCR considers the MED when the advertising AS path is the same for candidate routes and there are multiple entry points for that AS. To determine the preferred VXC, MCR selects a lower MED metric over a higher metric.
For more information about setting the MED, see [Configuring a preferred route](/mcr/mcr-bgp-advanced#med). |
| Origin | Indicates where a prefix came from. A prefix origin is a key factor used by BGP to select the best path to a destination between multiple alternative paths in the network. The lowest value is preferred.
IGP - Indicates that the prefix originated from an Interior Gateway Protocol. This origin has the lowest and most preferred value.
EGP - Indicates that the prefix originated from an Exterior Gateway Protocol. This origin has the medium value.
Incomplete - Indicates that the prefix was learned via other means, such as statically defined. This origin has the highest value. |
| Updated | Displays the last time the route was updated. |
## Viewing static routes
Static routes are manually defined and maintained. Static routing is not really a routing protocol but instead a simple process of manually entering a route prefix and destination to define a route.
**To view static routes**
1. Select the **Routes Table** tab.
2. Select All Routes.
3. For Protocol, select Static.
## Reloading the data
Routes are added, updated, and withdrawn from the routing tables as the networks change.
The Looking Glass collects route details when you select an MCR and doesn’t refresh changes to the routes table automatically. The routes table updates when you manually reload the data.
**To reload the route information**
* Click **Reload Data** in the upper-right corner.
The MCR Looking Glass has a limit of 100 requests per day per MCR.
# MCR Diversity
Source: https://docs.megaport.com/mcr/mcr-mve-diversity
This help topic describes the functionality and specifications of the diversity of Megaport Cloud Router (MCR).
Diverse connections improve the robustness of your network by using different physical infrastructure to provide network services. Diverse connections build in redundancy and eliminate single points of failure.
() simplifies the deployment of diverse connections by establishing diversity zones. A diversity zone is a group of devices at a single Megaport location. s in different diversity zones are physically separated on Megaport devices and connected to different devices.
During Megaport scheduled maintenance, no more than one diversity zone in a given metro will experience downtime at any time. Whenever possible, diversity zones in the same city have maintenance periods scheduled for different days.
Each indicates its diversity zone with either a red or blue icon.
## Selecting a diversity zone
When you select the location for your , you can select the diversity zone.
When you choose a diversity zone, the location results list will be filtered by that zone:
* **Auto (default)** -- This will show all locations where is available.
* **Red or Blue diversity zone** -- If you select Red or Blue diversity zone, only locations that have availability in that zone will be displayed.
| Icon | Meaning | Use case |
| :-: | :- | :- |
| | Auto select diversity zone | Allow Megaport to allocate the diversity zone |
| | Red diversity zone | Allocate the to the red diversity zone |
| | Blue diversity zone | Allocate the to the blue diversity zone |
### Auto diversity zone
If you choose the Auto diversity zone option, Megaport will select the zone to which your service is allocated.\
The following rules apply:
* If both diversity zones are available, one zone will be chosen.
* If only one zone is available, that zone will be chosen.
# How MCR Performs NAT
Source: https://docs.megaport.com/mcr/mcr-nat
This help topic describes how NAT on the MCR supports public peering to Cloud Service Providers.
conserves IPv4 address space by translating the unregistered private IP addresses used for an organization's private inner network into a single registered public IP address. This single public IP address is then used to connect to external networks, like the internet.
This topic describes how NAT on the MCR is designed to specifically support public peering types to Cloud Service Providers.
## Many-to-one NAT using different ports
MCR supports Overload NAT, also known as Source Overload NAT or NAT Overload, which is a form of many-to-one NAT. It works as follows:
* **Source NAT (SNAT)** -- Translates multiple private IP addresses to a single public IP address.
* **Port Address Translation (PAT)** -- Assigns unique source ports to ensure that each connection remains distinct.
This configuration supports egress traffic (outbound connectivity) to Megaport Marketplace partners and other external networks, such as the internet or cloud services.
The MCR commonly performs NAT at the boundary where two networks are connected. For example, before forwarding packets from the inner network to the outer network, the MCR translates the private, non-unique IP addresses to a single, globally unique public IP address. This many-to-one translation allows the MCR to advertise only one IP address to the outside world while hiding multiple private source IP addresses behind the IP address of the MCR interface.
While a typical use case involves translating private IP addresses on the inside network to a public IP address on the outside network, this is not a strict requirement. The MCR can translate any IP address—private or public—on either interface as required.
NAT on the MCR is similar to Cisco's NAT overload or Checkpoint's Hide NAT functionality.
MCR keeps track of each IP address translation and port assignment in a NAT table that can handle thousands of concurrent translations. When a port is no longer in use, MCR releases it and returns it to the pool of available ports.
This image shows an MCR at the edge of the data center, privately connecting to the Azure Platform as a Service () with a Virtual Cross Connect (VXC) into Azure public peering, known as Microsoft Peering. Because Microsoft will only accept public IPv4 addresses through Microsoft Peering, the MCR translates the private IP addresses to public addresses using NAT. The MCR provides the added benefit of using Megaport's autonomous system number (ASN) and publicly registered IP space for this connection.
## MCR NAT example
In this example, MCR is logically sitting between a customer's data center (10.100.0.0/16) and Azure (West US 13.100.0.0/16). Packets destined for 13.100.0.0/16 are sent from the data center to the MCR.
1. The data center sends a packet with a source IP of 10.100.20.10 and a destination IP of 13.100.12.136 toward the MCR.
2. MCR receives the packet on its inside interface. Upon egress, MCR performs a SNAT to translate the source IP address (10.100.20.10) to the local IP address of its outside interface (117.18.84.113). To create a unique session, MCR also performs a PAT and assigns the session a unique TCP or UDP source port. The destination IP and port are left intact.
3. When Azure receives the packet, it has a source IP of 117.18.84.113. Azure forwards the packet to the destination 13.100.12.136 and replies back to the source at 117.18.84.113.
4. Assume that Azure receives another packet from MCR with a source IP of 10.100.5.16 and a destination IP of 13.100.14.27. MCR performs a SNAT to the same IP address of 117.18.84.113. The only difference is the TCP/UDP source port that has been automatically assigned by MCR.
## Verifying the NAT assignment
MCR automatically configures the VLAN IDs used for private and public peering after you configure the peering type. When provisioning VXCs from the MCR to a service provider, MCR configures the private peering with VLAN 100 and the public peering with VLAN 200, by default.
This image shows MCR with a VXC connecting to Azure. During the initial VXC configuration, both Private and Public Microsoft peering types were selected. For this configuration, MCR automatically configured VLAN 100 to support private peering and VLAN 200 to support the public Microsoft peering.
The **Network Address Translation (NAT)** field appears to the right of the Interface IP Addresses field. The NAT Source IP address is the IP address of the MCR's outside interface, to which any packets will be translated.
When multiple Azure VXCs on an MCR populate the same VLAN 100 tag (private peering) and the same VLAN 200 tag (public peering), MCR manages the 802.1Q tunnel, also known as a Q-in-Q tunnel, for each Azure VXC that terminates on the MCR. Each Azure VLAN will still be a separate logical interface. For more information, see [Configuring Q-in-Q](/connections/q-in-q).
# MCR Peering Between Private Clouds
Source: https://docs.megaport.com/mcr/mcr-private-cloud
This help topic describes Megaport Cloud Router (MCR) peering.
Megaport Cloud Router (MCR) supports architectures that include combinations of private and public cloud peering types, as well as non-cloud connectivity to your data center. This topic describes:
* The MCR connectivity options supported by the Cloud Service Providers (CSPs) for peering between private clouds.
* How autonomous system numbers (ASNs) work with the Border Gateway Protocol (BGP) routing to advertise routes.
## Supported connectivity options with MCR
MCR allows you to build a robust architecture that supports private peering to multiple cloud providers. You can provide connectivity to the same cloud provider, in different regions, with different on-ramps, as long as each BGP peer has a different ASN.
This section describes many, but not all, of the supported private peering connectivity architectures with the MCR. Because networks are not identical, the examples provide a starting point for your peering architecture.
### AWS private peering between VPCs
AWS provides the ability to route between different AWS Virtual Private Clouds (VPCs) when using your own private ASN and the MCR.
### Azure private peering with a single ExpressRoute and multiple VNets
With Azure, you can attach multiple virtual networks (VNets) to the same ExpressRoute and route traffic between the VNets without leaving the Azure network.
Azure private peering with *dual* ExpressRoute is not supported.
In this scenario, BGP loop prevention will prevent routes from being advertised, because Azure will detect its own ASN in the AS path.
### Azure private peering with dual ExpressRoute inter-VNet routing
MCR supports an architecture with dual ExpressRoute circuits connecting each VNet to both ExpressRoute circuits. Because the inter-VNet routing occurs without leaving Azure, the AS path is not evaluated. This deployment provides high availability while also allowing for inter-VNet routing.
### Google Cloud Platform VPC peering
VPCs in Google Cloud Platform (GCP) are global and include subnets for each region. GCP provides the ability to perform VPC peering to route traffic between two VPCs.
### Oracle Cloud Infrastructure VCN peering
Oracle provides remote Virtual Cloud Network (VCN) peering to route between regions. Support includes routing between Oracle Cloud Infrastructure (OCI) and OCI Classic, or between OCI and Oracle Government Cloud.
External routing between OCI commercial regions is not supported.
For more information, see [Remote VCN Peering](https://docs.cloud.oracle.com/iaas/Content/Network/Tasks/remoteVCNpeering.htm).
## Understanding autonomous system numbers
An autonomous system (AS) is a single network or a set of networks and routers that are managed and supervised on behalf of a single administrative entity, such as a business division. An AS is assigned a globally unique number that identifies the network to the world.
The MCR uses BGP to exchange routes between private peering and non-cloud peering types. To reduce the complexity of BGP support for the CSPs, the MCR provides automated configuration and follows standard BGP routing policies and inter-AS routing best practices. Although the MCR follows routing best practices and BGP has built-in loop prevention, an understanding of the autonomous system path list is helpful when assigning ASNs to peers.
### Understanding AS path loop prevention
When routes are advertised to an external BGP (eBGP) neighbor, the ASN of the local router is added to the AS path list (AS\_PATH). To the receiving autonomous system (AS), this creates a breadcrumb trail to the originating AS. This image shows two routers, R2 and R3, with the same ASN:
When an eBGP peer receives an eBGP route that includes its own AS number in the AS path, it will drop the route to prevent a BGP route loop. This is the expected behavior with BGP. In this scenario, because R2 and R3 have the same ASN, R3 will drop R2’s routes upon arrival.
After updating R2’s configuration with a unique AS number, 64515, R3 now accepts the routes being advertised by R2. It’s important to keep this in mind when configuring peering between two private clouds.
## Private ASN support
With AWS Direct Connect gateway, you can bring your own private ASN to the Amazon side of the connection. Other cloud service providers require you to peer using their public ASN.
This table summarizes the supported ASNs from each CSP:
| **Cloud Provider** | **Peering Type** | **Customer Side AS** | **Cloud Provider Side AS** |
| :- | :- | :- | :- |
| AWS | PRIV\_CLOUD | Private or Public ASN | Private ASN or ASN 7224 |
| Google Cloud | PRIV\_CLOUD | Private or Public ASN | ASN 16550 |
| Oracle Cloud | PRIV\_CLOUD | Private or Public ASN | ASN 31898 (Gov Cloud 6142) |
| Microsoft Azure | PRIV\_CLOUD | Private or Public ASN | ASN 12076 |
To learn more, explore these resources.
* AWS -- [AWS Direct Connect FAQs](https://aws.amazon.com/directconnect/faqs/)
* Google Cloud -- [Establishing 99.99% Availability for Partner Interconnect](https://cloud.google.com/interconnect/docs/tutorials/partner-creating-9999-availability)
* Oracle Cloud -- [FastConnect Requirements](https://docs.cloud.oracle.com/iaas/Content/Network/Concepts/fastconnectrequirements.htm#requirements)
* Microsoft Azure -- [Autonomous System numbers (ASN)](https://learn.microsoft.com/en-us/azure/expressroute/expressroute-routing#autonomous-system-numbers-asn)
# Resizing or Moving an MCR
Source: https://docs.megaport.com/mcr/mcr-resizing-moving
This help topic describes how to resize an MCR to a different rate limit or move an MCR to a different data center within the same metro.
This topic describes how to resize a Megaport Cloud Router (MCR) to a different rate limit or move an MCR to a different data center within the same metro. Because the MCR rate limit is fixed for the duration of the service and you cannot change its location, both operations require creating a new MCR and migrating your Virtual Cross Connects (VXCs) to the new instance.
The Move VXC feature transfers VXCs from one MCR to another within the same metro without recreating them. For more information, see [Moving VXCs](/connections/move-vxc).
## When to resize or move an MCR
Common scenarios for resizing or moving an MCR include:
* **Upgrading capacity** -- Your bandwidth requirements have grown beyond the current MCR rate limit.
* **Downsizing** -- Your traffic has decreased and you want to reduce costs by moving to a smaller rate limit.
* **Data center migration** -- Moving to a different data center within the same metro for improved latency, diversity, or other operational reasons.
* **Diversity requirements** -- Deploying MCRs in different diversity zones to improve resilience. For more information, see [MCR Diversity](/mcr/mcr-mve-diversity).
## Before you begin
Before starting the migration, gather the following information about your existing MCR:
* **Current configuration** -- The MCR ASN, BGP default state, and any service level reference numbers.
* **VXC inventory** -- Document all VXCs connected to the MCR, including their rate limits and VLAN assignments.
* **BGP configuration** -- All BGP peer configurations, including peer IP addresses, peer ASNs, and BGP passwords.
* **Route filters** -- Export or document any prefix filter lists and BGP peer filters configured on the MCR.
* **Packet filters** -- Any packet filter lists configured on the new MCR.
* **Static routes** -- Any static routes configured on the MCR.
* **IP addressing** -- Interface IP addresses for each VXC.
Prefix filter lists and packet filter lists are transferred between MCRs when you move VXCs. The MCR name, ASN, and BGP Default State must be configured on the new MCR; all other VXC configuration is transferred automatically during the move.
You can obtain this information from the Terraform configuration file if you are using Terraform, or your preferred AI tool. For more information, see [Creating a Megaport Terraform Provider Configuration File](/terraform/megaport-terraform-configuration) and [Megaport MCP Server Overview](/mcp-server).
## Planning the migration
### Preparation steps
1. **Verify VXC eligibility** -- Confirm that your VXCs can be moved. VXCs can only be moved between services of the same type within the same metro. For the full list of conditions, see [Conditions for moving a VXC](/connections/move-vxc#conditions).
2. **Plan IP addressing** -- Determine whether you will maintain the same IP addressing scheme on the new MCR. The interface IP addresses are configured per VXC and transferred with the VXC when moved.
3. **Document the configuration** -- Use the MCR Looking Glass to capture your current routing state before migration. For more information, see [Viewing Traffic Routing through MCR Looking Glass](/mcr/mcr-looking-glass).
4. **Coordinate with Cloud Service Providers (CSPs)** - If your MCR connects to CSPs, review any provider-specific requirements that might affect the migration.
5. **Schedule a maintenance window** - Moving VXCs will cause a brief traffic interruption as the connection is transferred to the new MCR.
### Understanding outage expectations
When you move a VXC from one MCR to another:
* **Traffic interruption** -- Traffic stops flowing through the VXC during the move. The VXC briefly goes offline and then comes back online on the new MCR. The interruption typically lasts from a few seconds to a few minutes, depending on provisioning times and routing configuration.
* **BGP session reset** -- BGP sessions drop during the move and re-establish after the VXC is live on the new MCR. Recovery time depends on your BGP timer configuration and the number of routes being exchanged.
* **Cloud provider VXCs** – Connections to CSPs such as AWS, Azure, and Google Cloud experience the same brief outage. BGP sessions drop and re-establish after the move.
Plan to move VXCs during a scheduled maintenance window when a brief traffic interruption is acceptable.
## Migration workflow
### Step 1 -- Create the new MCR
Create a new MCR with your required configuration:
1. Create the MCR with the new rate limit or in the new data center location.\
For more information, see [Creating an MCR](/mcr/creating-mcr).
2. Configure the same ASN as your existing MCR to maintain consistent BGP identity, or use a different ASN if required.
The new MCR can use a different ASN from the existing MCR if all VXCs are configured with a `local-as` value. In this scenario, BGP peers continue to see the `local-as` configured on the VXC rather than the MCR ASN. All VXCs must have `local-as` configured for this approach to work.
3. Set the **BGP Default State** to **Shut Down** if you want to preconfigure BGP sessions before enabling route exchange.
We recommend setting the **BGP Default State** to **Shut Down** on the new MCR. This prevents BGP sessions from establishing during VXC migration before routing policies and filters are applied, reducing the risk of unintended route advertisements, particularly to CSPs with route limits or quotas. You can choose a different approach if appropriate for your environment.
### Step 2 -- Move VXCs to the new MCR
Move your VXCs from the old MCR to the new one:
1. In the Megaport Portal, go to the **Services** page and select the original MCR.
2. Click the **Move Connections** icon.
3. Select the VXCs you want to move.
4. Select the new MCR as the destination in the Move To area.
5. Review your selections and click **Move**, then **Confirm**.
For more information, see [Moving VXCs](/connections/move-vxc).
You can move multiple VXCs at once. Consider whether to move all connections simultaneously for a single maintenance window or move them in phases.
### Step 3 -- Check filters and verify BGP
After moving each VXC:
1. Edit the VXC on the new MCR and confirm that any prefix filter lists and packet filter lists were successfully moved to the new MCR.
2. If you set the **BGP Default State** to **Shut Down**, enable the BGP sessions.
3. Verify that BGP sessions establish successfully by checking the BGP status in the VXC configuration or the MCR Looking Glass.
For more information, see [Configuring an MCR](/mcr/configuring-mcr).
### Step 4 -- Verify routing and connectivity
After moving VXCs:
1. Open the MCR Looking Glass for the new MCR.
2. Verify that BGP sessions show as established (green check mark).
3. Check the routing table to confirm expected routes are present.
4. Verify that routes are being advertised and received correctly by viewing neighbor routes.
5. Test end-to-end connectivity through the new MCR.\
You can use the MCR Looking Glass or ping and traceroute tests to verify traffic is flowing correctly through the new MCR.
For more information, see [Viewing Traffic Routing through MCR Looking Glass](/mcr/mcr-looking-glass) and [Troubleshooting an MCR Routing Issue](/troubleshooting/mcr/routing).
### Step 5 -- Terminate the old MCR
After all VXCs have been moved and verified on the new MCR:
1. Confirm that no VXCs remain on the original MCR.
2. Terminate the old MCR.\
For more information, see [Terminating an MCR](/mcr/terminating-mcr).
Terminating an MCR on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. For more information, see [MCR Pricing and Contract Terms](/finance/mcr-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
## Helpful references
* [Configuring an MCR](/mcr/configuring-mcr)
* [Creating an MCR](/mcr/creating-mcr)
* [MCR Diversity](/mcr/mcr-mve-diversity)
* [MCR Route Filtering](/mcr/route-filtering)
* [Moving VXCs](/connections/move-vxc)
* [Terminating an MCR](/mcr/terminating-mcr)
* [Using Packet Filters with MCR](/mcr/packet-filters)
* [Viewing Traffic Routing through MCR Looking Glass](/mcr/mcr-looking-glass)
# MCR Advanced VLAN and Routing Features
Source: https://docs.megaport.com/mcr/mcr-version-two
This help topic describes the advanced VLAN and routing features on Megaport Cloud Router (MCR).
The Megaport Cloud Router (MCR) is easy to configure for IP routing without needing to understand complex network protocols. This topic describes the MCR advanced VLAN and routing features that extend an MCR's capabilities beyond the default settings.
## MCR Looking Glass
The MCR Looking Glass provides single-screen visibility into traffic routing. This visibility helps you troubleshoot connections by showing the status of protocols and routing tables in the MCR.
For more information, see [Viewing Traffic Routing through the MCR Looking Glass](/mcr/mcr-looking-glass).
## VLANs
The Q-in-Q Connection option allows either a single VLAN (non Q-in-Q, also known as 802.1Q) or
stacked VLANs (Q-in-Q, also known as 802.1ad) to be carried over a VXC. In most cases, you will 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 being configured.
For certain use cases, you might need multiple inner VLANs exposed to a Port using Q-in-Q.
For more information about Q-in-Q, see [Configuring Q-in-Q](/connections/q-in-q).
MCR supports the standard Ethernet MTU of 1500 bytes.
## Public IP address allocation
When ordering the MCR, public IP addresses are provided as required, based on specific CSP requirements. Megaport will allocate up to a /29 free of charge from the Megaport address space for this connectivity. You can also use your own public IP addresses.
For an Azure ExpressRoute primary and secondary IP address, Megaport provides a /30 or 4 addresses for each.
## Security
You can enable Message Digest 5 (MD5) authentication between two eBGP neighbors to have
MCR verify each segment sent on the connection between the neighbors.
## IP MTU (Maximum Transmission Unit)
You can set the IP MTU value on an MCR up to a maximum of 9070 (if Q-in-Q is enabled) or 9074 (if Q-in-Q is disabled).
Fewer, larger packets ensure faster data transfer with reduced packet processing overhead. This is ideal for transferring large files between clouds or improving performance for high-throughput applications, such as machine learning workloads.
## Routing features
MCR manages both static and dynamic routes, up to 10,000 routes. These routing options are available for individual configuration of each sub-VLAN (C-Tag) on Q-in-Q capable connections.
### Dynamic routing
Dynamic routing propagates route table updates from the MCR across the VXC to the destination Port. MCR uses the Border Gateway Protocol (BGP) to provide flexible routing by exchanging routing information between peers.
MCR supports these BGP routing features:
### Bidirectional Forwarding Detection (BFD)
Enabling BFD on a VXC connection provides fast link failure detection and failover when connecting to services that support BFD on the remote peer. After BFD is enabled, a BGP peer relationship can be torn down quickly after notifications from BFD, failing over to another BGP peer.
For more information about the BGP BFD setting, see [Enabling the BFD protocol](/mcr/mcr-bgp-advanced#bfd).
### Multiple Exit Discriminator (MED)
MED is enabled on a VXC connection. For information on the MED setting, see [Configuring a preferred route](/mcr/mcr-bgp-advanced#med).
### BGP on/off toggle
BGP shutdown provides an easy way to administratively shut down a BGP connection without removing it. This feature can be useful while setting up a new route, performing maintenance, and so on.
For information on the BGP shutdown setting, see [Shutting down a BGP connection](/mcr/configuring-mcr#bgpshut).
### Static routing
Without BGP, MCRs use static routing to directly connect manually configured routes that access a single route. Static routing is generally used in place of BGP when a customer device does not support BGP or the target device requires manually configured IP addressing and routes.
For information on static routing, see [Configuring static routes](/mcr/configuring-mcr#static).
### Autonomous system number support
An autonomous system (AS) is a single network or a set of networks and routers that are managed and
supervised by a common network administrator (or group of administrators) on behalf of a single
administrative entity, such as a business division. An AS is assigned a globally unique number that
identifies the network to the world. MCR supports both 2-byte and 4-byte autonomous system numbers (ASNs).
ASN support includes per-peer local ASNs.
For more information about how MCR uses ASNs for route advertisement, see [MCR Private Cloud Peering](/mcr/mcr-private-cloud).
### NAT IP addresses
is generally used for public and private NAT or inter-customer isolation. You can configure NAT for static or dynamic routing.
For more information, see [Creating an MCR VXC](/mcr/mcr-vxc) and [How MCR Performs NAT](/mcr/mcr-nat).
# Creating an MCR VXC
Source: https://docs.megaport.com/mcr/mcr-vxc
This help topic describes how to create Virtual Cross Connects (VXCs) on a Megaport Cloud Router (MCR) to connect to services on the Megaport network.
With a Megaport Cloud Router (MCR) configured, you can 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.
A VXC 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 MCR.
The VXC target destination type determines the peering type. The peering type determines which routes are advertised. For more information, see [MCR Route Advertisement](/mcr/route-advertisement).
**To create and connect a VXC**
1. Log in to the Megaport Portal, select
**Services**, then select the MCR.\
If you haven't already created an MCR, see [Creating an MCR](/mcr/creating-mcr).
2. 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:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
For specific CSP configuration details:
* 3DS Outscale -- See [Creating MCR Connections to 3DS Outscale](/cloud/mcr/outscale).
* Alibaba -- See [Creating MCR Connections to Alibaba Express](/cloud/mcr/alibaba).
* AWS -- See [Creating MCR Connections to AWS](/cloud/mcr/aws).
* Azure -- See [Creating MCR Connections to Azure using ExpressRoute](/cloud/mcr/azure).
* DigitalOcean -- See [Creating MCR Connections to DigitalOcean Infrastructure](/cloud/mcr/digitalocean).
* Google -- See [Creating MCR Connections to Google Cloud Services](/cloud/mcr/google).
* IBM -- See [Creating MCR Connections to IBM Cloud Direct Link](/cloud/mcr/ibm-2.0).
* Latitude.sh -- See [Creating MCR Connections to Latitude.sh](/cloud/mcr/latitude-sh).
* Oracle -- See [Creating MCR Connections to Oracle Cloud Infrastructure](/cloud/mcr/oracle).
* OVHcloud -- See [Creating MCR Connections to OVHcloud Connect](/cloud/mcr/ovhcloud).
* Salesforce -- See [Creating MCR Connections to Salesforce Express Connect](/cloud/mcr/salesforce).
* SAP -- See [Creating MCR Connections to SAP HANA Enterprise Cloud](/cloud/mcr/sap).
* **Private VXC** -- Connect to other Ports local to the current company account. After selecting Private VXC, select a destination Port. For more information, see [Creating a Private VXC](/connections/private-vxc).
* **Megaport Internet** -- Connect to the internet. After selecting Megaport Internet, select a destination Port (internet router). For more information, see [Creating a Megaport Internet Connection for an MCR](/megaport-internet/mcr).
* **Megaport Marketplace** -- Connect to any service provider present in the Megaport Marketplace. After selecting Megaport Marketplace, select a provider. For more information, see [Megaport Marketplace](/marketplace/overview).
* **Enter Service Key** -- Connect to a third-party on the Megaport network that isn't publicly listed in the Megaport Marketplace. Select this destination if you have been given a service key, and enter the service key. For more information, see [Creating a Connection using a Service Key](/marketplace/create-connection-service-key).
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Specify 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.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred B-End VLAN** -- Specify the 802.1q VLAN tag for this connection that you will receive through the B-End VLAN. This field will show if the configuration requires this information.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.\
The MCR A-End Connection Details page appears. For each VXC connected to an MCR, you can configure one or more interfaces, IP addresses, BGP connections, packet filter lists, and static routes. Most VXCs will use one interface, however, you can configure multiple interfaces by enabling a connection and specifying an inner VLAN tag for each interface. Each VLAN ID must be unique and you can add up to five VLAN IDs.
The MCR A-End Connection Details page is not displayed during MCR VXC creation in some situations, and is dependent on the VXC destination. The MCR VXC configuration will be auto-configured in these situations. If you are creating a single-use service key on an MCR, the configuration is not auto-configured and the page will be displayed. For information about configuring connection details when they are auto-configured, see [Configuring an MCR](/mcr/configuring-mcr).
6. If required, click **Enable Q-in-Q** to enable multiple interfaces and click **+ Add Interface** to add an additional interface.
7. Enter a description for the connection.
8. Enter one or more interface IP addresses and subnet masks to configure on the A-End interface.
9. (Optional) Select a NAT source IPv4 address from the **Network Address Translation (NAT)** drop-down list.\
All packets leaving this interface will have their source NAT rewritten to this address.
allows flexibility in designing a scalable and secure multi-vendor, multicloud, 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 (CSP) requirements.
For more information about how MCR performs NAT to support public peering types to cloud service providers, see [How MCR performs NAT](/mcr/mcr-nat/).
10. (Optional) Enter an value (in bytes) for the VXC.\
The IP MTU can range from 1280 to 9070 (9074 if Q-in-Q is disabled). The default value is 1500.\
For more information, see [MCR Advanced VLAN and Routing Features](/mcr/mcr-version-two/) and [Using IPsec with MCR](/mcr/ipsec-mcr/).
11. (Optional) If IPsec has been enabled on your MCR, you can configure IPsec tunnels.
Click **+ Add IPsec Tunnel Interface**.\
Add the IPsec tunnel details:
* **Description** -- Enter a description of the IPsec tunnel for your reference.
* **Source IP Address** -- Click the box and select the address from the drop-down list.\
This is a list of interface IP addresses defined on this VXC.
* **Destination IP Address** -- Add the destination IP address.\
The destination IP address of the tunnel must not be an IP address configured on the same MCR.
* **Pre-shared key** -- Add a key that is common to both the IKE2 (Internet Key Exchange version 2) initiator and responder. The length must be between 8 and 100 characters.
* **Local Identifier** (optional) -- Enter the identifier used for IKE authentication. This allows you to override the default source IP address with a non-IP address, which is required for some configurations. By default, the source IP address is used. Valid values include IPv4/IPv6 addresses, domain names, and email addresses (lowercase, 5-100 characters). For example, `megaport.com` or `user@example.com`.
* **Remote Identifier** (optional) -- Enter the identifier used for IKE authentication. This allows you to override the default destination IP address with a non-IP address, which is required for some configurations. By default, the destination IP address is used. Valid values include IPv4/IPv6 addresses, domain names, and email addresses (lowercase, 5-100 characters). For example, `megaport.com` or `user@example.com`.
* **Start Action** -- Select either active or passive. Passive indicates that the local MCR is an IPsec responder waiting for the remote to perform IKE2 initiation.
* **Phase 1 Lifetime** -- Enter a value between 300 and 604800 seconds. This is the lifetime of IKE2 session in seconds. The default value is 28800 seconds (8 hours). When it expires, rekeying will occur.
* **Phase 2 Lifetime** -- Enter a value between 300 and 86400 seconds. This is the lifetime in seconds of the IPsec Security Association (SA). The value must be less than the Phase 1 Lifetime. The default value is 3600 seconds (1 hour). When it expires, rekeying will occur.
12. Enter any details specific to the VXC type.
* For more information about configuring IPsec, see [Using IPsec with MCR](/mcr/ipsec-mcr/).
* For more information about using packet filters, see [Using Packet Filters](/mcr/packet-filters/).
* For more information about adding a BGP connection, see [Configuring BGP](/mcr/configuring-mcr/#configbgp).
* For more information about enabling Bidirectional Forwarding Detection (BFD) settings, see [Enabling the BFD protocol](/mcr/mcr-bgp-advanced/#bfd).
* For more information about adding a static route, see [Configuring static routes](/mcr/configuring-mcr/#static).
* For more information about configuring a DHCP server, see [Configuring a DHCP pool](/mcr/configuring-mcr/#dhcp).
13. Click **Next**.
14. Configure the B-End.\
The requirements will vary by destination or provider.
15. Click **Next**.\
The Summary page appears.
16. Review the Summary details.\
Click each down arrow to view A-End and B-End configuration details.
17. Click **Add VXC** to move this configuration to your cart.
18. Repeat these steps to provision any additional VXCs.
19. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
20. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
21. Click **Order Now**.
# Using Packet Filters with MCR
Source: https://docs.megaport.com/mcr/packet-filters
This help topic describes how to create and use packet filter lists when creating a connection to an MCR.
Packet filters control which traffic flows through your Megaport Cloud Router (MCR). Packet filters allow data from defined IP addresses to pass through, and deny access to data from other defined IP addresses.
Packet filters are defined on an MCR after it has been ordered and has gone live. You then edit the configuration of your MCR to add the packet filters that you need. When you configure a connection to your MCR, you can add your packet filters to either the A-End or B-End of the connection, depending on your MCR's location.
## Packet filter rules
* Packet filter lists are defined on a deployed MCR.
* Packet filter lists are applied to the VXC interface - either A-End or B-End, depending where your MCR is located.
* If no packet filters are applied to the connection, then all traffic is allowed to flow through your MCR.
* When a packet filter is applied to the connection, any traffic not permitted by the packet filter is denied.
* Packet filters support the following matches:
* Source IP Address
* Destination IP Address
* IP Protocol
* Source Port/Port Range (for TCP and UDP protocols)
* Destination Port/Port Range (for TCP and UDP protocols)
* Packet filters support both IPv4 and IPv6.
* You can create up to 20 packet filter lists.
* Each packet filter list can contain up to 50 entries.
## Creating packet filters
You can only create packet filters on a deployed MCR. You can create a maximum of 20 packet filter lists per MCR.
**To create a packet filter list**
1. Create, order, and deploy an MCR.\
For more information, see [Creating an MCR](/mcr/creating-mcr).
2. On the Services page, find your new MCR and click the gear icon next to the MCR in the Portal.
The MCR Configuration screen appears.
3. Click the **Packet Filter Lists** tab.\
The Packet Filter List page appears.
4. Click **New List** to add a new list.
5. Enter a name for your packet filter list in the **Name** field.
6. Enter your filter details.
* **Action** -- Select Permit or Deny from the drop-down list.
* **Source IP Address** -- Enter the source IP address you want to filter traffic from.
* **Destination IP Address** -- Enter the destination IP address of your filter.
The source IP address and destination IP address must be the same format. For example, they must both be IPv4 or IPv6.
* **Protocol** -- Select the protocol to filter traffic on. If the protocol you require is not on the list, you can select **Custom**.
* **IP Protocol Number** -- This will be populated automatically when you choose a protocol from the drop-down list. If you choose **Custom**, you must enter a number from the list of assigned internet protocol numbers.
* **Source Ports** -- You can specify a source port or a range of ports in the format 1111-9999.
* **Destination Ports** -- Specify a destination port or a range of ports.
* **Description** (optional) - Add a description.
Use the position icon at the beginning of the row to reorder the list using drag and drop.\
Click the trash icon at the end of the row to delete an entry in a list.
7. Add as many entries to the list as you need, up to a maximum of 50 per list.
8. Click **Save**.
## Editing a packet filter list
Add or delete entries from a packet filter list, or update the settings of each entry.
**To edit a packet filter list**
1. Select the list you want to edit from the drop-down list.
2. Make your changes.\
You can change any part of the list.
3. Click **Save**.
## Duplicating a packet filter list
You can duplicate a list to speed up filter configuration.
**To duplicate a packet filter list**
1. Select the list you want to duplicate from the drop-down list.
2. Click **Duplicate List**.
3. Enter a name for the list in the **Name** field.
4. Edit the required details in the list to make it unique.
5. Click **Save**.
## Deleting a packet filter list
You can delete entire lists if they are not required any more or are out of date.
**To delete a packet filter list**
1. Select the list you want to delete from the drop-down list.
2. Click **Delete List**.
3. Click **OK** to confirm.
## Applying a packet filter list
You can apply a packet filter list to the VXC when you create a connection from your MCR.
**To apply a packet filter list**
1. Create a connection from the MCR with the packet filter lists defined.\
For more information, see [Creating an MCR VXC](/mcr/mcr-vxc).
2. In the VXC definition, enter the connection details then click **Next**.
3. On the MCR A-End page, enter these details:
* **Interface IP Addresses** -- Enter the A-End interface IP address and subnet mask as required for your network.
* **Packet Filters** -- Select a packet filter list from the **Inbound** or **Outbound** drop-down list, as required for your configuration.
You can also fill in other fields here, such as Network Address Translation (NAT) or BGP connections.
For more information, see [How MCR performs NAT](/mcr/mcr-nat) and [Configuring BGP Advanced Settings](/mcr/mcr-bgp-advanced).
4. Click **Next**.
5. Read the Summary page and click **Add VXC**.
## Helpful references
* [Configuring an MCR ](/mcr/configuring-mcr)
* [Creating an MCR](/mcr/creating-mcr)
* [Creating an MCR VXC](/mcr/mcr-vxc)
* [MCR Route Filtering](/mcr/route-filtering)
* [Viewing Traffic Routing through MCR Looking Glass](/mcr/mcr-looking-glass)
# MCR Route Advertisement
Source: https://docs.megaport.com/mcr/route-advertisement
This help topic describes Megaport Cloud Router (MCR) peering types and the routes advertised by each type.
This topic describes MCR peering types and the routes advertised by each peering type.
The Megaport Cloud Router (MCR) works in architectures that are connected using different combinations of peering types. In addition to private peering connectivity, MCR can connect to public peering types such as AWS, Azure, Oracle, and other Cloud Service Providers (CSPs).
MCR uses a Virtual Cross Connect (VXC) to connect to other endpoints on the Megaport network. The VXCs support different types of peers. MCR employs routing policies aligned with the VXC peering type.
The peering type defined for the VXC determines which routes are advertised.
## MCR peering types
MCR supports the peering types shown in this table:
| **Peering Type** | **Megaport Peering Attribute** | **Routes Advertised** |
| :- | :- | :- |
| Non-cloud | NON\_CLOUD | Routes from the Border Gateway Protocol (BGP) peer behind a Port and AWS Hosted Connections. |
| Private cloud | PRIV\_CLOUD | Routes from AWS Hosted VIF Private, Azure Private Peer, and Google Cloud Platform. |
| Public cloud | PUB\_CLOUD | Routes from AWS Hosted VIF Public, Azure MS Peer, Salesforce, and other cloud providers. |
* Although you can configure private cloud and public cloud peering types simultaneously, MCR does not exchange routes between the two.
* AWS Direct Connect Hosted Connection partners cannot see the VIF type created within AWS. As a result, traffic from these hosted connections is categorized as NON\_CLOUD. MCR users should take care not to advertise public cloud routes to other cloud providers. MCR route filtering is available to help manage this.
### Non-cloud VXCs
NON\_CLOUD VXCs are categorized into these types:
* **Physical Port Connections** -- VXCs connected to a physical port in a data center, typically referring to private network infrastructure.
* **AWS Hosted Connections** -- These are classified as NON\_CLOUD because AWS connectivity partners do not have a mechanism to identify the VIF type created within AWS.
* **Megaport Marketplace Service Providers** -- Connections to various service providers listed in the Megaport Marketplace.
* **Business-to-Business (B2B) VXCs** -- Connections established between multiple Megaport accounts using service keys. For more information, see [Setting up Service Keys](/marketplace/service-keys).
| **Megaport Endpoint** | **Peering Type** |
| :- | :- |
| Physical Port | Private VXC |
| MCR | AWS Hosted Connection on VXC |
| Megaport Marketplace | Private VXC |
| B2B VXC | Service Key |
### Private cloud VXCs
Private cloud (PRIV\_CLOUD) VXCs connect to private peering options with public Cloud Service Providers (CSPs). Private peering typically involves exchanging RFC 1918 routes with the service provider.
| **Cloud Service Provider** | **Peering Type** |
| :- | :- |
| AWS Direct Connect | Hosted VIF with Private VIF |
| Azure ExpressRoute | Private Peering |
| Google Cloud Interconnect | Partner Interconnect Attachment |
| Oracle Cloud Infrastructure | FastConnect Private Peering |
Similar connectivity is available from IBM Cloud, Alibaba, SAP HANA Enterprise Cloud, and many other CSPs. For a full list of CSPs, see [MCR Cloud Connectivity Overview](/cloud/mcr).
### Public cloud VXCs
Public cloud (PUB\_CLOUD) VXCs provide direct connectivity to public peering options from public CSPs. Public peering options typically involve exchanging public address space with a service provider.
| **Cloud Service Provider** | **Peering Type** |
| :- | :- |
| AWS Direct Connect | Hosted VIF with Public VIF |
| Azure ExpressRoute | Microsoft Peering |
| Salesforce | ExpressConnect |
| Oracle Cloud Infrastructure | FastConnect Public Peering |
## Route advertisement scenarios
### Non-cloud and private cloud
A combination of non-cloud and private cloud connectivity is fairly straightforward when it comes to route advertisement. Using network virtualization and segmentation mechanisms allow multi-tenant networks to exchange private RFC 1918 address space between each environment. The private cloud is introduced as a private node on your internal network.
This image shows a corporation using a firewall to segment its cloud connectivity. The cloud network is connecting from their firewall in the data center to their MCR via a private NON\_CLOUD VXC. MCR is, in turn, connecting to AWS via a PRIV\_CLOUD VXC.
### Public cloud
The public cloud connectivity option requires the exchange of public address space, similar to peering with an internet service provider (ISP). Large organizations that require connectivity to multiple ISPs employ network engineers and architects that are familiar with all of the nuanced requirements necessary to participate in exchanging public routes on the internet.
MCR alleviates some of these nuances by providing default policies that ensure you don’t inadvertently advertise public routes belonging to one CSP to another CSP. For example, consider route advertisement in a network topology with an ExpressRoute Microsoft peering to Azure and a public virtual interface (VIF) to AWS.
If any-to-any connectivity were allowed between the two public cloud peerings, all traffic between AWS and Azure would traverse MCR. This would cause a global service disruption for both CSPs. To avoid service disruption, the CSPs protect their customers with policies that prevent this type of misconfiguration. However, because mistakes can happen, MCR also has routing mechanisms in place to restrict the public cloud peering types from exchanging public address spaces.
### MCR route advertisement configurations
The supported MCR route advertisement configuration types are:
* Public cloud → Non-cloud
* Private cloud → Non-cloud, Private cloud
* Non-cloud → Non-cloud, Private cloud, Public cloud
Support for these peering configuration types enables a globally available platform that allows rapid, on-demand deployment of routing services in a secure manner, with best practice routing policies already applied.
# MCR Route Filtering
Source: https://docs.megaport.com/mcr/route-filtering
This help topic describes Megaport Cloud Router (MCR) route filtering.
This topic describes Megaport Cloud Router (MCR) route filtering.
Route filtering provides selective control over which networks are discoverable between Border Gateway Protocol (BGP) neighbor routers. Route filtering is configured to influence the routing path and manage redundancy, while improving security.
This topic includes these sections:
* [How routes are advertised without filters](/mcr/route-filtering#defaultroutes)
* [Selecting a filter type](/mcr/route-filtering#selectfilter)
* [Creating BGP prefix filters using match criteria](/mcr/route-filtering#bgpprefixfilter)
* [Maintaining prefix filters](/mcr/route-filtering#maintainfilters)
* [Validating routes after applying filters](/mcr/route-filtering#validateroutes)
## Route filtering overview
Route filtering provides control over MCR route installation and propagation, typically between two or more networks. The networks can be either on-premises or a Cloud Service Provider (CSP).
You can use route filtering to:
* Redistribute or prevent redistribution of routes between Virtual Cross Connects (VXCs).
* Create a BGP prefix filter that includes a set of IPv4 or IPv6 CIDR blocks to manage as a group.
* Allow or deny specific routes on specific connections.
## Default peering route advertisements
MCR uses to exchange network reachability information with adjacent BGP systems, known as *neighbors*, or *peers*. MCR works in architectures that are connected using different combinations of peering types. In addition to private peering connectivity, the MCR can connect to public peering types such as AWS, Azure, Oracle, and other cloud service providers (CSPs).
BGP communicates between two neighbors using a standard TCP connection. By default, once the BGP neighbors are connected, they share routing information with each other. The connection between the neighbors is called a BGP connection or session.
Without using any route filters, Megaport advertises routes to BGP connections based on these peering types:
| **Peering Type** | **Routes Advertised** | **Advertised To** |
| :- | :- | :- |
| Non-cloud | Routes from the Border Gateway Protocol (BGP) peer behind a Port. | Non-cloud, private cloud, public cloud |
| Private cloud | Routes from AWS Private, Azure Private Peer, and Google Cloud Platform. | Non-cloud, private cloud |
| Public cloud | Routes from AWS Public, Azure MS Peer, Salesforce, and other cloud providers. | Non-cloud |
As an example, a route received from a Public Cloud BGP connection will not be advertised to a Private Cloud BGP connection.
You cannot override or control the peering type route advertisement.
Route filtering doesn’t change this existing peer type policy but provides finer control when you need to filter specific routes or prefixes that would have otherwise been discovered and exchanged between BGP neighbors. Route filters are *optional*. Route filters cannot be used to advertise routes that are already filtered based on the peer type.
For the default route advertisement details, see [MCR Route Advertisement](/mcr/route-advertisement).
## Selecting a filter type
You can set a route filter to define which route advertisements MCR permits or denies from BGP neighbors. You can filter routes by BGP connection or by prefix. Route filtering supports IPv4 and/or IPv6 routes for each format. The two filter types are:
* **BGP peer filter** -- An all-or-nothing filter that permits or denies route exchange between BGP neighbors. For example, consider a network deployment with BGP neighbors A, B, and C. A and B are allowed to exchange routes with each other but not with C, while all neighbors can exchange routes with headquarters. BGP peer filtering provides a simple and straightforward way to filter routes between the neighbors to meet these requirements.
* **BGP prefix filter** -- An advanced filter that permits or denies specific routes using route prefixes (IP addresses or ranges) to identify individual neighbors. You can apply the same prefix filter to more than one BGP neighbor, eliminating the need to type manual, redundant prefix entries. You can specify a permit or deny action for each prefix in the filter list. You can apply different lists using import or export directions.
## Before you begin
Before configuring a route filter, plan the implementation by determining your requirements. Then create a route filter based on these requirements.
### Deployment considerations
* You need to create an MCR, as described in [Creating an MCR](/mcr/creating-mcr).
* You can configure route filters before or after configuring BGP, as route filters work on existing or new BGP connections.
* You might want to shut down BGP route exchange if you plan to add several BGP sessions across your Virtual Cross Connects (VXCs) before they exchange route information and route filters are applied. When you are finished configuring, you can then go into the relevant BGP sessions and enable them. For more information, see [Configuring an MCR](/mcr/configuring-mcr).
MCR route filtering supports and relies on the BGP Route Refresh mechanism to update routes using a soft reset when filters change the routing. If Route Refresh is not enabled on all active BGP connections, you need to shut down and re-enable the connection in the Megaport Portal to update routes. If you have enabled the BGP Shut Down option, routes will be updated when you disable BGP Shut Down; that is, re-enable BGP.
## Filtering by BGP peer
By default, MCR permits all routes unless otherwise filtered by the peer type policy, as described in [Default peering route advertisements](/mcr/route-filtering#defaultroutes).
You can configure a policy for each pair of BGP connections configured on the MCR to fine-tune routing. The BGP pairings are unidirectional, meaning that each pair of BGP connections has two policies - one for A to B, and another for B to A.
A BGP peer filter policy has three possible actions:
* **Default** -- Follows the default policy defined by the source peering type BGP connection.
* **Permit** -- Allows routes received from neighbor A to be advertised to neighbor B.
* **Deny** -- Prevents routes received from neighbor A from being advertised to neighbor B.
### BGP peer filter example
BGP connections A, B, and C are connected to the same MCR.
Connection A has a global permit policy. To filter routes toward connection B, the A to B policy can be set to Deny without affecting any routes advertised to C.
Connection C has a global deny policy. To allow routes to be advertised only to A, the C to A policy can be set to Permit. If a new BGP peer is added later, routes from C will follow the global policy and not be advertised.
### Creating a BGP peer filter
A BGP peer filter limits the number of routes that have been advertised or received from BGP neighbors.
**To create a BGP peer filter**
1. Select the VXC attached to the MCR and select A-End.
2. Next to the BGP connection, click **Edit**.
3. Select the **Filters** tab.
4. Under BGP Peer Filter, select whether the routes received by this BGP connection are advertised to BGP peers by default or by exception.
5. Select an action for the BGP peer from the Actions drop-down list:
* **Default** -- Follows the default policy defined by the source peering type BGP connection.
* **Permit** -- Allows routes received from neighbor A to be advertised to neighbor B.
* **Deny** -- Prevents routes received from neighbor A from being advertised to neighbor B.
6. Click **Update**.
7. Click **Save**.
The MCR Looking Glass displays the routes received or sent after applying route filtering. For more information, see [Viewing Traffic Routing Through MCR Looking Glass](/mcr/mcr-looking-glass).
## Filtering by BGP prefix
A prefix is the destination network of the route. An IP network is a group of IP addresses. The network address is the prefix.\
For example:
* IPv4 address: 192.0.2.1
* IPv4 network prefix: 192.0.2.0/24 (includes 192.0.2.0 - 192.0.2.255)
A *prefix filter* is a named list of IP networks. Each entry consists of an IPv4 or IPv6 CIDR prefix or range of prefixes that you define and manage. A CIDR range means that you can filter several networks using a single routing entry.
A prefix filter can be applied to a BGP connection to selectively identify routes to advertise or receive from neighboring routers. You can also make a list of routes *not* to advertise or receive, allowing everything else. When you define a prefix filter, the MCR accepts only routes matching the prefix information. This filter type is useful in environments with a large list of prefixes and peers to manage. You can apply the same prefix filter to more than one BGP peer, reducing manual work and eliminating potential errors.
A prefix filter contains:
* A list of IPv4 or IPv6 prefixes (for example, 10.0.0.0/16) and a name associated with the list.
* A match condition. You can specify exact matches with specific routes or less precise matches based on prefix length.
* An action that is carried out if the prefix and the match condition are both true (for example, Permit).
In a prefix filter, rules are evaluated from the top down. Evaluation stops with the first match. An implicit deny is applied to routes that don't match any prefix list entry.
### Prefix filter list actions
* **Inbound prefix filtering using a permit action** -- MCR applies the prefix filter to inbound BGP route advertisements from the neighbor. Routes not matching the prefixes on this list are denied at the earliest possible point and are never used by the MCR.
* **Inbound prefix filtering using a deny action** -- MCR applies the prefix filter to inbound BGP route advertisements from the neighbor. Routes matching the prefixes on this list are blocked. All other prefixes are allowed to enter the MCR routing table.
* **Outbound prefix filtering using a permit action** -- MCR applies the prefix filter to outbound routes. Routes matching the prefix list are advertised to the BGP neighbor and all other routes are filtered.
* **Outbound prefix filtering using a deny action** -- MCR applies the prefix filter to outbound routes. Routes matching the prefix list are blocked from the BGP neighbor and all other routes are advertised.
### Creating a BGP prefix filter
Each MCR can manage up to 50 prefix filters. Each prefix filter can contain up to 200 prefix entries.
Each prefix filter is independent and you can apply only one list per BGP neighbor at a time.
**To create a prefix filter**
1. On the Megaport Portal Services page, select an MCR.\
The MCR must have a Live status before you can create a prefix filter.\
The MCR Details page appears.
2. Under MCR Configuration, select the **Prefix Filter Lists** tab.
3. Click **New List**.
4. Enter a unique descriptive name to identify the filter. The minimum description length is from 1 to 100 characters.\
This prefix name will appear in the drop-down list of prefix lists under the Filters section of the BGP Configuration tab.
Prefix filters cannot be shared among MCRs. You must re-create prefix filters for each MCR.
5. Select either IPv4 or IPv6 format.\
The prefixes must use the same address format. A warning appears if you try to mix the two formats within the same list.
6. Select a position for the rule.\
The rule position is critical because evaluation stops with the first match and the rest of the list is ignored. If no conditions match, MCR applies an implicit deny.
7. Select the action to take for the filter: Match or Don't Match.
8. Enter the prefix subnets in CIDR notation. For IPv4, use a.b.c.d/x, where *a.b.c.d* is the exact prefix and *x* is the exact prefix length.
This field also accepts a dotted-quad notation for the subnet mask (for example, 255.255.255.0 instead of /24).
9. Prefixes can be exact-match-only or you can specify the number of bits in the mask to use as matching criteria. Select the subnet mask criteria:
* **Exact** -- Limits the filter to only this specific prefix. Any smaller prefixes contained within the prefix are not matched.
* **Min and Max** -- Specify a range of subnet mask lengths to match for more flexibility. Specify how many bits of the subnet mask the filter needs to match, starting with the most significant bit in the leftmost position of the address. When you specify a subnet mask range, the filter now has two conditions to match: the route must be within the a.b.c.d/x boundary and it must have a mask length between the minimum and maximum range. Shorter prefixes match more addresses, while longer prefixes match fewer.
* **Min** -- The minimum starting prefix length to be matched. Valid values are from 0 to 32 (IPv4), or 0 to 128 (IPv6). The Min must be no greater than or equal to the Max value.
* **Max** -- The maximum ending prefix length to be matched. The prefix length is greater than or equal to the Min value. Valid values are from 0 to 32 (IPv4), or 0 to 128 (IPv6), but the Max must be no less than the value of Min.
For example, 10.0.0.0/8 Min 16 matches 10.0.0.0/16, 10.0.1.0/24, 10.0.0.1/30 but does not match 10.2.0.0/15.
The Min and Max values on an MCR are similar to Cisco's **ge** and **le** values used with the **ip prefix-list** CLI command.
When using the Min and Max values, you must satisfy this condition:
Prefix length \<= Max \<= Min
10. Click **Save**.
11. Click **Next**.
Use a CIDR calculator to ensure that all data is valid and within range.
The next step is to apply the filter to the BGP connection, as described in [Applying a prefix filter to a BGP connection](#applyprefixfilter).
#### Example filter entries
* Exact match on 1.2.3.0/24 -- exactly matches the prefix 1.2.3.0 with a subnet mask of 255.255.255.0
* Match 192.2.3.0/24 min 32 -- checks the first 24 bits of the prefix 192.2.3.0 that have a subnet mask of 32
* Match 10.0.12.0/24 max 32 -- matches all 10.0.12.*x* networks that have a subnet mask less than or equal to 32
### Creating a prefix filter based on an existing prefix filter
If you want to create a filter that is similar to an existing filter, you can use the existing filter as the basis for the new one. This saves you the time of creating a new filter from scratch.
**To create a prefix filter based on an existing filter**
1. Select an MCR.\
The MCR Details page appears.
2. Under MCR Configuration, select the **Prefix Filter Lists** tab.
3. Select the filter list on which you want to base the new list.
4. Click **Duplicate List**.
5. Enter a unique descriptive name to identify the filter.\
This prefix name will appear in the drop-down list of prefix lists in the Filters tab of the BGP Configuration screen.
6. Make any changes to the parameters unique to this filter.
7. Click **Save**.
8. Click **Next**.
### Applying a prefix filter to a BGP connection
Prefix filters are configured directly on MCR and then attached to a BGP connection.
**To apply a prefix filter**
1. Select the VXC attached to the MCR, then select A-End.
2. Next to the BGP connection, click **Edit**.
3. Select the **Filters** tab.
4. Under BGP Prefix Filter, you can apply an import filter and an export filter:
* **Import** -- The MCR applies the prefix filter to inbound advertisements from the neighbor.
* **Export** -- The MCR applies the prefix filter to outbound advertisements to the neighbor.
Select whether the filter will limit the set of routes that the MCR will receive from, or advertise to the peer. These options are available:
* **No Prefix Filter** -- Allows all routes. No routes will be filtered.
* **Permit List** -- Allows only routes that match the prefix list. Other routes will be filtered.
* **Deny List** -- Allows all routes except those that match the selected prefix list.
5. Select the prefix filter you want to apply from the drop-down list.
6. Click **Update**.
7. Click **Save**.
After applying the filter, re-enable route exchange if it is disabled. For more information, see [Editing an MCR](/mcr/configuring-mcr#editmcr).
A prefix filter can be attached to more than one BGP session.
## Maintaining prefix filters
In a prefix filter list, rules can be added, deleted, and reordered.
### Adding a rule to an existing prefix filter
Each prefix filter can contain up to 200 rules. Duplicate rules are not allowed.
**To add a rule to an existing filter**
1. Select an MCR on the Services page.\
The MCR Details page appears.
2. Under MCR Configuration, select the **Prefix Filter Lists** tab.
3. Select a prefix list from the Prefix Filter List drop-down list.
4. Add the rule.
5. Click **Save**.\
You must click **Save** to apply rule changes. Switching to another list without saving prompts a warning that the changes will be lost.
### Deleting a rule from a prefix filter
**To delete a rule from a filter**
1. Select an MCR on the Services page.\
The MCR Details page appears.
2. Under MCR Configuration, select the **Prefix Filter Lists** tab.
3. Select a prefix list from the Prefix Filter List drop-down list.
4. Select a rule.
5. Click **Delete**.
6. Click **Save**.
### Reordering rules in a prefix filter
In a prefix filter list, the rule position is critical because rules are evaluated one at a time, starting at the top of the list down. Evaluation stops with the first match.
**To reorder a rule position**
* Drag the icon in the Position column to a different location and release.
### Deleting a prefix filter list
To delete a prefix filter list, you must first remove any other resources that reference it, such as VXCs. If you try to delete a prefix filter list before removing its resources, a dialog lists the resources in use.
All prefix lists are automatically removed from an MCR when it is terminated.
**To delete a prefix filter**
1. Select an MCR on the Services page.\
The MCR Details page appears.
2. Under MCR Configuration, select the **Prefix Filter Lists** tab.
3. Select a prefix list from the Prefix Filter List drop-down list.
4. Click **Delete List**.
5. Click **Save**.
## Validating routes after applying filters
The MCR Looking Glass displays the routes received or sent after applying route filtering.
For more information, see [Viewing Traffic Routing Through MCR Looking Glass](/mcr/mcr-looking-glass).
**To view the routes after applying a route filter**
1. Choose Tools > MCR/NAT Gateway Looking Glass.
2. Select an MCR from the MCR drop-down list.
3. Next to the VXC, click **Neighbour Routes**.
4. Next to Show, select the **Advertised** or **Received** tabs to narrow the list.
# MCR Route Summarization
Source: https://docs.megaport.com/mcr/route-summarization
This help topic describes how you can achieve a similar outcome to route summarization on MCR.
This topic describes how you can achieve a similar outcome to route summarization on MCR using a combination of static routes and filtering. This will help avoid the situation where CSP limits are being reached due to the number of routes being advertised.
This image shows how route summarization could be configured, with the customer-facing VXC originating several prefixes but where you want to advertise only a summary route to the CSP.
If you configure a static on the VXC facing the source of the smaller networks, this will cause the MCR to also advertise the supernet to the CSP. You can then use prefix filters to not advertise the specifics to the CSP which will achieve approximately the same behavior as route summarization.
## Helpful references
* [Creating an MCR VXC](/mcr/mcr-vxc)
* [Filtering by BGP prefix](/mcr/route-filtering#bgpprefixfilter)
* [Introduction to Route Summarization](https://networklessons.com/rip/introduction-route-summarization)
* [Route Summarization](https://networklessons.com/subnetting/route-summarization)
# Terminating an MCR
Source: https://docs.megaport.com/mcr/terminating-mcr
This help topic describes how to terminate an MCR directly from the Megaport Portal.
You can terminate an MCR directly from the Megaport Portal. Terminating an MCR on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MCR contract terms, see [MCR Pricing and Contract Terms](/finance/mcr-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate an MCR**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MCR you want to terminate.
The Terminate Services window appears. Early termination fees will be shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MCR. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MCR termination, or click **No, Keep Services** to cancel.\
The MCR and its associated VXCs are deleted from the Megaport network.
# Welcome to the Megaport Documentation
Source: https://docs.megaport.com/megaport/index
Click a tile for popular categories, search to find a specific topic, or use the side navigation to explore category details.
Latest platform updates and changes.
Set up your account and first service.
Explore Megaport's portfolio of networking products.
Private links to AWS, Azure and more.
Protect data in transit with MACsec and IPsec.
Automate services with the API, Terraform, and AI tools.
Manage your account, pricing, and billing settings.
Diagnose and resolve common connectivity issues.
Get help from the Megaport support team.
# 6WIND Licensed Network Functions
Source: https://docs.megaport.com/mve/6wind/6wind-network-functions
This help topic describes the different licensed network functions available with 6WIND VSR.
6WIND VSR with Megaport's MVE offers four distinct licensed network functions:
* **Virtual Border Router (vBR)** -- The Border Router product facilitates efficient interconnection between different network segments especially in geographically dispersed areas, with hyperscalers, or connectivity to Internet Exchange services, or upstream service providers. It ensures that data traffic is routed efficiently, reducing latency and improving overall network performance. For more information, see the [6WIND vBR Datasheet](https://media.megaport.com/docs/pdf/6wind/6wind-mega-virtual-border-router.pdf).
* **Virtual Carrier Grade Network Address Translation (vCGNAT)** -- As IPv4 addresses become increasingly scarce, the vCGNAT router plays a vital role in extending the life of these addresses by allowing multiple users to share a single public IP address. This not only ensures seamless service continuity but also enhances network security by hiding internal IP addresses from external threats. 6WIND vCGNAT supports NAT44 (Ipv4 to IPv4) and NAT64 (IPv6 to IPv4) with DNS64 (DNS conversion from IPv4 to IPv6). For more information, see the [6WIND vCGNAT Datasheet](https://media.megaport.com/docs/pdf/6wind/6wind-mega-virtual-carrier-grade-nat.pdf).
* **Virtual Security Gateway (vSecGW)** -- Virtualized Security Gateway (vSecGW) provides comprehensive, highly scalable and network-integrated Layer 3 IPsec-based VPN connectivity. The vSecGW functionality can be applied to any type of network traffic in fixed, wireless, and converged environments. This allows either site to site IPsec services, or to act as a VPN concentrator for remote user connectivity to Megaport services. For more information, see the [6WIND vSecGW Datasheet](https://media.megaport.com/docs/pdf/6wind/6wind-mega-virtual-security-gateway.pdf).
* **Virtual L3/L4 Firewall (vFW)** -- The vFW product offers robust protection against a wide range of cyber threats, ensuring that the network remains secure without compromising performance.
With advanced filtering and monitoring capabilities, the Firewall helps operators and enterprises meet stringent regulatory requirements while safeguarding customer and/or internal data. For more information, see the [6WIND vFW Datasheet](https://media.megaport.com/docs/pdf/6wind/6wind-mega-virtual-firewall.pdf).
# Connecting MVEs Integrated with 6WIND
Source: https://docs.megaport.com/mve/6wind/connect-mve-to-mve
This help topic describes how to connect two Megaport Virtual Edges (MVEs) integrated with 6WIND.
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with 6WIND to another MVE.
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer / partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [Creating an MVE Integrated with 6WIND](/mve/6wind/creating-mve-6wind).
## Creating a VXC between two MVEs
A private VXC deployment between two MVEs integrated with 6WIND starts in the Megaport Portal. To complete the configuration, you use the 6WIND command line interface (CLI).
**To create a VXC**
1. In the Megaport Portal, go to the
**Services** page and click **+Connection** next to the originating A-End MVE.
2. Select Private VXC.
3. Select the destination B-End MVE and location.\
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `Dallas MVE 4 to LA MVE 2`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. For more information, see the 6WIND documentation.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **vNIC selection** -- Depending on the definition of the MVEs you are using, you might have to specify A-End and B-End vNICs.
* **A-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
* **B-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
For more information about vNIC selection when connecting MVEs with different services, see [Types of vNIC Connections](/mve/vnic-connections).
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.\
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. 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 through the B-End VLAN.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Click **Add VXC** to move this configuration to your cart.
8. Repeat these steps to provision any additional VXCs.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs on the 6WIND side. For more information about specific network design and configuration options before configuring interfaces for the MVEs, see the [6WIND Documentation](https://doc.6wind.com/turbo-router-3.x/index.html).
# Creating an MVE Integrated with 6WIND
Source: https://docs.megaport.com/mve/6wind/creating-mve-6wind
This help topic describes how to create and configure Megaport Virtual Edge (MVE) with 6WIND.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with 6WIND.
For information on the 6WIND-specific settings, see [6WIND - Virtual Service Router](https://doc.6wind.com/turbo-router-3.x/index.html).
## Basic steps
This section summarizes the configuration steps using the Megaport Portal. Detailed procedures follow this basic step summary.
The basic steps are:
* Obtain a license from 6WIND.
* Generate an SSH key pair for authentication.
* Create the 6WIND MVE in the Megaport Portal.
* Ensure that the connection has been established on the 6WIND CLI.
## Licensing
Before you create an MVE in the Megaport Portal, you need a valid 6WIND license (EVAL or Production).
To request an evaluation license key from 6WIND, raise your request through the [6WIND VSR evaluation page](https://portal.6wind.com/mve-register.php), fill in the form and select the product of interest. Alternatively, for more information about obtaining a 6WIND license, contact your 6WIND Sales Associate or Reseller, or your Megaport Sales Representative for guidance.
The next step is to generate an SSH key pair for authentication.
## Administrative access to MVE
MVE Console access from the Megaport Portal is not available for 6WIND VSR. Internet connectivity is required to access and manage your 6WIND MVE, so make sure you plan to provision internet connectivity (a Megaport Internet connection or a third-party internet connection) as part of your deployment.
You connect your MVE through a public/private SSH key pair to establish a secure connection. The public SSH key allows you to use SSH to access the MVE and perform administrative tasks, such as setting the administrative password, enabling HTTPS access, and optionally registering the MVE to your management platform.
Megaport supports the 2048-bit RSA key type.
**To generate an SSH key pair (Linux/Mac OSX)**
* Enter the SSH keygen command in the terminal.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ssh-keygen -f ~/.ssh/megaport-mve-instance-1-2048 -t rsa -b 2048
```
The key generator command creates an SSH key pair and adds two files to your \~/.ssh directory:
* **megaport-mve-instance-1-2048** - contains the private key.
* **megaport-mve-instance-1-2048.pub** - contains the public key that is authorized to log in to the vendor account.
**To generate an SSH key pair (Windows, using [PuTTYgen](https://www.puttygen.com))**
1. Open PuTTYgen.
2. In the Key section, choose RSA 2048 bit and click **Generate**.
3. Move your mouse randomly in the small screen to generate the key pairs.
4. Enter a key comment to identify the key.\
This is convenient when you use several SSH keys.
5. Enter a Key passphrase, and re-enter to confirm.\
The passphrase is used to protect your key. You will be asked for it when you connect via SSH.
6. Click **Save private key**, choose a location, and click **Save**.
7. Click **Save public key**, choose a location, and click **Save**.
You will copy and paste the contents of the public key file in the Megaport Portal later to distribute the public key to the MVE. Your private key will match the public key to grant access. Only a single private key has access to the MVE for SSH access.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/6wind/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also typically create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **6WIND VSR**.
4. Select the software version.
The MVE will be configured to be compatible with that version of 6WIND.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the 6WIND-specific settings:
* **SSH Key** -- Copy and paste the contents of your public SSH key here. You can find the public key in the **megaport-mve-instance-1-2048.pub** file generated earlier.
* **Virtual Interfaces (vNICs)** -- Each MVE is configured with one vNIC named *Data Plane* by default. To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed.
You can add a total of five vNICs to the MVE, including the one added by default. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Enter a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with 6WIND.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
MVE Console access from the Megaport Portal is not available for 6WIND VSR. This makes internet connectivity mandatory for 6WIND, not just recommended. If you click **Not now**, you will not be able to access or manage your 6WIND MVE until you provision internet connectivity. For more information, see [Console Access button is disabled](/mve/console-access#console-access-button-is-disabled).
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select **vNIC-0** for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up a 6WIND VSR.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/6wind/creating-mve-vxc).
# Creating a VXC to an MVE Integrated with 6WIND VSR
Source: https://docs.megaport.com/mve/6wind/creating-mve-vxc
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE) integrated with 6WIND.
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with 6WIND.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.\
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
For specific configuration details, see [Connecting MVE to MVE](/mve/6wind/connect-mve-to-mve).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/6wind/terminating-mve).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# 6WIND with Megaport Virtual Edge
Source: https://docs.megaport.com/mve/6wind/index
This help topic describes 6WIND with Megaport MVE functionality.
The integration of 6WIND and its Virtual Service Router (VSR) with Megaport's MVE delivers secure, high-performance multicloud and hybrid cloud connectivity, allowing you to connect, secure, and easily manage your cloud environments. For more information, see the [6WIND VSR Datasheet](https://media.megaport.com/docs/pdf/6wind/6wind-mega-virtual-service-router.pdf).
6WIND provides an overlay network and manages the network connections, routing, and network policies. You use the Megaport Portal to create and order the MVE and create and manage the Virtual Cross Connects (VXCs) to the cloud on-ramps and other services in the Megaport SDN. The 6WIND fabric acts as the overlay, and the Megaport SDN acts as the underlay.
For more information, see [6WIND Licensed Network Functions](/mve/6wind/6wind-network-functions).
The following diagram shows an example network implementation of 6WIND features over the Megaport network.
# Planning Your 6WIND Deployment
Source: https://docs.megaport.com/mve/6wind/plan-deployment
This help topic describes 6WIND deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
| **You Provide** | **Megaport Provides** |
| - | - |
| Internet connection from branch | Platform to host virtual 6WIND Virtual Service Router (VSR) appliances |
| Network and Security vendor enabled at branch | Complete connection from a branch to any destination on the Megaport network and interoperation with other Megaport products and services |
| Customer premises equipment (CPE) installed in branch | Megaport Internet connection to terminate the tunnel between MVE and CPE at branch via internet |
| 6WIND software license to use on Megaport SDN | Access to the Megaport ecosystem |
## Deployment considerations
This section provides an overview of the MVE deployment options and features.
For information about the 6WIND-specific settings, see [6WIND - Virtual Service Router](https://doc.6wind.com/turbo-router-3.x/index.html).
### Network and Security vendors
MVE is integrated with 6WIND Virtual Service Router (VSR), which uses the 6WIND command line interface (CLI) and/or the Netconf API to create the private overlay network.
For information about all supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### Console access
MVE Console access from the Megaport Portal is not available for 6WIND VSR. Plan to provision internet connectivity (either a Megaport Internet connection or a third-party internet connection using a private VXC) as part of your deployment, as this is required to access and manage your 6WIND MVE. For more information, see [Console Access button is disabled](/mve/console-access#console-access-button-is-disabled).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **6WIND VSR**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* If your MVE compute still has capacity, you can upgrade your 6WIND license in terms of network throughput and function components, for example, IPsec tunnels, NAT connections, and so on. Contact your 6WIND Sales Representative directly.
* You can provision another MVE instance, add it to your overlay network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, add it to your overlay network, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### 6WIND VSR performance matrix
This table summarizes the matrix of performance expected for each of the 6WIND VSR network functions in relation to each of the MVE sizes.
| **MVE Sizes / VSR Functions** | **Virtual Border Router (vBR)** | **Virtual L3/L4 Firewall (vFW)** | **Virtual Carrier Grade NAT (vCGNAT)** | **Virtual Security Gateway (vSecGW)** |
| - | - | - | - | - |
| 2 CPU / 8 GB RAM | Up to: 1M Routes | Up to: 100K CPS | Up to: 100K CPS 5M sessions | Up to: 25K IPsec tunnels |
| 4 CPU / 16 GB RAM | Up to: 2M Routes | Up to: \~250K CPS | Up to: \~250K CPS 15M sessions | Up to: 50K IPsec tunnels |
| 8 CPU / 32 GB RAM | Up to: 4M Routes | Up to: \~600K CPS | Up to: \~600K CPS 30M sessions | Up to: 100K IPsec tunnels |
| 16 CPU / 64 GB RAM | Up to: 6M Routes | Up to: \~1M CPS | Up to: \~1M CPS 50M sessions | Up to: 150K IPsec tunnels |
| 32 CPU / 128 GB RAM | Up to: 8M Routes | Up to: \~1.5M CPS | Up to: \~1.5M CPS 80M sessions | Up to: 250K IPsec tunnels |
The default 6WIND VSR option requires 2 CPU cores (one for the control plane and one for the data plane) and 2 GB RAM. Depending on the selected network function and the expected performance outcome, additional CPU cores and RAM are associated with the VSR. These figures consider 1 CPU core for the control plane and the rest for the data plane.
### Security
MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN.
### Licensing
Before you create an MVE in the Megaport Portal, you need user accounts with ordering permissions that provide access to the Megaport Portal. For more information, see [Creating an Account](/setting-up/registering).
In addition, you need a valid license from 6WIND. To request an evaluation license key, raise your request through the [6WIND VSR evaluation page](https://portal.6wind.com/mve-register.php), fill in the form and select the product of interest. Alternatively, for more information about obtaining a 6WIND license, contact your 6WIND Sales Associate or Reseller, or your Megaport Sales Representative for guidance.
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
### vNICs
Each MVE can have up to five vNICs. An MVE is created with one vNIC by default. You can add up to four more, making a total of five.
Before specifying the number of vNICs on your MVE:
* Be aware that the number of vNICs cannot be changed after an MVE has been ordered. Decide in advance how many vNICs to specify when you create the MVE.
* Consult your service provider to make sure that functionality won't be affected if you add a vNIC.
If you need to change the number of vNICs after an MVE has been ordered, you will have to cancel and re-order the MVE.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
# Terminating an MVE
Source: https://docs.megaport.com/mve/6wind/terminating-mve
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
Before terminating the MVE, release the 6WIND production license in the 6WIND licensing portal to be able to re-use it. See the [6WIND documentation](https://doc.6wind.com/turbo-router-3.x/index.html) for more information about releasing the license for further use. Alternatively, via the 6WIND CLI, enter edit running mode, then enter:
`System license enabled false `
`Commit `
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window appears, displaying a list of services connected to the MVE. Early termination fees are shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use your SD-WAN management console to delete the MVE.
# Connecting MVEs Integrated with Anapaya
Source: https://docs.megaport.com/mve/anapaya/connect-mve-to-mve
This help topic describes how to connect two Megaport Virtual Edges (MVEs) integrated with Anapaya.
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with Anapaya to another MVE.
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer / partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [Creating an MVE Integrated with Anapaya](/mve/anapaya/creating-mve-anapaya).
## Creating a VXC between two MVEs
A private VXC deployment between two MVEs integrated with Anapaya starts in the Megaport Portal. To complete the configuration, you use the Anapaya console.
**To create a VXC**
1. In the Megaport Portal, go to the
**Services** page and click **+Connection** next to the originating A-End MVE.
2. Select Private VXC.
3. Select the destination B-End MVE and location.\
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `Dallas MVE 4 to LA MVE 2`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. For more information, see the Anapaya documentation.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **vNIC selection** -- Depending on the definition of the MVEs you are using, you might have to specify A-End and B-End vNICs.
* **A-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
* **B-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
For more information about vNIC selection when connecting MVEs with different services, see [Types of vNIC Connections](/mve/vnic-connections).
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.\
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. 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 through the B-End VLAN.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Click **Add VXC** to move this configuration to your cart.
8. Repeat these steps to provision any additional VXCs.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs on the Anapaya side. For more information about specific network design and configuration options before configuring interfaces for the MVEs, see the [Anapaya Configuration](https://learn.anapaya.net/docs/technical-documentation/anapaya-appliance/configuration/).
# Creating an MVE Integrated with Anapaya
Source: https://docs.megaport.com/mve/anapaya/creating-mve-anapaya
This help topic describes how to create and configure Megaport Virtual Edge (MVE) with Anapaya.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Anapaya.
When you create an Anapaya MVE in the Megaport Portal, the instance is deployed using a single Anapaya VM image. You configure the appliance role as EDGE, CORE, or GATE through the Anapaya management console, depending on your license and deployment requirements.
For more information, see:
* [Introducing SCION with Anapaya and Megaport](https://www.megaport.com/blog/introducing-scion-with-anapaya-and-megaport/)
* [Anapaya EDGE/CORE/GATE appliance](https://learn.anapaya.net/docs/technical-documentation/anapaya-appliance/)
## Basic steps
This section summarizes the configuration steps using the Megaport Portal. Detailed procedures follow this basic step summary.
The basic steps are:
* Obtain a license from Anapaya.
* Generate an SSH key pair for authentication.
* Create the Anapaya MVE in the Megaport Portal.
* Ensure that the connection has been established on the Anapaya appliance.
## Licensing
Before you create an MVE in the Megaport Portal, you need a valid Anapaya license.
To obtain or manage an Anapaya license, see [Anapaya EDGE/CORE/GATE appliance](https://learn.anapaya.net/docs/technical-documentation/anapaya-appliance/) or contact your Megaport Sales Representative for guidance.
The next step is to generate an SSH key pair for authentication.
## Administrative access to MVE
You connect your MVE through a public/private SSH key pair to establish a secure connection. The public SSH key allows you to use SSH to access the MVE and perform administrative tasks, such as setting the administrative password, enabling HTTPS access, and optionally registering the MVE to your management platform.
Megaport supports the 2048-bit RSA key type.
**To generate an SSH key pair (Linux/Mac OSX)**
* Enter the SSH keygen command in the terminal.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ssh-keygen -f ~/.ssh/megaport-mve-instance-1-2048 -t rsa -b 2048
```
The key generator command creates an SSH key pair and adds two files to your \~/.ssh directory:
* **megaport-mve-instance-1-2048** - contains the private key.
* **megaport-mve-instance-1-2048.pub** - contains the public key that is authorized to log in to the vendor account.
**To generate an SSH key pair (Windows, using [PuTTYgen](https://www.puttygen.com))**
1. Open PuTTYgen.
2. In the Key section, choose RSA 2048 bit and click **Generate**.
3. Move your mouse randomly in the small screen to generate the key pairs.
4. Enter a key comment to identify the key.\
This is convenient when you use several SSH keys.
5. Enter a Key passphrase, and re-enter to confirm.\
The passphrase is used to protect your key. You will be asked for it when you connect via SSH.
6. Click **Save private key**, choose a location, and click **Save**.
7. Click **Save public key**, choose a location, and click **Save**.
You will copy and paste the contents of the public key file in the Megaport Portal later to distribute the public key to the MVE. Your private key will match the public key to grant access. Only a single private key has access to the MVE for SSH access.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/anapaya/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also typically create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Anapaya Appliance**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Anapaya.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Anapaya-specific settings:
* **SSH Key** -- Copy and paste the contents of your public SSH key here. You can find the public key in the **megaport-mve-instance-1-2048.pub** file generated earlier.
* **Virtual Interfaces (vNICs)** -- Each MVE is configured with one vNIC named *Management* by default. To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed.
You can add a total of five vNICs to the MVE, including the one added by default. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Enter a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with Anapaya. The overlay network is created and maintained by Anapaya to provide secure connectivity between branch locations and cloud/data center endpoints.
After creating the MVE in the Megaport Portal, configure the Anapaya appliance using the Anapaya management console.
Once the appliance is configured, you must obtain an Autonomous System (AS) certificate for each configured appliance. The AS certificate is required for the appliance to join the selected Isolation Domain (ISD) within the SCION network.
For more information about:
* configuring the Anapaya appliance, see [Anapaya EDGE/CORE/GATE appliance](https://learn.anapaya.net/docs/technical-documentation/anapaya-appliance/).
* obtaining the AS certificate based on the ISD you are joining, see [SCION AS Onboarding](https://learn.anapaya.net/docs/academy/processes/isd-as-onboarding/).
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select **vNIC-0** for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up an Anapaya instance.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/anapaya/creating-mve-vxc).
# Creating a VXC to an MVE Integrated with Anapaya Appliance
Source: https://docs.megaport.com/mve/anapaya/creating-mve-vxc
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE) integrated with Anapaya.
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with Anapaya.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.\
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
For specific configuration details, see [Connecting MVE to MVE](/mve/anapaya/connect-mve-to-mve).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/anapaya/terminating-mve).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# Anapaya with Megaport Virtual Edge
Source: https://docs.megaport.com/mve/anapaya/index
This help topic describes Anapaya with Megaport Virtual Edge (MVE) functionality.
The Anapaya platform is built on the SCION (Scalability, Control, and Isolation On Next-Generation Networks) Internet architecture, delivering secure, high-performance business data transfer with enhanced control and availability for critical applications and cloud environments.
Integrating Anapaya with Megaport's MVE extends these capabilities to enterprises using Megaport’s global private SDN. Megaport provides the network underlay, while Anapaya manages routing policies, and secure communications across clouds, ISPs, and data centers. You use the Megaport Portal to create and order MVE instances and establish Virtual Cross Connects (VXCs) to cloud on-ramps and other services, with Anapaya delivering the overlay for policy-based, resilient, and secure connectivity.
This documentation assumes you have working knowledge of SCION and a basic understanding of Anapaya appliances and deployment architectures.
When you create an Anapaya MVE in the Megaport Portal, the instance is deployed using a single Anapaya VM image. You configure the appliance role as EDGE, CORE, or GATE through the Anapaya management console, depending on your license and deployment requirements.
For more information, see:
* [Introducing SCION with Anapaya and Megaport](https://www.megaport.com/blog/introducing-scion-with-anapaya-and-megaport/)
* [Anapaya EDGE/CORE/GATE appliance](https://learn.anapaya.net/docs/technical-documentation/anapaya-appliance/)
* [AS Numbers and Certificates](https://learn.anapaya.net/docs/technical-documentation/anapaya-appliance/getting-started/as-registration/)
The following diagram shows an example network implementation of Anapaya features over the Megaport network.
# Planning Your Anapaya Deployment
Source: https://docs.megaport.com/mve/anapaya/plan-deployment
This help topic describes Anapaya deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
Before deploying Anapaya, contact the SCION access provider that the EDGE will connect to. For more information about available SCION access providers, contact your Anapaya representative or see the [Anapaya website](https://www.anapaya.net/).
| **You Provide** | **Megaport Provides** |
| - | - |
| Internet connection from branch | Platform to host virtual security instances |
| Anapaya deployed at branch | Complete connection from a branch to any destination on the Megaport network and interoperation with other Megaport products and services |
| Customer premises equipment (CPE) installed in branch | Megaport Internet connection to terminate the tunnel between MVE and CPE at branch via internet |
| Anapaya software license to use on Megaport SDN | Access to the Megaport ecosystem |
## Deployment considerations
This section provides an overview of the MVE deployment options and features.
### Network and Security Vendors
MVE integrates with Anapaya to deliver secure, SCION-based connectivity with path control and high availability between your network and cloud environments.
For more information about supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Anapaya Appliance**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* You can provision another MVE instance, add it to your overlay network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, add it to your overlay network, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### Security
MVE provides secure connectivity between your branch locations and cloud or data center destinations via the Megaport SDN. Anapaya instances hosted on MVE enable SCION-based traffic forwarding with security, resilience, and multipath capabilities across Megaport’s private network backbone. Traffic stays encrypted and policy-enforced from edge to destination.
### Licensing
Before creating an MVE in the Megaport Portal, ensure that your user account has ordering permissions. For more information, see [Creating an Account](/setting-up/registering).
You also need a valid Anapaya license. To obtain or manage an Anapaya license, see the [Anapaya website](https://www.anapaya.net/).
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
### vNICs
Each MVE can have up to five vNICs. An MVE is created with one vNIC by default. You can add up to four more, making a total of five.
Before specifying the number of vNICs on your MVE:
* Be aware that the number of vNICs cannot be changed after an MVE has been ordered. Decide in advance how many vNICs to specify when you create the MVE.
* Consult your service provider to make sure that functionality won't be affected if you add a vNIC.
If you need to change the number of vNICs after an MVE has been ordered, you will have to cancel and re-order the MVE.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
# Terminating an MVE
Source: https://docs.megaport.com/mve/anapaya/terminating-mve
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window appears, displaying a list of services connected to the MVE. Early termination fees are shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use your Anapaya management console to delete the MVE.
Ensure that you also terminate the Anapaya software license for the MVE using the Anapaya management console.
# Aruba EdgeConnect SD-WAN with Megaport Virtual Edge
Source: https://docs.megaport.com/mve/aruba/index
This help topic describes Aruba EdgeConnect SD-WAN with Megaport MVE functionality.
Aruba EdgeConnect SD-WAN creates the private overlay network and manages the network connections and network policies. You use the Megaport Portal to create and order the MVE and create and manage the Virtual Cross Connects (VXCs) to the cloud on-ramps and other services in the Megaport SDN. The Aruba SD-WAN fabric acts as the overlay, and the Megaport SDN acts as the underlay.
TCP throughput issues caused by NIC driver settings have been fixed in EdgeConnect versions 9.1.4.1 and later and 9.2.2.0 and later.
The following diagram shows an example network implementation of Aruba EdgeConnect SD-WAN features over the Megaport network.
# MVE Overview
Source: https://docs.megaport.com/mve/index
This help topic describes Megaport Virtual Edge (MVE) functionality.
MVE is a globally distributed virtual network service designed to simplify and enhance network connectivity.
By integrating with Megaport’s private software-defined network (SDN), MVE enables virtual network functions including next-generation firewall (NGFW), software-defined wide area network (SD-WAN) gateways, virtual router, and EDGE, CORE, and GATE nodes, through a single and intuitive platform. Megaport MVE supports a number of leading vendors.
Key benefits of MVE are:
* **Dynamic network extension** -- Enables flexible and on-demand expansion of network infrastructure.
* **Scalable connectivity** -- Supports varying and growing traffic demands across different locations.
* **Secure connections** -- Delivers reliable and protected communication between branches, data centers, and clouds.
* **Hardware reduction** -- Eliminates the need for physical network hardware and simplifies deployment and management.
For more information, see
[Megaport Virtual Edge](https://www.megaport.com/products/megaport-virtual-edge/).
MVE is integrated with these providers:
* [6WIND Virtual Service Router (VSR)](/mve/6wind)
* [Anapaya](/mve/anapaya)
* [Aruba EdgeConnect SD-WAN](/mve/aruba)
* [Arista VeloCloud SD-WAN](/mve/vmware)
* [Aviatrix Secure Edge](/mve/aviatrix)
* [Check Point CloudGuard](/mve/checkpoint)
* [Cisco](/mve/cisco)
* [Deciso OPNsense](/mve/deciso)
* [F5 BIG-IP Virtual Edition](/mve/f5)
* [Fortinet FortiGate](/mve/fortinet)
* [Juniper](/mve/juniper)
* [Netskope One SD-WAN](/mve/netskope)
* [Palo Alto Networks Prisma SD-WAN](/mve/palo-alto/prisma)
* [Palo Alto Networks VM-Series NGFW](/mve/palo-alto)
* [Peplink FusionHub](/mve/peplink)
* [Versa Secure SD-WAN](/mve/versa)
## Virtual Firewall as a Service (FWaaS) with MVE
MVE is a cloud-based security solution that delivers firewall capabilities as a service. You can deploy NGFW using Fortinet, Palo Alto, and Cisco.
Key benefits of MVE FWaaS:
* **Dynamic deployment** -- Firewalls can be deployed flexibly and strategically.
* **Consistent security** -- A uniform, distributed security posture across all locations.
* **Secure connectivity** -- Fast and secure data flow between clouds, branches, and remote sites.
* **Hardware reduction** -- Eliminates the need for physical firewall appliances.
* **Simplified management** -- Streamlines firewall, network, and internet management.
* **Flexible licensing** -- Supports Bring Your Own License (BYOL) for firewalls.
* **Advanced security features** -- Includes intrusion prevention, deep packet inspection, and secure web filtering.
### Use cases of FWaaS with MVE
Cloud and hybrid security:
* **Centralizing firewalls** -- Centralized firewalls protect multicloud traffic.
* **Reducing license costs** -- License reduction via centralized cloud firewalls.
* **Optimizing multicloud security** -- Focus multicloud interconnection security instead of securing each cloud in isolation.
Branch office and remote workforce protection:
* **Secure remote access** -- Protect traffic originating from remote users and branch offices.
* **Decentralized security** -- Shift away from on-premises physical firewalls.
* **Improve scalability and flexibility** -- Distributed firewalls offer scalability and flexibility in managing security across geographically dispersed locations.
* **Hardware reduction** -- Eliminate the need for physical firewall appliances.
Compliance and data protection:
* **Centralized firewall management** -- A single point of control for managing firewalls.
* **Consistent global policies** -- Enforce uniform security policies across all locations.
* **Strategic control point** -- Position the firewall management system between data centers (DCs), Cloud Service Providers (CSPs), and the internet.
## SD-WAN gateways with MVE
MVE enables quick deployment of SD-WAN and other network services without physical hardware. MVE deploys virtual network functions at the edge of the Megaport network, enhancing the speed and security of network traffic to cloud and branch locations.
SD-WAN centralizes and simplifies WAN management by virtualizing networks, allowing for flexible transport, automated routing, and real-time performance monitoring.
Megaport SDN is a global private on-demand network. MVE integrates with Megaport internet to allow SD-WAN appliances to connect to the Megaport SDN via the internet.
Reliance on the internet is minimized to a few hops. Megaport SDN acts as a bridge to Megaport's private network and ensures low latency.
In the diagram below, once traffic enters the Megaport SDN through an MVE, it remains within Megaport’s secure and private infrastructure, which optimizes network reliability.
Key benefits of MVE SD-WAN:
* **Global, flexible connectivity** -- Global, flexible connectivity without private circuits.
* **Optimized SD-WAN termination** -- Localized traffic via metro MVE edge points. Connect via Cross Connects, DCs, or the internet.
* **Direct cloud and SaaS access** -- Direct access to clouds, , data centers, and the Megaport Marketplace.
* **Flexible, pay-as-you-go pricing** -- Simplified pay-as-you-go cost management including IP address usage, internet access, and a connection to the internet that terminates the tunnel between the MVE and customer-provided equipment at the branch.
* **Enhanced security with SASE** -- NFV with leading SD-WAN partners for SASE.
* **Fast Portal provisioning** -- Rapid deployment using the Megaport Portal.
## Virtual router with MVE
MVE integrates virtual router capabilities from leading vendors such as Cisco, Fortinet, and 6WIND. It allows you to deploy and manage virtual network functions (VNFs) on demand, offering flexibility and control over network routing, security, and optimization.
Unlike the [Megaport Cloud Router (MCR)](/mcr), MVE offers vendor-specific CLI access and advanced features, including VPN, QoS, firewall, NAT, and SD-WAN, enabling consistent functionality across both virtual and physical platforms.
Key benefits of MVE virtual router:
* **Multivendor support** -- Deploy virtual routers from Cisco, Fortinet, 6WIND, and other providers with their software feature sets.
* **On-demand provisioning** -- Scale quick virtual network functions in global Megaport locations.
* **Enhanced control** -- CLI access for direct configuration and advanced routing options beyond what MCR offers.
* **Edge connectivity** -- Seamless integration with SD-WAN, public clouds, and private networks for optimized traffic flow.
* **Security and performance** -- Leverage vendor-specific security policies, QoS, and traffic management.
## SCION integration with Anapaya and MVE
MVE supports integration with Anapaya to enable SCION (Scalability, Control, and Isolation On Next-Generation Networks). SCION is a next-generation internet architecture that provides stronger path control, isolation from failures, and explicit trust information for end-to-end communication.
Through Anapaya, Megaport MVE can deliver:
* Cryptographically verified path segments
* Multi-path discovery and failover
* Route selection based on performance, trust, or geographic location
This approach is designed for environments that require high security, resilience, and predictable latency.
An MVE can deploy as an Anapaya EDGE, CORE or GATE role. This provides direct, private connectivity to major cloud providers while minimizing reliance on the public internet. Cryptographically verified, path-aware routing enhances security and ensures predictable network behavior, all without additional physical hardware, leveraging MVE’s virtual network function hosting.
Key benefits of SCION with MVE:
* **Trusted networks** -- SCION networks are organized into autonomous systems (AS) and grouped into trust domains (ISDs) with defined trust policies. Each ISD can establish its own trust roots and maintain its own public key infrastructure (PKI), cryptographically verifying participating autonomous systems (AS) and reducing reliance on third-party PKIs.
* **Fast multi-path discovery and failover** -- SCION discovers path segments (hops) in advance and assembles available paths to destinations, allowing quick switching between paths and simultaneous use of multiple paths. This increases resilience and protects against outages or denial-of-service attacks.
* **Path validation** -- Every hop on a SCION path is cryptographically verified, which protects against route leaks, hijacks, and IP address spoofing, and ensures stronger validation of traffic.
* **Geofencing for data sovereignty** -- Users can select preferred paths for their data based on performance, trust, or geographic attributes. This supports compliance with data sovereignty requirements.
* **Scalability and interoperability** -- SCION is compatible with existing internet infrastructure and protocols. SCION-enabled devices can connect through SCION gateways without requiring changes to internal network infrastructure.
## Juniper Session Smart Router (SSR) with MVE
Juniper SSR on MVE transforms SD-WAN deployment by eliminating the complexity of traditional tunnel-based overlays. Using Secure Vector Routing (SVR), Juniper SSR creates dynamic, session-aware, and highly secure connections that simplify network management while improving application performance and security across branch offices, remote sites, and multicloud environments.
The SSR deploys Juniper's advanced, software-defined routing platform on MVE as a virtual router and SD-WAN gateway, managed through the Juniper Mist platform. By removing the need for VPN tunnels entirely, Juniper SSR reduces operational burden while delivering enhanced security and application performance across Megaport's global private network.
Key benefits of Juniper SSR on MVE:
* **Secure Vector Routing (SVR)** -- Eliminates VPN tunnel complexity, replacing traditional overlays with session-aware routing, which reduces operational overhead and improves network reliability.
* **Session-aware routing** -- Routes traffic based on application sessions rather than network topology, providing dynamic path selection and optimized performance.
* **Application-centric approach** -- Simplifies network configuration by aligning routing policies with application requirements instead of complex network constructs.
* **Enhanced security** -- Delivers authenticated, session-based security without the overhead and vulnerabilities of traditional VPN tunnels.
* **Juniper Mist cloud management** -- Centralized management, automation, and analytics through the Juniper Mist platform for streamlined operations across distributed locations.
* **Seamless multicloud connectivity** -- Extends consistent policies and secure connectivity across branch offices, remote sites, and cloud environments over Megaport's private SDN.
## Juniper vSRX with MVE
Juniper vSRX on MVE delivers advanced firewall and security capabilities through a virtualized . The vSRX provides the same security features as physical SRX Series platforms in a virtual form, enabling flexible deployment across Megaport's global private network.
With vSRX, you get stateful firewall protection, intrusion prevention, application visibility, and VPN capabilities. Deploying vSRX on MVE lets you secure traffic between branch locations, cloud environments, and data centers without physical hardware.
Key benefits of Juniper vSRX on MVE:
* **Flexible deployment** -- Deploy Juniper NGFW security without physical appliances, shipping delays, or rack-space requirements.
* **Stateful firewall protection** -- Provides deep packet inspection and application awareness for comprehensive threat defense.
* **Intrusion prevention** -- Detects and blocks network threats with integrated intrusion detection and prevention.
* **Simplified management** -- Optional Juniper Mist integration for centralised visibility and control.
## Helpful references
* [Megaport Virtual Edge Locations](/mve/locations)
* [MVE Deployment Scenarios](/mve/mve-use-cases)
* [MVE Diversity](/mve/mcr-mve-diversity)
* [Types of vNIC Connections](/mve/vnic-connections)
# Megaport Virtual Edge Locations
Source: https://docs.megaport.com/mve/locations
This help topic provides a list of locations where you can connect to a Megaport Virtual Edge (MVE).
Before you create a Megaport Virtual Edge (MVE), you need to determine the best location - one that supports MVE and one that is in the most compatible metro area. MVE instances are located in key metro areas to maintain low latency from your cloud and workloads to MVE.
Megaport Internet functionality enables traffic flow to and from branch locations using SD-WAN technologies through internet connections. You use pre-existing connectivity from your premises to securely access the MVE that is geographically located closest to those premises.
In general, you provision MVEs at the metro locations nearest to your branch sites and on-premises locations to benefit from the lowest latency and highest throughput.
You can connect multiple locations to an individual MVE. You can also deploy multiple instances and load-balance your branch sites.
We recommend two MVE host systems per region for resiliency.
On the [Megaport Enabled Locations](https://www.megaport.com/megaport-enabled-locations/) page, you can search for nearby Megaport Points of Presence (PoPs) using the **MVE-Enabled** filter, where you can deploy an MVE.
Review the appropriate *Planning Your Deployment* topic for your SD-WAN or NGFW (next generation firewall) vendor before you begin:
* [6WIND](/mve/6wind/plan-deployment)
* [Anapaya](/mve/anapaya/plan-deployment)
* [Aruba](/mve/aruba/plan-deployment)
* [Aviatrix](/mve/aviatrix/plan-deployment)
* [Check Point CloudGuard](/mve/checkpoint/plan-deployment)
* [Cisco](/mve/cisco/plan-deployment)
* [Deciso OPNsense](/mve/deciso/plan-deployment)
* [F5 BIG-IP Virtual Edition](/mve/f5/plan-deployment)
* [Fortinet](/mve/fortinet/plan-deployment)
* [Juniper](/mve/juniper/plan-deployment)
* [Netskope One SD-WAN](/mve/netskope/plan-deployment)
* [Palo Alto Networks (VM-Series)](/mve/palo-alto/plan-deployment)
* [Palo Alto Networks (Prisma SD-WAN)](/mve/palo-alto/plan-deployment-prisma)
* [Peplink](/mve/peplink/plan-deployment)
* [Versa](/mve/versa/plan-deployment)
* [VMware](/mve/vmware/plan-deployment)
# MVE Diversity
Source: https://docs.megaport.com/mve/mcr-mve-diversity
This help topic describes the functionality and specifications of the diversity of Megaport Virtual Edge (MVE).
Diverse connections improve the robustness of your network by using different physical infrastructure to provide network services. Diverse connections build in redundancy and eliminate single points of failure.
() simplifies the deployment of diverse connections by establishing diversity zones. A diversity zone is a group of devices at a single Megaport location. s in different diversity zones are physically separated on Megaport devices and connected to different devices.
During Megaport scheduled maintenance, no more than one diversity zone in a given metro will experience downtime at any time. Whenever possible, diversity zones in the same city have maintenance periods scheduled for different days.
Each indicates its diversity zone with either a red or blue icon.
## Selecting a diversity zone
When you select the location for your , you can select the diversity zone.
When you choose a diversity zone, the location results list will be filtered by that zone:
* **Auto (default)** -- This will show all locations where is available.
* **Red or Blue diversity zone** -- If you select Red or Blue diversity zone, only locations that have availability in that zone will be displayed.
| Icon | Meaning | Use case |
| :-: | :- | :- |
| | Auto select diversity zone | Allow Megaport to allocate the diversity zone |
| | Red diversity zone | Allocate the to the red diversity zone |
| | Blue diversity zone | Allocate the to the blue diversity zone |
### Auto diversity zone
If you choose the Auto diversity zone option, Megaport will select the zone to which your service is allocated.\
The following rules apply:
* If both diversity zones are available, one zone will be chosen.
* If only one zone is available, that zone will be chosen.
# MVE Deployment Scenarios
Source: https://docs.megaport.com/mve/mve-use-cases
This help topic describes deployment scenarios for Megaport Virtual Edge (MVE).
This topic describes many, but not all, of the deployment use cases with an SD-WAN partner and Megaport Virtual Edge (MVE).
For all use cases, replacing a single MVE with two MVEs improves network reliability by providing redundancy.
## Branch to branch
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
## Branch to cloud
This deployment extends the enterprise branch network to one or many cloud resources to enable one seamless network from branch to cloud.
## Branch to data center
This deployment connects the enterprise branch network to the enterprise data center footprint, covering more than 700 Megaport-enabled global data center locations.
## VPC to VPC
This carrier-neutral deployment connects multiple cloud regions, providers, or accounts for network interoperation, privately.
# SSE and SASE within the Megaport Network
Source: https://docs.megaport.com/mve/sase
This help topic explains the differences between SASE, SSE and how Megaport provides the private and how high-performance backbone to integrate SASE and SSE functions into your network.
As organizations move toward cloud-native environments, the way organizations secure and connect their networks has fundamentally changed.
This topic explains the differences between and , and how Megaport provides the private and high-performance backbone to integrate SSE and SASE functions into your network.
## Understanding SSE and SASE within the Megaport network
**SSE -- The security component**
SSE is a set of cloud-delivered security services. It is designed to protect users and data regardless of where they are located.
* **Key services** -- , , and .
* **Goal** -- Secure User-to-App and App-to-App traffic.
**SASE -- The comprehensive architecture**
SASE provides a comprehensive approach for networking and security. It represents the convergence of networking () and security functions into a single, global, cloud-native service.
* **The formula** -- SASE = SSE + SD-WAN
* **Goal** -- Simplify management and improve performance by combining connectivity and security.
As a Network as a Service (NaaS) provider, Megaport plays a critical role by hosting SD-WAN and security services. By providing a secure and private underlay as well as hosting capability, Megaport enables the seamless integration of SSE and SASE features directly into your network architecture.
**Megaport's role -- Connectivity layer**
While SSE and SASE providers such as Palo Alto Networks, Cisco, and Fortinet manage the security inspection and policy, Megaport provides the private software-defined network that carries the traffic between your locations and the cloud.
Megaport bypasses the inherent instability of the public internet by utilizing a private and dedicated backbone. By using Megaport, you ensure your SSE and SASE traffic doesn't get slowed down by public internet congestion and high-jitter or high-latency hops.
**Network overview -- SSE and SASE via the Megaport network**
The following network diagram illustrates how the Megaport network carries private traffic to integrate SSE and SASE functions into your network.
## Summary of features provided by SSE and SASE
The following table summarizes SSE and SASE features.
| **Feature** | **SSE** | **SASE** |
| - | - | - |
| **Primary functions** | Data and access security | Network + security |
| **Common component** | CASB, FWaaS, SWG, ZTNA | SD-WAN + SSE |
| **User/branch deployment** | Via a lightweight agent on the laptop or a browser portal | SSE Agent plus site-to-site and site-to-cloud tunnels automated by SD-WAN ( /) |
| **Vendor examples** | Zscaler, Netskope, Cloudflare | Cisco, Fortinet, Palo Alto |
## Implementing SSE using Megaport services
**Architectural overview**
Some SSE platforms, including Cloudflare, Netskope, Cato, and Palo Alto Prisma Access, integrate with Megaport by providing private connectivity to Megaport-enabled data centers and cloud on-ramps.
You can also implement SSE solutions with a Megaport Virtual Edge (MVE), which hosts virtualized network functions (VNFs) such as , CASB, SGW, and ZTNA, at the edge of Megaport’s global private network. The MVE also facilitates secure access from cloud-based SSE platforms to private applications hosted in data centers and CSPs.
While SASE focuses on the convergence of SD-WAN and security, an SSE-centric MVE deployment prioritizes the security stack and serves as a private on-ramp to cloud security providers. Instead of sending sensitive corporate traffic solely over the unpredictable public internet, user traffic is directed to a localized MVE.
**Deployment workflow**
1. **Provision the MVE** -- Deploy an MVE instance in the metro area geographically closest to your users or branch offices to minimize latency.
2. **Appliance activation** -- Once the virtual appliance is active on the MVE, it is registered with your SSE vendor's central management console (for example, Prisma Access Strata Cloud Manager, FortiSASE). This allows you to push granular security policies and identity-based access controls to the edge.
3. **Establish connectivity** -- To complete the path, you configure Virtual Cross Connects (VXCs) from the MVE directly to your Cloud Service Providers (CSPs) or your SSE vendor’s cloud points of presence (PoPs).
This setup creates a secure private underlay where traffic is first secured on the MVE and then transported across Megaport's private backbone.
This bypasses internet congestion, mitigates DDoS risks, and provides a more stable, predictable path for your SSE-protected data.
## Implementing SASE using Megaport services
**Architectural overview**
You can implement SASE SD-WAN with MVE, which hosts SD-WAN virtualized network functions (VNFs) directly on Megaport’s global private SDN.
Instead of relying solely on the public internet, traffic from branch offices or remote users connects to a localized MVE. The MVE runs certified SASE or VNF appliances from partners such as Cisco, Fortinet, Palo Alto Networks, Versa, and so on, which integrate the SSE security stack with networking optimization (SD-WAN).
**Deployment workflow**
1. **Provision the MVE** -- Deploy an MVE instance in the metro area geographically closest to your users or branch offices to minimize latency.
2. **Configure security policies** -- Once the virtual appliance is active, it will automatically register and authenticate with the vendor’s central orchestrator to incorporate SD-WAN security policies. For example, Palo Alto Panorama and Fortinet FortiManager.
3. **Establish connectivity** -- Configure VXCs from the MVE to CSPs such as AWS, Azure, or Google Cloud. This creates a connectivity where traffic is secured at the edge and then transported across Megaport’s private backbone, bypassing internet congestion and reducing egress costs. A 100% private underlay to key locations, such as an enterprise headquarters office or a manufacturing facility, can be created through Megaport's private data center interconnects globally.
## MVE vendor image deployment
The following table provides a list of documentation explaining how to deploy a host MVE for your chosen vendor. This is the first step before implementing SSE and SASE services.
As Megaport continues to add new vendors, if a specific vendor is missing, check the [MVE Overview](/mve) section for the most up-to-date list of supported vendors.
For detailed configuration steps, please consult the product documentation provided on each vendor's website.
| **Providers** | **Solution** | **Links** |
| - | - | - |
| 6WIND Licensed Network Functions | SASE | [Planning Your 6WIND Deployment](/mve/6wind/plan-deployment) |
| Anapaya | SSE | [Planning Your Anapaya Deployment](/mve/anapaya/plan-deployment) |
| Arista VeloCloud SD-WAN | SASE | [Planning Your Arista VeloCloud SD-WAN MVE Deployment](/mve/vmware/plan-deployment) |
| Aruba | SSE, SASE | [Planning Your Aruba EdgeConnect SD-WAN MVE Deployment](/mve/aruba/plan-deployment) |
| Aviatrix | SASE | [Planning Your Aviatrix Secure Edge Deployment](/mve/aviatrix/plan-deployment) |
| Check Point CloudGuard | SSE, SASE | [Planning Your Check Point Deployment](/mve/checkpoint/plan-deployment) |
| Cisco | SSE, SASE | [Planning Your Cisco MVE Deployment](/mve/cisco/plan-deployment) |
| Fortinet | SSE, SASE | [Planning Your Fortinet Secure SD-WAN Deployment](/mve/fortinet/plan-deployment) |
| Juniper | SASE | [Planning Your Juniper Deployment](/mve/juniper/plan-deployment) |
| Netskope One SD-WAN | SASE | [Planning Your Netskope One SD-WAN Deployment](/mve/netskope/plan-deployment) |
| Palo Alto Networks | SSE, SASE | [Planning Your Palo Alto Networks VM-Series MVE Deployment](/mve/palo-alto/plan-deployment) |
| Peplink FusionHub | SASE | [Planning Your Peplink FusionHub Deployment](/mve/peplink/plan-deployment) |
| Versa | SASE, SSE | [Planning Your Versa Secure SD-WAN Deployment](/mve/versa/plan-deployment) |
## Helpful references
* [Connections Overview](/connections/overview)
* [MVE Overview](/mve)
* [Using IPsec with Megaport](/encryption/ipsec)
# Connecting MVEs Integrated with Arista VeloCloud SD-WAN
Source: https://docs.megaport.com/mve/vmware/connect-mve-to-mve
This help topic describes how to connect two Megaport Virtual Edges (MVEs).
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with Arista VeloCloud SD-WAN to another MVE. This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private Virtual Cross Connect (VXC) to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (MVE) and a B-End (another MVE).
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer/SD-WAN partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [Creating an MVE Integrated with Arista VeloCloud](/mve/vmware/creating-mve).
## Creating a VXC between two MVEs
Private VXC deployment between two Arista VeloCloud MVEs starts in the Megaport Portal where you will create the VXC. Then, you will configure the A-End and B-End MVE devices in the Orchestrator management console.
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and click **+Connection** next to the originating A-End MVE.
2. Select Private VXC and click **Next**.
3. Select the destination B-End MVE and location.\
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `LA MVE 2 to Dallas MVE 4`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. Consult Arista VeloCloud 's documentation for more information.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.\
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. 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 through the B-End VLAN.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Click **Add VXC** to move this configuration to your cart.
8. Repeat these steps to provision any additional VXCs.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs in Orchestrator.
The next procedure configures IP connectivity with BGP, providing just one solution out of many. Consult your SD-WAN vendor documentation for specific network design and configuration options before configuring interfaces for the MVEs.
## Adding edge details to Orchestrator
For the Orchestrator steps, see the [VeloCloud Orchestrator Guide (Arista)](https://www.arista.com/en/orchestrator-guide-vc-6-4).
## Validating your connection
Use Orchestrator to validate your connection.
For more information, see the [VeloCloud Orchestrator Guide](https://www.arista.com/en/orchestrator-guide-vc-6-4).
You can also check connectivity and BGP status from the CLI of the edge device. For more information, see [Reviewing your Arista VeloCloud MVE connection settings](/cloud/mve/vmware/generic/mve-vxc-details).
# Creating an MVE Integrated with Arista VeloCloud SD-WAN
Source: https://docs.megaport.com/mve/vmware/creating-mve
This help topic describes how to create and configure Megaport Virtual Edge (MVE) for Arista VeloCloud SD-WAN.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Arista VeloCloud SD-WAN. Once you have a Megaport account, you use the Arista centralized management console called Orchestrator. In Orchestrator you create and configure the profile and edge device. In the Megaport Portal, you create, administer, maintain, monitor, and terminate MVE.
Before you begin, you need to create a Megaport account:
* **New Megaport customers** -- Log in to the Megaport Portal, create your account, and proceed to your Arista VeloCloud SD-WAN Orchestrator account. For more information about setting up a Megaport account, see [Creating an Account](/setting-up/registering).
* **Existing Megaport customers** -- Proceed to [Creating an Arista VeloCloud edge profile and device](#createprofile) to start creating a new MVE.
Arista VeloCloud provides documentation for their SD-WAN product at [Arista VeloCloud SD-WAN Documentation](https://www.arista.com/en/admin-guide-vc-6-4).
## Licensing
Before you create an MVE in the Megaport Portal, you need a valid license from Arista VeloCloud. For more information about obtaining an Arista VeloCloud license, see [Edge Licensing](https://www.arista.com/en/operator-guide-vc-6-4/sd-wan-6-4-edge-licensing) or ask your Arista VeloCloud Sales Associate or Reseller.
## Basic steps
This section provides an overview of the configuration steps in Orchestrator and the Megaport Portal.
The basic steps are:
* Create an Arista VeloCloud SD-WAN edge device profile and edge device in Orchestrator.
* Configure the Arista VeloCloud SD-WAN device and apply the profile to the device.
* Generate an SSH public key.
* Create an MVE instance in the Megaport Portal.
## Creating an Arista VeloCloud SD-WAN Virtual Edge profile and device
To get started, you create a default profile so that when the edge device registers to Orchestrator, it retrieves its base configuration, connects to Orchestrator, and enables some specific firewall rules. After that you can manage the MVE device through Orchestrator.
**To create an edge profile in Orchestrator**
1. Log in to Orchestrator.
2. Click the link for the Customer profile account.
3. Choose Configure > Profiles.
4. Click **New Profile**.
5. Enter a Profile Name and an optional Description.\
For example, megaport-default-profile.
6. Click **Create**.
**To create a virtual edge device in Orchestrator**
1. Select the **Device** tab.
2. Select Global Segment from the Configure Segment drop-down.
3. Enable Cloud VPN.
4. Unselect all device types, except for Virtual Edge.
5. Under Device Settings: Virtual Edge, click **Edit** next to GE1 and GE2 and disable those interfaces sequentially.
6. Ensure that GE3 is enabled.\
GE3 becomes the first available routed interface. Other ports do not require to be disabled and can be left in their current state.
7. Configure the following options for the GE3 interface:
* **Interface Enabled** -- Select this option.
* **Capability** -- Choose Routed from the drop-down list.
* **Addressing Type** -- Choose DHCP from the drop-down list.
* **WAN Overlay** -- Enable this option and choose Auto-Detect Overlay from the drop-down list.
* All other interfaces -- Leave the default values.
8. Click **Update GE3**.
9. Under Wi-Fi Radio, ensure that Radio Enabled is unselected (there are no wireless interfaces).
10. Click **Save Changes** in the upper-right corner.
11. Select the **Firewall** tab and enter comma-separated IP values for any customer-side management IPs that require access to the edge device.
12. Ensure that the Firewall Status option is set to On.
13. Next to Support Access, enter the trusted IP addresses that are allowed access to the device.
14. Next to SNMP Access, you can optionally allow SNMP access to the WAN public interface. Enter the trusted IP addresses to allow.
15. Next to Local Web UI Access, enter the trusted IP addresses to allow access to the WAN interface. This is important because you are configuring a Arista VeloCloud Virtual Edge device with no LAN ports and no console.
16. Accept 80 as the Local Web UI Port Number or change it to match your environment.
17. Click **Save Changes** in the upper-right corner.
The next step is to configure and assign the profile to the edge device.
## Configuring the Arista VeloCloud edge device
After creating the profile, you will configure the edge device to get it connected to the internet.
**To configure a Arista VeloCloud edge device in Orchestrator**
1. In Orchestrator, click the link for the Customer profile account.
2. Choose Configure > Edges.
3. In the upper-right corner, click **New Edge...**.
4. Populate the fields as required for your network.
* **Name** -- Enter a name for the edge device.
* **Model** -- Choose Virtual Edge from the drop-down list.
* **Profile** -- Select the recently created profile to assign to the new edge device.
* **Authentication** -- Choose an authentication option for the edge device.\
For more information about the authentication options, see the [Arista VeloCloud SD-WAN documentation](https://www.arista.com/en/admin-guide-vc-6-4/sd-wan-6-4-provision-a-new-edge).
* **Edge License** -- Choose the license to apply to this edge device. The list displays the licenses assigned to your enterprise. Licenses are grouped by the edge device throughput limit (1 Gbps or 10 Gbps), region, and length of contract. For more information about obtaining a VeloCloud license, see [Edge Licensing](https://www.arista.com/en/admin-guide-vc-6-4/sd-wan-6-4-edge-licensing) or ask your Arista VeloCloud Sales Associate or Reseller.
* **Custom Info** (optional) -- Enter a description for the edge device.
* **Contact Name and Contact Email** -- Enter a contact name and email address for this device.
5. Click **Create**.
6. The **Edge Overview** tab lists an activation key. Save the activation key for use in the Megaport Portal.
7. Make any device-specific changes to the Device, Business Policy, or Firewall parameters. Or, use a device-specific profile to use predefined profile settings.
8. Click **Save Changes** in the upper-right corner.
The next step is to generate an SSH key for authentication.
## Administrative access to MVE
You connect your MVE through a public/private SSH key pair to establish a secure connection. The public SSH key allows you to use SSH to access the MVE and perform administrative tasks, such as setting the administrative password, enabling HTTPS access, and optionally registering the MVE to your management platform.
Megaport supports the 2048-bit RSA key type.
**To generate an SSH key pair (Linux/Mac OSX)**
* Enter the SSH keygen command in the terminal.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ssh-keygen -f ~/.ssh/megaport-mve-instance-1-2048 -t rsa -b 2048
```
The key generator command creates an SSH key pair and adds two files to your \~/.ssh directory:
* **megaport-mve-instance-1-2048** - contains the private key.
* **megaport-mve-instance-1-2048.pub** - contains the public key that is authorized to log in to the vendor account.
**To generate an SSH key pair (Windows, using [PuTTYgen](https://www.puttygen.com))**
1. Open PuTTYgen.
2. In the Key section, choose RSA 2048 bit and click **Generate**.
3. Move your mouse randomly in the small screen to generate the key pairs.
4. Enter a key comment to identify the key.\
This is convenient when you use several SSH keys.
5. Enter a Key passphrase, and re-enter to confirm.\
The passphrase is used to protect your key. You will be asked for it when you connect via SSH.
6. Click **Save private key**, choose a location, and click **Save**.
7. Click **Save public key**, choose a location, and click **Save**.
You will copy and paste the contents of the public key file in the Megaport Portal later to distribute the public key to the MVE. Your private key will match the public key to grant access. Only a single private key has access to the MVE for SSH access.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/vmware/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also typically create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Arista VeloCloud SD-WAN**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Arista VeloCloud SD-WAN.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Arista VeloCloud SD-WAN-specific settings:
* **Orchestrator Address** -- Enter an FQDN (Fully Qualified Domain Name) or IPv4 or IPv6 address for the Orchestrator where you created the edge device.
* **Activation Code** -- Enter the activation key provided to you by Orchestrator after creating the edge device.
* **SSH Key** -- Copy and paste the contents of your public SSH key here. You can find the public key in the **megaport-mve-instance-1-2048.pub** file generated earlier.
* **Virtual Interfaces (vNICs)** -- Each MVE is configured with one vNIC named *Data Plane* by default. To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed.
You can add a total of five vNICs to the MVE, including the one added by default. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Enter a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with Arista VeloCloud SD-WAN. The overlay network is created and maintained by Arista VeloCloud SD-WAN to provide secure tunnels from the branch locations.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select **vNIC-0** for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up a Arista VeloCloud SD-WAN.
## Viewing the MVE in the Megaport Portal
After creating the MVE, you can view it in the Megaport Portal on the Services page. You can also view the public IP addresses assigned.
**To view an MVE in the Megaport Portal**
* Go to the **Services** page.
The Megaport Internet icon differs from a standard VXC icon in the Megaport Portal, as shown in the image.
For more information about the Services page, see [Understanding the Services Page](/portal-admin/services-page).
**To view the public IP addresses assigned to the MVE**
1. Click the gear icon next to the Megaport Internet connection.\
The Connection Configuration screen appears. From here, you can modify any of the Megaport Internet connection details.
2. Select the **Details** tab.
3. Locate the public IP address (IPv4 or IPv6).\
These are the public IP addresses assigned to the MVE. Make a note of these addresses for use later.
4. Verify that you see your new MVE device in the Megaport Portal under **Services**.
The Public IP Addresses (IPv4 or IPv6) are the addresses of the MVE device. By this time, the new MVE should be registered to your Orchestrator and ready for additional configuration.
## Viewing the MVE in Orchestrator
After creating the MVE, you can monitor the status in Orchestrator.
**To view an MVE in Orchestrator**
1. Log in to Orchestrator.
2. Choose Monitor > Network Overview.
3. Click the MVE edge device from the list.\
The Link Status and Bandwidth Usage metrics are displayed.
### Validating your connection
* In Orchestrator under Test & Troubleshoot > Remote Diagnostics, select the MVE and click Run for Troubleshoot BGP - Show BGP Summary to verify the BGP session and ensure the edge device is up.
You can also check connectivity and BGP status from the CLI of the edge device. For more information, see [Reviewing MVE Connection Settings in Arista VeloCloud SD-WAN](/cloud/mve/vmware/generic/mve-vxc-details).
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/vmware/creating-mve-vxc).
# Creating a VXC to an MVE Integrated with Arista VeloCloud
Source: https://docs.megaport.com/mve/vmware/creating-mve-vxc
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE) in Arista VeloCloud Orchestrator.
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with Arista VeloCloud SD-WAN.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
For specific CSP configuration details:
* AWS Direct Connect -- See [Creating MVE Connections to AWS](/cloud/mve/vmware/aws).
* Azure Express Route -- See [Creating MVE Connections to Azure using ExpressRoute](/cloud/mve/vmware/azure).
* Google Cloud -- See [Creating MVE Connections to Google](/cloud/mve/vmware/google).
* Other cloud connections -- See [Creating MVE Connections Any Endpoint](/cloud/mve/vmware/generic).
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
For specific configuration details, see [Connecting MVEs](/mve/vmware/connect-mve-to-mve).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/vmware/terminating-mve).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# Arista VeloCloud SD-WAN with Megaport Virtual Edge
Source: https://docs.megaport.com/mve/vmware/index
This help topic describes Arista VeloCloud SD-WAN with Megaport MVE functionality.
Arista VeloCloud SD-WAN creates the private overlay network and manages the network connections and network policies. You use the Arista VeloCloud Orchestrator management console to create an edge profile and edge device, and then you can apply the profile to the device.
You use the Megaport Portal to create and order the MVE and create and manage the Virtual Cross Connects (VXCs) to the cloud on-ramps and other services in the Megaport SDN. The Arista VeloCloud SD-WAN fabric acts as the overlay, and the Megaport SDN acts as the underlay.
The following diagram shows an example network implementation of Arista VeloCloud SD-WAN features over the Megaport network.
# Planning Your Arista VeloCloud SD-WAN MVE Deployment
Source: https://docs.megaport.com/mve/vmware/plan-deployment
This help topic describes Arista VeloCloud SD-WAN deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
| **You Provide** | **Megaport Provides** |
| - | - |
| Internet connection from branch | Platform to host virtual SD-WAN appliances |
| SD-WAN vendor enabled at branch | Complete connection from a branch to any destination on the Megaport network and interoperation with other Megaport products and services |
| Customer premises equipment (CPE) installed in branch | Megaport Internet connection to terminate the tunnel between MVE and CPE at branch via internet |
| SD-WAN software license to use on Megaport SDN | Access to the Megaport ecosystem |
## Deployment considerations
This section provides an overview of the MVE deployment options and features.
### SD-WAN vendors
MVE is integrated with Arista VeloCloud SD-WAN, which uses Orchestrator management console to create the private overlay network.
For information about all supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Arista VeloCloud SD-WAN**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* You can provision another MVE instance, add it to your overlay network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, add it to your overlay network, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### Security
MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN. CSP-hosted instances of partner SD-WAN products route critical traffic across the Megaport SDN, reducing internet dependence. Traffic remains encrypted and under your policy control while traveling across the Megaport SDN, to or from, MVE.
### Licensing
You bring your own Arista VeloCloud SD-WAN license for use with MVE. It is your responsibility to have the appropriate licenses for the SD-WAN endpoints created on the Megaport network. For more information about obtaining an Arista VeloCloud Edge license, see [Edge Licensing](https://www.arista.com/en/admin-guide-vc-6-4/sd-wan-6-4-edge-licensing) or ask your Arista VeloCloud Sales Associate or Reseller.
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
### vNICs
Each MVE can have up to five vNICs. An MVE is created with one vNIC by default. You can add up to four more, making a total of five.
Before specifying the number of vNICs on your MVE:
* Be aware that the number of vNICs cannot be changed after an MVE has been ordered. Decide in advance how many vNICs to specify when you create the MVE.
* Consult your service provider to make sure that functionality won't be affected if you add a vNIC.
If you need to change the number of vNICs after an MVE has been ordered, you will have to cancel and re-order the MVE.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
# Terminating an MVE
Source: https://docs.megaport.com/mve/vmware/terminating-mve
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window appears, displaying a list of services connected to the MVE. Early termination fees are shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use your SD-WAN management console to delete the MVE.
# Types of vNIC Connections
Source: https://docs.megaport.com/mve/vnic-connections
This help topic describes the different types of vNIC connections depending on the service you are connecting to.
A Virtual Network Interface Card (vNIC) is a virtual version of a physical network card. It connects an MVE to the Megaport network, functioning like a physical NIC to enable the MVE to communicate with other services.
When an MVE has multiple vNICs, you must specify either an A-End or B-End vNIC when creating new connections. You can add multiple vNICs while deploying an MVE. You can also rename a vNIC later, after the MVE is deployed. To rename a vNIC, simply type the new name directly into the Virtual Interfaces (vNICs) field in the Portal.
You can configure a maximum of five vNICs on an MVE. After the MVE has been created, you cannot add or remove vNICs.
Other considerations include:
* You can have one or more VXCs per vNIC, up to the maximum permitted for the MVE. The maximum number of VXCs allowed per MVE is determined by its size. For more information, see [Megaport Limits and Quotas](/limits-quotas).
* Each VXC can be configured as either tagged or untagged, based on your requirements. For more information, see [Using tagged or untagged VXCs](/encryption/macsec#tagged-or-untagged-vxc).
* You can configure a single untagged VXC with one or more tagged VXCs per vNIC.
* Each vNIC supports only one untagged VXC, allowing a maximum of five untagged VXCs per MVE across all five vNICs.
Each overlay vendor has specific rules for vNIC usage. Before creating your MVE, refer to the vendor’s documentation. These rules might include requirements for orchestrator vNICs and tagging, LAN and WAN vNIC selection, and High Availability (HA) configurations.
## MVE to Megaport Internet
You can use a Megaport Internet connection to connect your MVE to the internet. This connection supports various use cases, such as connecting an MVE overlay device to an orchestrator, linking branch offices, or enabling VPN access.
When creating a Megaport Internet connection for an overlay orchestrator, most vendors typically require the interface to be configured as untagged on vNIC-0. However, some vendors have different requirements, so always refer to their documentation.
## MVE to MVE
When connecting two MVEs, you must specify both the A-End and B-End vNICs. The VXCs for each vNIC can be either tagged or untagged. Note that a single tagged vNIC can have multiple VXCs configured on it.
## MVE to Port
When connecting an MVE to a Port, you must specify an A-End vNIC, which can be either tagged or untagged. Tagged VXCs can be assigned a VLAN for the MVE side. Similarly, a tagged Port can be assigned a VLAN.
The following example shows that the A-End vNIC is untagged, and the B-End Port is tagged.
## MVE to MCR
When connecting an MVE to an MCR, you must specify an A-End vNIC, which can be tagged or untagged. Tagged VXCs can be assigned a VLAN for the MVE side, while assigning a VLAN for the MCR side is not required.
# Introducing Megaport
Source: https://docs.megaport.com/overview/index
This help topic introduces the features and services offered by Megaport.
Megaport is a software layer that provides an easy way to create and manage network connections. Through the Megaport network, you can deploy private point-to-point connectivity between any of the locations on Megaport’s global network infrastructure.
## The Megaport network
Megaport operates a global network infrastructure and manages this network through software-defined networking (SDN). This network enables fast, flexible, and on-demand connectivity to hundreds of global services with an extensive footprint throughout Asia Pacific, North America, Europe, and the Middle East.
You can use this global network by creating a high-speed interface called a Port. By creating a Port, you can create point-to-point connections between any of your own locations or to a connected Cloud Service Provider (CSP). You can also connect to any other service that is connected to the Megaport network.
Since the network is managed through software, you can set up a new connection or change an existing connection in less than a minute.
You can deploy and manage services through the Megaport Portal or API.
### Easy, flexible, and on-demand
* As your business demands change, you can easily increase or decrease your bandwidth at any time.
* Create and run a global network with or without the need for physical infrastructure.
* Megaport network uses a pay-as-you-go service model. Connections can range from 1 Mbps to high-capacity multi-Gbps speeds, depending on the Port and data center capabilities.
* Flexible contract terms that align with cloud consumption models.
* Provision direct connectivity to the leading cloud and network providers on the Megaport network.
* Connect to multiple cloud providers and cloud regions from a single interconnection point for cost-effective multi-region redundancy.
### Secure and private connectivity
* Establish seamless, point-to-point connectivity between regions and CSPs from your physical data center or without the need to own and manage hardware.
* Keep your traffic secure when connecting between metros, regions, and countries.
* The Megaport network does not traverse the internet. All CSP connections are enabled through their dedicated partner connections and fully integrated with CSP APIs.
* Deploy scalable bandwidth between your data centers for storage backup and replication.
* Manage your connectivity autonomously and optimize your workflow using Megaport's API.
### Services
* **[Port](/connections/creating-port/)** -- High-speed Ethernet interface that connects to the Megaport network, available in a range of capacities depending on the location and Port type.
* **[Virtual Cross Connect (VXC)](/connections/overview)** -- Connection between any two endpoints on the Megaport network. Most connections support capacity ranging from 1 Mbps to several Gbps. Higher-capacity Ports in some metros can support much greater speeds, depending on the network configuration.
* **[Megaport Cloud Router (MCR)](/mcr/)** -- Virtual router for on-demand, private, Layer 3 connectivity to service providers between key global routing zones.
* **[Megaport Virtual Edge (MVE)](/mve/)** -- On-demand Network Functions Virtualization service that supports branch-to-cloud connectivity on the Megaport SDN. MVE provides the edge-computing framework to deploy SD-WAN gateways, virtual routers, and integrated transit gateways.
* **[IP Address](/ip-address/)** -- A standalone public IPv4 or IPv6 subnet that you order, manage, and link to your Megaport Internet connections.
* **[Internet Exchange (IX)](/ix/)** -- Connect to content and services across multiple regions, exchanging traffic directly and reducing bandwidth usage on client internet connections.
* **[Megaport Internet](/megaport-internet/)** -- A scalable, on-demand service that allows you to connect to the internet from Ports, MCRs, and MVEs. As part of the MVE provisioning, you create a Megaport Internet connection to provide connectivity and to allow MVE to register and communicate with the SD-WAN overlay network.
* **[Megaport Object Storage](/storage/object/)** -- S3-compatible object storage provisioned on Latitude.sh and connected to the Megaport network through a dedicated VXC.
* **[Megaport NAT Gateway (NAT Gateway)](/nat/)** -- A NAT service that enables devices in a private network to access the internet without requiring each device to have a public IP address.
* **[Megaport Marketplace](/marketplace/overview)** -- An online hub where global service providers and enterprise customers interconnect, so you can connect to a broad range of internet services, cloud providers, and managed services.
## Curious to learn more?
Click below to join the fun with Megaport Live: Tech Drop-Ins!
# Partner-Managed Accounts
Source: https://docs.megaport.com/partner/managed
This help topic provides an overview of the differences between partner accounts and those managed by a partner.
Megaport has two types of customer accounts: direct and indirect.
Direct customers work directly with Megaport to set up their account and configure and manage services. Indirect customers work with a Megaport partner. Indirect customer accounts are also called managed accounts.
Partners can find more information in the [Megaport Partner Program](https://www.megaport.com/partners/) overview and the [Megaport Partner Portal Documentation](/partners).
If you work with a Megaport partner and have a managed account, there are differences in the Portal experience and the visibility/availability of some features. Partners can customize the Portal experience for their managed accounts and can turn on or off features such as pricing and chat support.
Managed accounts can receive technical support assistance from a partner or from Megaport.
If you work through a partner, you might notice these differences in the Megaport Portal:
* **Billing market** -- Billing markets are not visible to managed accounts - only to partner accounts.
* **Chat support** -- By default, the chat support feature is disabled for managed accounts supported by a partner. See your partner program details for more information about how to get support.
For managed accounts supported by Megaport, chat support is enabled.
* **Company profile** -- By default, managed accounts do not have permission to view or edit company profile information.
* **Dashboard** -- Your partner determines whether managed accounts can see the Megaport Portal dashboard.
* **Megaport Quoting Tool** -- Managed accounts do not have access to the Quoting Tool for quoting service costs.
* **Invoice payment** -- Managed accounts do not pay bills directly to Megaport. Charges incurred by managed accounts are billed by the partner account.
* **Megaport Marketplace** -- Managed accounts do not have permission to view or edit Megaport Marketplace profile information.
* **Notification emails** -- Maintenance event notifications are sent directly to the partner and not your managed account. Your partner will communicate with you regarding any maintenance events that affect your account. Security emails are sent directly to anyone affected.
* **Ordering services** -- When configuring a service, you only see locations where your partner has enabled a billing market.
* **Pricing visibility** -- By default, pricing is not visible for managed accounts. You will not see any pricing information when creating, configuring, or updating services unless your partner enables this setting for you.
* **Technical support details** -- Managed accounts supported by a partner can view technical support details but do not have permission to edit them. Managed accounts supported by Megaport cannot view or edit technical support details.
* **Service Approval Queue** -- Partners might require that services and add-ons created, updated, or terminated by managed accounts be approved by the partner before they are provisioned. If this applies to your account, the Portal will display a message during service creation, update, or termination, indicating that the action is pending approval. For more information, see [Service Approval Queue for Partners](/partners/services/service-approval-queue).
* **Custom branding** -- Partners can add their branding to the Portal for their managed accounts. For more information, see [Adding Custom Branding](/partners/account/custom-branding).
* **Ordering restrictions in Brazil** -- Managed accounts and partners acting on behalf of managed accounts cannot order services in the Brazil market because of regulatory limitations. When partners enable the Brazil billing market or update the billing market settings, the Portal displays a warning about this restriction.
# Connecting to Latitude.sh
Source: https://docs.megaport.com/portal-admin/connect-latitude
This help topic describes how to connect to Latitude.sh to order bare metal, and what happens when you do.
You can manage both connectivity and infrastructure by connecting to Latitude.sh from the Megaport Portal.\
Latitude.sh allows you to deploy and manage bare metal instances globally. The platform offers the flexibility of virtualized cloud environments with the performance, security, and control of dedicated infrastructure.
On the Services page, click **Add Services**, then select **Order Bare Metal** in the **Compute** section.
You can also access Latitude.sh from the bottom left of the Megaport Portal. In the Megaport Portal, click the **latitude.sh** button to open the Latitude.sh Portal.
**To connect to Latitude.sh for the first time**
From the Megaport Portal:
* Click **Add Services**, then click **Order Bare Metal**
* Click **latitude.sh**
You will be transferred to the Latitude.sh Portal.
The first time someone from your company connects to Latitude.sh, a company account will be created for
Latitude.sh based on your company details in the Megaport Portal. That user will be logged in straight away.
Subsequent users who click through from the Megaport Portal must click the **Request access** button to log in for the first time.
For more information about using Latitude.sh's bare metal cloud infrastructure, see the [Latitude.sh documentation](https://www.latitude.sh/docs).
# Understanding the Services Page
Source: https://docs.megaport.com/portal-admin/services-page
This help topic describes the Services page and its features.
The Services page provides an overview of all your Megaport services. You can view, configure, and edit your Ports, MCRs, MVEs, and their connections (VXCs, IXs, and Megaport Internet connections). Each connection is grouped under its associated Port, MCR, or MVE.
## Maintenance and outage banner
At the top of the page, a banner will be displayed to inform you about any future or ongoing maintenance or outages. If there are no maintenance or outages, the banner will not be displayed.
The banner will only show events three days before the maintenance or outage is scheduled to occur.
Select **View All** to see details about the maintenance or outage.
Click **X** to close the banner.
## Creating services
Click **Add Services** in the top-right of the page header to open the Add Services page, then select a [Port](/connections/creating-port), [MCR](/mcr/creating-mcr), [MVE](/mve), or [NAT Gateway](/nat/creating-nat-gateway) to configure and order.
The Add Services page groups options by category to help you quickly choose what to deploy.
* **Network Services** -- Includes cards for **Port**, **MCR**, **MVE**, and **NAT Gateway**
* **Compute** -- Includes **Order Bare Metal**, which opens the Latitude.sh ordering flow in a new tab
* **Cancel** -- Returns you to the Services page without starting a new order
After you select a service card, the Portal opens the workflow for that service type.
## Connecting to Latitude.sh
Click **Order Bare Metal** to create a bare metal service with Latitude.sh.\
For more information, see [Connecting to Latitude.sh](/portal-admin/connect-latitude).
## Filtering and sorting services
The filtering and sorting tools allow you to customize the Services page to help you find the information you need.
### Filtering services
To narrow the services shown on the page, enter your text search in the **Filter Services** field. The filter will match against the name, location, and ID of the services. Any services matching your search will be highlighted.
Click (View Additional Filters) to filter services by service type and contract term length, in addition to the text filter. For example, you can filter on Ports on a 12 month term. The filters will persist if you navigate away and return to the Services page in the same session.
The number of matching services is displayed below the **Filter Services** field. Click **Clear Filters** to remove all filters and display all services in the Services page.
### Sorting services
You can change the order of the items on the Services page according to the following criteria:
* **Creation Date** -- Sorts by the date they were created.
* **Name** -- Sorts by name, in alphabetic order.
* **Location** -- Sorts by country, and then by the location within that country.
You can sort in either ascending or descending order.
You can only sort Ports, MCRs, and MVEs, not their connections (such as VXCs or IXs), which are displayed in the order they were added.
You can also hide or show all the connections for a Port, MCR, or MVE. By default, the Portal shows all the connections unless there are more than 10, in which case they are collapsed initially. Click the Extra Actions kebab menu and select Expand All Services
to expand all connections under a service, or select Collapse All Services to hide them.
## Downloading a service inventory
The Services page provides a convenient way to get an inventory of all services associated with your account. The inventory includes all live and configured services, along with any services that have been decommissioned.
**To download an inventory of services**
* On the Services page, click (Extra Actions) > Download Inventory Report.\
The service inventory is saved in the comma-separated values (CSV) file format and downloaded to your Downloads folder.
* You can import the CSV data into spreadsheets and databases.
* You can open the CSV file in any text editor.
## Viewing and editing services
By default, services are listed by the date they were created. VXCs, IXs, and Megaport Internet connections are grouped under each Port, MCR, or MVE.
### Service status
The icons for each Megaport service change color to indicate their provisioning status. Any important information relating to the status is shown under each service, such as a pending approval, a cancellation, or a missing billing market.
| **Icon** | **Color** | **Service Status Description** |
| :- | :- | :- |
| | **Green** | The service is configured and live. |
| | **Gray** | The service is not live. This can happen for several reasons, for example, the service could be in the process of being deployed, or a Port could be waiting for connection approval from the data center. |
| | **Orange** | The status of this service is unknown. |
| | **Red** | The service is down. |
Each service on the page provides icons so you can modify Port, MCR, MVE, NAT Gateway, VXC, IX, and Megaport Internet connection configurations at any time.
## Service details
### Ports
Each Port displays its speed, location, diversity zone (if applicable), and allocation percentage. This percentage reflects the amount of bandwidth defined for the Port that has been assigned to VXCs. For more information, see [Creating a Port](/connections/creating-port).
* **Service ID** -- A unique alphanumeric reference associated with each service. The service ID appears next to the Port name. Click the service ID to copy it to the clipboard, which can be useful when using the Megaport API to automate your Megaport service provisioning.
* **Service Diagnostics** -- Click the diagnostics icon to view the current operational status of the Port, including whether it is up or down, incoming and outgoing traffic, optical levels, any errors, any scheduled maintenance, and any active outages. The diagnostic displays the total number of attached connections and highlights any that are down or shut down.
* **Traffic Information**\
The diagnostics panel shows the current Incoming Traffic (data received by the service) and Outgoing Traffic (data sent by the service). To see traffic trends for the last 24 hours, click **Expand Graph**. Use the **In (Mbps)** and **Out (Mbps)** check boxes above the graph to show or hide each traffic series. Click **Collapse Graph** to hide the graph when you have finished.\
The graph is collapsed by default.
* **Optical Levels**\
For Ports with optical monitoring, the diagnostics panel includes an Optical Levels section that displays the current signal strength readings for the Port. The diagnostics panel also provides a health status indicator based on the signal readings, which can help you identify potential issues with the optical connection.
The signal strength readings include:
* **TX Power** – The transmit power level measured in dBm.
* **RX Power** – The receive power level measured in dBm.
The health status indicator shows:
* **Optical Signals Healthy** – Signal strength is within normal operating parameters.
* **Signal Strength Low** – One or more signal readings are below the recommended threshold. If you see this status, check your Cross Connect and [contact Support](/support/contact) for troubleshooting assistance.
To see how the optical readings have changed over the last 24 hours, click **Expand Graph**. Click **Collapse Graph** to hide the graph when you have finished. The graph is collapsed by default.
* **Errors**\
The diagnostics panel includes an Errors section that shows the current In errors/sec (errors received by the service) and Out errors/sec (errors sent by the service). To see how the error rates have changed over the last 24 hours, click **Expand Graph**. Use the **In (Errors/second)** and **Out (Errors/second)** check boxes to show or hide each error series. Click **Collapse Graph** to hide the graph when you have finished. The graph is collapsed by default.
* **Move Connections** -- Move any connections on the Port to a different Port.\
For more information, see [Moving VXCs](/connections/move-vxc).
* **Details** -- Click the gear icon to view or edit the configuration details, monitoring logs, usage, and billing information for a Port.
* **View Service on Map** -- Click the drop pin icon to view the Port on the map in the Megaport Portal dashboard. You can also create connections and maintain the Port. For more information, see [Megaport Portal Dashboard](/dashboard).
* **Service Keys** -- Click the key icon to generate and manage keys to connect Ports in separate Megaport accounts or deploy a VXC between two businesses. This icon is shown only when the Port is ready for a service key.\
For more information, see [Setting up Service Keys](/marketplace/service-keys).
* **Delete** -- Click the trash icon to terminate a Port and its associated connections. Port termination is immediate.\
For more information, see [Terminating a Port](/connections/terminating-port).
* **Lock** -- A Company Admin can click the padlock icon to lock a Port and prevent accidental modification or deletion. If an administrator has locked the Port, other users will see that it has been locked but only an administrator can unlock it. For more information, see [Locking Megaport Services](/portal-admin/locking).
* **+Connection** -- Click to establish a connection to a CSP, the internet (where available), an IX, a service provider on the Megaport Marketplace, or deploy a private VXC to another Port (local to the current company account). If you have a service key, you can connect Ports in separate Megaport accounts or enable a business-to-business VXC. For more information, see [Connections Overview](/connections/overview).
* **Hide/Show** -- Click the Hide/Show toggle to hide or show the connections on a Port.
### MCRs
Each MCR displays its rate limit, location, and allocation percentage. This percentage reflects the amount of bandwidth defined for the Port or MCR that has been assigned to VXCs. For more information, see [Creating an MCR](/mcr/creating-mcr).
* **Service ID** -- A unique alphanumeric reference associated with each service. The service ID appears next to the MCR name. Click the service ID to copy it to the clipboard, which can be useful when using the Megaport API to automate your Megaport service provisioning.
* **Service Diagnostics** -- Click the diagnostics icon to view the current operational status of the MCR, including whether it is up or down, incoming and outgoing traffic, any scheduled maintenance, and any active outages. The diagnostic displays the total number of attached connections and highlights any that are down or shut down, with links to troubleshooting resources.
* **Traffic Information**\
The diagnostics panel shows the current Incoming Traffic (data received by the service) and Outgoing Traffic (data sent by the service). To see traffic trends for the last 24 hours, click **Expand Graph**. Use the **In (Mbps)** and **Out (Mbps)** check boxes above the graph to show or hide each traffic series. Click **Collapse Graph** to hide the graph when you have finished.\
The graph is collapsed by default.
* **BGP Sessions**\
If your MCR has BGP sessions that are down, a drop-down **BGP Sessions** section will appear. Expand the **BGP Sessions** section, and click the BGP session name to link to the details page of the VXC associated with that session. Use this page to view the BGP configuration and monitoring logs for troubleshooting.
* **Ping and Traceroute**\
If your MCR is experiencing a routing issue, use the **Ping** and **Traceroute** tabs to test network connectivity and identify routing problems. For more information, see [Troubleshooting an MCR Routing Issue](/troubleshooting/mcr/routing).
* **Looking Glass** -- Click the binoculars icon for single-screen visibility into traffic routing. This visibility helps you troubleshoot connections by showing the status of protocols and routing tables in the MCR. For more information, see [Viewing Traffic Routing through MCR Looking Glass](/mcr/mcr-looking-glass).
* **Move Connections** -- Move any connections on the MCR to a different MCR.\
For more information, see [Moving VXCs](/connections/move-vxc).
* **Details** -- Click the gear icon to view and edit configuration details, service logs, and usage metrics for an MCR.
* **View Service on Map** -- Click the drop pin icon to view the MCR on the map in the Megaport Portal dashboard. You can also create connections and maintain the MCR. For more information, see [Megaport Portal Dashboard](/dashboard).
* **Delete** -- Click the trash icon to terminate an MCR and its associated VXCs. MCR termination is immediate. For more information, see [Terminating an MCR](/mcr/terminating-mcr).
* **Lock** -- A Company Admin can click the padlock icon to lock an MCR and prevent accidental modification or deletion. If an administrator has locked the MCR, other users will see that it has been locked but only an administrator can unlock it. For more information, see [Locking Megaport Services](/portal-admin/locking).
* **+Connection** -- Click to establish a connection to a CSP, the internet (where available), a service provider on the Megaport Marketplace, or deploy a private VXC to another Port (local to the current company account). If you have a service key, you can connect to Ports in separate Megaport accounts or enable a business-to-business VXC. For more information, see [Connections Overview](/connections/overview).
* **Hide/Show** -- Click the Hide/Show toggle to hide or show the connections on an MCR.
### MVEs
Each MVE displays its SD-WAN vendor, configured size, and location.
As part of the MVE provisioning, you create a Megaport Internet connection to provide connectivity and to allow MVE to register and communicate with the SD-WAN overlay network. You can also create a Megaport Internet connection at any time after the MVE has been provisioned. The Megaport Internet icon differs from a standard VXC icon in the Megaport Portal.
For more information, see the Megaport documentation for your SD-WAN provider: [MVE Overview](/mve).
* **Service ID** -- A unique alphanumeric reference associated with each service. The service ID appears next to the MVE name. Click the service ID to copy it to the clipboard, which can be useful when using the Megaport API to automate your Megaport service provisioning.
* **Service Diagnostics** -- Click the diagnostics icon to view the current operational status of the MVE, including whether it is up or down, incoming and outgoing traffic, any scheduled maintenance, and any active outages. The diagnostic displays the total number of attached connections and highlights any that are down or shut down.
* **Traffic Information**\
The diagnostics panel shows the current Incoming Traffic (data received by the service) and Outgoing Traffic (data sent by the service). To see traffic trends for the last 24 hours, click **Expand Graph**. Use the **In (Mbps)** and **Out (Mbps)** check boxes above the graph to show or hide each traffic series. Click **Collapse Graph** to hide the graph when you have finished.\
The graph is collapsed by default.
* **Move Connections** -- Move any connections on the MVE to a different MVE.\
For more information, see [Moving VXCs](/connections/move-vxc).
* **Details** -- Click the gear icon to view and edit configuration details, service logs, and usage metrics.
* **View Service on Map** -- Click the drop pin icon to view the MVE on the map in the Megaport Portal dashboard. You can also create connections and maintain the MVE. For more information, see [Megaport Portal Dashboard](/dashboard).
* **Delete** -- Click the trash icon to terminate the MVE and its associated VXCs. MVE termination is immediate. For more information, see the Megaport documentation for your SD-WAN provider: [MVE Overview](/mve).
* **Lock** -- A Company Admin can click the padlock icon to lock an MVE and prevent accidental modification or deletion. If an administrator has locked the MVE, other users will see that it has been locked but only an administrator can unlock it. For more information, see [Locking Megaport Services](/portal-admin/locking).
* **Console Access** -- Click to open the MVE Console in a new full-screen view. The console provides direct browser-based access to your MVE instance for troubleshooting, configuration, and system administration. For more information, see [Using the MVE Console](/mve/console-access).
* **Restart MVE** -- Click to restart the MVE instance. Restarting performs a clean shutdown and startup of the virtual machine, preserving its configuration. A confirmation screen is displayed before the restart proceeds. You can monitor the restart progress using the Service Diagnostics tool.
You must have at least Company Admin, Technical Admin, or Technical Contact privileges to perform this action. For more information, see [Managing User Roles](/portal-admin/user-management/roles).
* **+Connection** - Click to establish a connection to a CSP, the internet (where available), a service provider on the Megaport Marketplace, or deploy a private VXC to another Port (local to the current company account). If you have a service key, you can connect to Ports in separate Megaport accounts or enable a business-to-business VXC. For more information, see [Connections Overview](/connections/overview).
* **Hide/Show** -- Click the Hide/Show toggle to hide or show the connections on an MVE.
### NAT Gateways
Each NAT Gateway displays its rate limit, location, and allocation percentage. This percentage reflects the amount of bandwidth defined for the Port or NAT Gateway that has been assigned to VXCs. For more information, see [Creating a NAT Gateway](/nat/creating-nat-gateway).
* **Service ID** -- A unique alphanumeric reference associated with each service. The service ID appears next to the NAT Gateway name. Click the service ID to copy it to the clipboard, which can be useful when using the Megaport API to automate your Megaport service provisioning.
* **Service Diagnostics** -- Click the diagnostics icon to view the current operational status of the NAT Gateway, including whether it is up or down, incoming and outgoing traffic, any scheduled maintenance, and any active outages. The diagnostic displays the total number of attached connections and highlights any that are down or shut down, with links to troubleshooting resources.
* **Traffic Information**\
The diagnostics panel shows the current Incoming Traffic (data received by the service) and Outgoing Traffic (data sent by the service). To see traffic trends for the last 24 hours, click **Expand Graph**. Use the **In (Mbps)** and **Out (Mbps)** check boxes above the graph to show or hide each traffic series. Click **Collapse Graph** to hide the graph when you have finished.\
The graph is collapsed by default.
* **BGP Sessions**\
If your NAT Gateway has BGP sessions that are down, a drop-down **BGP Sessions** section will appear. Expand the **BGP Sessions** section, and click the BGP session name to link to the details page of the VXC associated with that session. Use this page to view the BGP configuration and monitoring logs for troubleshooting.
* **Ping and Traceroute**\
If your NAT Gateway is experiencing a routing issue, use the **Ping** and **Traceroute** tabs to test network connectivity and identify routing problems. For more information, see [Troubleshooting a NAT Gateway Routing Issue](/troubleshooting/nat/routing).
* **Looking Glass** -- Click the binoculars icon for single-screen visibility into traffic routing. This visibility helps you troubleshoot connections by showing the status of protocols and routing tables in the NAT Gateway. For more information, see [Viewing Traffic Routing through MCR Looking Glass](/mcr/mcr-looking-glass).
* **Move Connections** -- Move any connections on the NAT Gateway to a different NAT Gateway. For more information, see [Moving VXCs](/connections/move-vxc).
* **Details** -- Click the gear icon to view and edit configuration details, service logs, and usage metrics for a NAT Gateway.
* **View Service on Map** -- Click the drop pin icon to view the NAT Gateway on the map in the Megaport Portal dashboard. You can also create connections and maintain the NAT Gateway. For more information, see [Megaport Portal Dashboard](/dashboard).
* **Delete** -- Click the trash icon to terminate a NAT Gateway and its associated VXCs. NAT Gateway termination is immediate. For more information, see [Terminating a Megaport NAT Gateway](/nat/terminating-nat-gateway).
* **Lock** -- A Company Admin can click the padlock icon to lock a NAT Gateway and prevent accidental modification or deletion. If an administrator has locked the NAT Gateway, other users will see that it has been locked but only an administrator can unlock it. For more information, see [Locking Megaport Services](/portal-admin/locking).
* **+Connection** -- Click to establish a connection to a CSP, the internet (where available), a service provider on the Megaport Marketplace, or deploy a private VXC to another Port (local to the current company account). If you have a service key, you can connect to Ports in separate Megaport accounts or enable a business-to-business VXC. For more information, see [Connections Overview](/connections/overview).
* **Hide/Show** -- Click the Hide/Show toggle to hide or show the connections on a NAT Gateway.
### VXCs
Each VXC displays its name, rate limit, location, diversity zone, and whether the Port/MCR/MVE is at the A-End or B-End of the connection. For more information, see [Connections Overview](/connections/overview).
If you are at the A-End of the connection, and the connection is to a company on the Megaport Marketplace, it will display the logo, have a tooltip of the company name, and allow you to click the icon to view the details on the Megaport Marketplace. In this example, the VXC at the A-End is connected to AWS.
If you are at the B-End of the connection (and don't own the A-End), it will show the generic Megaport Marketplace logo (not clickable) and have a tooltip that says that you are at the B-End of a connection owned by another company.
* **Service ID** -- A unique alphanumeric reference associated with each service. The service ID appears next to the VXC name. Click the service ID to copy it to the clipboard, which can be useful when using the Megaport API to automate your Megaport service provisioning.
* **Service Diagnostics** -- Click the diagnostics icon to view the current operational status of the VXC, including whether it is up or down, incoming and outgoing traffic, any scheduled maintenance, and any active outages. The diagnostic displays the total number of attached connections and highlights any that are down or shut down.
* **Traffic Information**\
The diagnostics panel shows the current Incoming Traffic (data received by the service) and Outgoing Traffic (data sent by the service). To see traffic trends for the last 24 hours, click **Expand Graph**. Use the **In (Mbps)** and **Out (Mbps)** check boxes above the graph to show or hide each traffic series. Click **Collapse Graph** to hide the graph when you have finished.\
The graph is collapsed by default.
* **Move Connection** -- Move the VXC to a different location. The move can only be to a service of the same type. For example, Port to Port, MCR to MCR, or MVE to MVE. For more information, see [Moving VXCs](/connections/move-vxc).
* **Details** -- Click the gear icon to view the configuration details, monitoring logs, usage, and billing information. The gear icon will be displayed in blue if the VXC has been shut down. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
* **View Service on Map** -- Click the drop pin icon to view and maintain the VXC on the map in the Megaport Portal dashboard. For more information, see [Megaport Portal Dashboard](/dashboard).
* **Delete** -- Click the trash icon to terminate a VXC. VXCs can be individually terminated or are terminated as part of terminating the attached Port, MCR, or MVE. For more information, see [Terminating a VXC](/connections/terminating-vxc).
* **Lock** -- A Company Admin can click the padlock icon to lock a VXC and prevent accidental modification or deletion. If an administrator has locked the VXC, other users will see that it has been locked but only an administrator can unlock it. For more information, see [Locking Megaport Services](/portal-admin/locking).
### Megaport Internet connections
Each Megaport Internet connection displays its name, rate limit, location, diversity zone, and shows that the Port/MCR/MVE is at the A-End of the connection. For more information, see [Megaport Internet Overview](/megaport-internet).
* **Service ID** -- A unique alphanumeric reference associated with each service. The service ID appears next to the Megaport Internet connection name. Click the service ID to copy it to the clipboard, which can be useful when using the Megaport API to automate your Megaport service provisioning.
* **Service Diagnostics** -- Click the diagnostics icon to view the current operational status of the Megaport Internet connection, including whether it is up or down, incoming and outgoing traffic, any scheduled maintenance, and any active outages. The diagnostic displays the total number of attached connections and highlights any that are down or shut down.
* **Traffic Information**\
The diagnostics panel shows the current Incoming Traffic (data received by the service) and Outgoing Traffic (data sent by the service). To see traffic trends for the last 24 hours, click **Expand Graph**. Use the **In (Mbps)** and **Out (Mbps)** check boxes above the graph to show or hide each traffic series. Click **Collapse Graph** to hide the graph when you have finished.\
The graph is collapsed by default.
* **Move Connection** -- Move the Megaport Internet connection to a different location. The move can only be to a service of the same type. For example, Port to Port, MCR to MCR, or MVE to MVE. For more information, see [Moving VXCs](/connections/move-vxc).
* **Details** -- Click the gear icon to view the configuration details, monitoring logs, usage, and billing information.
* **View Service on Map** -- Click the drop pin icon to view and maintain the Megaport Internet connection on the map in the Megaport Portal dashboard. For more information, see [Megaport Portal Dashboard](/dashboard).
* **Delete** -- Click the trash icon to terminate a Megaport Internet connection. Megaport Internet connections can be individually terminated or are terminated as part of terminating the attached Port, MCR, or MVE. For more information, see [Terminating a Megaport Internet Connection](/megaport-internet/terminating-connection).
* **Lock** -- A Company Admin can click the padlock icon to lock a Megaport Internet connection and prevent accidental modification or deletion. If an administrator has locked the connection, other users will see that it has been locked but only an administrator can unlock it. For more information, see [Locking Megaport Services](/portal-admin/locking).
### IXs
Each IX displays its name, rate limit, and location. For more information, see [Internet Exchange Overview](/ix).
* **Service ID** -- A unique alphanumeric reference associated with each service. The service ID appears next to the IX name. Click the service ID to copy it to the clipboard, which can be useful when using the Megaport API to automate your Megaport service provisioning.
* **Service Diagnostics** -- Click the diagnostics icon to view the current operational status of the IX, including whether it is up or down, incoming and outgoing traffic, any scheduled maintenance, and any active outages. The diagnostic displays the total number of attached connections and highlights any that are down or shut down, with links to troubleshooting resources.
* **Traffic Information**\
The diagnostics panel shows the current Incoming Traffic (data received by the service) and Outgoing Traffic (data sent by the service). To see traffic trends for the last 24 hours, click **Expand Graph**. Use the **In (Mbps)** and **Out (Mbps)** check boxes above the graph to show or hide each traffic series. Click **Collapse Graph** to hide the graph when you have finished.\
The graph is collapsed by default.
* **IX Telemetry** -- Click the telemetry icon to view the peering rates of the IX. Use IX Telemetry to view and analyze your network traffic flow statistics, check whether a peer is using a lot of network traffic, and diagnose and troubleshoot any configuration or networking issues. For more information, see [IX Telemetry](/ix/ix-telemetry).
* **Move Connection** -- Move the A-End of the IX to a different Port.\
For more information, see [Moving IXs](/ix/move-ix).
* **Details** -- Click the gear icon to view the configuration details, monitoring logs, usage, and billing information. The gear icon will be displayed in blue if the IX has been shut down. For more information, see [Shutting Down an IX for Failover Testing](/ix/shutting-down-an-ix).
* **View Service on Map** -- Click the drop pin icon to view and maintain the IX on the map in the Megaport Portal dashboard. For more information, see [Megaport Portal Dashboard](/dashboard).
* **Delete** -- Click the trash icon to terminate an IX. IXs can be individually terminated or are terminated as part of terminating the attached Port. For more information, see [Terminating an IX](/ix/terminating-an-ix).
* **Lock** -- A Company Admin can click the padlock icon to lock an IX and prevent accidental modification or deletion. If an administrator has locked the IX, other users will see that it has been locked but only an administrator can unlock it. For more information, see [Locking Megaport Services](/portal-admin/locking).
# Megaport Portal Design Changes
Source: https://docs.megaport.com/portal-design-changes/index
This help topic describes new Megaport Portal designs to provide timely update to customers.
Megaport is rolling out a new layout for the Megaport Portal as part of our ongoing effort to make the Portal easier and more intuitive to use.
We have introduced a refined Services page layout, helping you find information more quickly, manage services more efficiently, and gain a clearer view of your network. For a summary of the changes, see the [Release Notes](/whatsnew) and the Portal ‘What’s New' announcement.
These design changes do not affect existing service functionality. Any new features or changes to existing functionality are documented separately in the [Megaport Documentation](/megaport).
Watch the following short videos to learn about the new Portal designs.
## Services page
### New Services page
You can switch between the new and old views by clicking the toggle button in the upper-right corner.
The old view will be deprecated in the near future. We recommend that all users switch to the new layout to familiarize themselves with the updated experience.
### Navigation menu
### Company settings
### New Services page layout
### Filters, sort by, and global actions
### Actions
### Connections
### Add services
## Helpful references
* [July 2026 Release Notes](/whatsnew#july-2026)
* [June 2026 Release Notes](/whatsnew#june-2026)
* [Understanding the Services Page](/portal-admin/services-page)
# Megaport Products Overview
Source: https://docs.megaport.com/products/index
This help topic introduces the products and services available on the Megaport network.
This topic introduces the products and services available on the Megaport network. For an introduction to the Megaport network itself, see [Introducing Megaport](/overview).
There's a simple pattern to how these products fit together:
1. **Get on the Megaport Network** -- Create a [Port](/connections/creating-port), [Megaport Cloud Router (MCR)](/mcr), or [Megaport Virtual Edge (MVE)](/mve) as your general-purpose entry point onto the Megaport **network**. If you need devices in a private network to reach the internet without exposing individual public IP addresses, provision a [Megaport NAT Gateway (NAT Gateway)](/nat) as another entry point instead.
2. **Connect** -- Deploy a [Virtual Cross Connect (VXC)](/connections/overview) from your entry point to wherever you need to go. Browse the [Megaport Marketplace](/marketplace/overview) to find service providers already on the network.
3. **Go anywhere** -- Use the VXC to reach cloud regions, the public internet, internet exchanges, or [Megaport Object Storage](/storage/object), Megaport's **Storage** offering. For cloud service provider connectivity, see [Cloud Connectivity](/cloud/megaport).
Megaport also offers **Compute**, on-demand CPU and GPU access through the same Latitude.sh platform that powers Megaport Object Storage. For more information, see [Megaport Compute](https://www.megaport.com/solutions/compute/).
## Products
Megaport offers these products:
* **[Port](/connections/creating-port/)** -- High-speed Ethernet interface that connects to the Megaport network, available in a range of capacities depending on the location and Port type.
* **[Virtual Cross Connect (VXC)](/connections/overview)** -- Connection between any two endpoints on the Megaport network. Most connections support capacity ranging from 1 Mbps to several Gbps. Higher-capacity Ports in some metros can support much greater speeds, depending on the network configuration.
* **[Megaport Cloud Router (MCR)](/mcr/)** -- Virtual router for on-demand, private, Layer 3 connectivity to service providers between key global routing zones.
* **[Megaport Virtual Edge (MVE)](/mve/)** -- On-demand Network Functions Virtualization service that supports branch-to-cloud connectivity on the Megaport SDN. MVE provides the edge-computing framework to deploy SD-WAN gateways, virtual routers, and integrated transit gateways.
* **[IP Address](/ip-address/)** -- A standalone public IPv4 or IPv6 subnet that you order, manage, and link to your Megaport Internet connections.
* **[Internet Exchange (IX)](/ix/)** -- Connect to content and services across multiple regions, exchanging traffic directly and reducing bandwidth usage on client internet connections.
* **[Megaport Internet](/megaport-internet/)** -- A scalable, on-demand service that allows you to connect to the internet from Ports, MCRs, and MVEs. As part of the MVE provisioning, you create a Megaport Internet connection to provide connectivity and to allow MVE to register and communicate with the SD-WAN overlay network.
* **[Megaport Object Storage](/storage/object/)** -- S3-compatible object storage provisioned on Latitude.sh and connected to the Megaport network through a dedicated VXC.
* **[Megaport NAT Gateway (NAT Gateway)](/nat/)** -- A NAT service that enables devices in a private network to access the internet without requiring each device to have a public IP address.
* **[Megaport Marketplace](/marketplace/overview)** -- An online hub where global service providers and enterprise customers interconnect, so you can connect to a broad range of internet services, cloud providers, and managed services.
To get started, select a product from the side navigation.
## Helpful references
* [Common Multicloud Connectivity Scenarios](/deployment/multicloud)
* [Modernizing Your MPLS Network with Megaport Solutions](/deployment/wan-replacement)
* [Megaport On-ramp as a Service](/deployment/onramp-as-a-service)
# Service Provisioning Methods
Source: https://docs.megaport.com/provisioning-methods/index
This help topic describes suitable users and scenarios for the Portal, API, Terraform, and CLI service provisioning methods.
Megaport offers various methods for provisioning and managing services: the Portal, API, Terraform, and CLI. The optimal choice depends on the customer's need for automation, the complexity of the deployment, and the user's role.
The table below provides a quick-reference guide to suitable users and scenarios for each method.
| **Method** | **Key Benefits** | **Use Cases** | **Typical Users** |
| - | - | - | - |
| Portal |
Easiest to use (web-based GUI)
No coding required
Quick testing and provisioning
|
Manual, one-off deployments or simple, non recurring changes (for example, provisioning a single VXC) and demos
Low frequency deployments
|
Graphical UI Users
Network Engineers
Account Managers
|
| API |
Full programmatic control and flexibility
Customer app integration such as existing billing, provisioning, or network management systems
|
Integrating Megaport services into a customer application or proprietary portal
Integrates provisioning with existing Continuous Integration (CI) and Continuous Deployment (CD) pipelines
Disaster Recovery (DR) and High Availability (HA) by quickly rebuilding resources in a different region or cloud
|
Cloud Architects
DevOps Engineers
Platform Engineers
|
| Megaport CLI |
Speedy and efficient network management
JSON-driven automation-first design
One tool manages diverse multicloud connectivity without console-switching
Consistent, repeatable and flexible deployment
|
Integrates provisioning with existing CI and CD pipelines
Rapid provisioning. Useful during change windows where time is critical
Define multicloud topology in JSON and deploy it across regions with a single script
Script health checks and reporting
Disaster recovery and environment replication
|
Cloud Architects
DevOps Engineers
Platform Engineers
Network Engineers
|
If an organization chooses to adopt Terraform to manage certain Megaport services, it must commit to using Terraform exclusively for those services.
Mixing service management via the Megaport Portal and/or API with Terraform will inevitably cause Terraform state drift. That is, the Terraform state will become inconsistent with the actual infrastructure configuration managed through the Portal and cause Terraform errors. For more information, see [ Understanding Terraform state for Megaport resources](/terraform/terraform-state-management#understanding-terraform-state-for-megaport-resources).
## Choosing your Megaport services provisioning method
### Megaport Portal (UI)
The Portal is the ideal choice for manual, visual configuration and quick, hands-on management. It offers the fastest path to provisioning for one-off needs.
Choose the Portal when you need to:
* Quickly provision a service manually for immediate use.
* Conduct initial setups, demos, or training on new features.
* Perform a one-time deployment that doesn't require version control.
* Prefer a visual, click-through workflow rather than system integration.
### Megaport API
The API is best suited for achieving dynamic automation and system integration. It allows teams to build custom logic that interacts directly with Megaport services without requiring a user interface login.
Choose the API when you need to:
* Build a custom application or orchestrator for provisioning.
* Enable event-driven or dynamic configuration based on internal business logic.
* Perform frequent, programmatic configuration updates across services.
* Integrate Megaport provisioning into a large, existing internal system or customer-facing platform.
### Terraform (Infrastructure as Code - IaC)
Terraform is the preferred method for users who require auditable, repeatable, and version-controlled deployments at scale. It offers full control over the lifecycle of your infrastructure.
Choose Terraform when you need to:
* Implement Infrastructure as Code (IaC) for your network resources.
* Manage services across multiple environments (dev, staging, production) reliably.
* Connect to multiple clouds or manage large-scale hybrid environments.
* Ensure a standardized, auditable, and repeatable process for network builds and governance.
### Megaport CLI
The Megaport CLI is the preferred method for users who require high-speed, automated network management and integration into CI and CD pipelines. It supports technical teams deploying multicloud topologies through single-command scripts, ensuring consistent and repeatable configurations across global environments.
Choose Megaport CLI when you need to:
* Enable rapid provisioning and streamlined management.
* Integrate with CI and CD pipelines via JSON-driven workflows for consistent, repeatable deployments.
* Manage diverse cloud connectivity from a single interface, eliminating console switching.
* Use scripts for network deployment while enabling health checks and disaster recovery.
## Helpful references
* [Master the Megaport CLI](https://tutorials.megaport.com/cli/)
* [Megaport API Overview](/api)
* [Megaport CLI Overview](/cli)
* [Megaport Terraform Provider Overview](/terraform)
* [Quick Start Guide](/getting-started)
* [Understanding the Services Page](/portal-admin/services-page)
# Resetting Your Password
Source: https://docs.megaport.com/setting-up/change-password
This help topic describes how to reset your Megaport account password if you have forgotten it, or if you need to for security purposes.
After you have a Megaport account, you might occasionally need to reset your login password. For example, you might have forgotten your password or the password needs to be reset for security purposes.
This is also required when a Company Admin invites other users to the Megaport account.
There is a maximum of between five and 20 password reset requests that a user can attempt per hour. The exact maximum number of attempts will vary, depending on the risk parameters associated with the requests. This behavior is subject to change. If you exceed the maximum number of password reset attempts, a *Password Reset - Request Failed* error message will appear.
Where Single Sign-On (SSO) is enabled, the **Forgot Password** option only resets your local Megaport account password, not your SSO IdP password.
**To reset your password**
1. Visit the Megaport Portal, enter your email address then click **Continue**.
2. Click **Forgot Password**.
3. In the **Email** field, enter your email address then click **Reset Password**.
A message appears, stating that if the account exists, an email will be sent to reset your password. The email will include instructions for resetting your password.
4. Click **OK** to close the Password Reset prompt.
5. Click **Reset Your Password** in the email that you received.\
The link is valid for one hour.
6. In the Reset Password screen, enter and confirm your new password.
The Megaport Portal password policy includes minimum password complexity rules. Your new password must contain:
* At least 8 characters
* Uppercase characters (A-Z)
* Lowercase characters (a-z)
* Numbers (0-9)
* At least one special character: ^ \$ \* . \[ ] ( ) ? " ! @ # % & / \ , > \< ' : ; | \_ \~ \` = + -
The password policy uses a password strength estimator to prevent common, easily guessed passwords, such as Passw0rd. If you have met all complexity requirements and your password is still being rejected, the likely cause is that the password is too common or easy to guess.
7. Click **Reset Password**.\
The Password Changed OK prompt appears.
8. Click **OK**.\
You can now log in to the Megaport Portal with your new password.
# Updating a Company Profile
Source: https://docs.megaport.com/setting-up/company-profile
This help topic describes how to update your company profile in the Megaport Portal.
Your company profile includes your account name and unique account identifier.
Entering an account name is mandatory when signing up for a Megaport account. However, you can change the account name defined for your company profile.
The account name is the name the public sees, not the legal name of your company.
**To update a company profile**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Company Profile.
3. Edit your account name.
4. Click **Save**.
# Multi-Factor Authentication
Source: https://docs.megaport.com/setting-up/enforcing-mfa
This help topic describes Multi-Factor Authentication (MFA) and how to set up MFA for users to log in to the Megaport Portal.
If you are having trouble creating a new Megaport account, or logging in to an existing account, see [Megaport Portal Authentication Frequently Asked Questions (FAQs)](/troubleshooting/signup-login-faq).
This topic describes how to set up Multi-Factor Authentication (MFA) for users to log in to the Megaport Portal. It also describes how to reset MFA for your users, and how to review the MFA status of all users in your company.
MFA is enabled by default for all new Megaport accounts created after March 16 2026.
## About Multi-Factor Authentication
There are various security risks associated with identity facing businesses. Employees using weak passwords, or the same passwords for multiple accounts, can leave organizations vulnerable to breaches and cyber criminal activity. Multi-Factor Authentication (MFA) can help organizations deal with these issues. It makes life easier for employees, allowing them to more easily manage their different accounts securely. It also gives administrators greater visibility and control over identity management, and helps organizations achieve legal compliance with data regulations.
MFA is an authentication method and security system that ensures all of your business accounts require more than one verification factor before they can be accessed. For example, a username and password, and a code from an authentication app. MFA is a core component of a strong identity and access management (IAM) policy, and provides an extra level of security for your Megaport Portal account. We recommend that you use the Google Authenticator app when securing your accounts with MFA.
Each user should install a login verification app (such as Google Authenticator) on their digital device (phone, tablet, computer, and so on). When users log in, they check the login verification app for the token or code that they need to enter as the additional factor.
MFA is mandatory, so your users must enable MFA on their login, if not already set up. They will not be able to log in to the Megaport Portal until they do so. For more information about enabling MFA for your user account and logging in, see [Managing Your User Profile](/setting-up/manage-profile) and [Logging in to the Megaport Portal](/setting-up/logging-in).
It is not recommended to access Megaport APIs using MFA with a username, password, and token. Although this is technically possible, we recommend to instead use API keys as the preferred authentication method when using Megaport APIs. If you currently have any user accounts being used for API, we recommend changing these to API keys before enforcing MFA. For more information, see [Creating an API Key](/api/api-key).
### MFA benefits
The main benefit of MFA is that it enhances your organization's security by requiring your users to identify themselves by more than a username and password. By themselves, usernames and passwords are vulnerable to cyber attacks and can be stolen by third parties. Enforcing the use of an additional verification factor such as a code from an authentication app increases the ability of your organization to remain safe from attacks from cyber criminals.
Full benefits of MFA include:
* Improved security
* Protection against unauthorized account access if credentials or devices are stolen
* Regulatory compliance
### MFA and Single Sign-On (SSO)
MFA provides additional security to reduce the possibility of unauthorized access through stolen credentials, by requiring multiple authentication factors. SSO allows organizations to simplify and strengthen security because users can access all connected services with a single login.\
MFA is mandatory unless your company is using SSO. If your company is using SSO, you will not be required to use MFA to log in to the Megaport Portal. For more information about SSO, see [Setting up Single Sign-On](/setting-up/enforcing-sso).
## Administering MFA for your Company account
To administer MFA for your company account, you must be a Company Admin. If you are not a Company Admin, contact your company’s administrator to request changes to the MFA settings for your company account.
MFA can introduce new administrative responsibilities to support users, so we highly recommend that you assign a minimum of two Company Admins to help users troubleshoot and resolve authentication issues quickly.
For more information about user roles, see [Managing User Roles](/portal-admin/user-management/roles).
Megaport Support cannot reset MFA tokens on the customer's behalf. Company Admins will need to manage tokens.
These rules apply for the different types of Megaport Portal accounts.
| **Account Type** | **Who Can Administer MFA?** |
| :- | :- |
| Direct | A Company Admin can administer MFA. |
| Partner | A Company Admin can administer MFA for their own partner account. A Company Admin can administer MFA for any of their managed accounts. |
| Managed | A Company Admin can administer MFA for their own account. |
## Resetting MFA for your users
The MFA setting of individual users can be reset. As a Company Admin, you might need to do this so that a user can enroll a new device. This disables the previous MFA code and the user will be asked to enable MFA again the next time that they log in to the Megaport Portal.
**To reset MFA for a user**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Manage Users.
3. Find the user you want to update.
4. Click (Edit) for the required user.
5. Click **Reset** in the Multi-Factor Authentication area.\
A confirmation prompt is displayed. The user account for which you are resetting MFA must be a real user and not set up for any automated process, because the user will need to log in again and enable MFA for the account.
6. Click **OK**.
7. Click **Close** to close the Edit User screen.\
The next time that the user logs in to the Megaport Portal, they will need to enable MFA again. For more information, see [Logging in after MFA has been reset for your profile](/setting-up/logging-in#logging-in-after-mfa-has-been-reset-for-your-profile).
## Helpful references
* [Logging in to the Megaport Portal](/setting-up/logging-in)
* [Managing Your User Profile](/setting-up/manage-profile)
* [Managing Security Settings](/portal-admin/security-settings)
* [Setting up Single Sign-On](/setting-up/enforcing-sso)
# Setting up Single Sign-On
Source: https://docs.megaport.com/setting-up/enforcing-sso
This help topic describes how a Company Admin can configure identity provider (IdP) details and make it mandatory for users to log in to the Megaport Portal with Single Sign-On (SSO).
If you are having trouble creating a new Megaport account, or logging in to an existing account, see [Megaport Portal Authentication Frequently Asked Questions (FAQs)](/troubleshooting/signup-login-faq) and [Single Sign-On (SSO) Frequently Asked Questions (FAQs)](/troubleshooting/sso-faq) for commonly asked questions and answers.
See your identity provider's website for further setup instructions, help with fault resolution, and privacy policies.
This topic describes how a Company Admin can configure identity provider (IdP) details and then make it mandatory for users to log in to the Megaport Portal with Single Sign-On (SSO). It also describes how a Company Admin can review the SSO configuration details for their company.
## About Single Sign-On
There are various security risks associated with identity-facing businesses. Employees using weak passwords, or the same passwords for multiple accounts, can leave organizations vulnerable to breaches and cyber criminal activity. Single Sign-On (SSO) can help organizations deal with these issues. It makes life easier for employees, allowing them to more easily manage their different accounts securely. It also gives administrators greater visibility and control over identity management, and helps organizations achieve legal compliance with data regulations.
SSO is an identity and access management solution that allows users to log in to multiple applications, websites, and software systems with one-time user authentication. That is, SSO allows users to log in once and access multiple services without having to authenticate again.
SSO provides both improved security to organizations and an enhanced user experience. Users can access all applications to which they are entitled, without the need to log in and authenticate multiple times once their identity is validated. It also allows administrators to more easily manage user identity and access.
When you set up SSO for your company, your users will be able to log in to the Megaport Portal using SSO. You first need to enable SSO by adding an identity provider (IdP) in the Megaport Portal, which is the third-party service provider that manages user identity. Once enabled, your existing users will default to using SSO if their email address is tied to your external IdP. This is optional after initially enabling SSO, however, as a Company Admin you can enforce SSO login for all your users. For more information about logging in, see [Logging in to the Megaport Portal](/setting-up/logging-in).
### SSO benefits
Using SSO benefits users and organizations in the following ways:
* **Provides a better customer experience** -- SSO provides users with a single login experience and simplifies access and identity management. Users require fewer passwords and can still securely access the applications they need to perform their job function.
* **Improves password and network security** -- Where SSO is not used, users need to remember and manage multiple login passwords for various applications. This can lead to insecure passwords and security practices that are not recommended. For example, using the same password for multiple applications. Using SSO prevents these password issues and requires a strong password that is used for validation across multiple applications.
* **Increases administrative control** -- All user access management information is stored in a single location. This means there is only one source of each user’s access rights and privileges. Administrators can change a user’s privileges once and know that the settings will update organization-wide.\
Individual user permissions within the Megaport Portal are controlled by Megaport's internally defined roles, not the roles the user has in their IdP.
* **Improves productivity** -- Users often access multiple applications that each require separate authentication to log in. Manually entering a username and password every time is unproductive, especially if technical issues are encountered. SSO helps to streamline the authentication process and remove unnecessary time-consuming activities.
### SSO and Multi-Factor Authentication (MFA)
SSO allows organizations to simplify and strengthen security because users can access all connected services with a single login. MFA provides additional security to reduce the possibility of unauthorized access through stolen credentials by requiring multiple authentication factors.\
If you use SSO, you will not need to use MFA. The only time MFA will be required is if your company uses SSO, but you log in with email and password.
## Who can enforce SSO globally for an account?
To enforce SSO globally for an account, you must be a Company Admin within the account.
* Before implementing SSO, make sure to prepare all users associated with your Megaport account by communicating what SSO is, why it is being implemented, and whether SSO is optional or required.
* Because enforcing SSO can introduce new administrative responsibilities to support users, we highly recommend that you assign a minimum of two Company Admins to help users troubleshoot and resolve authentication issues quickly.
* See your identity provider's website for further setup instructions, help with fault resolution, and privacy policies.
These rules apply for the different types of Megaport Portal accounts:
| **Account Type** | **Who Can Enforce SSO?** |
| :- | :- |
| Direct | A Company Admin can enforce SSO globally or make it optional. |
| Partner | A Company Admin can enforce SSO globally or make it optional for their own partner account.
A Company Admin can enforce SSO globally or make it optional for any of their managed accounts. Changing the SSO setting for one managed account does not affect any other managed accounts. |
| Managed | A Company Admin can enforce SSO globally or make it optional for their own account. Partners can change this setting if they are a Company Admin. |
## Adding an identity provider (IdP)
An IdP is a trusted third-party company or service that manages an organization’s user identity.
IdPs provide authentication services to third-party service providers (such as applications, websites, or other digital services) by validating the identity and authenticating a user to the application using the identity the IdP manages, without sharing login details. An SSO service uses an IdP to check user identity at log in, but does not store the user identity.
To enable SSO in the Megaport Portal, you need to add an IdP connection. Each company can have a maximum of one IdP (SAML) connection. After you have added a connection, you can also modify and delete the connection.
The Megaport Portal communicates with the IdP and creates connections using SAML 2.0.
See your identity provider's website for further setup instructions, help with fault resolution, and privacy policies.
* Only SAML based SSO is supported.
* Currently only one IdP (SAML) connection can be configured in Megaport per company.
* Only Company Admins can make changes to SSO settings. Other users do not have access to this section in the Megaport Portal.
**To add an IdP connection**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Security Settings.
The Integration details area of the screen includes the **Audience URI** and **IdP Response URL** fields. To ensure that your SSO configuration is complete, you need to integrate your IdP with the Audience URI (Entity ID, Audience) and IdP Response URL (Assertion Consumer Service (ACS) URL, Single Sign-On URL, Application Callback URL, Reply URL) values listed on this screen. These are Megaport-generated values and are essential components required for SAML SSO authentication to work correctly.
3. Click the Copy icon for both **Audience URI** and **IdP Response URL** values and paste them into a safe location.
* **Audience URI** -- Also known as Entity ID, this field defines the entity or audience for which the SAML assertion is intended. This value is usually a URL that contains the IdP's name. It is a unique identifier for your application.
* **IdP Response URL** -- Also known as Assertion Consumer Service (ACS) URL, Single Sign-On URL, Application Callback URL, and Reply URL, this field defines the URL to which your users will be directed for logging in.
4. Click **Add SAML Connection**.
5. Read the information in the [SSO Features and Instructions for Use](/troubleshooting/sso-terms-conditions) topic.\
This topic provides guidance on setup, and important information about Single Sign-On.
6. Provide these details:
* **Provider Name** -- The name of the IdP connection. This is a user-defined name that will be shown in the Megaport Portal for the connection. The name cannot be changed after the connection is created.
* **Domains** -- The specific domains that will be handled by this IdP connection. Multiple domains separated by a comma are accepted. For example, *megaport.com,gmail.com*
* **Metadata source** -- Select how to provide the IdP metadata.
* **Metadata URL** -- Enter the URL to download the IdP metadata file. The metadata file is an XML document that contains information required for interaction with the IdP, such as identifiers, endpoint URLs, and public keys.
* **Metadata file** -- Upload a static XML metadata file from your IdP. Use this option if your IdP metadata endpoint is not accessible from the internet.\
Click **Metadata file** and select a valid XML file (.xml) from your local system.
* **Attribute mapping** -- Attributes or fields that need to be mapped from the IdP to Megaport. SSO attribute mapping matches the attribute values of a user's profile maintained by the IdP, to the Megaport Portal user profile attribute values. As different systems use different attribute values and authentication methods, the data must match between the IdP and Megaport Portal.\
For more information about attribute mapping requirements for your IdP, see your IdP's website and documentation.
7. Click **Save**.\
To ensure that your SSO configuration is complete, you now need to integrate your IdP with the Audience URI (Entity ID) and IdP Response URL (ACS URL) values that you copied earlier.
8. Set up the Megaport-generated Audience URI and Response URL values in your IdP configuration. For instructions on how to do this for your IdP service provider, see the IdP documentation.\
After this has been done, your users can log in to the Megaport Portal using SSO. For more information, see [Logging in to the Megaport Portal](/setting-up/logging-in).
**To modify an IdP connection**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Security Settings.
3. In the Actions column for the configured connection, click **Edit**.\
The Single Sign-On connection details display. When modifying an IdP connection, you can only change the domains or attribute mapping values.
4. In the **Domains** field, update the specific domains for which to configure SSO. Multiple domains separated by a comma are accepted.
5. In the Attribute mapping area, update any attributes or fields that need to be mapped from the IdP to Megaport.
6. Click **Save**.
**To delete an IdP connection**
You can delete an IdP connection, for example, if your company decides to change IdP service providers. If an IdP connection is deleted, users will no longer be able to log in to the Megaport Portal through that IdP. User authentication will revert to what was set previously, and users can still log in using other authentication methods.
* If SSO enforcement is enabled, it will become disabled. For more information, see [Making SSO mandatory for users](#enforce-sso).
* If an active user has only ever logged in using SSO, they can use the Forgot Password link on the login screen to reset their password for their username/password profile, then log in using username and password. For more information, see [Resetting Your Password](/setting-up/change-password) and [Logging in to the Megaport Portal](/setting-up/logging-in).
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Security Settings.
3. In the Actions column for the configured connection, click **Delete**.\
The Delete Provider prompt displays.
4. Read the prompt and make sure that you want to delete the IdP connection.
5. Click **Delete**.\
The IdP connection is deleted.
## Making SSO mandatory for users
After you have configured an IdP connection for your company to enable SSO, you can enforce SSO. As a Company Admin, changing your company's global SSO preference from optional to enforced ensures that all users accessing your company in the Megaport Portal are logging in using SSO.
When SSO is enforced, all users must authenticate using the configured IdP. If a user has logged in to the Megaport Portal before using username and password, and a Company Admin adds an IdP connection and enforces SSO, then as long as the user's email has a domain that matches the IdP, they will be redirected to the external IdP on the next login.
One exception to this is Company Admins who can still log in with other methods, even without an SSO-associated domain.
For more information about logging in using SSO, see [Logging in to the Megaport Portal](/setting-up/logging-in).
**To make SSO mandatory for users**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Security Settings.
3. Click the slide button to **ON**.\
A message is displayed stating that once SSO enforcement is ON, all users must authenticate using the configured IdP.
4. Click **Save**.\
SSO is now set to ON and enforced globally for all users when logging in to the Megaport Portal.
## Making SSO optional for users
You can make SSO optional for your users (turn enforcement off). Users will still need to log in using SSO by default if their email address is associated with your external IdP, however, all users have the option to log in to the Megaport Portal using any approved authentication method, including Google, direct username and password, or SSO.
Optional (OFF) is the default SSO setting, however, SSO might have been enforced for your company at some stage. This task assumes that SSO is currently enforced (ON) and you want to change the setting back to Optional (OFF).
**To make SSO optional for users**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Security Settings.
3. Click the slide button to **OFF**.\
A message is displayed stating that once SSO enforcement is OFF, users can use different authentication methods to log in, including username and password, Google, or SSO.
4. Click **Save**.\
SSO enforcement is now set to OFF (optional).
## Reviewing the SSO details of your company
As a Company Admin, you can view the SSO configuration details for your company. For example, this allows you to review and validate that the SSO IdP details set up against your account are correct before enforcing SSO.
These SSO details are displayed:
* **Provider Name** -- The user-defined name of the IdP connection that has been configured.
* **Domains** -- The specific domains for which SSO has been configured. Multiple domains separated by a comma are accepted. For example, *megaport.com,gmail.com*
* **Metadata URL or Metadata file** -- If you configured the IdP using a metadata URL, the URL is displayed. If you uploaded a metadata file, the message 'Metadata was provided via file upload' is displayed instead.
* **Attribute mapping details** - Attributes or fields that have been mapped from the IdP to Megaport.
**To review the SSO details of your company**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Security Settings.
The *Provider Identity* column shows the user-defined name of the IdP connection that has been configured, the *Type* column shows the type of SSO configured, and the Actions column shows the valid actions associated with your role.
* Only SAML based SSO is supported.
* Currently only one IdP connection can be configured in Megaport.
* Only Company Admins can see this page.
3. Click **Edit** to review the SSO details configured for your company.
## Reviewing the SSO status of your users
As a Company Admin, you can view the current state of enforcement of SSO credentials for your users who have access to log in to the Megaport Portal. This allows you to manage the security risk profile for users with access to Megaport services.
These icons are displayed when SSO is configured:
| **Icon** | **Description** |
| :- | :- |
| | The user's email domain is linked to an SSO domain and they will use SSO by default when logging in to the Megaport Portal. |
| | The user's email domain is not associated with an SSO domain, however, the user can log in to the Megaport Portal with other authentication methods. That is, username and password, and Google. |
| | SSO is enforced for the company and the user is not SSO compatible. Access is prohibited and the user will not be able to log in to the Megaport Portal. |
**To review the SSO status of your users**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Manage Users.
3. The *Role* column shows the role that the user has within the company, and the *SSO Compatibility* column shows the SSO status of the user's account. Click the up and down arrows next to the column name to sort by user role or SSO status, or any of the available columns.
## Helpful references
* [Logging in to the Megaport Portal](/setting-up/logging-in)
* [Managing Security Settings](/portal-admin/security-settings)
* [Multi-Factor Authentication](/setting-up/enforcing-mfa)
# Setting Up Financial Details
Source: https://docs.megaport.com/setting-up/finance-basics
This help topic describes the basic requirements for adding billing information to your account.
Before you can start ordering services, you need to set up these basic financial details.
You set up the finance information after you create your company profile.
The [Billing Overview](/finance/overview) of this site provides detailed information about invoices and payments.
## Enable a billing market
Before you can order services in a region, you need to enable a billing market. We recommend that you enable multiple markets to cover your business needs.
For example, if your business operates in the US and Australia, enable billing markets for those two countries.
Without an enabled billing market, you can still create a shopping cart and view pricing, but you won't be able to submit an order.
For more information, see [Enabling Billing Markets](/finance/enabling-market).
## Set up a finance user
You can provide portal access to those who make financial decisions for the registered company by creating specific user roles: *Finance* or *Financial Contact*. These roles determine the user's permissions to manage the account.
For more information, see [Assigning a Finance User Role](/finance/finance-user).
## Payment options
There are multiple payment options available, including electronic funds transfer (EFT) and automatic credit card payments. Electronic payment methods available are outlined on your invoice. Bank details for EFTs are outlined in the [onboarding letter](/finance/finance-forms) for your billing market.
Payment by credit card is available for most billing markets and currencies. For more information, see [Credit Card Payments](/finance/credit-card-payments).
Payment details do not appear if your account is managed by a partner. Contact your partner to arrange billing and payment.
# Setting Up a Megaport Account
Source: https://docs.megaport.com/setting-up/index
This help topic describes how to set up a new Megaport account.
To set up a new Megaport account, you create a company profile, add technical support contact details, set up a billing account, and assign a user role to a finance contact for invoice purposes. After you complete these steps, you can provision new services, test connectivity, and verify service pricing.
If you work with a Megaport partner, the partner will set up your account and help you manage it. For more information, see [Partner-Managed Accounts](/partner/managed).
Before you set up a new account, make sure you have this information:
* **Billing currency** -- A list of currencies for the billing market(s). You can specify a currency for each region, or globally.
* **Billing markets** -- A list of markets where you want to provision services (you can add to this list at a later time).
* **Company details** -- A registered company name and address.
* **Billing contact details** -- The full name, email address, and phone number of the billing contact.
* **Tax details** -- The tax or VAT registration number as required per region (for example, a Tax ID Number, New Zealand Business Number, Business Registration Number, or Australian Business Number).
* **Purchase order number** (optional) -- An PO number for tracking. This number will appear on all invoices related to its market.
* **Technical Support contact details** -- The phone number and email address of your internal support team contact.
If you want to advertise your services on the Megaport Marketplace, this profile information will be required to complete your profile:
* Company logo
* Company biography
* Company headquarters address
* Contact email address, web site, and phone number
* Services offered by your company (selected via the Megaport Marketplace)
* Social media details: Facebook, Twitter, Google, and LinkedIn (optional)
Megaport Marketplace connects your business to Megaport's global ecosystem of enterprise customers. Service providers can promote their business and end users can efficiently multi-source their organization's IT needs and find the best solution regardless of location. For more information about Megaport Marketplace, see [Megaport Marketplace Overview](/marketplace/overview).
## What's next?
Once you have set up your account, you can add a Port, a Megaport Cloud Router (MCR), and Megaport Virtual Edge (MVE), and connect to the Megaport network. For more information, see [Creating a Port](/connections/creating-port), [MCR Overview](/mcr), [MVE Overview](/mve), or [Creating a VXC](/connections/overview#create_vxc).
# Inviting Users to Your Account
Source: https://docs.megaport.com/setting-up/inviting-users
This help topic describes how a Company Admin can invite other users to their Megaport account.
A Company Admin can create new user accounts by inviting users to the company account from the Megaport Portal.
Invited users will receive an introductory email with information about accessing the Megaport Portal. This email will include a temporary password that can be used to log in, after which the user must set a new password that meets the minimum security requirements. The temporary password is valid for up to 24 hours. After this time, you will need to resend the introductory email to issue a new temporary password. You can also resend the introductory email at any time before the 24-hour limit, if required.
If Single Sign-On (SSO) has been enabled for your account (an IdP connection has been created), and the email domain is associated with a registered SSO domain, the email will contain a link that must be clicked to confirm the user for the account. Invited users will not be able to log in if they have not clicked this link.
You can also delete invited users if they do not activate their account and change their password.
When a Google user is invited to an account by a Company Admin, that user will be sent a temporary password and is required to log in directly through a username and password, then reset the account password. This will create their account, and later allow them to log in using a username and password or their Google account. If the user doesn't use the username and password method for the first login with the temporary password then the account will not be created correctly, and the user won't be able to log in using Google credentials.
**To invite other users to your account**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Manage Users.
3. Click **New User**.
4. Complete these fields:
* **First Name** -- The first name of the user being invited to your account.
* **Last Name** -- The last name of the user being invited to your account.
* **Email** -- The email address of the user being invited to your account.\
The email address must be unique and cannot be from a free email domain (such as Gmail, Yahoo, or Outlook).\
Megaport will send the user an email to this address with a temporary password for logging in to the Megaport Portal.
When SSO is enabled (an IdP connection has been created), and the email domain is associated with SSO, the user will be sent an email containing a link that must be clicked to confirm the user for the account. If the email domain is not associated with SSO, the standard invite email will be sent with a temporary password for logging in.\
Users from other domains can be added, however, a pop-up message will show during creation warning that the user won't be able to log in unless they are a Company Admin.\
For more information, see [Setting up Single Sign-On](/setting-up/enforcing-sso).
* **Phone** -- The phone number of the user being invited to your account. Enter this phone number in international format, for example, +61 4321 1234.
* **Role** -- Select the Megaport user role to assign to the invited user.\
A brief description of the selected role is displayed.
Click the **View all user actions** link in this screen to learn more about the supported functionality of each role.
5. Click **Save**.\
Complete these steps for each user that you want to invite to your account. When you create a new user, the user is sent an email with instructions for logging in or confirming the user account.
**To resend the invitation email**
When an account has not been activated, a **Resend Invite** button is available on the Edit User page.
If you need to resend the invitation email, use these instructions.
You must be a Company Admin to resend the invitation email.
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Manage Users.
3. Locate the user to edit then click (View User).
4. Click **Resend Invite** to resend the invitation email.
5. A pop-up window will appear asking for confirmation. Click **OK**.
A message will appear telling you that the email has been resent.
**To delete invited users**
A Company Admin can delete invited users if they haven't activated their account and successfully logged in.
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Manage Users.
3. Locate the user to delete.\
Use the filter field at the top of the page to quickly find the user by name.
4. Click (Delete).
If the user was invited and never logged in to the Megaport Portal, they will be deleted.
* If the user was invited and has logged in, the Delete button will no longer be available. You need to edit and deactivate the user instead.
* Users that have been invited and not accepted, then deleted, can be re-invited using the same email address. The same email address can also be used where an accepted user has been deactivated (however once the email address is re-used, the initial user who was marked as *Inactive* cannot be re-activated).
## Accepting an invite to your Megaport account
If a Company Admin of your Megaport account has sent you an email inviting you to the account, you can accept the invite and confirm your user account.
You might receive different invitation emails depending on the security policies set by the Company Admin. If SSO has been enabled, and the email address is associated with an SSO domain, you will receive an email with a link asking you to confirm your user account. Otherwise, you will receive an email with a temporary password.
**To accept an invite to your Megaport account (username and password)**
This is the invite you will receive when your company requires you to log in to Megaport using a username and password. You will also receive this email if SSO is set up on the account, SSO is set to optional, and you have an email address that isn't associated with an SSO registered domain.
1. In the invitation email you received, click the link to log in.
2. In the Megaport Portal, log in using your email and temporary password that was sent in the email to you.\
Enter your email > click Continue > enter your password > click Continue.
You are prompted to reset your password.
3. In the Reset Password screen, enter your new password and then confirm the new password.
The Megaport Portal password policy includes minimum password complexity rules. Your new password must contain:
* At least 8 characters
* Uppercase characters (A-Z)
* Lowercase characters (a-z)
* Numbers (0-9)
* At least one special character: ^ \$ \* . \[ ] ( ) ? " ! @ # % & / \ , > \< ' : ; | \_ \~ \` = + -
The password policy uses a password strength estimator to prevent common, easily guessed passwords, such as Passw0rd. If you have met all complexity requirements and your password is still being rejected, the likely cause is that the password is too common or easy to guess.
4. Click **Reset Password**.\
The Password Changed OK prompt appears.
5. Click **OK**.\
You are now confirmed as a new user and logged in to the Megaport Portal with your new password.
**To accept an invite to your Megaport account (SSO)**
This is the invite you will receive where you are invited to an account that has SSO enabled, and your email address is associated with one of the configured SSO domains.
* In the invitation email that you received, click **Complete Account Setup** to confirm your user account.
You are now confirmed as a new user and logged in to the Megaport Portal.
# Logging in to the Megaport Portal
Source: https://docs.megaport.com/setting-up/logging-in
This help topic describes how you can log in to the Megaport Portal with Multi-Factor Authentication (MFA) and Single Sign-On (SSO).
If you are having trouble creating a new Megaport account, or logging in to an existing account, see [Megaport Portal Authentication Frequently Asked Questions (FAQs)](/troubleshooting/signup-login-faq).
This topic describes how to log in to the Megaport Portal using Multi-Factor Authentication (MFA) and Single Sign-On (SSO).
MFA is mandatory unless your company is using SSO. If your company is using SSO, you will not be required to use MFA to log in to the Megaport Portal.\
For more information about MFA and SSO, see [Multi-Factor Authentication](/setting-up/enforcing-mfa) and [Setting up Single Sign-On](/setting-up/enforcing-sso).
Once you have been invited to your company by a Company Admin, you can log in to the Megaport Portal. You will need to log in using MFA or SSO.
## How logging in works
Logging in to the Megaport Portal takes place on a hosted Megaport login page. After you log in, your session is shared with other Megaport systems, such as the Quoting Tool and Latitude.sh, so you do not need to log in to each system separately.
To log in, first enter your email address then click **Continue**. The next step depends on the authentication method configured for your account.
The Megaport Portal login page uses a two-step, identification-first flow. You first enter your email address and click **Continue**.
The login page then displays the authentication method configured for your account: password and MFA, Sign in with Google, or your company's identity provider for SSO.
## About MFA
MFA is an authentication method and security system that ensures all of your business accounts require more than one verification factor before they can be accessed. For example, a username and password, and a code from an authentication app. MFA is a core component of a strong identity and access management (IAM) policy, and provides an extra level of security for your Megaport Portal account. We recommend that you use the Google Authenticator app when securing your accounts with MFA.
Each user should install a login verification app (such as Google Authenticator) on their digital device (phone, tablet, computer, and so on). When users log in, they check the login verification app for the token or code that they need to enter as the additional factor.
For more information about managing your MFA settings, see [Securing your account with MFA](/setting-up/manage-profile#securing-your-account-with-mfa).
## Logging in with MFA for the first time
MFA is mandatory. You will need to enter a valid token from an authenticator app every time you log in to the Megaport Portal, in addition to your email and password. For more information about setting up MFA, see [Multi-Factor Authentication](/setting-up/enforcing-mfa).
The first time you log in to the Megaport Portal, you will be prompted to set up MFA. You will need to scan a QR code with an authenticator app on your phone (for example, Google Authenticator) to generate the required token for logging in. After you have set up MFA, you will need to enter a valid token from the authenticator app every time you log in to the Megaport Portal, in addition to your email and password.
**To log in with MFA for the first time**
1. Visit the Megaport Portal.
Click **Get help signing in** on the login page for help if you are experiencing issues logging in.
2. Enter your email then click **Continue**.\
If you are logging in with Google, click **Sign in with Google** instead. If you are already logged in to Google in the browser, this button will show your details.
3. Enter your password then click **Log In**.\
The Multi-Factor Authentication setup screen appears.
4. Scan the QR code with the authenticator app on your phone (for example, Google Authenticator).
5. Enter the one-time token generated by the authenticator app.\
Using Google Authenticator, this is a series of six numbers.
6. Click **Enable MFA**.\
MFA is enabled and you are logged in to the Megaport Portal.
After five failed login attempts, your account will be locked. To have your account reactivated, contact your Company Admin.
## Logging in with MFA
You need to supply a valid token from the authenticator app every time you log in to the Megaport Portal, in addition to your email and password.
**To log in with MFA**
1. Visit the Megaport Portal.
Click **Get help signing in** on the login page for help if you are experiencing issues logging in.
2. Enter your email then click **Continue**.
3. Enter your password then click **Log In**.
4. Enter the code from the authenticator app and click **Verify** to log in.
After five failed login attempts, your account will be locked. To have your account reactivated, contact your Company Admin.
## Logging in after MFA has been reset for your profile
If you or your Company Admin has reset MFA for your profile since the last time you logged in, you need to set up MFA again to log in to the Megaport Portal. You will not be able to log in until you have done so.
Your previous MFA codes will no longer be valid and you must scan the QR code again for the authentication app to generate new codes. If you cancel out of this setup, you will be prompted again to set it up the next time you try to log in.
**To log in after MFA has been reset for your profile**
1. Visit the Megaport Portal.
2. Enter your email then click **Continue**.\
If you are logging in with Google, click **Sign in with Google** instead. If you are already logged in to Google in the browser, this button will show your details.
3. Enter your password then click **Log In**.\
The Multi-Factor Authentication screen appears stating that a Company Admin has reset and disabled your MFA code, and that you need to set up MFA again to log in.
4. Scan the QR code with the authenticator app on your phone (for example, Google Authenticator).
5. Enter the one-time token generated by the authenticator app.\
Using Google Authenticator, this is a series of six numbers.
6. Click **Enable MFA**.\
MFA is enabled and you are logged in to the Megaport Portal.
You need to supply a valid token from the authenticator app every time you log in to the Megaport Portal, in addition to your email and password.
After five failed login attempts, your account will be locked. To have your account reactivated, contact your Company Admin.
## About SSO
SSO is an identity and access management solution that allows users to log in to multiple applications, websites, and software systems with one-time user authentication. That is, SSO allows users to log in once and access multiple services without having to authenticate again.
SSO provides both improved security to organizations and an enhanced user experience. Users can access all applications to which they are entitled, without the need to log in and authenticate multiple times once their identity is validated. It also allows administrators to more easily manage user identity and access.
## Logging in with SSO
Once you have been invited to your company by a Company Admin, you can log in to the Megaport Portal. If a Company Admin has enforced SSO for your company, you must use SSO when logging in. You will be directed to your company's identity provider (IdP) for authentication after entering your email address in the Megaport Portal login page.
See your identity provider's website for further setup instructions, help with fault resolution, and privacy policies.
**To log in with SSO**
1. Visit the Megaport Portal.
Click **Get help signing in** on the login page for help if you are experiencing issues logging in.
2. Enter your email address then click **Continue**.\
For the first time you are logging in, and if your email domain is associated with an external IdP for SSO login, a pop-up message will appear and you will be directed to the IdP for authentication.
3. In the IdP page, enter your email address and password.\
Where available, select to remain logged in if required.
4. Click Log in/Sign in to log in.\
You are logged in to the Megaport Portal. Subsequent logins will log you straight in after entering your email address then clicking **Continue** in the Megaport Portal login page.
## Logging out
Click **Logout** to safely log out of the Megaport application.
If you have the Megaport Portal or Quoting Tool open in multiple tabs in the same browser, logging out in one tab automatically logs you out of all other open tabs of that application. The other tabs update immediately without requiring a refresh and display a message with a link to log in again.
This behavior applies only to tabs in the same browser and is application-specific. Logging out of the Megaport Portal does not log you out of the Quoting Tool, and vice versa.
## Account lockout
After five failed login attempts, your Megaport Portal account is locked as a security measure to help prevent unauthorized access.
Once locked, the account cannot be used to sign in until it is reactivated by a Company Admin.
**To unlock your account**
1. Contact your Company Admin and ask them to reactivate your account.
2. Once your account has been reactivated, you can log in to the Megaport Portal with your email, password, and a valid token from your authenticator app.\
If you have forgotten your password, click **Forgot Password** on the login page to receive an email to update your password.
**To unlock an account as a Company Admin**
1. Visit the Megaport Portal, then log in with your Company Admin account.
2. Choose User Menu > Admin Settings > Manage Users.
3. Find the user whose account is locked, edit their profile, then click **Active** to reactivate their account.
## Helpful references
* [Contacting Support](/support/contact)
* [Megaport Portal Authentication Frequently Asked Questions (FAQs)](/troubleshooting/signup-login-faq)
* [Multi-Factor Authentication](/setting-up/enforcing-mfa)
* [Setting up Single Sign-On](/setting-up/enforcing-sso)
# Creating an Account
Source: https://docs.megaport.com/setting-up/registering
This help topic describes how to create a direct customer account in the Megaport Portal.
This topic describes how to create a direct customer account. As the creator of a direct account, you will be assigned the role of Company Admin.
You can create an account by either signing up with an email address and password or using existing Google account credentials. When using your Google account, you must first sign in to your Google account.
If you experience any issues while creating a new Megaport account or when logging in to an existing account, see the [Megaport Portal Authentication Frequently Asked Questions (FAQs)](/troubleshooting/signup-login-faq).
**To create a company account**
* Visit the Megaport Portal and click **Create a new account**.
You can create an account using an [email address and password](#emailpassword) or [Google account credentials](#google).
**To create an account with email and password**
1. Click **Create Account with email**.
2. Provide these details:
* **First Name** -- Enter the first name of the person creating the account.
* **Last Name** -- Enter the last name of the person creating the account.
* **Account Name** -- Enter the name of your account, company, or organization.\
Megaport creates the company after you complete the signup process, and automatically records the account name in your Company Profile. You can change the name later if required. For more information, see [Modifying a Company Profile](/setting-up/company-profile).
* **Email** -- Enter the email address for the Megaport account.\
If this email address is already associated with another Megaport account, you need to enter a different address. Megaport verifies the email address before you can log in.
Accounts cannot be created from free email domains. In this instance, an error message will be displayed and you need to use another email address.
* **Password** -- Enter the Megaport account password.\
The Megaport Portal password policy enforces minimum password complexity rules. Your password must contain:
* At least 8 characters
* Uppercase characters (A-Z)
* Lowercase characters (a-z)
* Numbers (0-9)
* At least one special character: ^ \$ \* . \[ ] ( ) ? " ! @ # % & / \ , > \< ' : ; | \_ \~ \` = + -
The password policy uses a password strength estimator to prevent common, easily guessed passwords, such as Passw0rd. If you have met all complexity requirements and your password is still being rejected, the likely cause is that the password is too common or easy to guess.
* **Confirm Password** -- Enter the password again to confirm.
3. Review and accept the Privacy Policy, Site Terms, and Acceptable Use Policy.
4. Click **Create Account**.\
Megaport sends an account confirmation email.
5. Open the account confirmation email.\
If you did not receive the original email, click **Resend Email**. Clicking **Resend Email** invalidates the previous email.
6. Click **Verify Email** in the confirmation email. The link is valid for 24 hours.
A confirmation page verifies that the new account was created. Megaport sends the Company Admin a welcome email.
7. Visit the Megaport Portal, enter your email and password, then click **Continue** to log in.\
You are now successfully logged in to the Megaport Portal.
**To sign up with Google**
1. Click **Sign up with Google**.\
You are directed to Google to enter your credentials if you are not already signed in.\
After successfully entering your credentials, Google directs you back to Megaport.
2. In the **Account Name** field, enter the name of your account, company, or organization.\
Megaport creates the company after you complete the signup process, and automatically records the account name in your Company Profile. You can change the name later if required. For more information, see [Modifying a Company Profile](/setting-up/company-profile).
3. Read and accept the Privacy Policy, Site Terms, and Acceptable Use Policy.
4. Click **Continue to Megaport Portal**.\
Megaport creates your account and logs you in automatically.
# Providing Support Contact Details
Source: https://docs.megaport.com/setting-up/tech-support-details
This help topic describes how to provide your internal tech support contact details in the Megaport Portal.
This topic describes how to provide your internal tech support contact details in the Megaport Portal.
To streamline communication between the Megaport Support team and your account, company, or organization, we need to know how to contact your internal support team. During initial account setup, a Company Admin or Sales Team member enters the support phone number and email address. These details provide a way for us to reach out should you need any assistance.
Here are the contact detail requirements by account type:
| **Account Type** | **Supported By** | **Contact Details Required?** | **Details Displayed in Megaport Portal?** |
| :- | :- | :-: | :- |
| **New direct** | **Megaport** | **Yes** | **Yes** |
| **Existing direct with no provisioned services** | **Megaport** | **Yes** | **Yes** |
| New partner | Partner | Yes | Yes, visible in managed account list. |
| New partner | Megaport | Yes | Yes, visible in managed account list. |
| New managed | Megaport | Yes | No |
| New managed | Partner | No | No |
After support details have been added to an account, certain users can edit them. However, for new accounts and accounts without provisioned services, the details cannot be deleted. The viewing and editing permissions by account type are:
* Company Admins can view and edit support contact details.
* Direct account users can view the support contact details, but cannot edit them.
* Managed account users supported by their partners can view the support contact details, but cannot edit them.
* Managed account users supported by Megaport cannot view or edit support contact details.
Partners can find more information in the [Megaport Partner Program](https://www.megaport.com/partners/) overview and the [Megaport Partner Portal Documentation](/partners).
New and existing direct accounts without any provisioned services cannot place orders until their account setup is complete, including technical support contact details and a [billing market](/finance/enabling-market). You can still add services to a saved configuration and view pricing, but the services cannot be ordered until the account setup is complete.
**Your Contact At Megaport**
This page will also show the email addresses of your Megaport Account Manager or Customer Success Manager.
**To enter support details**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Account Contacts.
3. Enter the phone number of your internal support team.\
The number is validated against the billing market format of your billing contact phone number. Megaport requires a technical support team phone number and team email address for new direct accounts and for existing direct accounts without any provisioned services.
4. Enter the email address of your internal support team.\
The email format and address is validated against the email address provided during account sign up.
5. Click **Save**.
# Technical Specifications
Source: https://docs.megaport.com/tech-specs/index
This help topic details the technical specifications of the Megaport network.
A Port is the high-speed Ethernet interface that connects to the Megaport network. It is configured as an 802.1Q VLAN trunk to support multiple Virtual Cross Connects - each presented as a unique VLAN.
These tables summarize the technical specifications for Megaport services:
| **Interface Speed** | **Interface** |
| - | - |
| 1 Gbps | 1000BASE-LX (10km; duplex on ) |
| 10 Gbps | 10GBASE-LR (10km; duplex on SMOF) |
| 100 Gbps | 100GBASE-LR4 (10km; duplex on SMOF) |
| 400 Gbps | 400GBASE-LR4 (10km; duplex on SMOF) |
| **Service Attribute** | **Service Parameter/Value** |
| - | - |
| MAC Layer | IEEE 802.3-2002 |
| Maximum Ethernet Frame Size (MTU) | VXCs support an Ethernet MTU of 9100 bytes. MVEs support a VXC Ethernet MTU of up to 9100 bytes; however, the supported IP MTU depends on the MVE vendor and the configuration. For more information, contact your Megaport Account Manager. Megaport Internet VXCs are limited to an MTU of 1500 bytes. IX and many CSP ports do not support jumbo frames, but all support the standard MTU of 1500 bytes. |
| VLAN Ethernet Type | 0x8100 |
| | Supported |
| CoS Level | Standard |
| Unicast Frame Delivery | Deliver Unconditionally |
| Multicast Frame Delivery | Deliver Unconditionally |
| Broadcast Frame Delivery | Deliver Unconditionally |
## Layer 2 control tunneling
| **Protocol** | **Action** |
| - | - |
| , , , PVST+Per-VLAN Spanning Tree and Per VLAN Spanning Tree Plus Protocols. | Tunnel |
| | Discard |
| | Discard - See Link Aggregation Control Protocol (LACP) note below. |
| | Discard |
| | Tunnel (MACsec only) - See MACsec note below. |
| | Tunnel |
| | Tunnel |
* Link aggregation is supported using Link Aggregation Control Protocol (LACP). You can use LACP on an individual interface if you plan to add interfaces in the future. Link aggregation is supported locally by enabling LACP when creating a Port, but LACP is not carried across a VXC. For more information about Link Aggregation Groups, see [Creating a Link Aggregation Group](/connections/lag).
* LACP is supported for VXCs set to 'Untag'. LACP allows bundling of customer's network over the underlying VXCs and is supported for existing and new deployments.
(0x88e5) frames are transported only on untagged VXCs, or over tagged VXCs when the VLAN is not encrypted.\
Some equipment does not support unencrypted VLANs. Check whether the equipment you use supports unencrypted VLANs, also known as clear tag mode, before using MACsec-encrypted traffic over tagged VXCs.
Megaport polices traffic to the committed information rate (CIR) of the ordered VXC speed. Megaport does not shape customer traffic. You can configure your own shaper if required; however, do not exceed four megabytes for the committed burst size (CBS).
# 2020 Release Notes
Source: https://docs.megaport.com/whatsnew/2020
This help topic describes changes and enhancements made to the Megaport Portal during 2020.
* [Monitoring Services for Status](/monitoring/service-status) -- This new topic describes how Megaport monitors services.
* [Using the Megaport Terraform Provider](/terraform) -- This new topic describes how to integrate the Megaport Terraform Provider with the Megaport API to provision and manage Megaport services.
* **Port Diversity**:
* [Port Diversity](/connections/port-diversity) -- This new topic describes how to configure and manage diverse Ports.
* [Creating a Port](/connections/creating-port), [Creating a LAG](/connections/lag), and [Adding a Port to an Existing LAG](/connections/lag-adding) -- These topics now include Port diversity details.
* [Terminating a Port](/connections/terminating-port) -- This topic has been updated with a new section on terminating diverse Ports.
* **Introducing support for OVHcloud Connect**:
* [Connecting to OVHcloud Connect](/cloud/megaport/ovhcloud) -- This new topic describes how to connect to OVHcloud Connect from your Port on the Megaport network.
* [OVHcloud Connect Direct](/cloud/megaport/ovhcloud/direct) -- This new topic describes how to set up a direct, secure connection to OVHcloud Connect.
* [Creating MCR Connections to OVHcloud Connect](/cloud/mcr/ovhcloud) -- This new topic covers how to create connections between MCR and OVHcloud Connect.
* [Modernizing Your MPLS Network with Megaport Solutions](/deployment/wan-replacement) -- This new topic examines options and considerations for modernizing your MPLS network with Megaport.
* [Quick Start Guide](/getting-started) -- This new topic provides basic workflows to get your account set up and start provisioning network services.
* [API Overview](/api) -- This section enhances the API reference at [dev.megaport.com](https://dev.megaport.com) by describing how to use the API to perform common tasks. New topics step you through using the API to complete procedures such as logging in, creating a Port or MCR, and creating a VXC to a Cloud Service Provider.
* [Creating an MCR](/mcr/creating-mcr) -- The new *Initial BGP State* option lets you select whether you want any new BGP sessions you configure to be live as soon as you save the configuration.
* [Understanding Locations](/enabled-locations) -- This new topic describes how to use the new Megaport Locations page to find a Megaport Point of Presence.
* [Connecting to Cloudflare with Megaport](/cloud/megaport/cloudflare) -- This new topic describes how to connect to Cloudflare through the Megaport Portal.
* **Pricing & Billing updates**:
* [Virtual Cross Connect Pricing](/finance/vxc-pricing) -- This topic has been updated with Megaport Pricing Zones and Metros.
* [MCR Billing](/finance/mcr-pricing) -- This new topic covers MCR billing details.
* [Making a One-Off Credit Card Payment](/finance/credit-card-payments) -- This new topic covers how to use a credit card to make a payment outside of the billing cycle.
# 2021 Release Notes
Source: https://docs.megaport.com/whatsnew/2021
This help topic describes changes and enhancements made to the Megaport Portal during 2021.
* [Introducing MVE for VMware SD-WAN](/mve/vmware) -- A set of new topics that describe the Megaport and VMware SD-WAN solution, including overview, deployment, cloud, and connection details.
* **More details about currencies supported per country** -- Added details for currencies supported in each [billing market](/finance/enabling-market) and for [credit card payments](/finance/credit-card-payments).
* [Enhanced troubleshooting topics and videos](/troubleshooting/overview) -- This section has been expanded with detailed steps and quick tip videos to help you investigate errors and unexpected behaviors with your Megaport services.
* [Introducing MVE for Aruba EdgeConnect SD-WAN](/mve/aruba) -- A set of new topics that describe the Megaport and Aruba SD-WAN solution, including overview, deployment, cloud, and connection details.
* Japanese, French, Spanish, and German documentation has been updated with recent content. For access from any page, use the menu in the upper-right corner to select a language.
* **Support for 20G VXCs** -- [Topic updates](/connections/overview) to indicate support for connections of up to 20 Gbps between 100 Gbps Ports within the same metro.
* **Expanded information for User Roles** -- The [Managing User Roles](/portal-admin/user-management/roles) topic includes a table that describes what functionality is available for each role.
* **Updated and new W8 forms** -- The [Vendor Onboarding](/finance/finance-forms) page includes updated and new W8 forms. The new forms are for Spain, Finland, Germany, Luxembourg, and Switzerland.
* **Megaport Documentation now available in Spanish** -- For access from any page, use the menu in the upper-right corner to select the language.
* [Introducing MVE for Versa Secure SD-WAN](/mve/versa) -- A set of new topics that describe the Megaport and Versa SD-WAN solution, including overview, deployment, cloud, and connection details.
* **Enhanced and Reorganized [Billing](/finance/overview) and [Pricing](/finance/port-pricing) Information** -- Billing and Pricing details are now in separate sections and include expanded and enhanced content.
* [Connecting to Sungard AS with Megaport](/cloud/megaport/1111systems) -- This new topic describes how to connect to Sungard AS through the Megaport Portal.
* [Partner-Managed Accounts](/partner/managed) -- The documentation has been updated to reflect how partner-managed accounts can have a different experience when ordering and managing services.
* [Downloading an Invoice](/finance/download-invoice) -- The help topic has been updated to reflect an easier approach to downloading CSV and PDF invoices.
* Japanese, French, and German documentation has been updated with recent content -- For access from any page, use the menu in the upper-right corner to select a language.
* [Introducing MVE for Fortinet Secure SD-WAN](/mve/fortinet) -- A full set of new topics that describe the Megaport and Fortinet SD-WAN solution, including overview, deployment, cloud, and connection details.
* [Introducing MVE](/mve) -- Introducing Megaport Virtual Edge (MVE) -- An on-demand, vendor-neutral Network Functions Virtualization (NFV) hosting service.
* [MCR Route Filtering](/mcr/route-filtering) -- This new topic describes how you can configure route filters on MCR to easily control which routes are exchanged between BGP neighbor routers.
* [Megaport Support Services](/support) -- This section has been updated with details on Megaport Support requests and how we perform network maintenance.
* Japanese, French, and German versions of the Megaport Documentation are now available -- For access from any page, use the menu in the upper-right corner to select a language.
* **Support for IBM Direct Link 2.0**:
* [Connecting to IBM Direct Link 2.0](/cloud/megaport/ibm/direct-link-2.0) -- This new topic describes how to connect to IBM Direct Link 2.0 from your Port on the Megaport network.
* [Creating MCR Connections to IBM Cloud Direct Link 2.0](/cloud/mcr/ibm-2.0) -- This new topic describes how to create connections to IBM Direct Link 2.0 from your MCR on the Megaport network.
* [Configuring Q-in-Q](/connections/q-in-q) -- This topic has been updated with ways to configure multiple layer VLAN tag handling on network devices without native Q-in-Q support.
* [Connecting to Microsoft Azure ExpressRoute](/cloud/megaport/microsoft) -- This topic has been updated with ways to connect to ExpressRoute on network devices that do not support Q-in-Q.
* [Megaport Support Services](/support) -- This new section provides a general overview of the Support team and describes how to contact Megaport Support.
* [Megaport API documentation](https://dev.megaport.com) -- The API reference documentation has been thoroughly updated, with a new format, new organization, and new examples in many popular client languages. The site also includes an updated Postman collection with pre-built requests.
* [Creating a VXC](/mcr/mcr-vxc) -- A streamlined workflow in the Megaport Portal makes it easier to configure Megaport Cloud Router (MCR) Virtual Cross Connects (VXCs). The updated MCR Connection Detail page consolidates the VXC configuration attributes. This user experience refresh has no affect on existing MCR behavior.
# 2022 Release Notes
Source: https://docs.megaport.com/whatsnew/2022
This help topic describes changes and enhancements made to the Megaport Portal during 2022.
* **3DS Outscale** -- These new topics describe how to create connections to 3DS Outscale via a [Megaport Port](/cloud/megaport/outscale), a [Megaport Cloud Router (MCR)](/cloud/mcr/outscale), and Virtual Cross Connects (VXCs).
* **Megaport Portal Authentication** -- Various new or updated help topics relating to the improvements in user authentication in the Megaport Portal, including:
* [Creating an account](/setting-up/registering)
* [Inviting Users to Your Account](/setting-up/inviting-users)
* [Resetting Your Password](/setting-up/change-password)
* [Managing Your User Profile](/setting-up/manage-profile)
* [Megaport Portal Authentication FAQs](/troubleshooting/signup-login-faq)
* [Adding and Modifying Users](/portal-admin/user-management)
* [Creating an API Key](/api/api-key)
* [Diversity in Google Connections](/cloud/megaport/google/google-diversity) -- This new topic describes how to identify and create diverse connections in Google Cloud.
* [Diversity in Azure Connections](/cloud/megaport/microsoft/azure-diversity) -- This new topic describes how to identify and create diverse connections in Azure ExpressRoute.
* [Megaport Letter of Authorization](/portal-admin/loa) -- New topic describing the LOA and how it is used.
* Japanese, French, Spanish, and German documentation has been updated with recent content. For access from any page, use the menu in the upper-right corner to select a language.
* [Configuring AWS Outposts Rack with Private Connectivity](/cloud/megaport/aws/outposts) -- This new topic describes how to deploy AWS Outposts Rack with an AWS Direct Connect Hosted Connection via a Megaport Port, a Megaport Cloud Router (MCR), and Virtual Cross Connects (VXCs).
* [Enabling Billing Markets](/finance/enabling-market) -- This topic has been updated with tax questions for UK, Australia, and Singapore billing markets. These questions will help calculate an accurate tax rate.
* **Updated and new W8 forms** -- The [Customer Onboarding](/finance/finance-forms) page includes updated and new onboarding letters. The new letters are for Belgium, Spain, Finland, and Luxembourg.
* [Monitoring Ports, VXCs, and IXs](/monitoring/port-vxc-monitoring), [Monitoring MCR](/monitoring/mcr-monitoring), and [Monitoring MVE](/monitoring/mve-monitoring) -- These topics have been updated to reflect the enhanced date range functionality now available when viewing usage details in the Service Graph.
* [Configuring BGP Advanced Settings](/mcr/mcr-bgp-advanced) -- This help topic has been updated with support for ASN path prepending, which allows you to set the route advertisement priority for outgoing BGP paths.
* Japanese, French, Spanish, and German documentation has been updated with recent content. For access from any page, use the menu in the upper-right corner to select a language.
* [Megaport API Documentation](https://dev.megaport.com#b0a9984c-abb3-4643-becd-7529ab8fdc36) has a new topic that describes how to validate a VXC order for an MCR. This topic includes BGP configuration.
* **New Package Sizes for MVE** -- Megaport Virtual Edge (MVE) instances are now offered in several tiered package sizes that include appropriate internet bandwidth sizing. The sizing specifications vary for each SD-WAN partner:
* [Aruba](/mve/aruba/plan-deployment#size)
* [Cisco](/mve/cisco/plan-deployment#size)
* [Fortinet](/mve/fortinet/plan-deployment#size)
* [Versa](/mve/versa/plan-deployment#size)
* [VMware](/mve/vmware/plan-deployment#size)
* [Configuring BGP Advanced Settings](/mcr/mcr-bgp-advanced) -- This help topic has been updated with Megaport Cloud Router (MCR) Google Cloud Services support for single-hop Bidirectional Forwarding Detection (BFD).
* [Creating an MVE Integrated with Aruba Using a System Tag](/mve/aruba/creating-mve-system-tag) -- This new help topic describes how you can use a system tag to streamline configuration when deploying Megaport Virtual Edge (MVE) with Aruba SD-WAN as the integration partner.
* [New Market](/finance/vxc-pricing) -- Mexico has been added to the list of available markets, with new metros for Mexico City and Querétaro.
* [Securing the Network with SASE](/mve/sase) -- This new help topic describes how you can access Secure Access Service Edge (SASE) services when deploying Megaport Virtual Edge (MVE) with Fortinet or Versa Secure SD-WAN as the integration partner. SASE provides comprehensive, policy-driven security services across the network.
* [MVE Contract Term Renewal](/finance/mve-pricing) -- This help topic has been updated to describe how to add, extend, or renew an MVE contract term.
* [Connecting to Alibaba Express Connect](/cloud/megaport/alibaba) and [Creating MCR Connections to Alibaba Express](/cloud/mcr/alibaba) -- These topics have been updated to reflect the new connectivity model for Alibaba Express Connect and capacity tiers up to 1 Gbps.
* [Terms for MVEs](/finance/mve-pricing) -- MVEs now support 12, 24, and 36-month terms in addition to the pay-as-you-go option. Contract terms provide fixed pricing and discounts.
* [Customer Field Services](/finance/customer-field-services) -- This new topic describes the process Megaport follows when customers require an onsite technician to troubleshoot an issue or provide a solution.
* Japanese, French, Spanish, and German documentation has been updated with recent content. For access from any page, use the menu in the upper-right corner to select a language.
* [Terms for MCRs](/finance/mcr-pricing) -- MCRs now support 12, 24, and 36-month terms in addition to the pay-as-you-go option. You can specify the term for an MCR during creation, or edit an existing MCR to specify a new term. Contract terms provide fixed pricing and discounts.
# 2023 Release Notes
Source: https://docs.megaport.com/whatsnew/2023
This help topic describes changes and enhancements made to the Megaport Portal during 2023.
* **Terms on VXC** -- Terms on VXC is now available for both Direct and Partner customers. This feature allows customers to order VXCs at a discounted rate and lock in the price for the length of the term, in line with the terms available for Ports, MCRs, and MVEs. When creating a new VXC or updating an existing VXC, customers now have the option to select a term (or subscription).
Available term options are No Minimum Term (default), 12, 24, and 36 months. Longer terms result in a lower monthly rate.
Key points:
* An early termination fee (ETF) equal to 50% of the remaining contract value applies if a VXC is canceled before the minimum term is complete.
* While the VXC is on term, speed changes are not allowed (all other changes that won’t affect the price are allowed, including shutting down and moving the VXC).
* Speed changes are allowed only when re-terming and only if increasing the speed.
* When re-terming, you can select a term that is >= current term AND you can also increase speed.
* Customers can re-term at any time and will be notified in the last month of term to renew their term.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing).
* **Issue fixed** -- When creating an untagged VXC between two MVEs, the Summary page was showing preferred VLAN as -1 when not specified.
* **Megaport Internet** -- You can now order Megaport Internet connections from Ports and MCRs within a metro (rate from 20 Mbps to several Gbps). Megaport Internet connections for Ports and MCRs can only be ordered from three countries (Australia / US / UK) and cannot leave a metro (A-End and B-End must be within the same metro).\
For more information, see [Megaport Internet Overview](/megaport-internet).
* **Large VXCs** -- Large VXCs are now available to order in the Megaport Portal. Many locations will now support large VXCs up to 25 Gbps. As network upgrades occur, this will increase to supporting VXCs up to 100 Gbps in the future. For metro VXCs, pricing is the same from 10 Gbps to 100 Gbps. For long haul VXCs, pricing will be more linear depending on the network route and pricing zones.
If you create a VXC greater than the speed supported, you will see an error “Invalid Rate Limit” displayed in the Portal.
* **Improved Portal A-End / B-End Display** -- When ordering a VXC to and from an MCR in combination with any product, it is now highlighted more obviously to indicate which End is being changed.
* **Move VXC / IX - Improved Services Page** -- Tooltips have been added to advise why a VXC cannot be moved under certain conditions.
* **Megaport Internet** -- Updated the logo for Megaport Internet connections.
* **Issues fixed:**
* A promo code wasn’t applying if a Port went live after the next billing cycle.
* Canceling an expiring Port was applying 30 days notice charge.
* When viewing a Port in the design state, the Port Configuration page wasn’t being displayed if attached to a VXC with an invalid rate limit.
* **Cancellation Reasons** -- When canceling services, customers will now be asked to provide a reason for terminating the service. A new drop-down field has been added to the Terminate Services window that allows you to select from a predefined list, or select *Other* and enter a description in the free text field provided. Multiple help topics where service cancellation is described have been updated for this new field.
* **Reverse DNS for IX Connections** -- Enabled the ability to add and edit reverse DNS for IX connections.
* Added a new field called Reverse DNS to the Megaport Portal for customers to specify a reverse DNS when editing an IX. For more information, see [Editing an IX](/ix/editing-an-ix#reverse-dns).
* Updated the Validate, Buy, and Update IX APIs to support the specifying of reverse DNS. For more information, see [PUT Update IX (API Documentation)](https://dev.megaport.com/#6ae89dd9-e4bd-4fb5-8533-f8a4a0d02385).
* **Move VXC / IX** -- The Megaport Portal now allows you to move a single or multiple VXCs / IXs across Ports, MCRs, and MVEs. There are rules as to when a VXC or IX can be moved, including:
* The source and destination Port service must be the same. That is, both Ports must be the same type (Port, MCR, or MVE).
* Source and destination Ports must be owned by the same customer account.
* Source and destination Ports must be located within the same metro.
* Must be a normal customer Port or supported Cloud Service Provider port. Currently supported CSP ports are: AMS-IX, AWS, AWSHC, and Oracle.
* The VXC or IX service being moved must not have a VLAN conflict with any existing service on the destination Port.
* The VXC or IX service being moved must have a speed less than or equal to the destination Port maximum.
For more information, see [Moving VXCs](/connections/move-vxc) and [Moving IXs](/ix/move-ix).
* **IP Transit Renamed** -- The Transit VXC service that was previously ordered with an MVE to communicate with the SD-WAN overlay network has been renamed to **Megaport Internet**. You will now create a Megaport Internet connection when creating an MVE. All references to the following in the Megaport Portal and documentation have been changed to Megaport Internet:
* Transit VXC
* IP Transit VXC
* Megaport IP Transit
* **Palo Alto MVE** -- Updated the Licence Data field to allow alphanumeric characters a-z, A-Z, 0-9 (min. 8 characters).
* **Return Key Confirms MFA Token** -- You can now press Enter on a keyboard to submit the form for enabling MFA, rather than having to use a mouse click to submit.
* **New IX Location - Charlotte NC** -- MegaIX is now available in Charlotte, NC and available for ordering in the Megaport Portal. Megaport's MegaIX is your high-speed express lane to the most in-demand global networks.
* **Dashboard** -- Added a new interactive map view of services to the Dashboard. Partner accounts can switch between partner / managed accounts views. For more information about using the new Megaport Portal interactive globe dashboard, see [Megaport Portal Dashboard](/dashboard).
* **Megaport ONE** -- Launched the Beta version of Megaport ONE. Megaport’s new feature-rich networking, compute, and orchestration platform will take users through the cloud. For more information about the announcement, see
[Megaport Announces Public Availability of Megaport ONE Beta](https://s37613.pcdn.co/wp-content/uploads/2023/09/Megaport-Announces-Public-Availability-of-Megaport-ONE-Beta-5-Sep-2023.pdf).
* **vNIC Connectivity** -- Megaport now allows you to add up to five Virtual Network Interface Cards (vNICs) to a Megaport Virtual Edge (MVE). You will have to specify which vNIC to use as an A-End or B-End when creating a connection to or from the MVE. Various topics relating to planning MVE deployments, creating MVEs, and connecting a VXC to an MVE have been updated to describe vNIC requirements. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
Consult your service provider to make sure that functionality won’t be affected if you add a vNIC.
* **Issues fixed:**
* Designed Services being removed on refresh: Partners were losing designed services when designing services for their Managed Accounts.
* Sort and filter buttons on the Services Page alignment.
* **France-IX Connectivity** -- Megaport now supports connectivity to France-IX via VXC using the Service Key and Megaport Marketplace connectivity types. You can connect to France-IX by creating a VXC from a Port, MCR, and MVE. For more information, see [France-IX Connectivity](/ix/france).
* **MCR Looking Glass Performance Improvements** -- MCR Looking Glass has been updated to support asynchronous requests for IP, BGP, and neighbor routes. A new endpoint called **GET MCR IP / BGP / BGP Neighbor Routes in Async Mode** has also been created to support retrieving these results. For more information, see [MCR Looking Glass (API Documentation)](https://dev.megaport.com/#3ccc098c-3d47-4467-8845-5a19a565f3e3).
Synchronous mode will be deprecated in the future so we recommend using asynchronous mode.
* **VXC/IX Shutdown** -- A feature has been added that allows you to shut down and re-enable VXC and IX services for failover testing. For more information, see:
* [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc)
* [Shutting Down an IX for Failover Testing](/ix/shutting-down-an-ix)
* [Shutting Down a VXC and IX with the API](/api/api-vxc-shut-down)
* [PUT Update VXC (API Documentation)](https://dev.megaport.com/#4293df4a-545d-45a2-bfa1-90f41df13160)
* [PUT Update IX (API Documentation)](https://dev.megaport.com/#6ae89dd9-e4bd-4fb5-8533-f8a4a0d02385)
* **Mexico Billing Market** - Four new mandatory TAX Registration fields related to fiscal and legal compliance information are now required when adding or editing the Mexico billing market. These fields are Company Type, Tax Regime, Tax Purpose, and RFC Number. For more information, see:
* [Enabling Billing Markets](/finance/enabling-market)
* [POST Set Billing Market (API Documentation)](https://dev.megaport.com/#6713863b-f2c4-4fcf-9e7d-81262d8b20ae)
* **New Service Status Email Notification Group** -- A new notification group for service up and service down events called Service Status has been added. For more information, see [Configuring Email Notifications](/portal-admin/email-notifications).
* **VLAN** -- Preferred B-End VLAN field is hidden if the customer configuring a Service Key VXC is not the owner of the B-End (Port).
* **Login** -- Fixed how mix-cased e-mail addresses are handled to ensure that the user gets the federated identity re-added with the correct casing.
* **IBM Cloud Direct Link** -- These topics have been updated to describe the automated cloud VXC workflow now available when provisioning a cloud VXC to IBM Direct Link:
* [Connecting to IBM Cloud Direct Link](/cloud/megaport/ibm/direct-link-2.0)
* [Creating MCR Connections to IBM Cloud Direct Link](/cloud/mcr/ibm-2.0)
* [GET Partner Megaports (API Documentation)](https://dev.megaport.com/#c276af3b-884e-481a-bb3e-9ad5a22471cc)
* [POST Create VXC to IBM (API Documentation)](https://dev.megaport.com/#1c2d1c18-6dd0-4e89-b79f-a4e6620a6b46)
* **Single Sign-On (SSO)** -- Further improvements have been made to the user experience and security of customers accessing the Megaport Portal, with the release of SSO. SSO allows you to log in to multiple applications or services using a single set of credentials. Using SSO, you can access our platform using your corporate credentials. Company Admins can also choose to enforce SSO for their team, which forces users to use their corporate credentials to log in to the Megaport Portal.\
There are various new or updated help topics relating to the SSO improvements, including:
* [Setting up Single Sign-On](/setting-up/enforcing-sso)
* [Inviting Users to Your Account](/setting-up/inviting-users)
* [Logging in to the Megaport Portal](/setting-up/logging-in)
* [Adding and Modifying Users](/portal-admin/user-management)
* [Managing Your User Profile](/setting-up/manage-profile)
* [Single Sign-On (SSO) Features and Instructions for Use](/troubleshooting/sso-terms-conditions)
* Japanese, French, Spanish, and German documentation has been updated with recent content. Updates include information on configuring AWS Outposts Rack with private connectivity, a new topic describing the LOA, new topics on diversity in Google and Azure connections, information on user authentication (including creating API keys), and a guide to creating connections to 3DS Outscale. For access from any page, use the menu in the upper-right corner to select a language.
* **Change BGP Password and ASN after Ordering IX Service** -- Various new or updated help topics relating to the ability to change the BGP password and ASN after you have ordered an IX service:
* [Internet Exchange Overview](/ix)
* [Changing an IX Configuration with the API](/api/api-ix-change)
* [Update IX (API Documentation)](https://dev.megaport.com/#6ae89dd9-e4bd-4fb5-8533-f8a4a0d02385)
* [Allow Internet Traffic Exchange Between MVEs](/mve/mve-faqs) -- This FAQ topic has been updated to explain that internet traffic between MVEs is now allowed. These partner topics were also updated:
* [Aruba](/mve/aruba/connect-mve-to-mve)
* [Cisco](/mve/cisco/connect-mve-to-mve)
* [Fortinet](/mve/fortinet/connect-mve-to-mve)
* [Versa](/mve/versa/connect-mve-to-mve)
* [VMware](/mve/vmware/connect-mve-to-mve)
* [Introducing MVE for Palo Alto Networks VM-Series](/mve/palo-alto) -- A full set of new topics that describe the Megaport and VM-Series Next Generation Firewall (NGFW) solution, including overview, deployment, cloud, and connection details.
* **New Package Sizes for MVE** -- Megaport Virtual Edge (MVE) instances are now consolidated into four new tiered package sizes. Each size now has 4 GB of RAM for every vCPU allocated. In addition, new Transit VXC functionality allows you to adjust the IP Transit bandwidth at any time. The sizing specifications are listed for each partner:
* [Aruba](/mve/aruba/plan-deployment#size)
* [Cisco](/mve/cisco/plan-deployment#size)
* [Fortinet](/mve/fortinet/plan-deployment#size)
* [Versa](/mve/versa/plan-deployment#size)
* [VMware](/mve/vmware/plan-deployment#size)
* [Palo Alto Networks](/mve/palo-alto/plan-deployment#size)
* **Megaport Support for Managed Account Users** -- We now offer direct technical support for managed account users. In this optional support model, customers managed by a partner contact the Megaport Support team directly with any support requests. Enrolling in the Megaport direct support model provides a way for partners to offer a self-service experience to their customers.
* [Configuring Email Notifications](/portal-admin/email-notifications)
* [Providing Support Contact Details](/setting-up/tech-support-details)
* [Partner-Managed Accounts](/partner/managed)
* **Multi-Factor Authentication (MFA)** -- Improvements have been made to the user experience and security of customers accessing the Megaport Portal, including having MFA enforced at an account level and admin visibility of which users have MFA set up. There are various new or updated help topics relating to the MFA improvements, including:
* [Multi-Factor Authentication](/setting-up/enforcing-mfa)
* [Logging in to the Megaport Portal](/setting-up/logging-in)
* [Managing Your User Profile](/setting-up/manage-profile)
* [Managing User Roles](/portal-admin/user-management/roles)
* **Autonomous Mode for Cisco MVE** -- Megaport Virtual Edge (MVE) integrated with Cisco now supports provisioning of the MVE NFV service as a virtualized standalone router, providing full control of the cloud provider to users with advanced routing expertise. This provisioning mode does not require SD-WAN. For more information, see [Cisco with MVE](/mve/cisco).
# 2024 Release Notes
Source: https://docs.megaport.com/whatsnew/2024
This help topic describes changes and enhancements made to the Megaport Portal during 2024.
* **Activity Logging** -- Improvements have been made to the account activity information that is logged and displayed in the Portal. A Company Admin can now view a list of global activities, which can be filtered in various ways, such as by user or date. This provides a much better audit trail and view of all activities that have occurred for a company. For example, it can help prove any malicious activity via compromised accounts or show evidence of activities performed by API keys.
Previously, the Portal only allowed the logged-in user to see their activities.
A new API `v3/activity` has also been created that can be used to retrieve activity logs for the logged-in user.
* **Link Marketplace Profiles to Relevant Docs Pages** -- A new feature has been added where each service provider in the Megaport Marketplace now automatically has a 'how to connect' guide. Each profile page in the Megaport Marketplace has a **Documentation** link at the top right which links to a page in the Megaport documentation and describes how to connect to that service provider.
* **Service Inventory Report Update** -- The Service Inventory report has been updated to increase the amount of services that can be included in the report. This is to accommodate companies that have a large amount of services.
* **Terraform v1.2.5** -- Version 1.2.5 of the Terraform provider has been released. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.2.5](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.2.5).
* **Brazil Market** -- Megaport has officially expanded into Brazil, bringing our connectivity services to São Paulo. The pricing for Brazil is now live in the Portal and Quoting Tool and we are set up to accept pre-orders in Brazilian Real. Megaport’s full product suite, including Ports, VXCs, MCRs, MVEs and Megaport Internet services, are scheduled to be live in early December.
* **Add Price Breakdown to Portal** -- The Portal has been updated to show wholesale reseller discount and term discount pricing for Megaport services. This now makes it clear what pricing and discounts you are getting for the service. When creating a new service, the price breakdown is added to a new section on the Summary page. For an existing service, there is a new *Billing* tab in the service details which displays this information.
* **Deprecate v2 APIs Replaced by v3 APIs** -- As previously communicated, some of our v2 APIs have been superseded by v3 versions and were scheduled for deprecation. These v2 APIs have now been officially deprecated and no longer supported by Megaport:
* Get MVE Price: GET /v2/pricebook/mve
* Get VXC Price: GET /v2/pricebook/vxc
* Validate Orders: POST /v2/networkdesign/validate
* Buy Services: POST /v2/networkdesign/buy
* Update VXC Details: PUT /v2/product/vxc/
* Delete Services: POST v2/product//action/
For more information, see [API v2 Shutdown FAQs](/troubleshooting/api-v2-faq).
* **Removed Pricing Function for Azure ExpressRoute** -- The pricing function that was previously available when creating an Azure ExpressRoute connection has been removed. You should use the Quoting Tool instead for pricing of Azure ExpressRoute connections. For more information, see [Quoting Service Cost](/finance/creating-estimates).
* **Resource Tags Added to Service Inventory Report** -- Resource tags for services have been added to the Service Inventory report. You can view resource tags only for the company to which you belong. This allows you to export tagging information for external analysis.
* **Megaport Marketplace - Configure B-End VLAN When Accepting a VXC for a Port** -- As a Megaport Marketplace vendor, you can now configure the B-End VLAN of a Port when accepting an order from a customer via the Megaport Marketplace. This allows you to assign the appropriate VLAN configuration before approving the connection request to your port.
* **Megaport Marketplace - Allow Profile Visibility with no Public Listings** -- You can now set your Megaport Marketplace profile to public with or without services being market public. This allows you to generate interest in your brand in the marketplace without the need to have services set to public.
* **Restrict New Users Creating an Account from Free Email Domains** -- A restriction has now been placed on the ability to create Megaport accounts from free email domains. This is to restrict the use of personal accounts where the sign up process is not completed. In this instance, an error message will now be displayed.
* **Country Filter Replaced by Search Filter for VXC B-End Sorted by Proximity** -- On the Edit and New Connection screens, the Country filter list has been replaced by *Search by Port Name, Country, Metro, City, or Address* for Ports, MCRs, and MVEs.
* **Terraform v1.2.3** -- Version 1.2.3 of the Terraform provider has been released. This update includes importing MVEs, filtering MVE images, provisioning Oracle VXCs, updating Partner configuration on BGP VXCs, updating contract term in Ports/MCRs/MVEs, improved Azure VXC peering support, improved location filtering, among other issues. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.2.3](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.2.3).
Release version v1.2.2 was skipped.
* **Sort VXC B-End by Proximity** -- When ordering a VXC or IX, changes have been made to sort the B-End by proximity to the A-End. For example, ordering an AWS connection from an MCR in Auckland will show the NZ-based endpoints at the top of the list. The VXC B-End is now sorted by RTT (Round-trip Time) and sorted alphabetically where this information is not available.
A tooltip was also added to explain the RTT sorting: *The destination ports are sorted by Megaport's monthly averaged Network Latency times. If no latency information is available, the destination ports are sorted alphabetically.*
* **Resource Tags Added to Invoice Report** -- Resource tags for services have been added to the Invoices report (CSV only). This allows you to export tagging information for external analysis.
* **Megaport Internet in France** -- Megaport Internet connections can now be ordered from Ports and MCRs in France. Previously, you could only order Megaport Internet from an MVE in France.
* **Remove Distributors** -- The Distributor account type has been removed from all Megaport systems and applications.
* **6WIND MVE Request License Form** -- A link has been added to the 6WIND MVE offering so that mutual Megaport and 6WIND customers who want to set up a 6WIND MVE can request either an evaluation or full license from 6WIND.
* **Add Coordinates for New IX Locations** -- Map coordinates have been added for the most recent IX locations that have come online. These are now available in the Portal Dashboard map.
* **AnnounceKit Implemented** -- AnnounceKit has been released to the Megaport Portal, allowing real-time communication of new feature and improvement information to Portal users. This is available from the News option in the Portal.
* **VXC Name/Secondary Name Only Sent Based of Ownership** -- Where the A-End and B-End owners are different for a VXC, only the `name` field for the VXC A-End owner is updated, and not `secondaryName`.
* **Issues fixed:**
* When adding a Port to an existing LAG, the Cost Center field is now transferred to the new Port.
* Resource tags are now replicated to LAGs.
* Fixed duplication header for resource tag in the Inventory report.
* **Service Status Page Calendar** -- Improvements have been made to the Service Status page to assist you in monitoring maintenance and outage events that affect your services. Filtering criteria has been updated, and a calendar has been added that allows you to monitor maintenance events in either a calendar or list view. The calendar view allows you to quickly see start and end times of maintenance events, making it easier to track upcoming activities.\
For more information, see [Monitoring Maintenance and Outage Events](/portal-admin/monitoring-events).
* **Renamed Peer Macro to Peer AS-SET** -- On the Connection Details for IX Service screen, the Peer Macro field has been renamed to Peer AS-SET to more clearly identify the purpose of the field. This value defines the AS macro filter for the peer.
* **Credit Card Payment for Italy Market** -- Support has been added for credit card registration and payment for the Italy market. This allows customers with services in the Italy market to easily and safely make automatic payments for services and automatically populate payment details for one-off payments.
* **Issue fixed:**
* The BGP Auth Key field was not showing the input value. Therefore, validation has been added when entering an AWS BGP Auth key and this field now shows the requirements needed for a valid BGP auth key.
* **Removed MCR BFD Timer Settings** -- Support for maintaining MCR BFD timer settings has been removed from the Portal and API. In the Advanced tab of the MCR BGP Connection screen, there is now only a Use BFD = On/Off option. The BFD settings are not editable, the default values configured when BFD is enabled are Transmit Interval: 300 milliseconds, Receive Interval: 300 milliseconds, Multiplier: 3.
* **Improved Navigation of Data Center List** -- On the [Network Latency Page](https://www.megaport.com/network-latency/) on megaport.com, these improvements have been made to the data center navigation:
* Data center location list is now sorted alphabetically
* Latency table is also filtering by full numbers
* Enabled DC location list is now sorted alphabetically at the [Enabled Locations Page](https://www.megaport.com/megaport-enabled-locations/)
* **Issues fixed:**
* A user was unable to make changes in the Megaport Marketplace if the company was enabled but had no services.
* Links in the *A new service has been ordered* emails were broken. These email links now correctly launch to the respective services.
* **Introducing 6WIND Virtual Service Router (VSR) for MVE** -- 6WIND VSR is now available as a new vendor and product when ordering MVEs.
The integration of the 6WIND Virtual Service Router (VSR) suite with Megaport’s MVE includes the vBR (Border Router), vCGNAT (Carrier-Grade NAT), vSecGW (Security Gateway), and vFW (Virtual Firewall) network function offerings.
This update includes a set of new topics that describe the Megaport and 6WIND VSR solution, including overview, deployment, planning, and connection details.
For more information, see [6WIND with Megaport Virtual Edge](/mve/6wind).
* **Introducing Palo Alto Prisma SD-WAN for MVE** -- Palo Alto Prisma is now available as a new product when ordering MVEs.
The integration of Palo Alto Networks Prisma SD-WAN with Megaport’s MVE provides agility, robust security, and simplified connectivity for global networks tailored for today’s digital and cloud-first distributed enterprises.
For more information, see [Palo Alto Networks with Megaport Virtual Edge](/mve/palo-alto/prisma).
* **Resource Tags** -- Customers now have the ability to create, modify, and delete resource tags to manage their active services via the Megaport Portal. Resource tags are key value pairs that act as metadata for organizing Megaport resources. These tags will appear in the Service Inventory report by default for the company who has implemented the tags providing they own the service the tag is put against.
* **MCR and MVE in the Megaport Marketplace** -- MCRs and MVEs can now be listed in the Megaport Marketplace. Customer specific technical information is not visible to the other party.
* You can toggle a service between Private and Public in the Megaport Marketplace Profile page (Company > Megaport Marketplace Profile).
* The Megaport Marketplace Profile and Edit Profiles pages have had usability updates to make them easier to navigate. All customers services are now visible in this section, including clear indication if they are Private or Public.
* The connection name at both ends of a VXC can be different.
* **Megaport Internet in Japan** -- Megaport Internet connections can now be ordered from Ports and MCRs in Japan. Previously, you could only order Megaport Internet from an MVE in Japan.
* **New Cisco C8Kv Version** -- A new MVE image Cisco C8Kv 17.15.01a has been released to the Portal and is available for ordering.
* **IP Address Labels** -- IP address labels on the VXC configuration details screen have been updated to be more accurate.
* **Issue fixed:**
* Lines connecting product icons were misaligned on the Services page in the Portal.
* **BGP Configuration Information Support for Megaport Internet** -- configuration information for Megaport Internet connections is now available as read only in the Connection Details page. To see the BGP configuration settings for your Megaport Internet connection, on the Services page click the gear icon next to the connection then click **Megaport Internet**. The ability to add and edit BGP details will be added in a future release.
* **Term Pricing Display Improvement in Quoting Tool** -- The way that service term pricing is displayed in the Quoting Tool has been improved. You can now see the pricing options at a glance, instead of having to select each term option from a drop-down list.
* **Terraform Updates** -- Terraform is being continuously improved and updated, and has recently been updated to Terraform v 1.1.7. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases](https://github.com/megaport/terraform-provider-megaport/releases).
* **Issue fixed:**
* Saved configuration was not retrieving port diversity information. Now, when you configure a Port with port diversity, you can see the diversity information that is set.
* **Megaport Portal Translation Updates** -- Updated translations in Japanese, French, Spanish, and German are now available in the Portal. Updates include translations for all Portal features that were released in Q3 this year. A brand new translation is also available for Brazilian Portuguese. For access from any page, use the menu in the upper-right corner to select a language.
* **Feedback on Higher Speed VXCs From Customers** -- An option has been added to the Create/Update VXC screen for customers to share feedback on higher speed VXCs. This is similar to the Send Feedback form in the user profile name menu in the top right corner of the Portal.
* **Resource Tagging** - Customers now have the ability to create, modify, and delete resource tags to manage their active services via the Megaport API. Resource tags are key value pairs that act as metadata for organizing Megaport resources. These tags will appear in the Service Inventory report by default for the company who has implemented the tags providing they own the service the tag is put against.
* **Cancellation Reasons Updated** -- When canceling a service, the reasons that customers are presented with for terminating the service have been updated. An optional comment box has also been added for all cancellation reasons.
* **Update Megaport Marketplace to not Distinguish Between Service Types** -- Changes have been made so you can no longer distinguish between different service types in the Megaport Marketplace. If a customer wants to connect to a service provider in the Megaport Marketplace, they will know who the provider is, what the location is, but won't see the type of service behind it.
* **Add Max Length Validation to Service Level Reference Field** -- Validations have been changed for the Service Level Reference field (costCentre) so that this field now has a maximum value of 255 characters.
* **Service Status Timezone Parameter** -- In the Maintenance & Outages page, you can now view maintenance and outage events affecting services in the time zone of your choice. If you select a time zone on the Maintenance tab, it will apply only to the maintenance events. Similarly, if you select a time zone on the Outages tab, it will apply only to the outage events.
* **Issues fixed:**
* 'Attempted logout was unauthorised' message was incorrectly displayed when a user attempted to log out.
* API was responding with a 400 error instead of a 404 when querying a product that doesn’t exist.
* Re-terming a burst VXC on a 1 year term priced at burst rate instead of new term/speed rate.
* Currency was displayed in AUD instead of the currency set on the billing market when re-terming a Port.
* Incorrect calculation of B-End charges for a VXC after a speed change.
* **New Cisco Secure Firewall Threat Defense Virtual MVE Image** -- A new MVE image FTDV v7.4.2-172 has been released to the Portal and is available for ordering.
* **Terraform v1.1.1 Released** -- A new Terraform version has been released which fixes an issue related to MCR Prefix List Filter with ExpressRoute VXC, and includes other improvements. For more information, see
[https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.1.1](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.1.1).
To keep up to date with all Terraform releases, you can click **Watch** at the top of the [terraform-provider-megaport repository page](https://github.com/megaport/terraform-provider-megaport), from there select **Custom** then the **Releases** check box.
* **Updated Tools Menu in the Portal** -- The Tools menu has been separated into two sections, In-App Tools and Additional Tools. Additional Tools are external to the Portal and will open in a separate browser tab.
The Quoting Tool menu option is not available for managed or distributor account users.
* **Billing Market Restrictions** -- Customers can no longer directly update the Company Legal Name and Business Registration ID captured on a billing market through the Portal or public APIs. Contact your Account Manager or Customer Success Manager to change your Company Legal Name associated with the purchasing entity.
* **Updated Wording on the VXC Ordering Page** -- The wording has been updated to make it more clear and reflect the new changes allowing customers to increase VXC speed during a term.
* **Issue fixed:**
* The A-End location of an IX wasn’t showing when viewing an existing IX. This issue has been fixed and the A-End location is now displayed on the Connection Details page of IX connections.
* **Increase VXC Speed During Contract Term** -- You can now increase the rate limit of a VXC above the original contracted value while the VXC is on a contract term. You can increase the VXC speed to the maximum limit allowed without having to re-term it. For more information, see [Changing the Speed of a Termed VXC](/connections/vxc-termed-rate-change).
The term discount will now appear differently in the invoice for any service ordered on term, not just VXC.
* **New Quoting Tool for Direct Accounts** -- All direct Megaport accounts now have access to the Quoting Tool to generate quotes and estimate service costs, before ordering the services. The Quoting Tool is available at [https://pricing.megaport.com](https://pricing.megaport.com). For more information, see [Quoting Service Cost](/finance/creating-estimates).
Managed account users are restricted from accessing the Quoting Tool.
* **Cisco Secure Firewall Threat Defense Virtual on MVE** -- Cisco Secure Firewall Threat Defense Virtual can now be integrated with MVE and deployed on the Megaport network. Cisco Secure Firewall Threat Defense Virtual uses Cisco's firewall functionality to enable consistent security policies for workloads across physical, virtual, and cloud environments.
Deploying Cisco Secure Firewall Threat Defense Virtual on MVE allows you to create a single security solution in your workflows for personal devices, data centers, and the closest availability zones of your cloud platforms.
For more information, see [Creating an MVE with Cisco Secure Firewall Threat Defense Virtual](/mve/cisco/creating-mve-firewall).
* **Introducing MVE for Aviatrix Secure Edge** -- Aviatrix Secure Edge is now available as a new vendor and product when ordering MVEs.
The integration of Aviatrix with Megaport’s MVE delivers secure, high-performance multicloud and hybrid cloud connectivity, allowing you to connect, secure, and easily manage your cloud environments.
This update includes a set of new topics that describe the Megaport and Aviatrix Secure Edge solution, including overview, deployment, planning, and connection details.
* **Requires a Cloud-init File**: You can obtain this through Aviatrix.
* **vNIC Support**: Minimum of three vNICs, with support for a maximum of five vNICs through Megaport.
For more information, see [Aviatrix Secure Edge with Megaport Virtual Edge](/mve/aviatrix).
* **MVE Configuration Screen Improvements** -- The MVE configuration screen has been streamlined to enhance usability. The product version selection has been moved to the configuration panel on the right in the Service Details section, reducing clutter and eliminating the need to scroll through long lists when ordering an MVE. This update significantly improves the initial vendor selection process.
* **Service Utilization Data Export** -- An **Export CSV** button has been added to the usage graph when editing a service or connection, allowing customers to export their service utilization data as a CSV file.
* **Service Logging Improvements** -- Some improvements have been made to the Service Logs page, including accurately displaying the recorded logs for a given time period, and listing from most recent to oldest. The Service Logs page has also been updated to show a maximum of 100 of the most recent logs for a service.
* **Rackspace Tile Added to Services Page** -- The Rackspace tile has been added to the Add Connection section of the Services page, listed alphabetically after the Megaport products.
* **Service Status Page Updates** -- Additional improvements have been made to the recently released Service Status Page feature based on feedback. Changes include page navigation improvements and the addition of a **Refresh** button to update the page with the latest data.
* **New IX Locations** -- MegaIX is now available in Adelaide, Chicago, and Bay Area, and available for ordering in the Megaport Portal. Megaport's MegaIX is your high-speed express lane to the most in-demand global networks.
* **Move VXC Multiple vNIC Labels** -- Some usability improvements have been made to the vNIC and VLAN field titles when moving the A-End and/or B-End connections to an MVE with multiple vNICs. The text *New* has been added to make it clear these are the new vNIC details, and the popup tooltip was updated with additional information.
* **Improve Searching for B-End Destination of VXC in the Portal** -- Improved the selection of VXC B-End destination when ordering.
* *Port* relabelled with *Destination* instead.
* The destination list can be filtered using a text search on service name and location details.
* **Letter Case Now Ignored When Sorting Private VXC Destinations List Alphabetically** -- Previously, services with titles that started with uppercase letters were all listed first, and then lowercase titles were listed below. This has now been changed so that letter case is ignored when sorting this list alphabetically.
* **Issues fixed:**
* An incorrect message was displayed in the header when editing VXCs for some cloud providers.
* Minor issues that occurred regarding Azure VXC creation from MVEs.
* Speed changes for VXCs (not on term) are now editable. An issue occurred where customers were unable to edit their VXC rate limit.
* **Megaport Docs RSS Feed** -- An RSS Feed has been added to the Megaport Docs which allows you to be notified when an update or change has been made to the documentation. The RSS Feed icon is available at the bottom right of each page. Simply subscribe to the feed using an RSS reader, for example, Slack or Feedly, to keep up to date with information about all of our latest features!
* **Connecting to Cisco Webex** -- A new topic has been created that describes how to connect a Port to Cisco Webex Edge Connect. For more information, see [Connecting to Cisco Webex Edge Connect with Megaport](/cloud/megaport/cisco/webex).
* **Service Key Support for MCR and MVE** -- In the Megaport Portal, you can now create a service key for an MCR and MVE. A customer or other business can now connect to your Port, MCR, or MVE via a service key.
* **All keys** -- The owner of the B-End (service key provider) can change the name of the VXC at their end to something more meaningful after the VXC has been created by the other party (A-End). This will not affect the name of the VXC with the A-End customer.
* **All keys** -- Only the owner of the VXC can request a speed change, up to and including the maximum set by the service key creator. An approval by the creator of the service key will be required before the change happens. An email will be sent advising of the speed change request.
* **MCR keys** -- Can add B-End configuration information relating to the MCR when creating a single-use service key.
* **MVE keys** -- Can add Preferred B-End VLAN information when creating a single-use service key.
For more information, see [Setting up Service Keys](/marketplace/service-keys).
* **Service Status Page Update** -- Services affected by an ongoing maintenance or outage event are now flagged on the Services page. You can view details about the maintenance or outage in the Maintenance & Outages page.
* **Allow Megaport Internet VXC to MVE in Another Country** -- You can now order an MVE in a country where there is no Megaport Internet connection but there is the necessary compute infrastructure to support MVEs. For example, an MVE located in Ireland can order a Megaport Internet VXC to the UK. Previously both had to exist in the same country to order an MVE. This update allows you to select Megaport Internet for MVEs in countries outside the one where you are placing the order.
* **Support for Monitoring Maintenance and Outage Events** -- The Maintenance & Outages page allows you to monitor events that affect your services, including current, scheduled, and past events.
By staying informed about maintenance activities and service outages, you can plan effectively around scheduled maintenance and provide faster responses during unplanned outages.
Access to the Maintenance & Outages page is also available to both partners and managed accounts.
For more information, see [Monitoring Maintenance and Outage Events](/portal-admin/monitoring-events).
* **Cancellation Reasons Updated** -- When canceling a service, the reasons that customers are presented with for terminating the service have been updated.
* **Hyperforce on AWS** -- A new topic has been created that describes how to use Megaport to deploy the AWS Direct Connect (Hosted Connection) architecture for Salesforce Hyperforce support using a public VIF. For more information, see [Integrating Megaport with Salesforce Hyperforce on AWS](/cloud/megaport/aws/hyperforce).
* **Issues fixed:**
* Megaport Internet connections for MVEs can be created with individual Service Level References (SLRs), but if the associated MVE is updated, even just by changing the name, the SLRs of all Megaport Internet connections for that MVE were being overwritten with the MVE's SLR. The SLR of Megaport Internet connections attached to MVEs are now independent and are not updated if the MVE SLR is updated.
* NPE errors were occurring in the /v2/employment endpoint because the user did not have an email address defined.
* **Megaport Internet Available in More Countries** -- Megaport Internet connections can now also be ordered from Ports and MCRs in New Zealand, Canada, and Singapore, in addition to Australia, UK and the US where it was already available.
* **Move VXC on MVE Enhancements** -- You can now move a VXC to a different vNIC on the same MVE. When moving a VXC between MVEs, you can now also select the required vNIC on the destination MVE.
* **Service Key VLAN Validation** -- Validation has been added to the VLAN field when creating a service key for a Port. The VLAN value entered must be between 2 and 4093.
* **Service Inventory Report** -- This report has been improved to support companies with a large number of services. The reporting of service termination date and time has also been improved.
* **Issues fixed:**
* When filtering services by contract term of 12 months, the Megaport Portal filter was not returning the correct contract term. Month to month was being shown instead.
* The monthly rate was not being shown when editing a service key VXC.
* Rate limit for a service key VXC could be set to a value greater than the maximum rate limit.
* **Pricing Tool enhancements** -- The following is now available in the Pricing Tool:
* A-End Type selection for VXC. Port is selected by default but can be changed to MCR or MVE.
* You can now select Megaport Internet as the VXC connection type. Megaport Internet is available if:
* A-End type is MCR, Port is in UK, US, or AU, and B-End location is in the same country as the A-End location.
* A-End type is MVE and the B-End location is in the same country as the A-End location.
In all other scenarios, Megaport Internet is grayed out and cannot be selected.
* **MCR VXC BGP Prefix Filter** -- Updated the MCR VXC BGP Prefix Filter from *None* in the Megaport Portal to *No Prefix Filter* and updated the related text accordingly. This was done to clarify the meaning of the option, that no import or export prefix filter is applied and all valid routes are allowed.
* **Extra Actions Drop-Down** -- A usability improvement has been made to the new Extra Actions drop-down menu in the Megaport Portal Services page. The previous Expand/Collapse options have been changed to a single dynamic menu option for either expanding or collapsing all services.
* **Service Keys for Ports** -- Service keys for Ports have been updated in the Megaport Portal. The Service Key screen has had a refresh and the Megaport Portal has changed from displaying an 8 character service key to the full 36 character UUID.
* **Issues fixed:**
* When updating the VXC rate limit, some customers were getting into a loop. This is no longer occurring.
* Rate limit for a service key VXC can be set to more than the maximum rate limit. A VXC now cannot be updated above the maximum rate.
* **GSA/GRA Updated** -- Megaport has updated the standard Global Services Agreement (GSA) and Global Reseller Agreement (GRA) terms (in accordance with Clauses 15(a) and 20(a) respectively). As part of this update, the early termination fee (ETF) applied to a service on a contract that is canceled before the term is complete has changed from 50% to 100%. This change took effect in the Megaport Portal on April 15, 2024.
* **Service Inventory Report in the Megaport Portal** -- A feature has been added to the Megaport Portal that allows you to download your service inventory including historical services. The report is saved in comma-separated values (CSV) file format and can be downloaded from the Extra Actions > Download Inventory Report option in the Services page.\
For more information, see [Downloading a service inventory](/portal-admin/services-page#service-inventory).
* **Service Filters** -- You can now search for and filter by VXCs on a term in the Megaport Portal Services page.
* **Read Only User Changes** -- Read Only users can now:
* View the MCR prefix list
* View AWS connection details
* On the VXC/MCR Configuration page:
* See if Q-in-Q is on or off
* Access BGP connection to see the settings and filters
* **Added Account Manager and Customer Success Manager Fields** -- New fields Account Manager and Customer Success Manager have been added to the Support Details page in the Megaport Portal.
* **Other updates:**
* Improved services filtering speed.
* Fixed an issue with the price displayed when re-terming a VXC and increasing the rate limit.
* Japanese, French, Spanish, and German documentation has been updated with recent content. Updates include information on:
* setting up Single Sign-On (SSO) in the Megaport Portal.
* provisioning a cloud VXC to IBM Cloud Direct Link.
* the new notification group for service up and service down events (Service Status).
* how to shut down and re-enable VXC and IX services for failover testing.
* connecting to France-IX.
* adding up to five Virtual Network Interface Cards (vNICs) to a Megaport Virtual Edge (MVE).
* using the new interactive map view of services.
* how to move a VXC and IX across Ports, MCRs, and MVEs.
* how to add and edit reverse DNS for IX connections.
* how to order Megaport Internet connections from Ports and MCRs.
For access from any page, use the menu in the upper-right corner to select a language.
* **More Metro Availability in MVE-enabled Markets** -- Thanks to some recent improvements in the Megaport network, you can now deploy MVEs in more metro markets. MVEs can now be deployed in these additional locations: Australia (Brisbane), Canada (Montreal), Germany (Berlin), Mexico (Querétaro), and USA (Las Vegas and Portland).
For an exact and up-to-date list of available locations, see the [Megaport Enabled Locations page](https://www.megaport.com/megaport-enabled-locations/) on our website and select **MVE Enabled Locations**.
* **Show Pricing for Terms in the Megaport Portal** -- When creating a new service, you can now easily see the pricing for contract terms in the Portal. The way pricing is displayed now, you can immediately see the price for the available contract terms options, and the cost benefit of signing up to a term. The default term of 12 Months is selected for VXCs, Ports, MCRs, and MVEs.
* **Services Filtering** -- New filter options are available to give you a better Portal experience. Full text search capability in the Portal was available previously, however, this has been enhanced by a new option which allows you to select the service type and contract term to filter on. The sorting options have also been improved, with the ability to choose Creation Date, Name, or Service Location as your ascending/descending service list sort view.\
For more information, see [Filtering and sorting services](/portal-admin/services-page#filter).
* **Deep Linking Supported in the Megaport Portal** -- Customers that need to follow an approval pipeline project, rejoice! All in-portal links (previously only available to logged-in users) are now shareable and arrive at the same screen for other users within that account, following their authentication (and subject to user permissions). This allows documentation to be populated with specific references to Portal URLs, which will trigger the authentication process and arrive on the specific screen referenced rather than simply defaulting to the Services page or Portal dashboard.
* **Wasabi Technologies Support** -- Megaport now supports connectivity to Wasabi Direct Connect (WDX). Customers can enable multiple VXCs to Wasabi from a single location, providing the scalability and agility required in response to evolving business needs. To create a connection from a Megaport Port to a Wasabi Technologies cloud storage service, you will need a service key.\
For more information, see [Connecting to Wasabi with Megaport](/cloud/megaport/wasabi).
* **VXC Shutdown Added to the Create Screen** -- The VXC and IX shutdown feature has been expanded so that you can now shut down a VXC and IX service when creating the service. Previously it could be done only when editing the service.
* **MCR and MVE Diversity** -- You can now choose a diversity zone in the Megaport Portal when creating MCRs and MVEs. A new diversity zone filter is available on the Locations tab when setting up an MCR and MVE. Selection is set to *Auto* by default, meaning if you don’t select blue or red diversity zone, the zone is chosen automatically. Tool tips are also available for the new diversity selection.\
The diversity zone in which the service will be deployed is visible throughout the set up process. When choosing a diversity zone, only locations that have capacity on the selected diversity zone are displayed.\
For more information, see [MCR and MVE Diversity](/mcr/mcr-mve-diversity).
* **Megaport Internet Long Haul** -- Megaport Internet VXCs can now be ordered long haul from Ports, MCRs, and MVEs within the same country. Port and MCR Megaport Internet VXCs remain available only in the UK, US, and AUS.\
When adding a Megaport Internet connection from an MVE, you are now prompted to select the destination Port. Previously a destination Port in the same diversity zone as the MVE was assigned automatically.
* **VXC Inner VLAN Tags** -- The requirement for VXC inner VLAN tags to match in the Megaport Portal has been removed. This means when ordering a private VXC between two MVEs, you can select the A-End VLAN and B-End VLAN, and these can be different.\
When ordering an Azure connection from an MVE, if you tag the preferred A-End VLAN, you can now also set a different Azure peering VLAN.
* **Updated MVE pop-up documentation links with vendor specific links** -- Previously when you set up an MVE connection, you were presented with a pop-up which had vendor specific wording in the first two lines, but the link for more information opened a generic documentation landing page. This has been improved so that the link now opens a vendor specific MVE overview page.
* **Lookup AWS HC Bandwidth** -- The Megaport Portal now fetches bandwidths for AWS HC via API. This ensures that the information being provided to the customer is up to date and correct. This enhancement also applies to the Deal Estimator. A new public API `/v2/secure/awshc` has also been created for this purpose.
* **Customer Maintenance Notifications for New Services** -- Now if you order a service in a location where planned maintenance work is required, you will be notified by email within a minimum of 24 hours. The service is then included in all future ENS planned maintenance notifications.
* **New IX Locations** -- MegaIX is now available in Denver, Atlanta, Miami, and New York, and available for ordering in the Megaport Portal. Megaport's MegaIX is your high-speed express lane to the most in-demand global networks.
* **Issues fixed:**
* When you edit a deployed IX, the VLAN validation API call was not being made.
* After approving or rejecting a connection, the services page breaks.
# 2025 Release Notes
Source: https://docs.megaport.com/whatsnew/2025
This help topic describes changes and enhancements made to the Megaport Portal during 2025.
* **Italian Language Support** -- Italian is now a supported language in the Megaport Portal. To change your language preference, select **Language** from the user menu.
* **Megaport Internet in Italy** -- Megaport Internet connections can now be ordered from Ports and MCRs in Italy. Previously, you could only order Megaport Internet from an MVE in Italy.\
For more information, see [Megaport Internet Overview](/megaport-internet).
* **Megaport Internet via IPsec-enabled MCR** – Megaport Internet via IPsec-enabled MCR is now available in the Netherlands, Hong Kong, and Mexico.
* **Service Inventory Report Enhancement** -- An additional column called **Monthly Rate** has been added to the report, which shows the monthly rate for each service. This allows you to use the report for budget planning and validating monthly invoice amounts.
* **400 Gbps Ports Filter Added to Dashboard** -- A new filter called **400 Gbps Ports Available** has been added to the Megaport Portal Dashboard, which allows you to filter the dashboard to only show locations that support 400 Gbps Ports.
* **Oracle Cloud Infrastructure (OCI) Locations** -- You can now view the OCI Onramp locations in the Megaport Portal, including the latency information, while creating a VXC to Oracle Cloud.
* **GCP Locations** -- You can now view the Google Partner locations in the Megaport Portal, including the latency information, while creating a VXC to Google Cloud.
* **New Date Field Added** -- The **Last Updated** field has been added to the User Profile screen in the Portal, which allows you to keep track of your account activity and history.
* **Quoting Tool IPsec Add-on Enhancement** -- You can now add IPsec as an add-on to a quote when pricing an MCR in the Quoting Tool.
* **Issues fixed:**
* When creating an MVE in the Portal, changing the product version after viewing available locations does not refresh the location and capacity data, which remains based on the initially selected version.
* A VXC between two Ports displays duplicate VXC prices in the checkout screen.
* **Latitude.sh and Megaport Integration** -- We have created a seamless integration between the Megaport and Latitude.sh portals so customers can easily navigate between both in order to configure network connectivity and cloud infrastructure. From the Megaport Portal Services page, there is a new option called **Order Bare Metal** which allows you to click through to the Latitude.sh portal to order high-speed connectivity to Bare Metal Cloud.
* **New User Invite Email Improvements** -- Company admins can now resend invitation emails to users who have not yet activated their accounts. New temporary passwords are generated automatically and are valid for 24 hours. The new invitation email and temporary password are sent using the new **Resend Invite** button in the Manage Users screen, and work whether the original temporary password is still valid or has expired.\
For more information, see [Inviting Users to Your Account](/setting-up/inviting-users).
* **Introducing the Support Requests Portal** -- We have added more ways for you to get support. The Support Requests Portal is a dedicated hub for managing all your support cases in one centralized location. The portal offers:
* **Streamlined case creation** -- Five targeted request types ensure faster routing to the right team.
* **Complete case tracking** -- Monitor cases from creation through resolution with clear, easy-to-understand status indicators.
* **Team collaboration** -- Add collaborators and attach files to provide complete context for your cases.
You can access the portal through Megaport Portal > User Menu > Support Requests.
The Support Requests Portal is available to direct accounts, partners, and some managed accounts under certain conditions. Managed accounts without chat enabled will not be able to access support requests. Partners can create requests on behalf of any of their managed accounts.
* **Upload LOA to the Megaport Portal** -- You can now upload a Letter of Authorization (LOA) directly in the Portal when ordering a Cross Connect with a new Port. An **Upload LOA** option will be displayed for the Port, allowing you to upload a PDF form shortly after the service is ordered. You will then receive an email from Megaport with a case reference number and instructions for completing your order.\
For more information, see [Ordering a Cross Connect](/connections/cross-connect).
* **Service Inventory Report Enhancements** -- These changes have been made to improve the Service Inventory report:
* **Standardized date/time format** -- The format of the date fields has been changed to be UTC with an offset time zone, following the OSI standard.
* **New Last Updated Date column** - Shows the last time that the service was updated.
* **New Auto Renew column** - Shows TRUE/FALSE to quickly indicate whether a service is set to auto-renew. This helps you plan for upcoming changes, decide whether to renew, and contact your Megaport Account Manager early to lock in current pricing.
* **New Add-Ons column** - Shows the specific details of additional services, such as Cross Connects and IPSec. This allows you to easily identify and track service configuration for accurate budgeting and invoice validation.
* **Switzerland Billing Market VAT Onboarding Questions** -- For the Switzerland billing market, you must now indicate whether you are registered for value-added tax (VAT). Registered users must also provide their VAT registration number.
* **Remove Terminate Later for Ports** -- We have removed the option to select terminate **Later** in the Terminate Services window for all Ports (with or without a minimum term). Port termination now supports immediate cancellation only and clearly displays any applicable early termination fees (ETF). This change provides customers with a clearer, more predictable experience when ending services and understanding any applicable charges.
* **Terraform v1.4.6** -- Version 1.4.6 of the Terraform provider has been released. This is a small release that fixes a Port/VXC validation bug with larger contract terms. 48 and 60-month contract term periods should now work without issues on Port/MVE/MCR/VXC where available. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.6](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.6).
* **Terraform v1.4.5** -- Version 1.4.5 of the Terraform provider has been released. The main fix in this release involves VLAN and Inner VLAN values in the VXC Resource. Documentation was also added for [Terraform MCP Server](https://github.com/megaport/terraform-provider-megaport/blob/main/terraform-mcp-server.md) and [Location Data Source and using Location IDs](https://github.com/megaport/terraform-provider-megaport/tree/main?tab=readme-ov-file#datacenter-location-data-source). For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.5](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.5).
* **IPsec on MCR in Singapore** -- Changes have been made so you can now enable and use IPsec on MCR in Singapore.
* **Improved Embedded Help Linking** -- Some of the documentation links in field popups in the Portal have been improved to provide more focused and context-sensitive help:
* **MVE Configuration** -- The Admin Password and other field pop-up links have been updated for various vendors to link directly to the documentation for that vendor.
* **Service Billing Details tab** -- Previously, the **pricing documentation** link on the Service Billing Details page linked to the same documentation page. Now the link opens the pricing page in the Megaport Documentation relevant to the service type you are viewing.
* **Issue fixed:**
* When configuring a VXC to IBM Cloud, the Preferred A-End VLAN field was greyed out in the Megaport Portal, meaning that the user could not specify or modify the VLAN. This issue did not occur for other CSPs.
* **Introducing MVE for Juniper SSR** -- Juniper Session Smart Router (SSR) is now available as a vendor and product option when ordering MVEs. Built on Secure Vector Routing (SVR), Juniper SSR replaces complex tunnel-based overlays with a secure, high-performance, application-aware SD-WAN. Managed through the Juniper Mist cloud, it simplifies operations and delivers dynamic, secure connectivity across branches, remote sites, and multicloud environments.\
Deploying Juniper SSR on Megaport Virtual Edge (MVE) extends these capabilities over Megaport’s global private SDN, combining intelligent overlays with resilient underlay connectivity.\
For more information, see [Juniper with Megaport Virtual Edge](/mve/juniper).
* **IPsec Tunnels Increased to 30** -- Customers can now choose up to 30 IPsec tunnels on an MCR, in packs of 10. This provides the ability to scale IPsec integrations as required. The number of tunnels can be defined both when creating an MCR and editing an existing MCR. The destination IP address of the tunnel must be an IP address not configured on the same MCR.\
For more information, see [Using IPsec with MCR](/mcr/ipsec-mcr).
* **More Term Options Available** -- For all termed services, you can now order a service on 48 and 60-month terms.
* **MCR BGP Alerting** -- We’ve introduced MCR BGP alerting, allowing you to opt in to receive service status email notifications when a BGP session status changes (Up or Down). If a session is flapping, only one email per hour will be sent. Users who are already subscribed to receive service status email notifications are automatically subscribed to BGP status notifications.
* **API Key Limit Increased** -- The maximum number of API keys that can be created per company has been increased from five to 100. For more information, see [Megaport Limits and Quotas](/limits-quotas).
* **Megaport Internet in Sweden** -- Megaport Internet connections can now be ordered from Ports and MCRs in Sweden. Previously, you could only order Megaport Internet from an MVE in Sweden.\
For more information, see [Megaport Internet Overview](/megaport-internet).
* **Activity Log Updates** -- These improvements have been made to the activity logs:
* The Activity Name filter in the Company Activity page now shows only the activities that have been performed, improving relevance and usability.
* Activity log retention has been increased from 60 days to 6 months, allowing for longer-term auditing.
* Improved consistency and readability of logs.
* **Terraform v1.4.4** -- Version 1.4.4 of the Terraform provider has been released. The key updates in this release include:
* Improved documentation for `preventDestroy` as well as our safeguards for deletion with attached resources.
* Improved documentation for the `admin_password_hash` field for Palo Alto MVE vendor configuration.
* Improved documentation for location data source examples and using a permanent ID for sustainability.
* Support of 400 Gbps Ports in locations where available.
* Support for 48 and 60-month contract terms for Ports, VXCs, MCRs, and MVEs.
* New MCR Prefix Filter List standalone resource. For more information about this feature, see
[NEW FEATURE: MCR Prefix Filter List Resources](https://github.com/megaport/terraform-provider-megaport?tab=readme-ov-file#-new-feature-mcr-prefix-filter-list-resources).
For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.4](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.4).
* **IPsec add-on for MCR** -- An IPsec add-on for MCR is now available, which provides secure, encrypted connectivity (offering integrity, confidentiality, and authentication) for customers connecting branch offices, remote users, or other clouds directly into their Megaport network. This feature is currently available in all markets except Singapore. Customers can enable IPsec when creating or editing an MCR, which grants them a pack of 10 tunnels. This allocation is consumed when configuring tunnels on a VXC, requiring mandatory fields like Source IP, Destination IP, and Pre-Shared Key.\
For more information, see [Using IPsec with MCR](/mcr/ipsec-mcr).
* **Introducing MVE for Anapaya** -- Anapaya is now available as a new vendor and product when ordering MVEs. Built on the SCION (Scalability, Control, and Isolation On Next-Generation Networks) Internet architecture, Anapaya delivers secure, high-performance connectivity with enhanced availability and control for critical applications and cloud environments. Integrating Anapaya with Megaport Virtual Edge (MVE) extends these capabilities over Megaport’s global private SDN, combining resilient underlay connectivity with policy-based, secure overlays. For more information, see [Anapaya with Megaport Virtual Edge](/mve/anapaya).
* **Azure Onramp Locations in the Portal** -- Customers selecting Microsoft Azure on-premises previously needed to provide a service key to view available locations, and latency information was not shown. With our recent improvements, customers can now see all locations and their latency information without first entering a service key. The new workflow still allows you to proceed to the pricing page, but you must provide a service key and select a location to continue further.
* **Megaport Internet in Brazil** -- Megaport Internet connections can now be ordered from Ports and MCRs in Brazil. Previously, you could only order Megaport Internet from an MVE in Brazil.\
For more information, see [Megaport Internet Overview](/megaport-internet).
* **Customer ASN Valid Values Updated for IBM** -- The `customer_asn` is an integer that identifies your network’s Autonomous System Number. We have updated the supported `customer_asn` ranges for IBM as follows:
* **Valid Ranges**: 1-65401, 65434-4201064999, 4201066000-4294967294
* **Excluded Ranges**: 65201-65234
* **Excluded Values**: 13884, 36351, 64512, 64513, 65100, 65500, 65516, 65519, 65521, 65531
* **Terraform v1.4.3** -- Version 1.4.3 of the Terraform provider has been released. The key updates in this release include Fortinet MVE transit VXC documentation example updates and a change to support the update of the cost centre from a defined value to null. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.3](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.3).
* **Terraform v1.4.2** -- Version 1.4.2 of the Terraform provider has been released. This release fixes minor bugs involving VXC updates in the provider. It also allows you to manually input product UID for end configurations for partner ports, which is particularly useful for Google Cloud VXCs where the service key might be open to a selection of ports. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.2](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.2).
* **Activity Log Updates** -- These improvements have been made to the activity logs:
* The search for Company Activity logs has now been expanded to search full log details, including the information contained in the **More Details** option.
* Company Admin users can now view activity logs for a specific service. From the **Logs** tab of the service details page, click **User Logs** to view only the logs relevant to that service.
* **Megaport Translation Update** -- An updated translation is now available in Japanese for the Megaport Documentation. Updates include translations for all Portal features that were released this year. For access from any page, use the menu in the upper-right corner to select the language.
* **Bulgarian Market Currency** -- In preparation for Bulgaria's Euro adoption on 1 January 2026, BGN has been removed as an available currency when enabling a Bulgarian billing market. Now EUR and USD are the available currencies, with EUR remaining the default currency.
* **Indicate Interface Source of BGP Peering** -- We have improved the MCR Looking Glass to show the interface source (status) of the BGP peering (IPsec or Standard Interface) through a new icon and hover text.
* **Updated VMware Icon and Labels to Arista VeloCloud** -- In the Megaport Portal, all branding for the VMware MVE offering has been changed to Arista VeloCloud.
* **FortiOS Version 7.6 Available** -- FortiOS version 7.6 is now available when creating a Fortinet Fortigate MVE in the Megaport Portal.
* **Introducing MVE for Cisco Meraki** -- Cisco Meraki is now available as a new product when ordering MVEs. Cisco Meraki offers cloud-managed network solutions that can be integrated with Megaport Virtual Edge (MVE) to extend the capabilities of your network with simplified management and scalability. For more information, see [Cisco Meraki with Megaport Virtual Edge](/mve/cisco/creating-mve-meraki).
Cisco Meraki is currently in public Beta. Do not deploy without first contacting your Megaport Account Manager.
* **IP Address Ordering in the Portal** -- Customers can now request a public IP address for a Megaport Internet connection in the Portal. The connection must be in the Configured or Live state before an IP address can be ordered. When submitting the request, you need to select the subnet size and review the terms, which are separate from and in addition to the GSA. Requests are processed by Megaport within 48 hours. For more information, see [Requesting additional IP addresses](/megaport-internet/routing#IPaddress).
An IP address can only be ordered for a Megaport Internet connection on a 12-month or longer term.
* **400 Gbps Ports Now Available!** -- You can now order a 400 Gbps Port in the Portal. Please contact your Megaport Sales Representative with any questions regarding location availability.
* **Activity Logs Search Improvement** -- The activity log search in the Portal is now case-insensitive. This enhancement improves search results and makes it easier to find the log information you need.
* **MCR Interface Improvement for Q-in-Q** -- On the MCR A-End Connection Details tab of the VXC Connection Details page, the Enable Q-in-Q option has been moved next to the Virtual LAN ID field (for single sub-interface connections). For multi sub-interface configurations, Q-in-Q is always enabled, so the button is not shown.
* **Update vNIC Description After MVE Deployment** -- Based on user feedback, an improvement has been made which allows you to update vNIC descriptions for an MVE after the MVE has been deployed.
* **Show/Hide Navigation Feature** -- The Megaport documentation site now has a show/hide navigation option, located at the top of the contents pane on the left. Click this toggle to hide the right and left navigation panes, which maximizes the content area and allows you to focus solely on the documentation. Click the toggle again to display the navigation panes.
* **Terraform v1.4.1** -- Version 1.4.1 of the Terraform provider has been released. This version fixes an issue with some MVE vendor configurations, such as Cisco SD-WAN, failing API validation. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.1](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.1).
* **Terraform v1.4.0** -- Version 1.4.0 of the Terraform provider has been released. This version includes some breaking changes that require immediate attention:
* We’ve updated to `v3` of the Megaport Locations API which includes breaking changes. The `v2` version of the Locations API is now deprecated. Please upgrade to v1.4.0 of the Megaport Terraform Provider as soon as you can.\
For more information, see [API Deprecation Notices and Frequently Asked Questions (FAQs)](/troubleshooting/api-v2-faq).
* The `site_code` filter is no longer supported and will cause configuration failures. You must migrate to use the `id` (recommended) or `name` filters instead. Several location fields are now deprecated and will display warnings. Please review [the migration guide](https://github.com/megaport/terraform-provider-megaport?tab=readme-ov-file#-breaking-change-location-data-source-migration) and update your configurations promptly to avoid service disruption.
For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.0](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.0).
* **Issues fixed**:
* Activity log description filter was applied only on the second attempt.
* Incorrect maximum word count for the Marketplace company bio.
* A customer couldn’t add a user due to the phone number format.
* **Introducing MVE for Check Point CloudGuard** -- Check Point CloudGuard is now available as a new vendor and product when ordering MVEs. Check Point CloudGuard delivers enterprise‑grade network security integrated with Megaport Virtual Edge (MVE), combining advanced threat prevention, centralized policy management, and flexible, scalable connectivity for distributed enterprise networks. This initial release supports one vNIC per MVE.\
For more information, see [Check Point CloudGuard with Megaport Virtual Edge](/mve/checkpoint).
* **Temporary Password Expiry Updated** -- The expiry limit for invitation emails sent to Megaport users has been reduced from 7 days to 24 hours. This change has several benefits, including faster user onboarding and a reduced risk of malicious use, for example, when invitations are left open too long or sent to an incorrect or compromised email address.
* **Request Higher Speed Feature** -- Based on user feedback, improvements have been made to the request higher speed feature, located next to the **Rate Limit** field for a connection. These improvements include:
* Always displaying the minimum and maximum supported speeds (hard limits) as help text under the field.
* Showing a clear alert message when you enter a speed higher than the supported (soft) limit.
* Displaying the unit (Mbps) inside the field to remove any ambiguity about the required speed format.
* **Filter Services by User** -- On the Services page, you can now filter the list to show only the services you have created. A new filter option called **Current User** has been added to the service filter list to make it easier to view and manage your own services.
* **Aruba EC-V MVE Storage** -- The Aruba EC-V MVE storage has been increased from 30 GB to 60 GB.
* **Terraform v1.3.9** -- Version 1.3.9 of the Terraform provider has been released. This version includes various improvements, bug fixes, and documentation updates. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.9](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.9).
The Megaport Terraform Provider is updated frequently to include new features, improvements, and bug fixes. To ensure compatibility and avoid potential errors, we recommend using the latest provider version in your `.tf` configuration file. To check for the latest version, see [https://github.com/megaport/terraform-provider-megaport/releases](https://github.com/megaport/terraform-provider-megaport/releases).
* **Issue fixed**:
* A 408 timeout error was occurring when the MCR Looking Glass was loading routes in the Portal.
* **Megaport Internet Higher Bandwidth** -- You can now order Megaport Internet connections up to 25 Gbps via the Portal and the API. However, there are some limitations to be aware of:
* 25 Gbps Megaport Internet is currently available only in AU and US. Additional countries will be supported in the future.
* This speed is available only in select metros, where the required transit uplinks are in place.
* Available from Ports, MCRs, and MVEs deployed on the new high-performance compute platform. MVEs on older platforms are restricted to 10 Gbps transit.
* **Megaport Internet in Ireland and Switzerland** -- Megaport Internet connections can now be ordered from Ports and MCRs in Ireland and Switzerland. Previously, you could only order Megaport Internet from an MVE in Ireland and Switzerland. For more information, see [Megaport Internet Overview](/megaport-internet).
* **Activity Logs Added** -- These Portal activities have been added to the Activity Log:
* Enabling, resetting, and disabling Multi-Factor Authentication (MFA)
* Updating user notification settings
* Updating user profiles
* Locking and unlocking services
* Creating and updating resource tags
* Updating service terms
* Creating and updating a managed account
* Creating a Megaport Marketplace profile
* Creating and updating Prefix Filter and Packet Filter lists
* **Quoting Tool Improvements** -- These improvements have been made to the Quoting Tool:
* Added Roll Up Discounts and Include Partner Discounts options to the quote summary. This allows for a cleaner quote display and for partners to generate quotes to share with their managed accounts, where discounts are not shown.
* Quotes can now be created for Megaport Internet connections up to 25 Gbps in supported metros.
* **Megaport Documentation Available in Italian** -- The Megaport Documentation is now available in Italian. To access this version from any page, click the globe menu in the top right corner and select **Italiano**. You can also access the Italian version directly here.
* **Terraform v1.3.8** -- Version 1.3.8 of the Terraform provider has been released. This version includes various improvements and bug fixes. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.8](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.8).
* **Terraform v1.3.7** -- Version 1.3.7 of the Terraform provider has been released. This version includes these changes:
* **OpenTofu Compatibility** -- Tested in CI and currently supported. Installation instructions added to the docs.
* **VXC Attachment Deletion Protection** -- The `safeDelete` capability has been added to the Port, MCR, and MVE resources. Resources that have one or more VXCs attached will no longer be deleted when a delete request is made via the API.
* **Updating vNIC Index in VXC** -- Added vNIC index fields for VXC updates and added acceptance tests for MVE to MVE VXC migration.
* **CI Improvements** -- Added retry logic to linter and specified version for CI-lint, testing for OpenTofu compatibility in Github runner, and improved test coverage across the provider.
* **Improved ASN Handling** -- The handling of autonomous system number (ASN) values in MCR resources has been fixed.
* **MCR Diversity Zone** -- Fixed diversity zone field computation for MCRs.
* **Oracle VXCs** -- Fixed Oracle VXC CSP connection issues.
* **Untagged Inner VLANs in VXC** -- Fixed inner VLAN untagged (-1) handling in VXC updates.
* **MCR Prefix Filter List Edge Case Fix** -- Ensured consistent representation of empty MCR prefix filter lists.
For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.7](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.7).
* **Megaport Marketplace Destinations** -- You can now see the same available destinations (interconnect locations) when accessing the +Connection > Megaport Marketplace tile on the Services page, as you do when going directly to the Megaport Marketplace.
* **Megaport Internet BGP Connection Requests** -- You can now request BGP configuration updates from within the Megaport Portal for Megaport Internet connections. This process involves ordering the Megaport Internet connection first and then requesting the BGP parameters on the Megaport Internet tab of the Connection Details page. The Megaport Internet connection can be from a Port, MCR, or MVE.
* **Issues fixed**:
* VXC and IX were not repriced correctly when the currency was changed in the Quoting Tool.
* An MVE term change issue occurred when the MVE was added to the cart and then edited. After the edit, the term information was missing.
* The billing amount was not being displayed on the Billing tab of the Connection Details page.
* **MVE Ordering Workflow** -- We've simplified the MVE ordering workflow for customers. In the new workflow, you simply choose an MVE vendor image, and the Portal will handle all of the backend intelligence, guiding you to available deployment locations and sizes through validation and dynamic filtering. This means a much more intuitive user experience.\
Additional changes as part of this enhancement include:
* New MVE image sizes are available (currently for 6WIND, Fortinet and Palo Alto only - at selected locations):
* 16 core (vCPU) / 64 GB RAM
* 32 core (vCPU) / 128 GB RAM
* 12 core (vCPU) / 48 GB RAM has now been deprecated
* An information panel has been added to the bottom of the Configure Service screen to help customers configure MVEs.
* **Quoting Tool Improvements** -- Various updates and improvements have been made to the Quoting Tool, including:
* The Multi-Factor Authentication (MFA) workflow in the Quoting Tool has been updated to be the same as the Megaport Portal. This supports username and password, Single Sign-On (SSO), and Google. Users will now have a more consistent login experience across both applications.\
For more information about MFA, see [Multi-Factor Authentication](/setting-up/enforcing-mfa).
* You can now search for quotes by quote ID or the first 8 characters of the quote.
* The formatting of the PDF quote has been improved, including making the *Discount* column consistent for each product, grouping sub-totals by product type, and improving the overall PDF presentation and styling.
* **Cross Connect Ordering Updates** -- Improvements to email workflows for Ports with and without Cross Connects, UX improvements, and added information about prerequisites, expected timelines, and revised Cross Connect terms.
* **Activity Logging Updates** -- These additional activities have been added to the activity log in the Megaport Portal for improved audit reporting and history:
* Credit Cards -- Any changes made to credit card payment set up, and if payments were made. Activities include card registration, update, removal, or payment successful.
* Billing Market -- Any changes made to the billing market configuration, including billing market enabled and updated.
* Service Key -- A log is created when a user successfully adds, updates, or deletes a service key.
* **Megaport Internet in Spain** -- Megaport Internet connections can now be ordered from Ports and MCRs in Spain. Previously, you could only order Megaport Internet from an MVE in Spain.\
For more information, see [Megaport Internet Overview](/megaport-internet).
* **Megaport Marketplace Improvements** -- These enhancements have been made to the Megaport Marketplace:
* Added new exchanges (AIx, FSx, VVx) to the Provider Type filter in the Megaport Marketplace and updated the About settings to list these exchanges under a new Exchanges heading.
* Enabled vendors and customers on the Megaport Marketplace to view and navigate exchanges via dedicated tabs, improving discoverability and association with target markets.
* **User Menu Settings Separated out to User and Admin** -- Based on user feedback relating to the recently released User Menu (top right corner of the Portal), the previous single Settings menu has been separated out to User Settings and Admin Settings. This makes it easier for customers to navigate these menu options and perform tasks, such as downloading invoices.
* **Prefix and Packet Filter Lists Doc Links** -- On the MCR Configuration page in the Portal, the documentation links have been updated to link to specific information about prefix filter lists and packet filter lists. This helps customers create prefix and packet filter lists when configuring an MCR.
* **Issues fixed**:
* The Azure ExpressRoute configuration page was not hiding the BGP shared key. The key now shows as asterisks instead of the actual key.
* The customer was unable to update the rate limit from 200 Mbps to 500 Mbps and was receiving an error.
* Using the +Ports command on a LAG was not working. This has been fixed, and all additional Ports are now correctly nested under the LAG.
* Occasionally, the MCR size options listed in the Portal location do not match available capacity.
* **Activity Logging Improvements** -- These additional improvements have been made to the activity logging functionality in the Megaport Portal:
* API keys are no longer associated with a specific user and will only show under the Company Activity logs.
* Users will only see their own logs under the User Activity option in the Portal settings menu (no longer includes API keys).
* New free text search functionality is available in the Company Activity option for Company Admins.
* New activity log filters are available - you can now filter logs by date, description, user type, and specific user.
* **Jumbo Frame Support on MCR** -- A new field called IP Maximum Transmission Unit (MTU) has been added to the MCR A-End Connection Details page. This field allows you to set the largest size (in bytes) of an IP packet that can be sent over the connected VXC. You can define jumbo frames above the standard 1500 bytes (MTU), up to a maximum of 9074 bytes, for use in high-performance networks to reduce overhead and improve efficiency.
* **New Package Sizes for MVE** – Megaport Virtual Edge (MVE) instances are now available in two new sizes:
* 16 core (vCPU)
* 32 core (vCPU)
**Deprecated the 12 core (vCPU) MVE size**:
* The 12 core option is no longer available for new MVE deployments, including for existing customers.
* Existing customers with deployed 12 core MVEs will continue to be supported.
* MVEs previously mapped to 12 core instances, such as the ones provisioned by Cisco vManage, are now assigned to the 16 core size.
For detailed sizing information per vendor and location, see the [MVE section](https://portal.megaport.com/mve) of the Megaport Portal.
* **Megaport Marketplace Improvements** -- These enhancements have been made to the Megaport Marketplace:
* Various Megaport Marketplace Profile interface changes to improve usability. Including changing Services to Interconnect Locations, adding location information to each interconnect location, and displaying diversity zone details when creating a connection from the Megaport Marketplace.
* Megaport Marketplace display name standardization changes including now showing the Account Name (Company Trading Name).
* Added an Interconnect Locations tab to the Megaport Marketplace Profile, which allows an organization to choose to display the locations where they will accept interconnect requests and where (regions) their services can be consumed.
* Megaport Marketplace Provider and Customer Type categories have been updated.
* **Megaport Marketplace / Ecosystem Available on the Megaport Website** -- The Megaport Marketplace is now available and searchable on our public website. A new Ecosystem Overview page has been released, with a curated, navigable view into our Marketplace.
You can find the new page here: [https://www.megaport.com/ecosystem/](https://www.megaport.com/ecosystem/).
This allows you to view a list of all the service providers on the Megaport network, see which Exchanges are available, and so on. As part of this new site, the Marketplace Provider Type categories have also changed to better align with the types of providers available.
* **Single Use Key Status in Service Key Management Screen** -- An indicator has been added to the Type column in the Service Key management screen to show whether a Single Use key has been used. Under any Single Use service key, the text (Available) or (Used) is displayed to indicate the service key status.
* **Partner and Wholesale Discounts in the Quoting Tool** -- The Quoting Tool has been updated to show the discount breakdown in the quote summary for any discounts that apply (Partner and Wholesale discounts).
* **Terraform v1.3.6** -- Version 1.3.6 of the Terraform provider has been released. The key updates in this release include security, MVE/VXC, and Partner Configurations/VXC Schema:
* Upgraded crypto package to v0.36.0 (#226)
* Bumped x/net dependency to v0.38.0 (#230)
* Added computed VLAN field for MVE VNICs, allowing greater flexibility (#224)
* Required VNIC index for MVE end configs to properly match API behavior (#229)
* Fixed inconsistent Palo Alto name format in MVE image data source to work properly with MVE ordering and API validation (#227)
* Changed validation issue for AWS partner configuration - `type` field no longer required for `AWSHC` connect type, only VIFs (#223)
* Refactored partner configuration functionality for better readability/maintainability (#225)
For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.6](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.6).
* **Terraform v1.3.5** -- Version 1.3.5 of the Terraform provider has been released. This version includes support for higher MCR speeds of 25 Gbps, 50 Gbps, and 100 Gbps.\
For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.5](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.5).
* **Issues fixed**:
* Monitoring and usage statistics can now be viewed in the Portal for higher speed MCRs (25 Gbps and above).
* An incorrect number of records were being exported in the Service Inventory report.
* Various other general bug fixes and improvements have been made to improve our systems.
* **Terraform v1.3.4** -- Version 1.3.4 of the Terraform provider has been released. The key updates in this release include:
* New `megaport_ix` resource -- This allows for the management of Megaport Internet Exchange (IX) connections via Terraform, supporting create, read, update, and delete operations.
* Improved Aviatrix MVE documentation -- Enhanced documentation and examples are now available for Aviatrix Multi-Cloud Virtual Exchange (MVE), with details on `cloud-init`.
* Clarification on `requested_product_uid` for CSP VXCs -- Updated schema documentation for `requested_product_uid` in A-End and B-End configurations clarifies that the actual product UID for cloud connections might differ due to Megaport’s automatic port assignment.
* Improved `product UID` mismatch warning -- The warning message for mismatched product UIDs has been updated for clarity, emphasizing that this is often expected behavior.
For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.4](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.4).
* **AUD Added to NZ Billing Market** -- AUD has been added to the New Zealand billing market and NZD has been added to the Australian billing market as available currencies.
This is currently available only to customers setting up their billing market for the first time. If you already have billing markets enabled and want to use these currencies, please contact your Account Manager or Customer Success Manager (CSM) to discuss options.
* **Sort Activity Logs by Date/Time** -- The recently released User Activity and Company Activity pages in the Portal now allow you to sort activity logs by date/time.
* **Invoice Endpoint Improvements** -- The invoicing endpoints have been updated to change the Invoice Charge From/To date fields to reflect the time period to which the ETF applies - the ETF duration.
* **New IX Locations** -- MegaIX is now available in Dublin, Osaka and Montreal, and available for ordering in the Megaport Portal. Megaport's MegaIX is your high-speed express lane to the most in-demand global networks.
* **Cross Connect Ordering for Existing Services** -- These improvements have been made to the Cross Connect ordering process and functionality:
* CSV export from the Quoting Tool now includes Cross Connect quotes.
* The Portal Services page view has been updated to show existing Ports that were ordered with a Cross Connect (through the Portal, not legacy Cross Connects previously ordered manually), so you can clearly see that the Cross Connect was included when the Port was ordered.
* You can now add a Cross Connect to an existing Port that is not yet Live and does not include a Cross Connect. For example, you order a Port as per normal, but after ordering the Port, have a change of mind and want to order the Cross Connect through Megaport.
* **Packet Filtering on MCR Endpoints** -- New endpoints have been created to manage MCR packet filters via the API. New fields have also been added to the VXC create/update endpoint data within the interfaces object to define packet filters for a VXC (`packetFilterIn`/ `packetFilterOut`).
* GET MCR Packet Filter Details -- /v2/product/mcr2//packetFilter/
* GET MCR Packet Filter Summary List -- /v2/product/mcr2//packetFilters
* POST Create MCR Packet Filter -- /v2/product/mcr2//packetFilter
* PUT Update MCR Packet Filter -- /v2/product/mcr2//packetFilter/
* DEL Delete MCR Packet Filter -- /v2/product/mcr2//packetFilter/
* **New Company Activity Logs Page** -- A new Company Activity option has been added to the Megaport Portal settings menu. The Company Activity page allows Company Admins to view the activities of all users in their company. As part of this change, a new option called User Activity was also added to the settings which allows the current user to view a log of their own activities.
* **Packet Filtering on MCR** -- Stateless packet filtering has been added as a new security feature for MCRs. The MCR packet filter feature is used to control the traffic that is permitted or denied on attached interfaces (VXCs). Packet filter lists can be created from the MCR Edit Connection screen (similar to Prefix Filter lists), but cannot be created until the MCR has been provisioned. If an interface has a packet filter applied, any packet not permitted by the filter will be dropped.
Packet filter rules and limits:
* When no packet filter is configured, all traffic is permitted.
* When a packet filter is configured, any traffic not permitted by the filter is denied.
* Up to 20 packet filter lists can be configured on each MCR.
* Each list can contain up to 50 entries.
* A filter can be applied multiple times on the same MCR.
The filters support these matches:
* Source IP Address
* Destination IP Address
* IP Protocol
* Source Port/Port Range (for TCP and UDP protocols)
* Destination Port/Port Range (for TCP and UDP protocols)
Filters will support both IPv4 and IPv6.
For more information, see [Using Packet Filters](/mcr/packet-filters).
* **Maintenance or Outage Updates** -- We have added some CSP notifications to provide better visibility to customers. Emails will not be sent, however, the notifications will be visible in the Service Status page. Please check the notifications from your CSP for more information, as Megaport is not responsible for CSP outages.
* **Markets Invoiced from Megaport Ireland** -- Some Megaport billing entities on your invoice have changed. Any customers affected by this change have been notified by email. These billing markets will be invoiced from Megaport Ireland from now on.
* Belgium
* Denmark
* Poland
* Spain
* Switzerland
* **Portal Finance Role Changes** -- The Finance and Financial Contact roles in the Megaport Portal can now enable and update billing markets. This includes updating PO references.\
For more information, see [Managing User Roles](/portal-admin/user-management/roles) and [Enabling Billing Markets](/finance/enabling-market).
* **Terraform v1.3.3** -- Version 1.3.3 of the Terraform provider has been released. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.3](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.3).
* **IX Service Preferred VLAN Field Moved** -- When ordering an IX service, the Preferred VLAN field has been moved to the Connection Details page. Now the Connection Details page is more closely aligned with the VXC ordering page and all of the IX-specific options are grouped together on the second page.\
For more information, see [Joining an IX](/ix/joining-an-ix).
* **Release Notes Links Added** -- A link has been added to these release notes from the **Tools** menu in the Megaport Portal. A link was also added to the Megaport Documentation tile at the bottom of the Megaport Portal dashboard. This allows you quick access to the latest information about product features and changes.
* **Cross Connect Documentation Link** -- A documentation link has been added to the Review Order screen with information about Cross Connects, when a Cross Connect is included with a Port order.
* **Issues fixed:**
* Logging in with SSO to the staging portal - SSO configurations are now persistent across non-production environments, including staging. Customers who want to use SSO will need to configure it in staging separately.
* In the Megaport Marketplace, the Marketplace customer ‘Website’ URL navigation was incorrect to that respective link. This has been updated to ensure an URL is absolute by adding https\:// prefix where required.
* **Minimum Term Renewal** -- You can now automatically renew the minimum contract term put on a service. Previously, services would roll over to no contract term at the list price at the end of the contract term, unless a manual action was taken to re-term the service.
Now services can be set to **Automatically Renew** at the same duration and discounted price at the end of the contract term, with no manual re-terming action needed. When ordering services on contract with a minimum term of 12, 24 or 36 months, the option to auto renew the term will be enabled by default.
Company Admins can manage the default state for the contract term renewal in the User Menu > Settings > Minimum Term Renewal page. The Company Admins of Partner accounts can manage the default state for all their managed accounts through the Partner Admin > Manage Global Settings > Minimum Term Renewal page.
The Minimum Term Renewal page options are:
* When creating new services on term, the option to Auto Renew the Term will be enabled by default.
* When creating new services on term, the option to Auto Renew the Term will be disabled by default.
Existing services are not affected by the management of the default state of the Minimum Term Renewal options for the contract term renewal.
At the end of the contract term:
* Notifications are sent at least 30 days before term contracts end including services with the Auto Renew Term option enabled.
* If Auto Renew Term has been set to **on** for your services, no further action is required. The service will be automatically renewed for another term of the same length at the same price. The Auto Renew Term setting remains on and the contract term will continue to auto-renew.
* If you would prefer not to lock services onto a minimum term, before the contract expiry date simply go to the Megaport Portal and turn the Auto Renew Term option off - the monthly recurring charge will retain the same market month-to-month rate for Ports or the pay-as-you-go rate for virtual services as when it was ordered.
For more information, see [Managing Minimum Term Renewal](/portal-admin/auto-renew).
* **Portal Settings Reorganized** -- Various user-level and company-level Megaport Portal settings have been consolidated into one settings page, accessible from the user menu. The changes include:
* Creating a consolidated Settings page, accessible from the user menu, with Admin and User sections.
* Moving User Profile and Notification Settings in the user menu into the User section of the new Settings page.
* Moving all Company menu items (Company Profile, Megaport Marketplace Profile, Billing Markets, Manage Users, Security Settings, Company Entitlements) into the Admin section of the new Settings page.
* **Introducing MVE for Peplink FusionHub** -- Peplink FusionHub is now available as a new vendor and product when ordering MVEs.
Peplink FusionHub Virtual is a software-based SpeedFusion appliance that enables secure and scalable VPN connectivity across cloud environments. When deployed on Megaport Virtual Edge (MVE), FusionHub extends the benefits of Peplink’s SpeedFusion technology to enterprises using Megaport’s global private SDN.
* **Quoting Tool Improvements** -- Various updates and improvements have been made to the Quoting Tool, including sorting, filtering, pagination, search functionality, and improved service detail display. You can now also add a Cross Connect to the Quoting Tool if it is available at the selected location.
* **Terraform v1.3.1** -- Version 1.3.1 of the Terraform provider has been released. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.1](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.1).
* **Activity Logs for API Keys Differentiated from User** -- The activity log entries for API keys have been differentiated from the user and customers can view these logs in the Portal User Menu > Settings > Profile page.
* **Add Ability to Untag VLAN for Service Keys** -- You can now configure a single-use service key to have an untagged VLAN.
* **Update Service Key Rate Limits and Flows** -- A customer that has used a service key can now change the rate limit on that VXC without requiring approval if the change is within the approved maximum speed allowed by the service key.
* **Email Notification Subscription Improvements** -- Changes have been made to allow for a more granular selection of email notification subscriptions. You can now subscribe to individual notifications or notification groups in the Portal. Previously you could only subscribe to email notifications at the group level.
* **Cross Connect Workflow Improvements** -- In the Portal, you can now order a data center cross connect when ordering a new Port. This provides an improved customer experience and convenience when ordering a Port, and allows customers to reduce the cross connect provisioning time.\
For more information, see [Ordering a Cross Connect](/connections/cross-connect).
* **Support for Large MCRs** -- Large MCRs can now be ordered through the Portal in Chicago and Ashburn. This release provides initial support for ordering MCRs with capacities over 10 Gbps - that is 25, 50, and 100 Gbps. More metros will progressively be added this quarter.
* **Quoting Tool - Ability to Exclude Services from Quote** -- Customers can now exclude the costs associated with specific top-level services from a quote. When editing a service in a quote, the **Exclude \[service type] from quote** check box can be used to exclude the costs associated with that service from the quote total cost.
* **Added a Link to the Megaport Trust Center in the Portal** -- A link has been added to the Megaport Trust Center ([https://trust.megaport.com](https://trust.megaport.com)) so customers can navigate directly to the trust center from the Portal. The link is in the footer next to the privacy policy link.
* **Company Trading Name Renamed in the Portal** -- All instances of Company Trading Name have been changed to Account Name in the Portal. This change is displayed on the login page and the Company Profile page.
* **Manual Refresh Button for Services List in the Portal** -- A refresh services button has been added to the Services page. This allows users to manually refresh the services list without requiring a full Portal web page refresh.
* **New Market Added** -- Brazil has been added to the list of available markets, with new metros for São Paulo. This also includes localization of the Portal and Megaport documentation. You can view the translated documentation at this URL: [https://docs-translated.megaport.com/pt/](https://docs-translated.megaport.com/pt/).
* **Terraform Updates** -- Several Terraform updates have recently been released with new features, including support for resource tags. Version 1.3.0 of the Megaport Terraform Provider is the latest release. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.0](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.3.0).
* **Error Message Improvements** -- Improvements have been made to the error message that occurs when a new user cannot be added to a company, to better inform the customer about the problem. This error can be displayed in various scenarios, such as when the email address is already in use by another account.
* **Removed the PUT /v2/product/cxc/ Endpoint** -- The PUT /v2/product/cxc endpoint has been deprecated as all active CXC services have been migrated to VXCs. Users should access the PUT /v2/product/vxc/ endpoint instead.
* **Issues fixed:**
* The AWS UI toggle between HC and VIF could get into a locked state when clicking after clicking the Back button during new connection setup.
* Previously you were unable to use the space character when editing the Megaport Marketplace service display name or description.
* Issue where customers couldn’t change the rate limit on their month-to-month services.
* An error was being returned by the Portal when a supplied ASN was valid.
* Updated the Terminate Services window to make the actions more clear when a service was unable to be canceled.
* **Oracle Virtual Circuit ID Now Returned** -- Improvements have been made to the public APIs relating to Oracle VXCs. The `virtualCircuitId` field (the VLAN ID on the Oracle side of the VXC) is now returned in the response for these APIs:
* GET v2/product/
* GET v2/products
* POST v3/networkdesign/validate
* POST v3/networkdesign/buy
* **Debug Information Icon Moved to Footer** -- To make more space available in the Portal menu area, the Debug icon has been moved to the status bar at the bottom of the screen.
* **Megaport Internet in Germany** -- Megaport Internet connections can now be ordered from Ports and MCRs in Germany. Previously, you could only order Megaport Internet from an MVE in Germany.
* **Activity Log Product/Service/M2M User Detail Improvements** -- These details have been added to the activity log:
* If the log is being created by an API key (M2M) user.
* The client ID of the API key if the log is being created by an API key (M2M) user.
* The type of the entity/service/product for which the activity log is being created.
* The UID of the entity/service/product for which the activity log is being created.
* **Terraform v1.2.6** -- Version 1.2.6 of the Terraform provider has been released. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.2.6](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.2.6).
* **Issues fixed:**
* Users are now correctly returned to the login page after logging out if they applied a filter, edited a service, then returned to the Services page to log out. Previously the user was logged out but remained on the Services page with no services listed.
* You can now select a country from the drop-down list in the Megaport Marketplace when searching for a provider.
# Megaport Release Notes
Source: https://docs.megaport.com/whatsnew/index
This help topic describes new Megaport features, and the new or updated topics in the Megaport Documentation Portal.
This topic describes changes and enhancements that have been made to the Megaport Portal.
Information about Megaport API changes are available in the API Developer Portal. For details, see
[Megaport API Release Notes](https://dev.megaport.com/#release-notes).
Information about Megaport Terraform Provider changes are available in the Megaport Terraform Provider GitHub repository. For details, see
[Megaport Terraform Provider Release Notes](https://github.com/megaport/terraform-provider-megaport/releases).
* **IP Address Block Ordering in the Portal** -- You can now order a public IP Address block as a standalone service. Select a metro and block size, then link the block to one or more Megaport Internet connections in the same metro, during ordering or at any time afterwards. IP Address blocks are displayed on the Services page, the Dashboard, and the Network Diagram view, and each block has its own details page. When you terminate a block, any linked Megaport Internet connections are automatically unlinked. You can also edit a Megaport Internet connection to link it to an IP Address block. For more information, see [IP Address Overview](/ip-address).
* **BMP Export Count Added to MCR Service Overview** -- The MCR Overview page now features a BMP Export metrics card displaying the current count of configured BMP export targets with direct navigation to your configuration settings. The Flow Export card label has also been updated to Flow Export for improved clarity.
* **More BGP Connections for MCRs and NAT Gateways** -- You can now configure up to 50 BGP connections on each MCR and NAT Gateway. The limit applies across all VXCs and interfaces on the service. Previously, you could configure up to five BGP connections per interface. For more information, see [Megaport Limits and Quotas](/limits-quotas).
* **Assigning Services to Projects When Ordering** -- The order pages for Ports, MCRs, MVEs, NAT Gateways, and IP Address blocks now include a **Project** field, so you can add a service to a project as you order it. To create a project without leaving the order page, select **New Project** in the field. The selected project appears in the Order Summary side panel and automatically applies to both Ports when ordering a diverse Port pair.
* **Old Services View Retired** -- The redesigned Services page is now the only view of your services. The option to switch back to the old view has been removed.
* **Greece Billing Market** -- Greece is now available as a billing market, with EUR (default) or USD as the supported currencies. Customers can now pre-order Ports in Greece.
* **India Billing Market Update** -- If you order a service located in an Indian state or territory where your India billing market has no branch configured, a warning at the Review Order stage names the affected state or territory and links to your billing market settings, allowing you to enter the GSTIN for that branch. The warning does not stop the order. For more information, see [Enabling Billing Markets](/finance/enabling-market).
* **Megaport Internet now Available in India** -- Customers in India can now order Megaport Internet from all supported Megaport services. As in other countries, the A-End and B-End must be in the same country. For more information, see [Megaport Internet Overview](/megaport-internet).
* **Maximum Packet Size for IPFIX Flow Export** — When you configure a flow export target on an MCR or NAT Gateway, you can now specify a maximum packet size, from 512 to 9074 bytes, for the flow export (IPFIX) stream. This limit is independent of the service MTU, which is useful when a flow collector cannot accept large IPFIX packets from a service that uses jumbo frames. If you leave the field blank, flow export uses the service MTU. For more information, see [Configuring flow export](/mcr/configuring-mcr#configuring-flow-export).
* **Improved Port Ordering Location Search** -- When you search for a data center while ordering a Port, the search term now also filters the list of providers. If your search matches only one metro, that metro is selected.
* **Account Identifier on the Company Profile Page** -- The Company Profile page now displays your company's Account Identifier, the value that uniquely identifies your company account. You can copy the value from the page. For more information, see [Updating a Company Profile](/setting-up/company-profile).
* **Signed Webhook Test Pings** -- A test ping sent with **Send Ping** is now signed in the same way as other webhook deliveries, so an endpoint that verifies signatures accepts it. For more information, see [Using Webhooks in the Megaport Portal](/portal-admin/using-webhooks).
* **User Profile and Notification Settings Consolidation** -- Notification Preferences are now available directly on the User Profile page, allowing you to manage your profile and notification settings in one place. Email Preferences also appear directly on the page instead of opening in a separate popup. Existing profile and security actions, including changing your email address or password and managing MFA, are unchanged.
* **Auto Renewal Setting Moved to Billing** -- The default Auto Renewal Setting option has been moved to the Billing menu in the sidebar.
* **Auto Renewal Setting on the Term Management Page** -- Company Admins can now set the Auto Renewal Setting directly from the Term Management page. This setting controls the default contract term renewal option for new services. For more information, see [Managing Contract Terms in Bulk](/finance/term-management).
* **Megaport CLI** -- The Megaport CLI version Beta 3 has now been released and includes MCR Looking Glass support.
* **Megaport MCP Server** -- The Megaport MCP Server can now modify services, their resource tags, and service add-ons.
* **Terraform v1.20.0** -- Version v1.20.0 of the Terraform provider has been released. For more information on this and all recent Terraform releases, see [https://github.com/megaport/terraform-provider-megaport/releases](https://github.com/megaport/terraform-provider-megaport/releases).
* **MVE Name Field is now Mandatory** -- When ordering a Megaport Virtual Edge (MVE) in the new Portal ordering screens, entering a name for your MVE is now required before submitting an order.
* **Updated Icons and Loading Indicator** -- Icons across the Portal have been updated, and a new animated Megaport logo replaces the previous loading spinner.
* **Megaport Enabled Locations Map Improvements** -- These updates have been made to the [Enabled Locations page](https://www.megaport.com/megaport-enabled-locations/):
* **Coming Soon Locations** -- Locations that are coming soon are now marked as **Coming Soon** in the locations list and the location details.
* **Coming Soon Locations** -- Locations that are coming soon now display the red Installed Location pin icon instead of the black Extended Location icon. The location details pop-up includes the banner message: "This location will go live soon. You can pre-order your services now.".
* **Location Type Tooltips** -- Pointing to a pin on the map now shows whether the location is an installed, extended, or coming soon location. This makes it easier to quickly identify location types.
* **Enabled Locations Usability Improvements** -- Discovering and exploring data centre locations is now faster and more intuitive. Search provides more accurate results with full support for partial matching, while smoother navigation makes it easier to select, zoom out of, and explore clustered locations. Location details now clearly show the available Port speeds, and mobile responsiveness has also been improved.
- **Quoting Tool Enhancements** -- These improvements have been made to the Quoting Tool:
* **Contract Details for Imported Services** -- When you edit an imported service, the edit screen now shows the service's contract length and contract end date.
* **Subtotals for Each Term** -- When a quote is priced across more than one term, the Advanced View and the downloaded PDF now show a subtotal for each term, in each currency that every service in the quote can be priced in. Previously, only a single subtotal was shown based on the active term selection, which made it difficult to compare monthly costs across term lengths without generating separate quotes.
* **All Currencies Selected by Default** -- When you open **Analyze & Export** for the first time, all available currencies are now selected.
* **IP Address Blocks** -- You can now quote IP Address blocks by metro, and import your existing Live and Configured IP Address blocks into a quote. Imported IP Address lines automatically carry over their held monthly pricing, display their subnet size across the quote and summary panels, and remain billed monthly without altering multi-term discount calculations.
* **Automatic Location Selection and Metro-Based Quoting** -- When you quote an MCR, MVE, or NAT Gateway, you can now choose **Auto** location mode, select a metro, and let Megaport choose the facility and diversity zone within it. **Manual** mode keeps the existing behavior of selecting a specific data center. In **Auto** mode, the available speeds, sizes, and rate limits reflect every orderable facility in the location rather than a single site, and the location is tagged Auto-selected.
* **New Login Experience for the Megaport Portal** -- The Megaport Portal now uses a centralized, hosted login page. When you log in, you will be directed to the new login page at auth.megaport.com instead of the previous Portal login page. Logging in is a two-step process; enter your email, then authenticate using a password and MFA, Google sign-in, or your company's SSO identity provider. The login page also includes a language selector and refreshed branding.
Logging out in one browser tab now ends your session in all other open tabs of the same application.
For more information, see [Logging in to the Megaport Portal](/setting-up/logging-in).
* **New Create and Edit Pages for Ports, MCRs, MVEs, and NAT Gateways** -- Ports, MCRs, MVEs, and NAT Gateways now use redesigned Create and Edit pages. For MCRs, MVEs, and NAT Gateways, the Create page defaults to metro-based ordering, allowing you to select a metro instead of a specific data center. The Edit page displays the metro unless you selected a specific data center when creating the service, in which case it displays the data center.
* **Projects in the Portal** -- Projects are now available in the Portal, allowing you to organize related services into groups. You can create, edit, and delete projects, and add or remove services from them.
* Projects are for organizational purposes only. They do not affect billing, configuration, policies, or provisioning.
* Connection services cannot be added directly to a project. They are automatically shown within the project of their access service(s).
* **Locking Services That Are Not Yet Live** -- You can now lock services before they are live. Previously, only live services could be locked. For more information, see [Locking Megaport Services](/portal-admin/locking).
* **Service Telemetry Enhancements** -- The Service Telemetry page includes these enhancements:
* **Extended History** -- View up to 12 months of traffic history, alongside the existing 5-minute resolution data. This gives you a complete picture of your bandwidth utilization for annual connection reviews and capacity planning.
* **Data Aggregation** -- Choose daily or monthly aggregation, with peak, 95th percentile, average, and minimum metrics. View data at resolutions of 5 minutes, 1 day, or 1 month.
* **CSV Export** -- Export monthly utilization data to a CSV file, including inbound and outbound bandwidth with all aggregate metrics, for offline reporting and capacity analysis.
* **Expanded Graph View** -- An expand icon has been added to the top-right corner of every telemetry graph card, which opens the graph in a larger view for better readability. The graph can also be exported as a CSV file from the expanded view.
* **Multi-Term Search** -- Search for multiple service IDs at once by separating them with commas, spaces, or semicolons. Previously, you could search for only one service ID at a time.
* **All Graphs on One Page** -- View all graphs for a service on a single page. The Metrics drop-down has been removed.
For more information, see [Monitoring Services using the Service Telemetry Page](/monitoring/service-telemetry).
* **BMP Export for MCRs and NAT Gateways** -- A new BMP Export tab, alongside Flow Export, allows you to stream BGP session and routing state from an MCR or NAT Gateway to your own BGP Monitoring Protocol (BMP) collector. You can configure up to three collector targets, with support for IPv4 and IPv6 endpoints, optional RIB export, and configurable export intervals. BMP Export provides live BGP routing state, session events, and statistics to your telemetry collectors over a persistent TCP connection.
* **IPsec Add-on in MCR Details** -- You can now configure and manage IPsec tunnels for an MCR directly from the redesigned MCR Details screen in the Portal, alongside the existing Flow Export and new BMP Export tabs.
* **Webhook Signing Secrets** -- You can now generate, rotate, and manage a signing secret for each webhook, allowing you to verify that deliveries genuinely come from Megaport. The signing secret is displayed only once when generated, so store it securely before closing the dialog.
* **RTBH for Megaport Internet** -- Remote Triggered Black Hole (RTBH) support is now available for Megaport Internet. If you run BGP, you can instantly drop incoming traffic targeted at a specific IP address under attack.\
For more information, see [Remote Triggered Black Hole](/megaport-internet/routing#remote-triggered-black-hole).
* **Dashboard Improvements** -- These improvements have been made to the Portal dashboard:
* **Redesigned Product Tiles** -- Each product type now displays a compact donut indicator showing the proportion of services that are up or down.
* **Smarter Tile Display** -- Product tiles are shown only for product types with at least one active service, reducing clutter. The **All Services** tile is always displayed first. If you have no services, the dashboard displays a message instead.
* **Collapsible Toolbar** -- You can minimize the bottom bar to provide more space for the map. When minimized, a summary showing the total number of services remains visible. Your preference is remembered between sessions.
* **More Map Space on Smaller Screens** -- The map now makes better use of the available screen height, particularly on smaller displays. The service status bar also remains visible when viewing the map or globe in full-screen mode.
* **Updated Styling** -- Product icons have been updated to align with the latest brand style, with support for both light and dark themes.
* **Performance Improvements** -- Dashboard rendering performance has been improved for accounts with a large number of services.
* **Other Changes** -- The Large Display button and the link to the external Service Status page have been removed from the dashboard.
For more information, see [Megaport Portal Dashboard](/dashboard).
* **Awaiting-LOA Notice on the Service Overview Page** -- When a newly provisioned Port is not yet live, a notification banner appears at the top of the Service Overview page. The banner indicates that the Port is awaiting activation and provides a **Download LOA** button for direct access to the Letter of Authorization. The banner disappears after the Port is live, but the LOA remains available from the page header. For more information, see [Megaport Letter of Authorization](/portal-admin/loa).
* **New Roles Available for API Keys** -- When creating an API key, you can now assign any of the six public roles, rather than only Company Admin or Read Only. This allows you to limit each API key to the permissions required for its intended use. Only Company Admins can create API keys. For more information, see [Creating an API Key](/api/api-key).
* **Move New User Button** -- The New User button on the Manage Users page has moved to the top of the page, making it quicker to add new users to your company. For more information, see [Adding and Modifying Users](/portal-admin/user-management).
* **France Billing Market E-Invoicing Requirements** -- From 1 September 2026, customers enabling the France billing market with a billing address in France must provide a SIRET number (a 14-digit French business location identifier) and a VAT ID, which is required for French domestic transactions.
* **Portal Maintenance and Outage Banner Improvements** -- The maintenance and outage banner now appears on both the Home and Services pages, providing greater visibility into scheduled maintenance, running maintenance, and active outages. You can filter events by status or custom date range, and select **View Details** to see the affected services.
* **New Documentation Portal** -- The Megaport documentation site has been rebuilt with a refreshed design, improved search, and simpler navigation to help you find information about configuring, managing, and troubleshooting Megaport services. The new site also includes an AI Assistant, allowing you to ask questions in natural language and get answers based on the documentation. Partner documentation is now included in the main documentation site, so partner-managed users no longer need to use a separate site.
* **New MVE Images Available** -- These MVE images are now available in the Portal:
* **Aviatrix** -- Pre-release image (g5-202606302056).
* **Check Point** -- Images vR81.20-JHF-146, vR82-JHF-107, and vR82.10-JHF-24.
* **Activity Log Naming Update** -- Activity log entries for term change events in VXC and IX flows now use clearer, updated naming, making these changes easier to identify and understand in the activity log.
* **Terraform v1.14.0** -- Version 1.14.0 of the Terraform provider has been released. This release includes a fix that stops a CSP partner-config change from destroying a live VXC. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.14.0](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.14.0).
* **Terraform v1.13.3** -- Version 1.13.3 of the Terraform provider has been released. This release includes a fix for prefix list handling. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.13.3](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.13.3).
* **Terraform v1.13.2** -- Version 1.13.2 of the Terraform provider has been released. This release includes support for overriding the API base and token URLs using environment variables. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.13.2](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.13.2).
* **Terraform v1.13.1** -- Version 1.13.1 of the Terraform provider has been released. This release includes a fix so that IX provisioning wait honors `wait_time`. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.13.1](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.13.1).
- **Quoting Tool Enhancements** -- These improvements have been made to the Quoting Tool:
* **Latitude.sh Products in the Quoting Tool** -- You can now quote Latitude.sh products directly.
* **Redesigned Add Services to Quote** -- Existing services are now grouped under Network to align with the Portal.
* **Contract Term End Dates for Imported Services** -- Now displayed in the Quoting Tool.
* **What's New in the Megaport Portal** -- We've refreshed navigation in the Megaport Portal. This is a navigation update, not a redesign of the Portal itself. Everything you could do before is still available, it’s just easier to find and access.
* **A Collapsible Navigation Side Menu** -- The left navigation can be collapsed into a compact, icon-only view, giving you more space to work. Expand it again at any time to restore the full menu with labels. Your preference is remembered as you navigate the Portal. No matter which view you're using, a breadcrumb trail at the top of every page always shows you exactly where you are and lets you jump back a level at any time, so you're never more than a click away from where you started.
* **Simpler, More Direct Access to Your Company and User Settings** -- Company-level settings including Company Profile, Manage Users, Marketplace Profile, and Security Settings, are now grouped together under the new Company Settings menu in the left side bar. User Profile and Notifications remain under the user menu in the top right.
* **New Additions Under Billing** -- The Billing menu now includes three new tools; Term Management, ETF Management, and the link to the Quoting Tool. Term Management lets you review and manage minimum term commitments across your services. ETF Management lets you review outstanding Early Termination Fees (ETFs) and waive them by matching them with an eligible service replacement.
* **Monitoring & Diagnostics** -- One home for all your tools. We’ve replaced the previous Tools menu with a new Monitoring & Diagnostics menu, which now includes Activity Logs (filtered to show relevant activity based on your role), Maintenance & Outages, IX Telemetry and Service Telemetry, and Looking Glass tools (MegaIX and MCR).
* **A New Home for Integrations** -- We've introduced a dedicated Integrations menu that includes API Key Generator for managing programmatic access to Megaport services, Webhooks, and Company Entitlements to view and manage entitlements available for your company.
For more information, see [Megaport Portal Design Changes](/portal-design-changes).
* **Shared Login Across Megaport Systems** -- The Quoting Tool and Latitude.sh now share the same user session. If you log in to one system, you are automatically logged in to the other system. The Megaport Portal is also planned to be migrated over to share the same user session in the future.
You need an existing Latitude.sh account before you can share a session across Megaport systems.
* **Network Map in the Portal** -- The Services page now includes a Diagram view that lets you visualize your network topology in one interactive view, alongside the existing List view. The Diagram view displays your services, including Ports, MCRs, MVEs, and NAT Gateways, and their connections, grouped by metro and data center. You can pan, zoom, drag nodes, trace connections, view VXC utilization, and identify diversity zones using color-coded indicators and a legend.
You can export the diagram as a PNG or PDF, open it in full-screen mode with animated traffic flow, or focus on a single service using the View Connections option. A notice is displayed when your network contains a large number of services.
* **Maintenance and Outage Banner** -- A new dismissible notification banner now appears in the Portal for ongoing and scheduled maintenance, and outage events.
The banner includes a **View All** link that takes you to the Service Status page, opened to the relevant Maintenance or Outages tab. It also includes a **View Impacted Services** button, letting you quickly navigate to services affected by active or upcoming events, with filters for viewing services with active outages, and active or scheduled maintenance.
For more information, see [Understanding the Services Page](/portal-admin/services-page).
* **Service Diagnostics Traffic and Error Graphs** -- The Service Diagnostics tool now displays telemetry graphs that are collapsible and collapsed by default. The Traffic section includes a graph for Ports, MCRs, MVEs, VXCs, and IXs. A new Errors section, available for Ports, appears below Optical Levels and shows In errors/sec and Out errors/sec in a dedicated graph.
* **Webhook Enhancements** -- These improvements have been made to webhooks:
* **Custom Header Name/Value Pairs** -- You can now add custom header names and values to a webhook when creating or editing a webhook, for use in authentication or routing. Up to 5 headers per webhook are supported, values are masked but editable, and are included in the request payload.
* **Webhook Management Improvements** -- The Edit Webhook page now displays created and updated metadata, including the date and the user who made the change. The webhooks list now combines the webhook name and destination URL into a single Destination column, and the Edit, Test, and Delete actions have moved into a menu.
* **Webhook Partner Context and Event Routing** -- Partner accounts can now control webhook event routing to separate their own account activity from events occurring across their managed accounts. When creating a new webhook, partners can select between *Your account* (default) or *Managed accounts* as the event origin. This is set at creation and clearly displayed in the webhooks list via a new Event origin column. This allows partners to receive events from all managed accounts with partner account context included in the payload, while maintaining a distinct stream for their own service notifications.
For more information, see [Using Webhooks in the Megaport Portal](/portal-admin/using-webhooks).
* **Enabled Locations Map Improvements** -- The revamped [Enabled Locations page](https://www.megaport.com/megaport-enabled-locations/) is now live, with improved filtering and interaction behavior. The update also includes these enhancements:
* Cloud Service Provider (CSP) on-ramps are now listed separately from other locations, and you can filter by provider.
* The **Recenter on matches** control, which refits the map to show all filter-matched locations, is now also available in the default map view.
* Location clustering has been adjusted so at least one cluster is always displayed per state.
* Real-time round-trip (RTT) latency is now displayed between data centers. The side-panel tile shows the top 10 lowest-latency data centers inline, with a full expanded panel available for complete latency details. Both views include a *Compare to another location* search to help you evaluate connectivity options.
* Megaport pin icons are now aligned with the Portal design.
* **Megaport CLI (Beta)** -- The Megaport CLI is now available in the Portal. The CLI provides technical users with a faster, scriptable way to provision, update, and manage Megaport services from a command-line interface, without navigating through the Portal. The CLI is currently in Beta and accessible from the Portal footer.
For more information, see [Megaport CLI Overview](/cli).
* **Billing Markets Enhancements** -- The Billing Markets page has been updated with a cleaner design and new usability features to match the Invoices and Bulk Term pages. The Billing Markets page now uses a single, full-width table and includes these improvements:
* **Consistent Table Styling** -- Standardized the table design to match the clean, unified layout used across the rest of the Megaport Portal, improving visual consistency and readability.
* **Column Sorting** -- You can now sort the table by Country and Status columns.
* **Search and Filter** -- You can now search for a specific country or filter by status using the **All**, **Enabled**, and **Disabled** options. The table includes Currency, Billing Contact, Billing Email, and PO Number columns for enabled markets. The **Clear Filters** option resets your filters.
* **Inline Editing** -- You can edit billing details inline. Select the **Edit billing details** icon on a row to update the Billing Contact, Billing Email, and PO Number directly in the table.
* **ETF Management** -- A new Early Termination Fee (ETF) management feature is now available in the Billing section of the Portal. This tool allows you to self-manage and waive open ETFs by selecting an eligible replacement service.
* **Additional Service Metrics now Available** -- New telemetry metrics are now available in the Portal for Internet Exchange (IX) and Port services, giving you deeper visibility into service performance and usage.
IX metrics:
* **BGP Route Counts** -- View the number of imported and filtered routes received from IX peers across all route server connections (IPv4 and IPv6).
* **Broadcast/multicast and Unknown Unicast Counters** -- Monitor byte and packet counts for broadcast, multicast, and unknown unicast traffic on your IX services to help identify potential peering configuration issues.
Port metrics:
* **Subscribed Bandwidth** -- See the total provisioned Mbps across all VXC and IX services on a Port, useful for calculating oversubscription rates.
* **Attached Service Count** -- View the total number of VXC and IX services provisioned on a Port.
For more information, see [Monitoring Services using the Service Telemetry Page](/monitoring/service-telemetry).
* **Graphing Improvements for LAGs** -- There is now clearer telemetry for customers on 400 Gbps Ports and LAGs. Optical light level graphs now display across all interfaces instead of just one, giving a complete picture in the Portal Service Telemetry dashboard.
For more information, see [Monitoring Services using the Service Telemetry Page](/monitoring/service-telemetry).
* **IX Flows Visualization** -- The IX Flows page now uses the Sankey diagram as its default and only visualization. The previous Plotly-based line chart and chart toggle have been removed. The Sankey diagram provides a clearer view of IX peer traffic flows, while existing features such as direction filtering (In, Out, and All) and the peer table remain available.
* **Validation Rules for Megaport Marketplace Forms** -- Megaport Marketplace forms now support configurable validation rules on form fields, giving providers greater control over the data collected during customer onboarding and connection requests. A new **Number** field type is available in the form builder, rendering as a numeric input for customers. Configure optional minimum and maximum value bounds with custom error messages. Validated fields are clearly indicated in the builder's field list for easy reference.
* **Improved Email Notifications** -- We've improved email notifications for service events by including more comprehensive details such as company name, service ID, bandwidth, and billing impact, while also adding service names to subject lines for easier identification. The refreshed email structure features dynamic headers and footers for better readability.
Enhanced monitoring and alerting have also been implemented to improve the reliability of notification delivery for all customers. Some examples include notifications for VXC speed change requests and when a billing contact has declined to validate their email.
* **Improved Dark Mode Readability for Connection Locations** -- On the Create Connection screen, location names for IX, Megaport Internet, and Megaport Marketplace destinations are now clearly legible in dark mode.
* **Quoting Tool Enhancements** -- We’ve now completed a series of Quoting Tool improvements over the past few months. Here are the most recent enhancements:
* **Quote Export Improvements** -- The Quoting Tool now allows you to export quotes in CSV and PDF format, reflecting the selected terms, currencies, and partner/retail discounts, including diversity zone information. The updated PDF export includes new optional sections for an introduction about Megaport, a free-text Tax Registration Number field, and a free-text Company Address field.
* **Advanced Pricing View** -- A new Analyze and Export button takes users to an Advanced View page where pricing can be displayed across multiple terms, currencies, and partner/retail discount levels at once. Term selection can also be changed in bulk for all services.
* **Renewals** -- A new Import button allows users to include a customer's existing services in a quote. Users can select which imported services to include/exclude, increase term or speed on imported services, and add new connections alongside imported connections. This streamlines bulk renewal and re-terming workflows.
* **Terraform v1.13.0** -- Version 1.13.0 of the Terraform provider has been released. This release includes managed account support; partners can now provision on behalf of a managed account using their own credentials. This release also includes improvements to Cisco C8000v documentation. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.13.0](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.13.0).
* **Terraform v1.12.0** -- Version 1.12.0 of the Terraform provider has been released. This release includes a change to expose as\_override on VXC BGP connections. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.12.0](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.12.0).
* **Terraform v1.11.1** -- Version 1.11.1 of the Terraform provider has been released. This release includes a fix for a state preservation issue when the API returns an empty diversity\_zone. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.11.1](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.11.1).
* **Terraform v1.11.0** -- Version 1.11.0 of the Terraform provider has been released. This release includes these key improvements:
* IPsec tunnel support for VXCs -- Configure IPsec tunnel options directly on a VXC, with pre\_shared\_key handled as write-only so secrets never land in state.
* New megaport\_nat\_gateway\_sessions data source -- Look up active NAT Gateway sessions (speed, session count) without leaving Terraform.
* NAT Gateway speed/session validation -- Invalid speed/session combinations are now caught at plan time instead of failing on apply.
* Fixed inner VLAN drift warnings -- Update/verify logic now treats -1 and 0 as equivalent for untagged inner VLANs, so you won’t see spurious mismatch warnings when moving VXCs between MVEs.
* Security fix -- Access keys are now masked in provider debug logs.
* Various reliability fixes to VXC plan modification and MCR data source reads.
For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.11.0](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.11.0).
* **Portal Menu Redesign** -- The Portal navigation menu has been updated with a new Billing menu. Invoices, Billing Markets, and Term Management have been moved into this menu, making billing-related features easier to find.
* **Services Page Refresh** -- The Services page in the Megaport Portal has been updated with a new look and feel.
* **Full-width layout** -- The services list now spans the full page width, allowing you to view your services at a glance.
* **Updated product icons** -- Service rows now display gradient-styled product icons consistent with the updated Megaport brand.
* **Improved row density** -- Tighter spacing and refined whitespace make it easier to scan your list of services.
* **Expand/Collapse all** -- This control has been promoted to a visible button in the page header, making it quicker to expand or collapse all service groups.
* **Row styling improvements** -- Updated hover states, rounded corners, and refreshed status and service identifier chips for a cleaner look.
* **In-app guided tour** -- A guided tour orients customers to the new layout on the first visit.
* **Add Services Page** -- A new **Add Services+** button and page replace the individual **Create Port**, **Create MCR**, **Create MVE**, and **Create NAT Gateway** buttons on the Services page. The new page presents services as a card grid grouped into Network Services and Compute, where you can select a service to configure and order.
* **Megaport Storage** -- You can now order Object Storage connections directly from the Megaport Portal. A new **Megaport Object Storage** tile is available in both the New Connection screen and the Add Connection section on your services.
Object Storage connections require storage capacity at Latitude.sh. If you're new to Latitude.sh, provision Object Storage first in the Latitude.sh Portal, then return to the Megaport Portal to create the connection and complete your order.
For more information, see [Megaport Object Storage Overview](/storage/object).
* **Latitude.sh Direct Connectivity and Provider Support** -- The Megaport Portal now supports Latitude.sh as a B-End provider. A new **Latitude.sh** tile has been added to the B-End provider selection screen, displaying available interconnect ports with red/blue diversity indicators and latency information.
You can now create VXC connections directly to Latitude.sh compute infrastructure from the Megaport Portal. This integration introduces a new `connectType` of COMPUTE and includes cost-free connectivity for same-country connections. To create a connection, select Latitude.sh from the provider list and choose the target interconnect port.
* **Invoice Management Improvements** -- A new Invoices page is available under the new Billing menu in the Portal's sidebar navigation. The Invoices page provides a centralized location for managing your billing documents and tracking payment history. In the new page, you can view, filter, and sort your invoices. Each invoice shows its payment status, and you can download individual invoices as PDF or CSV files.
The Billing Markets page has been moved to the new Billing menu, but remains unchanged and continues to provide access to billing market settings and configurations.
* **Bulk Service Term Management** -- A new Term Management page is available under the new Billing menu in the Portal's sidebar navigation. The Term Management page lets you start and update a new contract term for multiple services at once. A guided wizard walks you through selecting eligible services, choosing the new term and auto-renew setting, reviewing the pricing summary and terms and conditions, and submitting the changes, with a per-service result for each selected service.
* Managed Account Support -- Services requiring partner approval automatically generate approval records and return a PENDING\_APPROVAL status.
* Activity Logging -- All successful and failed term changes are recorded in the activity log for auditability.
* **Improved Failed Login Attempt Email Messaging** -- The failed login attempt email notification has been updated to provide clearer guidance when a login attempt is unsuccessful. The email now explicitly states the account lockout threshold and informs users that their Company Administrator can reactivate a locked account. Accounts will be locked after five unsuccessful login attempts.
* **Webhook Updates and Enhancements** -- Various updates and improvements have been made to webhooks.
* **Event Category Filtering** -- Webhook subscribers can now filter their subscriptions by event category, allowing them to subscribe only to the groups of events that are relevant to their workflows.
* **Flap Suppression** -- Service availability and BGP events use debounced delivery. Down events are sent immediately when detected, while up events are sent only after the service has remained stable for a short period. This approach provides rapid failure notifications while reducing noise caused by flapping links.
* **New Webhook Events Available** -- New webhook events covering order management, invoices, payments, Megaport Marketplace approvals, and partner order approvals are now available. These webhooks provide automated notifications regarding order approval and fulfilment in real-time, payment processing state transitions, including payment success and failure events.
For more information, see [Using Webhooks in the Megaport Portal](/portal-admin/using-webhooks).
* **Flow Export for MCR and NAT Gateway** -- You can now export network flow data (IPFIX) from your MCR and NAT Gateway services to external collectors for traffic analysis and monitoring.
A new Flow Exporters tab is available when you edit an MCR or NAT Gateway, allowing you to manage flow export targets and send network traffic data to external collectors. You can configure up to three flow export targets per service, each with a description, an optional local IP address selected from the addresses on the service, the collector IP address (IPv4/IPv6) and port, and the protocol (TCP or UDP). You can add flow export targets after the service is provisioned.
* **DHCP Server Pools on MCR VXCs** -- You can now configure a DHCP server pool on an MCR VXC interface, supporting DHCP services on a per-interface basis.
You can configure pools when creating a new MCR VXC or add them later by editing the VXC. Add a pool by specifying the network in CIDR notation, a start and end IP address, with an optional default gateway, description, and DNS servers. Each interface supports one DHCP pool.
* One pool per interface is supported.
* IPv6 DHCP pools, static DHCP assignments, and live lease visibility are not yet supported.
* DHCP cannot be configured on IPsec tunnel interfaces or where the other end is an IX or transit service.
* **Netskope One SD-WAN Now Available on MVE** -- MVE now supports Netskope One SD-WAN as a new vendor option. Running Netskope One SD-WAN on MVE enables deployment of Netskope's SASE platform directly on Megaport's global private network without requiring physical hardware or data center rack space. You can spin up a unified, secure SASE platform globally in minutes, which provides built-in zero-trust access, next-gen firewall, secure web gateway, and data loss prevention at the edge, while keeping branch-to-branch and branch-to-cloud traffic off the public internet for improved performance and security.
For more information, see [Netskope One SD-WAN with Megaport Virtual Edge](/mve/netskope).
* **Deciso OPNsense Now Available on MVE** -- MVE now supports Deciso OPNsense as a new vendor option. Deciso OPNsense on Megaport’s MVE delivers open-source firewall and routing capabilities directly on Megaport’s global private SDN. By integrating OPNsense with MVE, you can deploy a feature-rich firewall and routing platform without physical hardware or data center rack space.
For more information, see [Deciso OPNsense with Megaport Virtual Edge](/mve/deciso).
* **Megaport Advanced Services** -- A new *Advanced Services* feature is now available in the Portal, allowing you to request assistance from the Megaport Advanced Services team. Advanced Services provides paid professional services engagements for Configuration Assistance and Project Services.
During checkout, you can indicate that you would like the Advanced Services team to implement your solution, and provide details about your requirements. The team will then review the request to scope and price the engagement.\
You can also request Advanced Services assistance from the Help & Support menu in the Portal.
For more information, see [Megaport Advanced Services Overview](/advanced-services).
* **Dark Mode Support for the Dashboard Map** -- The Dashboard map now follows your selected Portal theme. In dark mode, the map renders the oceans, continents, borders, and labels in a dark style so it matches the rest of the Portal. Light mode is unchanged.
* **Improved Billing Contact Email Verification Experience** -- When a Company Admin updates the billing contact email address on a billing market, the new contact receives a verification email. Previously, confirming the email redirected users to the Portal login page, which provided no clear feedback on the verification status. Now, users are redirected to a dedicated Email Verification Success landing page that confirms the email address has been verified and outlines the next steps.
For more information, see [Enabling Billing Markets](/finance/enabling-market).
* **Improved VLAN Tagging Interface for VXC Configuration** -- The VLAN input on the VXC configuration page has been redesigned. The previous **Untag** toggle is replaced with clearer Tagged and Untagged options, with tooltip and inline guidance explaining how tagging affects the connection. When you select **Tagged**, you can assign a VLAN ID automatically or specify your own VLAN ID manually.
* **India Billing Market CAF Enhancements** -- The Customer Acquisition Form (CAF) for the India billing market has been enhanced. The entity type labels for Limited Liability Partnership (LLP) and Public Sector Undertaking (PSU) are now expanded, per-entity-type definitions appear as tooltips, and there is additional guidance for TAN and statutory registration details. For more information, see [Enabling Billing Markets](/finance/enabling-market).
* **In-Portal LOA Upload** -- You can now upload a Letter of Authorization (LOA) for a Cross Connect directly in the Portal. Clicking **Upload LOA** opens a prompt where you can drag and drop or browse for a PDF file, instead of redirecting you to the Support Requests Portal.
* **Download LOA Improvement** -- You can now download uploaded Letter of Authorization (LOA) files directly from the Portal, without having to go to the Support Requests Portal.
* **Improved Support Chat** -- The live chat experience has been improved to streamline support requests for compute, storage, and network issues. When you start a chat session, you can now select an issue type to help route your request to the appropriate Support team for faster, more relevant assistance.
* **Activity Logs on the Service Logs Page** -- The Service Logs page now includes an Activity Logs tab, allowing Company Admins to view both service logs and activity logs for a specific service in one place, without navigating to the Activity Logs page.
* **Terraform v1.10.1** -- Version 1.10.1 of the Terraform provider has been released. This release
marks all sensitive fields (such as MVE vendor keys/license data, VXC auth\_key, BGP shared\_key/password) as `Sensitive` and adds a README notice about the removal of the `cancel_at_end_of_term` attribute. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.10.1](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.10.1).
* **Terraform v1.10.0** -- Version 1.10.0 of the Terraform provider has been released. This release removes the Terminate Later option for Ports and persists the VXC UID to state before the provisioning wait. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.10.0](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.10.0).
* **Quoting Tool Enhancements** -- These improvements have been made to the Quoting Tool:
* You can now add DDoS Protection as an optional add-on when quoting a Megaport Internet connection in the Quoting Tool, at locations where DDoS Protection is available. When added, DDoS Protection appears as a separate line item with its own monthly rate in the quote and is included in the PDF quote export.
* The Download CSV and PDF buttons have moved into a new Advanced View screen. The previous Pricing Comparison button is now named Analyze & Export and opens this screen, where you can download CSV and PDF quotes.
* Megaport Storage is now available as a connection type. When you add a connection to a quote, you can select Megaport Storage as the destination and configure a connection name, rate limit, and contract term.
* Latitude.sh is also now available as a connection type.
* The Quoting Tool now uses the same side menu as the Portal, and the user profile menu includes a theme option.
* You can now import existing services into quotes. These services can be excluded from the quote if needed.
* The Pricing Comparison screen now includes add-on charges (such as IPsec, Cross Connect, and DDoS Protection) as separate line items beneath their parent service. Summary totals have been updated to include add-on monthly rates, ensuring the Pricing Comparison total matches the Quote Summary.
* **New Portal Menu Design** -- We’ve streamlined the Megaport Portal to improve navigation and accessibility! The primary navigation menu has moved from the top header to a new left-hand sidebar. You can now find these core categories quickly on the left side of your screen:
* **Dashboard** -- Your centralized overview of network health and activity.
* **Services** -- Manage your Ports, MCRs, MVEs, NAT Gateways, IXs, and VXCs.
* **Marketplace** -- Discover and connect with our global ecosystem of providers.
* **Tools** -- Access telemetry, looking glass, speed tests, and diagnostic utilities.
* **Service Status** -- Real-time updates on network performance, maintenance, and outages.
- The Session Event Log has been removed as part of the menu redesign. Use the Activity Logs now for all logging activity. For more information, see [Viewing Activity Logs](/portal-admin/activity-logs).
* **Mandatory Multi-Factor Authentication (MFA)** -- Effective from May 11 2026, MFA is now mandatory for all customers accessing the Portal. This security enhancement requires all users to set up MFA on their accounts, providing an additional layer of protection against unauthorized access. Users will be prompted to configure MFA during their next login if they have not already done so.
* SSO users are exempt from MFA - authentication is handled by their IdP.
* API keys are not affected. However, any automation or scripts using username/password authentication will break. Customers must switch to using API keys instead.
For more information about MFA, see [Multi-Factor Authentication](/setting-up/enforcing-mfa).
* **Security: Account Lockout After Failed Login Attempts** -- User accounts are now automatically locked after 10 consecutive failed login attempts, protecting against unauthorized access. Once locked, users will see a clear message directing them to contact their company administrator. Company admins can reactivate locked users from the Admin > Manage Users section, which also resets the failed attempts counter so the user can log in normally again.
* **Megaport Marketplace Forms Added** -- Megaport Marketplace service providers can now collect required information from customers upfront, by creating custom forms and embedding them in the Marketplace ordering workflow. This helps speed up the approval process and reduces manual communication.
When a customer initiates a request to connect to a provider with an associated form, they are prompted to complete the form as part of the ordering process. Customers can provide all required information in a single step, reducing delays and eliminating the need for follow-up requests from the provider.\
For more information, see [Megaport Marketplace Forms](/marketplace/forms).
* **New Webhook Events Available** -- You can now subscribe to service lifecycle events through webhooks. New event types include service availability changes (up/down), BGP availability changes (up/down), service configured, and service terminated. These events allow you to receive real-time notifications about the operational status of your services directly to your systems.
Maintenance and outage events are now available. You can subscribe to scheduled maintenance and unplanned outage lifecycle events.\
Billing events are also now available. You can subscribe to billing-related events such as when a service starts billing, is re-termed or comes off term, and when an invoice is generated.
For more information, see [Using Webhooks in the Megaport Portal](/portal-admin/using-webhooks).
* **Technical Contact Console Access** -- Users with the Technical Contact role can now access the MVE console and restart MVEs. Technical Contacts can now view operational information and perform essential actions on MVEs they are associated with. Previously, these actions were limited to Company Admin and Technical Admin roles.
* **Portugal Billing Market** -- Portugal is now available as a billing market. You can enable the Portugal market in the Portal to order services with EUR (default) or USD as the billing currency. 1, 10, and 100 Gbps Ports are available at the Equinix LS1 location in Lisbon.
* **India Billing Market** -- These updates have been made to the India billing market:
* **Indian Rupees (INR) Billing Currency** -- Customers with the appropriate permissions can enable the India market to order services with Indian Rupees (INR) as the billing currency. When enabling the India market, customers with a non-Indian address can also opt to pay in USD instead of INR.
* **India Billing Market CAF Form** -- The India Billing Market onboarding process now includes a Customer Acquisition Form (CAF) tab. When enabling the India market, you must complete the CAF with additional regulatory information to ensure compliance with local requirements.
* **NAT Gateway Widget Added to Dashboard** -- A NAT Gateway widget has been added to the Dashboard summary bar, providing at-a-glance visibility into your NAT Gateway services. The new widget displays total, Up, and Down counts for your NAT Gateway services, matching the behavior of the existing service widgets.
* **Service Telemetry Updates** -- The Service Telemetry page now displays VXCs alongside Ports, MCRs, and MVEs. Each service card now includes a service type label to help you quickly identify the service type when viewing telemetry data. MVE attributes have also been updated to show vendor, vCPU cores, and RAM.
* **Service Diagnostics Quick Navigation Improvements** -- The Scheduled Maintenance and Unplanned Outage tiles are now clickable. When a service has an active scheduled maintenance or unplanned outage, clicking the relevant tile will take you directly to the Service Status page, filtered to show only the status information for that service. This makes it faster and easier to view full details about any ongoing or upcoming events affecting your services.
* **New DC Location Type for Distribution Agreement Partners** -- Data center locations associated with Distribution Agreement partners (including sites in South Africa, South Korea, the Philippines, and other regions) now appear in the Portal with an **Extended** location status. Instead of the standard ordering workflow, these locations present a *Contact Sales* prompt, directing customers to the sales team for engagement. This enables greater visibility of partner locations on the Dashboard while ensuring the appropriate sales-led process is followed for these sites.
* **Portal Terms Updated** -- The terms and conditions displayed in the Portal cart when ordering add-on services (IPsec, Cross Connect, IP Address) have been simplified and standardized to match how standalone products work.\
Customers now see one of these standard terms paragraphs based on their account type:
* Partners with GRA signed -- Terms referencing the Global Reseller Agreement
* Direct customers / Partners without GRA signed -- Terms referencing the Global Services Agreement and Service Schedules
* Managed Accounts -- A short message directing them to contact their Megaport partner
* **Ping and Traceroute for MCR and NAT Gateway** -- You can now run ping and traceroute diagnostics directly from your MCRs and NAT Gateways, making it easy to troubleshoot connectivity, measure latency, and visualize network paths, without leaving the Portal or needing external tooling.
* **Ping** -- Run an ICMP ping from any MCR or NAT Gateway to a destination IPv4 or IPv6 address. Configurable options include packet count (1–60, default 3) and packet size (1–9,186 bytes, default 56). An optional source IP can be specified for NAT Gateway scenarios.
* **Traceroute** -- Trace the hop-by-hop network path from any MCR or NAT Gateway to any IPv4 or IPv6 destination. Supports an optional source IP for NAT Gateway path testing.
Ping and traceroute are accessible from two locations in the Portal:
* **Service Diagnostics** -- New Ping and Traceroute tabs in the Service Diagnostics, enabling diagnostics directly from your services.
* **MCR / NAT Gateway Looking Glass** -- New Ping and Traceroute tabs alongside the existing route diagnostics.
Key details:
* Supports both IPv4 and IPv6 addresses (public and private).
* Source IP is optional and must be an address configured on the MCR / NAT Gateway. When provided, it must match the destination's address family.
* Results are displayed in real-time with Copy and Export controls for easy sharing.
* If an MCR / NAT Gateway has no active VXCs attached, a descriptive error is returned explaining that at least one active VXC is required.
* All requests run asynchronously -- results are available for polling once the operation completes.
Constraints:
* Destination must be an IP address -- hostname resolution is not supported.
* ICMP only -- UDP/TCP-based traceroute variants are not available.
* One diagnostic operation runs at a time -- subsequent requests queue until the current operation completes.
* Results expire after 10 minutes and are not persisted.
* **Terraform v1.9.1** -- Version 1.9.1 of the Terraform provider has been released. This release includes documentation updates for adding import and example usage to NAT Gateway, bug fixes, and version updates. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.9.1](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.9.1).
* **Terraform v1.9.0** -- Version 1.9.0 of the Terraform provider has been released. This release includes the new megaport\_nat\_gateway resource family (gateway, packet filter, prefix list) with VXC vrouter A-End interfaces extended for NAT Gateway BGP whitelists, and an admin\_password attribute for Cisco MVEs. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.9.0](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.9.0).
* **Terraform v1.8.0** -- Version 1.8.0 of the Terraform provider has been released. This release includes the new megaport\_mves data source, support for modifying MCR ASN in place, VXC ModifyPlan now guarded against unknown end-config objects, and transit/AWS VXC VLAN updates issue fix. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.8.0](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.8.0).
* **Quoting Tool Enhancements** -- These improvements have been made to the Quoting Tool:
* **Quoting Tool Import Existing Services** -- A new **Import Existing Services** button is available in the Quoting Tool. You can import your existing services into a quote, search by name or service UID, and optionally exclude imported services from the quote total. This allows you to quote term renewals, and include existing services in your network design without affecting pricing calculations. All imported services are fully editable with pricing.
* **Multi-Currency Pricing** -- The Pricing Comparison view now supports displaying pricing in multiple currencies within a single quote. Select additional currencies in the comparison dialog to see pricing for each service in those currencies alongside the native currency.
* **Multi-Discount Option Display** -- The Multi-Discount Option Display has been added to show Partner Discounted Pricing alongside Standard Pricing in the Network Design Summary.
* **Bulk Update Terms** -- You can now bulk update terms across all services in a quote. When editing the term for any service in the quote, a new option allows you to apply that term change to all services in the quote. This makes it much faster to see how different term lengths affect pricing across your entire design without having to edit each service individually.
* **Download all Term Prices in CSV** -- You can now download the pricing for all term options for each service in a quote as a CSV file. This allows you to analyze and compare pricing across different term lengths in a spreadsheet format, making it easier to identify the best options for your network design. The CSV includes columns for service name, location, term length, standard price, and partner discounted price (if applicable).
* **Issue fixed:**
* Fixed an issue where the rate limit field briefly appeared as a text input before switching to the expected drop-down menu when creating an AWS Hosted Connection. The drop-down now renders immediately, providing a smoother and more consistent experience.
* When a partner user attempted to save an existing quote for a managed account, the save operation failed with a validation error.
* Emergency planned maintenance notifications were not visible on the Service Status page when viewing from a Partner Managed account context.
* **Megaport NAT Gateway Now Available** -- Megaport NAT Gateway is now available for self-service ordering directly in the Megaport Portal. This gateway can now be easily configured and managed in the Portal, and is designed for customers who need a high-performance, cost-effective alternative to expensive, in-cloud NAT solutions. This provides an easy, one-click way to provide secure network address translation for your workloads, with no offline conversations or lead times required.\
For more information, see [Megaport NAT Gateway Overview](/nat).
* **NAT Gateway in the Quoting Tool** -- You can now add NAT Gateway services when creating quotes in the Quoting Tool. When designing a network quote, click **Add NAT Gateway** to configure a NAT Gateway with options for location, name, session count (250K to 10M sessions), rate limit, and contract term. You can optionally exclude the NAT Gateway from the quote total if you want to include it in the design without affecting pricing.
* **Introducing MVE for F5 BIG-IP Virtual Edition** -- You can now deploy F5 BIG-IP VE directly on MVE, enabling advanced application delivery, traffic management, and security services without the need for physical hardware, shipping delays, or data center rack-space requirements. This enables you to run a full-featured virtual application delivery controller (ADC) at the network edge, improving application performance and reducing latency by keeping traffic closer to users and cloud services.
F5 BIG-IP VE on MVE supports key capabilities including Local Traffic Manager (LTM) for intelligent load balancing, BIG-IP DNS for global traffic distribution, Web Application Firewall (WAF) for application protection, and SSL/TLS offloading to optimize performance. With support for throughput up to 10 Gbps (depending on license tier) and integration with F5 BIG-IQ for centralized management, you can scale and manage application services consistently across data center and edge deployments.
For more information, see [F5 BIG-IP Virtual Edition with Megaport Virtual Edge](/mve/f5).
* **Webhooks in the Megaport Portal** -- The phase 1 release of webhooks for authentication-related events is now available. Webhooks allow you to receive real-time event notifications via HTTP callbacks instead of relying on email alerts or polling. Webhooks deliver machine-consumable events directly to your systems, making it easier to detect credential attacks as they happen, automate incident response, streamline approval workflows, and integrate Megaport into your existing monitoring, ITSM, and security platforms.
Company Admins and Technical Admins can configure and manage webhook endpoints directly in the Megaport Portal. Each company can register up to 10 webhook endpoints, subscribe to specific event types, and secure delivery using IP allowlists. Any failed deliveries are automatically retried to ensure reliable event notification.
For more information, see [Using Webhooks in the Megaport Portal](/portal-admin/using-webhooks).
* **New Traffic Visualization Tools** -- We have introduced two new ways to monitor network traffic:
* **Sankey Flow for IX telemetry** -- Visual diagram showing how traffic flows through your IX, with inbound and outbound traffic by top peers and bandwidth represented proportionally. Select from 24-hour, 12-hour, or 7-day time windows to spot trends.
* **Service Telemetry Graphs for Ports, MCRs, and MVEs** -- Consolidated view of In/Out traffic patterns across all services. You can choose time windows from 1 hour to 3 months and see Avg/Peak/Current metrics for quick capacity checks, and visualize telemetry data previously available only via API.
* **Extended Locations in the Portal Dashboard** -- The Portal Dashboard now displays extended locations. Customers can toggle their settings to view all locations, installed locations only, extended locations, or just locations where they have active services. Extended locations are shown with distinct map pins to differentiate them from enabled locations. Extended locations support viewing, but to order services at these locations, contact your Account Manager for assistance.
* **Megaport Internet Now Available in Hong Kong** -- Customers can now purchase Megaport Internet connections from Ports, MCRs, and MVEs in Hong Kong without restriction. Previously, Megaport Internet in Hong Kong was limited to MCRs with IPsec enabled and MVEs.
* **MCR AS Number Now Editable After Deployment** -- Customers can now modify the AS number on deployed MCRs. Previously, the AS number could only be set during MCR creation. The ability to change the AS number after deployment provides greater flexibility for customers to adapt to network changes and topology adjustments without needing to redeploy the MCR.
This change applies only to MCRs that do not have VXCs attached.
* **MCR and NAT Gateway BGP AS Override** -- You can now enable AS override on MCR and NAT Gateway BGP connections directly from the Megaport Portal. A new option is available in the BGP connection settings for MCR and NAT Gateway VXCs, allowing you to independently control AS override on both the A-End and B-End while ordering and when updating existing connections. The setting applies to eBGP connections only, is off by default, and does not affect existing services or integrations.
* **IKE Identifier Overrides for MCR IPsec Tunnels** -- You can now specify custom Local Identifier and Remote Identifier values when configuring an IPsec tunnel on an MCR. These optional fields allow you to override the default IKE authentication identifiers (which use the source IP by default), giving you greater flexibility when connecting to third-party devices or cloud providers that require specific IKE identity settings.
Supported identifier formats include IPv4 addresses, IPv6 addresses, domain names, and email addresses. The fields are located in the Advanced section of the IPsec tunnel configuration.
* **Service Diagnostics Tool Updates** -- These improvements have been made to the Service Diagnostics tool:
* The Service Diagnostic tool has been updated for NAT Gateway. You can now view the health status, traffic levels, and other key metrics of your NAT Gateway directly in the diagnostics tool, giving you real-time insights into the performance of your NAT Gateway.
* You can now launch the diagnostics tool directly from any service on the Services page. Quickly view service health, live traffic data, and the status of all attached connections. Stay ahead with integrated views of scheduled maintenance and any planned outages affecting your services.
* **Latitude.sh Portal Login** -- Users with a Megaport account can now log in to the Latitude.sh Portal with their Megaport credentials. This integration allows you to seamlessly access Latitude.sh's on-demand bare metal servers, GPUs, storage, and global networking with cloud-like provisioning using your existing Megaport account.
* **India Billing Market Updates** -- Customers with the appropriate permissions can enable the India market to order services with Indian Rupees (INR) as the billing currency. When enabling the India market, customers with an Indian address can also opt to pay in USD instead of INR.\
The India Billing Market Onboarding form has been updated to ensure compliance and accurate tax reporting. When providing an Indian address, customers will now be prompted to provide:
* GSTIN (Goods and Services Tax Identification Number)
* ISP License Holder Name
* CIN (Corporate Identification Number)
* TAN (Tax Deduction and Account Number)
If you have an Indian primary address, and have additional business locations in other Indian states or territories, you can also register additional Indian branch addresses with their corresponding GSTINs.
* **Quoting Tool Updates** -- These improvements have been made to the Quoting Tool Pricing Comparison:
* Partner Pricing in Partner Comparison screen (Partners only) -- Partner users now have a **Display Partner Pricing** check box in the sticky footer of the Pricing Comparison screen. When selected, every service shows an additional line item with the partner discount applied — making it much faster to show partners the different pricing scenarios.
* Edit Terms in Comparison Screen -- You can now edit the term lengths for each service directly in the Pricing Comparison screen. This allows you to see how different term lengths affect pricing without having to exit the comparison view and reconfigure the quote. Simply click on the term length for any service to select a new term, and the pricing will update in real time to reflect the change.
* **Terraform v1.7.0** -- Version 1.7.0 of the Terraform provider has been released. This release includes new resources, data sources, bug fixes, and documentation updates. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.7.0](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.7.0).
* **Terraform v1.6.0** -- Version 1.6.0 of the Terraform provider has been released. This release features MCRs as a data source. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.6.0](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.6.0).
* **Terraform v1.5.2** -- Version 1.5.2 of the Terraform provider has been released. This is a small release with a fix for VXC updates where adding a\_end\_partner\_config or b\_end\_partner\_config to an existing VXC was silently dropped. Terraform reported success but changes never reached the API.\
Note that any customers already affected will have stale state and will need to remove the partner config block, apply, then re-add it to force the update through.
For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.5.2](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.5.2).
* **SSO Infrastructure Upgrade** -- Megaport has migrated to an upgraded Single Sign-On (SSO) infrastructure. For impacted customers with an existing SSO configuration, ensure you follow the full migration process in the guide that was distributed to your company. This process includes updating your identity provider (IdP) settings to match the new Megaport URLs, and testing the SSO connection to confirm it is working correctly.
* **SSO SAML Metadata Upload** -- You can now upload a SAML metadata XML file when configuring an IdP in the Megaport Portal. This is useful when your IdP metadata endpoint is not accessible from the internet. When setting up or updating your SSO configuration, you can upload the SAML metadata XML file instead of providing a metadata URL. This allows the Portal to extract the necessary SSO configuration details directly from the file, ensuring a smoother setup process for customers with restricted network access.\
For more information, see [Setting up Single Sign-On](/setting-up/enforcing-sso) and [Single Sign-On (SSO) Frequently Asked Questions (FAQs)](/troubleshooting/sso-faq).
* **MFA Enforced for New Accounts** -- Multi-Factor Authentication (MFA) is now enforced by default for all new Megaport accounts. When Megaport enforces MFA for your company, the MFA enforcement option in Company Settings is grayed out to prevent changes. For more information, see [Multi-Factor Authentication](/setting-up/enforcing-mfa).
Existing companies and users will continue using their current MFA settings for now.
* **India Billing Market** -- We are excited to announce that we have now gone live with our first four sites in India, and customers can now order services at these locations in Mumbai and Chennai.
* **Introducing MVE for Juniper vSRX Virtual Firewall** -- You can now deploy Juniper’s vSRX next‑generation virtual firewall directly on MVE, eliminating physical hardware, shipping delays, and data centre rack-space requirements. The service allows customers to apply their existing Juniper security policies at the network edge to reduce latency by avoiding traffic hairpinning back to a central hub. Juniper vSRX on MVE supports 2–16 vCPUs and up to 5 vNICs for scalable performance, and includes cloud-init support for day‑0 automation plus optional Mist integration for simplified management.\
For more information, see [Juniper with Megaport Virtual Edge](/mve/juniper).
* **Aruba EC-V V9 on MVE** — Aruba HPE EC-V V9 is now available for all customers in the Megaport Portal. Select Aruba EC-V V9 if your Aruba Orchestrator is version v9.4.5.0\_100128 or later. Aruba EC-V V8 remains available for earlier Orchestrator versions, but after deployment, you must upgrade to version 9 using Aruba Orchestrator. Aruba EC-V V9 offers enhanced performance, features, supports a minimum of 2 vNICs and a maximum of 5 vNICs, and provides improved scalability and flexibility for your SD-WAN deployments.\
For more information, see [Creating an MVE in the Megaport Portal](/mve/aruba/creating-mve-system-tag#creating-mve).
* **Restart MVEs from the Megaport Portal** — You can now gracefully restart your Megaport Virtual Edge (MVE) directly from the Megaport Portal. On the Services page, click the **Restart MVE** icon next to the service to initiate a clean shutdown and startup of the virtual machine while preserving its configuration. This is useful when your MVE vendor requires a restart for configuration changes or troubleshooting. During the restart, the service is temporarily unavailable.\
You can monitor progress in real-time using the Service Diagnostics tool.
This action requires Company Admin or Technical Admin privileges.
* **MCP Server** -- We have launched our very own MCP server at [https://mcp.megaport.com/](https://mcp.megaport.com/), giving AI assistants like Claude / Codex / ChatGPT / Copilot / Gemini direct access to customers’ Megaport network for diagnostics, telemetry, and service discovery. The MCP Server is currently read-only for customers to use with their own LLMs.
* **Service Diagnostics Tool Updates** -- These improvements have been made to the Service Diagnostics tool:
* Added Incoming and Outgoing traffic information
* Added Click to Copy functionality for the serviceId
* Optical levels and traffic graphs are now available for Ports
* Shutdown status is now displayed for IXs, VXCs, and Megaport Internet connections
* You can now click to go directly from the Service Diagnostic tool to the service's Connection Details page
* The tool now includes the number of attached connections to a service, with the ability to view the details of any connections that are down.
* **New Help and Support Menu** -- A new Help menu is available in the Megaport Portal header. Click the Help icon (?) to access Documentation, API Documentation, Release Notes, Support Requests, and Send Feedback from a single location. Support Requests and Send Feedback have moved from the User menu to the new Help menu. By bringing these tools together, we've made it faster for you to find answers, manage tickets, and share feedback without switching menus.
* **Extended Sites on Portal Dashboard** -- Extended and partner-delivered data center sites are now displayed on the Portal Dashboard. Extended sites are shown with distinct map pins to differentiate them from enabled locations. A new vertical menu on the dashboard lets you filter between **Show enabled locations** (all locations including extended) and **Show installed locations** (only active and deployment-ready sites). Extended sites support viewing, but to order services at these locations, contact your Account Manager for assistance.
* **Increase Service Status History from 7 to 90 Days** -- The service status information history in the Megaport Portal has been extended from 7 days to 90 days. This means you can now view the status of your services for a longer period, which can be helpful for troubleshooting and historical analysis. The filters for Maintenance and Outage statuses have also been updated to reflect the extended 90-day window, with label changes to indicate Maintenance (Completed/Cancelled) and Outage (Resolved).
* **Terraform v1.5.1** -- Version 1.5.1 of the Terraform provider has been released. This release includes several bug fixes and improvements, including:
* CSP partner port rotation warnings replaced with debug-level logging
* MCR prefix filter list reads/updates now skip unnecessary API fetches
* Prefix filter list deletes retry on 409 conflicts to handle race conditions
* Terraform MCP server documentation added
* Acceptance tests improved for better reliability
For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.5.1](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.5.1).
* **Terraform v1.5.0** -- Version 1.5.0 of the Terraform provider has been released. This release includes several bug fixes, including:
* Resolves issues with VXC vnic\_index drift
* VXC import drift
* MCR prefix filter CIDR normalization
* VXC ip\_mtu on B-End
* MVE sizes data source
For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.5.0](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.5.0).
* **Quoting Tool Enhancements** -- These improvements have been made this month:
* Improved the usability of the CSV export file. Service name, Location, and other details are now in separate columns for easier analysis.
* For partner companies only, a new column called **Partner Rates** has been added to the CSV export file. This column shows the discounted price for that partner for the service for the associated term.
* **Issues fixed:**
* Resolved an issue in the MCR Looking Glass where IP prefixes could not be expanded to view detailed information. Users can now reliably expand prefixes to inspect route details as expected.
* Resolved an issue where some customers were unable to open the support chat in the Megaport Portal. The chat widget now loads and functions correctly for all affected users.
* Resolved an issue in Activity Logs where adding additional **Type** filter options did not visually update the selection in the UI, even though the results were filtered correctly. All selected types are now clearly displayed in the Type filter control so the applied filters accurately reflect the results.
* Resolved an issue on the IX connection configuration page where the Graph Visibility buttons (Public/Private) could not be selected and saving changes did not work. Users can now successfully change IX graph visibility between Public and Private and save the updated configuration.
* **MVE for Cisco Meraki General Availability** -- This release removes the beta status from the Cisco Meraki integration, which is now fully supported for production deployments. You no longer need to contact your Account Manager before deploying. For more information, see [Creating an MVE with Cisco Meraki](/mve/cisco/creating-mve-meraki).
* **Latitude.sh Application Switcher** -- A new drop-down menu is available via the Megaport logo in the Megaport Portal header. Click the drop-down and select **latitude.sh** to navigate directly to the Latitude.sh dashboard. This provides a quick way to switch between the Megaport Portal and Latitude.sh without navigating through menus.
* **Google Sign-in for the Latitude.sh Portal** -- From the new drop-down menu, you can now sign in to the Latitude portal using your Google account. After authenticating with Google, you will be returned to the Portal and logged in, with clear messaging if your Google account is not linked to a Megaport account.
* **Service Diagnostics Tool (Initial Release)** -- A new **Service Diagnostics** icon is available for all services on the Services page. Click this icon to view the current operational status of a service, including whether it is up or down, any scheduled maintenance, and active outages. For Ports, MCRs, and MVEs, the diagnostic also displays the total number of attached connections and highlights any that are down or shut down, with links to troubleshooting resources. This is an initial release with additional enhancements planned.
* **100 Gbps Megaport Internet VXCs** -- 100 Gbps Megaport Internet VXCs are now available in Chicago.
* **Configured Services Sidebar Moved** -- The Configured Services sidebar (shopping cart) has been moved from the left side of the Portal screen to the right side. This change improves space and consistency for navigation, in preparation for the upcoming Portal side navigation layout.
* **Arista VeloCloud Multi-vNIC Support** -- When ordering an Arista VeloCloud MVE, you can now configure up to five vNICs (including the default vNIC). You must select the additional vNICs during MVE creation, as you cannot add or remove them after deployment.
* **Megaport Internet 2-Month Expiration Notice** -- Customers with Megaport Internet connections on contract terms now also receive an automated email notification two months before the term expires, in addition to the existing one-month notification.
* **Activity Logs Enhancement** -- The Activity Logs page now displays User Type and User in separate columns with independent filters, making it easier to filter activity by specific criteria.
* **Improved Billing Display for Ports with a Cross Connect** -- Updated the Billing tab in the Port details to show a separate Cross Connect Monthly Rate line item for Ports with a Cross Connect.
* **India Billing Market** -- India is now available as a billing market, with INR (Indian Rupee) as the supported currency. Customers can now also pre-order Ports in India.
* **Quoting Tool Enhancements** -- These improvements have been made:
* Added diversity zone selection so users can specify Red/Blue site preferences when creating quotes for Ports, MCRs, MVEs, and Cloud VXCs.
* Added IX terms so users can generate quotes for an IX connection on terms. The term defaults to 12 months.
* Customers can now quote Ports and VXCs in India.
* Add-on charges (for example, Cross Connects, IPsec) are now on a separate row and diversity zone is now in a separate column when downloading the quote in comma-separated values (CSV) format.
* Added enhanced PDF export options. When downloading a quote as a PDF, users can now optionally include an About Megaport section, a Tax Registration number, and a company address. The downloaded PDF includes the selected options and any text entered in these new fields.
* A new Pricing Comparison view is available in the Quote Summary section, displaying quoted services with all the term options and their respective prices. This allows users to compare term pricing across the entire quote in a single view.
* **100 Gbps Megaport Internet VXCs** -- 100 Gbps Megaport Internet VXCs are now available in Atlanta, Ashburn, and Dallas, with more locations to follow soon!
* **MVE Console Access in the Megaport Portal** -- You can now access your Megaport Virtual Edge (MVE) console directly from the Megaport Portal. This secure, browser-based console allows you to run commands and perform configuration tasks without external tools. Console sessions are encrypted, role-based, and automatically disconnected after inactivity.\
For more information, see [Using the MVE Console](/mve/console-access).
* **IX Contract Terms** -- You can now place new and existing IX services on a contract term.
* The term defaults to 12 months for new orders. 12, 24, 36, 48, and 60-month terms are available.
* The rate limit can be increased to the maximum speed allowed or decreased back to the original speed when termed.
* Early termination fees (ETF) apply when canceling an IX on term.
* **Dark Mode Support (Beta)** -- Introducing our new dark mode interface for the Megaport Portal. You can select the mode in which to view the Portal from the new **Theme** option in the User menu.
* **Order Approval for Managed Accounts** -- Partners can now require managed accounts to submit service requests for approval. This feature gives partners full control over service fulfillment and billing for their managed users. New services, re-terming, and speed changes now require partner approval before managed account users can proceed if approval is on (approval is off by default, and requests expire if not actioned within 7 days).
Key capabilities include:
* **Partner Review Queue** – A new **Manage Order** dashboard allows partners to approve or reject new service orders, speed changes, and re-terming requests from a centralized queue.
* **Service Integrity** – Services are automatically locked while an approval request is pending to prevent conflicting modifications.
* **Automated Notifications** – Four new notification types are available to keep both partners and managed users informed of order status changes. These notifications are enabled by default for all users.
* **Partner Admin Self-Service** – An updated **Partner Admin** page provides a table view to manage feature toggles across all managed accounts in real time. Partners can configure approval requirements per managed account.
* **Service Termination Approval for Managed Accounts** -- Support has been added for requiring approval of early service terminations. Partners who have enabled approval requirements for managed account services will now receive approval requests when a managed account user attempts to terminate a service that incurs an early termination fee (ETF).
* **New Aviatrix Version** -- A new Aviatrix image, g4-202507291722, has been added to the Megaport Portal for selection when creating an MVE with Aviatrix. For more information, see [Creating an MVE Integrated with Aviatrix](/mve/aviatrix/creating-mve-aviatrix).
* **Terraform v1.4.7** -- Version 1.4.7 of the Terraform provider has been released. This is a small release that fixes some issues with the standalone Prefix Filter List Resource and updating VXCs in production. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.7](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.4.7).
* **AWS 4-Byte ASN Support** -- AWS Direct Connect now supports 4-byte ASNs, meaning customers can now specify a value between 2 and 4294967294 for the Customer ASN field when configuring a new AWS Hosted VIF connection.
* **EECC Waiver for EU Micro/Small Businesses in Billing Markets** -- We have added EECC waiver for EU micro/small businesses in billing markets, which allows qualifying organizations to opt out of European telecom consumer protections during billing setup.
* **Checkout Pricing Refresh** -- The Portal now automatically refreshes prices when you click **Buy** if the pricing was fetched more than one minute ago. If prices have changed since your last view, the updated pricing is shown before you confirm your purchase.
* **Added IP Address as a Quotable Service in the Quoting Tool** -- IP Address has been added as a standalone product in the Quoting Tool with configurable location, purpose, currency and subnet size, allowing users to add and configure IP addresses as part of a quote.
* **Issues fixed:**
* Overlapping services and table part format are not showing correctly in the MCR Looking Glass.
* Ordering Megaport Internet services in certain non-US markets (Spain, Luxembourg, and Mexico) incorrectly required the US billing market to be enabled. Billing market validation now correctly uses the local market for these countries.
## Previous years
* [2025](/whatsnew/2025)
* [2024](/whatsnew/2024)
* [2023](/whatsnew/2023)
* [2022](/whatsnew/2022)
* [2021](/whatsnew/2021)
* [2020](/whatsnew/2020)
# Creating an IP Address Block
Source: https://docs.megaport.com/ip-address/creating-ip-address
This help topic describes how to order an IP Address block in the Megaport Portal.
This topic describes how to order an IP Address block on the Megaport network.
IP Address is available as a standalone product, and blocks are provisioned automatically after you place your order. You can also request a new IP Address block directly from an existing Megaport Internet connection. The request takes you to the same ordering flow described below.
Before proceeding, ensure that you have set up your Megaport Portal account. For more information, see [Setting Up a Megaport Account](/setting-up).
**To order an IP Address block**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Service**, then select **IP Address**.
3. Specify the block details:
* **Block Name** -- Specify a name for the block that is easily identifiable, particularly if you plan on ordering more than one.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
4. Select a location.
Use the **Search** field, or select a region and then a metro.
5. Select the IP version and block size:
* **IP Version** -- Select **IPv4** or **IPv6**.
* **Block Size** -- Select a subnet size. The available sizes depend on the IP version:
* **IPv4** -- Select a subnet size from /30 to /24. Each option shows the number of addresses in the block and its monthly rate.
* **IPv6** -- Select a subnet size of /64, /60, /56, or /48. Each option shows its monthly rate. Sizes that have no monthly charge are labeled **Free**.
6. IP Address orders are for a minimum 12-month contract term. Review the **Contract Term** information, and turn off **Contract Renewal** if you do not want the block to automatically renew for another 12-month term when the contract ends.
7. Complete the **Usage & Justification** section:
* **Purpose** -- Enter a description of the intended purpose of the block, for example, Mail Server or Load Balancer.
* **Projected Duration** -- Select 12 Months, 24 Months, or 36 Months.
* **Additional Remarks** (optional) -- Enter any additional information that further explains the need for IP address space.
The contract term for an IP Address block is fixed at 12 months. When ordering, you must select a projected duration of 12, 24, or 36 months. The projected duration does not need to match the contract term. Megaport uses the projected duration to allocate additional public IP addresses, and you must confirm that you intend to use the requested allocation within the selected timeframe.
8. (Optional) Under **Link Internet VXCs**, select any live Megaport Internet connections in the selected metro that you want to link to the block.
9. Review the terms and conditions.
10. (Optional) Click **+ Add New Tag** to specify any resource tags for the IP Address block. Enter a **Key** and **Value** for the tag.
* **Key** -- Specify a lowercase string with a maximum length of 128 characters. Valid characters are letters, numbers, and - . \_ : / \\
* **Value** -- Specify a string with a maximum length of 256 characters. Valid characters are letters, numbers, spaces, and - . \_ : @ / + \\
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that identifies a person or company.
11. Click **Add IP Address Block**.
The block is added to your cart under Configured Services.
12. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
13. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
IP Address blocks do not receive a Standard Term discount. If your cart contains only an IP Address block, the Standard Term discount does not appear at checkout. It appears only when your cart also contains services that receive a term-based discount.
14. Click **Order Now**.
The IP Address block is provisioned automatically, typically within seconds.
## Helpful references
* [IP Address Overview](/ip-address)
* [Linking and Unlinking Megaport Internet Connections](/ip-address/linking-vxc)
* [Megaport Internet Overview](/megaport-internet)
# IP Address Overview
Source: https://docs.megaport.com/ip-address/index
This help topic describes the IP Address product, including how it works, block sizes, resource limits, and contract terms.
An block is a public IPv4 or IPv6 subnet that you order, manage, and link to your services in the Megaport Portal. IP Address is available as a standalone product, alongside Ports, MCRs, MVEs, and NAT Gateways.
You do not need an existing Megaport Internet connection to order an IP Address block. You can link the block to one or more Megaport Internet connections in the same metro during ordering or at any time afterward to advertise the addresses.
## How it works
An IP Address block is available across a metro rather than being tied to a specific data center or connection. When you order a block, you select a metro, IP version, and subnet size. Megaport then provisions the block automatically, typically within seconds. No manual approval is required.
After a block is live, you can:
* Link it to one or more Megaport Internet connections in the same metro. A block can be linked to multiple connections, and a connection can have multiple blocks linked to it. For more information, see [Linking and Unlinking Megaport Internet Connections](/ip-address/linking-vxc).
* Request a new IP Address block directly from an existing Megaport Internet connection, on the **Megaport Internet** tab of the Connection Details page, instead of starting from **Add Service**.
* Rename the block, update its resource tags, or change its linked connections at any time.
After you order a block, its metro, IP version, and subnet size cannot be changed. To use a different metro, IP version, or subnet size, you must order a new IP Address block.
If you delete an IP Address block, any linked Megaport Internet connections are automatically unlinked before the block is deleted. The addresses return to the available pool, so you might not be able to order the same range again.
## IP Address block sizes
IP Address blocks are available in IPv4 and IPv6 subnet sizes.
**IPv4**
The monthly rate for each subnet size is shown when you select it during ordering. Some IPv6 block sizes have no monthly charge. For more information, see [Creating an IP Address Block](/ip-address/creating-ip-address).
## Resource limits
By default, the resource limit for IP Address blocks is 0 (Zero). To adjust the limit, contact Megaport Support or your Customer Success Manager. For more information, see [Limits and Quotas](/limits-quotas#ip-address).
## IP Address terms
IP Address blocks are ordered on a minimum 12-month contract term. By default, the block automatically renews for another 12-month term when the contract ends. You can turn off automatic renewal during ordering, or later, so the block moves to month-to-month billing instead.
If you terminate the block before the end of its term, an early termination fee (ETF) applies. You can waive the ETF by ordering an eligible replacement service. For more information, see [IP Address Pricing and Contract Terms](/finance/ip-address-pricing) and [Managing Early Termination Fees](/finance/etf-management).
## Helpful references
* [Creating an IP Address Block](/ip-address/creating-ip-address)
* [IP Address Billing](/finance/ip-address-billing)
* [IP Address Pricing and Contract Terms](/finance/ip-address-pricing)
* [Linking and Unlinking Megaport Internet Connections](/ip-address/linking-vxc)
* [Managing Early Termination Fees](/finance/etf-management)
* [Megaport Internet Overview](/megaport-internet)
* [Megaport Limits and Quotas](/limits-quotas)
# Linking and Unlinking Megaport Internet Connections
Source: https://docs.megaport.com/ip-address/linking-vxc
This help topic describes how to link and unlink Megaport Internet connections to an IP Address block in the Megaport Portal.
You can link an IP Address block to one or more Megaport Internet connections in the same metro. A block can be linked to multiple connections, and a connection can have multiple blocks linked to it.
Only live Megaport Internet connections in the same metro as the block are eligible for linking. You can link or unlink a connection from either the IP Address block or the Megaport Internet connection. Both methods produce the same result.
Megaport-assigned IP address space must be advertised only on Megaport Internet services. Advertising these networks to other Megaport services or third-party providers is forbidden.
## Linking from an IP Address block
Use the **Configuration** tab of the block to select the Megaport Internet connections that you want to link.
**To link from an IP Address block**
1. In the Megaport Portal, go to the **Services** page and click the IP Address block.
2. Click the **Configuration** tab.
3. Under **Link Internet VXCs**, select the check box next to each connection you want to link. Only connections in the same metro as the block are available for selection.
4. Click **Save linked VXCs**.
The **Linked VXCs** tab shows each linked connection as a topology diagram, including the VLANs, speed, and diversity zone on each end.
## Linking from a Megaport Internet connection
Use the **Megaport Internet** tab of the connection to select the IP Address blocks that you want to link.
**To link from a Megaport Internet connection**
1. In the Megaport Portal, go to the **Services** page and click the Megaport Internet connection.
2. Click the **Megaport Internet** tab in the Connection Details page.
3. Under **IP Addresses**, select the check box next to each block you want to link. Blocks are listed by their prefix, not by name, and only blocks in the same metro as the connection are available for selection.
If you do not have an existing block in the metro, click **Request IP Address** to order a new one. For more information, see [Creating an IP Address Block](/ip-address/creating-ip-address).
4. Click **Link IP Address**.
The **Configuration** tab lists available connections by name, while the **Megaport Internet** tab lists available IP Address blocks by prefix.
## Unlinking an IP Address block
You can also unlink an IP Address block from a Megaport Internet connection.
* **From the block** -- In the **Services** page, click the IP Address block you want to update, then click the **Configuration** tab. Clear the check box next to the connection, then click **Save linked VXCs**.
* **From the connection** -- In the **Services** page, click the Megaport Internet connection, then click the **Megaport Internet** tab. Under **IP Addresses**, click **Unlink** next to the block.
Changes apply immediately after saving. Unlinking a connection does not delete the IP Address block or the connection, it only removes the association between them. If you terminate the IP Address block or the connection, the link is removed automatically.
## Helpful references
* [Creating an IP Address Block](/ip-address/creating-ip-address)
* [IP Address Overview](/ip-address)
* [Megaport Internet Overview](/megaport-internet)
# Terminating an IP Address Block
Source: https://docs.megaport.com/ip-address/terminating-ip-address
This help topic describes how to terminate an IP Address block directly from the Megaport Portal.
You can terminate an IP Address block directly from the Megaport Portal.
If the block is linked to any Megaport Internet connections, those connections are unlinked automatically before the block is deleted. The addresses return to the available pool, so you might not be able to order the same range again.
Terminating an IP Address block on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [IP Address Pricing and Contract Terms](/finance/ip-address-pricing) and [Managing Early Termination Fees](/finance/etf-management).
**To terminate an IP Address block**
1. In the Megaport Portal, go to the **Services** page.
2. Click the **Actions** menu next to the IP Address block you want to terminate, then click **Delete**.
The Terminate Services window appears. Early termination fees will be shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the block. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the termination, or click **No, Keep Services** to cancel.
The IP Address block is deleted from the Megaport network.
# Megaport Internet Overview
Source: https://docs.megaport.com/megaport-internet/index
This help topic describes the Megaport Internet connection model available in the Megaport Portal.
Megaport lets you connect to the services you need, when you need them. The process is simple and fast, and involves these basic steps:
1. Create a [Port](/connections/creating-port), [Megaport Cloud Router (MCR)](/mcr/creating-mcr), [Megaport Virtual Edge (MVE)](/mve), or [Megaport NAT Gateway (NAT Gateway)](/nat/creating-nat-gateway).
2. Deploy Megaport Internet connections.
3. Use Megaport Internet connections to connect to the internet.
connections are scalable, on-demand services delivered over a VXC that allow you to connect to the public internet from Ports, MCRs, MVEs, and NAT Gateways. Port, MCR, and NAT Gateway connections are available countrywide. MVE connections are available in all countries where there are available resources. MVE connections are available in any country where Megaport Internet is available. Diversity zones are enabled on internet routers which you can select when creating a connection.
You can add up to 100 Megaport Internet connections per Port and up to 25 Megaport Internet connections per MCR, MVE, or NAT Gateway. Any limit on the number of VXCs per Port, MCR, MVE, or NAT Gateway will include the Megaport Internet service, along with any other type of VXC.
You must use Megaport Internet in accordance with the Service Schedule that forms part of your Agreement with Megaport.
Megaport Internet connections for Ports and MCRs can be ordered from Australia, US, UK, NZ, Canada, Singapore, Japan, France, Germany, Spain, Ireland, Switzerland, and India, and are countrywide only. That is, the A-End and B-End must be in the same country.
Megaport Internet connections for NAT Gateways can be ordered from Australia, Brazil, Canada, France, Germany, Hong Kong, India, Ireland, Italy, Japan, New Zealand, Singapore, Spain, Sweden, Switzerland, UK, and USA, and are countrywide only.
### Megaport Internet usage policies
Megaport Internet is policed/rate limited to the purchased bandwidth. We do not apply any volume-based limitation (that is, Gbps/month). We also don't provide DNS services and so therefore have no visibility into what websites a customer is visiting, and do not record personal data.
We don't apply volume limits or quality of service parameters to the service aside from limiting throughput to the purchased speed. The customer should be able to use the full amount of their purchased speed for the entire duration of the service provided they are not congesting their access product.
If a customer has a 1 Gbps access product with 100 Mbps of internet and a 1 Gbps VXC on it, if they download at 1 Gbps over their VXC it could have a detrimental effect on the performance of their internet service. We allow customers to oversubscribe their Port but the utilization of the service is entirely within their control.
The download and upload speed of the internet service should match the purchased rate limit. For more information, see [Megaport Internet rate limits](#mic-rate-limit).
Megaport does not control conditions outside of our network. The download and upload rates are applicable only in aggregate (that is, downloading from/uploading to multiple sources) or within our own network.
## Network architecture
The network has been designed so that if one of the two upstream connections goes down, the failover mechanism established between the two internet routers will push the traffic onto the second upstream link, ensuring the continuity of the service.
To increase the availability of the service, we recommend:
* Connecting two Megaport Internet services from the single endpoint (Port/MCR/MVE), one connecting to the internet router (red) and the other one connecting to the internet router (blue), or
* Two connections each with all elements in the same diversity zone. That is, Port (red) > Megaport Internet > internet router (red) + Port (blue) > Megaport Internet > internet router (blue).
## Features and benefits
Using Megaport Internet connections can benefit users and organizations in the following ways:
* **Instant provisioning** -- Users can activate a new internet connection on an existing service in under 60 seconds.
* **Scalability** -- Customers can save money by adjusting the connection bandwidth according to their requirements. A Megaport Internet connection can be created with a rate limit from 20 Mbps to several Gbps and adjusted in increments of 1 Mbps.
* **Flexible terms** -- Users can cancel any time without an early termination fee (ETF). Month-to-month contract terms are available.
* **Diversity** -- Customers can minimize disruptions to their network by building resilient designs. Two diversity zones are offered for the internet routers.
* **Public static IP address** -- Customers can define policies and routes knowing that the IP address will stay the same. A Megaport Internet connection has a single usable IPv4 or /64 public IPv6 subnet.
## Megaport Internet use cases
Megaport Internet connections are commonly used for these purposes:
* **Main or back-up internet connection** -- Highly scalable and resilient internet connection used as main or secondary access.
* **Temporary internet connection** -- Internet connection established for seasonal needs or for specific time-bound projects.
* **Management link** -- Minimum internet bandwidth established to gain out-of-band management access to network assets.
The public IP address associated with a Megaport Internet connection cannot be used for public cloud peering.
## Megaport Internet rate limits
Megaport Internet connections can be created from a Port, MCR, or MVE from 20 Mbps to several Gbps. The rate limit is scalable and you can specify any speed within these limits in increments of 1 Mbps.
For Ports and MCRs, the maximum Megaport Internet speed cannot exceed the maximum speed of the service it is being connected to.
## Megaport Internet terms
You can specify an optional term for your connection. The choices are:
* No Minimum Term
* 12 months (this is the default)
* 24 months
* 36 months
* 48 months
* 60 months
Discounts are applied depending on the term duration. For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing).
You can select No Minimum Term to pay-as-you-go at the current rack rate and adjust the rate limit as required.
If you have a Megaport Internet connection on a contract term, you can change the speed of the connection. For more information, see [Changing the Speed of a Termed VXC](/connections/vxc-termed-rate-change).
Deleting a Megaport Internet connection before the end of the term will generate early termination fees (ETF), also known as early termination charges (ETC). To avoid ETF, select No Minimum Term until the configuration is complete. You can update the connection at any time to opt into a term.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
## Locations available
Megaport Internet connections are available for the indicated services in these countries:
| Country | Port | MCR | MVE | NAT Gateway |
| :-: | :-: | :-: | :-: | :-: |
| Australia | **✓** | **✓** | **✓** | **✓** |
| Brazil | **✓** | **✓** | **✓** | **✓** |
| Canada | **✓** | **✓** | **✓** | **✓** |
| France | **✓** | **✓** | **✓** | **✓** |
| Germany | **✓** | **✓** | **✓** | **✓** |
| Hong Kong | **✓** | **✓** | **✓** | **✓** |
| India | **✓** | **✓** | **✓** | **✓** |
| Ireland | **✓** | **✓** | **✓** | **✓** |
| Italy | **✓** | **✓** | **✓** | **✓** |
| Japan | **✓** | **✓** | **✓** | **✓** |
| Mexico | | **✓** \* | **✓** | |
| Netherlands | | **✓** \* | **✓** | |
| New Zealand | **✓** | **✓** | **✓** | **✓** |
| Singapore | **✓** | **✓** | **✓** | **✓** |
| Spain | **✓** | **✓** | **✓** | **✓** |
| Sweden | **✓** | **✓** | **✓** | **✓** |
| Switzerland | **✓** | **✓** | **✓** | **✓** |
| UK | **✓** | **✓** | **✓** | **✓** |
| USA | **✓** | **✓** | **✓** | **✓** |
\* MCR requires IPsec.
## IP Address blocks
IP Address is available as a standalone product, independent of Megaport Internet. You can order an IP Address block on its own or when managing a Megaport Internet connection, then link the block to one or more Megaport Internet connections in the same metro.
For more information, see [IP Address Overview](/ip-address).
## Configure BGP on Megaport Internet
After your Megaport Internet connection is live, you can configure . To add BGP details, edit the Megaport Internet connection and enter your BGP settings.\
For more information, see [Enabling BGP](/megaport-internet/routing#enableBGP).
## Move and shut down
After Megaport Internet connections have been created in the Megaport Portal, they can be managed in the same way as a VXC. You can move a Megaport Internet connection between services of the same type, for example, Port to Port or MCR to MCR. This is useful for reducing interruptions during maintenance and other tasks that would otherwise cause downtime. Moving the Megaport Internet connection will not affect the contract term. For more information, see [Moving VXCs](/connections/move-vxc).
You can also temporarily shut down a Megaport Internet connection, for example, for failover testing, redundancy, or network design testing purposes. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
## Helpful references
* [Creating a Megaport Internet Connection for an MCR](/megaport-internet/mcr)
* [Creating a Megaport Internet Connection for an MVE](/megaport-internet/mve)
* [Creating a Megaport Internet Connection for a NAT Gateway](/megaport-internet/nat-gateway)
* [Creating a Megaport Internet Connection for a Port](/megaport-internet/port)
* [Creating a Megaport Internet Connection from a Port with the API](/api/api-mic)
* [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing)
* [Megaport Internet Routing Guide](/megaport-internet/routing)
* [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring)
* [Terminating a Megaport Internet Connection](/megaport-internet/terminating-connection)
* [Troubleshooting Megaport Internet Connectivity](/troubleshooting/mic/megaport-internet)
* [Understanding the Services Page](/portal-admin/services-page)
* [VXC, Megaport Internet, and IX Billing ](/finance/billing-details)
# Creating a Megaport Internet Connection for an MCR
Source: https://docs.megaport.com/megaport-internet/mcr
This help topic describes how to create a Megaport Internet connection for an MCR in the Megaport Portal.
This topic describes how to create a Megaport Internet connection for an MCR in the Megaport network.
With an MCR configured, you can create a Megaport Internet connection. You can create a Megaport Internet connection for an MCR, for example, as your main or back-up internet connection, or to establish an internet connection for seasonal needs or for specific time-bound projects.
If you are creating a Megaport Internet connection for an MCR in Mexico or the Netherlands, you must enable and keep IPsec enabled on the MCR. You cannot disable IPsec in these markets. For more information, see [Using IPsec with MCR](/mcr/ipsec-mcr).
For more information about Megaport Internet connections, see [Megaport Internet Overview](/megaport-internet).
## Creating a Megaport Internet connection
You can create a Megaport Internet connection for an MCR during MCR provisioning or any time after it has been provisioned.
**To create a Megaport Internet connection**
1. In the Megaport Portal, go to the **Services** page and select the MCR you want to use.
If you haven't already created an MCR, see [Creating an MCR](/mcr/creating-mcr).
2. If this is the first connection for the MCR, click the **Megaport Internet** tile. The tile is a shortcut to the configuration page. Alternatively, click **+Connection**.
MCR details including the speed, location, and diversity zone are displayed. The diversity zone for an A-End service is visible after the service is deployed and available.
3. Click **Megaport Internet**.\
Port details including name, location, diversity zone, and latency are displayed.
4. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere in the same country as the originating MCR.\
You can filter by diversity zone, or select to view all.
5. Click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next**.\
The MCR A-End Connection Details page displays, indicating that the MCR connection configuration will be generated automatically. The connection details can be changed later if required.
8. Click **Next** to review the Megaport Internet connection summary, including price.
9. Click **Add VXC** to save the connection.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
When the Megaport Internet connection is deployed, you can view it in the Portal Services page.
## Updating a Megaport Internet connection
You can update a Megaport Internet connection for an MCR any time after it has been created.
**To edit a Megaport Internet connection**
* Click the gear icon next to the connection in the Megaport Portal to make changes.
You can modify the details on the Megaport side including the connection name, rate limit, service level (invoice) reference, connection state, and contract terms. You can also modify the MCR connection details including interface IP address, NAT source IP address, BGP connections, enable BFD, and static routes.\
Once submitted, the changes take effect in a few minutes.
**To add BGP details to a Megaport Internet connection**
You can add BGP information to the Megaport Internet connection when the connection is live.\
For more information, see [Enabling BGP](/megaport-internet/routing#enableBGP).
## Helpful references
* [Creating a Megaport Internet Connection for an MVE](/megaport-internet/mve)
* [Creating a Megaport Internet Connection for a NAT Gateway](/megaport-internet/nat-gateway)
* [Creating a Megaport Internet Connection for a Port](/megaport-internet/port)
* [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing)
* [Megaport Internet Routing Guide](/megaport-internet/routing)
* [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring)
* [Terminating a Megaport Internet Connection](/megaport-internet/terminating-connection)
* [Troubleshooting Megaport Internet Connectivity](/troubleshooting/mic/megaport-internet)
* [Understanding the Services Page](/portal-admin/services-page)
* [VXC, Megaport Internet, and IX Billing ](/finance/billing-details)
# Creating a Megaport Internet Connection for an MVE
Source: https://docs.megaport.com/megaport-internet/mve
This help topic describes how to create a Megaport Internet connection for an MVE in the Megaport Portal.
This topic describes how to create a Megaport Internet connection for an MVE in the Megaport network.
With an MVE configured, you can create a Megaport Internet connection. You can create a Megaport Internet connection for an MVE, for example, as your main or back-up internet connection, or to establish an internet connection for seasonal needs or for specific time-bound projects.
For more information about Megaport Internet connections, see [Megaport Internet Overview](/megaport-internet).
## MVE setup
Internet access might be required as part of initial MVE setup, and we highly recommend that you create a Megaport Internet connection during the provisioning process. However, you can also create a Megaport Internet connection for an MVE at a later time.
See the Megaport Internet connection process during MVE setup for each supported provider:
* 6WIND -- See [Creating an MVE Integrated with 6WIND](/mve/6wind/creating-mve-6wind)
* Anapaya -- See [Creating an MVE Integrated with Anapaya](/mve/anapaya/creating-mve-anapaya)
* Arista VeloCloud SD-WAN -- See [Creating an MVE Integrated with Arista VeloCloud SD-WAN](/mve/vmware/creating-mve)
* Aruba EdgeConnect SD-WAN -- See [Creating an MVE Integrated with Aruba Overview](/mve/aruba/creating)
* Aviatrix -- See [Creating an MVE Integrated with Aviatrix](/mve/aviatrix/creating-mve-aviatrix)
* Check Point -- See [Creating an MVE Integrated with Check Point](/mve/checkpoint/creating-mve-checkpoint)
* Cisco -- See [Creating a Cisco MVE in Autonomous Mode](/mve/cisco/creating-mve-autonomous)
* Deciso OPNsense -- See [Creating an MVE Integrated with Deciso OPNsense](/mve/deciso/creating-mve-deciso)
* F5 BIG-IP Virtual Edition -- See [Creating an MVE Integrated with F5 BIG-IP Virtual Edition](/mve/f5/creating-mve-f5-bigip)
* Fortinet FortiGate -- See [Creating an MVE Integrated with Fortinet](/mve/fortinet/creating-mve)
* Juniper -- See [Juniper with Megaport Virtual Edge](/mve/juniper)
* Netskope One SD-WAN -- See [Creating an MVE Integrated with Netskope One SD-WAN](/mve/netskope/creating-mve-netskope)
* Palo Alto Networks VM-Series Next Generation Firewall -- See [Creating a VM-Series MVE](/mve/palo-alto/creating-mve)
* Palo Alto Networks Prisma SD-WAN -- See [Creating an MVE Integrated with Palo Alto Prisma SD-WAN](/mve/palo-alto/creating-mve-prisma)
* Peplink FusionHub -- See [Creating an MVE Integrated with Peplink](/mve/peplink/creating-mve-peplink)
* Versa Secure SD-WAN -- See [Creating an MVE Integrated with Versa](/mve/versa/creating-mve)
## Creating a Megaport Internet connection
You can create a Megaport Internet connection for an MVE during MVE provisioning or any time after it has been provisioned.
**To create a Megaport Internet connection**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
If you haven't already created an MVE, see the [MVE Overview](/mve) for vendor-specific details about creating an MVE.
2. Click **+Connection**.
MVE details including the size, location, and diversity zone are displayed.
3. Click **Megaport Internet**.\
Port details including name, location, diversity zone, and latency are displayed.
4. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can filter by diversity zone, or select to view all.
5. Select the diversity zone that matches the diversity zone of the MVE.
6. Click **Next**.
7. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Specify a vNIC from the drop-down list. For more information about vNICs, see [Types of vNIC Connections](/mve/vnic-connections).
We recommended that you follow the Megaport documentation section fro the MVE vendor you are deploying for vendor vNIC and VLAN specifics.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged**. This selection removes the VLAN tagging for this connection and it will be configured without a VLAN ID.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
8. Click **Next** to review the Megaport Internet connection summary, including price.
9. Click **Add VXC** to save the connection.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
When the Megaport Internet connection is deployed, you can view it in the Portal Services page.
## Updating a Megaport Internet connection
You can update a Megaport Internet connection for an MVE any time after it has been created.
**To edit a Megaport Internet connection**
* Click the gear icon next to the connection in the Megaport Portal to make changes.
You can modify the details on the Megaport side including the connection name, rate limit, VLAN ID, service level (invoice) reference, connection state, and contract terms. Once submitted, the changes take effect in a few minutes.
**To add BGP details to a Megaport Internet connection**
You can add BGP information to the Megaport Internet connection when the connection is live.\
For more information, see [Enabling BGP](/megaport-internet/routing#enableBGP).
## Helpful references
* [Creating a Megaport Internet Connection for an MCR](/megaport-internet/mcr)
* [Creating a Megaport Internet Connection for a NAT Gateway](/megaport-internet/nat-gateway)
* [Creating a Megaport Internet Connection for a Port](/megaport-internet/port)
* [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing)
* [Megaport Internet Routing Guide](/megaport-internet/routing)
* [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring)
* [Terminating a Megaport Internet Connection](/megaport-internet/terminating-connection)
* [Troubleshooting Megaport Internet Connectivity](/troubleshooting/mic/megaport-internet)
* [Understanding the Services Page](/portal-admin/services-page)
* [VXC, Megaport Internet, and IX Billing ](/finance/billing-details)
# Creating a Megaport Internet Connection for a NAT Gateway
Source: https://docs.megaport.com/megaport-internet/nat-gateway
This help topic describes how to create a Megaport Internet connection for a Megaport NAT Gateway in the Megaport Portal
This topic describes how to create a Megaport Internet connection for a NAT Gateway in the Megaport network.
With a NAT Gateway configured, you can create a Megaport Internet connection. You can create a Megaport Internet connection for a NAT Gateway, for example, as your main or back-up internet connection, or to establish an internet connection for seasonal needs or for specific time-bound projects.
For more information about Megaport Internet connections, see [Megaport Internet Overview](/megaport-internet).
## Creating a Megaport Internet connection
You can create a Megaport Internet connection for a NAT Gateway during NAT Gateway provisioning or any time after it has been provisioned.
**To create a Megaport Internet connection**
1. In the Megaport Portal, go to the **Services** page and select the NAT Gateway you want to use.
If you haven't already created a NAT Gateway, see [Creating a NAT Gateway](/nat/creating-nat-gateway).
2. If this is the first connection for the NAT Gateway, click the **Megaport Internet** tile. The tile is a shortcut to the configuration page. Alternatively, click **+Connection**.
NAT Gateway details including the speed, location, and diversity zone are displayed. The diversity zone for an A-End service is visible after the service is deployed and available.
3. Click **Megaport Internet**.\
Port details including name, location, diversity zone, and latency are displayed.
4. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere in the same country as the originating NAT Gateway.\
You can filter by diversity zone, or select to view all.
5. Click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next**.\
The NAT Gateway A-End Connection Details page is displayed, indicating that the NAT Gateway connection configuration will be generated automatically. The connection details can be changed later if required.
8. Click **Next** to review the Megaport Internet connection summary, including price.
9. Click **Add VXC** to save the connection.
10. Click **Review Order** to proceed through the checkout process.\
When the Megaport Internet connection is deployed, you can view it in the Portal Services page.
## Updating a Megaport Internet connection
You can update a Megaport Internet connection for a NAT Gateway any time after it has been created.
**To edit a Megaport Internet connection**
* Click the gear icon next to the connection in the Megaport Portal to make changes.
You can modify the details on the Megaport side including the connection name, rate limit, service level (invoice) reference, connection state, and contract terms. You can also modify the NAT Gateway connection details including interface IP address, NAT source IP address, BGP connections, enable BFD, and static routes.\
Once submitted, the changes take effect in a few minutes.
**To add BGP details to a Megaport Internet connection**
You can add BGP information to the Megaport Internet connection when the connection is live.\
For more information, see [Enabling BGP](/megaport-internet/routing#enableBGP).
## Helpful references
* [Creating a Megaport Internet Connection for an MCR](/megaport-internet/mcr)
* [Creating a Megaport Internet Connection for an MVE](/megaport-internet/mve)
* [Creating a Megaport Internet Connection for a Port](/megaport-internet/port)
* [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing)
* [Megaport Internet Routing Guide](/megaport-internet/routing)
* [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring)
* [Terminating a Megaport Internet Connection](/megaport-internet/terminating-connection)
* [Troubleshooting Megaport Internet Connectivity](/troubleshooting/mic/megaport-internet)
* [Understanding the Services Page](/portal-admin/services-page)
* [VXC, Megaport Internet, and IX Billing](/finance/billing-details)
# Creating a Megaport Internet Connection for a Port
Source: https://docs.megaport.com/megaport-internet/port
This help topic describes how to create a Megaport Internet connection for a Port in the Megaport Portal.
This topic describes how to create a Megaport Internet connection for a Port in the Megaport network.
With a Port configured, you can create a Megaport Internet connection. You can create a Megaport Internet connection for a Port, for example, as your main or back-up internet connection, or to establish an internet connection for seasonal needs or for specific time-bound projects.
For more information about Megaport Internet connections, see [Megaport Internet Overview](/megaport-internet).
## Creating a Megaport Internet connection
You can create a Megaport Internet connection for a Port during Port provisioning or any time after it has been provisioned.
**To create a Megaport Internet connection**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.
If you haven't already created a Port, see [Creating a Port](/connections/creating-port).
2. If this is the first connection for the Port, click the **Megaport Internet** tile. The tile is a shortcut to the configuration page. Alternatively, click **+Connection**.
Port details including the speed, location, and diversity zone are displayed.
The diversity zone for an A-End service is visible after the service is deployed and available. The A-End diversity zone is also visible when ordering a diverse pair of Ports. When ordering a single Port, you will not see the diversity zone until it is deployed, and not at all if the location does not support diversity.
3. Click **Megaport Internet**.\
Port details including name, location, diversity zone, and latency are displayed.
4. Select the destination Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere in the same country as the originating Port.\
You can filter by diversity zone, or select to view all.
5. Click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged**. This selection removes the VLAN tagging for this connection and it will be configured without a VLAN ID.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next** to review the Megaport Internet connection summary, including price.
8. Click **Add VXC** to save the connection.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
When the Megaport Internet connection is deployed, you can view it in the Portal Services page.
## Updating a Megaport Internet connection
You can update a Megaport Internet connection for a Port any time after it has been created.
**To edit a Megaport Internet connection**
* Click the gear icon next to the connection in the Megaport Portal to make changes.
You can modify the details on the Megaport side including the connection name, rate limit, VLAN ID, service level (invoice) reference, connection state, and contract terms. Once submitted, the changes take effect in a few minutes.
**To add BGP details to a Megaport Internet connection**
You can add BGP information to the Megaport Internet connection when the connection is live.\
For more information, see [Enabling BGP](/megaport-internet/routing#enableBGP).
## Helpful references
* [Creating a Megaport Internet Connection for an MCR](/megaport-internet/mcr)
* [Creating a Megaport Internet Connection for an MVE](/megaport-internet/mve)
* [Creating a Megaport Internet Connection for a NAT Gateway](/megaport-internet/nat-gateway)
* [Creating a Megaport Internet Connection from a Port with the API](/api/api-mic)
* [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing)
* [Megaport Internet Routing Guide](/megaport-internet/routing)
* [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring)
* [Terminating a Megaport Internet Connection](/megaport-internet/terminating-connection)
* [Troubleshooting Megaport Internet Connectivity](/troubleshooting/mic/megaport-internet)
* [Understanding the Services Page](/portal-admin/services-page)
* [VXC, Megaport Internet, and IX Billing ](/finance/billing-details)
# Megaport Internet Routing Guide
Source: https://docs.megaport.com/megaport-internet/routing
This help topic describes how to configure BGP routing for a Megaport Internet connection.
This topic describes standard Megaport Internet configuration and how you can configure on Megaport Internet connections.
is available for , , and in selected countries. For the latest information on Megaport Internet availability, see [Locations available](/megaport-internet#locations). You can access the product by ordering a Megaport Internet connection to a Megaport internet router.
Multiple diversity zones are available in all metros where Megaport Internet is available. For maximum resiliency, connect to both zones by matching red to red and blue to blue. Additional resiliency is available by connecting to Megaport Internet in an additional nearby metro. For more information, see [Port Diversity](/connections/port-diversity), [MCR Diversity](/mcr/mcr-mve-diversity), and [MVE Diversity](/mve/mcr-mve-diversity).
All Megaport Internet connections are assigned IPv4 and IPv6 addresses as standard and configured as follows:
* /31 Point-to-point IPv4 network
* /64 Point-to-point IPv6 network
* is enabled for IPv4 and will permanently offer the same static IPv4 address.
* IPv6 router advertisements are enabled for SLAAC-capable IPv6 clients.
* It is not required to use the dynamic address assignment methods. The address information is also available in the Megaport Portal and you can configure your equipment with static addresses from the assigned range.
* Megaport adheres to [BCP 38](https://www.rfc-editor.org/rfc/rfc2827.txt). Packets sent to Megaport must have a valid source address in the assigned IPv4 or IPv6 ranges.
* To protect against abuse of Megaport IP address space for the sending of spam, Megaport filters outgoing connections to TCP port 25 when the source address is a Megaport-owned IP address. Customer-supplied address space is not filtered. Exceptions for specific IP addresses can be made upon request, with valid justification.
## IP Address blocks
IP Address is available as a standalone product, independent of Megaport Internet. You can order an IP Address block on its own or when managing a Megaport Internet connection, then link the block to one or more Megaport Internet connections in the same metro.
For more information, see [IP Address Overview](/ip-address).
Megaport-assigned IP address space must be advertised only on Megaport Internet services. Advertising these networks to other Megaport services or third-party providers is forbidden.
## Enabling BGP
You can request BGP on new and existing Megaport Internet VXCs. With BGP enabled:
* Customers might advertise Megaport assigned IP blocks or their own provider independent IP addresses (see [BGP filtering](#BGPfiltering)).
* Megaport configures an IPv4 and IPv6 BGP neighbor.
* Megaport uses the first IP address and configures the BGP neighbor as the second IP address in the point-to-point network.
* You can optionally provide a BGP password.
* Source address filtering permits only Megaport-assigned IP addresses and prefixes that customers have provided for advertisement over BGP.
* Megaport sets a minimum BGP hold timer of 20 seconds. A BGP connection will not establish if you configure a value lower than this on your router.
is not currently supported with Megaport Internet.
### Requesting BGP on Megaport Internet connections
You can enable BGP configuration details on a Megaport Internet connection when it is live. To add BGP details, edit the Megaport Internet connection and provide the BGP details.
To configure BGP for your Megaport Internet connection, you must provide these details:
* Customer
* BGP Password (optional) -- You can add a password for your BGP entry, or you can leave this field blank.
* Prefixes (optional) -- A list of publicly assigned IPv4 or IPv6 networks to be advertised.
* AS-SET -- A list of ASNs used to define routing policies and filter prefixes from multiple ASNs.
BGP requests will be reviewed by Megaport Customer Support before being implemented.
**To request BGP settings on a Megaport Internet connection**
The BGP settings can be added to the Megaport Internet connection when the service has been provisioned.
You must have at least Technical Admin privileges to perform this action. For more information, see [Managing User Roles](/portal-admin/user-management/roles).
1. In the Megaport Portal, go to the **Services** page and find the Megaport Internet connection that you want to update.
2. Click the gear icon next to the connection.
3. Click **Megaport Internet**.
The image below shows the edit Connection Details page for a Megaport Internet connection on a Port. For a Megaport Internet connection on an MCR, the Megaport Internet entry will be in a different position.
4. Click **Update BGP Connection**.
5. Enter these details:
* **Customer ASN**
* Must be a valid public or private BGP ASN.
* Mandatory if entering BGP details.
* For more information, see [Using private AS numbers](#privateasn).
* **BGP Password** (optional)
* The allowed password length is from 1 to 25 characters.
* The password can include any of these characters:
* a-z
* A-Z
* 0-9
* ! @ # . \$ % ^ & \* + = - \_
* **Route Table**
* Select your routing preference from the drop-down list.
* Ensure that valid route objects are created in the appropriate Regional Internet Registry (RIR) or Routing Assets Database (RADb) for all advertised networks.
* Your selection determines how routes are advertised.
* Each option advertises an increasing number of routes.
* For more information, see [Advertised routes](#advertisedroutes).
* **Prefixes** (optional)
* A list of publicly assigned IPv4 or IPv6 networks to be advertised
* The list must be entered as a comma-separated list.\
For example, 192.0.2.0/24, 192.0.2.0/30.
* For more information, see [BGP filtering](#BGPfiltering).
* **AS-SET** (optional)
* A list of ASNs used to define routing policies and filter prefixes from multiple ASNs.
* Multiline input required.
* Entries must be separated by a comma.
* **Additional Remarks** (optional)
* Add any additional information or justification.
6. Click **Update BGP Connection** to submit your changes.
Megaport Customer Support will review the request. If everything is in order, you will receive an email with the next-step instructions.
If there are any issues with the request, Megaport Customer Support will contact you.
## BGP filtering
You can optionally provide a list of IPv4 and IPv6 prefixes that you want to advertise.
* Prefixes must be publicly assigned addresses and owned by the customer, or the customer must provide an LOA from the owner authorizing their use.
* Prefix length must be between /12 and /24 for IPv4 prefixes.
* Prefix length must be between /24 and /48 for IPv6 prefixes.
Megaport will filter out any advertised prefixes not listed.
Megaport performs filtering. Invalid routes are filtered. For more information, see [RPKI](https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/).
Megaport automatically permits longer prefixes down to /32 for IPv4 and /128 for IPv6 in our filters. This allows you to share a single /24 (IPv4) or /48 (IPv6) route across multiple Megaport Internet services within the same metro area.
Prefixes longer than /24 and /48 are not exported to external neighbors.
The maximum number of BGP prefixes accepted is 4x the number of registered prefixes to allow for limited traffic engineering using more specific routes.
Megaport will not install routes from transit or peering sources that fall within a customer’s advertised prefixes. All traffic destined for addresses within a customer’s advertised prefix range will be routed via the customer’s Megaport Internet service, even if a more specific route exists via an external path.
Megaport sets a high local-preference on customer BGP routes.
Route objects must be created with the relevant Regional Internet Registry (RIR) or Routing Assets Database (RADb) for all networks, regardless of whether the network uses private or public ASNs. For statically routed networks or private ASNs, route objects must specify the origin of **AS49915**.
Upstream filters can take up to 48 hours to update after the service has been configured. During this period, newly created or modified routes might not propagate to the internet completely.
## Advertised routes
You can choose from four options, with an increasing number of routes. If you do not specify your preferred option, Megaport will only advertise a default route.
Megaport always advertises a default route with all routing options.
Routing options:
* **Default Route** -- A locally originated default route (one route).
* **Customer Routers** -- In addition to the above, this includes the routes of Megaport customers.
* **Customer and Peer Routes** -- In addition to the above, this includes the routes of Megaport peers.
* **Full Routes** -- In addition to the above, this includes a complete internet routing table (>900,000 routes).
Megaport internal communities and private communities are removed from outbound route announcements.
## Traffic engineering communities
You can set these communities to influence the advertisement of your routes to other neighbors.\
TE communities are stripped on egress.
| Large Community | Standard Community | Action |
| - | - | - |
| 49915:65000:0 | 65000:0 | Do not export |
| 49915:65000:ASN | 65000:ASN | Do not export to ASN |
| 49915:65001:0 | 65001:0 | Prepend once |
| 49915:65001:ASN | 65001:ASN | Prepend once to ASN |
| 49915:65002:0 | 65002:0 | Prepend twice |
| 49915:65002:ASN | 65002:ASN | Prepend twice to ASN |
| 49915:65003:0 | 65003:0 | Prepend three times |
| 49915:65003:ASN | 65003:ASN | Prepend three times to ASN |
| | 65535:65284 | nopeer Do not advertise to any bilateral or route-server peers |
## Remote Triggered Black Hole
allows you to drop traffic to a host under attack at the Megaport edge, before it reaches your Megaport Internet connection.
Announce a host route tagged with one of these communities from the device that BGP peers with Megaport, such as your own router or firewall. Megaport discards traffic to that address, so you do not need to configure a black hole route on your network. Withdraw the announcement to restore normal forwarding. You do not need to take any action in the Megaport Portal to activate or withdraw a black hole route.
| Community | Action |
| - | - |
| 49915:666 | Black hole the announced host route. |
| 65535:666 | Black hole the announced host route. |
Megaport accepts a black hole announcement only when:
* The route has a /32 (IPv4) or /128 (IPv6) prefix.
* The route is contained within a prefix you are already authorized to advertise on the connection (see [BGP filtering](#BGPfiltering)).
Accepted black hole routes count toward the maximum number of BGP prefixes accepted on your connection (see [BGP filtering](#BGPfiltering)).
For more information about black hole communities, see [RFC 7999 - BLACKHOLE Community](https://www.rfc-editor.org/rfc/rfc7999.html).
## Using private AS numbers
Megaport supports BGP for customers that do not have a public AS number, using private AS numbers.
You can choose your ASN from either the 2-byte or 4-byte private ranges.
All routes Megaport advertises upstream will have private AS numbers stripped from the AS path. This might result in Megaport appearing to be the origin of the prefix. If the network owner has published RPKI ROA records, you might need to create additional ROAs permitting Megaport AS49915 to advertise the route.
## Helpful references
* [Contacting Support](/support/contact)
* [Creating a Megaport Internet Connection for a Port](/megaport-internet/port)
* [Creating a Megaport Internet Connection for an MCR](/megaport-internet/mcr)
* [Creating a Megaport Internet Connection for an MVE](/megaport-internet/mve)
* [Creating a Megaport Internet Connection for a NAT Gateway](/megaport-internet/nat-gateway)
* [Creating a Megaport Internet Connection from a Port with the API](/api/api-mic)
* [MCR Diversity](/mcr/mcr-mve-diversity)
* [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring)
* [MVE Diversity](/mve/mcr-mve-diversity)
* [Port Diversity](/connections/port-diversity)
* [Terminating a Megaport Internet Connection](/megaport-internet/terminating-connection)
* [Troubleshooting Megaport Internet Connectivity](/troubleshooting/mic/megaport-internet)
# Connecting MVEs Integrated with Aruba EdgeConnect SD-WAN
Source: https://docs.megaport.com/mve/aruba/connect-mve-to-mve
This help topic describes how to connect two Megaport Virtual Edges (MVEs) integrated with Aruba EdgeConnect SD-WAN.
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with Aruba EdgeConnect SD-WAN to another MVE.
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer/SD-WAN partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [Creating an MVE in Aruba](/mve/aruba/creating).
## Creating a VXC between two MVEs
A private VXC deployment between two MVEs integrated with Aruba starts in the Megaport Portal. To complete the configuration, you use the Aruba Orchestrator console.
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and click **+Connection** next to the originating A-End MVE.
2. Select Private VXC.
3. Select the destination B-End MVE and location.\
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `LA MVE 2 to Dallas MVE 4`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. Consult Aruba’s documentation for more information.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **vNIC selection** -- Depending on the definition of the MVEs you are using, you might have to specify A-End and B-End vNICs.
* **A-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
* **B-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
For more information about vNIC selection when connecting MVEs with different services, see [Types of vNIC Connections](/mve/vnic-connections).
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.\
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. 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 through the B-End VLAN.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Click **Add VXC** to move this configuration to your cart.
8. Repeat these steps to provision any additional VXCs.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs in Aruba Orchestrator.
The next procedure configures IP connectivity with BGP, providing just one solution out of many. Consult your SD-WAN vendor documentation for specific network design and configuration options before configuring interfaces for the MVEs.
## Configuring the A-End MVE in Orchestrator
After you create the VXC between your MVEs, you need to configure it in Orchestrator. This involves configuring LAN interfaces.
**To configure the A-End appliance**
1. Log in to your enterprise Aruba Orchestrator system.
2. Choose Configuration > Discovery | Discovered Appliances or click **Appliances Discovered** on the upper right of the screen.
3. Select the A-End MVE.
4. Go to the System menu and choose Interface.
5. Choose Configuration > Networking | Deployment.
6. Locate the appliance by the hostname and click the Edit (pencil) icon.
7. Add a new LAN side interface: Click **+Add** next to LAN Interfaces.
If this is the first LAN side service connection, click **+Add**. If you already have a LAN interface, click **+IP** under the Interface drop-down list to add a new configuration.
Here is a screen with sample values.
8. In the Interface drop-down menu, choose *wan0*.
9. In the **VLAN** field, enter the A-End VLAN value for this connection from the Megaport Portal.\
Click the Details icon for the connection in the Megaport Portal to find this value. Note that it might be different from the B-End VLAN ID.
10. (Optional) Select a preconfigured Label or select None.
11. In the **IP/Mask** field, enter the A-End interface IP Address and subnet mask as required for your network.
12. For the Next Hop, enter the B-End IP address.
13. Specify in and out bandwidth values.\
The bandwidth must be equal to or less than the MVE bandwidth limit.
14. Click **Apply**.
15. If prompted, reboot the appliance.\
At this point, the A-End interface is created. Once the device is reachable from Orchestrator, you can configure a Border Gateway Protocol (BGP) session.
To set up the MVEs to exchange routing information, follow the steps in [To configure BGP in Orchestrator](#configureBGP).
## Configuring the B-End MVE in Orchestrator
1. Log in to your enterprise Aruba Orchestrator system.
2. Choose Configuration > Discovery | Discovered Appliances or click **Appliances Discovered** on the upper right of the screen.
3. Select the B-End MVE.
4. Go to the System menu and choose Interface.
5. Choose Configuration > Networking | Deployment.
6. Locate the appliance by the hostname and click the Edit (pencil) icon.
7. Add a new LAN side Interface: Click **+Add** next to LAN Interfaces.
If this is the first LAN side service connection, click **+Add**. If you already have a LAN interface, click **+IP** under the Interface drop-down list to add a new configuration.
Here is a screen with sample values.
8. In the Interface drop-down menu, choose *wan0*.
9. In the **VLAN** field, enter the B-End VLAN value for this connection from the Megaport Portal.\
Click the Details icon for the connection in the Megaport Portal to find this value. Note that it might be different from the A-End VLAN ID.
10. (Optional) Select a preconfigured Label or select None.
11. In the **IP/Mask** field, enter the B-End interface IP Address and subnet mask as required for your network.\
This value is the Customer Address from the AWS connection details in the Portal.
12. For the Next Hop, enter the A-End IP address.
13. Specify in and out bandwidth values.\
The bandwidth must be equal to or less than the MVE bandwidth limit.
14. Click **Apply**.
15. If prompted, reboot the appliance.\
A reboot is required only when adding the first LAN interface, as the system switches the appliance from server mode to router mode.
At this point, the B-End interface is created. The next step is to optionally create a Border Gateway Protocol (BGP) session.
**To configure a BGP neighbor** (optional)
1. In Orchestrator, go to Configuration > Networking | BGP.
2. Click the Edit (pencil) icon for the appliance.
3. Move the slider to **Enable BGP**.
4. Provide the local AS number.\
This is the Customer ASN (your local MVE), collected in step 1.
5. In the **Router ID** field, enter a system IP as required by your network design.\
You can use any IP address on the MVE, such as the loopback 0 IP specified during the initial acceptance of the appliance, the interface IP on the MVE side of the VXC, or the transit IP address.
6. In the BGP Peers section, click **Add** and provide the following information:
* **Peer IP** -- Enter the neighbor/peer IP address.
* **Local Interface** -- Choose the associated LAN interface (the interface is in the format *wan0.\{VLAN ID}*).
* **Peer ASN** -- Enter the peer ASN.
* **Peer Type** -- Choose Branch.
* **Enable Password** -- If required, select this and then enter and confirm your MD5 password.
7. Click **Add**.
8. Click **Apply**.\
It takes several seconds for the configuration to be pushed to the appliance. Click the refresh icon to update the data from the appliance.
When successful, the Peer State indicates *Established*:
## Validating your connection
You can review connection details, including the connection state, from the CLI with these commands:
* `show interface wan0.` -- Displays configuration details and current status for the appliances.
* `show bgp neighbors` or `show bgp summary` -- Displays configuration details and current status for the BGP neighbors.
**To start a CLI session from Orchestrator**
1. In Orchestrator, use the mouse to hover over the appliance and click the Appliance Menu icon to the right of the appliance name.
2. Choose CLI Session from the menu.
3. Enter **enable** mode to use the recommended CLI commands to display configuration details.
# Creating an MVE Integrated with Aruba Manually
Source: https://docs.megaport.com/mve/aruba/creating-mve-manual
This help topic describes how to manually create and configure a Megaport Virtual Edge (MVE) with Aruba EdgeConnect SD-WAN.
This topic describes how to manually create and configure a Megaport Virtual Edge (MVE) with Aruba EdgeConnect SD-WAN. Before you begin, you need user accounts with ordering permissions that provide access to the Megaport Portal and to Aruba.
For more information about setting up a Megaport account, see [Creating an Account](/setting-up/registering).
For more information about creating an MVE integrated with Aruba using a system tag, see [Creating an MVE Using a System Tag](/mve/aruba/creating-mve-system-tag).
Aruba provides documentation for their SD-WAN product, including Orchestrator and cloud connections, at the [Aruba Documentation Library](https://arubanetworking.hpe.com/techdocs/sdwan/).
## Basic steps
This section provides an overview of the configuration steps in Aruba Orchestrator and the Megaport Portal. The basic steps are:
* Obtain a license from Aruba.
* Create the Aruba MVE in the Megaport Portal.
* View the MVE public IP address assignment in the Megaport Portal.
* Configure the Aruba EdgeConnect (EC-V) in Aruba Orchestrator.
* Apply the license to the EC-V.
The next sections provide details.
## Licensing
Before you create an MVE in the Megaport Portal, you need to buy a valid EdgeConnect SD-WAN license from Aruba. All licenses are managed by the Aruba Cloud Portal.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/aruba/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also typically create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Aruba EC-V**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Aruba.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Aruba-specific settings:
* **Orchestrator Account Name** -- Enter the Account Name from Aruba Orchestrator. To view your Account Name, log in to Orchestrator and choose Orchestrator > Licensing | Cloud Portal.
* **Account Key** -- Enter the Account Key from Aruba Orchestrator. The key is linked to the Account Name. To view your Account Key, log in to Orchestrator and choose Orchestrator > Licensing | Cloud Portal. If a key isn't visible in Orchestrator, click **Generate Account Key**.
* **System Tag** (optional) -- Aruba Orchestrator System Tags and preconfiguration templates register the EC-V with the Cloud Portal and Orchestrator, and enable Orchestrator to automatically accept and configure newly discovered EC-V appliances. Enter the Appliance/System Tag you specified when you created the preconfiguration template in Orchestrator.
* **Virtual Interfaces (vNICs)** -- Aruba EC-V requires a minimum of two vNICs. To change a vNIC name, type over the default text. You can also change vNIC names later, after the MVE has been deployed.
You can add a total of five vNICs to the MVE. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Enter a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with Aruba SD-WAN.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select **vNIC-0** for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up an Aruba EdgeConnect (EC-V).
## Viewing the MVE
You can view the MVE in Orchestrator and the Megaport Portal.
### Viewing in Orchestrator
The MVE is now managed via Aruba Orchestrator and you can view it in the list of Discovered Devices.
**To view an MVE in Orchestrator**
1. Log in to Orchestrator.
2. Choose Orchestrator > Configuration > Deployment.
3. Click the Edit icon next to the appliance.
As you add to your network, you can clone and modify the template for reuse with other EC-V deployments, assigning each EC-V a unique system tag.
### Viewing in the Megaport Portal
After creating the MVE, you can view it in the Megaport Portal on the Services page. You can also view the public IP addresses assigned.
**To view an MVE in the Megaport Portal**
* Go to the **Services** page.
The Megaport Internet icon differs from a standard VXC icon in the Megaport Portal, as shown in the image.
For more information about the Services page, see [Understanding the Services Page](/portal-admin/services-page).
#### Updating the Megaport Internet connection
* Click the gear icon next to the Megaport Internet connection in the Megaport Portal to make changes.
You can modify the Megaport Internet connection details including the connection name, rate limit, VLAN ID, invoice reference, connection state, and contract terms. Once submitted, those changes take effect in a few minutes.
To delete the Megaport Internet connection, click the trash icon. For more information, see [Terminating a Megaport Internet Connection](/megaport-internet/terminating-connection).
To lock or unlock the Megaport Internet connection, click the padlock icon.
**To view the public IP addresses assigned to the MVE**
1. Click the gear icon next to the Megaport Internet connection.\
The Connection Configuration screen appears. From here, you can modify any of the Megaport Internet connection details.
2. Select the **Details** tab.
3. Locate the public IP address (IPv4 or IPv6).\
These are the public IP addresses assigned to the MVE.
## Approve and upgrade the MVE EC-V appliance
After you create the new EC-V appliance, it will be visible under *Discovered Appliances* in Aruba Orchestrator. Next, you will accept it as a new appliance and upgrade its software to version 9.1.0.0\_91199.
**To approve and upgrade the new EC-V appliance**
Before Aruba Orchestrator adds the EC-V to its list of managed appliances, you need to manually approve it.
1. Log in to your enterprise Aruba Orchestrator system.
2. Choose Configuration > Discovery | Discovered Appliances or click **Appliances Discovered** on the upper right of the screen.\
You will see a new device awaiting approval.
3. Click **Approve** next to the new device.\
The Upgrade Appliance screen appears. MVE requires that you upgrade Aruba Orchestrator to a minimum of version 9 or later.
4. Choose a 9.x software version from the drop-down list that is compatible with your version of Orchestrator.
5. Click **Upgrade & Reboot Appliance**.\
The upgrade and reboot process takes approximately 5 to 10 minutes.
6. Click **Close** when the upgrade is complete.
7. Click **Refresh Discovery Information** in the Discovered Devices screen to verify the new software version.
8. Click **Approve**.\
The Upgrade Appliance screen shows that no upgrades are available, confirming that Orchestrator is up to date.
9. Click **Skip**.
10. Click **Run Manual Configuration Wizard** in the Apply Appliance Preconfiguration screen.\
You can also select a preconfiguration template, if available.
11. Provide the appliance details:
* **Hostname** -- Megaport assigns a hostname by default, however this is a free text field allowing you to assign an easily identifiable name for this appliance.
* **Group** -- As required for your network, specify a group name for the appliance.
* **Admin Password** -- Specify and confirm a secure password.
* **Serial Number** -- This number is assigned by default.\
The rest of the fields are optional.
12. Click **Next**.
13. Select a profile in the Deployment Profile drop-down list, or click **Next** to skip.
14. (Optional) Click **Add** to add a loopback interface and IP address that meet your network requirements, or click **Next**.
15. As required for your network, select **Use SD-WAN Fabric Learned Routes** and/or **Automatically include local subnets** and click **Next**.
16. As required for your network, select or deselect the appropriate options under *Add Business Intent Overlays to this Site* and *Select Template Groups to be applied to this Site*.\
Note that improper configuration of overlays and/or labels can result in Orchestrator communication errors. For more information, see the Aruba documentation.
17. Click **Apply**.\
The Appliance Wizard applies the configuration updates to the MVE EC-V appliance.
18. Click **Close**.
The appliance is now managed via Aruba Orchestrator and you can view it in the list of Discovered Devices.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/aruba/creating-mve-vxc).
# Creating an MVE Integrated with Aruba Using a System Tag
Source: https://docs.megaport.com/mve/aruba/creating-mve-system-tag
This help topic describes how to create and configure a Megaport Virtual Edge (MVE) with Aruba EdgeConnect SD-WAN using a system tag.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Aruba EdgeConnect SD-WAN using a system tag.
System tag configuration simplifies MVE deployment by automating several required configuration tasks. This method automatically performs these tasks:
* Enables Aruba Orchestrator to approve and configure the newly discovered EC-V without user intervention.
* Upgrades Orchestrator to version 9 or later.
* Registers the MVE with the Cloud Portal and Orchestrator.
* Assigns the appropriate group memberships and roles to the MVE.
* Applies the MVE configuration using your custom deployment settings.
* Spins up an EdgeConnect (EC-V).
In Orchestrator, a Megaport MVE is called an Aruba EdgeConnect (EC-V). The terms EC-V and MVE are used interchangeably in this topic.
Before you begin, you need user accounts with ordering permissions that provide access to the Megaport Portal and to Aruba.
For more information about setting up a Megaport account, see [Creating an Account](/setting-up/registering).
For more information about creating an MVE integrated with Aruba manually, see [Creating an MVE Integrated with Aruba Manually](/mve/aruba/creating-mve-manual).
Aruba provides documentation for their SD-WAN product, including Orchestrator and cloud connections, at the [Aruba Documentation Library](https://arubanetworking.hpe.com/techdocs/sdwan/).
## Basic steps
The basic configuration steps using a system tag are:
* Obtain a license from Aruba.
* Create a preconfiguration template in Aruba Orchestrator. The template includes a system tag.
* Create the Aruba MVE in the Megaport Portal, assigning the system tag to the MVE. Orchestrator configures the MVE using the deployment parameters specified in the template.
The next sections provide details.
## Licensing
Before you create an MVE in the Megaport Portal, you need to buy a valid EdgeConnect SD-WAN license from Aruba. All licenses are managed by the Aruba Cloud Portal.
## Creating a preconfiguration template
Aruba Orchestrator system tags identify a unique preconfiguration template used to register the MVE with the Cloud Portal and Orchestrator, and enable Orchestrator to automatically accept and configure the newly discovered MVE appliance.
**To preconfigure a template**
1. Log in to Aruba Orchestrator.
2. Choose Configuration > Overlays & Security > Discovery > Preconfiguration.
3. Click **New**.
4. Name the template.
5. Enable Auto Approve when Discovered.
6. Enter the Appliance/System Tag name to use as the unique identifier to associate with the MVE. For example, `aruba-test-1`. Make a note of the system tag for use in the Megaport Portal later. Orchestrator will match this tag with the MVE during discovery.
7. Enter any deployment-specific parameters by modifying the script values on the right side of the page. The example script applies these deployment settings automatically:
* Upgrades the appliance to the specified 9.*x* software version.
* Assigns appropriate roles and group memberships to the appliance.
* Converts the appliance to inline router mode.
* Creates a LAN-side placeholder interface.
* Assigns WAN-side bandwidth calculations based on the MVE sizing.
* Enables stateful source NAT (SNAT) firewall settings on the WAN public-facing interface.
8. Delete any unused parameters.
9. Click **Validate** to test the configuration.
10. Click **Save**.
Once you have saved the template, you are ready to create the MVE in the Megaport Portal.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/aruba/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also typically create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Aruba EC-V**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Aruba.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Aruba-specific settings:
* **Orchestrator Account Name** -- Enter the Account Name from Aruba Orchestrator. To view your Account Name, log in to Orchestrator and choose Orchestrator > Licensing | Cloud Portal.
* **Account Key** -- Enter the Account Key from Aruba Orchestrator. The key is linked to the Account Name. To view your Account Key, log in to Orchestrator and choose Orchestrator > Licensing | Cloud Portal. If a key isn't visible in Orchestrator, click **Generate Account Key**.
* **System Tag** -- Aruba Orchestrator System Tags and preconfiguration templates register the EC-V with the Cloud Portal and Orchestrator, and enable Orchestrator to automatically accept and configure newly discovered EC-V appliances. Enter the Appliance/System Tag you specified when you created the preconfiguration template in Orchestrator.
* **Virtual Interfaces (vNICs)** -- Aruba EC-V requires a minimum of two vNICs. To change a vNIC name, type over the default text. You can also change vNIC names later, after the MVE has been deployed.
You can add a total of five vNICs to the MVE. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Enter a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with Aruba SD-WAN.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select **vNIC-0** for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up an Aruba EdgeConnect (EC-V).
## Viewing the MVE
You can view the MVE in Orchestrator and the Megaport Portal.
### Viewing in Orchestrator
The MVE is now managed via Aruba Orchestrator and you can view it in the list of Discovered Devices.
**To view an MVE in Orchestrator**
1. Log in to Orchestrator.
2. Choose Orchestrator > Configuration > Deployment.
3. Click the Edit icon next to the appliance.
As you add to your network, you can clone and modify the template for reuse with other EC-V deployments, assigning each EC-V a unique system tag.
### Viewing in the Megaport Portal
After creating the MVE, you can view it in the Megaport Portal on the Services page. You can also view the public IP addresses assigned.
**To view an MVE in the Megaport Portal**
* Go to the **Services** page.
The Megaport Internet icon differs from a standard VXC icon in the Megaport Portal, as shown in the image.
For more information about the Services page, see [Understanding the Services Page](/portal-admin/services-page).
#### Updating the Megaport Internet connection
* Click the gear icon next to the Megaport Internet connection in the Megaport Portal to make changes.
You can modify the Megaport Internet connection details including the connection name, rate limit, VLAN ID, invoice reference, connection state, and contract terms. Once submitted, those changes take effect in a few minutes.
To delete the Megaport Internet connection, click the trash icon. For more information, see [Terminating a Megaport Internet Connection](/megaport-internet/terminating-connection).
To lock or unlock the Megaport Internet connection, click the padlock icon.
**To view the public IP addresses assigned to the MVE**
1. Click the gear icon next to the Megaport Internet connection.\
The Connection Configuration screen appears. From here, you can modify any of the Megaport Internet connection details.
2. Select the **Details** tab.
3. Locate the Public IP address (IPv4 or IPv6).\
These are the public IP addresses assigned to the MVE.
If you have set Orchestrator to automatically approve and upgrade the EC-V appliance, you will see the EC-V under *Discovered Appliances*. If not, you need to manually approve and upgrade its software to version 9.1.0.0\_91199.
**To approve and upgrade the new EC-V appliance**
Before Aruba Orchestrator adds the EC-V to its list of managed appliances, you need to manually approve it.
1. Log in to your enterprise Aruba Orchestrator system.
2. Choose Configuration > Discovery | Discovered Appliances or click **Appliances Discovered** on the upper right of the screen.\
You will see a new device awaiting approval.
3. Click **Approve** next to the new device.\
The Upgrade Appliance screen appears. MVE requires that you upgrade Aruba Orchestrator to a minimum of version 9 or later.
4. Choose a 9.x software version from the drop-down list that is compatible with your version of Orchestrator.
5. Click **Upgrade & Reboot Appliance**.\
The upgrade and reboot process takes approximately 5 to 10 minutes.
6. Click **Close** when the upgrade is complete.
7. Click **Refresh Discovery Information** in the Discovered Devices screen to verify the new software version.
8. Click **Approve**.\
The Upgrade Appliance screen shows that no upgrades are available, confirming that Orchestrator is up to date.
9. Click **Skip**.
10. Click **Run Manual Configuration Wizard** in the Apply Appliance Preconfiguration screen.\
You can also select a preconfiguration template, if available.
11. Provide the appliance details:
* **Hostname** -- Megaport assigns a hostname by default, however this is a free text field allowing you to assign an easily identifiable name for this appliance.
* **Group** -- As required for your network, specify a group name for the appliance.
* **Admin Password** -- Specify and confirm a secure password.
* **Serial Number** -- This number is assigned by default.\
The rest of the fields are optional.
12. Click **Next**.
13. Select a profile in the Deployment Profile drop-down list, or click **Next** to skip.
14. (Optional) Click **Add** to add a loopback interface and IP address that meet your network requirements, or click **Next**.
15. As required for your network, select **Use SD-WAN Fabric Learned Routes** and/or **Automatically include local subnets** and click **Next**.
16. As required for your network, select or deselect the appropriate options under *Add Business Intent Overlays to this Site* and *Select Template Groups to be applied to this Site*.\
Note that improper configuration of overlays and/or labels can result in Orchestrator communication errors. For more information, see the Aruba documentation.
17. Click **Apply**.\
The Appliance Wizard applies the configuration updates to the MVE EC-V appliance.
18. Click **Close**.
The appliance is now managed via Aruba Orchestrator and you can view it in the list of Discovered Devices.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/aruba/creating-mve-vxc).
# Creating a VXC to an MVE Integrated with Aruba EC-V
Source: https://docs.megaport.com/mve/aruba/creating-mve-vxc
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE) integrated with Aruba EdgeConnect SD-WAN.
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with Aruba.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.\
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
For specific CSP configuration details:
* AWS Direct Connect -- See [Creating MVE Connections to AWS](/cloud/mve/aruba/aws).
* Azure Express Route -- See [Creating MVE Connections to Azure using ExpressRoute](/cloud/mve/aruba/azure).
* Google Cloud -- See [Creating MVE Connections to Google](/cloud/mve/aruba/google).
* Other cloud connections -- See [Creating MVE Connections to Generic Endpoints](/cloud/mve/aruba/generic).
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
For specific configuration details, see [Connecting MVE to MVE](/mve/aruba/connect-mve-to-mve).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/aruba/terminating-mve).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# Creating an MVE Integrated with Aruba Overview
Source: https://docs.megaport.com/mve/aruba/creating/index
This help topic provides an overview of configuration methods to create a Megaport Virtual Edge (MVE) with Aruba EdgeConnect SD-WAN.
This topic provides an overview of the configuration methods used to create an MVE integrated with Aruba.
You can configure the MVE using one of these methods:
* **Create a preconfigured appliance template in Aruba Orchestrator** -- In the Megaport Portal, you identify the MVE using the system tag associated with the template. Aruba automates the appliance approval and configuration process when using a system tag. This method eliminates the manual steps required to upgrade software, perform reboots, and apply device configurations. For more information, see [Creating an MVE Using an Aruba System Tag](/mve/aruba/creating-mve-system-tag).
* **Configure the MVE manually** -- Manually create and configure a Megaport Virtual Edge (MVE) with Aruba EdgeConnect SD-WAN. Before you begin, you need user accounts with ordering permissions that provide access to the Megaport Portal and to Aruba. For more information, see [Creating an MVE Integrated with Aruba Manually](/mve/aruba/creating-mve-manual).
# Planning Your Aruba EdgeConnect SD-WAN MVE Deployment
Source: https://docs.megaport.com/mve/aruba/plan-deployment
This help topic describes Aruba EdgeConnect SD-WAN deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
| **You Provide** | **Megaport Provides** |
| - | - |
| Internet connection from branch | Platform to host virtual SD-WAN appliances |
| SD-WAN vendor enabled at branch | Complete connection from a branch to any destination on the Megaport network and interoperation with other Megaport products and services |
| Customer premises equipment (CPE) installed in branch | Megaport Internet connection to terminate the tunnel between MVE and CPE at branch via internet |
| SD-WAN software license to use on Megaport SDN | Access to the Megaport ecosystem |
## Deployment considerations
This section provides an overview of the MVE deployment options and features.
For more information, see the [Aruba Documentation Library](https://arubanetworking.hpe.com/techdocs/sdwan/).
### SD-WAN vendors
MVE is integrated with Aruba SD-WAN, which uses the Aruba Orchestrator console to create the private overlay network.
For information about all supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Aruba EC-V**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* You can provision another MVE instance, add it to your SD-WAN overlay network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, add it to your SD-WAN overlay network, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### Security
MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN. CSP-hosted instances of partner SD-WAN products route critical traffic across the Megaport SDN, reducing internet dependence. Traffic remains encrypted and under your policy control while traveling across the Megaport SDN, to or from, MVE.
### Licensing
You bring your own Aruba EdgeConnect SD-WAN license for use with MVE. It is your responsibility to have the appropriate licenses for the SD-WAN endpoints created on the Megaport network.
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
### vNICs
Each MVE can have up to five vNICs. Aruba EC-V requires a minimum of two vNICs, and you can add up to three more for a total of five.
Before specifying the number of vNICs on your MVE:
* Be aware that the number of vNICs cannot be changed after an MVE has been ordered. Decide in advance how many vNICs to specify when you create the MVE.
* Consult your service provider to make sure that functionality won't be affected if you add a vNIC.
If you need to change the number of vNICs after an MVE has been ordered, you will have to cancel and re-order the MVE.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
# Terminating an MVE
Source: https://docs.megaport.com/mve/aruba/terminating-mve
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window appears, displaying a list of services connected to the MVE. Early termination fees are shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use your SD-WAN management console to delete the MVE.
# Connecting MVEs Integrated with Aviatrix Secure Edge
Source: https://docs.megaport.com/mve/aviatrix/connect-mve-to-mve
This help topic describes how to connect two Megaport Virtual Edges (MVEs) integrated with Aviatrix Secure Edge.
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with Aviatrix Secure Edge to another MVE.
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer / partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [Creating an MVE Integrated with Aviatrix](/mve/aviatrix/creating-mve-aviatrix).
## Creating a VXC between two MVEs
A private VXC deployment between two MVEs integrated with Aviatrix Secure Edge starts in the Megaport Portal. To complete the configuration, you use the Aviatrix console.
**To create a VXC**
1. In the Megaport Portal, go to the
**Services** page and click **+Connection** next to the originating A-End MVE.
2. Select Private VXC.
3. Select the destination B-End MVE and location.\
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `Dallas MVE 4 to LA MVE 2`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. For more information, see the Aviatrix Secure Edge documentation.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **vNIC selection** -- Depending on the definition of the MVEs you are using, you might have to specify A-End and B-End vNICs.
* **A-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
* **B-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
For more information about vNIC selection when connecting MVEs with different services, see [Types of vNIC Connections](/mve/vnic-connections).
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.\
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. 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 through the B-End VLAN.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Click **Add VXC** to move this configuration to your cart.
8. Repeat these steps to provision any additional VXCs.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs on the Aviatrix Secure Edge side. For more information about specific network design and configuration options before configuring interfaces for the MVEs, see the [Aviatrix Documentation](https://docs.aviatrix.com/documentation/latest/building-your-network/edge-spoke-workflow-megaport.html).
# Creating an MVE Integrated with Aviatrix
Source: https://docs.megaport.com/mve/aviatrix/creating-mve-aviatrix
This help topic describes how to create and configure Megaport Virtual Edge (MVE) with Aviatrix.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Aviatrix.
For information on the Aviatrix-specific settings, see [Aviatrix Secure Edge on Megaport Virtual Edge Deployment Workflow](https://docs.aviatrix.com/documentation/latest/building-your-network/edge-spoke-workflow-megaport.html).
## Basic steps
This section summarizes the configuration steps using the Megaport Portal. Detailed procedures follow this basic step summary.
The basic steps are:
* Obtain a license from Aviatrix.
* Create a cloud-init file in the Aviatrix portal.
* Create the Aviatrix MVE in the Megaport Portal.
* Ensure that the connection has been established on the Aviatrix portal.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/aviatrix/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also typically create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Aviatrix Secure Edge**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Aviatrix.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Aviatrix-specific settings:
* **Cloud-init File** -- Upload the cloud-init text file that you created in the Aviatrix portal. For more information, see [Aviatrix Secure Edge on Megaport Virtual Edge Deployment Workflow](https://docs.aviatrix.com/documentation/latest/building-your-network/edge-spoke-workflow-megaport.html).
The cloud-init file is not validated on the Megaport side. After the connection is made, you can check that the connection is active on the Aviatrix portal.
* **Virtual Interfaces (vNICs)** -- Each MVE for Aviatrix is configured with three vNICs by default. The vNICs are:\
0: eth0\
1: eth1\
2: eth2
To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed. An MVE can have a total of five vNICs, including those added by default. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Enter a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
We recommend adding five vNICs to allow maximum virtual connections on the Aviatrix Edge Gateway MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with the Aviatrix Controller.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select **vNIC-2 eth2** for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up an Aviatrix Secure Edge.
After provisioning, use the Aviatrix Controller and CoPilot portal to perform advanced configuration and management.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/aviatrix/creating-mve-vxc).
# Creating a VXC to an MVE Integrated with Aviatrix Secure Edge
Source: https://docs.megaport.com/mve/aviatrix/creating-mve-vxc
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE) integrated with Aviatrix Secure Edge.
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with Aviatrix.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.\
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
For specific CSP configuration details:
* AWS Direct Connect -- See [Creating MVE Connections to AWS](/cloud/mve/aviatrix/aws).
* Azure Express Route -- See [Creating MVE Connections to Azure using ExpressRoute](/cloud/mve/aviatrix/azure).
* Google Cloud -- See [Creating MVE Connections to Google](/cloud/mve/aviatrix/google).
* Other cloud connections -- See [Creating MVE Connections to Generic Endpoints](/cloud/mve/aviatrix/generic).
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
For specific configuration details, see [Connecting MVE to MVE](/mve/aviatrix/connect-mve-to-mve).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/aviatrix/terminating-mve).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# Aviatrix Secure Edge with Megaport Virtual Edge
Source: https://docs.megaport.com/mve/aviatrix/index
This help topic describes Aviatrix with Megaport MVE functionality.
The integration of Aviatrix with Megaport's MVE delivers secure, high-performance multicloud and hybrid cloud connectivity, allowing you to connect, secure, and easily manage your cloud environments.
Aviatrix Secure Edge creates the private overlay network and manages the network connections and network policies. You use the Megaport Portal to create and order the MVE and create and manage the Virtual Cross Connects (VXCs) to the cloud on-ramps and other services in the Megaport SDN. The Aviatrix Secure Edge fabric acts as the overlay, and the Megaport SDN acts as the underlay.
For more information, see [Aviatrix Secure Edge on Megaport's Global Network](https://aviatrix.com/aviatrix-and-megaport/).
The following diagram shows an example network implementation of Aviatrix Secure Edge features over the Megaport network.
# Planning Your Aviatrix Secure Edge Deployment
Source: https://docs.megaport.com/mve/aviatrix/plan-deployment
This help topic describes Aviatrix Secure Edge deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
| **You Provide** | **Megaport Provides** |
| - | - |
| Internet connection from branch | Platform to host virtual Secure Edge appliances |
| Secure Edge vendor enabled at branch | Complete connection from a branch to any destination on the Megaport network and interoperation with other Megaport products and services |
| Customer premises equipment (CPE) installed in branch | Megaport Internet connection to terminate the tunnel between MVE and CPE at branch via internet |
| Secure Edge software license to use on Megaport SDN | Access to the Megaport ecosystem |
## Deployment considerations
This section provides an overview of the MVE deployment options and features.
For information about the Aviatrix-specific settings, see [Aviatrix Secure Edge Deployment](https://docs.aviatrix.com/previous/documentation/latest/deploying-secure-networks/edge-index.html).
### Network and Security vendors
MVE is integrated with Aviatrix, which uses the Aviatrix Secure Edge console to create the private overlay network.
For information about all supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Aviatrix Secure Edge**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* You can provision another MVE instance, add it to your overlay network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, add it to your overlay network, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### Security
MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN. CSP-hosted instances of partner Secure Edge products route critical traffic across the Megaport SDN, reducing internet dependence. Traffic remains encrypted and under your policy control while traveling across the Megaport SDN, to or from, MVE.
### Licensing
Before you create an MVE in the Megaport Portal, you need user accounts with ordering permissions that provide access to the Megaport Portal. For more information, see [Creating an Account](/setting-up/registering).
In addition, you need a valid license from Aviatrix. For more information about obtaining an Aviatrix license, see [Getting Started](https://docs.aviatrix.com/documentation/latest/getting-started/index.html?expand=true) or ask your Aviatrix Sales Associate or Reseller.
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
### vNICs
Each MVE can have up to five vNICs. An MVE is created with one vNIC by default. You can add up to four more, making a total of five.
Before specifying the number of vNICs on your MVE:
* Be aware that the number of vNICs cannot be changed after an MVE has been ordered. Decide in advance how many vNICs to specify when you create the MVE.
* Consult your service provider to make sure that functionality won't be affected if you add a vNIC.
If you need to change the number of vNICs after an MVE has been ordered, you will have to cancel and re-order the MVE.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
# Terminating an MVE
Source: https://docs.megaport.com/mve/aviatrix/terminating-mve
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window appears, displaying a list of services connected to the MVE. Early termination fees are shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use your Secure Edge management console to delete the MVE.
# Connecting MVEs Integrated with Check Point
Source: https://docs.megaport.com/mve/checkpoint/connect-mve-to-mve
This help topic describes how to connect two Megaport Virtual Edges (MVEs) integrated with Check Point.
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with Check Point CloudGuard to another MVE.
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer / partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [Creating an MVE Integrated with Check Point](/mve/checkpoint/creating-mve-checkpoint).
## Creating a VXC between two MVEs
A private VXC deployment between two MVEs integrated with Check Point CloudGuard starts in the Megaport Portal. To complete the configuration, you use the Check Point SmartConsole.
**To create a VXC**
1. In the Megaport Portal, go to the
**Services** page and click **+Connection** next to the originating A-End MVE.
2. Select Private VXC.
3. Select the destination B-End MVE and location.\
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `Dallas MVE 4 to LA MVE 2`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. For more information, see the Check Point CloudGuard documentation.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **vNIC selection** -- Depending on the definition of the MVEs you are using, you might have to specify A-End and B-End vNICs.
* **A-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
* **B-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
For more information about vNIC selection when connecting MVEs with different services, see [Types of vNIC Connections](/mve/vnic-connections).
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.\
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. 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 through the B-End VLAN.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Click **Add VXC** to move this configuration to your cart.
8. Repeat these steps to provision any additional VXCs.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs on the Check Point CloudGuard side. For more information about specific network design and configuration options before configuring interfaces for the MVEs, see the [Check Point CloudGuard Documentation](https://support.checkpoint.com/results/sk/sk179752).
# Creating an MVE Integrated with Check Point
Source: https://docs.megaport.com/mve/checkpoint/creating-mve-checkpoint
This help topic describes how to create and configure Megaport Virtual Edge (MVE) with Check Point.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Check Point.
Check Point's architecture is different from many other firewall vendors.
Check Point uses a central Security Management Server (Policy Server) to manage and configure its Security Gateways, including MVEs. The Security Management Server defines security policies and distributes them to gateways, which then enforce those policies.
**Initial access and management**
* Use vNIC 0 for initial communication with the device.
* Configure vNIC 0 as untagged to allow first-time administrative login.
* Check Point firewalls disable Internet Control Message Protocol (ICMP) by default. You cannot use ping or other ICMP-based tools to verify connectivity immediately after deployment.
* After the MVE is live, log in using SSH or HTTPS.
**Policy and advanced configuration**
* Use Check Point Smart Console for advanced configuration and policy management. You must fully configure the Smart Console before you can create or publish firewall policies.
* Deploy a Management Gateway (Security Management Server) to define and distribute firewall policies. You can deploy the Management Gateway in any CSP environment.
For information about automating Check Point CloudGuard deployments, see [CloudGuard Network Security - How to configure cloud-init automation](https://support.checkpoint.com/results/sk/sk179752) and [How to provide user data in KVM with Configuration Drive](https://support.checkpoint.com/results/sk/sk180452).
## Basic steps
This section summarizes the configuration steps using the Megaport Portal. Detailed procedures follow this basic step summary.
The basic steps are:
* Obtain a license from Check Point.
* Create the Check Point MVE in the Megaport Portal. Check Point’s architecture is different from many other firewall vendors as it uses a central Security Management Server (Policy Server) to manage and configure its Security Gateways.
* Ensure that the connection has been established on the Check Point portal.
## Administrative access to MVE
You connect your MVE through a public/private SSH key pair to establish a secure connection. The public SSH key allows you to use SSH to access the MVE and perform administrative tasks, such as setting the administrative password, enabling HTTPS access, and optionally registering the MVE to your management platform.
Megaport supports the 2048-bit RSA key type.
**To generate an SSH key pair (Linux/Mac OSX)**
* Enter the SSH keygen command in the terminal.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ssh-keygen -f ~/.ssh/megaport-mve-instance-1-2048 -t rsa -b 2048
```
The key generator command creates an SSH key pair and adds two files to your \~/.ssh directory:
* **megaport-mve-instance-1-2048** - contains the private key.
* **megaport-mve-instance-1-2048.pub** - contains the public key that is authorized to log in to the vendor account.
**To generate an SSH key pair (Windows, using [PuTTYgen](https://www.puttygen.com))**
1. Open PuTTYgen.
2. In the Key section, choose RSA 2048 bit and click **Generate**.
3. Move your mouse randomly in the small screen to generate the key pairs.
4. Enter a key comment to identify the key.\
This is convenient when you use several SSH keys.
5. Enter a Key passphrase, and re-enter to confirm.\
The passphrase is used to protect your key. You will be asked for it when you connect via SSH.
6. Click **Save private key**, choose a location, and click **Save**.
7. Click **Save public key**, choose a location, and click **Save**.
You will copy and paste the contents of the public key file in the Megaport Portal later to distribute the public key to the MVE. Your private key will match the public key to grant access. Only a single private key has access to the MVE for SSH access.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/checkpoint/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Check Point CloudGuard Network**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Check Point CloudGuard.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Check Point CloudGuard-specific settings:
* **Admin Password** -- Specify a temporary administrator password that you will use to access the virtual device. The password must be a minimum of 8 characters and include:
* 1 uppercase character (A-Z)
* 1 lowercase character (a-z)
* 1 number (0-9)
* 1 symbol
Store the admin password securely and do not share it with anyone. You can reset the admin password at the first login into the configured device.
Megaport does not store customer passwords.
* **SSH Key** -- Copy and paste the contents of your public SSH key here. You can find the public key in the **megaport-mve-instance-1-2048.pub** file generated earlier.
* **Virtual Interfaces (vNICs)** -- Each Check Point MVE is configured with one vNIC named *Data Plane*. To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with Check Point CloudGuard. The overlay network is created and maintained by Check Point CloudGuard to provide secure tunnels from the branch locations.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up a Check Point CloudGuard instance.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/checkpoint/creating-mve-vxc).
# Creating a VXC to an MVE Integrated with Check Point CloudGuard Network
Source: https://docs.megaport.com/mve/checkpoint/creating-mve-vxc
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE) integrated with Check Point.
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with Check Point CloudGuard.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.\
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
For specific configuration details, see [Connecting MVE to MVE](/mve/checkpoint/connect-mve-to-mve).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/checkpoint/terminating-mve).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# Check Point CloudGuard with Megaport Virtual Edge
Source: https://docs.megaport.com/mve/checkpoint/index
This help topic describes Check Point CloudGuard with Megaport Virtual Edge (MVE) functionality.
Check Point CloudGuard delivers enterprise-grade network security integrated with Megaport Virtual Edge (MVE), combining advanced threat prevention with flexible, scalable connectivity.
Using the Megaport Portal, you can create and manage MVE instances along with Virtual Cross Connects (VXCs) that connect to cloud on-ramps and other services within the Megaport software-defined network (SDN). MVE provides the underlying compute, networking, and connectivity platform, while Check Point CloudGuard delivers a secure overlay firewall and security policy enforcement.
For information about Check Point CloudGuard, see [CloudGuard Network Security](https://www.checkpoint.com/cloudguard/cloud-network-security/).
The following diagram shows an example network implementation of Check Point CloudGuard features over the Megaport network.
# Planning Your Check Point Deployment
Source: https://docs.megaport.com/mve/checkpoint/plan-deployment
This help topic describes Check Point deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
| **You Provide** | **Megaport Provides** |
| - | - |
| Internet connection from branch | Platform to host virtual security instances |
| Check Point CloudGuard deployed at branch | Complete connection from a branch to any destination on the Megaport network and interoperation with other Megaport products and services |
| Customer premises equipment (CPE) installed in branch | Megaport Internet connection to terminate the tunnel between MVE and CPE at branch via internet |
| Check Point CloudGuard software license to use on Megaport SDN | Access to the Megaport ecosystem |
## Deployment considerations
This section provides an overview of the MVE deployment options and features.
Check Point's architecture is different from many other firewall vendors.
Check Point uses a central Security Management Server (Policy Server) to manage and configure its Security Gateways, including MVEs. The Security Management Server defines security policies and distributes them to gateways, which then enforce those policies.
**Initial access and management**
* Use vNIC 0 for initial communication with the device.
* Configure vNIC 0 as untagged to allow first-time administrative login.
* Check Point firewalls disable Internet Control Message Protocol (ICMP) by default. You cannot use ping or other ICMP-based tools to verify connectivity immediately after deployment.
* After the MVE is live, log in using SSH or HTTPS.
**Policy and advanced configuration**
* Use Check Point Smart Console for advanced configuration and policy management. You must fully configure the Smart Console before you can create or publish firewall policies.
* Deploy a Management Gateway (Security Management Server) to define and distribute firewall policies. You can deploy the Management Gateway in any CSP environment.
For information about automating Check Point CloudGuard deployments, see [CloudGuard Network Security - How to configure cloud-init automation](https://support.checkpoint.com/results/sk/sk179752) and [How to provide user data in KVM with Configuration Drive](https://support.checkpoint.com/results/sk/sk180452).
### Network and Security Vendors
MVE integrates with Check Point CloudGuard to deliver advanced threat prevention and secure, policy-based traffic routing between your network and cloud environments.
For more information about supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Check Point CloudGuard Network**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* You can provision another MVE instance, add it to your overlay network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, add it to your overlay network, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### Security
MVE provides secure connectivity between your branch locations and cloud or data center destinations via the Megaport SDN. Check Point CloudGuard instances hosted on MVE inspect, secure, and control traffic across Megaport’s private network backbone. Traffic stays encrypted and policy-enforced from edge to destination.
### Licensing
Before creating an MVE in the Megaport Portal, ensure that your user account has ordering permissions. For more information, see [Creating an Account](/setting-up/registering).
You also need a valid Check Point CloudGuard license. To obtain or manage a Check Point CloudGuard license, see the [Check Point User Center](https://usercenter.checkpoint.com/).
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
### vNICs
One vNIC is supported for MVE integration with Check Point.
# Terminating an MVE
Source: https://docs.megaport.com/mve/checkpoint/terminating-mve
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window appears, displaying a list of services connected to the MVE. Early termination fees are shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use your SD-WAN management console to delete the MVE.
# Connecting MVEs Integrated with Cisco
Source: https://docs.megaport.com/mve/cisco/connect-mve-to-mve
This help topic describes how to connect two Megaport Virtual Edges (MVEs) integrated with Cisco SD-WAN.
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with Cisco to another MVE.
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer / partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
In vManage, an MVE is called a Cisco interconnect gateway.
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [the relevant Cisco product](/mve/cisco/creating/overview).
## Creating a VXC between two MVEs
A private VXC deployment between two MVEs integrated with Cisco starts in the Megaport Portal. To complete the configuration, you use the relevant Cisco console.
**To create a VXC**
1. In the Megaport Portal, go to the
**Services** page and click **+Connection** next to the originating A-End MVE.
2. Select Private VXC.
3. Select the destination B-End MVE and location.\
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `Dallas MVE 4 to LA MVE 2`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. For more information, see the Cisco documentation.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **vNIC selection** -- Depending on the definition of the MVEs you are using, you might have to specify A-End and B-End vNICs.
* **A-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
* **B-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
For more information about vNIC selection when connecting MVEs with different services, see [Types of vNIC Connections](/mve/vnic-connections).
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.\
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. 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 through the B-End VLAN.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Click **Add VXC** to move this configuration to your cart.
8. Repeat these steps to provision any additional VXCs.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs on the Cisco side. For more information about specific network design and configuration options before configuring interfaces for the MVEs, see the relevant Cisco documentation.
## Creating a VXC between two MVEs in vManage
**To create a VXC**
1. Select **Configuration > Cloud OnRamp for Multi-Cloud**.
2. Choose **Interconnect > Create Interconnect Connectivity**.
3. Select a Megaport account from the Choose Interconnect Account drop-down menu.
4. Choose the source interconnect gateway (A-End).
5. Click **Add Connection**.
6. Provide these details:
* **Destination Type** -- Select **Edge**.
* **Provider** -- Select **Megaport**.
* **Connection Name** -- Enter a name of your choice.
* **InterConnect Gateway** -- Select the destination interconnect gateway (B-End).
* **Bandwidth** -- Specify the connection bandwidth in Mbps.
7. Review the connection summary and click **Save**.
Cisco SD-WAN creates the interconnect connectivity (VXC) between the two gateways (MVEs). Once the process is complete, the status shows *Success*.
# Creating a Cisco MVE in Autonomous Mode
Source: https://docs.megaport.com/mve/cisco/creating-mve-autonomous
This help topic describes how to create and configure a Megaport Virtual Edge (MVE) with Cisco.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Cisco in *autonomous mode* for routing. Before you begin, you need user accounts with ordering permissions that provide access to the Megaport Portal. You also need a Cisco Smart account for licensing.
For information on setting up a Megaport account, see [Creating an Account](/setting-up/registering).
Cisco provides documentation in the [Catalyst 8000V Edge Software Installation And Configuration Guide](https://www.cisco.com/c/en/us/td/docs/routers/C8000V/Configuration/c8000v-installation-configuration-guide/m_csr_overview.html).
## Basic steps
This section summarizes the configuration steps using CLI commands and the Megaport Portal. Detailed procedures follow this basic step summary.
The basic steps are:
* Obtain a C8000V Smart License from Cisco.
* Generate an SSH key pair for authentication.
* Select autonomous mode in the Megaport Portal while creating the MVE.
* Enter an SSH key for full access to the MVE.
* Enter the MVE details.
* Create the Cisco MVE in the Megaport Portal.
* Activate the Cisco Smart License on the MVE using CLI commands.
## Licensing
Before you create an MVE in the Megaport Portal, you need a valid C8000V Smart License from Cisco. Smart Licensing is a license manager on a Cisco IOS XE device. You can place the order for Smart Licensing in the [Cisco Portal](https://cisco.com/).
The next step is to generate an SSH key pair for authentication.
## Administrative access to MVE
You connect your MVE through a public/private SSH key pair to establish a secure connection. The public SSH key allows you to use SSH to access the MVE and perform administrative tasks, such as setting the administrative password, enabling HTTPS access, and optionally registering the MVE to your management platform.
Megaport supports the 2048-bit RSA key type.
**To generate an SSH key pair (Linux/Mac OSX)**
* Enter the SSH keygen command in the terminal.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ssh-keygen -f ~/.ssh/megaport-mve-instance-1-2048 -t rsa -b 2048
```
The key generator command creates an SSH key pair and adds two files to your \~/.ssh directory:
* **megaport-mve-instance-1-2048** - contains the private key.
* **megaport-mve-instance-1-2048.pub** - contains the public key that is authorized to log in to the vendor account.
**To generate an SSH key pair (Windows, using [PuTTYgen](https://www.puttygen.com))**
1. Open PuTTYgen.
2. In the Key section, choose RSA 2048 bit and click **Generate**.
3. Move your mouse randomly in the small screen to generate the key pairs.
4. Enter a key comment to identify the key.\
This is convenient when you use several SSH keys.
5. Enter a Key passphrase, and re-enter to confirm.\
The passphrase is used to protect your key. You will be asked for it when you connect via SSH.
6. Click **Save private key**, choose a location, and click **Save**.
7. Click **Save public key**, choose a location, and click **Save**.
You will copy and paste the contents of the public key file in the Megaport Portal later to distribute the public key to the MVE. Your private key will match the public key to grant access. Only a single private key has access to the MVE for SSH access.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/cisco/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also typically create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Cisco C8000**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Cisco SD-WAN.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Cisco SD-WAN-specific settings:
* **Appliance Mode** -- Select Autonomous from the Appliance Mode drop-down list.
* **SSH Key** -- Copy and paste the contents of your public SSH key here. You can find the public key in the **megaport-mve-instance-1-2048.pub** file generated earlier. Must be RSA 2048 bits. We support both RFC4716 and RFC4253/OpenSSH formats.
* **Virtual Interfaces (vNICs)** -- Each MVE is configured with one vNIC named *Data Plane* by default. To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed.
You can add a total of five vNICs to the MVE, including the two added by default. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Enter a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with Cisco SD-WAN.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select **vNIC-0** for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up an MVE. At this point, the Cisco Catalyst 8000V MVE instance is booted.
## Viewing the MVE in the Megaport Portal
After creating the MVE, you can view it in the Megaport Portal on the Services page. You can also view the public IP addresses assigned.
**To view an MVE in the Megaport Portal**
* Go to the **Services** page.
The Megaport Internet icon differs from a standard VXC icon in the Megaport Portal, as shown in the image.
For more information about the Services page, see [Understanding the Services Page](/portal-admin/services-page).
**To view the public IP addresses assigned to the MVE**
1. Click the gear icon next to the Megaport Internet connection.
2. Select the **Details** tab.
3. Locate the public IP address (IPv4 or IPv6).\
These are the public IP addresses assigned to the MVE.
The next step is to activate Cisco Smart Licensing on the MVE.
## Activating the Cisco Smart License
Before you begin, you need to obtain a registration token from Cisco. After applying the token to the CLI configuration on the MVE, you can then verify the license status and configure the MVE throughput speed using CLI commands.
**To activate the Cisco Smart License**
1. Obtain a token ID from Cisco using your Smart account.
2. Use SSH to access the MVE. The default username is `mveadmin`.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ssh -i mveadmin@
```
Some older versions might require the ssh-rsa key type to be specified as permitted. For example, using the command:
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ssh -oHostKeyAlgorithms=+ssh-rsa -oPubkeyAcceptedAlgorithms=+ssh-rsa -i mveadmin@.
```
3. Submit a trust request to activate the license and register the MVE with Cisco.
Enter this command in enable mode and not configuration mode.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
license smart trust idtoken
OTgyODllZjktM2UzOC00ZTIzLThjODQtN2ZiZDc2ZDMzYjZmLTE2OTg0MjE0%0AODk5MDh8YURXSzBwdm0zTWtCU05mY3VRaUhTalFLbmJOTTQ2M0hIR2Y0U1E0%0ASUpmbz0%3D%0A local force
```
4. Verify that the trust token was installed.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
show license status
```
Wait for the instance to return a value for your smart and virtual accounts as well the date and time that the trust code was installed. This acknowledgement might take a couple of minutes.
5. Enter configuration mode.
6. Configure the throughput speed.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
platform hardware throughput level MB
```
Where *value* is a speed in mbps (for example, 10000 for 10G, 5000 for 5G, 1000 for 1G).
For speeds above 250 mbps, a Router US Export License for DNA (also known as an HSECK9) license must be available in your CSSM virtual account. After configuring the throughput level, the MVE instance retrieves the HSECK9 license automatically.
7. Verify the installed licenses.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
show license summary
```
8. Check the current throughput level.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
show platform hardware throughput level
```
**Example**:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
c8kv-auto-test-16#show license summary
Account Information:
Smart Account: Megaport As of Nov 04 15:44:06 2022 UTC
Virtual Account: CSR Virtual Account
License Usage:
License Entitlement Tag Count Status
-----------------------------------------------------------------------------
Router US Export Lic... (DNA_HSEC) 1 IN USE
network-advantage_1G (ESR_P_1G_A) 1 IN USE
dna-advantage_1G (DNA_P_1G_A) 1 IN USE
c8kv-auto-test-16#show plat hardware throughput level
The current throughput level is 2000000 kb/s
```
9. Save the configuration and reboot the MVE.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
wr mem
reload
```
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/cisco/creating-mve-vxc).
# Creating an MVE with Cisco Secure Firewall Threat Defense Virtual
Source: https://docs.megaport.com/mve/cisco/creating-mve-firewall
This help topic describes how to create and configure Megaport Virtual Edge (MVE) with Cisco Secure Firewall Threat Defense Virtual.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Cisco Secure Firewall Threat Defense Virtual.
Before you begin, you need user accounts with ordering permissions that provide access to the Megaport Portal. You also need a Cisco Smart account for licensing.
For details on setting up a Megaport account, see [Creating an Account](/setting-up/registering).
Cisco provides documentation in the [Cisco Secure Firewall Threat Defense Virtual Getting Started Guide](https://www.cisco.com/c/en/us/td/docs/security/firepower/quick_start/consolidated_ftdv_gsg/ftdv-gsg/m-introduction-to-ftdv.html).
## Basic steps
This section summarizes the configuration steps using the Megaport Portal. Detailed procedures follow this basic step summary.
The basic steps are:
* Obtain an FMC Registration Key and FMC IP address from Cisco.
* Enter the MVE details.
* Create the Cisco MVE in the Megaport Portal.
## Licensing
Before you create an MVE in the Megaport Portal, you need a valid FMC Registration Key from Cisco. You can place the order for your FMC Registration Key in the [Cisco Portal](https://cisco.com/).
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/fortinet/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also typically create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Cisco Secure Firewall Threat Defense Virtual**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Cisco Secure Firewall Threat Defense Virtual.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Cisco Secure Firewall Threat Defense Virtual-specific settings:
* **Admin Password** -- Specify a plain text password for administrator access. Prohibited characters are **" CR LF**.
* **Manage Locally** -- Select the check box to manage the MVE connection locally. Leave clear to make the MVE connect to the Firewall Management Center (FMC).
* **FMC IP Address** -- The IP address of the FMC. Required when **Manage Locally** is *not* selected.
You can provide input in the following formats:
* IPv4 address
* IPv6 address
* domain name
* **FMC Registration Key** -- This is required when **Manage Locally** is *not* selected and FMC IP address is provided.
* **NAT ID** (optional) -- Add an alphanumeric string that is used during the registration process between the FMC and the device. Used when **Manage Locally** is *not* selected.\
For more information, see [Cisco Secure Firewall Threat Defense Virtual Configuration Guide](https://www.cisco.com/c/en/us/td/docs/security/firepower/720/fdm/fptd-fdm-config-guide-720/fptd-fdm-mgmt.html).
* **Virtual Interfaces (vNICs)** -- Each MVE for Cisco Secure Firewall Threat Defense Virtual is configured with four vNICs by default. The vNICs are:\
0: Management\
1: Diagnostic\
2: Data1\
3: Data2
To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed. An MVE can have a total of five vNICs, including those added by default. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Enter a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with Cisco Secure Firewall Threat Defense Virtual SD-WAN.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select **vNIC-0** for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up a Cisco Secure Firewall Threat Defense Virtual.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/cisco/creating-mve-vxc).
## Helpful references
* [Integration of Cisco Secure Threat Defense Virtual with Megaport](https://blogs.cisco.com/security/integration-of-cisco-secure-threat-defense-virtual-with-megaport)
* [Introduction to Firepower Threat Defense Virtual](https://www.cisco.com/c/en/us/td/docs/security/firepower/quick_start/consolidated_ftdv_gsg/ftdv-gsg/m-introduction-to-ftdv.html)
* [Cisco Firewalls Overview](https://www.cisco.com/site/in/en/products/security/firewalls/index.html#tabs-7f5f5a2eac-item-1d285c9cd7-tab)
* [Cisco Virtual Firewalls Overview](https://www.cisco.com/site/in/en/products/security/firewalls/virtual-firewalls/index.html#tabs-3823800186-item-0e6f01b209-tab)
# Creating an MVE with Cisco Meraki
Source: https://docs.megaport.com/mve/cisco/creating-mve-meraki
This help topic describes how to create and configure Megaport Virtual Edge (MVE) with Cisco Meraki.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Cisco Meraki.
Before you begin, you need user accounts with ordering permissions that provide access to the Megaport Portal. For more information about setting up a Megaport account, see [Creating an Account](/setting-up/registering).
Before you create an MVE in the Megaport Portal, you also need to create a valid authorization token in the Cisco Meraki SD-WAN portal. For more information, see [vMX Setup Guide for Megaport MVE](https://documentation.meraki.com/SASE_and_SD-WAN/MX/Install_and_Get_Started/Installation_Guides/vMX_Setup_Guide_for_Megaport_MVE).
## Basic steps
This section summarizes the configuration steps using the Megaport Portal. Detailed procedures follow this basic step summary.
The basic steps are:
* Create a valid authorization token in the Cisco Meraki SD-WAN portal.
* Create the Cisco Meraki MVE in the Megaport Portal.
* Enter the MVE details.
* Ensure that the connection has been established on the Cisco Meraki SD-WAN portal.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/cisco/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also typically create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Meraki vMX**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Cisco Meraki.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Cisco Meraki-specific settings:
* **Token** -- Enter the token that was generated when you created the authorization token in the Cisco Meraki SD-WAN portal. For more information, see [vMX Setup Guide for Megaport MVE](https://documentation.meraki.com/SASE_and_SD-WAN/MX/Install_and_Get_Started/Installation_Guides/vMX_Setup_Guide_for_Megaport_MVE).
The authorization token does not get validated on the Megaport side. After the connection is made, you can check that the connection is active on the Cisco Meraki SD-WAN portal.
* **Virtual Interfaces (vNICs)** -- Each MVE is configured with two vNICs by default. The vNICs are:\
0: WAN\
1: LAN
To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with Cisco Meraki SD-WAN.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select **vNIC-0** for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up a Meraki vMX.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/cisco/creating-mve-vxc).
# Creating a VXC to an MVE Integrated with the relevant Cisco product
Source: https://docs.megaport.com/mve/cisco/creating-mve-vxc
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE).
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with Cisco.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.\
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
For specific CSP configuration details:
* AWS Direct Connect -- See [Creating MVE Connections to AWS](/cloud/mve/cisco/aws).
* Azure Express Route -- See [Creating MVE Connections to Azure using ExpressRoute](/cloud/mve/cisco/azure).
* Google Cloud -- See [Creating MVE Connections to Google](/cloud/mve/cisco/google).
* Other cloud connections -- See [Creating MVE Connections to Generic Endpoints](/cloud/mve/cisco/generic).
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
In vManage, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these MVEs via the Megaport network.
For specific configuration details, see [Connecting MVE to MVE](/mve/cisco/connect-mve-to-mve).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/cisco/terminating-mve).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# Creating a Cisco SD-WAN MVE in vManage
Source: https://docs.megaport.com/mve/cisco/creating/creating-mve
This help topic describes how to create and configure Megaport Virtual Edge (MVE) in Cisco vManage.
Cisco SD-WAN MVE is integrated with Megaport. Once you have a Megaport account, all further interactions are done through the Cisco centralized management console called vManage NMS.
The vManage NMS console is where you create, configure, administer, maintain, monitor, and terminate MVE.
**To create an MVE integrated with Cisco**
1. Create a Megaport account.
* **New Megaport customers** -- Log in to the Megaport Portal, create your account, and proceed to your Cisco vManage account. For more information, see [Creating an Account](/setting-up/registering).
* **Existing Megaport customers** -- Proceed to step 2.
Keep your Megaport account credentials handy, they will be required when creating the Cisco OnRamp for Multi-Cloud solution through vManage.
The Cisco vManage console uses Megaport API calls to synchronize and authenticate the MVE. If you are using a vManage console that does not allow this API call communication, for example, an on-premises vManage, you might need to open one or more ports on the customer firewall protecting the on-premises vManage. For more information, see [Firewall Ports for Cisco SD-WAN Deployments](https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/sdwan-xe-gs-book/cisco-sd-wan-overlay-network-bringup.html#c_Firewall_Ports_for_Viptela_Deployments_8690.xml).
2. Log in to Cisco vManage to create and configure a Megaport MVE.
In vManage, a Megaport MVE is called a Cisco interconnect gateway. The terms interconnect gateway and MVE are used interchangeably in this topic.
## Basic steps to create an MVE in vManage
This section provides an overview of the configuration steps in vManage. It uses your Megaport Portal account information to automatically make an API call to Megaport for MVE creation.
For more information about Cisco SD-WAN, see the [Cisco SD-WAN Cloud OnRamp Configuration Guide](https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/cloudonramp/ios-xe-17/cloud-onramp-book-xe/m-cloud-onramp-sdci.html).
The basic steps are:
* Attach a device to a template
* Configure the device template
* Configure the device
* Provision the Megaport account details
* Configure the MVE global settings
* Create the MVE (interconnect gateway)
The MVE with Cisco integration requires vManage platform version 20.5 or later. Before you begin, verify the vManage platform version.
**To view the vManage platform version**
* In the vManage console, click the question mark icon, choose About, and verify the version number.\
If your version is earlier than 20.5, upgrade to 20.5 or later.
**To attach a device to a Megaport template**
1. From the Configuration menu, choose Templates.
2. Select Default from the Template Type drop-down menu.
3. Select a template.\
This example uses the **Default\_MEGAPORT\_ICGW\_C8000V\_template\_V01** template, but you can also clone a default template and add to or modify the clone, as required.
4. Click the ellipsis (**...**).
5. Select Attach Devices.
6. Select a device from the list of available devices.\
If no devices are available, use your vSmart account to access the certificates for the devices.
7. Click the right arrow to move the device to the Selected Devices list and click **Attach**.
**To configure the device template**
1. Once the device is attached, click the ellipsis (**...**) and select **Edit Device Template**.
2. Select a color from the drop-down list.\
A *color* is a Cisco SD-WAN attribute that identifies the individual WAN transport tunnel. The color can provide restrictions such as VPN and assigns how other branches address the connection.
3. Enter a System IP address.\
Each interconnect gateway/MVE needs a unique System IP within the SD-WAN fabric. For example, 1.1.1.32. The system IP is not a routable IP address, but it must be unique among your edge devices.
4. Enter a site ID.\
Each interconnect gateway/MVE needs a site ID within the SD-WAN fabric. For example, 123132.
5. Enter a hostname.\
Each interconnect gateway/MVE needs a unique hostname within the SD-WAN fabric. For example, mve-atl-eq2.
6. Click **Update**.
**To configure the device**
1. Click the device name in the Device List.
2. Click **Configure Devices**.
**To provision the Megaport account details**
1. Select Configuration > Cloud OnRamp for Multi-Cloud.
2. Select the **Interconnect** tab.
3. Click Associate Interconnect Account.
4. Select Megaport as the interconnect provider.
5. Enter an account name.\
This name will appear in your vManage console.
6. (Optional) Enter an account description.
7. Enter your Megaport account credentials and click **Add**.\
vManage authenticates the account and saves the account details for later use.
**To configure global settings for an interconnect gateway (MVE)**
1. Select Configuration > Cloud OnRamp for Multi-Cloud.
2. Select the **Interconnect** tab.
3. Select Interconnect Global Settings and click **Edit**.
4. Provide these details:
* **Interconnect Provider** -- Select Megaport.
* **Software Image** -- Select the correct desired C8000 software version. For example, “C8000v 17.5 0\_20210121”.
* **Instance Size** -- Select a size from the drop-down list: MVE 2/4/500 (aka Small), MVE 4/8/1000 (aka Medium), or MVE 8/16/5000 (aka Large). Three sizes are available to support varying numbers of concurrent connections. Individual partner product metrics vary slightly. For more information, see [Planning your Cisco MVE Deployment](/mve/cisco/plan-deployment).
* **Interconnect Transit Color** -- Select a unique color for your links between the interconnect gateways. A *color* is a Cisco SD-WAN attribute that identifies the individual WAN transport tunnel. The color can provide restrictions such as VPN and assigns how other branches address the connection.
* **BGP ASN** -- Enter a BGP autonomous system number (ASN) for cloud peering of your choice. Or, reuse an existing ASN used by your organization.
5. Click **Update**.
The global settings are used as global default settings; however, you can modify global settings during MVE creation.
**To create the MVE**
1. Select Configuration > Cloud OnRamp for Multi-Cloud.
2. Choose Interconnect > Create Interconnect Gateway.
3. Provide these details:
* **Interconnect Provider** -- Select Megaport.
* **Gateway Name** -- Enter a unique name for the interconnect gateway (MVE).
* **Description** (optional) -- Enter a description.
* **Account Name** -- Select the Megaport account associated with vManage.
* **Location** -- Select a regionally appropriate location for the interconnect gateway (MVE). For more information, see [Planning your Cisco MVE Deployment](/mve/cisco/plan-deployment).
* **UUID** -- Select the UUID to associate with the interconnect gateway (MVE). This is the device attached to the template. The UUID allocates a license for MVE. If no UUIDs exist, you must first supply a license from your Cisco Smart Licensing account to purchase and attach appropriately sized device instance licenses to your Cisco instance.
* **Setting** -- Select default to configure the interconnect gateway (MVE) with the default global gateway settings. You can choose custom to adjust the size of the gateway instance.
4. Click **Add**.
Cisco creates the interconnect gateway (MVE). It can take from one to two minutes for the MVE instance to boot up and start the phone-home operation, and another two to five minutes to push the configuration and establish the BGP peering and tunnels. Once the process is complete, the status shows *Success*.
## Viewing the MVE in the Megaport Portal
After creating the MVE in vManage, you can view it in the Megaport Portal.
**To view an MVE in the Megaport Portal**
* Go to the **Services** page.
As part of the MVE provisioning, Cisco creates a Megaport Internet connection to provide connectivity and to allow MVE to register and communicate with the SD-WAN overlay network. The overlay network is created and maintained by Cisco SD-WAN to provide secure tunnels from the branch locations. The Megaport Internet size is based on the size of the MVE. The Megaport Internet icon differs from a standard VXC icon in the Megaport Portal, as shown in the image.
## Viewing the interconnect gateway in vManage
After creating the interconnect gateway, you can monitor the status in vManage.
**To view an interconnect gateway in vManage**
* Go to vManage > Monitor > Network.
Once the MVE is provisioned with an Active status, the next step is to create VXCs to connect the Megaport network to other MVEs or cloud service providers.
For more information, see [Creating a VXC to an MVE Integrated with Cisco](/mve/cisco/creating-mve-vxc).
## Deleting an MVE
You can terminate an MVE directly from vManage.
**To delete an interconnect gateway (MVE)**
1. Select Configuration > Cloud OnRamp for Multi-Cloud.
2. Choose Interconnect.
3. Select Gateway Management.
4. Select the interconnect gateway and click the ellipsis (**...**).
5. Select Delete.
# Creating a Cisco SD-WAN MVE Using a Bootstrap Configuration File
Source: https://docs.megaport.com/mve/cisco/creating/creating-mve-bootstrap
This help topic describes how to deploy a Cisco SD-WAN Megaport Virtual Edge (MVE) using a vManage device template and a bootstrap (cloud-init) configuration file.
This topic describes how to deploy a Cisco SD-WAN MVE using a bootstrap (cloud-init) configuration file. In this method, you build a device template in the Cisco vManage console, generate and download a bootstrap configuration file, then create the MVE in the Megaport Portal and upload that file.
This is a manual deployment method. It is separate from the automated Cloud OnRamp for Multi-Cloud method, in which vManage uses your Megaport Portal account details to make an API call to Megaport and create the interconnect gateway for you. For the automated method, see [Creating a Cisco SD-WAN MVE in vManage](/mve/cisco/creating/creating-mve).
In vManage, a Megaport MVE is called a Cisco interconnect gateway. The terms interconnect gateway and MVE are used interchangeably in this topic.
## Basic steps
This section provides an overview of the configuration steps. You configure the device template in vManage, generate the bootstrap file, then upload the file when you create the MVE in the Megaport Portal.
For more information about Cisco SD-WAN, see the [Cisco SD-WAN Cloud OnRamp Configuration Guide](https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/cloudonramp/ios-xe-17/cloud-onramp-book-xe/m-cloud-onramp-sdci.html).
The basic steps are:
* Attach a device to a template
* Configure the device template
* Configure the device
* Generate the bootstrap configuration file
* Provision the MVE in the Megaport Portal
The MVE with Cisco integration requires vManage platform version 20.5 or later. Before you begin, verify the vManage platform version.
**To view the vManage platform version**
* In the vManage console, click the question mark icon, choose About, and verify the version number.\
If your version is earlier than 20.5, upgrade to 20.5 or later.
## Attaching a device to a template
Log in to your Cisco vManage console and follow these steps.
**To attach a device to a Megaport template**
1. From the Configuration menu, choose Templates.
2. Select Default from the Template Type drop-down menu.
3. Select a template.\
This example uses the **Default\_MEGAPORT\_ICGW\_C8000V\_template\_V01** template, but you should first create a copy of the default template and then add to or modify the clone, as required.
4. Click the ellipsis (**...**).
5. Select Attach Devices.
6. Select a device from the list of available devices.\
If no devices are available, use your vSmart account to access the certificates for the devices.
7. Click the right arrow to move the device to the Selected Devices list then click **Attach**.
## Configuring the device template
Configure the device template, including the color, system IP, site ID, and hostname. The color is a Cisco SD-WAN attribute that identifies the individual WAN transport tunnel. The color labels the transport, and the router uses that label for policy and path selection.
**To configure the device template**
1. After the device is attached, click the ellipsis (**...**) and select **Edit Device Template**.
2. Select a color from the drop-down list.\
A *color* is a Cisco SD-WAN attribute that identifies the individual WAN transport tunnel. The color can provide restrictions such as VPN and assigns how other branches address the connection. Select the color that best represents the underlying transport.
3. Enter a System IP address.\
Each interconnect gateway/MVE needs a unique System IP within the SD-WAN fabric. For example, 1.1.1.32. The System IP is not a routable IP address, but it must be unique among your edge devices.
4. Enter a site ID.\
Each interconnect gateway/MVE needs a site ID within the SD-WAN fabric. For example, 123132.
5. Enter a hostname.\
Each interconnect gateway/MVE needs a unique hostname within the SD-WAN fabric. For example, mve-atl-eq2.
6. Click **Update**.
## Configuring the device
Configure the device pushes the operational configuration to the MVE, including its interfaces, routing, VPNs, and SD-WAN settings.
**To configure the device**
1. Click the device name in the Device List.
2. Click **Configure Devices**.
## Generating the bootstrap configuration file
Keep the template minimal and use the default settings. Do not configure any specific settings, because the purpose of the bootstrap file is onboarding only.
**To generate the bootstrap configuration file**
1. Select Configuration > Devices and open the WAN Edge list.
2. Click the ellipsis (**...**) for the device and select **Generate Bootstrap Configuration**.
3. Click **Download** to save the bootstrap file.
The bootstrap configuration file contains:
* System IP
* Site ID
* Organization name
* vBond information
* Certificates and authentication data
## Creating an MVE in the Megaport Portal
After you download the bootstrap file, create the MVE in the Megaport Portal and upload the file as the cloud-init file.
**To provision the MVE in the Megaport Portal**
1. Log in to the Megaport Portal and go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Cisco C8000** and select the software version, then click **Next**.
4. Select the MVE details, including the **Location** and **Size**, then click **Next**.\
Three sizes are available (small, medium, and large) to support varying numbers of concurrent connections. For more information, see [Planning Your Cisco MVE Deployment](/mve/cisco/plan-deployment).
5. Specify the Cisco SD-WAN-specific settings:
* **Appliance Mode** -- Select SD-WAN from the Appliance Mode drop-down list.
* **Cloud-init File** -- Click **Choose file** and upload the bootstrap configuration file you downloaded from vManage.
6. Complete the provisioning steps to create the MVE.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. After deployment, the MVE:
* Boots up
* Uses the bootstrap configuration
* Establishes a connection to vBond
* Joins the SD-WAN fabric
vManage then recognizes the device and pushes the full configuration.
## Next steps
Once the MVE is provisioned with an Active status, the next steps are to:
* Configure WAN (VPN 0) if it is not template-driven.
* Configure BGP if required.
* Connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace. For more information, see [Creating a VXC](/mve/cisco/creating-mve-vxc).
* Verify the control connections.
# Creating an MVE Integrated with Cisco Overview
Source: https://docs.megaport.com/mve/cisco/creating/overview
This help topic provides an overview of configuration methods to create a Megaport Virtual Edge (MVE) integrated with Cisco
This topic provides an overview of the deployment methods used to create an MVE integrated with Cisco.
You can configure the MVE in one of these modes:
* **Configure the MVE for routing using the Megaport Portal** -- In autonomous mode, the MVE uses Cisco Catalyst 8000V Edge software to act as a virtualized standalone router, providing full control of the cloud provider to users with advanced routing expertise. MVE in autonomous mode supports all advanced routing features, including multi-virtual routing and forwarding (VRF). After provisioning the MVE in autonomous mode, you can use existing policy management, CLI scripts, and other legacy solutions such as Cisco Dynamic Multipoint VPN (DMVPN). This provisioning method does not require SD-WAN. For more information, see [Creating a Cisco MVE in Autonomous Mode](/mve/cisco/creating-mve-autonomous).
To learn more about Cisco Catalyst Edge Software, see the [Cisco Catalyst 8000V Edge Software Data Sheet](https://www.cisco.com/c/en/us/products/collateral/routers/catalyst-8000v-edge-software/datasheet-c78-744101.html).
* **Create an SD-WAN MVE in vManage** -- Cisco SD-WAN MVE is integrated with Megaport. Once you have a Megaport account, all further interactions are done through the Cisco centralized management console called vManage NMS. For more information, see [Creating a Cisco SD-WAN MVE in vManage](/mve/cisco/creating/creating-mve).
* **Create an SD-WAN MVE using a bootstrap configuration file** -- Build a device template in vManage, generate and download a bootstrap (cloud-init) configuration file, then create the MVE in the Megaport Portal and upload that file. For more information, see [Creating a Cisco SD-WAN MVE Using a Bootstrap Configuration File](/mve/cisco/creating/creating-mve-bootstrap).
* **Configure an MVE with Cisco Meraki** -- You can create and configure an MVE using Cisco Meraki. For more information, see [Creating an MVE with Cisco Meraki](/mve/cisco/creating-mve-meraki).
* **Configure an MVE with Cisco Secure Firewall Threat Defense Virtual** -- You can create and configure an MVE using Cisco Secure Firewall Threat Defense Virtual. For more information, see [Creating an MVE with Cisco Secure Firewall Threat Defense Virtual](/mve/cisco/creating-mve-firewall).
# Cisco with Megaport MVE
Source: https://docs.megaport.com/mve/cisco/index
This help topic describes Cisco with Megaport Virtual Edge (MVE) functionality.
Cisco offers a range of solutions for Megaport Virtual Edge (MVE), providing advanced routing and security options. Depending on your needs, you can deploy a Cisco MVE C8000V for routing and SD-WAN functionalities or use Cisco Secure Firewall Threat Defense Virtual to ensure consistent security policies across various environments. Alternatively, Cisco Meraki provides a cloud-managed, simplified approach to SD-WAN and security, designed for ease of use and scalability.
## Deployment Options
### Cisco MVE C8000V Deployment Options
#### Cisco MVE for Routing (Autonomous Mode)
A Cisco MVE C8000V provisioned in autonomous mode creates a standalone router that supports the Cisco IOS XE software features and technologies, providing Cisco IOS XE routing, security, and switching features on a virtualization platform.
Cisco MVE supports your existing license. You bring your own Cisco Interconnect Gateway (Cisco Catalyst 8000V Edge Software) license for Cisco for use with MVE. The Megaport Portal is used to create and order the MVE and create and manage the Virtual Cross Connects (VXCs).
Megaport Virtual Edge in autonomous mode requires Cisco C8000V.
The following diagram shows an example network implementation of Cisco (Autonomous Mode) features over the Megaport network.
#### Cisco MVE in SD-WAN Mode (vManage)
Cisco MVE provisioned in SD-WAN mode supports IOS XE SD-WAN functionalities, including comprehensive SD-WAN, WAN gateway, and network services functions in the virtual and cloud environments.
Cisco creates the private overlay network and manages the network connections and network policies. The vManage management console is used to create and order the MVE and create and manage the Virtual Cross Connects (VXCs) to the cloud on-ramps and other services in the Megaport SDN. The Cisco SD-WAN fabric acts as the overlay, and the Megaport SDN acts as the underlay.
MVE in SD-WAN mode requires Cisco’s vManage management console running version 20.5 or later.
The following diagram shows an example network implementation of Cisco SD-WAN Mode (vManage) features over the Megaport network.
### Megaport MVE with Cisco Meraki
Cisco Meraki offers cloud-managed network solutions that can be integrated with Megaport MVE to extend the capabilities of your network with simplified management and scalability. Cisco Meraki's SD-WAN technology provides secure, optimized connectivity, enabling centralized control of multiple sites from the Meraki Dashboard.
By deploying Cisco Meraki's SD-WAN technology on Megaport MVE, you can benefit from automated connectivity and routing management, as well as security features that are built into the platform. Cisco Meraki’s centralized cloud architecture simplifies the deployment and management of network services, and Megaport MVE enhances the performance and flexibility of your Cisco Meraki deployments.
Cisco Meraki’s security solutions integrate seamlessly with Megaport MVE to provide unified management and consistent policy enforcement across your network.
The Meraki Dashboard is used to monitor and manage SD-WAN connections, with traffic prioritization and policies that ensure optimal performance of business-critical applications. The Megaport Portal is used to create and order the MVE, and establish Virtual Cross Connects (VXCs) to various cloud services and on-premises locations.
The following diagram shows an example network implementation of Cisco Meraki features over the Megaport network.
### Cisco MVE with Cisco Secure Firewall Threat Defense Virtual
Cisco Secure Firewall Threat Defense Virtual uses Cisco’s firewall functionality to enable consistent security policies for workloads across physical, virtual, and cloud environments.
Deploying Cisco Secure Firewall Threat Defense Virtual on MVE allows you to create a single security solution in your workflows for personal devices, data centers, and the closest availability zones of your cloud platforms.
## Helpful references
* [Cisco Catalyst 8000V Edge Software Data Sheet](https://www.cisco.com/c/en/us/products/collateral/routers/catalyst-8000v-edge-software/datasheet-c78-744101.html)
* [Creating a Cisco MVE in Autonomous Mode](/mve/cisco/creating-mve-autonomous)
* [Creating a Cisco SD-WAN MVE in vManage](/mve/cisco/creating/creating-mve)
* [Creating a Cisco SD-WAN MVE Using a Bootstrap Configuration File](/mve/cisco/creating/creating-mve-bootstrap)
* [Creating an MVE with Cisco Meraki](/mve/cisco/creating-mve-meraki)
* [Creating an MVE with Cisco Secure Firewall Threat Defense Virtual](/mve/cisco/creating-mve-firewall)
# Planning Your Cisco MVE Deployment
Source: https://docs.megaport.com/mve/cisco/plan-deployment
This help topic describes deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
## Appliance modes
Cisco MVE offers these appliance modes, each tailored to different deployment needs. Selecting the appropriate mode determines how you configure, manage, and use your Cisco MVE.
* **Autonomous Mode** – Supports Cisco IOS XE non-SD-WAN deployment for traditional routing without SD-WAN functionality. This mode provides access to the full Cisco IOS XE software features and technologies. For more information, see [Creating a Cisco MVE in Autonomous Mode](/mve/cisco/creating-mve-autonomous).
To learn more about Cisco Catalyst Edge software, see:
* [Cisco Catalyst 8000V Edge Software Data Sheet](https://www.cisco.com/c/en/us/products/collateral/routers/catalyst-8000v-edge-software/datasheet-c78-744101.html)
* [Cisco Catalyst 8000V Edge Software Installation And Configuration Guide](https://www.cisco.com/c/en/us/td/docs/routers/C8000V/Configuration/c8000v-installation-configuration-guide/day0-bootstrap-configuration.html)
* **SD-WAN Mode (vManage)** – Supports the Cisco SD-WAN solution. This mode uses the existing SD-WAN functionality with no changes. To operate with Cisco SD-WAN, a new MVE must be provisioned in SD-WAN mode. For more information, see [Creating a Cisco SD-WAN MVE in vManage](/mve/cisco/creating/creating-mve) and [Creating a Cisco SD-WAN MVE Using a Bootstrap Configuration File](/mve/cisco/creating/creating-mve-bootstrap).
* **Cisco Meraki Mode** – Enables a cloud-managed SD-WAN deployment, managed through the Cisco Meraki platform. This mode is ideal for users preferring a simplified, cloud-based SD-WAN solution for branch connectivity. Requires a Cisco Meraki authorization token for configuration. For more information, see [Creating an MVE with Cisco Meraki](/mve/cisco/creating-mve-meraki).
* **Cisco Secure Firewall Threat Defense Virtual (FTDv) Mode** – Provides integrated security with Cisco FTDv for customers needing firewall protection as part of their deployment. It is configured through Cisco FMC, with a focus on consistent security policies across network environments. For more information, see [Creating an MVE with Cisco Secure Firewall Threat Defense Virtual](/mve/cisco/creating-mve-firewall).
| **Appliance Mode** | **Features** |
| - | - |
| Autonomous |
Includes full Cisco IOS XE functionality for routing
Configured through the Megaport Portal or API
User provides an SSH key to access the router
Does not require SD-WAN
|
| SD-WAN |
Supports Cisco IOS XE SD-WAN, including Cisco Meraki SD-WAN integration
Configured via Cisco vManage
User provides a cloud-init file, generated by vManage and uploaded through Megaport Portal or API
|
| Cisco Meraki |
Cloud-managed SD-WAN for simplified deployment
Integrates with Megaport MVE for multi-branch scalability
Integrated with Cisco Secure Firewall Threat Defense Virtual
Requires FMC registration key for licensing
|
You select the appliance mode when you configure the MVE. After selecting a mode and deploying the MVE, you cannot change the appliance mode.
## Deployment considerations
This section provides an overview of the MVE deployment options and features.
### SD-WAN vendors
Cisco offers a range of solutions for MVE, providing both advanced routing capabilities and robust security options. Depending on your needs, you can deploy a Cisco MVE C8000V for routing and SD-WAN functionalities, use Cisco Meraki for cloud-managed SD-WAN with simplified management, or use Cisco Secure Firewall Threat Defense Virtual to ensure consistent security policies across various environments.
For information about all supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **the relevant Cisco product**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* You can provision another MVE instance, add it to your SD-WAN overlay network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, add it to your SD-WAN overlay network, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### Security
MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN. CSP-hosted instances of partner SD-WAN products route critical traffic across the Megaport SDN, reducing internet dependence. Traffic remains encrypted and under your policy control while traveling across the Megaport SDN, to or from, MVE.
### Licensing
**Cisco C8000 licensing**
You bring your own Cisco Interconnect Gateway (Cisco Catalyst 8000V Edge Software) Smart License for Cisco for use with MVE.
The Catalyst 8000V license is part of Cisco DNA and is based on bandwidth tiers.
New customers need a Catalyst 8000v license with Tier 2 bandwidth (DNA-C8KV-T2-A-SDCI) for small and medium MVE instances, or a Catalyst 8000V license with Tier 3 bandwidth (DNA-C8KV-T3-A-SDCI) for large MVE instances.
If you already have Catalyst 8000V licenses and subscriptions, MVE requires Cisco DNA Premier or Cisco DNA Advantage subscriptions and Tier 2 (for small and medium instances) or Tier 3 (for large instances) bandwidth.
You can order the solution through Cisco partners, who can order all components through Cisco Commerce Workspace (CCW). For more information, discuss licensing with your Account Manager and see the [Cisco Catalyst 8000V Edge Software Ordering Guide](https://www.cisco.com/c/en/us/products/collateral/routers/catalyst-8000v-edge-software/nb-06-cat8000v-edge-sw-og-cte-en.pdf).
**Cisco Meraki licensing**
For Cisco Meraki you need to create a valid authorization token in the Cisco Meraki SD-WAN portal. For more information, discuss licensing with your Account Manager and see the [Cisco Secure Access Meraki SD-WAN Configuration Guide](https://documentation.meraki.com/MX/Security_Service_Edge_Integrations/Cisco_Secure_Access_Meraki_SD-WAN_Configuration_Guide).
**Cisco Secure Firewall Threat Defense Virtual licensing**
For Cisco Secure Firewall Threat Defense Virtual, you need an [FMC Registration Key from the Cisco Portal](https://www.cisco.com/c/en/us/support/docs/security/firepower-management-center/215838-fmc-and-ftd-smart-license-registration-a.html).
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
**Cisco Meraki VLAN tagging**
Since Cisco Meraki does not support VLAN tagging, set the **Preferred A-End VLAN** to **Untagged** to ensure proper connectivity. For more information, see [Creating an MVE with Cisco Meraki](/mve/cisco/creating-mve-meraki).
### vNICs
Each MVE can have up to five vNICs. An MVE is created with one vNIC by default. You can add up to four more, making a total of five.
Each MVE for Cisco Secure Firewall Threat Defense Virtual is configured with four vNICs by default. The vNICs are:
* 0: Management
* 1: Diagnostic
* 2: Data1
* 3: Data2
Each MVE for Cisco Meraki is configured with two vNICs by default. The vNICs are:
* 0: WAN
* 1: LAN
Before specifying the number of vNICs on your MVE:
* Be aware that the number of vNICs cannot be changed after an MVE has been ordered. Decide in advance how many vNICs to specify when you create the MVE.
* Consult your service provider to make sure that functionality won't be affected if you add a vNIC.
If you need to change the number of vNICs after an MVE has been ordered, you will have to cancel and re-order the MVE.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
### Known limitations
The following table lists known limitations in the Cisco software for MVE. Before you select a software version, check whether these limitations affect your design.
| Limitation | Product | Affected software versions |
| - | - | - |
| Untagged and tagged VXCs on the same vNIC | Cisco C8000 (Autonomous and SD-WAN modes) | 17.x versions earlier than 17.18.04, and 26.x versions earlier than 26.01.02 |
| Untagged and tagged VXCs on the same vNIC | Cisco Secure Firewall Threat Defense Virtual | All versions |
| /31 IP addresses on data interfaces | Cisco Secure Firewall Threat Defense Virtual | All versions |
**Untagged and tagged VXCs on the same vNIC**
An MVE with an affected software version does not support an untagged VXC and tagged VXCs on the same vNIC. To work around this limitation:
* Use each vNIC for either one untagged VXC or tagged VXCs, not both.
* If your Megaport Internet connection is untagged on vNIC-0, connect tagged VXCs to a different vNIC.
* In Autonomous mode, an MVE has one vNIC by default. If you need both untagged and tagged VXCs, add at least one more vNIC when you create the MVE. You cannot add vNICs after deployment.
For more information about this limitation on Cisco C8000, see [Cisco bug CSCwr42574](https://quickview.cloudapps.cisco.com/quickview/bug/CSCwr42574).
**/31 IP addresses on data interfaces**
On a Cisco Secure Firewall Threat Defense Virtual MVE, data interfaces do not support a /31 IP address from DHCP. They also do not support a static /31 IP address configured in Cisco Secure Firewall device manager (FDM). Cisco supports a static /31 IP address on a data interface when you configure the address in Cisco Secure Firewall Management Center (FMC). The management interface supports a /31 IP address from DHCP. For more information, see [Cisco bug CSCwn92354](https://quickview.cloudapps.cisco.com/quickview/bug/CSCwn92354).
# Integrating MPLS with SDCI
Source: https://docs.megaport.com/mve/cisco/sdci-mpls
This help topic describes integration and management challenges with MPLS and highlights the Megaport Software-Defined Cloud Interconnect (SDCI) solution with MVE and Cisco SD-WAN.
This topic describes integration and management challenges with and highlights the Software-Defined Cloud Interconnect (SDCI) solution with MVE and Cisco SD-WAN.
SDCI helps improve network performance in a cost-effective manner while adding the flexibility to create highly reliable connections on demand. For more information, see this Cisco topic: [What Is Software-Defined Cloud Interconnect (SDCI)?](https://www.cisco.com/c/en/us/solutions/enterprise-networks/sd-wan/what-is-sdci.html)
## Challenge
Many organizations have a mix of sites using MPLS underlay and internet underlay. In this scenario, a data center typically acts as an anchor site with connections to both underlays. The anchor site routes traffic between the MPLS and internet environments.
A few common challenges with this scenario include a possible single point of failure with the data center and efficient traffic management.
## Solution
SDCI with MVE can address these challenges and act as the anchor site, either to provide a more efficient path or as a backup due to an outage at the data center location.
To add SDCI to your networks, connect to the nearest Megaport location (Point of Presence (PoP)) from your MPLS site at the data center. Then, create an MVE (virtual router) and connect to the Megaport network.
This solution involves these general steps:
1. Work with your MPLS provider to provision a new MPLS circuit to a Megaport-enabled data center where you will also create the Port to connect to the Megaport network.
2. [Create a Megaport account](/setting-up) directly through the Portal.
You need a Megaport account and you cannot use an account created through CCW. This solution requires that you create a Port and CCW accounts only let you order MVEs and VXCs.
3. [Create a Port](/connections/creating-port) through the Megaport Portal at the data center with the MPLS circuit.\
When you create a Port, you generate an LOA for the physical cross connect.
4. Work with your MPLS provider to request the data center establish a single-mode fiber cross connect between the MPLS circuit and the Port in the data center.\
This step requires the LOA generated when ordering the Port.
5. From the Megaport Portal, [create a private VXC](/connections/private-vxc) from the Port to the MVE.
# Terminating an MVE
Source: https://docs.megaport.com/mve/cisco/terminating-mve
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window appears, displaying a list of services connected to the MVE. Early termination fees are shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use your SD-WAN management console to delete the MVE.
# Using the MVE Console
Source: https://docs.megaport.com/mve/console-access
This help topic describes how to access and use the MVE Console directly from the Megaport Portal.
This topic describes how to access and use the MVE Console directly from the Megaport Portal.
The MVE Console provides direct access to your MVE instance through a browser-based interface. You can troubleshoot connectivity issues, view system logs, configure your MVE, and perform administrative tasks without additional tools or VPN connections. For detailed configuration, troubleshooting, and advanced operations, see your vendor’s official documentation and supported management tool.
## Use cases for the MVE Console
These are the main use cases for the MVE Console:
* **Troubleshooting connectivity issues** -- Diagnose and resolve issues if your MVE loses network connectivity.
* **Initial configuration** -- Perform initial setup tasks before network connectivity is established.
* **System administration** -- View system logs, monitor resource usage, and perform maintenance tasks.
* **Emergency access** -- Access your MVE when other remote access methods are unavailable.
* **Power management** -- Perform shutdown, reboot, or reset operations from the console controls.
## Prerequisites
To access the MVE Console, you need:
* An active MVE service that supports MVE Console access.
The MVE Console access is enabled by default for supported MVE services, and no additional configuration in the Megaport Portal is required.
When console access is not available, use the vendor-specific management tools or CLI methods for your MVE.
* Appropriate account permissions:
* **Company Admins, Technical Admins, and Technical Contacts** -- Can access the console for their company's MVE services. For more information about which roles have console access, see [Managing User Roles](/portal-admin/user-management/roles).
* **Partners** -- Can access the console for their managed accounts' MVE services when viewing those accounts in the Megaport Portal.
* **Managed account users** -- Can access the console for their MVE services (subject to their account permissions).
Partners can access the console only when viewing a managed account's services. The Console Access button is not available when partners view their own company's MVE services.
## Accessing the MVE Console
You can open the MVE Console from the Megaport Portal.
**To access the MVE Console**
1. In the Megaport Portal, go to the **Services** page.
2. Locate your MVE and click the icon.
The console automatically connects to your MVE when the page loads. The connection uses a secure, temporary authentication token that is valid for the duration of your session.
## Using the MVE Console
The MVE Console provides a full-screen view of your MVE instance, with a control bar at the top.
### Console controls
The control bar includes these options:
* **Connect** -- Manually connect to the MVE if the connection is not active.
* **Disconnect** -- Disconnect from the MVE Console session. Once disconnected, you can connect again manually by either closing the tab or clicking **Connect**.
Power operations (shutdown, reboot, and reset) will interrupt your MVE service. Use these options carefully and only when necessary.
If the connection is interrupted, the console automatically attempts to reconnect after a few seconds. You can also manually reconnect by clicking **Connect**.
* **Fullscreen** -- Toggle fullscreen mode for the console view.
* **Clipboard** -- Paste text into the MVE Console, including commands, configuration text, passwords, API keys, or any other content, from your local machine into the MVE Console.
**To paste text to the MVE Console**
1. Click **Clipboard**.
2. In the Paste to Console screen, type or paste your text into the text area.
3. Click **Paste to Console** to send the text to your MVE.
The text is sent to the console as if you were typing it directly. Multi-line text is supported, with line breaks converted to Enter key presses. After the text is sent, the screen closes and the text area is cleared.
The clipboard paste feature supports ASCII printable characters only (letters A-Z, numbers 0-9, common symbols, spaces, tabs, and line breaks). Non-ASCII characters such as accented letters (é, ñ), non-Latin scripts (中文, العربية), and emoji are automatically skipped during paste. If your text contains non-ASCII characters, you will need to type those characters manually after pasting the rest of your text.
The Clipboard button is available only when the console is connected. If you are not connected, use the Connect button first.
* **Notifications**
The Notifications button provides access to console event notifications and connection status messages. A badge on the button shows the number of unread notifications.
Notifications include:
* Connection status updates (connected, disconnected, reconnecting)
* Session timeout warnings
* Console bell signals from the remote system
* Connection errors and diagnostic messages
**To view notifications**
1. Click **Notifications**.
The notifications panel opens, displaying recent console events with timestamps.
2. Click **Clear All** to remove all notifications from the panel.
When you open the notifications panel, all notifications are automatically marked as read, and the badge counter is cleared. Important notifications also appear as pop-up messages in the console interface.
## Console session timeouts
Console sessions have time limits. Your console session can end for these reasons:
* **Maximum session duration** -- Each console session has a maximum allowed duration. When you connect to the console, your session token includes this time limit. You will receive a warning notification 10 minutes before your session expires.
* **Inactivity timeout** -- If you don't interact with the console for a period of time, your session automatically disconnects.
When a session timeout occurs:
1. The console automatically disconnects.
2. A notification appears explaining the reason for the disconnect.
3. You can reconnect immediately by clicking **Connect**.
To avoid losing work due to timeouts:
* Save your work frequently, especially when performing long-running configuration tasks.
* Watch for timeout warning notifications and reconnect if needed.
* Keep the console tab active when you are working on extended tasks.
Reconnecting after a timeout creates a new console session. If you were in the middle of a task, you might need to navigate back to where you were working.
## Troubleshooting console access
Use these troubleshooting steps to resolve common MVE Console access issues.
### Console Access button is disabled
The Console Access button appears grayed out with a tooltip stating 'Not supported on this platform'. Your MVE vendor platform doesn't support the MVE Console access. This is a limitation of the specific MVE vendor or image you are using, not an account permission issue.
Your MVE service functions normally, only the browser-based console access feature is unavailable. To manage your MVE, use your vendor-specific management tools or CLI access methods.
### Cannot access the console
If you cannot access the MVE Console:
* Verify that your MVE is in a live state (not being provisioned or terminated).
* Confirm that you have the appropriate account permissions.
* Concurrent access is not supported. If a console session already exists for that MVE, close the session and use the existing one.
* Try refreshing the browser page to establish a new connection.
* **For partners**: Ensure you are viewing a managed account's services. The Console Access button is not available when viewing your own company's MVE services.
If you experience connection issues while using the console:
* Check your internet connection stability.
* Disable any browser extensions that might interfere with WebSocket connections.
* Try using a different browser if the issue persists.
### Connection fails with 'session already exists' error
The MVE Console allows only one active connection at a time. If you see a 'session already exists' notification, a console session is already open.
This can happen if:
* The console is open in another browser tab or window
* A previous session didn't close properly after a network interruption
* Another user with access to your account is connected to the console
To resolve this:
1. Check for other open console tabs or windows and close them.
2. If you don't have any other console sessions open, wait a few minutes for the previous session to time out.
3. If the issue persists, click **Disconnect**, then **Connect** to force a new connection.
If another authorized user needs console access, the current user must disconnect first.
## Console security and session management
The MVE Console uses the following security measures:
* Connections are encrypted using WebSocket Secure (WSS) protocol.
* Each console session uses a temporary authentication token that expires when the session ends.
* Console access requires appropriate account permissions and cannot be accessed without authentication.
For stronger security, Megaport recommends enabling Single Sign-On (SSO) or Multi-Factor Authentication (MFA) for your company. For more information, see [Setting up Single Sign-On](/setting-up/enforcing-sso) and [Multi-Factor Authentication](/setting-up/enforcing-mfa).
Close the console browser tab or window when you are finished to ensure your session is terminated.
## Helpful references
* [Monitoring MCR](/monitoring/mcr-monitoring)
* [Monitoring MVE](/monitoring/mve-monitoring)
* [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring)
* [Viewing Activity Logs](/portal-admin/activity-logs)
# Connecting MVEs Integrated with Deciso OPNsense
Source: https://docs.megaport.com/mve/deciso/connect-mve-to-mve
This help topic describes how to connect two Megaport Virtual Edges (MVEs) integrated with Deciso OPNsense.
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with Deciso OPNsense to another MVE.
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer / partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [Creating an MVE with Deciso OPNsense](/mve/deciso/creating-mve-deciso).
## Creating a VXC between two MVEs
A private VXC deployment between two MVEs integrated with Deciso OPNsense starts in the Megaport Portal. To complete the configuration, you use the OPNsense web interface.
**To create a VXC**
1. In the Megaport Portal, go to the
**Services** page and click **+Connection** next to the originating A-End MVE.
2. Select Private VXC.
3. Select the destination B-End MVE and location.
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `Dallas MVE 4 to LA MVE 2`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. For more information, see the [OPNsense documentation](https://docs.opnsense.org/).
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic does not flow through this service and it behaves as if it is down on the Megaport network. Billing for this service remains active and you are still charged for this connection.
* **vNIC selection** -- Depending on the definition of the MVEs you are using, you might have to specify A-End and B-End vNICs.
* **A-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
* **B-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
For more information about vNIC selection when connecting MVEs with different services, see [Types of vNIC Connections](/mve/vnic-connections).
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport assigns one.
* **Preferred B-End VLAN** -- Specify the 802.1q VLAN tag for this connection that you receive through the B-End VLAN.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Confirm the configuration and click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs on the OPNsense side. For more information about specific network design and configuration options before configuring interfaces for the MVEs, see the [OPNsense documentation](https://docs.opnsense.org/).
# Creating an MVE Integrated with Deciso OPNsense
Source: https://docs.megaport.com/mve/deciso/creating-mve-deciso
Learn how to deploy Deciso OPNsense on Megaport Virtual Edge (MVE), enabling open-source firewall and routing capabilities without physical hardware.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Deciso OPNsense.
## Basic steps
This section summarizes the configuration steps using the Megaport Portal. Detailed procedures follow this basic step summary.
The basic steps are:
* Obtain an OPNsense license from Deciso (if required for your deployment).
* Generate an SSH key pair for authentication.
* Create the OPNsense MVE in the Megaport Portal.
* Access the OPNsense web interface to complete the configuration.
## Licensing
OPNsense is open-source software. Deciso offers optional commercial support subscriptions and the OPNsense Business Edition with additional features and support.
For more information about Deciso licensing and support options, see the [Deciso website](https://www.deciso.com/) or contact your Megaport Sales Representative for guidance.
## Administrative access to MVE
You connect your MVE through a public/private SSH key pair to establish a secure connection. The public SSH key allows you to use SSH to access the MVE and perform administrative tasks, such as setting the administrative password, enabling HTTPS access, and optionally registering the MVE to your management platform.
Megaport supports the 2048-bit RSA key type.
**To generate an SSH key pair (Linux/Mac OSX)**
* Enter the SSH keygen command in the terminal.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ssh-keygen -f ~/.ssh/megaport-mve-instance-1-2048 -t rsa -b 2048
```
The key generator command creates an SSH key pair and adds two files to your \~/.ssh directory:
* **megaport-mve-instance-1-2048** - contains the private key.
* **megaport-mve-instance-1-2048.pub** - contains the public key that is authorized to log in to the vendor account.
**To generate an SSH key pair (Windows, using [PuTTYgen](https://www.puttygen.com))**
1. Open PuTTYgen.
2. In the Key section, choose RSA 2048 bit and click **Generate**.
3. Move your mouse randomly in the small screen to generate the key pairs.
4. Enter a key comment to identify the key.\
This is convenient when you use several SSH keys.
5. Enter a Key passphrase, and re-enter to confirm.\
The passphrase is used to protect your key. You will be asked for it when you connect via SSH.
6. Click **Save private key**, choose a location, and click **Save**.
7. Click **Save public key**, choose a location, and click **Save**.
You will copy and paste the contents of the public key file in the Megaport Portal later to distribute the public key to the MVE. Your private key will match the public key to grant access. Only a single private key has access to the MVE for SSH access.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/deciso/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you typically also create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Deciso OPNsense**.
4. Select the software version.
This selection determines the version of OPNsense that runs on the MVE.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone is displayed on the location details through the rest of the provisioning, and on the Summary page.
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the OPNsense-specific settings:
* **Admin Password** (required) -- Specify a temporary administrator password that you use to access the virtual device. The password must be a minimum of 8 characters and include:
* 1 uppercase character (A-Z)
* 1 lowercase character (a-z)
* 1 number (0-9)
* 1 symbol
Store the admin password securely and do not share it with anyone. You can reset the admin password at the first login into the configured device.
Megaport does not store customer passwords.
* **SSH Key** (required) -- Copy and paste the contents of your public SSH key here. You can find the public key in the **megaport-mve-instance-1-2048.pub** file generated earlier.
* **Virtual Interfaces (vNICs)** -- Each MVE is configured with two vNICs named *WAN* and *LAN* by default. To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed.
You can add a total of five vNICs to the MVE. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Specify a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you must delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Specify a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
The portal prompts you to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to access the internet for management and updates.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic does not flow through this service and it behaves as if it is down on the Megaport network. Billing for this service remains active and you are still charged for this connection.
* **A-End vNIC** -- Select the vNIC for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to order the connection.
7. Click **Review Order** in the Configured Services area.
8. If you have a promotional code, click **Add Promo Code**, enter it, then click **Add Code**.
9. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up a Deciso OPNsense instance.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/deciso/creating-mve-vxc).
# Creating a VXC to an MVE Integrated with Deciso OPNsense
Source: https://docs.megaport.com/mve/deciso/creating-mve-vxc
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE) integrated with Deciso OPNsense.
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with Deciso OPNsense.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
For specific configuration details, see [Connecting MVE to MVE](/mve/deciso/connect-mve-to-mve).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/deciso/terminating-mve).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# Deciso OPNsense with Megaport Virtual Edge
Source: https://docs.megaport.com/mve/deciso/index
This help topic describes Deciso OPNsense with Megaport MVE functionality.
Deciso OPNsense on Megaport's MVE delivers open-source firewall and routing capabilities directly on Megaport's global private SDN. By integrating OPNsense with MVE, you can deploy a feature-rich firewall and routing platform without physical hardware, shipping delays, or data center rack space.
Megaport provides the network underlay, while OPNsense manages firewall policies, VPN connections, and network routing. You use the Megaport Portal to create and order MVE instances and establish Virtual Cross Connects (VXCs) to cloud on-ramps and other services on the Megaport SDN.
## Deciso OPNsense
OPNsense is an open-source, FreeBSD-based firewall and routing platform developed by Deciso.
Key capabilities include:
* **Stateful firewall** -- Inspect and filter traffic with flexible rule management and traffic shaping.
* **VPN services** -- IPsec, OpenVPN, and WireGuard support for secure site-to-site and remote access connectivity.
* **Intrusion detection and prevention** -- Integrated IDS/IPS using Suricata for real-time threat detection.
* **Web filtering and proxy** -- Control web access with transparent proxy and URL filtering.
* **Traffic shaping** -- Prioritize and manage bandwidth allocation across your network.
OPNsense provides a web-based management interface for configuration and monitoring, with CLI access for advanced administration.
## Helpful references
* [Deciso Website](https://www.deciso.com/)
* [OPNsense Documentation](https://docs.opnsense.org/)
# Planning Your Deciso OPNsense Deployment
Source: https://docs.megaport.com/mve/deciso/plan-deployment
This help topic describes Deciso OPNsense deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
| **You Provide** | **Megaport Provides** |
| - | - |
| Internet connection from branch | Platform to host the OPNsense virtual appliance |
| OPNsense enabled at branch | Complete connection from a branch to any destination on the Megaport network and interoperation with other Megaport products and services |
| Customer premises equipment (CPE) installed in branch | Megaport Internet connection to terminate the tunnel between MVE and CPE at branch via internet |
| OPNsense license (if using Business Edition) to use on Megaport SDN | Access to the Megaport ecosystem |
## Deployment considerations
This section describes MVE deployment options and sizing for Deciso OPNsense. For an overview of OPNsense features, see [Deciso OPNsense with Megaport Virtual Edge](/mve/deciso). For information about all supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Deciso OPNsense**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* You can provision another MVE instance, add it to your network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### Security
MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN.
### Licensing
Before you create an MVE in the Megaport Portal, you need user accounts with ordering permissions that provide access to the Megaport Portal. For more information, see [Creating an Account](/setting-up/registering).
OPNsense is open-source software. Deciso offers optional commercial support subscriptions and the OPNsense Business Edition with additional features and support. For more information, see the [Deciso website](https://www.deciso.com/).
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
### vNICs
Each MVE can have up to five vNICs. A Deciso OPNsense MVE is created with two vNICs by default:
* 0: WAN
* 1: LAN
You can add up to three more, making a total of five.
Before specifying the number of vNICs on your MVE:
* You cannot change the number of vNICs after ordering an MVE. Decide in advance how many vNICs to specify when you create the MVE.
* Consult your service provider to verify that adding a vNIC does not affect functionality.
If you need to change the number of vNICs after an MVE has been ordered, you must cancel and re-order the MVE.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
# Terminating an MVE
Source: https://docs.megaport.com/mve/deciso/terminating-mve
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term results in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
Use the OPNsense web interface to back up your configuration before terminating the MVE.
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window is displayed, showing a list of services connected to the MVE. The window displays early termination fees, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use the OPNsense web interface to delete the MVE.
# Connecting MVEs Integrated with F5 BIG-IP VE
Source: https://docs.megaport.com/mve/f5/connect-mve-to-mve
This help topic describes how to connect two Megaport Virtual Edges (MVEs) integrated with F5 BIG-IP Virtual Edition.
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with F5 BIG-IP Virtual Edition to another MVE.
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer / partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [Creating an MVE with F5 BIG-IP Virtual Edition](/mve/f5/creating-mve-f5-bigip).
## Creating a VXC between two MVEs
A private VXC deployment between two MVEs integrated with F5 BIG-IP VE starts in the Megaport Portal. To complete the configuration, you use the F5 BIG-IP management interface.
**To create a VXC**
1. In the Megaport Portal, go to the
**Services** page and click **+Connection** next to the originating A-End MVE.
2. Select Private VXC.
3. Select the destination B-End MVE and location.
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `Dallas MVE 4 to LA MVE 2`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. For more information, see the F5 BIG-IP documentation.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic does not flow through this service and it behaves as if it is down on the Megaport network. Billing for this service remains active and you are still charged for this connection.
* **vNIC selection** -- Depending on the definition of the MVEs you are using, you might have to specify A-End and B-End vNICs.
* **A-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
* **B-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
For more information about vNIC selection when connecting MVEs with different services, see [Types of vNIC Connections](/mve/vnic-connections).
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport assigns one.
* **Preferred B-End VLAN** -- Specify the 802.1q VLAN tag for this connection that you receive through the B-End VLAN.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Confirm the configuration and click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs on the F5 BIG-IP side. For more information about specific network design and configuration options before configuring interfaces for the MVEs, see the [F5 BIG-IP Documentation](https://my.f5.com/manage/s/article/K14946).
# Creating an MVE Integrated with F5 BIG-IP Virtual Edition
Source: https://docs.megaport.com/mve/f5/creating-mve-f5-bigip
Learn how to deploy F5 BIG-IP Virtual Edition on Megaport Virtual Edge (MVE), enabling advanced application delivery and traffic management without physical hardware.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with F5 BIG-IP Virtual Edition (VE).
## Basic steps
This section summarizes the configuration steps using the Megaport Portal. Detailed procedures follow this basic step summary.
The basic steps are:
* Obtain a license from F5.
* Generate an SSH key pair for authentication.
* Create the F5 BIG-IP VE MVE in the Megaport Portal.
* Access the F5 BIG-IP VE management interface to complete configuration.
## Licensing
Before you create an MVE in the Megaport Portal, you need a valid F5 BIG-IP license.
To obtain or manage an F5 BIG-IP license, see the [F5 Licensing Documentation](https://my.f5.com/manage/s/article/K7752) or contact your Megaport Sales Representative for guidance.
## Administrative access to MVE
You connect your MVE through a public/private SSH key pair to establish a secure connection. The public SSH key allows you to use SSH to access the MVE and perform administrative tasks, such as setting the administrative password, enabling HTTPS access, and optionally registering the MVE to your management platform.
Megaport supports the 2048-bit RSA key type.
**To generate an SSH key pair (Linux/Mac OSX)**
* Enter the SSH keygen command in the terminal.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ssh-keygen -f ~/.ssh/megaport-mve-instance-1-2048 -t rsa -b 2048
```
The key generator command creates an SSH key pair and adds two files to your \~/.ssh directory:
* **megaport-mve-instance-1-2048** - contains the private key.
* **megaport-mve-instance-1-2048.pub** - contains the public key that is authorized to log in to the vendor account.
**To generate an SSH key pair (Windows, using [PuTTYgen](https://www.puttygen.com))**
1. Open PuTTYgen.
2. In the Key section, choose RSA 2048 bit and click **Generate**.
3. Move your mouse randomly in the small screen to generate the key pairs.
4. Enter a key comment to identify the key.\
This is convenient when you use several SSH keys.
5. Enter a Key passphrase, and re-enter to confirm.\
The passphrase is used to protect your key. You will be asked for it when you connect via SSH.
6. Click **Save private key**, choose a location, and click **Save**.
7. Click **Save public key**, choose a location, and click **Save**.
You will copy and paste the contents of the public key file in the Megaport Portal later to distribute the public key to the MVE. Your private key will match the public key to grant access. Only a single private key has access to the MVE for SSH access.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/f5/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you typically also create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **F5 BIG-IP**.
4. Select the software version.
This selection determines the version of F5 BIG-IP VE that runs on the MVE.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone is displayed on the location details through the rest of the provisioning, and on the Summary page.
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the F5 BIG-IP VE-specific settings:
* **Admin Password** -- Specify a temporary administrator password that you use to access the virtual device. The password must be a minimum of 8 characters and include:
* 1 uppercase character (A-Z)
* 1 lowercase character (a-z)
* 1 number (0-9)
* 1 symbol
Store the admin password securely and do not share it with anyone. You can reset the admin password at the first login into the configured device.
Megaport does not store customer passwords.
* **SSH Key** -- Copy and paste the contents of your public SSH key here. You can find the public key in the **megaport-mve-instance-1-2048.pub** file generated earlier.
* **Virtual Interfaces (vNICs)** -- Each MVE is configured with one vNIC named *SRIOV or Management* by default. To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed.
All vNICs on an F5 BIG-IP VE MVE are attached using Single Root I/O Virtualization (SR-IOV) for direct access to the underlying physical network interface. The default name (*SRIOV or Management*) is a label only and you can rename it to suit your own naming conventions.
You can add a total of five vNICs to the MVE, including the one added by default. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Specify a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you must delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Specify a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
The portal prompts you to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to access the internet for management and licensing.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic does not flow through this service and it behaves as if it is down on the Megaport network. Billing for this service remains active and you are still charged for this connection.
* **A-End vNIC** -- Select the vNIC for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to order the connection.
7. Click **Review Order** in the Configured Services area.
8. If you have a promotional code, click **Add Promo Code**, enter it, then click **Add Code**.
9. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up an F5 BIG-IP Virtual Edition instance.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/f5/creating-mve-vxc).
# Creating a VXC to an MVE Integrated with F5 BIG-IP VE
Source: https://docs.megaport.com/mve/f5/creating-mve-vxc
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE) integrated with F5 BIG-IP Virtual Edition.
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with F5 BIG-IP Virtual Edition.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
For specific configuration details, see [Connecting MVE to MVE](/mve/f5/connect-mve-to-mve).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/f5/terminating-mve).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# F5 BIG-IP Virtual Edition with Megaport Virtual Edge
Source: https://docs.megaport.com/mve/f5/index
This help topic describes F5 BIG-IP Virtual Edition with Megaport MVE functionality.
F5 BIG-IP Virtual Edition (VE) on Megaport Virtual Edge (MVE) delivers advanced application delivery and security services directly on Megaport's global private Software Defined Network (SDN). By integrating BIG-IP VE with MVE, you can deploy a virtual Application Delivery Controller (ADC) without physical hardware, eliminating shipping delays, rack space requirements, and infrastructure overhead.
Megaport provides the network underlay, while F5 BIG-IP VE handles application traffic management, workload security, network protection, and secure application access. Through the Megaport Portal, you can provision MVE instances and establish Virtual Cross Connects (VXCs) to cloud on-ramps, data centers, and other services available on the Megaport SDN.
## F5 BIG-IP Virtual Edition
F5 BIG-IP VE delivers the same core traffic management, optimization, and security capabilities as physical BIG-IP appliances deployed in on-premises environments.
Key capabilities include:
* **Load balancing and traffic management** -- BIG-IP Local Traffic Manager (LTM) distributes application traffic across backend resources to improve performance, availability, and scalability.
* **Global Server Load Balancing (GSLB) and DNS** -- BIG-IP DNS directs users to the optimal application endpoint based on health, performance, and proximity.
* **Web Application Firewall (WAF)** -- BIG-IP Advanced WAF protects applications and APIs from OWASP Top 10 threats, bot attacks, API abuse, and Layer 7 DDoS attacks.
* **SSL/TLS offloading** -- BIG-IP LTM offloads encryption processing from application servers and enables inspection and policy enforcement on encrypted traffic.
* **Zero Trust application access** -- BIG-IP Zero Trust Access enforces identity-based app access control with authentication and authorization policies.
* **Network firewall and DDoS protection** -- BIG-IP Advanced Firewall Manager (AFM) provides stateful firewalling and protection against network-layer DDoS attacks.
* **Programmatic traffic control** -- F5 iRules enable advanced, programmable traffic manipulation, routing, and security enforcement beyond standard configuration options.
You can centrally manage BIG-IP VE deployments using [F5 BIG-IQ](https://www.f5.com/products/big-iq-centralized-management), which provides a unified interface for managing BIG-IP application services across data center, cloud, and Megaport edge environments.
BIG-IQ deployment is not supported on Megaport MVE.
## Performance and licensing
BIG-IP VE deployments on Megaport MVE support up to 10 Gbps of L4/L7 throughput, depending on the selected license tier, making them suitable for a wide range of high-performance workloads.
BIG-IP VE is licensed using a Bring Your Own License (BYOL) model. Purchase licenses separately through F5 or authorized F5 partners.
## Helpful references
* [F5 BIG-IP Virtual Edition Product Page](https://www.f5.com/products/big-ip-services/virtual-editions)
* [F5 BIG-IP Virtual Edition Documentation](https://my.f5.com/manage/s/article/K14946)
# Planning Your F5 BIG-IP Deployment
Source: https://docs.megaport.com/mve/f5/plan-deployment
This help topic describes F5 BIG-IP Virtual Edition deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
| **You Provide** | **Megaport Provides** |
| - | - |
| F5 BIG-IP VE software license | Platform to host the F5 BIG-IP VE virtual appliance |
| Application servers, backend services, or destinations to be load balanced, accelerated, or protected | Connectivity from the MVE to data centers, CSPs, and other endpoints on the Megaport SDN, and interoperation with other Megaport products and services |
| Configuration of BIG-IP modules (LTM, BIG-IP DNS, WAF, SSL/TLS offload) for your use case | Megaport Internet connection for management plane access, licensing, and updates |
| Administrator credentials and SSH key for initial access | Access to the Megaport ecosystem |
## Deployment considerations
This section describes MVE deployment options and sizing for F5 BIG-IP VE. For an overview of F5 BIG-IP VE features, see [F5 BIG-IP Virtual Edition with Megaport Virtual Edge](/mve/f5). For information about all supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **F5 BIG-IP**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* You can provision another MVE instance, add it to your network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### Security
MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN.
### Licensing
Before you create an MVE in the Megaport Portal, you need user accounts with ordering permissions that provide access to the Megaport Portal. For more information, see [Creating an Account](/setting-up/registering).
You bring your own F5 BIG-IP license for use with MVE. BIG-IP VE supports up to 10 Gbps of L4/L7 throughput, depending on the selected license tier. For more information about obtaining an F5 BIG-IP license, contact your F5 representative or see the [F5 Licensing Documentation](https://my.f5.com/manage/s/article/K7752).
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
### vNICs
Each MVE can have up to five vNICs. An F5 BIG-IP VE MVE is created with one vNIC by default. You can add up to four more, making a total of five.
Before specifying the number of vNICs on your MVE:
* You cannot change the number of vNICs after ordering an MVE. Decide in advance how many vNICs to specify when you create the MVE.
* Consult your service provider to verify that adding a vNIC does not affect functionality.
If you need to change the number of vNICs after an MVE has been ordered, you must cancel and re-order the MVE.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
# Terminating an MVE
Source: https://docs.megaport.com/mve/f5/terminating-mve
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term results in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
Before terminating the MVE, release the F5 BIG-IP license in the F5 licensing portal to be able to re-use it. For more information about releasing the license for further use, see the [F5 Licensing Documentation](https://my.f5.com/manage/s/article/K7752).
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window is displayed, showing a list of services connected to the MVE. The window displays early termination fees, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use the F5 BIG-IP management interface to delete the MVE configuration if needed.
# Connecting MVEs Integrated with Fortinet Secure SD-WAN
Source: https://docs.megaport.com/mve/fortinet/connect-mve-to-mve
This help topic describes how to connect two Megaport Virtual Edges (MVEs) integrated with Fortinet SD-WAN.
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with Fortinet Secure SD-WAN to another MVE.
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer/SD-WAN partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [Creating an MVE Integrated with Fortinet](/mve/fortinet/creating-mve).
## Creating a VXC between two MVEs
A private VXC deployment between two MVEs integrated with Fortinet starts in the Megaport Portal. To complete the configuration, you use the Fortinet FortiManager console.
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and click **+Connection** next to the originating A-End MVE.
2. Select Private VXC.
3. Select the destination B-End MVE and location.\
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `LA MVE 2 to Dallas MVE 4`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. Consult Fortinet's documentation for more information.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **vNIC selection** -- Depending on the definition of the MVEs you are using, you might have to specify A-End and B-End vNICs.
* **A-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
* **B-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
For more information about vNIC selection when connecting MVEs with different services, see [Types of vNIC Connections](/mve/vnic-connections).
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.\
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. 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 through the B-End VLAN.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Click **Add VXC** to move this configuration to your cart.
8. Repeat these steps to provision any additional VXCs.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs in FortiManager.
The next procedure configures IP connectivity with BGP, providing just one solution out of many. Consult your SD-WAN vendor documentation for specific network design and configuration options before configuring interfaces for the MVEs.
## Configuring the A-End MVE in FortiManager
1. Log in to your FortiManager Cloud instance at [Fortinet Support](https://support.fortinet.com).
2. Choose Services > FortiManager.
3. Select the A-End MVE.
4. Go to the System menu and choose Interface.
5. Click **+Create New > Interface**.
6. Provide these details:
* **Interface Name** -- Enter a name for the interface, for example, `VLAN2500`.
* **Alias Name** (optional) -- Provide an alternate name, for example, `MVE-2 to MVE-4`.
* **Type** -- Select VLAN.
* **Interface** -- Select the parent interface: port1.
* **VLAN ID** -- Enter the Local VLAN.
* **Role** - Select Undefined.
* **Addressing Mode** - Select Manual.
* **IP/Netmask** - Enter the local IP address and subject mask.
* **Administrative Access** - Select how you want to access this interface, such as HTTPS, PING, and SSH.
* **DHCP Server** - Choose **OFF**.
7. Click **OK**.
The new VLAN interface appears with your port1 physical interface.
You can run an `execute ping` command from FortiOS to verify the connection.
At this point, the interface is created. The next step is to optionally create the Border Gateway Protocol (BGP) session.
**To configure a BGP neighbor**
1. In FortiManager, go to **Router > BGP**.
2. Provide this information:
* **Local AS** -- Enter a unique, private autonomous system number (ASN).
* **Router ID** -- Enter an IP address in use on the system.
3. In Neighbors, click **+Create New**.
4. Enter the neighbor IP address.
5. Enter the Remote ASN.
6. Click **OK**.
7. Click **Apply**.
**To push the configuration to the device**
1. Choose Managed Devices.
The device Config Status is *Modified*.
2. Select the device.
3. Choose Install > Quick Install (Device DB).
4. Click **OK**.
5. Verify a successful installation and click **Finish**.
## Configuring the B-End MVE in FortiManager
1. Log in to your FortiManager Cloud instance at [Fortinet Support](https://support.fortinet.com).
2. Choose Services > FortiManager.
3. Select the B-End MVE.
4. Go to the System menu and choose Interface.
5. Click **+Create New > Interface**.
6. Provide these details:
* **Interface Name** -- Enter a name for the interface, for example, `VLAN2500`.
* **Alias Name** (optional) -- Enter an alternate name, for example, `MVE-4 to MVE-2`.
* **Type** -- Select VLAN.
* **Interface** -- Select the parent interface: port1.
* **VLAN ID** -- Enter the Local VLAN.
* **Role** - Select Undefined.
* **Addressing Mode** - Select Manual.
* **IP/Netmask** - Enter the local IP address and subject mask.
* **Administrative Access** - Select how you want to access this interface, such as HTTPS, PING, and SSH.
* **DHCP Server** - Choose **OFF**.
7. Click **OK**.
The new VLAN interface appears with your port1 physical interface.
You can run an `execute ping` command from FortiOS to verify the connection.
At this point, the interface is created. The next step is to optionally create a BGP session.
**To configure a BGP neighbor**
1. In FortiManager, go to **Router > BGP**.
2. Provide this information:
* **Local AS** -- Enter a unique, private autonomous system number (ASN).
* **Router ID** -- Enter an IP address in use on the system.
3. In Neighbors, click **+Create New**.
4. Enter the neighbor IP address.
5. Enter the Remote AS.
6. Click **OK**.
7. Click **Apply**.
**To push the configuration to the device**
1. Choose Managed Devices.
The device Config Status is *Modified*.
2. Select the device.
3. Choose Install > Quick Install (Device DB).
4. Click **OK**.
5. Verify a successful installation and click **Finish**.
## Validating your connection
You can review connection details, including the connection state, from the CLI with these commands:
* `get system interface` -- Displays configuration details and current status for the device interfaces.
* `get router info bgp neighbor ` -- Displays configuration details and current status for the BGP neighbors.
# Creating an MVE Integrated with Fortinet
Source: https://docs.megaport.com/mve/fortinet/creating-mve
This help topic describes how to create and configure a Megaport Virtual Edge (MVE) with Fortinet SD-WAN.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Fortinet Secure SD-WAN. Before you begin, you need user accounts with ordering permissions that provide access to the Megaport Portal and to Fortinet.
For more information about setting up a Megaport account, see [Creating an Account](/setting-up/registering).
Fortinet provides documentation for their SD-WAN product, including FortiManager and cloud connections, at [Fortinet SD-WAN Documentation Library](https://docs.fortinet.com/sdwan).
## Basic steps
This section provides an overview of the configuration steps in FortiManager and the Megaport Portal. Detailed procedures follow this basic step summary.
The basic steps are:
* Obtain a license from Fortinet.
* Generate an SSH key pair for authentication.
* Create the Fortinet MVE in the Megaport Portal.
* View the MVE public IP address assignment in the Megaport Portal.
* Set an admin password for the FortiGate.
* Allow secure console access to the FortiGate.
* Add the FortiGate to FortiManager Cloud (optional).
## Licensing
A valid FortiGate VM license file can be applied during the MVE deployment process through the Megaport Portal, or it can be applied post-deployment through the FortiGate WebUI or CLI interfaces.\
Alternatively, you can use the FortiFlex points-based licensing model. The FortiFlex token-based license must be applied through the CLI post-deployment.
If you buy a license from Fortinet, you will receive a registration code in a PDF. You will use this registration code to generate a license file.\
If you use FortiFlex points, you will generate a license token through the FortiFlex portal associated with your Fortinet Support account.
**To obtain a license file from Fortinet**
1. Log in to your registration account at [Fortinet Support](https://support.fortinet.com).
2. Choose Register Product and enter the provided registration code.
3. Follow the registration process.\
Fortinet generates the serial number and displays it on the Registration Completion page.
4. Choose **Manage > View Products** and click the serial number.
5. Click the download link and save the license file.\
You will upload the license file later in the Megaport Portal.
**To use FortiFlex points**
1. Deploy the FortiGate VM on MVE without choosing to upload a license file.
2. Access the FortiGate VM CLI by establishing a using the SSH session.
3. Copy the license token provided from your FortiFlex portal.
4. Inject the license token into the VM using the CLI.
5. Reboot the FortiGate VM when prompted.
Once the product is registered, it appears in the FortiCloud Asset Management product list.
The next step is to generate an SSH key pair for authentication.
## Administrative access to MVE
You connect your MVE through a public/private SSH key pair to establish a secure connection. The public SSH key allows you to use SSH to access the MVE and perform administrative tasks, such as setting the administrative password, enabling HTTPS access, and optionally registering the MVE to your management platform.
Megaport supports the 2048-bit RSA key type.
**To generate an SSH key pair (Linux/Mac OSX)**
* Enter the SSH keygen command in the terminal.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ssh-keygen -f ~/.ssh/megaport-mve-instance-1-2048 -t rsa -b 2048
```
The key generator command creates an SSH key pair and adds two files to your \~/.ssh directory:
* **megaport-mve-instance-1-2048** - contains the private key.
* **megaport-mve-instance-1-2048.pub** - contains the public key that is authorized to log in to the vendor account.
**To generate an SSH key pair (Windows, using [PuTTYgen](https://www.puttygen.com))**
1. Open PuTTYgen.
2. In the Key section, choose RSA 2048 bit and click **Generate**.
3. Move your mouse randomly in the small screen to generate the key pairs.
4. Enter a key comment to identify the key.\
This is convenient when you use several SSH keys.
5. Enter a Key passphrase, and re-enter to confirm.\
The passphrase is used to protect your key. You will be asked for it when you connect via SSH.
6. Click **Save private key**, choose a location, and click **Save**.
7. Click **Save public key**, choose a location, and click **Save**.
You will copy and paste the contents of the public key file in the Megaport Portal later to distribute the public key to the MVE. Your private key will match the public key to grant access. Only a single private key has access to the MVE for SSH access.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/fortinet/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also typically create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Fortinet FortiGate-VM**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Fortinet.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Fortinet-specific settings:
* **Appliance License** (optional) -- If you have purchased a license from Fortinet, click **Choose File** and select the appliance license generated earlier from Fortinet.\
If you are using FortiFlex, skip this step.
* **SSH Key** -- Copy and paste the contents of your public SSH key here. You can find the public key in the **megaport-mve-instance-1-2048.pub** file generated earlier.
* **Virtual Interfaces (vNICs)** -- Fortinet is configured with one vNIC named *Data Plane* by default. If required, you can change the name by typing over the *Data Plane* text. You can also change the vNIC name later, after the MVE has been deployed.
You can add a total of five vNICs to the MVE, including the one added by default. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Enter a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You cannot add or delete vNICs from a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with Fortinet SD-WAN.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select **vNIC-0** for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up a Fortinet FortiGate.
## Viewing the MVE in the Megaport Portal
After creating the MVE, you can view it in the Megaport Portal on the Services page. You can also view the public IP addresses assigned.
**To view an MVE in the Megaport Portal**
* Go to the **Services** page.
The Megaport Internet icon differs from a standard VXC icon in the Megaport Portal, as shown in the image.
For more information about the Services page, see [Understanding the Services Page](/portal-admin/services-page).
**To view the public IP addresses assigned to the MVE**
1. Click the gear icon next to the Megaport Internet connection.\
The Connection Configuration screen appears. From here, you can modify any of the Megaport Internet connection details.
2. Select the **Details** tab.
3. Locate the public IP address (IPv4 or IPv6).\
These are the public IP addresses assigned to the MVE.
## Allow console access to the FortiGate
Console access to the FortiGate is delivered through a secure HTTPS session. The MVE blocks all access to the public IP addresses assigned to the device until you SSH into it and grant HTTPS access.
**To set an admin Web UI password and allow HTTPS access**
1. SSH to the Fortinet MVE instance using the SSH private key generated earlier. The default username is admin, followed by the public IP address assigned to the device by Megaport.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ssh -i ~/.ssh/megaport-mve-instance-1-2048 admin@162.43.xx.x
```
Once in the FortiOS CLI, you can view system status and allow access to the device using CLI commands.
The FortiOS CLI differs from the standard NOS CLI or Linux shell.
2. Configure a password for the user admin account.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
FGVM08TM21001375 # config system admin
FGVM08TM21001375 (admin) # edit admin
FGVM08TM21001375 (admin) # set password xxxxxxxx
FGVM08TM21001375 (admin) # next
FGVM08TM21001375 (admin) # end
```
3. Allow HTTPS access to the public interface GUI on port 1.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
FGVM08TM21001375 # config system interface
FGVM08TM21001375 (interface) # edit port1
FGVM08TM21001375 (port1) # append allowaccess https
FGVM08TM21001375 (port1) # next
FGVM08TM21001375 (interface) # end
FGVM08TM21001375 #
```
4. Verify that HTTPS access is allowed.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
FGVM08TM21001375 # show system interface
```
With HTTPS access allowed, you can log in to the FortiGate through its Web UI using the user admin credentials.
## Supply the FortiFlex license token
If you are using FortiFlex to license your MVE, you must use the CLI to inject the license token from FortiFlex into the VM. Use the following command:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
exec vm-license
```
For example,
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
exec vm-license 58923569A3FFB7F46879
```
## Add the FortiGate to FortiManager Cloud
The next step is to add the FortiGate to FortiManager Cloud, Fortinet's SD-WAN centralized management platform.
This step is optional. You can manage a FortiGate as a standalone device without using FortiManager Cloud as its central manager.
**To add the FortiGate to FortiManager Cloud**
1. Log in to the FortiGate GUI: [https://162.43.xx.x](https://162.43.xx.x)
2. Select Device Manager.
3. From the Device Dashboard, Choose Security Fabric > Fabric Connectors.
4. Select FortiManager and click **Edit**.
5. Select the following settings:
* **Status** - Enabled
* **Type** - FortiManager Cloud
* **Mode** - Normal
6. Click **OK**.
The FortiCloud contacts your registered FortiManager Cloud for approval. The registration process does not require an IP address but instead uses backend authentication through prior registration and licensing.
### Authorize the FortiGate in FortiManager
Before FortiManager adds the FortiGate to its list of managed devices, you need to manually authorize it.
**To authorize the FortiGate**
1. Log in to your FortiManager Cloud instance at [Fortinet Support](https://support.fortinet.com).
2. Choose Services > FortiManager.
You will see an unauthorized device awaiting approval.
3. Click Unauthorized Devices, and then select the device to authorize.
4. Click **Authorize**.
5. You can optionally change the device name, apply a preconfigured policy package, or apply a preconfigured provisioning template to the device.
6. Click **OK** when you are satisfied with the configuration.\
A green check mark indicates the FortiGate was authorized by FortiManager.
7. Click **Close**.
The device is now managed via FortiManager Cloud and you can view it in the list of managed devices.
The IP address for the FortiGate displayed on the dashboard is an internal, private IP that is specifically used for the SD-WAN overlay.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/fortinet/creating-mve-vxc).
# Creating a VXC to an MVE Integrated with Fortinet FortiGate-VM
Source: https://docs.megaport.com/mve/fortinet/creating-mve-vxc
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE) integrated with Fortinet SD-WAN.
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with Fortinet.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.\
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
For specific CSP configuration details:
* AWS Direct Connect -- See [Creating MVE Connections to AWS](/cloud/mve/fortinet/aws).
* Azure Express Route -- See [Creating MVE Connections to Azure using ExpressRoute](/cloud/mve/fortinet/azure).
* Google Cloud -- See [Creating MVE Connections to Google](/cloud/mve/fortinet/google).
* Other cloud connections -- See [Creating MVE Connections to Generic Endpoints](/cloud/mve/fortinet/generic).
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
For specific configuration details, see [Connecting MVE to MVE](/mve/fortinet/connect-mve-to-mve).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/fortinet/terminating-mve).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# Configuring High Availability on Fortinet FortiGate Firewall based on FGSP
Source: https://docs.megaport.com/mve/fortinet/fortinet-fgsp-ha-mve
This help topic describes how to configure Fortinet FortiGate High Availability using FGSP for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for Fortinet FortiGate High Availability (HA) using FortiGate Session Life Support Protocol (FGSP) with route based redundancy.
For more information about Fortinet FortiGate, see [FortiGate / FortiOS documentation](https://docs.fortinet.com/product/fortigate/7.6).
## HA overview
When deploying Fortinet FortiGate firewalls on-premises, in a data center, or on Megaport Virtual Edge (MVE), using FGSP is a common approach for providing session redundancy. FGSP ensures that active sessions are synchronized between FortiGate peers, minimizing traffic disruption in the event of a firewall or link failure.
Historically, achieving HA-like session continuity in cloud or virtualized environments has been challenging, because it requires direct network paths between firewall peers and reliable session synchronization mechanisms. Megaport’s support for FortiGate firewalls on MVE and multi-vNIC functionality enables FGSP deployment, making session continuity possible even across virtualized network cores and multicloud connectivity.
FortiGate firewalls deployed on MVE can be configured with FGSP, combining the benefits of on-demand, as-a-service deployment, direct private connectivity to clouds and data centers, session synchronization, and orchestrated failover.
### FGSP modes
Fortinet FGSP differs from the traditional Fortinet HA protocol, FortiGate Clustering Protocol (FGCP), in that it focuses on session synchronization, rather than providing a unified, cluster-based active-active load balancing mechanism. While FGCP has Active/Active and Active/Passive modes, FGSP is typically used with:
* Two or more active FortiGate peers, where all devices can receive traffic as determined by the network layer. For example, router, SD-WAN, or an external load balancer.
* Session synchronization across peers, ensuring that if a peer fails, active sessions continue on surviving devices.
FGSP does not natively perform traffic failover. The upstream network, such as the router, SD-WAN overlay, or load balancer, must detect failures and redirect traffic to the surviving FortiGate instance.
### FGSP operation
FGSP synchronizes active sessions between FortiGate peers over a dedicated vNIC or VXC. Each FortiGate maintains its own interfaces, while the upstream network, for example, router or load balancer, determines traffic distribution.
In the event of a failure, such as a FortiGate node going down or a network path failing, the surviving FortiGate takes over the active sessions. The network must route new flows to the surviving peer. FGSP ensures that the existing session states are preserved, so traffic continuity is maintained.
FGSP is particularly useful in virtualized or multicloud deployments, where firewalls are deployed as active gateways in an overlay SD-WAN, and high availability cannot rely solely on traditional physical HA links.
### Architecture overview
The architecture deployed in this topic shows FortiGate firewalls on MVE with FGSP session synchronization.
There are two MVEs running FortiGate OS, each with its management interface connected to the internet. A dedicated VXC is created between the two MVEs to carry FGSP session synchronization traffic, while the data plane VXCs connect to one or more cloud environments or other networks.
In a production deployment, there might be additional VXCs for connecting to other networks, internet links, or VPNs. Management interfaces can also reside on private networks instead of the public internet, depending on your design.
The image below shows a high-level architecture diagram of the Fortinet FGSP deployment on MVE, showing session synchronization between two FortiGate peers and connectivity to multiple cloud environments, the internet, and Megaport Marketplace.
### Interface details
The following diagram shows the interface mapping for the FortiGate FGSP deployment. It shows vNIC 0 for management, vNIC 1 for data plane, and vNIC 2 for FGSP session synchronization, and data plane VXCs connect to cloud or overlay networks.
## Deploying FGSP on MVE
Deploying FGSP on an MVE requires the following configuration steps in the Megaport Portal and FortiGate OS:
1. Deploy the first FortiGate MVE instance
2. Deploy the second FortiGate MVE instance
3. Configure FGSP in FortiGate OS
### Deployment considerations
Each step of deploying a FortiGate MVE with FGSP requires some special considerations.
**Deploy the first FortiGate MVE instance**
We recommend that you assign a dedicated vNIC for FGSP session synchronization between peers. We also recommend that you assign a vNIC for management and a vNIC for data plane interfaces. A typical deployment requires three interfaces: management, data, and FGSP sync, but you can deploy up to 5 vNICs if required.
Fortinet recommends that FGSP session synchronization traffic is carried over a dedicated network segment or interface that is not shared with management or data traffic. This ensures reliable session synchronization, minimizes congestion, and avoids issues caused by or filtering on shared links. For more information, see the [Fortinet FGSP documentation](https://docs.fortinet.com/product/fortigate/7.6).
**Deploy the second FortiGate MVE instance**
Create a second FortiGate MVE of the same model and firmware version in the same or different metro. For performance-sensitive deployments, we recommend that the network path between the two MVE instances has low latency, but sub-millisecond latency is not required. Both FortiGate instances must be identical in model and firmware to support FGSP.
**Create VXCs for FGSP traffic**
If vNIC 0 is for management, vNIC 1 for data plane, then vNIC 2 can be assigned for FGSP session synchronization. Create a VXC between vNIC 2 on each MVE. Both ends should be untagged (no VLAN). This link will carry FGSP session synchronization traffic.
Ensure the FGSP VXC has sufficient bandwidth to handle peak session table synchronization traffic. Typical deployments start at 1 Gbps, but adjust based on the expected number of active sessions.
**Configure FGSP in FortiGate OS**
Configure each FortiGate MVE as an FGSP peer using the appropriate peer IP address over the VXC. Enable session pickup options to synchronize TCP, UDP, ICMP, NAT, and expectation sessions as required. Verify connectivity between peers and ensure session tables are being synchronized correctly. For more information, see the [FortiGate FGSP basic peer setup documentation](https://docs.fortinet.com/document/fortigate/7.6.5/administration-guide/869218/fgsp-basic-peer-setup).
### Creating the FortiGate MVEs in the Megaport Portal
The first step is to create and deploy two FortiGate MVEs in the Megaport Portal. Unlike traditional HA clustering (FGCP), Fortinet FGSP does not require multiple dedicated HA interfaces. Instead, it requires a reliable network path for session synchronization between FortiGate peers.
A typical FortiGate FGSP deployment on MVE includes:
* A management interface
* A data plane interface
* A recommended dedicated interface (or VNIC) for FGSP session synchronization.
**To create and deploy FortiGate MVEs**
1. In the Megaport Portal, go to the **Services** page.
2. Create a Fortinet FortiGate MVE as described in [Creating an MVE Integrated with Fortinet](/mve/fortinet/creating-mve).
3. On the MVE Details page, configure the required Virtual Interfaces (vNICs):
Repeat the same process to create a second FortiGate MVE, ensuring:
* The same FortiGate model
* The same FortiOS version
* Deployment in a suitable metro based on your latency and design requirements
* A Megaport Internet connection is created for the management interface of each FortiGate MVE.\
This allows initial access to the FortiGate GUI and CLI for configuration and validation.
This is the most common approach during initial deployment. However, the management interface can instead be connected to a private VXC once an alternative management path (such as a bastion host, Virtual Private Network (VPN), or private management network) is in place.
Ensure that management access is secured using appropriate firewall policies, trusted source IPs, and authentication mechanisms.
There will now be two MVEs deployed.
**Creating a VXC for FGSP session synchronization**
Now that the FortiGate MVEs have been created, the next step is to create a private VXC for FGSP session synchronization between the two devices.
Unlike traditional HA implementations, Fortinet FGSP requires a single reliable network path between peers to synchronize session state. This path must be direct, routable, and free of NAT.
Use the dedicated FGSP interface on each MVE (vNIC 2 in this example) and connect it to the same interface on the peer MVE:
* Create a private VXC between vNIC 2 on MVE 1 and vNIC 2 on MVE 2.
* Configure both ends of the VXC as untagged (no VLAN).
**To create a VXC between MVEs**
1. In the Megaport Portal, go to the **Services** page.
2. Create a VXC between the two FortiGate MVEs as described in [Connecting MVEs Integrated with Fortinet Secure SD-WAN](/mve/fortinet/connect-mve-to-mve).
### Configuring FGSP in FortiGate OS
Now that the underlying infrastructure has been created and configured in the Megaport Portal, the FortiGate firewalls need to be configured for FGSP session synchronization.
The management web interface for each firewall can be accessed via the IP of the VXC attached to the management vNIC (vNIC 0). You can find the IP address on the Details tab of the VXC in the Megaport Portal.
This section describes the configuration of FGSP on FortiGate OS. This example is based on FortiOS 7.6.x and should be used as an example only. Modifications might be required depending on your environment, network design, or future updates released by Fortinet.
For more information about configuration options, supported session types, and recommended practices, see the [Fortinet FGSP documentation](https://docs.fortinet.com/document/fortigate/7.6.5/administration-guide/668583/fgsp).
**Allowing access to each FortiGate MVE**
Follow the FortiGate set up and configuration steps in [Creating an MVE Integrated with Fortinet](/mve/fortinet/creating-mve).\
You can now connect to the management interface of each MVE using the IP of the VXC attached to vNIC 0 (Management).
**Configure the FGSP interface**
To configure FGSP session synchronization, select the interface dedicated to FGSP traffic, such as vNIC 2 (or port 3 in FortiOS), depending on the MVE interface mapping. This interface must be configured with a static IP address that is directly reachable by the peer FortiGate.
The FGSP interface must be routable end-to-end, must not use NAT, and must provide direct IP connectivity between both FortiGate peers. This interface is used exclusively for FGSP session synchronization traffic and should not be shared with management or data plane traffic, in accordance with Fortinet best practices.
For more information about configuring the FGSP interface, see the [FortiGate FGSP documentation](https://docs.fortinet.com/document/fortigate/7.6.5/administration-guide/668583/fgsp).
**Enable FGSP and set peer**
To enable FGSP and define the synchronization peer, open a CLI session on the FortiGate using either the GUI console or an SSH connection. Configure FGSP by specifying the IP address of the peer FortiGate on the dedicated FGSP interface. This configuration establishes the session synchronization relationship between the two FortiGate devices and allows session state information to be exchanged over the FGSP link.
For more detailed information, see the [FGSP basic peer setup](https://docs.fortinet.com/document/fortigate/7.6.5/administration-guide/869218/fgsp-basic-peer-setup).
For example:
```
config system standalone-cluster
set standalone-group-id 1
set group-member-id 1
set session-sync-dev "port3"
config cluster-peer
edit 1
set peerip 10.0.0.2
set syncvd "root"
next
end
end
```
**Configure session pickup options**
After configuring FGSP and setting the peer, enable session pickup globally to ensure that active TCP sessions are synchronized between the FortiGate peers.
If required, additional session types can also be synchronized, including connectionless traffic such as UDP and ICMP, NATed sessions, and expectation sessions used by protocols like SIP, H.323, or other VoIP applications. Enabling these options ensures that the surviving FortiGate can continue handling existing sessions seamlessly in the event of a failover.
For more information, see the Session pickup section of [FGSP basic peer setup](https://docs.fortinet.com/document/fortigate/7.6.5/administration-guide/869218/fgsp-basic-peer-setup).
For example:
```
config system ha
set session-pickup enable
set session-pickup-connectionless enable
set session-pickup-expectation enable
set session-pickup-nat enable
set standalone-config-sync enable
end
```
## Verify FGSP connectivity
After configuring FGSP, ensure that the dedicated FGSP interface on each FortiGate can reach its peer directly. Use the CLI to check the FGSP status and confirm that sessions are being synchronized properly.
Typical indicators of a functional FGSP connection include the following metrics:
* `sync_started=1` -- shows that the session synchronization mechanism has started.
* `standalone_sesync=1` -- indicates that the FortiGate is operating in standalone cluster mode
* `send=770` and `recv=764` -- packet counters which confirm that communication between the two FortiGate peers is occurring.
By verifying these metrics, you can confirm that FGSP is active and capable of maintaining session continuity during a failover.
For example:
```
#diagnose sys session sync
sync_ctx: sync_started=1, sync_tcp=1, sync_others=1,
sync_expectation=1, sync_nat=1, stdalone_sesync=1, asymmetric_traffic_control=0.
help_traffic_bounce=1, utm_traffic_bounce=1
sync: create=4:0, update=8, keepalive=0, delete=0:0, query=2, keepalive_query=0
recv: create=7:0, update=20, keepalive=1, delete=0:0, query=1
ses pkts: send=3675, alloc_fail=0, recv=3163, recv_err=0, sz_err=0,
…
sync_filter:
1: vd=0, szone=0, dzone=0, saddr=0.0.0.0:0.0.0.0, daddr=0.0.0.0:0.0.0.0, sport=0-65535, dport=0:65535, peerid=2, peervd=0, peerip=10.0.0.2
```
You can also verify session synchronization by running the following commands:
* `diagnose sys session list` -- to view active sessions
* `diagnose sys session stat` -- to see session statistics and counters, which further confirm that sessions are being replicated between peers.
### Creating data plane connections
Now that the FortiGate MVEs are deployed and the FGSP session synchronization is configured, the next step is to create data plane VXCs to connect the networks you want to route between.
The data plane VXCs will be attached as tagged VLAN subinterfaces of the data plane interface (for example, vNIC 1 / Port 2). The relevant subinterfaces and BGP peers (or routing configurations) will be configured within the FortiGate firewalls.
In this example, we’ll connect AWS and GCP, but the same process can be applied to any networks reachable via a VXC. Some tasks are performed in the Megaport Portal, and others within FortiGate OS.
**Create VXCs**
The VXCs are created in the Megaport Portal using the standard process as described in [Connections Overview](/connections/overview), specifying vNIC-1/Port 2 for the A-End vNIC and configuring the VXC to be delivered as a tagged VLAN.
Connections to the same destination should be created on both MVEs and delivered with or without being on the same VLAN. In this example, the Cloud1 VXC (to GCP) will be configured as VLAN 10 on MVE1 and VLAN 11 on MVE2, and the Cloud2 VXC (to AWS) will be configured as VLAN 20 on MVE1 and VLAN 21 on MVE2.
After the VXCs have been created, both MVEs should look similar to the image below.
### Configuring interfaces
Now configure the data plane interfaces for the VXCs delivered from Megaport.\
For each VXC, create a VLAN subinterface under the data plane interface, such as vNIC 1 - Port 2. Assign the VLAN ID provided by Megaport and configure the appropriate IP addresses for the subinterfaces according to your network design.
For more information, see [FortiGate documentation for interface settings](https://docs.fortinet.com/document/fortigate/7.6.5/administration-guide/574723/interface-settings).
**Configure BGP**
is used to distribute and manage routes automatically between the FortiGate MVEs and the connected networks. Each firewall can have different BGP peer addresses and traffic engineering settings.
The virtual router or BGP instance configuration is not synchronized by FGSP, so it must be configured individually on both FortiGate peers.
For detailed information about configuring BGP, see the [FortiGate BGP documentation](https://docs.fortinet.com/document/fortigate/7.6.5/administration-guide/750736/bgp).
BGP manages traffic failover between MVEs while FGSP ensures that active sessions remain synchronized across both devices during a failover. In most cases, enabling Bidirectional Forwarding Detection (BFD) on the BGP peers is recommended to improve failover recovery time. For more information about BFD, see [BFD Overview](https://docs.fortinet.com/document/fortigate/7.6.5/administration-guide/771813/bfd).
FGSP does not handle traffic forwarding; it only replicates session state, so the routing and failover of traffic are managed by BGP, SD-WAN, or any routing policies.
**Configure failover conditions**
Although FGSP has been configured to synchronize sessions between FortiGate peers, and upstream networks or SD-WAN will redirect traffic to the surviving device in the event of an outage, each firewall and connected network endpoint still needs to know when to consider a peer or path down and how to redirect traffic appropriately.
Failover optimization can be achieved through a combination of mechanisms. BGP with BFD provides rapid route convergence and failover at the routing level. Link monitoring and SD-WAN link health monitoring allow each FortiGate to detect failures on VXCs, cloud connections, or WAN paths and trigger traffic rerouting. In addition, custom scripts or automation can be applied to enforce specific policies or perform additional checks. These mechanisms are not limited to the FortiGate gateways using FGSP; they can also be applied on remote sites or endpoints to improve overall resilience and reduce downtime during failover.
FGSP ensures that active sessions synchronized to the surviving peer are maintained during a failover, but it does not handle traffic redirection itself. Unlike traditional active/passive HA clusters, failover in MVE deployments relies on upstream routing, BGP path monitoring, SD-WAN orchestration, and optional automation to redirect traffic while preserving session continuity. Proper configuration of these mechanisms across both gateways and remote endpoints ensures uninterrupted traffic flow and maximizes network availability.
**Review the configuration status**
Now that everything is in place and configured, there are a few ways that you can confirm everything is working as expected:
* All MVEs and VXCs in Megaport Portal should show as live and active.
* Both firewalls should have BGP sessions established and should be exchanging routes with their peers.
* Routes for your networks should be present in the routing table and Local Routing Information Base (RIB) of each firewall.
* Both peers should show as up and reachable, confirming that failover detection at the routing level is operational.
* Session states should be continuously synchronized between the two FortiGate peers. Each device should maintain an up-to-date view of active sessions, ensuring that traffic can continue uninterrupted if one peer becomes unreachable.
* Each firewall should correctly monitor the relevant paths using link monitoring or SD-WAN health checks. While the FortiGate MVE operate in standalone mode and do not enter a failover state, verifying that traffic is correctly routed via available paths ensures continuity of network flows.
By verifying MVEs/VXCs, BGP, routes, FGSP session sync, and path monitoring, you can confirm that both traffic forwarding and session continuity are functioning correctly across the FGSP deployment.
# Fortinet FortiGate with Megaport Virtual Edge
Source: https://docs.megaport.com/mve/fortinet/index
This help topic describes Fortinet FortiGate with Megaport MVE functionality.
Fortinet FortiGate creates the private overlay network and manages the network connections and network policies. The Megaport Portal is used to create and order the MVE and create and manage the Virtual Cross Connects (VXCs) to the cloud on-ramps and other services in the Megaport SDN. The Fortinet FortiGate fabric acts as the overlay, and the Megaport SDN acts as the underlay.
Fortinet offers several management system options. For simplicity, this documentation describes deployments using the FortiManager console.
The following diagram shows an example network implementation of Fortinet FortiGate features over the Megaport network.
# Planning Your Fortinet FortiGate Deployment
Source: https://docs.megaport.com/mve/fortinet/plan-deployment
This help topic describes Fortinet FortiGate deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
| **You Provide** | **Megaport Provides** |
| - | - |
| Internet connection from branch | Platform to host virtualized network function (VNF) appliances |
| VNF vendor enabled at branch | Complete connection from a branch to any destination on the Megaport network and interoperation with other Megaport products and services |
| Customer premises equipment (CPE) installed in branch | Megaport Internet connection to terminate the tunnel between MVE and CPE at branch via internet |
| VNF software license to use on Megaport SDN | Access to the Megaport ecosystem |
## Fortinet FortiGate features
The FortiGate-VM delivers both NGFW and SD-WAN services on a single virtual machine. Hosting the FortiGate-VM on MVE not only optimizes edge-to-cloud network connectivity, but also enforces advanced security services and policies across the Megaport backbone segments.
Embedding the FortiGate-VM into Megaport's NaaS platform extends the following core elements between the edge and cloud network fabric:
* Next-generation firewall (NGFW), including stateful firewall policies, network address translation (NAT), intrusion protection services, Secure Sockets Layer (SSL) inspection, and threat intelligence.
* Secure web gateway (SWG) services protect devices from malicious internet destinations using web content filtering and malware scanning.
* Zero trust network access (ZTNA), which controls access to applications by verifying users and devices before every application session and confirms that they meet the organization's policy to access that application.
The FortiGate-VM also supports remote user integration with Fortinet SASE solutions using their FortiClient endpoint security agent. The FortiClient enables the device to connect securely to the security fabric over either VPN (SSL or IPsec) or ZTNA tunnels.
The FortiSASE solution allows both the FortiGate and FortiCloud services to be used in a blended design as well. For example, internet and select applications might be protected using both SWG and a cloud access security broker (CASB) through FortiCloud, while private Megaport connections are protected using FortiGate security services.
If you have already deployed a Fortinet firewall, you can connect it to an MVE so that your headquarters or branches can access cloud services over private interconnects.
For more information about these features, see:
* [Fortinet Documentation Library](https://docs.fortinet.com/)
* [FortiGate VM on Linux KVM](https://www.fortinet.com/content/dam/fortinet/assets/data-sheets/FortiGate_VM_KVM.pdf)
* [FortiGuard Security Services](https://www.fortinet.com/content/dam/fortinet/assets/data-sheets/FortiGuard_Security_Services.pdf)
## Deployment considerations
This section provides an overview of the MVE deployment options and features.
Fortinet FortiGate uses virtual FortiGate appliances or physical FortiGate appliances much like many other VNF vendors. However, with Fortinet, you can configure the appliances for several different uses. For example, you can configure a Fortinet appliance for use:
* Strictly as a next-generation firewall (NGFW) for remote offices with local configuration and local logging only.
* As central management with central logging, or as central management without central logging.
* In a traditional SD-WAN style overlay network.
For more information, see the [Fortinet Documentation Library](https://docs.fortinet.com/).
### VNF appliance vendors integrated with MVE
MVE is integrated with Fortinet FortiGate, which uses the Fortinet FortiManager console to create the private overlay network.
For information about all supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Fortinet FortiGate-VM**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* You can provision another MVE instance, add it to your overlay network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, add it to your overlay network, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### Security
MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN. CSP-hosted instances of partner SD-WAN products route critical traffic across the Megaport SDN, reducing internet dependence. Traffic remains encrypted and under your policy control while traveling across the Megaport SDN, to or from, MVE.
Fortinet FortiGate includes access to a comprehensive security feature: . Fortinet on MVE natively supports SASE and SD-WAN services. For more information, see [SSE and SASE within the Megaport Network](/mve/sase).
### Licensing
You bring your own Fortinet (FortiGate) SD-WAN license for use with MVE. It is your responsibility to have the appropriate licenses for the SD-WAN endpoints created on the Megaport network.
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
### vNICs
Each MVE can have up to five vNICs. An MVE is created with one vNIC by default. You can add up to four more, making a total of five.
Before specifying the number of vNICs on your MVE:
* Be aware that the number of vNICs cannot be changed after an MVE has been ordered. Decide in advance how many vNICs to specify when you create the MVE.
* Consult your service provider to make sure that functionality won't be affected if you add a vNIC.
If you need to change the number of vNICs after an MVE has been ordered, you will have to cancel and re-order the MVE.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
# Terminating an MVE
Source: https://docs.megaport.com/mve/fortinet/terminating-mve
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window appears, displaying a list of services connected to the MVE. Early termination fees are shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use your SD-WAN management console to delete the MVE.
# Connecting MVEs Integrated with Juniper
Source: https://docs.megaport.com/mve/juniper/connect-mve-to-mve
This help topic describes how to connect two Megaport Virtual Edges (MVEs) integrated with Juniper.
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with Juniper to another MVE.
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer / partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [the relevant Juniper product](/mve/juniper).
## Creating a VXC between two MVEs
A private VXC deployment between two MVEs integrated with Juniper starts in the Megaport Portal. To complete the configuration, you use the Juniper Mist platform.
**To create a VXC**
1. In the Megaport Portal, go to the
**Services** page and click **+Connection** next to the originating A-End MVE.
2. Select Private VXC.
3. Select the destination B-End MVE and location.\
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `Dallas MVE 4 to LA MVE 2`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. For more information, see the Juniper documentation.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **vNIC selection** -- Depending on the definition of the MVEs you are using, you might have to specify A-End and B-End vNICs.
* **A-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
* **B-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
For more information about vNIC selection when connecting MVEs with different services, see [Types of vNIC Connections](/mve/vnic-connections).
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.\
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. 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 through the B-End VLAN.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Click **Add VXC** to move this configuration to your cart.
8. Repeat these steps to provision any additional VXCs.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs on the Juniper side. For more information about specific network design and configuration options before configuring interfaces for the MVEs, see the [Juniper Documentation](https://www.juniper.net/documentation/).
# Creating an MVE with Juniper SSR
Source: https://docs.megaport.com/mve/juniper/creating-mve-juniper-ssr
This help topic describes how to create and configure Megaport Virtual Edge (MVE) with Juniper Session Smart Router.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Juniper Session Smart Router (SSR).
## Basic steps
This section summarizes the configuration steps using the Megaport Portal. Detailed procedures follow this basic step summary.
The basic steps are:
* Obtain a license from Juniper.
* Generate a registration code in your Juniper Mist platform.
* Create the Juniper SSR MVE in the Megaport Portal.
* Ensure that the connection has been established on the Juniper Mist platform.
## Licensing
Before you create an MVE in the Megaport Portal, you need a valid Juniper license.
To obtain or manage a Juniper license, see the [Juniper Licensing User Guide](https://www.juniper.net/documentation/us/en/software/license/juniper-licensing-user-guide/index.html) or contact your Megaport Sales Representative for guidance.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/juniper/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also typically create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Juniper SSR**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Juniper.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Juniper-specific settings:
* **Registration Code** -- Copy and paste the registration code generated from the Juniper Mist platform.
When copying the registration code from Juniper Mist, do not copy the entire output shown in the Mist UI. The Mist output includes CLI commands at the top, for example, `configure authority mist-wan-assurance registration-code`. If these commands are included in the Registration Code field, the MVE deployment fails due to a syntax error.
Copy only the alphanumeric registration code from the lower portion of the Mist output and paste it into the Megaport Portal.
* **Virtual Interfaces (vNICs)** -- Each MVE for Juniper SSR can be configured with one to five vNICs.
Megaport recommends a minimum configuration of three vNICs:
* 0: Management
* 1: WAN
* 2: LAN
To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed.
You can add a total of five vNICs to the MVE. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Enter a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with Juniper SSR. The network is managed through the Juniper Mist platform, which provides centralized management and control for secure connectivity between branch locations and cloud/data center endpoints using Secure Vector Routing (SVR).
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select **vNIC-0** for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the Juniper SSR appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up a Juniper SSR instance.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/juniper/creating-mve-vxc).
# Creating an MVE with Juniper vSRX
Source: https://docs.megaport.com/mve/juniper/creating-mve-juniper-vsrx
This help topic describes how to deploy Juniper vSRX next-generation virtual firewall on Megaport Virtual Edge (MVE).
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Juniper vSRX .
## Basic steps
This section summarizes the configuration steps using the Megaport Portal. Detailed procedures follow this basic step summary.
The basic steps are:
* Obtain a license from Juniper.
* Generate an SSH key pair for authentication.
* Create the Juniper vSRX MVE in the Megaport Portal.
* Ensure that the connection has been established on the Juniper Mist platform.
## Licensing
Before you create an MVE in the Megaport Portal, you need a valid Juniper license.
To obtain or manage a Juniper license, see the [Juniper Licensing User Guide](https://www.juniper.net/documentation/us/en/software/license/juniper-licensing-user-guide/index.html) or contact your Megaport Sales Representative for guidance.
## Administrative access to MVE
You connect your MVE through a public/private SSH key pair to establish a secure connection. The public SSH key allows you to use SSH to access the MVE and perform administrative tasks, such as setting the administrative password, enabling HTTPS access, and optionally registering the MVE to your management platform.
Megaport supports the 2048-bit RSA key type.
**To generate an SSH key pair (Linux/Mac OSX)**
* Enter the SSH keygen command in the terminal.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ssh-keygen -f ~/.ssh/megaport-mve-instance-1-2048 -t rsa -b 2048
```
The key generator command creates an SSH key pair and adds two files to your \~/.ssh directory:
* **megaport-mve-instance-1-2048** - contains the private key.
* **megaport-mve-instance-1-2048.pub** - contains the public key that is authorized to log in to the vendor account.
**To generate an SSH key pair (Windows, using [PuTTYgen](https://www.puttygen.com))**
1. Open PuTTYgen.
2. In the Key section, choose RSA 2048 bit and click **Generate**.
3. Move your mouse randomly in the small screen to generate the key pairs.
4. Enter a key comment to identify the key.\
This is convenient when you use several SSH keys.
5. Enter a Key passphrase, and re-enter to confirm.\
The passphrase is used to protect your key. You will be asked for it when you connect via SSH.
6. Click **Save private key**, choose a location, and click **Save**.
7. Click **Save public key**, choose a location, and click **Save**.
You will copy and paste the contents of the public key file in the Megaport Portal later to distribute the public key to the MVE. Your private key will match the public key to grant access. Only a single private key has access to the MVE for SSH access.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/juniper/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also typically create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Juniper vSRX**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Juniper vSRX.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Juniper vSRX-specific settings:
* **Admin Password** -- Specify a temporary administrator password that you will use to access the virtual device. The password must be a minimum of 8 characters and include:
* 1 uppercase character (A-Z)
* 1 lowercase character (a-z)
* 1 number (0-9)
* 1 symbol
Store the admin password securely and do not share it with anyone. You can reset the admin password at the first login into the configured device.
Megaport does not store customer passwords.
* **SSH Key** -- Copy and paste the contents of your public SSH key here. You can find the public key in the **megaport-mve-instance-1-2048.pub** file generated earlier.
* **Mist SSH Public Key** (optional) -- Paste a 3072-bit RSA SSH public key for Juniper Mist management access. This key is separate from the 2048-bit SSH key used for MVE administrative access in the previous field, and is only required if you plan to manage the vSRX through Juniper Mist.
The Mist controller fields (**Mist SSH Public Key**, **Mist Password**, **Mist Device ID**, and **Mist Secret**) are optional. However, if you enter a value for any one of these fields, you must complete all four. Leave all four fields empty if you don't need Juniper Mist management.
Generate the Mist SSH key pair using the same process as the 2048-bit administrative key (see [Administrative access to MVE](#administrative-access-to-mve)), but use a 3072-bit key length and save it to a separate file. For example, on Linux or macOS you can run:
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ssh-keygen -f ~/.ssh/megaport-mve-instance-1-mist-3072 -t rsa -b 3072
```
On Windows, you can generate the key using [PuTTYgen](https://www.puttygen.com) by selecting **RSA 3072 bit** and clicking **Generate**, then copying the key from the field labeled *Public key for pasting into OpenSSH authorized\_keys file*.
Paste the contents of the resulting **.pub** file (or the PuTTYgen output) into this field and store the matching private key securely, as you need it to authenticate to the device through Juniper Mist.
* **Mist Password** (optional) -- Specify the Mist password from your Juniper Mist platform.
* **Mist Device ID** (optional) -- Specify the Mist Device ID from your Juniper Mist platform.
* **Mist Secret** (optional) -- Specify the Mist Secret from your Juniper Mist platform.
* **Virtual Interfaces (vNICs)** -- Each MVE for Juniper vSRX deploys with a minimum of two vNICs named *Management* and *Data Plane* by default. You can add up to three more, for a total of five. To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Enter a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to communicate with Juniper systems.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select the management vNIC for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the Juniper vSRX appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/juniper/creating-mve-vxc).
# Creating a VXC to an MVE Integrated with the relevant Juniper product
Source: https://docs.megaport.com/mve/juniper/creating-mve-vxc
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE) integrated with Juniper.
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with Juniper.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.\
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
For specific configuration details, see [Connecting MVE to MVE](/mve/juniper/connect-mve-to-mve).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/juniper/terminating-mve).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# Juniper with Megaport Virtual Edge
Source: https://docs.megaport.com/mve/juniper/index
This help topic describes Juniper with Megaport Virtual Edge (MVE) functionality.
Juniper's network solutions deliver advanced routing, security, and SD-WAN capabilities for modern enterprise connectivity. By integrating Juniper products with Megaport's MVE, enterprises gain access to powerful networking capabilities on Megaport's global private SDN.
Megaport provides the network underlay, while Juniper manages routing policies and secure communications across clouds, external networks, and data centers. You use the Megaport Portal to create and order MVE instances and establish Virtual Cross Connects (VXCs) to cloud on-ramps and other services, with Juniper delivering sophisticated overlay networking capabilities for resilient and secure connectivity.
## Juniper Session Smart Router (SSR)
Juniper SSR on MVE redefines SD-WAN deployment by removing the complexity of traditional tunnel-based overlays. It reduces operational burden while providing enhanced security and application performance across Megaport's global private network.
Using Secure Vector Routing (SVR), Juniper SSR creates dynamic, session-aware connections with built-in security that simplify network management and optimize application performance across distributed sites and multicloud environments.
When you create a Juniper SSR MVE in the Megaport Portal, the instance is deployed and managed through the Juniper Mist platform.
The following diagram shows an example network implementation of Juniper SSR features over the Megaport network.
## Juniper vSRX
Juniper vSRX on MVE lets you deploy Juniper’s directly on the Megaport network. This removes the need for physical hardware, shipping delays, and data center rack space.
By enforcing security policies at the network edge, the vSRX inspects and processes traffic closer to its source. This reduces latency and avoids the need to route traffic through a centralized security hub before reaching its destination.
## Helpful references
* [Juniper Mist Support and Documentation](https://www.juniper.net/documentation/product/us/en/mist/)
* [Juniper SSR Documentation](https://www.juniper.net/documentation/product/us/en/session-smart-router/)
* [Juniper vSRX Documentation](https://www.juniper.net/documentation/product/us/en/vsrx/)
# Planning Your Juniper Deployment
Source: https://docs.megaport.com/mve/juniper/plan-deployment
This help topic describes Juniper deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
| **You Provide** | **Megaport Provides** |
| - | - |
| Internet connection from branch | Platform to host virtual SD-WAN appliances |
| SD-WAN vendor enabled at branch | Complete connection from a branch to any destination on the Megaport network and interoperation with other Megaport products and services |
| Customer premises equipment (CPE) installed in branch | Megaport Internet connection to terminate the tunnel between MVE and CPE at branch via internet |
| SD-WAN software license to use on Megaport SDN | Access to the Megaport ecosystem |
## Deployment considerations
This section provides an overview of the MVE deployment options and features.
### Juniper products
Juniper Session Smart Router (SSR) delivers advanced routing capabilities, using Secure Vector Routing (SVR) to remove the complexity of traditional tunnel-based overlays. With session-aware routing, enhanced security, and simplified operations through cloud-based management on the Juniper Mist platform, the SSR provides a smarter approach to SD-WAN.
Juniper vSRX is a virtualized that provides the security capabilities of Juniper’s physical SRX Series platforms on Megaport's global private network.
For information about all supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **the relevant Juniper product**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* You can provision another MVE instance, add it to your SD-WAN overlay network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, add it to your SD-WAN overlay network, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### Security
MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN. CSP-hosted instances of partner SD-WAN products route critical traffic across the Megaport SDN, reducing internet dependence. Traffic remains encrypted and under your policy control while traveling across the Megaport SDN, to or from, MVE.
### Licensing
You bring your own Juniper license for use with MVE. Licensing requirements vary depending on the Juniper product you deploy.
Juniper licensing is subscription-based and managed through Juniper's licensing portal. You will need valid subscriptions based on your deployment size and feature requirements.
For more information, discuss licensing with your Account Manager and see the [Juniper Licensing User Guide](https://www.juniper.net/documentation/us/en/software/license/juniper-licensing-user-guide/index.html) or contact Juniper support.
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
### vNICs
Each MVE can have up to five vNICs. The number and default configuration of vNICs varies by Juniper product.
**Juniper SSR**: Each MVE for Juniper SSR is configured with three vNICs by default. Megaport recommends a minimum configuration of three vNICs:
* 0: Management
* 1: WAN
* 2: LAN
**Juniper vSRX**: Each MVE for Juniper vSRX deploys with two vNICs by default. You can add up to three more, for a total of five. The default vNICs are:
* 0: Management
* 1: Data Plane
Before specifying the number of vNICs on your MVE:
* Be aware that the number of vNICs cannot be changed after an MVE has been ordered. Decide in advance how many vNICs to specify when you create the MVE.
* Consult your service provider to make sure that functionality won't be affected if you add a vNIC.
If you need to change the number of vNICs after an MVE has been ordered, you will have to cancel and re-order the MVE.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
# Terminating an MVE
Source: https://docs.megaport.com/mve/juniper/terminating-mve
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window appears, displaying a list of services connected to the MVE. Early termination fees are shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use your Juniper management console to delete the MVE.
# MVE Frequently Asked Questions (FAQs)
Source: https://docs.megaport.com/mve/mve-faqs
This help topic provides answers to common questions about Megaport Virtual Edge (MVE).
### Is MVE an SD-WAN or Firewall product?
No, MVE is not an SD-WAN or Firewall product, but an enabler of the two. It is an on-demand platform that enables the use of an SD-WAN or Firewall service to be activated as a Virtual Network Function (VNF), assuming the customer owns a license for the VNF.\
In short, MVE provides the compute and the connectivity, whilst the customer must bring their own SD-WAN or Firewall license.
### Do I need to buy an internet connection to use MVE?
Most of the VNFs qualified to work with the MVE will use the public internet to communicate with the management platform, therefore having an internet connection attached to the MVE is very important. We recommend that you purchase a Megaport Internet connection with the initial MVE order, which will provide the internet connectivity required to authenticate/validate the license of the VNF and establish the communication with the management platform.
### Can I bring my own internet connection?
Yes, but you need to get the confirmation from one of our Solution Architects. For example, you might have to allocate the public IP address using DHCP.
### How does IP addressing work on MVE?
Included within the subscription for each MVE is a unique, dedicated, publicly accessible IP address that can be entered as a Domain Name Server (DNS) "A record" within the customer DNS for ease of use. This IP address will persistently be associated with the MVE for the duration of its life.
### Can two MVEs reach each other over the public internet?
Yes, there is no restriction in exchanging traffic between two MVEs over the internet.
### How does MVE work with, or compare to, the MCR?
Megaport Cloud Router (MCR) and MVE are complementary products that serve different needs.
MCR is a virtual BGP router that resides within the Megaport SDN. MCR configuration is optimized for enterprise-to-cloud or connections. MCR is ideal when customers are already present in a data center connected to the Megaport SDN or only need cloud-to-cloud connectivity. MCR is a standalone product, which is individually configured and operated.
MVE resides at the edge of the Megaport SDN. It provides access to the Megaport SDN for customers not already present within a data center. MVE configuration is done within both the Megaport Portal and the partner SD-WAN management console (details depend on your SD-WAN provider).
MVE and MCR are both subscription services, and can be used separately or together.
### Does MVE displace MCR?
No, MVE doesn't displace MCR.
### How is pricing structured?
MVEs are available in multiple sizes with recurring monthly flat fees. These fees include the compute (vCPUs, RAM, Storage) required for the VNF to work.
In addition to the compute, customers can create a Megaport Internet connection which provides the connectivity. Megaport Internet bandwidth is adjustable from 20 Mbps to several Gbps, so the price of the Megaport Internet connction will be a flat monthly recurring charge depending on the amount of selected bandwidth. Megaport Internet connections will be charged separately to the MVE compute.
These fees include the MVE, public IP address, and internet connectivity. Megaport Internet costs might differ by market. VXCs between MVEs or other resources are billed separately. You can choose a pay-as-you-go or contract term pricing model. For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
### Can I bring my own license?
Yes, in fact this is a must if you want to use MVE. Just be aware that the license needs to match the image/software version supported by Megaport.
### What is a vNIC?
A vNIC is a virtual network interface which customers can use to run VXC.
### How many vNICs can be enabled per MVE?
Up to five vNICs can be ordered per MVE dependant on vendor.
### Does a vNIC have a maximum speed that can be supported?
vNICs do not have a speed limit, but the VXCs that connect to the vNICs do.
### Can I order more vNICs after I have activated the MVE?
No, unfortunately you won’t be able to order more vNICs, even if you didn’t reach the limit of 5. The only way to use more vNICs is to reorder the MVE.
### Can I change the name of the vNIC?
Yes, you can change the name of the vNIC to anything you want. We recommend that you use names that are meaningful for the purpose of the vNIC.
You can also change the vNIC name later, after the MVE has been deployed.
### How much is the charge for a vNIC?
You can order up to five vNICs per MVE at no extra cost.
### Can I cancel/remove a vNIC after I activate the MVE?
No, the only way to change the number of vNICs available is to reorder the MVE.
### Will I break anything if I order all five vNICs from day one?
We strongly recommend that you get in touch with your license supplier to understand if adding more vNICs will affect the correct functionality of the image (SD-WAN or FWaaS).
# Connecting MVEs Integrated with Netskope One SD-WAN
Source: https://docs.megaport.com/mve/netskope/connect-mve-to-mve
This help topic describes how to connect two Megaport Virtual Edges (MVEs) integrated with Netskope One SD-WAN.
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with Netskope One SD-WAN to another MVE.
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer / partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [Creating an MVE Integrated with Netskope One SD-WAN](/mve/netskope/creating-mve-netskope).
## Creating a VXC between two MVEs
A private VXC deployment between two MVEs integrated with Netskope One SD-WAN starts in the Megaport Portal. To complete the configuration, you use the Netskope One portal.
**To create a VXC**
1. In the Megaport Portal, go to the
**Services** page and click **+Connection** next to the originating A-End MVE.
2. Select Private VXC.
3. Select the destination B-End MVE and location.\
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `Dallas MVE 4 to LA MVE 2`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. For more information, see the [Netskope documentation](https://docs.netskope.com/).
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **vNIC selection** -- Depending on the definition of the MVEs you are using, you might have to specify A-End and B-End vNICs.
* **A-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
* **B-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
For more information about vNIC selection when connecting MVEs with different services, see [Types of vNIC Connections](/mve/vnic-connections).
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.\
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. 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 through the B-End VLAN.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Confirm the configuration and click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs on the Netskope side. For more information about specific network design and configuration options before configuring interfaces for the MVEs, see the [Netskope documentation](https://docs.netskope.com/).
# Creating an MVE Integrated with Netskope One SD-WAN
Source: https://docs.megaport.com/mve/netskope/creating-mve-netskope
Learn how to deploy Netskope One SD-WAN on Megaport Virtual Edge (MVE), enabling SASE capabilities without physical hardware.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Netskope One SD-WAN.
## Basic steps
This section summarizes the configuration steps using the Megaport Portal. Detailed procedures follow this basic step summary.
The basic steps are:
* Obtain a license and portal access from Netskope.
* (Optional) Generate an activation token and URI in the Netskope One portal.
* Generate an SSH key pair for authentication.
* Create the Netskope One SD-WAN MVE in the Megaport Portal.
* Verify activation in the Netskope One portal.
## Licensing
Before you create an MVE in the Megaport Portal, you need a valid Netskope One SD-WAN license and access to the Netskope One portal.
For more information about obtaining a Netskope license, see the [Netskope website](https://www.netskope.com/) or contact your Megaport Sales Representative for guidance.
## Administrative access to MVE
You connect your MVE through a public/private SSH key pair to establish a secure connection. The public SSH key allows you to use SSH to access the MVE and perform administrative tasks, such as setting the administrative password, enabling HTTPS access, and optionally registering the MVE to your management platform.
Megaport supports the 2048-bit RSA key type.
**To generate an SSH key pair (Linux/Mac OSX)**
* Enter the SSH keygen command in the terminal.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ssh-keygen -f ~/.ssh/megaport-mve-instance-1-2048 -t rsa -b 2048
```
The key generator command creates an SSH key pair and adds two files to your \~/.ssh directory:
* **megaport-mve-instance-1-2048** - contains the private key.
* **megaport-mve-instance-1-2048.pub** - contains the public key that is authorized to log in to the vendor account.
**To generate an SSH key pair (Windows, using [PuTTYgen](https://www.puttygen.com))**
1. Open PuTTYgen.
2. In the Key section, choose RSA 2048 bit and click **Generate**.
3. Move your mouse randomly in the small screen to generate the key pairs.
4. Enter a key comment to identify the key.\
This is convenient when you use several SSH keys.
5. Enter a Key passphrase, and re-enter to confirm.\
The passphrase is used to protect your key. You will be asked for it when you connect via SSH.
6. Click **Save private key**, choose a location, and click **Save**.
7. Click **Save public key**, choose a location, and click **Save**.
You will copy and paste the contents of the public key file in the Megaport Portal later to distribute the public key to the MVE. Your private key will match the public key to grant access. Only a single private key has access to the MVE for SSH access.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/netskope/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you typically also create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Netskope One SD-WAN**.
4. Select the software version.
This selection determines the version of Netskope One SD-WAN that runs on the MVE.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone is displayed on the location details through the rest of the provisioning, and on the Summary page.
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Netskope One SD-WAN-specific settings:
* **SSH Key** -- Copy and paste the contents of your public SSH key here. You can find the public key in the **megaport-mve-instance-1-2048.pub** file generated earlier.
* **Admin Password** -- Specify a temporary administrator password that you use to access the virtual device. The password must be a minimum of 8 characters and include:
* 1 uppercase character (A-Z)
* 1 lowercase character (a-z)
* 1 number (0-9)
* 1 symbol
Store the admin password securely and do not share it with anyone. You can reset the admin password at the first login into the configured device.
Megaport does not store customer passwords.
* **Virtual Interfaces (vNICs)** -- Each MVE is configured with one vNIC named *WAN, LAN, Mgmt* by default. To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed.
You can add a total of five vNICs to the MVE. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Specify a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you must delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Activation Token** (optional) -- Enter the activation token for your Netskope SD-WAN service. These credentials are provided by Netskope when your SD-WAN service is provisioned. Contact your Netskope administrator if you have not received them.
If you enter an activation token, you must also enter an activation URI. Both fields must be filled together, or both can be left empty.
* **Activation URI** (optional) -- Enter the activation URI for your Netskope SD-WAN service. This value is provided alongside the activation token when your service is provisioned.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Specify a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
The portal prompts you to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to activate and communicate with Netskope One.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic does not flow through this service and it behaves as if it is down on the Megaport network. Billing for this service remains active and you are still charged for this connection.
* **A-End vNIC** -- Select the vNIC for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to order the connection.
7. Click **Review Order** in the Configured Services area.
8. If you have a promotional code, click **Add Promo Code**, enter it, then click **Add Code**.
9. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up a Netskope One SD-WAN instance.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/netskope/creating-mve-vxc).
# Creating a VXC to an MVE Integrated with Netskope One SD-WAN
Source: https://docs.megaport.com/mve/netskope/creating-mve-vxc
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE) integrated with Netskope One SD-WAN.
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with Netskope One SD-WAN.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.\
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
For specific configuration details, see [Connecting MVE to MVE](/mve/netskope/connect-mve-to-mve).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/netskope/terminating-mve).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# Netskope One SD-WAN with Megaport Virtual Edge
Source: https://docs.megaport.com/mve/netskope/index
This help topic describes Netskope One SD-WAN with Megaport MVE functionality.
Netskope One SD-WAN on Megaport's MVE delivers secure access service edge (SASE) capabilities directly on Megaport's global private SDN. By integrating Netskope One SD-WAN with MVE, you can deploy a unified SASE platform without physical hardware, shipping delays, or data center rack space.
Megaport provides the network underlay, while Netskope One SD-WAN manages the network connections and network policies. You use the Megaport Portal to create and order MVE instances and establish Virtual Cross Connects (VXCs) to cloud on-ramps and other services on the Megaport SDN.
## Netskope One SD-WAN
Netskope One SD-WAN is a unified SASE platform that converges networking and security services.
Key capabilities include:
* **Zero trust network access (ZTNA)** -- Secure access to private applications based on identity and context.
* **Secure web gateway (SWG)** -- Protect users from web-based threats with real-time inspection.
* **Cloud access security broker (CASB)** -- Control and secure access to cloud applications and data.
* **Next-generation firewall (NGFW)** -- Enforce security policies with application-aware firewall controls.
* **SD-WAN** -- Optimize traffic routing and application performance across your network.
* **Data loss prevention (DLP)** -- Prevent sensitive data exfiltration with inline inspection.
Netskope One SD-WAN is managed through the Netskope One portal, providing centralized visibility and policy management across all deployment locations.
## Helpful references
* [Installing the virtual appliance on Linux KVM](https://docs.netskope.com/en/install-the-virtual-appliance-on-linux-kvm)
* [Netskope One SD-WAN documentation](https://docs.netskope.com/)
# Planning Your Netskope One SD-WAN Deployment
Source: https://docs.megaport.com/mve/netskope/plan-deployment
This help topic describes Netskope One SD-WAN deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
| **You Provide** | **Megaport Provides** |
| - | - |
| Internet connection from branch | Platform to host the Netskope One SD-WAN virtual appliance |
| Netskope One SD-WAN enabled at branch | Complete connection from a branch to any destination on the Megaport network and interoperation with other Megaport products and services |
| Customer premises equipment (CPE) installed in branch | Megaport Internet connection to terminate the tunnel between MVE and CPE at branch via internet |
| Netskope One SD-WAN license to use on Megaport SDN | Access to the Megaport ecosystem |
## Deployment considerations
This section describes MVE deployment options and sizing for Netskope One SD-WAN. For an overview of Netskope One SD-WAN features, see [Netskope One SD-WAN with Megaport Virtual Edge](/mve/netskope). For information about all supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Netskope One SD-WAN**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* You can provision another MVE instance, add it to your network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### Security
MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN.
### Licensing
Before you create an MVE in the Megaport Portal, you need user accounts with ordering permissions that provide access to the Megaport Portal. For more information, see [Creating an Account](/setting-up/registering).
You also need a valid Netskope One SD-WAN license and access to the Netskope One portal to generate the activation token and URI (if using activation). For more information, see the [Netskope website](https://www.netskope.com/).
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
### vNICs
Each MVE can have up to five vNICs. A Netskope One SD-WAN MVE is created with one vNIC by default, named *WAN, LAN, Mgmt*. You can add up to four more, making a total of five.
Before specifying the number of vNICs on your MVE:
* You cannot change the number of vNICs after ordering an MVE. Decide in advance how many vNICs to specify when you create the MVE.
* Consult your service provider to verify that adding a vNIC does not affect functionality.
If you need to change the number of vNICs after an MVE has been ordered, you must cancel and re-order the MVE.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
# Terminating an MVE
Source: https://docs.megaport.com/mve/netskope/terminating-mve
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
Before terminating the MVE, deactivate the Netskope One SD-WAN device in the Netskope One portal to release the license for further use. For more information about deactivating Netskope devices, see the [Netskope documentation](https://docs.netskope.com/).
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window appears, displaying a list of services connected to the MVE. Early termination fees are shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use your SD-WAN management console to delete the MVE.
# Connecting MVEs Integrated with Palo Alto Networks VM-Series
Source: https://docs.megaport.com/mve/palo-alto/connect-mve-to-mve
This help topic describes how to connect two Megaport Virtual Edges (MVEs) integrated with Palo Alto Networks VM-Series.
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with Palo Alto Networks next-generation firewall (NGFW) to another MVE.
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer/SD-WAN partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [Creating a VM-Series MVE](/mve/palo-alto/creating-mve).
## Creating a VXC between two MVEs
A private VXC deployment between two MVEs integrated with Palo Alto Networks starts in the Megaport Portal. To complete the configuration, you will use Palo Alto Networks VM-Series.
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and click **+Connection** next to the originating A-End MVE.
2. Select Private VXC.
3. Select the destination B-End MVE and location.\
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `LA MVE 2 to Dallas MVE 4`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. Consult Palo Alto Networks' documentation for more information.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **vNIC selection** -- Depending on the definition of the MVEs you are using, you might have to specify A-End and B-End vNICs.
* **A-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
* **B-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
For more information about vNIC selection when connecting MVEs with different services, see [Types of vNIC Connections](/mve/vnic-connections).
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.\
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don’t specify a value, Megaport will assign one. For a Palo Alto Networks MVE, it will also be used to configure the VLAN tag in Palo Alto Networks PAN-OS.
* **Preferred B-End VLAN** -- Specify the 802.1q VLAN tag for this connection that you will receive through the B-End VLAN. For a Palo Alto Networks MVE, it will also be used to configure the VLAN tag in Palo Alto Networks PAN-OS.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Click **Add VXC** to move this configuration to your cart.
8. Repeat these steps to provision any additional VXCs.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs in the Palo Alto Networks VM-Series.
The next procedure configures IP connectivity with BGP, providing just one solution out of many. Consult your vendor documentation for specific network design and configuration options before configuring interfaces for the MVEs.
## Configuring the A-End MVE in VM-Series
Configure the new VLAN interface in VM-Series, including name, VLAN value, and IP address details.
**To configuring the A-End MVE in VM-Series**
1. Log in to your VM-Series instance.
2. Choose Network > Interfaces.
3. Select the A-End MVE (`ethernet1/1`).
4. Click **Add Subinterface**.
5. Provide these details:
* **Interface Name** -- Enter a name for the subinterface. In the adjacent field, enter a number to identify the subinterface.
* **Comment** -- Enter an alternate name, for example, `PA-MVE-1 to PA-MVE-2`.
* **Tag** -- Specify the VLAN value associated with the VXC you created earlier. For ease of use, specify the same number as the Interface Name.
* **Virtual Router** -- Select a virtual router to the interface, as required by your network.
6. Select the **IPv4** tab.
7. Select **Static** as the Type.
8. Click **+Add** to add a new IP address.
9. Enter the IPv4 address and netmask.
10. Click **OK**.
11. Click **Commit** in the top right corner.
12. Review the changes and click **Commit**.
The new VLAN interface appears with your `ethernet1/1` physical interface.
Next, you will create a security zone so the interface can route traffic.
**To create a security zone**
1. Select the `ethernet1/1.1010` subinterface.
2. Select New Zone from the Security Zone drop-down list.
3. Specify a name for the security zone.
4. Click **+Add** under Interfaces and add `ethernet1/1.1010` to the security zone.
5. Specify any additional details as required for your network security.
6. Select New Zone Protection Profile from the Zone Protection Profile drop-down list.
7. Specify any details as required for your network security. This example uses all the defaults.
8. Click **OK**.
9. Click **OK** in the Layer3 Subinterface screen.
10. Click **Commit** in the top right corner.
11. Review the changes and click **Commit**.
## Configuring the B-End MVE in VM-Series
* Follow the same procedure to configure the B-End interface, using a different IP address.
## Validating your connection
Next, you will test connectivity between the Palo Alto Networks MVEs.
Because Palo Alto is a firewall, you must [enable ICMP](https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClMmCAK) before an interface can respond to an ICMP echo request.
**To validate your connection**
1. Log in to your VM-Series instance.
2. Choose Network > Interfaces.
3. Select the newly created subinterface.
4. Select the **Advanced** tab.
5. Select New Management Profile from the drop-down list.
6. Specify a profile name in the **Name** field.
7. Select Ping from the Network Services list.
8. To add specific IP addresses or subnets to the ACL, click **+Add** under Permitted IP Addresses.
9. Click **OK**.
10. Click **OK**.
11. Click **Commit** in the top right corner.
12. Review the changes and click **Commit**.
13. Repeat steps 1 to 12 for the second Palo Alto Networks MVE.
14. Choose Device > Troubleshooting to test connectivity between the Palo Alto Networks MVEs.
15. Select Ping from the Select Test drop-down list.
16. Enter the relevant details.\
See the [Palo Alto Networks Tech Docs](https://docs.paloaltonetworks.com/pan-os/9-1/pan-os-web-interface-help/device/device-troubleshooting/ping-troubleshooting-test) for information on these fields.
17. Click **Execute** to run the test.
# Connecting MVEs Integrated with Palo Alto Networks Prisma SD-WAN
Source: https://docs.megaport.com/mve/palo-alto/connect-mve-to-mve-prisma
This help topic describes how to connect two Megaport Virtual Edges (MVEs) integrated with Palo Alto Networks Prisma SD-WAN.
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with Palo Alto Networks Prisma SD-WAN to another MVE.
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer/SD-WAN partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [Creating an MVE Integrated with Palo Alto Prisma SD-WAN](/mve/palo-alto/creating-mve-prisma).
## Creating a VXC between two MVEs
A private VXC deployment between two MVEs integrated with Palo Alto Networks starts in the Megaport Portal. To complete the configuration, you will use Palo Alto Networks Strata Cloud Manager.
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and click **+Connection** next to the originating A-End MVE.
2. Select Private VXC.
3. Select the destination B-End MVE and location.\
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `LA MVE 2 to Dallas MVE 4`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. Consult Palo Alto Networks' documentation for more information.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **vNIC selection** -- Depending on the definition of the MVEs you are using, you might have to specify A-End and B-End vNICs.
* **A-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
* **B-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
For more information about vNIC selection when connecting MVEs with different services, see [Types of vNIC Connections](/mve/vnic-connections).
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.\
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don’t specify a value, Megaport will assign one. For a Palo Alto Networks MVE, it will also be used to configure the VLAN tag in Palo Alto Networks PAN-OS.
* **Preferred B-End VLAN** -- Specify the 802.1q VLAN tag for this connection that you will receive through the B-End VLAN. For a Palo Alto Networks MVE, it will also be used to configure the VLAN tag in Palo Alto Networks PAN-OS.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Click **Add VXC** to move this configuration to your cart.
8. Repeat these steps to provision any additional VXCs.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs on the Palo Alto Prisma SD-WAN side. For more information about specific network design and configuration options before configuring interfaces for the MVEs, see the [Palo Alto Prisma SD-WAN documentation](https://docs.paloaltonetworks.com/prisma/prisma-sd-wan/prisma-sd-wan-admin).
# Creating a VM-Series MVE
Source: https://docs.megaport.com/mve/palo-alto/creating-mve
This help topic describes how to create and configure a VM-Series Megaport Virtual Edge (MVE).
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with VM-Series next-generation firewall (NGFW). You can use VM-Series to secure application traffic that flows through the MVE.
Before you begin, you need user accounts with ordering permissions that provide access to the Megaport Portal and the VM-Series firewall.
For more information about setting up a Megaport account, see [Creating an Account](/setting-up/registering).
Palo Alto Networks provides documentation for VM-Series at [VM-Series Tech Docs](https://docs.paloaltonetworks.com/vm-series).
## Basic steps
This section provides an overview of the configuration steps in the Megaport Portal and PAN-OS. Detailed procedures follow this basic step summary.
The basic steps are:
* Obtain a VM-Series license from Palo Alto Networks.
* Set a temporary admin password for VM-Series.
* Generate an SSH Public Key for authentication.
* Create the Palo Alto Networks VM-Series MVE in the Megaport Portal.\
We strongly recommend that you provision a Megaport Internet connection onto the management plane virtual interface.
* View the MVE public IP address assignment in the Megaport Portal.
* Allow secure console access to the VM-Series.
## Licensing
Before you create an MVE in the Megaport Portal, you need a valid license from Palo Alto Networks. After purchasing a VM-Series firewall, you receive an authorization code via email. You will use this Auth Code to register the MVE with Palo Alto Networks.
**To obtain an authorization code from Palo Alto Networks for VM-Series**
1. Log in to the Palo Alto Networks [Customer Support Portal](https://support.paloaltonetworks.com/) with your account credentials.
2. Choose Assets > VM-Series Auth-Codes > Add VM-Series Auth-Code.
3. Enter the Auth Code you received by email in the **Add VM-Series Auth-Code** field.
4. Select the check box on the far right to save.\
The page displays the list of Auth Codes registered to your Support account.
5. To view all the assets that are deployed, choose Assets > Devices.
Once the product is registered, it appears in the Palo Alto Networks Registration Completion page.
The next step is to generate an SSH key pair for authentication.
## Administrative access to MVE
You connect your MVE through a public/private SSH key pair to establish a secure connection. The public SSH key allows you to use SSH to access the MVE and perform administrative tasks, such as setting the administrative password, enabling HTTPS access, and optionally registering the MVE to your management platform.
Megaport supports the 2048-bit RSA key type.
**To generate an SSH key pair (Linux/Mac OSX)**
* Enter the SSH keygen command in the terminal.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ssh-keygen -f ~/.ssh/megaport-mve-instance-1-2048 -t rsa -b 2048
```
The key generator command creates an SSH key pair and adds two files to your \~/.ssh directory:
* **megaport-mve-instance-1-2048** - contains the private key.
* **megaport-mve-instance-1-2048.pub** - contains the public key that is authorized to log in to the vendor account.
**To generate an SSH key pair (Windows, using [PuTTYgen](https://www.puttygen.com))**
1. Open PuTTYgen.
2. In the Key section, choose RSA 2048 bit and click **Generate**.
3. Move your mouse randomly in the small screen to generate the key pairs.
4. Enter a key comment to identify the key.\
This is convenient when you use several SSH keys.
5. Enter a Key passphrase, and re-enter to confirm.\
The passphrase is used to protect your key. You will be asked for it when you connect via SSH.
6. Click **Save private key**, choose a location, and click **Save**.
7. Click **Save public key**, choose a location, and click **Save**.
You will copy and paste the contents of the public key file in the Megaport Portal later to distribute the public key to the MVE. Your private key will match the public key to grant access. Only a single private key has access to the MVE for SSH access.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/palo-alto/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also create two Megaport Internet connections.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Palo Alto VM-Series**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Palo Alto VM-Series.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Palo Alto VM-Series-specific settings:
* **License Data** (optional) -- Specify the VM-Series Auth Code (the valid license for the virtual appliance). The Auth Code is used to register the VM-Series MVE instance with Palo Alto Networks. You can find it in the Palo Alto Networks Support portal.
* **Admin Password** -- Specify a temporary administrator password. The password must be a minimum of 8 characters and include:
* 1 uppercase character (A-Z)
* 1 lowercase character (a-z)
* 1 number (0-9)
* 1 symbol
Megaport does not store customer passwords.
* **SSH Key** -- Copy and paste the contents of your public SSH key here. You can find the public key in the **megaport-mve-instance-1-2048.pub** file generated earlier.
* **Virtual Interfaces (vNICs)** -- Each MVE is configured with two vNICs named *Management Plane* and *Data Plane* by default. To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed.
You can add a total of five vNICs to the MVE, including the two added by default. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Enter a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with Palo Alto Networks licensing systems and, optionally, Panorama.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
As a best practice, we recommend including "Management Plane" in the name for reference later.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select **vNIC-0 Management Plane** from the drop-down list.
The internet connection on the *management virtual interface* will be used only for management purposes such as licensing, updates, and communication with Panorama. If you require internet traffic to flow between branches, users, and/or the cloud, you will create a second Megaport Internet connection on the *data plane virtual interface*. For more information, see [To create a second Megaport Internet connection on the data plane](#dataplane).
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to order the connection.
7. Click **Review Order** in the Configured Services area.
8. If you have a promotional code, click **Add Promo Code**, enter it, then click **Add Code**.
9. Click **Order Now**.
A second Megaport Internet connection is required if the firewall will be exchanging internet traffic with branches. Each data plane Megaport Internet connection receives its own unique public IP Address.
**To create a second Megaport Internet connection on the data plane virtual interface**
1. In the Megaport Portal, go to the **Services** page.
2. Click **+Connection** on the Palo Alto Networks MVE.
3. Select **Megaport Internet**.
4. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can filter by diversity zone, or select to view all.
5. Click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your data plane Megaport Internet connection to be shown in the Megaport Portal. As a best practice, we recommend including "Data Plane" in the name for reference later.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. This speed is adjustable starting from 20 Mbps, in 1 Mbps increments. Maximum available speed depends on location and service availability. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select *vNIC-1 Data Plane* from the drop-down list.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged**. This selection removes the VLAN tagging for this connection and it will be configured without a VLAN ID.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next** to proceed to the connection detail summary, click **Add VXC**, and order the connection.
8. Repeat these steps to provision any additional VXCs.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Ordering MVE provisions the instance and assigns IP addresses from the Megaport SDN. The Palo Alto Networks MVE provisioning time varies between versions and depends on whether you provide a license authorization code. It can take up to 15 minutes for the MVE to provision before you can log in and continue configuration.
After you order the MVE from the Megaport Portal, you can use Palo Alto Networks Panorama to manage the firewall.
## Viewing the MVE in the Megaport Portal
After creating the MVE, you can view it in the Megaport Portal on the Services page. You can also view the public IP addresses assigned.
**To view an MVE in the Megaport Portal**
* Go to the **Services** page.
The Megaport Internet icon differs from a standard VXC icon in the Megaport Portal, as shown in the image.
For more information about the Services page, see [Understanding the Services Page](/portal-admin/services-page).
**To view the public IP addresses assigned to the MVE**
1. Click the gear icon next to the Management Plane Megaport Internet connection.\
The Connection Configuration screen appears. From here, you can modify any of the Megaport Internet connection details.
2. Select the **Details** tab.
3. Locate the public IP address (IPv4 or IPv6).\
These are the public IP addresses assigned to the MVE.
## Updating the administrator password
Next, you will replace the temporary password you set in the Megaport Portal with a new secure password.
**To update the administrator password**
1. Log in to the Palo Alto Networks system using the temporary admin password you set in the Megaport Portal.
2. Choose Device > Administrators.
3. Select the `admin` user.
4. Enter the old temporary password, a new secure password, and confirm the new password.
5. Click **OK**.
6. Choose Config > Save Changes.
## Configuring the data plane interface
Next, you will configure the data plane interface and assign it an interface type.
**To configure the data plane interface**
1. Choose Network > Interfaces.
2. Select `ethernet1/1` from the Interface column.
3. Select Layer3 from the Interface Type drop-down list.
4. Click **OK**.
5. Highlight the ‘ethernet1/1’ row and click **Add Subinterface** at the bottom of the screen.
6. Provide these details:
* **Interface Name** -- Enter a name for the subinterface. In the adjacent field, enter a number to identify the subinterface.
* **Comment** -- Enter an alternate name.
* **Tag** -- Specify the A-End VLAN value associated with the Megaport Internet destination Port.
* **Virtual Router** -- Select a virtual router to the interface, as required by your network.
7. Select the **IPv4** tab.
8. Select **DHCP Client** as the Type.
9. Click **OK**.
10. Click **Commit** in the top right corner.
11. Review the changes and click **Commit**.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/palo-alto/creating-mve-vxc).
# Creating an MVE Integrated with Palo Alto Prisma SD-WAN
Source: https://docs.megaport.com/mve/palo-alto/creating-mve-prisma
This help topic describes how to create and configure Megaport Virtual Edge (MVE) with Palo Alto Prisma SD-WAN.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Palo Alto Prisma SD-WAN.
Before you begin, you need user accounts with ordering permissions that provide access to the Megaport Portal. You also need a Strata Cloud Manager console account for licensing.
For details on setting up a Megaport account, see [Creating an Account](/setting-up/registering).
Palo Alto Networks provides documentation in the [Prisma SD-WAN Administrator’s Guide](https://docs.paloaltonetworks.com/prisma/prisma-sd-wan/prisma-sd-wan-admin).
## Basic steps
This section summarizes the configuration steps using the Megaport Portal. Detailed procedures follow this basic step summary.
The basic steps are:
* Create a Prisma SD-WAN license key
* Obtain an ION Key and Secret Key (Authorization token) from Palo Alto Networks
* Enter the MVE details
* Order the Prisma MVE in the Megaport Portal
## Licensing
You bring your own Prisma license for the model that you want to deploy with MVE. It is your responsibility to have the appropriate licenses for the endpoints created on the Megaport network.
To create a Palo Alto Networks Prisma MVE in the Megaport Portal, you also need a valid ION Key and Secret Key (Authorization token) from Palo Alto Networks. Tokens are generated through the [Strata Cloud Manager console](https://docs.paloaltonetworks.com/strata-cloud-manager) by a Palo Alto Networks customer administrator. Tokens can be single use or multi use, are valid for 96 hours, and will be assigned to the virtual appliance during deployment.
For more information, see the [Prisma SD-WAN Administrator’s Guide](https://docs.paloaltonetworks.com/prisma/prisma-sd-wan/prisma-sd-wan-admin).
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/palo-alto/plan-deployment-prisma).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **the required Palo Alto Prisma SD-WAN product**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Prisma.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Prisma-specific settings:
* **ION Key** -- Enter the ION Key that was generated from the authorization token in the Prisma SD-WAN portal.
* **Secret Key** -- Enter the Secret Key that was generated from the authorization token in the Prisma SD-WAN portal.
* **Virtual Interfaces (vNICs)** -- Each MVE is configured with vNICs by default. The 3108v, 3104v, and 3102v models contain four vNICs and the 7108v model contains three vNICs by default, each with the first vNIC (vNIC 0) configured for the management/controller interface. The remaining vNICs can be assigned roles such as Public WAN, WAN, LAN, and so on. To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed.
You can add a total of five vNICs to the MVE. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Enter a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with Prisma SD-WAN.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select **vNIC-0** for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up a Palo Alto Prisma SD-WAN.
## Configuring the MVE in Strata Cloud Manager
After creating the MVE, you need to configure the device in Strata Cloud Manager. In Strata Cloud Manager, perform the following configuration tasks.
For full details on these tasks, see the
[Strata Cloud Manager documentation](https://docs.paloaltonetworks.com/strata-cloud-manager).
* Claim the device
* Assign the device to the data center site
* Set the data center site to Control Mode -- This allows you to configure routing features for the device.
* Give the device a name -- As a recommended practice, name the device the same as the MVE in the Megaport Portal.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/palo-alto/creating-mve-vxc-prisma).
## Helpful references
* [Prisma SD-WAN and Megaport Virtual Edge Solution Guide](https://www.paloaltonetworks.com/resources/guides/prisma-sd-wan-and-megaport-virtual-edge-solution-guide)
* [Simplify Cloud Networking with Prisma SD-WAN & Megaport MVE blog](https://www.paloaltonetworks.com/blog/sase/prisma-sd-wan-megaport-virtual-edge-integration-now-available/)
* [Strata Cloud Manager - Manage: CloudBlades for Prisma SD-WAN](https://docs.paloaltonetworks.com/strata-cloud-manager/getting-started/manage-configuration-prisma-sd-wan/manage-prisma-sd-wan-cloudblades)
# Creating a VXC to an MVE Integrated with Palo Alto VM-Series
Source: https://docs.megaport.com/mve/palo-alto/creating-mve-vxc
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE) integrated with Palo Alto Networks.
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with Palo Alto VM-Series.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.\
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
For specific CSP configuration details:
* AWS Direct Connect -- See [Creating MVE Connections to AWS Direct Connect with Palo Alto VM-Series](/cloud/mve/palo-alto/aws).
* Azure Express Route -- See [Creating an Azure Connection for an MVE with Palo Alto VM-Series](/cloud/mve/palo-alto/azure).
* Google Cloud -- See [Creating a Google Cloud Services Connection for an MVE with Palo Alto VM-Series](/cloud/mve/palo-alto/google).
* Other cloud connections -- See [Creating MVE Connections to Any Endpoint with Palo Alto VM-Series](/cloud/mve/palo-alto/generic).
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
For specific configuration details, see [Connecting MVE to MVE](/mve/palo-alto/connect-mve-to-mve).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/palo-alto/terminating-mve).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# Creating a VXC to an MVE Integrated with Palo Alto Networks Prisma SD-WAN
Source: https://docs.megaport.com/mve/palo-alto/creating-mve-vxc-prisma
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE) integrated with Palo Alto Networks Prisma SD-WAN.
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with Palo Alto Networks Prisma SD-WAN.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the Palo Alto Networks MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
For specific configuration details, see [Connecting MVE to MVE](/mve/palo-alto/connect-mve-to-mve-prisma).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/palo-alto/terminating-mve-prisma).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# Palo Alto Networks VM-Series Firewall with Megaport Virtual Edge
Source: https://docs.megaport.com/mve/palo-alto/index
This help topic describes Palo Alto Networks with Megaport Virtual Edge (MVE) functionality.
Palo Alto Networks offers a range of solutions for MVE, providing both advanced network flexibility and scalability, and robust security options. Depending on your needs, you can deploy a Palo Alto Networks VM-Series Firewall for extra security to your network at the edge or Palo Alto Networks Prisma SD-WAN for streamlined network management and SD-WAN functionalities.
VM-Series is the next-generation firewall (NGFW) solution from Palo Alto Networks that adds extra security to your network at the edge. Using Megaport Virtual Edge (MVE), you can quickly and securely deploy a NGFW in many global locations.
In the Megaport Portal you create and manage the MVE and Virtual Cross Connects (VXCs) to cloud on-ramps and other services in the Megaport software-defined network. MVE acts as the underlay providing the compute, networking, and connectivity on demand, so that when it is paired with the overlay of the VM-Series NGFW it quickly and securely deploys a complete virtual firewall service. You manage the firewall via the appliance's local GUI or Palo Alto network orchestrator, [Panorama](https://docs.paloaltonetworks.com/panorama).
The following diagram shows an example network implementation of Palo Alto Networks VM-Series Firewall features over the Megaport network.
# Configuring High Availability on Palo Alto Networks VM-Series Firewall
Source: https://docs.megaport.com/mve/palo-alto/palo-alto-ha-mve
This help topic describes how to configure High Availability for Palo Alto Networks VM-Series Megaport Virtual Edge (MVE).
This topic describes the steps to configure Palo Alto Networks Active/Active High Availability (HA) with route based redundancy.
Palo Alto Networks provides documentation for VM-Series at [VM-Series Tech Docs](https://docs.paloaltonetworks.com/vm-series).
## Basic steps
This section provides an overview of the configuration steps in the Megaport Portal and PAN-OS. Procedures follow this basic step summary.
The basic steps are:
1. Create a Palo Alto Networks MVE.\
Palo Alto Networks HA requires three dedicated HA interfaces (HA1, HA2, HA3), and the management and data plane interfaces. Add additional vNICs for a total of 5.
2. Create a second Palo Alto Networks MVE of the same size and version, within the same metro.
Palo Alto Networks requires the MVEs to be the same size, and to be within 20 milliseconds of each other. For HA prerequisite details, see [Prerequisites for Active/Active HA](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/high-availability/set-up-activeactive-ha/prerequisites-for-activeactive-ha).
3. Create the VXCs for HA traffic.\
vNIC 1 is for management, vNIC 2 for data plane, and vNIC 3 through 5 for dedicated HA traffic. Create a VXC between vNIC 3 (HA1) on each MVE, both ends should be untagged (no VLAN). Repeat for vNICs 4 (HA2) and 5 (HA3).\
We recommend the HA1 and HA2 VXCs are configured at 1 Gbps, and the HA3 VXC configured with a speed to allow it to carry the expected combined total traffic routed through the firewall.
4. Configure Active/Active HA in the Palo Alto Networks PAN‑OS software.\
For more information, see the Palo Alto Networks documentation at [Configure Active/Active HA](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/high-availability/set-up-activeactive-ha/configure-activeactive-ha).
## HA Overview
When deploying Palo Alto Networks next-generation firewalls (NGFW) on premises or in a data center, using the built in High Availability (HA) functionality is a common approach. PAN-OS HA is a robust solution that solves several challenges with redundant firewalls, in particular session state and configuration synchronization.
Historically this architecture has been hard to achieve in cloud environments as it relies on specific network functionality which often is not available. Megaport's support of Palo Alto Networks firewalls on Megaport Virtual Edge (MVE), and multi vNIC functionality on the MVE platform, makes this architecture possible. This solution is particularly useful for customers using MVE for a virtualized network core and/or connectivity.
Palo Alto Networks firewalls deployed on MVE can be configured with Active/Active HA, combining the benefits of on-demand as-a-service deployment, direct private connectivity to clouds and data centers, optimal resource utilization, session and configuration synchronization, and orchestrated failover.
### Active/Active HA
PAN-OS has two modes of HA:
* Active/Active
* Active/Passive
Active/Passive HA has only one firewall active at any one time, with the secondary firewall having all interfaces disabled and passing no traffic. This makes sense when working with a pair of devices in the same location connected to the same physical switches, and has the advantage that it doesn’t add complexity in simple architectures (like you might find in an office).
Active/Active HA allows both firewalls to be active and passing traffic at the same time, with all traffic being redirected to the remaining device if a firewall or monitored link fails. This has the advantage of allowing the rest of the network to be aware of the available paths, and of being able to use the capacity of both firewalls in a normal state.
Active/Active HA in PAN-OS uses routing and/or NAT to distribute traffic between both firewalls, while synchronizing the active sessions between both devices. Each firewall has its own interfaces with its own BGP sessions, and ECMP can be used to balance traffic across both devices. In the event of a failover, routes are updated, flows are redirected, and the remaining firewall picks up the existing sessions.
A failover can be triggered either by one of the firewalls failing, a monitored path becoming unavailable, or a failure of the HA links between the devices. If a monitored path becomes unavailable, traffic is forwarded from the affected device to the device with the available path via the HA3 link.
See the Palo Alto Networks documentation for more information about PAN-OS Active/Active HA at [Use Case: Configure Active/Active HA with Route-Based Redundancy](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/high-availability/set-up-activeactive-ha/determine-your-activeactive-use-case/use-case-configure-activeactive-ha-with-route-based-redundancy).
## Understanding the architecture
The architecture deployed in this topic is shown below.
There are two MVEs running Palo Alto Networks PAN-OS, each with their management interface connected to the internet. Three VXCs are connected between the two MVEs for the HA links, and the data plane VXCs are connected to two different cloud environments, which are connected together.
In a production deployment, there might be additional data plane VXCs to connect to other networks, internet connections, VPNs, and so on, and the management interfaces might be on private networks instead.
### Architecture overview
This image shows a high level architecture diagram of the Palo Alto Networks Active/Active HA solution.
### Interface details
This image shows the interface details for the Palo Alto Networks Active/Active HA solution.
## Create the Palo Alto Networks VM-Series MVEs in the Megaport Portal
The first step is to create and deploy two MVEs in the Megaport Portal. Palo Alto Networks HA requires three dedicated HA interfaces (HA1, HA2, HA3), as well as the management and data plane interfaces.
**To create and deploy Palo Alto Networks MVEs**
1. In the Megaport Portal, go to the **Services** page.
2. Create a Palo Alto Networks MVE as described in [Creating a VM-Series MVE](/mve/palo-alto/creating-mve).
3. On the MVE Details screen, make sure that you create five vNICs in the **Virtual Interfaces (vNICs)** field to support the additional interfaces used for HA.
4. Create a second Palo Alto Networks MVE of the same size and version, in another data center within the same metro.
Palo Alto Networks requires the MVEs to be the same size, and to be within 20 milliseconds of each other. This MVE must also have five vNICs added.
5. For management access, create a Megaport Internet connection for the management interface of each MVE.\
This is the most common approach during initial deployment, but the management interface can instead be connected to a private VXC once an alternative management path is configured.
Once completed, there should be two MVEs deployed which both look like this:
## Create the VXCs for HA traffic
Now that the MVEs have been created, the next step is to create three private VXCs for HA traffic between the two devices. Use ethernet1/2, ethernet1/3, and ethernet1/4 for the HA interfaces, connecting each one to the same interface on the other MVE, and configuring the VXCs as untagged.
For HA1 and HA2, create a 1 Gbps VXC for each. The bandwidth requirements for HA3 can be significant, especially during a path outage, so create a 10 Gbps VXC for that path.
**To create a VXC between MVEs**
1. In the Megaport Portal, go to the **Services** page.
2. Create a VXC between two Palo Alto Networks MVEs as described in [Connecting MVEs Integrated with Palo Alto VM-Series](/mve/palo-alto/connect-mve-to-mve).
3. Repeat this process to create untagged VXCs between the three interfaces on each MVE being used for HA. Each MVE should now look similar to the image below:
## Configure Active/Active HA in PAN-OS
Now that the underlying infrastructure has been created and configured in the Megaport Portal, the firewalls need to be configured in the Palo Alto Networks PAN‑OS software. The management web interface for each firewall can be accessed on the IP of the VXC attached to the management vNIC (vNIC0) (you can find the IP on the Details tab of the VXC).
This section describes the configuration of Active/Active HA in PAN-OS based on version 10.2. This should be used as an example only. Modifications to the configuration within the firewalls might be required for your environment and/or based on updates or changes released by Palo Alto Networks in future. In general, you should see the Palo Alto Networks documentation for detailed information about the available options and best practices in PAN-OS.
### Configure Hypervisor assigned MAC addresses
By default, PAN-OS will use self generated MAC addresses for the ethernet interfaces. This prevents successful configuration of HA as both firewalls will have the same MAC addresses. To prevent this, enable the option to use Hypervisor Assigned MAC Addresses. This will cause PAN-OS to use the real MAC address of the underlying hardware interfaces which will be different on each MVE.
For more information, see the Palo Alto Networks documentation at [Hypervisor Assigned MAC Addresses](https://docs.paloaltonetworks.com/vm-series/10-2/vm-series-deployment/about-the-vm-series-firewall/hypervisor-assigned-mac-addresses).
### Configure static management IPs
Palo Alto Networks' recommended design for HA on VM-Series appliances is to use the management interface for HA1. To be used for HA, an interface must have a static IP as using DHCP for HA is not supported by PAN-OS. By default, the management interface of an MVE uses DHCP to acquire its IP address, so this must be changed to static. When the management interface is configured with a static IP, static DNS servers must also be configured. As jumbo frames will be enabled, confirm the MTU of the management interface is set to 1500.
If you are using the provided Megaport Internet connection for management, although the IP is provided by DHCP by default, it is a persistent address and will not change as long as the Megaport Internet connection exists. The IP address, subnet mask, and gateway can be found in the Details section of the connection in the Megaport Portal. Configuring IPv6 is optional.
For more information about how to configure interfaces in PAN-OS, see the Palo Alto Networks documentation at [Configure Management Interface IP](https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClN7CAK).
### Enable jumbo frames
As the HA3 link sends encapsulated traffic between the firewalls, it requires an MTU greater than 1500 bytes. To achieve this, jumbo frames must be enabled globally. After jumbo frames are enabled globally, all interfaces will default to the higher MTU. If you want data plane interfaces to remain at an MTU of 1500, you need to specify the MTU for each interface. Megaport VXCs support an MTU of up to 9100.
For more information about how to enable jumbo frames, see the Palo Alto Networks documentation at [Enable Jumbo Frames on the VM-Series Firewall](https://docs.paloaltonetworks.com/vm-series/10-2/vm-series-deployment/about-the-vm-series-firewall/enable-jumbo-frames-on-the-vm-series-firewall).
### Create a virtual router
The next step on each firewall is to create a virtual router. This is required in PAN-OS regardless of whether the device is physical or virtual, standalone, or in HA. A virtual router represents a single route table.
For more information about creating virtual routers, see the Palo Alto Networks documentation at [Configure Virtual Routers](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-networking-admin/virtual-routers/configure-virtual-routers).
### Create a zone
Layer 3 interfaces must be added to zones before they become functional.
See the Palo Alto Networks documentation for detailed information on zones at [Segment Your Network Using Interfaces and Zones](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/getting-started/segment-your-network-using-interfaces-and-zones).
### Configure interface types
Next, configure the interfaces as the required type. Interface ethernet1/1 will be configured as Layer 3 (this will be used to connect to workloads), and interfaces ethernet1/2, ethernet1/3, and ethernet1/4 will be configured as HA.
For more information, see the Palo Alto Networks documentation at [Firewall Interfaces Overview](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-web-interface-help/network/network-interfaces/firewall-interfaces-overview).
### Configure HA
Now that the basic infrastructure is in place, we can configure the HA functionality.
See the Palo Alto Networks documentation for detailed information on Active/Active High Availability at
[Configure Active/Active HA](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/high-availability/set-up-activeactive-ha/configure-activeactive-ha).
## Create data plane connections
Now that the MVEs are in place and configured in HA, create some data plane VXCs to connect to the networks we want to route between. The data plane VXCs will be attached as tagged VLAN subinterfaces of ethernet 1/1, and the relevant subinterfaces and BGP peers will be configured within the firewalls.
In this example we’ll connect AWS and Azure, but the same process can be used to connect any networks that are reachable through a VXC. Some tasks are performed in the Megaport Portal and some in PAN-OS.
### Create VXCs
The VXCs are created in the Megaport Portal using the standard process as described in [Connections Overview](/connections/overview), specifying vNIC-1 ethernet1/1 for the A-End vNIC and configuring the VXC to be delivered as a tagged VLAN.
Connections to the same destination should be created on both MVEs and delivered as the same VLAN. In this example, the Cloud1 VXC (to AWS) will be configured as VLAN 100 on both MVEs, and the Cloud2 VXC (to Azure) will be configured as VLAN 200.
After the VXCs have been created, both MVEs should look similar to the image below.
### Configure interfaces
Now configure the data plane interfaces for VLANs 100 and 200 in PAN-OS. Subinterfaces for each VLAN will be created under ethernet1/1.
See the Palo Alto Networks documentation for detailed information on configuring interfaces at [Configure Interfaces](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-networking-admin/configure-interfaces).
### Configure BGP
BGP will be used to distribute and manage routes automatically, including load balancing and managing the failover of traffic from one firewall to the other during an outage. Although BGP will manage redirecting the traffic, existing sessions will be maintained as the HA functionality will keep the session state in sync between both firewalls.
As each firewall will use different peer addresses and might use different BGP settings for traffic engineering, the Virtual Router settings are not synchronized between devices and must be configured on both.
See the Palo Alto Networks documentation for detailed information on configuring BGP at [Configure BGP](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-networking-admin/bgp/configure-bgp).
In most cases, we also recommend enabling Bidirectional Forwarding Detection (BFD) to improve failover recovery time. For more information about BFD, see [BFD Overview](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-networking-admin/bfd/bfd-overview).
### Configure failover conditions
Although what has been configured already will synchronize sessions between devices, and the external peers will direct traffic to the remaining device in the event of an outage, we still need to tell each firewall when to consider itself *down* and for the remaining firewall to pick up the sessions that have been synchronized to it.
This is achieved by configuring Virtual Router Path monitoring. Each firewall is configured to monitor relevant paths, and when those paths go down, to forward traffic via the other device through the HA3 link.
See the Palo Alto Networks documentation for detailed information on configuring failover conditions at [Define HA Failover Conditions](https://docs.paloaltonetworks.com/pan-os/10-2/pan-os-admin/high-availability/set-up-activepassive-ha/define-ha-failover-conditions).
## Review the configuration status
Now that everything is in place and configured, there are a few ways that you can confirm everything is working as expected.
* Both MVEs and all VXCs in the Megaport Portal should be green.
* All indicators on the HA widget on the Dashboard tab of both firewalls should be green.
* Both BGP sessions on both firewalls should be *Established*.
* Network > Virtual Routers > More Runtime Stats > BGP > Peer
* Routes for your networks should be received from both peers on both firewalls.
* Network > Virtual Routers > More Runtime Stats > BGP > Local RIB
* If BFD has been configured, both peers on both firewalls should be up.
* Network > Virtual Routers > More Runtime Stats > BFD Summary Information
* Routes for your networks should be in the route table on both firewalls.
* Network > Virtual Routers > More Runtime Stats > Routing > Route Table
* Sessions from both firewalls should appear in the Session Browser on both devices, with synchronized sessions marked as Session From HA: True.
* Monitor > Session Browser
* Each firewall should enter *Tentative (Path down)* mode if any of the monitored paths on that device fail.
* Dashboard > High Availability widget
# Planning Your Palo Alto Networks VM-Series MVE Deployment
Source: https://docs.megaport.com/mve/palo-alto/plan-deployment
This help topic describes Palo Alto Networks deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
## Palo Alto Networks VM-Series Firewall
You will need a VM-Series license from Palo Alto Networks to use on the Megaport software-defined network (SDN). For more information, see [Licensing](#licensing).
Megaport provides you with:
* A Virtual Machine to host the Next Generation Firewall (NGFW) image
* A Megaport Internet connection to terminate the tunnel between MVE and CPE at branch via internet
* Access to the Megaport ecosystem.
### VM-Series features
VM-Series delivers NGFW services on a virtual machine. Hosting VM-Series on MVE not only optimizes edge-to-cloud network connectivity, but also enforces advanced security services and policies across the Megaport backbone segments.
The Palo Alto Networks Secure Access Service Edge (SASE) offering is for customers that are adopting the SASE architecture and need additional security for their network at the edge.
Embedding VM-Series into Megaport's NaaS platform extends the following core SASE elements between the edge and cloud network fabric:
* Next-generation firewall, including stateful corporate firewall policies, network address translation (NAT), intrusion protection services, Secure Sockets Layer (SSL) inspection, and threat intelligence.
* Secure web gateway (SWG) services protect devices from malicious internet destinations using web content filtering and malware scanning.
* Zero trust network access (ZTNA), which controls access to applications by verifying users and devices before every application session and confirms that they meet the organization's policy to access that application.
* Segmentation and whitelisting control applications communicating across different subnets, block lateral threat movement, and assist in achieving regulatory compliance.
* Threat Prevention, DNS Security, and WildFire services that apply application-specific policies that prevent malware and stop previously unknown threats from infecting the cloud.
VM-Series also supports remote user integration with Palo Alto Networks SASE solutions with Prisma Access. Prisma Access provides two remote user access connection methods:
* **GlobalProtect** -- Extends Prisma Access' visibility and control of all network traffic, applications, ports, and protocols to the user for secure access to internet or data center-based applications.
* **Explicit proxy** -- Allows SWG access to internet-based applications using HTTP and HTTPS.
For more information about these features, see the [VM-Series Tech Docs](https://docs.paloaltonetworks.com/vm-series).
If you have already deployed a VM-Series firewall, you can connect it to an MVE so that your headquarters or branches can access cloud services over private interconnects.
## Deployment considerations
This section provides an overview of the MVE deployment options and features.
Palo Alto Networks uses virtual or physical appliances much like many other platforms. However, with Palo Alto Networks, you can configure the appliances for several different uses. For example, you can configure a Palo Alto Networks appliance for use:
* Strictly as a next-generation firewall (NGFW) for remote offices with local configuration and local logging only.
* As central management with central logging, or as central management without central logging.
### SD-WAN vendors
MVE is integrated with Palo Alto Networks, which uses Palo Alto network orchestrator Panorama (VM-Series) to create the private overlay network.
For information about all supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Palo Alto VM-Series**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* You can provision another MVE instance, add it to your overlay network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, add it to your overlay network, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
If you need more cores (vCPUs), you can either:
* Create a new MVE with more cores and terminate the old one (this option will require you to reconfigure your firewall).
* Create a new MVE as a second firewall to offload the capacity from the first firewall.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### Security
MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN. CSP-hosted instances of partner SD-WAN products route critical traffic across the Megaport SDN, reducing internet dependence. Traffic remains encrypted and under your policy control while traveling across the Megaport SDN, to or from, MVE.
### Licensing
You bring your own VM-Series license for use with MVE. It is your responsibility to have the appropriate licenses for the endpoints created on the Megaport network.
To acquire a VM-Series license, we recommend that you start with Palo Alto Networks' [credit estimator tool](https://www.paloaltonetworks.com/resources/tools/ngfw-credits-estimator).
Recommendations:
* Ensure that the number of vCPUs you select suits your requirements.
* Choose Kernel-based Virtual Machine (KVM) as the Environment.
* For the best performance, we recommend that you match the number of vCPUs from your VM-Series license with the number of vCPUs on your MVE.
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
### vNICs
Each MVE can have up to five vNICs. A VM-Series MVE is created with two vNICs by default. You can add up to three more, making a total of five.
Before specifying the number of vNICs on your MVE:
* Be aware that the number of vNICs cannot be changed after an MVE has been ordered. Decide in advance how many vNICs to specify when you create the MVE.
* Consult your service provider to make sure that functionality won't be affected if you add a vNIC.
If you need to change the number of vNICs after an MVE has been ordered, you will have to cancel and re-order the MVE.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
# Planning Your Palo Alto Networks Prisma MVE Deployment
Source: https://docs.megaport.com/mve/palo-alto/plan-deployment-prisma
This help topic describes Palo Alto Networks deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
## Palo Alto Networks Prisma SD-WAN
Palo Alto Networks Prisma SD-WAN is the next-generation SD-WAN solution that is autonomous, application-defined, and cloud-delivered. Prisma SD-WAN helps you secure and connect your branch offices and data centers without increasing cost and complexity.
Palo Alto Networks Prisma focuses on these key capabilities:
* **Enhanced network flexibility and scalability** -- Scale network capacity up or down based on real-time business demands without requiring physical infrastructure changes.
* **Optimized cloud connectivity** -- Simplify access to multiple cloud providers while ensuring the most efficient path for data and network traffic to reduce latency and improve app performance.
* **Robust security** -- Ensure that your critical data and devices—including IoT devices—are protected with end-to-end encryption and advanced threat prevention.
* **Streamlined network management** -- Gain visibility across the entire network while reducing complexity with Strata Cloud Manager for Prisma SD-WAN.
* **Intelligent bandwidth management** -- Reduce costs with flexible bandwidth allocation that optimizes resources efficiently and avoids unnecessary expenditures or unused capacities.
Megaport supports these Prisma SD-WAN software models:
* 310xv (including 3108v, 3104v, and 3102v) (For remote branches)
* 7108v (For data centers)
## Deployment considerations
This section provides an overview of the MVE deployment options and features.
For information on the Palo Alto Networks Prisma-specific settings, see [Prisma SD-WAN and Megaport Virtual Edge Solution Guide](https://www.paloaltonetworks.com/resources/guides/prisma-sd-wan-and-megaport-virtual-edge-solution-guide).
### SD-WAN vendors
MVE is integrated with Palo Alto Networks, which uses Strata Cloud Manager console (Prisma SD-WAN) to create the private overlay network.
For information about all supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **the required Palo Alto Prisma SD-WAN product**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* You can provision another MVE instance, add it to your overlay network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, add it to your overlay network, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
If you need more cores (vCPUs), you can either:
* Create a new MVE with more cores and terminate the old one (this option will require you to reconfigure your firewall).
* Create a new MVE as a second firewall to offload the capacity from the first firewall.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### Security
MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN. CSP-hosted instances of partner SD-WAN products route critical traffic across the Megaport SDN, reducing internet dependence. Traffic remains encrypted and under your policy control while traveling across the Megaport SDN, to or from, MVE.
### Licensing
You bring your own Prisma license for the model that you want to deploy with MVE. It is your responsibility to have the appropriate licenses for the endpoints created on the Megaport network.
To create a Palo Alto Networks Prisma MVE in the Megaport Portal, you also need a valid ION Key and Secret Key (Authorization token) from Palo Alto Networks. Tokens are generated through the [Strata Cloud Manager console](https://docs.paloaltonetworks.com/strata-cloud-manager) by a Palo Alto Networks customer administrator. Tokens can be single use or multi use, are valid for 96 hours, and will be assigned to the virtual appliance during deployment.
For more information, see the [Prisma SD-WAN Administrator’s Guide](https://docs.paloaltonetworks.com/prisma/prisma-sd-wan/prisma-sd-wan-admin).
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
### vNICs
Each MVE can have up to five vNICs. Prisma SD-WAN 3108v, 3104v, and 3102v MVEs are created with four vNICs, while a 7108v MVE is created with three vNICs.
Before specifying the number of vNICs on your MVE:
* Be aware that the number of vNICs cannot be changed after an MVE has been ordered. Decide in advance how many vNICs to specify when you create the MVE.
* Consult your service provider to make sure that functionality won't be affected if you add a vNIC.
If you need to change the number of vNICs after an MVE has been ordered, you will have to cancel and re-order the MVE.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
# Palo Alto Networks Prisma with Megaport Virtual Edge
Source: https://docs.megaport.com/mve/palo-alto/prisma
This help topic describes Palo Alto Networks with Megaport Virtual Edge (MVE) functionality.
Palo Alto Networks offers a range of solutions for MVE, providing both advanced network flexibility and scalability, and robust security options. Depending on your needs, you can deploy a Palo Alto Networks VM-Series Firewall for extra security to your network at the edge or Palo Alto Networks Prisma SD-WAN for streamlined network management and SD-WAN functionalities.
## Palo Alto Networks Prisma SD-WAN
Palo Alto Networks Prisma SD-WAN is the next-generation SD-WAN solution that is autonomous, application-defined, and cloud-delivered. Prisma SD-WAN helps you secure and connect your branch offices and data centers without increasing cost and complexity.
Prisma SD-WAN provides complete end-to-end visibility into performance and remediation to provide application resiliency. With Prisma SD-WAN, businesses can enable cloud-delivered infrastructure for the network, security, operations, and multicloud by seamlessly deploying third-party entities, such as MVE, at speed and scale without added resources.
In the Megaport Portal you create and manage the MVE and Virtual Cross Connects (VXCs) to cloud on-ramps and other services in the Megaport software-defined network. You host virtual instances of Palo Alto Networks Prisma SD-WAN on the MVE, managed within Palo Alto Networks centralized [Strata Cloud Manager console](https://docs.paloaltonetworks.com/strata-cloud-manager).
The following diagram shows an example network implementation of Palo Alto Networks Prisma SD-WAN features over the Megaport network.
# Terminating an MVE
Source: https://docs.megaport.com/mve/palo-alto/terminating-mve
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window appears, displaying a list of services connected to the MVE. Early termination fees are shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use your Palo Alto management console to delete the MVE.
# Terminating an MVE
Source: https://docs.megaport.com/mve/palo-alto/terminating-mve-prisma
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window appears, displaying a list of services connected to the MVE. Early termination fees are shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.\
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use your SD-WAN management console to delete the MVE.
# Connecting MVEs Integrated with Peplink FusionHub
Source: https://docs.megaport.com/mve/peplink/connect-mve-to-mve
This help topic describes how to connect two Megaport Virtual Edges (MVEs) integrated with Peplink FusionHub.
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with Peplink FusionHub to another MVE.
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer / partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [Creating an MVE Integrated with Peplink](/mve/peplink/creating-mve-peplink).
## Creating a VXC between two MVEs
A private VXC deployment between two MVEs integrated with Peplink FusionHub starts in the Megaport Portal. To complete the configuration, you use the Peplink InControl2 portal.
**To create a VXC**
1. In the Megaport Portal, go to the
**Services** page and click **+Connection** next to the originating A-End MVE.
2. Select Private VXC.
3. Select the destination B-End MVE and location.\
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `Dallas MVE 4 to LA MVE 2`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. For more information, see the Peplink FusionHub documentation.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **vNIC selection** -- Depending on the definition of the MVEs you are using, you might have to specify A-End and B-End vNICs.
* **A-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
* **B-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
For more information about vNIC selection when connecting MVEs with different services, see [Types of vNIC Connections](/mve/vnic-connections).
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.\
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. 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 through the B-End VLAN.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Click **Add VXC** to move this configuration to your cart.
8. Repeat these steps to provision any additional VXCs.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs on the Peplink FusionHub side. For more information about specific network design and configuration options before configuring interfaces for the MVEs, see the [Peplink FusionHub User Manual and Installation Guide](https://download.peplink.com/manual/FusionHub-User-Manual-and-Installation-Guide.pdf).
# Creating an MVE Integrated with Peplink
Source: https://docs.megaport.com/mve/peplink/creating-mve-peplink
This help topic describes how to create and configure Megaport Virtual Edge (MVE) with Peplink.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Peplink.
For information about the Peplink-specific settings, see [Configuring FusionHub with Cloud-init for Automated Setup](https://download.peplink.com/resources/configuring_fusionhub_with_cloud-init_for_automated_setup.pdf) and [FusionHub User Manual and Installation Guide](https://download.peplink.com/manual/FusionHub-User-Manual-and-Installation-Guide.pdf).
## Basic steps
This section summarizes the configuration steps using the Megaport Portal. Detailed procedures follow this basic step summary.
The basic steps are:
* Obtain a license from Peplink.
* Create the Peplink MVE in the Megaport Portal.
* Ensure that the connection has been established on the Peplink portal.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/peplink/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also typically create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Peplink FusionHub**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Peplink FusionHub.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Peplink FusionHub-specific settings:
* **License Data** -- Specify the Peplink FusionHub license key (the valid license for the virtual appliance). The license key is used to register the Peplink FusionHub MVE instance with the Peplink InControl2 portal. The license key must be 16 characters long.
The license key is not validated in the Megaport Portal.
* **Admin Password** -- Specify a temporary administrator password. The password must be a minimum of 8 characters and include:
* 1 uppercase character (A-Z)
* 1 lowercase character (a-z)
* 1 number (0-9)
* 1 symbol
Megaport does not store customer passwords.
* **Virtual Interfaces (vNICs)** -- Each Peplink MVE is configured with two vNICs by default. To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed.
You can add a total of five vNICs to the MVE, including the two added by default. Peplink FusionHub requires a minimum of two vNICs.\
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Enter a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with Peplink FusionHub.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select **vNIC-0** for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up a Peplink FusionHub MVE.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/peplink/creating-mve-vxc).
# Creating a VXC to an MVE Integrated with Peplink FusionHub
Source: https://docs.megaport.com/mve/peplink/creating-mve-vxc
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE) integrated with Peplink FusionHub.
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with Peplink FusionHub.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.\
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
For specific configuration details, see [Connecting MVE to MVE](/mve/peplink/connect-mve-to-mve).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/peplink/terminating-mve).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# Peplink FusionHub with Megaport Virtual Edge
Source: https://docs.megaport.com/mve/peplink/index
This help topic describes Peplink with Megaport MVE functionality.
Peplink FusionHub Virtual is a software-based SpeedFusion appliance that provides secure, scalable VPN connectivity across cloud environments. It allows you to connect, protect, and centrally manage your cloud infrastructure. The integration of Peplink FusionHub with Megaport's MVE extends the benefits of Peplink’s SpeedFusion technology to enterprises using Megaport’s global private SDN.
Key benefits of running FusionHub on MVE:
* **Seamless cloud and data center connectivity** -- MVE provides direct, low-latency access to major cloud providers, while FusionHub ensures secure and optimized VPN traffic.
* **High-performance SD-WAN** -- FusionHub enhances application performance through traffic bonding, WAN smoothing, and intelligent failover, using MVE’s Global WAN.
* **Scalability and flexibility** -- FusionHub can be deployed on demand within MVE’s virtualized network environment, enabling rapid network expansion without physical appliances.
* **Enhanced security and reliability** -- FusionHub’s encryption and VPN capabilities integrate with MVE's private connectivity to ensure data security and uptime.
* **Multi-cloud and hybrid network support** -- The combined solution allows enterprises to interconnect multiple cloud services and branch locations securely over a single network fabric.
For more information, see the [Peplink FusionHub Datasheet](https://download.peplink.com/resources/peplink_fusionhub_datasheet.pdf) and [Peplink FusionHub Virtual Appliance](https://www.peplink.com/services/software/virtual-appliance-fusionhub/).
The following diagram shows an example network implementation of Peplink FusionHub features over the Megaport network.
# Planning Your Peplink FusionHub Deployment
Source: https://docs.megaport.com/mve/peplink/plan-deployment
This help topic describes Peplink FusionHub deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
| **You Provide** | **Megaport Provides** |
| - | - |
| Internet connection from branch | Platform to host virtual SD-WAN appliances |
| SD-WAN vendor enabled at branch | Complete connection from a branch to any destination on the Megaport network and interoperation with other Megaport products and services |
| Customer premises equipment (CPE) installed in branch | Megaport Internet connection to terminate the tunnel between MVE and CPE at branch via internet |
| SD-WAN software license to use on Megaport SDN | Access to the Megaport ecosystem |
## Deployment considerations
This section provides an overview of the MVE deployment options and features.
### SD-WAN vendors
MVE is integrated with Peplink FusionHub, which uses the Peplink FusionHub SpeedFusion to create the private overlay network.
For information about all supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Peplink FusionHub**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* You can provision another MVE instance, add it to your overlay network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, add it to your overlay network, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
If you need more cores (vCPUs), you can either:
* Create a new MVE with more cores and terminate the old one (this option will require you to reconfigure your firewall).
* Create a new MVE as a second firewall to offload the capacity from the first firewall.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### Security
MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN. CSP-hosted instances of partner SD-WAN products route critical traffic across the Megaport SDN, reducing internet dependence. Traffic remains encrypted and under your policy control while traveling across the Megaport SDN, to or from, MVE.
### Licensing
Before you create an MVE in the Megaport Portal, you need user accounts with ordering permissions that provide access to the Megaport Portal. For more information, see [Creating an Account](/setting-up/registering).
In addition, you need a valid license from Peplink. To obtain an evaluation license key, first create an account using the [Peplink ID page](https://peplinkid.peplink.com/). You can use your email address or third-party providers like Microsoft or Google. After you have a Peplink account, log in to [InControl2](https://mars.ic.peplink.com/), the management and provisioning portal for Peplink's SD-WAN solution, and create an evaluation license. For more information, see the [Peplink FusionHub User Manual and Installation Guide](https://download.peplink.com/manual/FusionHub-User-Manual-and-Installation-Guide.pdf).\
After the license key is created, it will be displayed on screen and will also be sent via email to the email account configured in the InControl2 portal.
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
### vNICs
Each MVE can have up to five vNICs. An MVE is created with one vNIC by default. You can add up to four more, making a total of five. Peplink FusionHub requires a minimum of two vNICs.
Before specifying the number of vNICs on your MVE:
* Be aware that the number of vNICs cannot be changed after an MVE has been ordered. Decide in advance how many vNICs to specify when you create the MVE.
* Consult your service provider to make sure that functionality won't be affected if you add a vNIC.
If you need to change the number of vNICs after an MVE has been ordered, you will have to cancel and re-order the MVE.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
# Terminating an MVE
Source: https://docs.megaport.com/mve/peplink/terminating-mve
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window appears, displaying a list of services connected to the MVE. Early termination fees are shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use your SD-WAN management console to delete the MVE.
# Connecting MVEs Integrated with Versa Secure SD-WAN
Source: https://docs.megaport.com/mve/versa/connect-mve-to-mve
This help topic describes how to connect two Megaport Virtual Edges (MVEs) integrated with Versa Secure SD-WAN.
This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with Versa Secure SD-WAN to another MVE.
This deployment uses the Megaport private software-defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.
With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.
The internet-facing interface on an MVE can reach the internet-facing interface on another MVE over the public internet. That is, you can exchange traffic from MVE to MVE in different metros over the internet. The basic connection model consists of an MVE at one metro connecting via a Megaport Internet connection to an MVE at another metro. Connectivity consists of a customer/SD-WAN partner-managed connection, not Megaport managed. For more information, see [Megaport Internet Overview](/megaport-internet).
## Before you begin
Provision two MVEs in different locations. If you haven't already created MVEs, see [Creating an MVE Integrated with Versa](/mve/versa/creating-mve).
## Creating a VXC between two MVEs
A private VXC deployment between two MVEs integrated with Versa starts in the Megaport Portal where you create the VXC (choose A-End and B-End devices, IP addressing, VLANs, and optional BGP parameters). Then, you configure the A-End and B-End MVE devices in Director.
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and click **+Connection** next to the originating A-End MVE.
2. Select **Private VXC** and click **Next**.
3. Select the destination B-End MVE and location.\
You can use the Select Destination Port search field to narrow the selection.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable, for example, `LA MVE 2 to Dallas MVE 4`. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. Although the rate limit for a VXC can be up to several Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. Consult Versa’s documentation for more information.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **vNIC selection** -- Depending on the definition of the MVEs you are using, you might have to specify A-End and B-End vNICs.
* **A-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
* **B-End vNIC** -- Specify a vNIC by using the pre-populated default, or select from the drop-down list.
For more information about vNIC selection when connecting MVEs with different services, see [Types of vNIC Connections](/mve/vnic-connections).
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection for the A-End. To specify a VLAN ID, select **Tagged** and enter the ID in the **Specify VLAN ID** field.\
Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. 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 through the B-End VLAN.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next** to view the Summary page.
7. Click **Add VXC** to move this configuration to your cart.
8. Repeat these steps to provision any additional VXCs.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.
The next step is to configure the A-End and B-End MVEs in Versa Director.
The next procedure configures IP connectivity with BGP, providing just one solution out of many. Consult your SD-WAN vendor documentation for specific network design and configuration options before configuring interfaces for the MVEs.
## Adding MVE details to Director
After you create the VXC between your MVEs, you need to configure it in Versa Director. This involves configuring subinterfaces, IP addresses, next hops, and BGP settings for each Versa MVE.
**To configure the A-End MVE**
1. Collect the connection details from the Megaport Portal.
To display the details, click the gear icon for the VXC connection from your MVE and click the **Details** view.
2. Log in to Versa Director.
3. Select the **Workflows** tab in the top menu bar.
4. Select Template > Templates in the left navigation.
5. Click the template you want to edit, then select the **Interfaces** tab.
6. In the WAN Interfaces section, locate the Sub Interface column and click (Add) to add a subinterface.
A new row appears in the table.
7. Specify these values for the new subinterface.
* **VLAN ID** -- Enter the VLAN value from the Megaport Portal.
* **Network Name** -- Choose **+ Create WAN Network** from the drop-down menu to open the Create WAN Network window. Specify a meaningful name for the network, click **OK**, and then select the WAN network you created. (Or, if appropriate for your environment, select an existing network name.)
* **IPv4** -- Choose Static from the drop-down menu.
8. Select the **Routing** tab to add BGP configuration information.
9. In the BGP section, select the network name you previously created in the Network column.
10. Specify the following values according to your MVE configuration:
* **Local AS** -- This is the A-End MVE.
* **Neighbor IP Address** -- This is the B-End MVE.
* **Peer AS** -- This is the B-End ASN.
* Optionally, you can enable BFD (as appropriate for your network).
The values for Local AS and Peer AS come from your network design. They are not part of the Megaport MVE/VXC.
11. Click (Add) to the right of the settings.
12. Click **Recreate** (at the bottom of the page).
A window opens that shows the differences of the configuration. The auto-merged version is recommended, and selected by default.
13. Click **Deploy**.
You can use variables in the template to specify values per device for these fields: **Router ID**, **Local AS**, **Peer AS**, and **Password**.
The Instance ID cannot be modified (the system automatically specifies a value) and the Static IP address is parameterized by default.
**To parameterize Router ID, BGP Local AS, Peer AS, and Password**
1. Select the **Configuration** tab in the top menu bar.
2. Select **Templates** > **Device Templates** in the horizontal menu bar.
3. Click your template.
By default, the Interfaces column appears.
4. In the left navigation, select **Virtual Routers** and click your network to open the Edit window.
5. In the Edit window, select BGP, then click the Instance ID to open the Edit BGP Instance window.
6. In the Edit BGP Instance window, click (Parameterize) next to each of the following fields: **Router ID**, **Local AS**, **Peer AS**, and **Password**.
7. Click **OK** two times to update.
8. Select the **Workflows** tab in the top menu bar, then select Devices > Devices in the left navigation.
9. Click your device to specify values for the variables you just created.
The Add Device window opens.
10. Select the **Bind Data** tab.
11. Specify values for the variables.
* **Local AS** -- Enter the A-End ASN.
* **Password** -- Enter the MD5 password.
* **Peer AS** -- Enter the B-End ASN.
* **Router ID** -- Enter the A-End IP address.
* **Hop Address** -- Enter the B-End IP address.
* **Static Address** -- Enter the A-End IP address, including the mask value.
12. Click **Redeploy** when finished.
When the new configurations for the device are prepared successfully, a green checkmark appears at the bottom of the Versa Director window.
13. To push the changes to the device, click **Commit Template** (on the upper right).
The Commit Template to Devices window opens.
14. Specify the following in the Commit Template to Devices window:
* **Organization** -- Select your organization from the drop-down menu.
* **Select Template** -- Select the template to push to the device from the drop-down menu.
Note that the Template State is OUT\_OF\_SYNC.
15. Click the eye icon in the Differences column to verify your configuration changes.
16. Click **Commit to Device**.
A green checkmark appears at the bottom right of the screen when the push is successful. The Template State is now IN\_SYNC.
Next, configure the B-End MVE.
There are multiple ways to configure A-End and B-End MVEs using Versa templates and workflows. The steps depend on how you have grouped devices and assigned templates. For example, if both MVEs are in the same device group and shared the same template, you can make changes to the variables in Bind Data for the B-End device to configure the connection.
These steps describe how to configure them using different templates.
**To configure the B-End MVE**
1. In Director, select the **Workflows** tab in the top menu bar.
2. Select Template > Templates in the left navigation.
3. Click the template you want to edit, then select the **Interfaces** tab.
4. In the WAN Interfaces section, locate the Sub Interface column and click (Add) to add a subinterface.
A new row appears in the table.
5. Specify these values for the new subinterface.
* **VLAN ID** -- Enter the VLAN value from the Megaport Portal.
* **Network Name** -- Choose the same network name as the A-End device from the drop-down menu.
* **IPv4** - Choose Static from the drop-down menu.
6. Select the **Routing** tab to add BGP configuration information.
7. In the BGP section, select the network name for the connection in the Network column.
8. Specify the following values according to your MVE configuration:
* **Local AS** -- This is your local MVE: B-End.
* **Neighbor IP Address** -- This is the A-End IP address.
* **Peer AS** -- This is the A-End ASN.
* Optionally, you can enable BFD (as appropriate for your network).
9. Click (Add) to the right of the settings.
10. Select the **Management Servers** tab, then click **Recreate** (at the bottom of the page).
A window opens that shows the differences of the configuration. The auto-merged version is recommended and selected by default.
11. Click **Deploy**.
You can use variables in the template to specify values per device for these fields: **Router ID**, **Local AS**, **Peer AS**, and **Password**.
The Instance ID cannot be modified (the system automatically specifies a value) and the **Static IP address** is parameterized by default.
**To parameterize Router ID, BGP Local AS, Peer AS, and Password**
1. Select the **Configuration** tab in the top menu bar.
2. Select **Templates** > **Device Templates** in the horizontal menu bar.
3. Click your template.
By default, the Interfaces section appears.
4. In the left navigation, select **Virtual Routers** and click your network to open the Edit window.
5. In the Edit window, select BGP, then click the Instance ID to open the Edit BGP Instance window.
6. In the Edit BGP Instance window, click (Parameterize) next to each of the following fields: **Router ID**, **Local AS**, **Peer AS**, and **Password**.
7. Click **OK** two times to update.
8. Select the **Workflows** tab in the top menu bar, then select Devices > Devices in the left navigation.
9. Click your device to specify values for the variables you just created.\
The Add Device window opens.
10. Select the **Bind Data** tab.
11. Specify values for the variables.
* **Local AS** -- Enter the B-End ASN.
* **Password** -- Enter the MD5 password.
* **Peer AS** -- Enter the A-End ASN.
* **Router ID** -- Enter the B-End IP address.
* **Hop Address** -- Enter the A-End IP address.
* **Static Address** -- Enter the local IP address, including the mask value.
12. Click **Redeploy** when finished.\
When the new configurations for the device are prepared successfully, a green checkmark appears at the bottom of the Versa Director window.
13. To push the changes to the device, click **Commit Template** (on the upper right).
The Commit Template to Devices window opens.
14. Specify the following in the Commit Template to Devices window:
* **Organization** -- Select your organization from the drop-down menu.
* **Select Template** -- Select the template to push to the device from the drop-down menu.
Note that the Template State is OUT\_OF\_SYNC.
15. Click the eye icon in the Differences column to verify your configuration changes.
16. Click **Commit to Device**.\
A green checkmark appears at the bottom right of the screen when the push is successful. The Template State is now IN\_SYNC.
**To verify the connection**
1. Select the **Monitor** tab in the top navigation bar, select Devices in the horizontal navigation bar, and then select your device to view details in the Summary screen.
2. In the Summary screen you can review your subinterface in the Interface column, and the Operational and Admin Status.
# Creating an MVE Integrated with Versa
Source: https://docs.megaport.com/mve/versa/creating-mve
This help topic describes how to create and configure a Megaport Virtual Edge (MVE) with Versa Secure SD-WAN.
This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Versa Secure SD-WAN. Before you begin, you need user accounts with ordering permissions that provide access to the Megaport Portal and to Versa.
For more information about setting up a Megaport account, see [Creating an Account](/setting-up/registering).
Versa provides documentation for their SD-WAN product, including Versa Director and cloud connections, at [VOS SD-WAN Configuration Product Documentation](https://docs.versa-networks.com/Versa_Operating_System/VOS_SD-WAN_Configuration).
## Basic steps
The basic steps to configure an MVE with Versa are:
* Obtain information for Versa Director.
* Create a new workflow template in Director.
* Add a new device group in Director.
* Add a new device in Director.
* Create the Versa MVE Instance in the Megaport Portal.
* View the MVE public IP address assignment in the Megaport Portal.
* Verify that the MVE is registered and is in-sync from the Versa Director UI.
The following sections provide detailed instructions.
## Obtaining required information for Versa Director
To set up Versa you need the following information:
* **Versa Director IPv4 address or FQDN** -- For example: cloud211.versa-networks.com.
* **Versa Controller IPv4 address or FQDN** -- In Versa Director, select the **Configuration** tab in the top menu bar. Select Templates > Device Templates in the horizontal menu bar, and select a template. In the template details page, select the **Services** tab (the gear icon) and then select SDWAN > System > Controller Config. The window displays a list of controllers, their IP address, and any assigned FQDNs.
* **Local Auth String** -- The default is `SDWAN-Branch@Versa.com` which can be modified in Versa Director.
* **Remote Auth String** -- The default is `Controller-1-staging@Versa.com` which can be modified in Versa Director.
* **Serial Number** -- This value is created when you add a new device in Versa Director.
## Creating a new workflow template in Director
The next step is to create a new workflow template and device in Versa Director. Versa strongly suggests using their workflows for creating templates and devices. The workflows automatically build and create some behind-the-scenes configurations and variable values that could otherwise be missed.
**To create a new workflow template in Director**
1. Log in to Versa Director.
2. Select the **Workflows** tab in the top menu bar.
3. In the left navigation, select Template > Templates.
4. Click (Add) to create a template.
5. In the **Basic** tab, specify these details.
* **Name** -- Enter a name for the staging template.
* **Type** -- Select the template type SDWAN Post Staging from the drop-down menu.
* **Organization** -- Select the provider organization to associate with the template.
* **Device Type** -- Select SDWAN from the drop-down menu.
* Select the appropriate role (Full Mesh, Hub, Hub Controller, or Spoke).
* **Controllers** -- Select a controller node from your network to associate with the template.
* **Subscription** -- Select the appropriate subscription information for your network.
* **Solution Tier** -- Network service to be configured.
* **Service Bandwidth** -- Allocated bandwidth for the service in Mbps.
* **Preferred Software Version** -- Preferred version of the software that should be deployed on Versa Director. The preferred software version applies to zero-touch provisioning (ZTP). During ZTP, Versa Director upgrades a branch to the preferred version, if applicable. The preferred version can be backward compatible for up to two previous VOS versions.
For more information about creating Versa staging templates, see [Create and Manage Staging and Post-Staging Templates](https://docs.versa-networks.com/Versa_Operating_System/VOS_SD-WAN_Configuration/Basic_SD-WAN_Configuration/Create_and_Manage_Staging_and_Post-Staging_Templates).
6. Select the **Interfaces** tab and specify these details.
* **Number of Ports** -- Choose 4. MVE requires 4 ports.\
Note, Port 0 is reserved for management (Mgmt) and cannot be changed.
* Click the icon for port 1 and select **WAN** from the drop-down menu. A row is added to the WAN Interfaces list. (The WAN interface is automatically configured by the MVE creation process to connect through the Megaport Internet connection with bandwidth determined by the MVE size.)
* **VLAN ID** -- The value should be set to **0**.
* **Network Name** -- The value should be set to **INET-1**.
* **IPv4** -- The value should be set to **DHCP**.
* The remaining fields can be left unchanged.
You can optionally enter circuit information.
7. Click **Continue** (at the bottom right) until you see the **Create** option, then click **Create**.
You can now apply the template to a new device group.
## Adding a new device group in Director
The next step is to create a new device group.
1. Log in to Versa Director.
2. Select the **Configuration** tab in the top menu bar.
3. In the horizontal menu bar, select Devices > Device Groups.
4. Click (Add) to add a device group.
5. Specify these details:
* **Name** -- Enter a name for the device group that is easily identifiable.
* **Description** -- Enter descriptive information about the device group.
* **Tags** (optional) -- Enter strings for users to search on.
* **Organization** -- Select your organization from the drop-down.
* **Post Staging Template** -- Select the template you created previously.
6. Click **OK**.
## Adding a new device in Director
The next step is to add a new device.
1. Log in to Versa Director.
2. Select the **Workflows** tab in the top menu bar.
3. In the left navigation, select Devices > Devices.
4. Click (Add) to open the Add Device window.
5. In the **Basic** tab, specify these details.
* **Name** -- Specify a meaningful name for the device.
* **Global Device ID** -- Versa Director automatically assigns the next available ID.
* **Organization** -- Choose your organization from the drop-down.
* **Deployment Type** -- Choose **CPE-Baremetal Device** from the drop-down.
* **Serial Number** -- Enter a serial number for the device. Specify a unique and meaningful value for the device and make a note of it, as you need it again when creating the Versa MVE instance in the Megaport Portal.
* **Device Groups** -- Choose the device group you created previously. This will assign the new device to that device group.
6. Click **Continue**.
7. In the **Location Information** tab, enter the country where the device is located.
8. Click **Continue** until you see the **Deploy** button.
9. Click **Deploy**.\
The new device is now deployed in Versa Director.
## Creating an MVE in the Megaport Portal
When creating an MVE, select a location that supports the MVE and is in a compatible metro area for your network design. You can connect multiple locations to an individual MVE. For more information about location details, see [Planning Your Deployment](/mve/versa/plan-deployment).
You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons. As part of the MVE creation process, you will also typically create a Megaport Internet connection.
**To create an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Versa FlexVNF**.
4. Select the software version.
The MVE will be configured to be compatible with that version of Versa.
5. Click **Next**.
6. Specify the MVE details:
* **Location** -- Select the MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
The country you choose must be a market in which you have already registered.
If you haven't registered a billing market in the location where you will deploy the MVE, follow the procedure in [Enabling Billing Markets](/finance/enabling-market).
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
* **Diversity Zone** -- Select a diversity zone.
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the Summary page at the end.\
For more information, see [MVE Diversity](/mve/mcr-mve-diversity).
* **Size** -- Select a size from the list of available sizes. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
7. Click **Next**.
8. Specify the Versa-specific settings:
* **Director Address** -- Enter the FQDN or IPv4 address of your Versa Director.
* **Controller Address** -- Enter the FQDN or IPv4 address of your Versa Controller.
* **Local Auth** -- Enter the Local Auth string as configured in your Versa Director.
* **Remote Auth** -- Enter the Remote Auth string as configured in your Versa Director.
* **Serial Number** -- Enter the serial number that you used when creating the device in Versa Director.
* **Virtual Interfaces (vNICs)** -- Each MVE is configured with one vNIC named *Data Plane* by default. To change the name, type over the name text in the box. You can also change the vNIC name later, after the MVE has been deployed.
You can add a total of five vNICs to the MVE, including the one added by default. For more information, see [Types of vNIC Connections](/mve/vnic-connections).
To add a vNIC:
1. Click **+ Add**.
2. Enter a name for the vNIC.
If you want to increase or decrease the number of vNICs on this MVE after it has been deployed, you will have to delete the entire MVE and recreate it. You cannot add or delete vNICs on a deployed MVE.
* **Megaport Marketplace** -- By default, each service is private to your enterprise and consumes services from the Megaport network for your own internal company, team, and resources. When set to private, the service is not searchable in the Megaport Marketplace, however, others can still connect to you using a [service key](/marketplace/service-keys). Megaport Marketplace visibility is controlled on your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
9. Click **Next**.
10. Specify optional settings:
* **MVE Name** -- Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
The MVE name is auto-generated based on the location name and shown on the Summary page. You can override it by entering your own.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
11. Confirm the configuration and pricing on the Summary page.
The monthly rate is based on location and size.
12. Click **Add MVE**.
You are prompted to create a Megaport Internet connection. A Megaport Internet connection provides connectivity and allows MVE to register and communicate with Versa SD-WAN.
**To create the Megaport Internet connection**
1. Click **Create Megaport Internet** to proceed (recommended), or click **Not now** to provision internet access at a later time.
MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Megaport Internet connection or configure a third-party internet connection using a private VXC. **We strongly recommend that you create a Megaport Internet connection for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly**.
2. Select the target Port (the internet router).\
The B-End of a Megaport Internet connection can be anywhere that Megaport Internet is available.\
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your Megaport Internet connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use the same Service Level Reference numbers for the Megaport Internet connection and MVE to help identify the matching pair in your invoice.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit is configurable starting from 20 Mbps and can scale to several Gbps or more, in 1 Mbps increments. Available speed tiers might vary by location and service type. You can change the speed as required after you create the Megaport Internet connection. Monthly billing details appear based on location and rate limit.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select **vNIC-0** for initial management access.
* **Preferred A-End VLAN** (optional) -- Select **Untagged** to remove VLAN tagging and allow first-time administrative login to the device.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to proceed to the connection detail summary.
6. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision any additional VXCs.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Ordering MVE provisions the appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up a Versa FlexVNF.
## Viewing the MVE in the Megaport Portal
After creating the MVE, you can view it in the Megaport Portal on the Services page. You can also view the public IP addresses assigned.
**To view an MVE in the Megaport Portal**
* Go to the **Services** page.
The Megaport Internet icon differs from a standard VXC icon in the Megaport Portal, as shown in the image.
For more information about the Services page, see [Understanding the Services Page](/portal-admin/services-page).
**To view the public IP addresses assigned to the MVE**
1. Click the gear icon next to the Megaport Internet connection.\
The Connection Configuration screen appears. From here, you can modify any of the Megaport Internet connection details.
2. Select the **Details** tab.
3. Locate the public IP address (IPv4 or IPv6).\
These are the public IP addresses assigned to the MVE. Make a note of these addresses for use later.
4. Verify that you see your new MVE device in the Megaport Portal under **Services**.
## Viewing the MVE in Versa Director
After creating the MVE, you can monitor the status in Director. In Director, verify that the new MVE configuration is synchronized, the service is up, and it is reachable.
**To view an MVE in Director**
1. Log in to Versa Director.
2. Select the **Monitor** tab, then select Devices in the horizontal menu.
3. Review the Config Synchronized, Reachability and Service columns.
It can take up to 10 minutes for the MVE to register with Versa Director.
## Next steps
Once the MVE is provisioned with an Active status, the next step is to connect a VXC to a Cloud Service Provider (CSP), a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.
For more information, see [Creating a VXC](/mve/versa/creating-mve-vxc).
# Creating a VXC to an MVE Integrated with Versa FlexVNF
Source: https://docs.megaport.com/mve/versa/creating-mve-vxc
This help topic describes how to connect a VXC to Megaport Virtual Edge (MVE) integrated with Versa Secure SD-WAN.
This topic describes how to connect a Virtual Cross Connect (VXC) to Megaport Virtual Edge (MVE) integrated with Versa.
With MVE configured, you can create VXCs to connect to services on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MVE) and a B-End (one of the destination types).
A VXC is mapped with a VLAN ID on each end.
You can order VXCs to reach any destination in the Megaport network. The maximum number of VXCs you can connect to a single MVE depends on its size. For more information, see [Megaport Limits and Quotas](/limits-quotas/#mvelimits).
**To create a VXC**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. If this is the first connection for the MVE, click the Cloud tile that matches the VXC type. The tile is a shortcut to the configuration page.\
Alternatively, click **+Connection** and select a cloud destination:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
For specific CSP configuration details:
* AWS Direct Connect -- See [Creating MVE Connections to AWS](/cloud/mve/versa/aws).
* Azure Express Route -- See [Creating MVE Connections to Azure using ExpressRoute](/cloud/mve/versa/azure).
* Google Cloud -- See [Creating MVE Connections to Google](/cloud/mve/versa/google).
* Other cloud connections -- See [Creating MVE Connections to Any Endpoint](/cloud/mve/versa/generic).
## Connecting MVE to MVE
In the Megaport Portal, you can create a VXC (interconnect connectivity) between MVEs at two or more Megaport locations. The VXC links the branch locations connected to these edge MVEs via the Megaport network, without traversing the public internet for the MVE to MVE connectivity.
For specific configuration details, see [Connecting MVE to MVE](/mve/versa/connect-mve-to-mve).
## Terminating a VXC
You can terminate a VXC directly from the Megaport Portal. Terminating an MVE automatically deletes all of its associated VXCs, including the Megaport Internet connection. For more information about terminating an MVE, see [Terminating an MVE](/mve/versa/terminating-mve).
For more information about terminating a VXC, see [Terminating a VXC](/connections/terminating-vxc).
# Versa Secure SD-WAN with Megaport Virtual Edge
Source: https://docs.megaport.com/mve/versa/index
This help topic describes Versa Secure SD-WAN with Megaport MVE functionality.
Versa Secure SD-WAN creates the private overlay network and manages the network connections and network policies. The Megaport Portal is used to create and order the MVE and create and manage the Virtual Cross Connects (VXCs) to the cloud on-ramps and other services in the Megaport SDN. The Versa Secure SD-WAN fabric acts as the overlay, and the Megaport SDN acts as the underlay.
Versa offers several management system options. For simplicity, this documentation describes deployments using the Versa Director console.
The following diagram shows an example network implementation of Versa Secure SD-WAN features over the Megaport network.
# Planning Your Versa Secure SD-WAN Deployment
Source: https://docs.megaport.com/mve/versa/plan-deployment
This help topic describes Versa Secure SD-WAN deployment considerations for the Megaport Virtual Edge (MVE).
This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).
| **You Provide** | **Megaport Provides** |
| - | - |
| Internet connection from branch | Platform to host virtual SD-WAN appliances |
| SD-WAN vendor enabled at branch | Complete connection from a branch to any destination on the Megaport network and interoperation with other Megaport products and services |
| Customer premises equipment (CPE) installed in branch | Megaport Internet connection to terminate the tunnel between MVE and CPE at branch via internet |
| SD-WAN software license to use on Megaport SDN | Access to the Megaport ecosystem |
### Versa Secure SD-WAN features
Versa Secure SD-WAN focuses on these key capabilities:
* **SD-WAN and Secure Access Service Edge (SASE)** -- A single platform with a best-of-class security offering. For more information, see [Securing the Network with SASE](/mve/sase).
* **One software stack** -- A single-pipeline integrated architecture for security, advanced networking, robust analytics, and automation.
The Versa Operating System (VOS) delivers both next-generation firewall (NGFW) and SD-WAN services on a single virtual machine. The VOS appliance deployed as a virtual machine on MVE not only optimizes edge-to-cloud network connectivity, but also enforces advanced security services and policies across the Megaport backbone segments.
Versa SASE gateway functionality can also be deployed on MVE as part of the many VOS capabilities. Versa refers to this deployment model as *private gateways*, which offer the same functionality as Versa Cloud Gateways but instead run on a customer or service provider platform.
The highly flexible VOS hosted on MVE provides these core SASE services:
* Cloud access security broker (CASB)
* Next-generation firewall (NGFW)
* Secure web gateway (SWG)
* Zero trust network access (ZTNA)
The Versa Secure Access Client (VSAC) is the endpoint security agent that extends SD-WAN and security services to client devices. The VSAC provides Intelligent Gateway Selection, allowing the client to connect to a Versa Cloud Gateway or a private gateway (on MVE). The VSAC policies steer client network traffic based on the specific application. For example, client network traffic for a real-time financial trading application hosted in AWS can be routed through VOS on MVE, whereas traffic for a cloud-based file storage repository can be routed through the Versa Cloud Gateway.
For more information, see
[VOS Versa Operating System](https://versa-networks.com/documents/datasheets/versa-vos.pdf) and [Versa Secure Private Access](https://versa-networks.com/documents/datasheets/versa-secure-private-access.pdf).
## Deployment considerations
This section provides an overview of the MVE deployment options and features.
### SD-WAN vendors
MVE is integrated with Versa Secure SD-WAN, which uses Versa's Director console to create the private overlay network.
For information about all supported on the MVE platform, see the [Megaport Virtual Edge (MVE) product page](https://www.megaport.com/products/megaport-virtual-edge/).
### MVE locations
For a list of global locations where you can connect to an MVE, see [Megaport Virtual Edge Locations](/mve/locations).
### Sizing your MVE instance
The instance size determines the MVE capabilities, such as how many concurrent connections it can support. To size your MVE correctly, consult the vendor's sizing documentation to ensure it aligns with the number and type of features you plan to enable.
When choosing an MVE instance size, keep in mind these items:
* Any increase on the network data stream load can degrade performance. For example, establishing secure tunnels with IPsec, adding traffic path steering, or using deep packet inspection (DPI) can affect the maximum throughput speed.
* Future plans to scale the network.
To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location.
**To check the MVE instance sizes in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **MVE**.
3. Select **Versa FlexVNF**.
4. Select the software version.
5. Click **Next**.
6. Select an MVE location.
Select a location geographically close to your target branch and/or on-premises locations.
You can use the **Search** field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled **Available**. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
If the MVE size you want is not in the list, then there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
**What if I need more MVE capacity in the future?**
To increase your MVE capacity, you have these options:
* You can provision another MVE instance, add it to your overlay network, and split the workload between the two MVEs.
* You can provision a larger MVE instance, add it to your overlay network, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
You can adjust the Megaport Internet bandwidth at any time without having to tear down the virtual machine.
### Security
MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN. CSP-hosted instances of partner SD-WAN products route critical traffic across the Megaport SDN, reducing internet dependence. Traffic remains encrypted and under your policy control while traveling across the Megaport SDN, to or from, MVE.
Versa Secure SD-WAN includes access to a comprehensive security feature: . Versa on MVE natively supports SASE and SD-WAN services. For more information, see [Securing the Network with SASE](/mve/sase).
### Licensing
You bring your own Versa (Director) SD-WAN license for use with MVE. It is your responsibility to have the appropriate licenses for the SD-WAN endpoints created on the Megaport network.
### VLAN tagging
Megaport uses to differentiate VXCs and MVEs on a host hardware system. The tenant MVE receives untagged traffic for the internet-facing link, and single-tagged 802.1Q traffic for VXCs toward other destinations on the Megaport network (such as CSP on-ramps or other MVEs). For more information, see [Configuring Q-in-Q](/connections/q-in-q).
### vNICs
Each MVE can have up to five vNICs. An MVE is created with one vNIC by default. You can add up to four more, making a total of five.
Before specifying the number of vNICs on your MVE:
* Be aware that the number of vNICs cannot be changed after an MVE has been ordered. Decide in advance how many vNICs to specify when you create the MVE.
* Consult your service provider to make sure that functionality won't be affected if you add a vNIC.
If you need to change the number of vNICs after an MVE has been ordered, you will have to cancel and re-order the MVE.
For more information, see [Types of vNIC Connections](/mve/vnic-connections).
# Terminating an MVE
Source: https://docs.megaport.com/mve/versa/terminating-mve
This help topic describes how to terminate an MVE directly from the Megaport Portal.
You can terminate an MVE directly from the Megaport Portal. Terminating an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about MVE contract terms, see [MVE Pricing and Contract Terms](/finance/mve-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate an MVE**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the MVE you want to terminate.
The Terminate Services window appears, displaying a list of services connected to the MVE. Early termination fees are shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the MVE. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the MVE termination, or click **No, Keep Services** to cancel.
The MVE and its associated VXCs are deleted from the Megaport network.
5. Use your SD-WAN management console to delete the MVE.
# Creating MCR Connections to AWS
Source: https://docs.megaport.com/cloud/mcr/aws
This help topic describes how to create a VXC from an MCR to AWS Direct Connect.
You can create a VXC from an MCR to AWS Direct Connect (DX) through the Megaport Portal. Follow the steps in this topic to establish a private, public, or transit VIF connection that can connect either directly to a selected VPC or to a range of VPCs either in a single or multiple AWS regions (within a single AWS account).
## Prerequisites
### Private Virtual Interface
Before you create a private connection from an MCR to AWS, make sure you have the following:
* Your
[AWS Account number](https://docs.aws.amazon.com/general/latest/gr/acct-identifiers.html#FindingYourAccountIdentifiers).
* An AWS
[virtual private gateway](https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html) or
[Direct Connect gateway](https://docs.aws.amazon.com/directconnect/latest/UserGuide/direct-connect-gateways.html) associated with your VPCs.
* The ASN number for the AWS gateway.\
When creating the AWS gateway, we recommend private ASNs for private connections
and we recommend replacing the AWS default ASN (usually 7224) as routing multiple
VXC instances to the same target ASN can result in routing anomalies.
* An MCR.\
If you don't currently have an MCR, create one following the procedures
in [Creating an MCR](/mcr/creating-mcr).
The preferred manner for inter-region peering is multiple VXCs
from a single MCR with individual connections to VGWs (often abbreviated
VGW). (This model also supports inter-region peering between VPCs from
multiple accounts.) Direct Connect gateways can aggregate multiple VGWs
from local and remote regions and this method is more extensible than
the VGW option, however, this option requires careful consideration of
traffic paths and latency implications. We recommend that you consult
the AWS documentation for information on the rules and limits imposed on the
connection types.
### Public Virtual Interface
You can create a public virtual interface to connect your MCR to public resources (non-VPC services).
To connect to public resources such as Amazon Simple Storage Service
(S3) and Amazon DynamoDB, AWS generally requires you to bring public IP
addresses to this connection. However, with the MCR, Megaport supplies a
/31 range for public peering and for the global AWS route tables.
Public VIFs are not required to terminate onto a virtual private gateway
or Direct Connect gateway and the target ASN will be the AWS public ASN
for the destination region.
For a public connection, you need your AWS Account number.
### Transit Virtual Interface
Before you create a transit connection from an MCR to AWS, make sure you
have the following:
* Your [AWS Account number](https://docs.aws.amazon.com/general/latest/gr/acct-identifiers.html#FindingYourAccountIdentifiers).
* An AWS [transit gateway](https://docs.aws.amazon.com/vpc/latest/tgw/tgw-getting-started.html)
attached to your Direct Connect gateway.
* The ASN number for the Direct Connect gateway attached to the transit gateway.
* An MCR.
## Connecting an MCR to AWS Direct Connect
Once you have the prerequisites met, you can create the VXC to AWS from the MCR.
The VXC connection can be one of two AWS models: Hosted VIF or Hosted Connection.
Hosted VIFs can connect to public or private AWS cloud services: a
Hosted VIF cannot connect to a transit virtual interface. The Hosted VIF
is fully integrated with AWS and provides access to the routing
information for automatic configuration of your MCR BGP peering.
A Hosted Connection can support one private, public, or transit virtual
interface. The Hosted Connection configuration process does not have
automatic access to routing information for the MCR and you need to
configure the routing manually and specify BGP peering details on both
the AWS virtual interface and the MCR A-End configuration in the Megaport Portal.
For more information about each connection type, see [Connecting to AWS Direct Connect](/cloud/megaport/aws).
**Overview of the workflow**
The following flowchart outlines the steps to set up an AWS Hosted VIF or Hosted Connection between your device and AWS via Megaport.
## Creating a Hosted VIF connection
AWS Hosted Virtual Interfaces (Hosted VIF) do not support diversity zones. To ensure connection diversity for Hosted VIFs, create VXCs to two destination ports in different data centers, instead of two ports in separate diversity zones.
**To create a Hosted VIF VXC from an MCR to AWS**
1. In the Megaport Portal, go to the **Services** page and select the MCR you want to use.
2. Click **+Connection** and click **Cloud**.
3. Select AWS as the service provider, select Hosted VIF as the AWS Connection Type, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Click **Next** to acknowledge the MCR Connection details.
7. Specify the connection details for the AWS service.
For private Hosted VIFs, only the AWS Connection Name, AWS Account ID,
and Amazon ASN fields are mandatory. For public Hosted VIFs, only the
AWS Connection Name and AWS Account ID are mandatory.
For both public and private connections, the BGP peering fields (BGP
Auth Key, Customer IP Address, and Amazon IP Address) are automatically populated
when the connection is created - although you can enter manual values if
you have specific requirements.
Here are details for each field:
* Select **Public** or **Private**.
* **Private** -- Access private AWS services such as a VPC, EC2
instances, load balancers, RDS DB instances, on private IP address
space.
* **Public** -- Access public AWS services such as Amazon Simple Storage
Service (S3), DynamoDB, CloudFront, and Glacier. You will also receive [Amazon's global IP prefixes](https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html) (approximately 2,000 prefixes).
Public VIFs require manual intervention from Amazon and could take up to 72 hours. For more information, see [Configuring Public AWS Connections with IP Addresses Provided by AWS](/cloud/megaport/aws/aws-public-ip).
* **AWS Connection Name** -- This is a text field and will be the name
of your virtual interface that appears in the AWS console. The AWS
Connection Name is automatically populated with the name specified in a
previous step.
* **AWS Account ID** -- This is the ID of the account you want to
connect. You can find this value in the management section of your
AWS console.
* **Customer ASN** (optional) -- Specifies the ASN used for
BGP peering sessions on any VXCs connected to the MCR. This value
is defined when you configure the MCR and, once defined, it cannot
be changed. The default value is the Megaport public ASN 133937.
* **Amazon ASN** -- For private connections, this value needs to match
either the ASN for the AWS virtual private gateway (for 1:1 VPC
connections) or the ASN for the AWS Direct Connect gateway. For public connections, if you supply this value, it will be ignored and the ASN will be the AWS public ASN for the destination region.
* **BGP Auth Key** (optional) -- Specify the BGP key. If you leave this blank, Megaport negotiates a key automatically for you with AWS which will be displayed in the Megaport Portal. The key is not displayed in the AWS console.
The BGP Auth Key is generated during the ordering process when this field is left blank. It will not be displayed on the Summary page when ordering. To see the key, view the Connection Settings after the service has been deployed and is live.
* **Customer IP Address** (optional) -- The IP address space (in CIDR format) used on your network for peering. If left blank, Megaport assigns an address.
* **Amazon IP Address** (optional) -- The IP address space in CIDR format assigned in the AWS VPC network for peering. If left blank, Megaport automatically assigns an address.
* **Prefixes** (optional) -- (visible for Public connections only) Specify IP Prefixes to announce to AWS. Specify the prefixes you will advertise when deploying a Public Direct Connect (RIR-assigned IPv4 addresses only).\
Once you configure Prefixes for a Public connection, you cannot change them and the field is grayed out. To change this value, create a support ticket with AWS so they can make this change in a non-impacting way. Or, you can cancel the Hosted VIF and reorder. In both cases, you need to wait for AWS to manually approve the request.
8. Click **Next** to proceed to the connection detail summary, and add the
VXC to the cart.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Once the VXC connection is deployed successfully, it appears on the Portal Services page associated with the MCR.
Click the VXC title to display the details of this connection.
For private connections, in the Details section, the service
status (Layer 2) is up but BGP (Layer 3) will be down because the
matching configuration does not exist on the AWS side. This will be
configured once you accept the virtual interface in the AWS console.
#### Accepting the Virtual Interface for Private Connections
Two to three minutes after ordering a private Hosted VIF VXC, the
corresponding inbound VIF request is visible on the AWS Direct
Connect > Virtual Interfaces
page in the AWS console. (This is specific to the region associated with
the target AWS port.) If your VIF doesn't appear after a few minutes,
confirm that you are viewing the correct region.
**To review and accept the private virtual interface**
1. From the AWS Direct Connect > Virtual Interface page, click the ID
of the interface to display the configuration and peering details.
The name and account ID of the VIF should match the values supplied in
the Portal and the BGP ASN should match the Customer ASN configured with
the VXC. The Amazon Side ASN is the default region's AWS ASN and
not the value specified during the configuration - this is
updated in the next step when the virtual interface is accepted and
assigned.
2. Click **Accept**.
3. Select the gateway type and then the specific gateway for this new
virtual interface.
4. Click **Accept virtual interface**.
After you accept the interface, the Amazon side ASN field changes to the
ASN value specified in the configuration. The state of the connection
changes from *confirming* to *pending*, and then changes to *available* once BGP has
established. Note that sometimes there is a delay in the *available* BGP
status appearing on the AWS end, though you can confirm the current state
of the Layer 3 link through the Portal view.
#### Accepting the Virtual Interface for Public Connections
Several minutes after ordering a public Hosted VIF VXC, the
corresponding inbound VIF request appears on the AWS Direct
Connect > Virtual Interfaces page in the AWS console. (This is specific to the region associated with
the target AWS port.)
**To review and accept the public virtual interface**
1. From the AWS Direct Connect > Virtual Interface page, click the ID
of the interface to display the configuration and peering details.
2. Review the configuration details and click **Accept**, and when
prompted, click **Confirm**.
The state of the connection changes from *confirming* to *verifying*. At
this point, the connection needs to be verified by Amazon - a process
that can take up to 72 hours. When verified, the state changes to
*available*.
## Creating a Hosted Connection
**To create a Hosted Connection VXC from an MCR to AWS**
1. In the Megaport Portal, go to the **Services** page and select the MCR you want to use.
2. Click **+Connection** and click **Cloud**.
3. Select AWS as the service provider, select Hosted Connection as the AWS Connection Type, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection. You can also filter by diversity zone.\
Each destination port has either a blue or red icon to indicate its diversity zone. To achieve diversity, you need to create two connections with each one in a different zone.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. For the MCR Connection detail, provide an IP address in CIDR format.\
This value is the IP address for the interface and is the MCR IP address
used for BGP peering to AWS.
Assign a /30 address in private address space.
You can add a secondary IP address, if needed.
You can change these values in the A-End details of the VXC configuration.
7. 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 automatically populated based on the address
you specified as interface IP addresses.
* **Peer IP** -- The IP address for the BGP peer. In this example, the
local IP is 192.168.100.1 so the peer IP address would be
192.168.100.2.
* **Peer ASN** -- The ASN of the AWS gateway.
* **BGP Password** -- The shared key to authenticate the peer. This field is optional for the creation of the VXC, but is required to set up
the BGP peering. You can add it after you create the VXC.
The shared key length is from 1 to 25 characters. The key can include any of these characters:
a-z\
A-Z\
0-9\
! @ # . \$ % ^ & \* + = - \_
Click the eye icon to see the password as you type. The view persists until you click the eye icon again to hide the password.
* **Description** (optional) -- Enter a description that will help identify this connection. The minimum description length is from 1 to 100 characters.
* **BGP State** -- Shuts down the connection without removing it. The initial setting will be taken from the setting on the A-End of the MCR. Enabling or shutting down the BGP state does not affect existing BGP sessions. The BGP state only affects new VXCs. This setting overrides the MCR state for an individual connection. For more information, see [Creating an MCR](/mcr/creating-mcr).
When you create the virtual interface in the AWS console for this
connection, you will match these values.
8. Click **Add**.\
The BGP details appear under BGP Connection details.
9. Click **Next**.
10. Specify the connection details for the AWS service.
* **AWS Connection Name** -- This is a text field and will be the name of your virtual interface that appears in the AWS console. The AWS Connection Name is automatically populated with the name specified in a previous step.
* **AWS Account ID** -- This is the ID of the account you want to connect. You can find this value in the management section of your AWS console.
11. Click **Next** to proceed to the connection detail summary, click **Add VXC**, and order the connection.
Once the VXC connection is deployed successfully, it appears on the Megaport Portal Services page and is associated with the MCR. Click the VXC title to display
the details of this connection. Note that the service status (Layer 2) is up but BGP (Layer 3) will be down because the configuration does not exist yet.
Once deployed in the Megaport Portal, you need to set up the connection in the AWS console:
1. In AWS, accept the connection.\
To review and accept in the AWS console, go to **Services > AWS Direct Connect > Connections** and click the connection name to review the details and accept. For more information, see the [AWS
documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/accept-hosted-connection.html).\
The state will be pending for a few minutes while AWS deploys the connection.
2. In the AWS console, click **Create Virtual Interface** and create a virtual interface for the hosted connection. Ensure you enter these values for BGP peering:
* **Your router peer IP** -- The BGP peer IP configured on the MCR.
* **Amazon router peer IP** -- The BGP peer IP configured on the AWS endpoint.
* **BGP authentication key** -- The password used to authenticate the BGP session.
Important details to note:
* AWS provides [detailed steps](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-vif.html) for creating Public, Private, and Transit interfaces.
* The name you provided for the connection in the Megaport Portal appears in the Connection list on this page.
* The VLAN is populated and appears to be editable; however, you will get an error if you try to change it.
Once you accept the Hosted Connection in AWS and create a virtual interface with the BGP peering settings, the VXC state changes to configured in the Megaport Portal.
## Using a service key
You can create a service key that allows you to share your service with another Megaport account holder.
For more information, see [Setting up Service Keys](/marketplace/service-keys/).
# AWS Transit Gateway Inter-Region Routing with MCR
Source: https://docs.megaport.com/cloud/mcr/aws-transit-gw-routing
This help topic describes how to configure Megaport Cloud Router to provide centralized routing between AWS transit gateways in different regions using BGP.
You can configure Megaport Cloud Router (MCR) to provide centralized routing between transit gateways in different regions using BGP to advertise routes dynamically.
This topic describes a sample configuration and explains each of these steps:
* [Creating an MCR](#creating-an-mcr)
* [Creating VXCs to AWS Hosted Connect](#creating-vxcs-to-aws-hosted-connect)
* [Accepting the Hosted Connection](#accepting-the-hosted-connection)
* [Creating the Direct Connect gateways](#creating-the-direct-connect-gateways)
* [Creating a transit virtual interface between the MCR and each Direct Connect gateway](#creating-a-transit-virtual-interface-between-the-mcr-and-each-direct-connect-gateway)
* [Configuring BGP between the MCR and each Direct Connect gateway](#configuring-bgp-between-the-mcr-and-each-direct-connect-gateway)
* [Creating a transit gateway](#creating-a-transit-gateway)
* [Attaching your VPCs to the transit gateway](#attaching-your-vpcs-to-the-transit-gateway)
* [Attaching your transit gateway to the Direct Connect gateway](#attaching-your-transit-gateway-to-the-direct-connect-gateway)
* [Verifying route tables](#verifying-route-tables)
## Prerequisites
Before proceeding, ensure you have the following:
* One or more VPCs in each region.\
The VPCs cannot have overlapping CIDRs.
* AWS account number(s) associated with the transit gateways
* Five private, non-overlapping autonomous system numbers (ASNs).\
The supported range is 64512 to 65534 for 16-bit ASNs and 4200000000 to 4294967294 for 32-bit ASNs.
The examples in this topic use these values:
## Creating an MCR
For this example, you will create a 2.5 Gbps MCR in the CoreSite VA1 data center.\
For more information about this process, see [Creating an MCR](/mcr/creating-mcr).
**To create an MCR**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Service**, then select **Cloud Router (MCR)**.
The Create Cloud Router page opens. Complete the sections on this page to configure your MCR. The order summary updates as you make selections. On wider screens, the summary is displayed in a panel on the right. On narrower screens, it is displayed in a bar at the bottom of the page that you can expand.
3. In the **Details** section, specify these fields:
* **MCR Name** -- Specify a name that helps you identify the MCR. This example configuration uses mcr-va-01.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Project** (optional) -- Select a project to add the MCR to, or leave the default (No Project).
4. In the **Location** section, specify these fields:
* **Location** -- Use the **Search** field to find Ashburn, then select it. CoreSite VA1 is in the Ashburn metro area.
* **Mode** -- Select Manual so that you can choose a specific data center.
* **Diversity Zone** -- Select Auto to have Megaport select the zone for you. For more information, see [MCR Diversity](/mcr/mcr-mve-diversity).
5. In the **Provider** section, select CoreSite, then select CoreSite VA1 from the **Data Centre** drop-down list.\
Only providers and data centers available at your selected location are listed.
6. In the **Configuration** section, select the required **Rate Limit**. For this example, select 2.5 Gbps.
7. In the **BGP & ASN** section, specify these fields:
* **MCR ASN** -- Specify 65001 to override the default ASN.
* **BGP Default State** -- Leave as Enabled.
8. In the **Pricing** section, select a **Contract Term**. For this example, select 12 Months.
9. In the **Resource Tags** section, add any tags you want to apply to this MCR.
The price updates dynamically based on your selections in the order summary. Note that some partner-managed accounts do not display the pricing details.
10. Review the order summary, then click **Add MCR**.
The newly created MCR is added to your cart under Configured Services, ready for checkout.
11. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
12. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
13. Click **Order Now**.
Wait a few moments for the MCR to be deployed. When deployed, the MCR status on the **Services** page changes to Up, indicating that the MCR is ready for Virtual Cross Connects (VXCs).
## Creating VXCs to AWS Hosted Connect
With the new MCR, you want to create two VXC connections: one for each diversity zone.\
For more information about this process, see [Creating an MCR VXC](/mcr/mcr-vxc).
**To create a VXC to AWS Hosted Connect**
1. From the Services page of the Megaport Portal, select the newly created MCR.
2. Click the Amazon Web Services tile.
3. Select Hosted Connection as the AWS Connection Type.\
A list of available AWS Hosted Connect locations appear.
4. Enter **USA** in the Select Destination Port search field, click the red diversity zone icon, then select US East (N. Virginia) CoreSite VA1, Reston, USA.
5. Click **Next**.
6. Specify the details for the VXC.
* **Connection Name** - Name the connection *mcr-va-01 to dxgwy1*.
* **Rate Limit** - Choose 1 Gbps.
* **Minimum Term** - Choose 12 months.
* **Resource Tags** - Add your own reference information if required.
7. Click **Next**.
8. For now, skip the MCR Connection detail (we will come back to it later) and click **Next**.
9. Enter your account ID in the **AWS Account ID** field then click **Next**.
10. Click **Add VXC**.
Repeat these steps to create a second VXC, but instead click the blue Diversity Zone icon and select US East (N. Virginia) Coresite VA1. Name the connection *mcr-va-01 to dxgwy2*.
On the right side of the Services page, the two VXCs appear as Configured Services. Click **Review Order**, review the Megaport Global Services Agreement, then click **Order Now**.
The Megaport Portal displays the Services page, where both VXCs appear and transition from a deployable to configured state. Once the VXCs are provisioned, their icons change to green, signifying they are ready for service.
The next steps are in the AWS console to:
* Accept the Hosted Connections
* Create the Direct Connect Gateways
* Create the transit gateways
* Create the transit VIF
* Attach your VPCs to each transit gateway
## Accepting the Hosted Connection
You must accept a Hosted Connection before you can begin using it.
Follow the steps for accepting a Hosted Connection from the [AWS Direct Connect User Guide](https://docs.aws.amazon.com/directconnect/latest/UserGuide/accept-hosted-connection.html).
1. Open the [Amazon Direct Connect console](https://console.aws.amazon.com/directconnect/v2/home).
2. Go to **Services > AWS Direct Connect > Connections**.
3. Click the ID of the connection named *mcr-va-01 to dxgwy1*.
4. Click **Accept** on the top right and **Confirm** in the Accept Hosted connection confirmation window.
5. Repeat the steps to accept the second connection named *mcr-va-01 to dxgwy2*.
Each connection will transition from a pending to available state.
## Creating the Direct Connect gateways
Direct Connect gateways are global resources, which means they can be used by resources in any commercial AWS region. Each Direct Connect gateway is its own ASN. In our sample configuration, we create multiple Direct Connect gateways with unique ASNs to allow routing between transit gateways in the different regions.
We will follow the steps for [creating a Direct Connect gateway](https://docs.aws.amazon.com/directconnect/latest/UserGuide/direct-connect-gateways-intro.html#create-direct-connect-gateway).
1. Choose Direct Connect Gateways from the navigation pane on the left, and then click **Create Direct Connect Gateway**.
2. Enter the Name and Amazon side ASN: our example uses *dx-gwy1* and *65101*.
3. Click **Create**.
4. Repeat this process for a second Direct Connect gateway with *dx-gwy2* for the name and *65102* for the Amazon-side ASN.
## Creating a transit virtual interface between the MCR and each Direct Connect gateway
These steps follow those outlined [for creating a transit virtual interface to the Direct Connect gateway](https://docs.aws.amazon.com/directconnect/latest/UserGuide/direct-connect-transit-gateways.html) from the AWS Direct Connect User Guide.
1. In the AWS console, choose Connections from the navigation pane on the left, and then click the ID of the connection for *mcr-va-01 to dxgwy1*.
2. In the navigation pane, choose Virtual interfaces.
3. Click **Create virtual interface**.
4. Choose Transit as your Virtual interface type.
5. Under Transit virtual interface settings, enter *tvif-dxgwy1* for the Virtual interface name.\
The Connection and VLAN fields are pre-populated.
6. Under the Virtual interface owner, select My AWS account.
7. In the Direct Connect gateway drop-down, select *dx-gwy1*.\
The **BGP ASN** field is the ASN of the MCR, which is *65001*.
You do not need to change the other settings.
8. Scroll to the bottom and click **Create virtual interface**.
A message appears confirming that the virtual interface was created successfully.
9. Click the ID of the newly created Virtual interface to display the Peerings information. Take note of the values for the BGP authentication key, your router IP, and the Amazon router IP. You will need these to finish configuring the MCR.
Repeat these steps for the transit virtual interface between the MCR and *dx-gwy2* and name the virtual interface *tvif-dxgwy2*.
## Configuring BGP between the MCR and each Direct Connect gateway
1. In the Megaport Portal, go to the **Services** page.
2. Select the MCR you want to use.
3. Locate the VXC titled *mcr-va-01 to dxgwy1*, click the green VXC icon, and click **Next**.
4. In the **Interface IP Addresses** field, enter the value for the router IP (subnet mask included) that you previously copied from the AWS Direct Connect console.
5. Click **Add BGP Connection**.
6. Enter the following values:
* **Local IP** -- Select the value you just entered from the drop-down list.
* **Peer IP** -- Enter the Amazon router IP value (without the subnet mask).
* **Peer ASN** -- Enter the ASN of *dxgwy1*, which is *65101*.
* **BGP Password** -- Enter the BGP authentication key from the AWS console.
7. Click **Add**, click **Save**, and then click **Close**.
It can take a couple minutes for the updates to be reflected in the Portal.
Repeat these steps for the VXC to *dxgwy2* and *tvif-dxgwy2*. Use the ASN value of *65102*.
1. Locate the VXC titled *mcr-va-01 to dxgwy2*, click the green VXC icon, and click **Next**.
2. In the **Interface IP Addresses** field, enter the value for the router IP (subnet mask included) that you previously copied from the AWS Direct Connect console.
3. Click **Add BGP Connection**.
4. Enter the following values:
* **Local IP** -- Select the value you just entered from the drop-down list.
* **Peer IP** -- Enter the Amazon router IP value (without the subnet mask).
* **Peer ASN** -- Enter the ASN of *dxgwy2*, which is *65102*.
* **BGP Password** -- Enter the BGP authentication key from the AWS console.
5. Click **Add**, click **Save**, and then click **Close**.
Within 3 to 5 minutes, check the AWS Direct Connect console, and review the details of each transit virtual interface for the BGP status.
## Creating a transit gateway
These steps follow those outlined for [creating a transit gateway](https://docs.aws.amazon.com/vpc/latest/tgw/tgw-getting-started.html#step-create-tgw) from the Amazon Virtual Private Cloud Transit Gateways Guide.
1. Open the [Amazon VPC management console](https://console.aws.amazon.com/vpc/).
2. Select the region for your VPC.\
For our example, select *us-west2*.
3. Choose Transit Gateways from the navigation pane on the left.
4. Click **Create Transit Gateway**.
5. Specify the following transit gateway details:
* **Name tag** -- Give your transit gateway a friendly name. This example uses the name *tgw-us-west2*.
* **Description** -- This field is optional.
* **Amazon side ASN** -- Enter the autonomous system number for your transit gateway. Following the values defined in prerequisites, we will use *65103*.\
The rest of the settings are optional. You can modify the default settings if you want to disable DNS support, or you don’t want to use the default route table. Leave the default values as they are.
6. Click **Create Transit Gateway**.
7. Wait for the request to succeed and click **Close**.\
The initial state of the transit gateway is Pending.
Repeat these steps for the transit gateway in *us-east1*, with the name *tgw-us-east1*, and Amazon-side ASN *65104*.
## Attaching your VPCs to the transit gateway
These steps follow those outlined for [attaching your VPCs to the transit gateway](https://docs.aws.amazon.com/vpc/latest/tgw/tgw-getting-started.html#step-attach-vpcs) from the Amazon Virtual Private Cloud Transit Gateways Guide.
Before you complete these steps, wait for the state of your transit gateway to change to *available*. This might take 15 to 20 minutes to complete.
1. Make sure that the *us-west2* region is selected.
2. From the VPC console, scroll to the bottom and select Transit Gateway Attachments.
3. Choose Transit Gateway Attachments from the navigation pane on the left.
4. Select the transit gateway you created for the attachment from the Transit Gateway ID drop-down list.
5. Select VPC as the Attachment type.
6. Optionally, enter an attachment name.
7. DNS support is enabled by default; keep this setting.
8. Ensure that the **IPv6 support** check box is cleared.
9. Select the VPC to attach from the VPC ID drop-down list.
10. For Subnet IDs, select one subnet for each Availability Zone to be used by the transit gateway to route traffic.\
You can select only one subnet per Availability Zone.
11. Click **Create attachment**.
12. Wait for the request to succeed, and then click **Close**.
13. Repeat these steps for the VPC in *us-east1*.
## Attaching your transit gateway to the Direct Connect gateway
These steps follow those outlined for [Transit Gateway Associations](https://docs.aws.amazon.com/directconnect/latest/UserGuide/direct-connect-transit-gateways.html) from the AWS Direct Connect User Guide.
1. Open the [Amazon VPC management console](https://console.aws.amazon.com/vpc/).
2. Select Direct Connect gateways from the navigation pane on the left.
3. Select the ID for the *dx-gwy1* Direct Connect gateway.
4. Choose Gateway associations.
5. Select the transit gateway you created (*tgw-us-west2*) from the Gateways drop-down list.
6. Enter the CIDR prefix of your VPCs in Allowed prefixes.\
This tells the TGW what prefixes to advertise to the Direct Connect gateway. Up to 20 prefixes are permitted per transit gateway.
7. Click **Associate gateway**.
8. Repeat these steps for *dx-gwy2* and *tgw-us-east1*.
When complete, the state of the transit gateway association changes from *associating* to *available*.
## Verifying route tables
As the final step, verify the routing tables on each transit gateway.
These steps follow those outlined for [View Transit Gateway Route Tables](https://docs.aws.amazon.com/vpc/latest/tgw/tgw-route-tables.html#view-tgw-route-tables) from the Amazon Virtual Private Cloud Transit Gateways Guide.
1. Open the [Amazon VPC management console](https://console.aws.amazon.com/vpc/).
2. Select the region for your VPC (our example uses *us-west2*).
3. Choose Transit Gateway Route Tables from the navigation pane on the left.
4. Select the **Routes** tab to see the route for the corresponding transit gateway learned from Direct Connect Gateway.
5. Repeat these steps for the transit gateway in *us-east1*.
## Using a service key
You can create a service key that allows you to share your service with another Megaport account holder.
For more information, see [Setting up Service Keys](/marketplace/service-keys/).
# Creating MCR Connections to Azure using ExpressRoute
Source: https://docs.megaport.com/cloud/mcr/azure
This help topic describes how to create a VXC from an MCR to Microsoft Azure ExpressRoute.
You can create a VXC from an MCR to Microsoft Azure ExpressRoute through the Megaport Portal.
You can create the VXC to Azure from the MCR and establish either private or Microsoft peering.
To connect to ExpressRoute using MCR, you need an ExpressRoute service key obtained from the Azure Resource Manager (ARM) portal. Follow the steps in the Microsoft topic
[Tutorial: Create and modify an ExpressRoute circuit](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-circuit-portal-resource-manager) to get this key.
To check the latency and price of connecting to a particular Azure Partner location, start the procedure to [add a connection to Microsoft Azure](#azure-vxc) but instead of providing a **Microsoft Azure Service Key**, click **View all Azure Partner locations**. You can proceed to the Connection Details page without a service key and review the pricing of the selected port. To place an order for a Microsoft Azure connection, you need to provide a service key.
**To create a VXC from an MCR to Azure**
1. In the Megaport Portal, go to the **Services** page and select the MCR you want to use.
2. Add a VXC connection for the MCR.\
If this is the first connection for the MCR, click the Microsoft
Azure tile. The tile is a shortcut to the configuration page.
Alternatively, click **+Connection**, click **Cloud**, then click **Microsoft Azure**.
3. Add the ExpressRoute service key into the **Microsoft Azure Service Key** field.\
The Portal verifies the key then displays the available port locations based on the ExpressRoute region.
4. Select the connection point for your first connection.
5. Select one or both of the peering types: **Private** and **Microsoft**.
6. Click **Next**.
7. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit for the VXC will be capped at the maximum allowable based on the ExpressRoute service key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
8. Continue with the default settings and click **Next** through the next screens.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
The Megaport system takes about five minutes to deploy and configure the required peering types.
## Viewing the configuration
Once the VXC connection deploys successfully, it is attached to the MCR on the Megaport Portal Services page:
1. Click the VXC to display the details of this connection.
2. Select the **Configure A End** tab of the VXC detail to view this information:
* **VLANs** -- 100 and 200 by default. 100 for Private peering and 200 for Microsoft.
* **Local ASN** -- 133937. This is the default Megaport autonomous system number (ASN).
* **Peer ASN** -- For Microsoft Azure via ExpressRoute, 12076 for all peering types.
* **Local IP and Peer IP** -- Reflects the APIPA range for BGP peering (auto-configured) on Private peering. Microsoft peering displays a Megaport-assigned public IP range (within 117.18.80.0/21).
* **BGP Password** -- Blank by default; this field is not mandatory for ExpressRoute connection because they traverse a private (non internet) path. However, if you enter a BGP password, you also need to update it manually on the ExpressRoute configuration page to match. The passwords do not synchronize automatically for security reasons.
## Confirming ExpressRoute configuration details
The corresponding ExpressRoute details screen in the Azure portal shows
that the Layer 2 connection is up (Provider Status = Provisioned) and Layer 3
for the Private (or Microsoft) peering is similarly configured:
* Click the Azure private peering type to display the Private peering configuration.
Values for both primary and secondary subnets are provided, regardless of whether only one of these peering locations is established. If you add a second ExpressRoute VXC using this service key, it will inherit the same peering types and automatically configure for the next available IP address allocation within that peering type.
## Creating and linking a Virtual Network Gateway
In addition to the ExpressRoute circuit, you need to create a Virtual Network Gateway (VNG) and associate it with both VNets used for private peering, as well as linking the VNG to your ExpressRoute circuit to provide routing on the Azure side toward the MCR.
The creation of the VNG can take approximately 45 minutes,
although this is a one-time requirement.
For more information, follow the steps in
Configure a virtual network gateway for ExpressRoute using the Azure
portal to create the VNG. Note that Microsoft charges apply per the ExpressRoute Gateways section of the
[Azure VPN gateway pricing page](https://azure.microsoft.com/en-gb/pricing/details/vpn-gateway/).
After you create the VNG, you need to associate the ExpressRoute VNG to the ExpressRoute circuit by following
Connect a virtual network to an
ExpressRoute circuit using the portal guidance.
## Using a service key
You can create a service key that allows you to share your service with another Megaport account holder.
For more information, see [Setting up Service Keys](/marketplace/service-keys/).
## Troubleshooting
### How do I confirm the BGP configuration?
To confirm a successful BGP/Layer 3 configuration, return to Azure private peering, click the detail line and then click **Get ARP Records**.
This function takes about a minute to populate
data. For a successful connection you see a display similar
to this image, indicating that the MAC addresses have resolved on both the On-Prem
and Microsoft sides of the connection:
After switching from primary to secondary, this display currently only shows a
value for the Microsoft side of the connection, because the VXC to the
secondary target has not been configured.
To configure the secondary VXC, create
another VXC from your MCR with the same ExpressRoute service key;
however, this time target the secondary router presentation.
Once Layer 3 BGP is active and confirmed, you can view
the Route Table as seen by the Microsoft edge devices by clicking
**Get route table** in the Private peering pane. It displays the next
hop, weighting, and AS path for the network values. You can toggle the display
to view the secondary path route table when both primary and secondary VXCs are active.
### My public prefix configuration is the “verifying” state. What can I do?
When you create a public circuit and you specify public peer IP addresses, you need approval from the Microsoft Azure team (private circuits do not require this authorization and are available within minutes). Before approving public peer IP prefixes or public ASNs, the Azure team needs to verify the ownership by confirming that the advertised public prefixes and peer ASN are assigned to the organization listed in your Azure account. If you are getting the public prefixes from another entity, and the assignment is not recorded with the Internet Routing Registry, the validation will not complete.
**Resolution**
If the public virtual interface state is in the *verifying* or *validation needed* state for more than 72 hours, check the email address registered to your Azure account. You might have received an email from the Azure team if the owner of the BGP ASN or one of your advertised routes does not match your account details.
If the BGP ASN or an advertised route does not match your account, collect the documents that show the public prefixes are assigned to your organization by the entity that is listed as the prefix owner in the routing registry. Submit these documents for manual validation by opening a support ticket for the Azure team.
## Helpful references
* [Diversity in Azure Connections](/cloud/megaport/microsoft/azure-diversity)
* [Azure Paired Regions - HA Design](/cloud/megaport/microsoft/azure-ha-design)
# Diversity in AWS Connections
Source: https://docs.megaport.com/cloud/megaport/aws/aws-diversity
This help topic describes how to identify and create diverse connections in AWS.
Diverse connections improve the resiliency of your network by using different physical infrastructure to provide network services. Diverse connections build in redundancy and eliminate single points of failure.
AWS Hosted Connections simplify the deployment of diverse connections by establishing diversity zones. A diversity zone is a group of devices at a single Megaport location. Ports and VXCs in different diversity zones are physically separated on Megaport devices and connected to different AWS devices. During Megaport scheduled maintenance, no more than one diversity zone will experience downtime at any moment. Whenever possible, diverse services have maintenance periods scheduled for different days.
Megaport creates AWS diversity zones by dividing the customer edge routers into two groups. Each AWS destination port indicates its diversity zone with either a red or blue icon.
To create diverse connections, you need to create two connections: one connection for each diversity zone. For end-to-end diversity, the connections must be on diverse ports at both ends.
AWS Hosted Virtual Interfaces (Hosted VIF) do not support diversity zones. To ensure connection diversity for Hosted VIFs, create VXCs to two destination ports in different data centers, instead of two ports in separate diversity zones.
The preferred diversity method deploys connections in different Megaport locations regardless of the diversity zone. This offers the most redundancy and protection. For recommendations from AWS, see [AWS Direct Connect Resiliency Recommendations](https://aws.amazon.com/directconnect/resiliency-recommendation/).
## Configuration Examples
The following scenarios show a range of configurations with different levels of resilience:
* [No Diversity](#no-diversity)
* [Low Resiliency: VXC Diversity](#low-resiliency-vxc-diversity)
* [Single-Site Redundant: Port and VXC Diversity](#single-site-redundant-port-and-vxc-diversity)
* [High Resiliency: Location, Port, and VXC Diversity](#high-resiliency-location-port-and-vxc-diversity)
* [Maximum Resiliency: Location, Port, and VXC Diversity](#maximum-resiliency-location-port-and-vxc-diversity)
### No Diversity
We do not recommend this setup for production applications.
This configuration provides a basic connection to AWS. This configuration requires a single physical cross-connect to a Megaport Port, which connects to an AWS Direct Connect router through a single VXC.
This setup does not provide any redundancy. When Megaport, the data center, or AWS performs maintenance on their component, the connection will be unavailable.
### Low Resiliency: VXC Diversity
We recommend this setup for applications that require some resilience, but do not require continuous uptime.
This configuration provides a connection to AWS with VXC diversity. This configuration requires a single physical cross-connect to a Megaport Port. The connection uses two separate VXCs, one in each diversity zone, to connect to two AWS Direct Connect routers.
This setup provides redundancy for the VXCs and the AWS Direct Connect routers. The Port remains a single point of failure. When Megaport or the data center performs maintenance that affects the Port, the connection will be unavailable.
### Single-Site Redundant: Port and VXC Diversity
We recommend this setup when you require a high level of connection uptime and resilience from a single data center.
This configuration provides a diverse connection to AWS from a single data center. This configuration uses two separate Megaport Ports, one in each diversity zone, each with a corresponding VXC that connects to two different AWS Direct Connect routers.
This setup provides redundancy for the virtual connections (VXCs), the AWS Direct Connect routers, and the Megaport Ports. If Megaport, the data center, or AWS performs maintenance on any single connection component, the traffic automatically fails over to the other path, and you remain connected.
For the single-site redundant deployment recommendation from AWS, see: [Single-Site Redundant Deployment for Non-Critical Workloads](https://aws.amazon.com/directconnect/resiliency-recommendation/#single-site-redundant-deployment-for-non-critical-workloads).
### High Resiliency: Location, Port, and VXC Diversity
We recommend this setup when you require high availability and location diversity for your AWS connection.
This configuration provides a resilient connection to AWS across two different data centers. This configuration uses a Megaport Port in each data center, each in a separate diversity zone. Each Megaport Port has a single VXC that connects to a different AWS Direct Connect router.
This setup provides redundancy for the VXCs, the AWS Direct Connect routers, and the Megaport Ports. It also provides location diversity by having the Ports in separate data centers. If Megaport, a data center, or AWS performs maintenance on a single connection component, the traffic automatically fails over to the other path, and you remain connected.
For the multi-site, non-redundant deployment recommendation from AWS, see: [High Resiliency: Multi-Site Non-Redundant Deployment for Critical Production Workloads](https://aws.amazon.com/directconnect/resiliency-recommendation/#high-resiliency-multi-site-non-redundant-deployment-for-critical-production-workloads).
### Maximum Resiliency: Location, Port, and VXC Diversity
We recommend this setup when you require a high level of connection uptime, resilience, and location diversity for your mission-critical applications.
This configuration provides a highly available and fully diverse connection to AWS, utilizing redundancy across two different data centers. This configuration uses two Megaport Ports in each data center, with connections established in both diversity zones. All four Megaport Ports have a VXC connecting to the AWS Direct Connect service, providing multiple failover paths.
This setup VXC, AWS Direct Connect, Megaport Port, and location diversity. If Megaport, a data center, or AWS performs maintenance on any single connection component, traffic automatically fails over to one of the remaining paths, and the connection will remain available.
For the multi-site, redundant deployment recommendation from AWS, see: [Maximum Resiliency: Multi-Site Redundant Deployment for Critical Production Workloads](https://aws.amazon.com/directconnect/resiliency-recommendation/#maximum-resiliency-multi-site-redundant-deployment-for-critical-production-workloads).
# AWS Encryption Options for High Throughput and High Resilience
Source: https://docs.megaport.com/cloud/megaport/aws/aws-encryption
This help topic describes high throughput and high resilience encryption options into AWS.
This topic describes two scenarios for creating encrypted network connections to AWS with high throughput and high resilience.
* [Scenario 1: Encrypted connection to transit Virtual Private Cloud (VPC)](#scenario1)
* [Scenario 2: Encrypted connection to transit gateway (TGW)](#scenario2)
## Prerequisites
* Two Megaport-enabled locations with established diversity zones.
* An AWS Direct Connect Hosted Connection (used as an example in this topic), or a Hosted Virtual Interface (Hosted VIF) connection.
* Sufficient size of the Elastic Compute Cloud (EC2) instance running the Network Virtual Appliance (NVA) within AWS to handle high-throughput encryption.
## Key considerations
* Maximum throughput is primarily determined by how much compute is available on the devices that handle the encryptions (such as Network Virtual Appliances, firewalls, or routers).
* Overall uptime targets determine the number of devices, underlying connections, and overlay tunnels (for example 99.9% or 99.99%, a separate metric from the SLA number).
* The routing protocol and configuration determines the failover time, and how quickly a device detects a fault. In some cases, a graceful shutdown might not be possible.
## Scenario 1: Encrypted connection to transit Virtual Private Cloud (VPC)
### Physical Layer - Megaport and Megaport-enabled locations + AWS edge locations
In each diversity zone, you can have a single Port or a pair of Ports in a Link Aggregation Group (LAG). Each Megaport-enabled location is protected by dual diverse fiber paths into Megaport’s global core network.
### Layer 2 - Virtual Cross Connect (VXC)
Using the protected physical layer, create a VXC (Layer 2 circuit) to connect to each on-ramp where Megaport meets the AWS edge network. Each Hosted Connection location has diverse physical infrastructure available. This image shows four VXCs connecting four devices on Megaport to AWS at AWS edge locations. Use a private virtual interface over AWS Direct Connect, so it is attached to the target Virtual Private Gateway (VGW) or a Direct Connect Gateway onto VGW.
### Layer 3 - IP and BGP Sessions
Assign IP addresses and establish a BGP session over each of the previously created VXCs. If one of the sessions is interrupted, active BGP sessions are available for failover.
### Network Virtual Appliances within transit VPC and on-premises firewalls
The uptime requirement determines the number of on-premises devices and Network Virtual Appliances (NVAs) in AWS; it can be a cluster/stack of two or more devices in each data center.
### Encrypted tunnels
You can establish encrypted tunnels using industry standard protocols or vendor proprietary protocols. The maximum throughput depends on the available computing power on the NVAs and the on-premises firewall. Each encrypted tunnel is protected by the network infrastructure setup.
For faster, automated failover, we recommend that you set up dynamic routing protocols over the encrypted tunnels that are separate from the underlying network.
## Scenario 2: Encrypted connection to a TGW
### Physical Layer - Megaport and Megaport-enabled locations + AWS edge locations
In each diversity zone, you can have a single Port or a pair of Ports in a LAG. Each Megaport-enabled location is protected by dual diverse fiber paths into Megaport’s global core network.
### Layer 2 - VXC
Using the protected physical layer, create a VXC to connect to each on-ramp where Megaport meets the AWS edge network. Each Hosted Connection location has diverse physical infrastructure available. This image shows four VXCs connecting four different devices on Megaport to AWS at AWS edge locations. Make sure to use a public virtual interface over AWS Direct Connect to receive all public AWS global prefixes.
### Layer 3 - IP and BGP sessions
Assign a public IP address that you own to each VXC you created, and establish a BGP session. If any interruptions occur, there are four active BGP sessions available for easy failover.
If you do not own any public IP addresses, see [Creating MCR Connections to AWS](/cloud/mcr/aws).
### Using on-premises devices to establish IPsec VPN connections to TGW
The number of on-premises devices depends on your uptime requirement. You can have a cluster or stack of two or more devices in each data center.
### Establishing IPsec VPN tunnels to transit gateway
Each VPN connection created in AWS has two available tunnels for high availability (HA) with a maximum throughput of 1.25 Gbps. You can use ECMP (Equal-Cost Multi-Path) routing to create multiple VPN connections to aggregate throughput up to 50 Gbps.
# AWS Frequently Asked Questions (FAQs)
Source: https://docs.megaport.com/cloud/megaport/aws/aws-faq
This help topic answers common questions about AWS and Megaport.
Click any of the FAQs in the right navigation for suggestions and resolution.
## How can I configure VPN as a backup for my Direct Connect connection?
I want to configure a backup VPN connection for failover with my AWS Direct Connect connection. Any recommendations and best practices?
### Resolution
To configure the hardware VPN as a backup for your Direct Connect connection:
* Be sure that you use the same virtual private gateway for both Direct Connect and the VPN connection to the VPC.
* If you are configuring a Border Gateway Protocol (BGP) VPN, advertise the same prefix for Direct Connect and the VPN.
* If you are configuring a static VPN, add the same static prefixes to the VPN connection that you are announcing with the Direct Connect virtual interface.
* If you are advertising the same routes toward the AWS VPC, the Direct Connect path is always be preferred, regardless of AS path prepending.
Be sure that Direct Connect is the preferred route from your end, and not over VPN when the Direct Connect virtual interface is up to avoid asymmetric routing; this might cause traffic to be dropped. We always prefer a Direct Connect connection over VPN routes. For information on route priority and routing options, see the AWS topic [Route Priority](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Route_Tables.html#route-tables-priority).
If you want a short-term or lower-cost solution, consider configuring a hardware VPN as a failover option for a Direct Connect connection. VPN connections are not designed to provide the same level of bandwidth available to most Direct Connect connections. Ensure that your use case or application can tolerate a lower bandwidth if you are configuring a VPN as a backup to a Direct Connect connection.
## How do I enable BFD for use with Direct Connect?
We recommend enabling BFD when configuring multiple AWS Direct Connect connections or when configuring a single AWS Direct Connect connection and a VPN connection as a back up to ensure fast detection and failover. BFD detects link or path failures and updates dynamic routing as Direct Connect quickly terminates BGP peering so that backup routes can kick in. This ensures that the Bidirectional Forwarding Detection (BGP) neighbor relationship is quickly torn down instead of waiting for 3 keep-alives to fail at a hold-down time of 90 seconds.
### Resolution
The BFD interval specifies how often we send BFD packets, the min\_rx is how often a router expects to receive the packets, and the multiplier is how many we can miss before the BGP neighbor relationship is considered down.
Asynchronous BFD is automatically enabled for each Direct Connect virtual interface on the AWS side, but it does not take effect until it’s configured on your router. The Direct Connect default sets the BFD liveness detection minimum interval to 300 milliseconds and the BFD liveness detection multiplier to 3.
Before using BFD echo mode with your network device, you must disable the sending of Internet Control Message Protocol (ICMP) and redirect messages with the **no ip redirect** command to avoid high CPU utilization.
## How do I set an Active/Passive Direct Connect connection?
When using AWS Direct Connect to transport production workloads to and from AWS, it is recommended to use dual Direct Connect Virtual Circuits, either from a single Port, a pair of physical Port connections (either discrete or LAG/LACP) in a single DC, or spread across multiple DC locations.
You can configure the following:
* Two routers to terminate the primary and secondary DX connections to avoid a single point of device failure.
* A private virtual interface on each of the DX routers that terminate to the same VPC.
HA routing protocols (such HSRP, VRRF, GLBP, etc.) on two routers to allow Local servers to use multiple routers that act as a single virtual router, maintaining connectivity even if the primary router fails, because the secondary router will take over and become active, or run an internal routing protocol such as iBGP which will learn routes from Direct Connect EBGP and distribute prefixes to internal iBGP gateways.
* Active/Passive (failover). One connection is handling traffic, and the other is on standby. If the active connection becomes unavailable, all traffic is routed through the passive connection. You will need to AS path prepend the routes on one of your links for it to be the passive link.
For more information, see [Configure Redundant Connections with AWS Direct Connect](https://docs.aws.amazon.com/directconnect/latest/UserGuide/getting_started.html#RedundantConnections).
The local preference attribute identifies a preferred exit point from the local autonomous system (AS). If there are multiple exit points from the AS, the local preference attribute selects the exit point for a specific route.
### Influencing AWS outbound traffic using AS Path prepending
The BGP Best Path Algorithm decides how the best path to an autonomous system is selected. A common value to determine the best path is the AS Path length. When two or more routes exist to reach a prefix, the default in BGP is to prefer the route with the shortest AS path.
The secondary router will advertise a longer AS path, so traffic from VPC to your network will always be through the primary router.
## My public virtual interface is stuck in the “verifying” state. What can I do?
When you create a public virtual interface and you specify the public peer IP addresses, it requires approval from the AWS Direct Connect team (private VIFs/VXCs do not require this authorization and are available within minutes). Before approving public IP prefixes or public ASNs, the AWS Direct Connect team needs to verify the ownership of the public IP prefixes and BGP ASN. The AWS Direct Connect team verifies ownership by confirming that the regional registry belongs to the organization name listed in your AWS account.
### Resolution
If the public virtual interface state is in the verifying state for more than 72 hours, check the email address registered to your AWS account. You might have received an email from the AWS Direct Connect team if the owner of the BGP ASN or one of your advertised routes does not match your account details.
If the BGP ASN or an advertised route does not match your account, you can:
* Ask the IP address owner to email [directconnect-requests@amazon.com](mailto:directconnect-requests@amazon.com) stating that they authorize to have the public IP prefixes approved for the public virtual interface dxvif-xxx.
\--*or*--
* Ask the IP address owner to submit a letter of authorization written on a company letterhead or ask them to send a email authorizing the use of the public IP prefix for the public virtual interface dxvif-xxx with your AWS account. Then sign in to the account that owns the Direct Connect public virtual interface, open a case, and attach the letter of authorization to your case.
## Virtual interface BGP status is down in the AWS console. What should I do?
Your virtual interface status might be down because of configuration issues with the Layer 2 or .
### OSI Layer 2 configuration
First, verify that your OSI layer 2 is configured correctly.
Verify the following details:
* You have configured the correct VLAN ID with dot1Q encapsulation on your device (such as a router or switch). The VLAN ID appears in the Portal Information tab as the A-End service for your VXC.
* The peer IP address configuration is identical on your device, through the Portal, and in the AWS Direct Connect console.
* Any intermediate devices are configured for VLAN tagging with appropriate VLAN ID, and VLAN-tagged traffic is preserved in the AWS Direct Connect endpoint.
* Your device is learning the media access control (MAC) address of the AWS Direct Connect endpoint for the configured VLAN ID from the Address Resolution Protocol (ARP) table.
* Your device can ping the Amazon peer IP sourcing from your peer IP.
### BGP Configuration
If the OSI layer 2 test results are positive, then confirm the BGP configuration on your device. Verify the following:
* The local ASN and remote ASN as provided in the Portal Information tab as A-End service for your VXC.
* The neighbor IP address and BGP MD5 password as provided in the Portal Information tab as A-End service for your VXC.
* Your device is not blocking ingress or egress from TCP port 179 (BGP) and other appropriate ephemeral ports.
* Your device is not advertising more than 100 prefixes to AWS by BGP. By default, AWS only accepts up to 100 prefixes using a BGP session on AWS Direct Connect.
After confirming these configurations, your virtual interface BGP status should be up.
# Configuring Public AWS Connections with IP Addresses Provided by AWS
Source: https://docs.megaport.com/cloud/megaport/aws/aws-public-ip
This help topic describes how to configured public AWS connections with IP addresses provided by Amazon.
To create a public virtual interface for AWS, you need to specify the public peer IP addresses.
If you do not have public IP addresses, you can request them from AWS, however allocation is not guaranteed. AWS Direct Connect team will review your request and aims to respond within 72 hours, but this SLA applies only to the review and approval process, not to the assignment of IP addresses. As a general rule, we recommend using your own public IP addresses rather than relying on AWS to provide them.
Private VIFs/VXCs do not require AWS authorization and are available within minutes.
For a public address, the AWS Direct Connect team needs to verify the ownership of the public IP prefixes and BGP ASN before approving public IP prefixes or public ASNs. The AWS Direct Connect team verifies ownership by confirming that the regional registry belongs to the organization name listed in your AWS account.
AWS approval is outside of Megaport control and our service offering. Megaport can facilitate the implementation, but Megaport cannot guarantee timelines or support from AWS.
**To configure a public AWS connection with AWS IP addresses**
1. In the Megaport Portal, create a public AWS connection (Hosted VIF or Hosted Connection) and use a placeholder IP address in the **Amazon IP Address** field.
This VXC allows AWS to identify the AWS Direct Connect circuit for the connection.
2. Request a public IP /31 from AWS to establish peering.
In the AWS portal, open a ticket and request a /31 address for the VXC (Support > Support Center > Create Case).
Specify these details:
* megaport @ facility xxx on-ramp and connection type (Hosted VIF or Hosted Connection).
* the region and the data center for the IPs.
* Don’t share any Megaport details for this request, such as account numbers or port identifiers.
For example:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
megaport @ facility ap-southeast-2 on-ramp (Hosted VIF)
Region: Asia Pacific (Sydney) (ap-southeast-2) Sydney, Australia
DC where we will connect: Global Switch
We will require IP addresses assigned from AWS for this (IPv4 /31).
```
3. When AWS issues the /31 IP address, delete the VIF associated with the VXC (that contains the placeholder values) and create a new VIF using the /31 IP address from AWS.
For Hosted VIFs, go to the Megaport Portal and update the IP address in the **Amazon IP Address** field for the VXC. Megaport automatically deletes the old VIF and creates a new one with the updated address.
For Hosted Connections, go to the AWS portal and delete the VIF with the placeholder values and create a new VIF with the new IP address. You don’t need to modify the VXC in the Megaport Portal.
## Helpful references
* [Configuring and Maintaining AWS Hosted VIFs](/cloud/megaport/aws/hosted-vif)
* [My public virtual interface is stuck in the “verifying” state. What can I do?](/cloud/megaport/aws/aws-faq#verifying)
* [Hosted virtual interfaces in the AWS documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.html)
# Configuring a Direct Connect Dedicated Connection
Source: https://docs.megaport.com/cloud/megaport/aws/dedicated-connection
This help topic describes how to configure a Direct Connect Dedicated Connection between Megaport and AWS.
A Direct Connect dedicated connection can support up to 50 public or private virtual interfaces and up to four transit virtual interfaces. The total number of VIFs cannot exceed 51 per dedicated connection. The configuration requires a physical cross connect between a Port and a Direct Connect port and a Virtual Cross Connect (VXC) between the Port connected to the Direct Connect port and a second Port.
**To create a Direct Connect dedicated connection**
1. Provision a Direct Connect port in the AWS Console and designate Megaport as the vendor.
2. Download an LOA from AWS.
3. Provision a Port in the same data center as the Direct Connect port.
4. Contact your Megaport Account Manager to set up a physical cross connect from the Direct Connect port to the Port.
5. Configure a private VXC to connect the Port attached to the Direct Connect port to a second Port in a different data center.
This connection is not set up exclusively through the Megaport Portal, but instead requires direct coordination with your Megaport Account Manager.
# Configuring and Maintaining AWS Hosted Connections
Source: https://docs.megaport.com/cloud/megaport/aws/hosted-connection
This help topic describes how to configure and maintain AWS Hosted Connections with Megaport.
A Hosted Connection is an AWS Direct Connect service that provisions connectivity on demand over pre-provisioned network circuits. A Hosted Connection can support one private, public, or transit VIF.
Each Hosted Connection supports a single VIF and you can obtain multiple VIFs by configuring multiple hosted connections.
## Diverse connections
Hosted Connections support diverse connections. Diverse connections improve the robustness of your network by using different physical infrastructure to build in redundancy and eliminate single points of failure. You can achieve diversity by connecting to AWS ports in different diversity zones. Each destination port has either a red or blue icon to indicate the diversity zone.
To create diverse connections, you need to create two connections: one connection for each diversity zone.
## Before you begin
To deploy an AWS Hosted Connection, you need your [AWS Account number](https://docs.aws.amazon.com/general/latest/gr/acct-identifiers.html#FindingYourAccountIdentifiers)
and the details of the VPC environment. Ensure that you have already configured the Direct Connect gateway, AWS gateway, VPCs, and related attachments and associations. The AWS documentation provides detailed steps for VPC configuration as well as how to create and deploy each type of gateway.
## Creating a Hosted Connection
Unlike configuring a Hosted VIF, where the virtual interface and associated Layer 3 details are automatically provisioned, when you configure a Hosted Connection you must provision the virtual interface.
**To create a Hosted Connection**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.\
If you haven’t already created a Port, see [Creating a Port](/connections/creating-port).
2. Add an AWS connection for the Port.\
If this is the first connection for the Port, click the AWS tile.
The tile is a shortcut to the configuration page. Alternatively, click **+Connection**, click **Cloud**, then click **AWS**.
3. For AWS Connection Type, click **Hosted Connection**.
4. In the **Select Destination Port** list, select the AWS region and the interconnection point for your connection, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection. You can also filter by diversity zone.\
Each destination port has either a blue or red icon to indicate its diversity zone. To achieve diversity, you need to create two connections with each one in a different zone.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection. The speed cannot be changed once deployed. The drop-down list shows predefined rate limits available for your Port. Higher speeds might be available depending on location and Port capabilities.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged** to remove the VLAN tagging for this connection. The untagged option limits you to only one VXC deployed on this Port. (The VLAN for the AWS side termination will be automatically allocated and will not affect your Port details.) You must use untagged VLANs if you are creating a MACsec connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.
7. Specify the cloud details.
* **AWS Connection Name** -- This is a text field and will be the name of your virtual interface that appears in the AWS console. For easy mapping, the field defaults to the same name you specified
for the VXC name on the previous screen.
* **AWS Account ID** -- This is the ID of the account you want to connect. You can find this value in the management section of your AWS console.
8. Click **Next**.\
A summary page appears that includes the monthly cost.
9. Click **Back** to make changes or click **Add VXC** to move this
configuration to your cart.\
Once you have finished this
configuration, you can configure additional VXCs or proceed through
the checkout process.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
Megaport will deploy the connection. The deployment can take several minutes.
After creating a Hosted Connection, you need to accept it in the AWS console to activate it.
**To accept a Hosted Connection**
1. In AWS, go to Services > AWS Direct Connect > Connections and
click the connection name.
2. Click **Accept** at the top right of the window.
The state will be pending for a few minutes while AWS deploys the
connection. After it is deployed, the state changes from "ordering" to
"available."
The connection is now available, however you need to create a VIF to connect to AWS services.
For more information about accepting AWS connections, see the
[AWS documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/accept-hosted-connection.html).
## Creating a virtual interface
Once you have created and accepted a Hosted Connection, create a VIF and attach the Hosted Connection to a gateway.
AWS provides
[detailed instructions](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-vif.html) for creating Public, Private, and Transit interfaces.
**To create and attach a VIF**
1. In the AWS console, click **Create Virtual Interface**.
2. Select the interface type.
The type will vary depending on the type of service you need to access.
* **Private** -- Access resources running into a VPC using their private IP addresses. You can choose to terminate a private virtual interface on a private virtual gateway (to access a single VPC) or to a Direct Connect gateway (this will give you a 1 VIF to 10 VPCs mapping).
* **Public** -- Access all AWS public endpoints, as well as all AWS resources that are reachable by a public IP address.
* **Transit** -- Transport traffic from a Direct Connect gateway to one or more transit gateways.
3. Specify the configuration details:
* **Virtual interface name** -- Enter a name for the virtual interface.
* **Connection** -- The physical connection where you want this virtual interface to be provisioned. The name you provided for the Hosted Connection in the Megaport Portal appears here.
* **Virtual interface owner** -- The account that will own the virtual interface. Select My AWS account.
* **Direct Connect gateway** -- Select the Direct Connect gateway to attach this virtual interface to. A transit VIF is not directly attached to a Transit gateway, but to a Direct Connect gateway.
* **VLAN** -- The VLAN assigned to the virtual interface. Leave this value as is. The VLAN address is populated and appears to be editable; however, you will get an error if you try to change it. VLANs cannot be extended from on-premises to AWS, and are used only for traffic separation between different virtual interfaces.
* **BGP ASN** -- Enter the Border Gateway Protocol (BGP) autonomous system number (ASN) for the on-premises side of the BGP session.
The following BGP details can be filled out or left blank. When left blank, they are auto-populated by AWS.
If you are using this connection with an MCR, you need to
populate the router peer IP addresses and BGP authentication
key. (The fields are optional, so you can leave them blank for
the initial creation and add the values later.) You also need
to ensure you enter the same values for the MCR VXC in the
Portal in the standard MCR A-End user interface. Without these
values, you cannot establish BGP peering. For detailed
information, see [Creating MCR Connections to AWS](/cloud/mcr/aws).
You can also choose whether you want the virtual interface to support Jumbo frames. Enable Jumbo MTU to support an Ethernet packet of 8500 bytes.
4. Click **Create virtual interface**.
To view the VIF details and state, navigate to Services > AWS Direct Connect > Connections > Name of the Megaport-Created-Hosted Connection.
If BGP hasn’t been configured, the interface state will be shown as “down.”
The last step is to configure BGP on the on-premises network device. The [AWS documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-vif.html#vif-router-config) provides details on how to download the router configuration as a unique feature of Hosted Connections. If you have a Megaport Cloud Router (MCR) instead of an on-premises device, see [Creating MCR Connections to AWS](/cloud/mcr/aws).
If you download the router configuration files, verify that the AWS and Megaport VXC VLAN numbers match. While in most cases Megaport uses the same VLAN number as AWS, the VLAN might be different in the Port configuration that is connected to your on-premises device given the automation of the platform.
Once you accept the connection and create the VIF in AWS, the VXC state changes to “configured” in the Megaport Portal.
**To edit a Hosted Connection**
* Click the gear icon next to the connection in the Megaport Portal to make changes.
You cannot change the rate limit or the AWS connection name or
account ID for Hosted Connections.
You can modify the details on the Megaport side including the
connection name, VLAN ID, and Service Level Reference.\
If this is a termed connection, you cannot reduce the term.\
Once submitted, those changes take effect in a few minutes.
**To delete a Hosted Connection**
1. In AWS, open the AWS Direct Connect console.
2. Delete the virtual interface and then delete the connection.\
You can only delete a connection if there are no virtual interfaces attached to it.
3. In the Megaport Portal, click the trash icon next to the VXC and confirm the deletion when prompted.
For more information, see [Terminating a VXC](/connections/terminating-vxc).
Until you delete the virtual interface and connection in the AWS console, you cannot delete the VXC in the Megaport Portal.
# Configuring and Maintaining AWS Hosted VIFs
Source: https://docs.megaport.com/cloud/megaport/aws/hosted-vif
This help topic describes how to configure and maintain AWS Hosted VIF connections with Megaport.
To deploy an AWS Hosted VIF, you need your
[AWS Account number](https://docs.aws.amazon.com/general/latest/gr/acct-identifiers.html#FindingYourAccountIdentifiers) and the details of the VPC environment.
You can deploy multiple VXCs to the same VPC (for redundancy); however, you cannot deploy a single VXC to multiple VPCs. You need a separate VXC to connect to each AWS VPC.
AWS Hosted Virtual Interfaces (Hosted VIF) do not support diversity zones. To ensure connection diversity for Hosted VIFs, create VXCs to two destination ports in different data centers, instead of two ports in separate diversity zones.
**To create a Hosted VIF connection**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.\
If you haven’t already created a Port, see [Creating a Port](/connections/creating-port).
2. Add an AWS connection for the Port.\
If this is the first connection for the Port, click the AWS tile. The tile is a shortcut to the configuration page. Alternatively, click **+Connection**, click **Cloud**, then click **AWS**.
3. Select AWS as the service provider, select Hosted VIF as the AWS Connection Type, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
Match this to the VXC name on the next screen for easy mapping.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Accepted values start at 1 Mbps and scale in 1 Mbps increments. Maximum available speed depends on location and service availability. Note the sum of all hosted virtual VXCs to a service can exceed the Port capacity (for example, 10 Gbps, 100 Gbps, or higher) but the total aggregate will never burst beyond the Port capacity.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection. 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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged** to remove the VLAN tagging for this connection. The untagged option limits you to only one VXC deployed on this Port. The VLAN for the AWS side termination will be automatically allocated and will not affect your Megaport details. You must use untagged VLANs if you are creating a MACsec connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Specify the cloud details.
* Select **Public** or **Private**.
* **Private** -- Access private AWS services such as a VPC, EC2 instances, load balancers, RDS DB instances, on private IP address space.
* **Public** -- Access public AWS services such as Amazon Simple Storage Service (S3), DynamoDB, CloudFront, and Glacier. You will also receive [Amazon's global IP prefixes](https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html) (approximately 2,000 prefixes).
Public VIFs require manual intervention from Amazon and could take up to 72 hours. For more information, see [Configuring Public AWS Connections with IP Addresses Provided by AWS](/cloud/megaport/aws/aws-public-ip).
* **AWS Connection Name** -- This is a text field and will be the name of your virtual interface that appears in the AWS console. For easy mapping, use the same name for this field as you did for the VXC name on the previous screen.
* **AWS Account ID** -- This is the ID of the account you want to connect. You can find this value in the management section of your AWS console.
* **Customer ASN** -- Your network's autonomous system number (ASN). For private Direct Connects, this must be a private ASN in the range 64512 - 65535. For public Direct Connects, this can be a private or public ASN in the range 2 - 4294967294. If using a public ASN, you must own it.
* **BGP Auth Key** (optional) -- Specify the BGP key. If you leave this blank, Megaport negotiates a key automatically for you with AWS which will be displayed in the Megaport Portal. The key is not displayed in the AWS console.
The BGP Auth Key is generated during the ordering process when this field is left blank. It will not be displayed on the Summary page when ordering. To see the key, view the Connection Settings after the service has been deployed and is live.
* **Customer IP Address** -- The IP Address space (in CIDR format) you will use on your network for peering. For private connections, this field is optional and if left blank, Megaport assigns a private /30 address. For public connections, this field is required and needs public IPs (/30) allocated by you for BGP connectivity. You must own the public IPs.
* **Amazon IP Address** -- The IP address space in CIDR format assigned in the AWS VPC network for peering. For private connections, this field is optional and if left blank, Megaport automatically assigns a private /30 address. For public connections, this field is required and needs public IPs (/30) allocated by you for BGP connectivity. You must own the public IPs.
* **Prefixes** -- For Public connections only - IP Prefixes to announce to AWS. RIR-assigned IPv4 addresses only. Specify the prefixes you will advertise when deploying a Public Direct Connect.
Once you configure Prefixes for a Public connection, you cannot change them and the field is grayed out. To change this value, create a support ticket with AWS so they can make this change a non-impacting way. Or you can cancel the Hosted VIF and reorder. In both cases, you need to wait for AWS to manually approve the request.
7. Click **Next**.\
A summary page appears that includes the monthly cost. Click **Back** to make changes or click **Add VXC** to move this configuration to your cart. Once you have finished this configuration, you can configure additional VXCs or proceed through the checkout process.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
11. Accept the virtual interface in AWS.\
To review and accept in the AWS console, go to **Services** >
**AWS Direct Connect** for the Direct Connect dashboard. For a
private virtual interface, you must also have an existing virtual
private gateway or Direct Connect gateway. For more information, see the
[AWS documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/accepthostedvirtualinterface.html).
Once you accept the hosted VIF in AWS, the VXC state changes to configured in the Megaport Portal. You can review the configuration details to get the A-End VLAN ID, BGP Auth Key, and IP addresses that you need to configure your router.
**To edit a Hosted Virtual Interface**
* Click the gear icon next to the connection in the Megaport Portal to make changes.
If you have permissions to edit VXCs, you can modify the details on
the Megaport side including the connection name, VLAN ID, Service Level Reference, and rate limit.\
If this is a termed connection, you cannot reduce the term.\
Once submitted, those changes take effect in a few minutes.
You can also make changes to the AWS details of a VXC. When you
change the AWS details, the service will be rebuilt and you need to
accept changes to the connection in AWS.
**To delete a Hosted Virtual Interface**
* Click the trash icon next to the connection in the Megaport Portal.
For more information, see [Terminating a VXC](/connections/terminating-vxc).
# Integrating Megaport with Salesforce Hyperforce on AWS
Source: https://docs.megaport.com/cloud/megaport/aws/hyperforce
This help topic describes how to integrate Megaport with Salesforce Hyperforce on AWS.
This topic describes how you can use Megaport to deploy the AWS Direct Connect (Hosted Connection) architecture for Hyperforce support using a public VIF.
You can use Megaport to create an AWS Direct Connect Layer 2 connection between your on-premises or colocation-based infrastructure and your Salesforce Hyperforce environment on AWS.
Before you begin, ensure that you have created a Port (You can also use MCR and MVE to access Hyperforce). After you create the Port, you can connect a Virtual Cross Connect (VXC) from the Port to the virtual interface associated with the AWS infrastructure. A VXC is a point-to-point Ethernet connection between an A-End (your Port) and a B-End (in this case, your AWS instance).
If you aren’t a Megaport customer, you can create a 10 Gbps, 100 Gbps, or higher Port in one of our global [data centers/Points of Presence](https://www.megaport.com/megaport-enabled-locations/). If your company is not located in one of our PoPs, you can procure a last mile circuit to one of the sites to connect to Megaport. [Contact Megaport](https://www.megaport.com/contact/) for more information.
If you require a Port in a different location to physically separate this solution from other existing traffic traversing your Ports, we recommend that you [create a new one](/connections/creating-port) before proceeding.
This image shows Port access to Hyperforce via Public Virtual Interface (VIF).
## Salesforce Hyperforce overview
Hyperforce is the next-generation Salesforce infrastructure architecture, built for the public cloud. Hyperforce infrastructure is composed of code rather than hardware, so that the Salesforce platform and applications can be delivered rapidly and reliably to locations worldwide, giving customers more choice and control over data residency.
When customers require direct network connectivity from their on-premises environment to Hyperforce, AWS Direct Connect can be used. This enables access into the AWS cloud with guaranteed bandwidth, and is recommended for latency, performance sensitive situations, and architectures.
A public VIF is used for Hyperforce connectivity. Traffic is sent from the customer location, and after it arrives at the Direct Connect location, can be routed through the AWS network to either AWS public services or services deployed on the AWS cloud which are accessible via Elastic IP addresses (such as Hyperforce).
To create a public VIF for AWS, you need to specify the public peer IP addresses. For more information, see [Configuring Public AWS Connections with IP Addresses Provided by AWS](/cloud/megaport/aws/aws-public-ip).
If you do not have public IP addresses, you need to request them from AWS. The request requires approval from the AWS Direct Connect team and it can take up to 72 hours for AWS to review and approve your request.
## Best practices and considerations
When connecting to Hyperforce on AWS, you should consider the following:
* **Failover** -- Routing information between the AWS network and your router is exchanged dynamically through Border Gateway Protocol (BGP). To improve failover times, we suggest that you implement Bidirectional Forwarding Detection (BFD).
* **Routing security** -- You must connect to AWS using public IP addresses to use a public VIF. Advertising a public IP address space to AWS that’s not advertised to the public internet will ensure traffic from AWS will only route to these IPs using the Direct Connect connections. To ensure your users access Hyperforce only through the Direct Connect connection, you can add IP prefixes selected for a Direct Connect connection to the trusted IP ranges for your organization.
* **Prioritizing Routing Over AWS Direct Connect** -- Public IP prefixes used by Hyperforce are advertised through public VIF on a Direct Connect connection and to the internet. Therefore, you might receive routing information about both through the Direct Connect connection and the ISP connection. In case they learn the same prefixes, it’s best to set proper routing policies in the on-premises environment (routers), so a Direct Connect connection is preferred.
## Integrating Megaport with Hyperforce on AWS
You can use the Megaport Portal to create a VXC to the Hyperforce on AWS environment using a public VIF.
**To integrate Megaport with Hyperforce on AWS**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.\
If you haven't already created a Port, see [Creating a Port](/connections/creating-port).
2. Add an AWS connection for the Port.\
If this is the first connection for the Port, click the AWS tile. The tile is a shortcut to the configuration page. Alternatively, click **+Connection**, click **Cloud**, then click **AWS**.
3. For AWS Connection Type, you have the options of **Hosted VIF** or **Hosted Connection**.\
For this scenario, click **Hosted Connection**.
4. Next, create a new VXC. In the Select Destination Port list, select the AWS region and the interconnection point for your connection, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection. You can also filter by diversity zone.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. You must choose from the provided bandwidth options. The sum of all hosted virtual VXCs to a service can exceed the Port capacity (for example, 10 Gbps, 100 Gbps, or higher), however the total aggregate will never burst beyond the Port capacity.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more details, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This VLAN ID must be a unique ID on this Port and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged** to remove the VLAN tagging for this connection. The untagged option limits you to only one VXC deployed on this Port.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.
7. Specify the cloud details:
* **AWS Connection Name** -- This is a text field and will be the name of your virtual interface that appears in the AWS console. For easy mapping, use the same name for this field as you did for the VXC name on the previous screen.
* **AWS Account ID** -- This is the ID of the account you want to connect. You can find this value in the Account Settings section of your AWS console.
8. Click **Next**.
9. Review the connection details and click **Add VXC**.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
Your work in the Megaport Portal is complete. Next, you will connect the new VXC to your AWS environment.
13. In approximately 2 minutes, log in to your AWS account.\
The VXC you implemented will appear in your Direct Connect under Connections.
14. Click **Create connection**.\
You will then need to connect to a Direct Connect Gateway. For details on connecting to various types of gateways, see [Working with Direct Connect gateways - AWS Direct Connect](https://docs.aws.amazon.com/directconnect/latest/UserGuide/direct-connect-gateways.html).
## Helpful references
* [Diversity in AWS Connections](/cloud/megaport/aws/aws-diversity)
* [Introducing Hyperforce - General Information & FAQ](https://help.salesforce.com/s/articleView?id=000388902\&language=en_US\&type=1)
* [Salesforce Hyperforce Product Overview](https://www.salesforce.com/products/public-cloud-infrastructure/)
* [How to Access Salesforce Hyperforce Securely and Reliably with AWS Direct Connect](https://aws.amazon.com/blogs/apn/how-to-access-salesforce-hyperforce-securely-and-reliably-with-aws-direct-connect/)
# Connecting to AWS Direct Connect
Source: https://docs.megaport.com/cloud/megaport/aws/index
This help topic describes the supported Megaport connection models for AWS Direct Connect.
You can create a network connection from your Port to AWS with Virtual Cross Connects (VXCs) and AWS Direct Connect.
Megaport supports three AWS Direct Connect models:
* [Hosted Virtual Interfaces (Hosted VIFs)](#vif)
* [Hosted Connections](#hosted)
* [Direct Connect dedicated connections](#direct)
## Hosted Virtual Interfaces
Hosted VIFs can connect to public or private AWS cloud services. Each VXC (Hosted VIF) lets you manage the bandwidth and as long as the total bandwidth of the VXCs does not exceed the size of the Port, utilization of each VXC (to the VPC) will not affect the other VXCs.
Key features include:
* Connections can share bandwidth, which is managed and monitored to ensure defined network performance.
* If you connect to AWS from a Megaport Cloud Router (MCR), the Hosted VIF provides access to the routing information for automatic configuration of your MCR.
* You can change the service speed without affect to the service.
* This model does not support Transit Gateway virtual interfaces.
* AWS Direct Connect port charges are included with your Megaport order. You are informed of the billing details and shown the Megaport rates as you configure the connection.
* Maximum VXC speed of 5 Gbps. Higher speeds might be available depending on location and Port capabilities.
This is the original option supported by Megaport for AWS Direct Connect.
To get started with Hosted VIFs:
* [Configure and maintain an AWS Hosted VIF](/cloud/megaport/aws/hosted-vif)
* [Helpful references](#helpful-references)
## Hosted Connections
A Hosted Connection can support one private, public, or transit virtual interface.
Key features include:
* Support for Transit Gateway.
* Dedicated (not shared) bandwidth with one-to-one subscription.
* You cannot change the speed after you create the connection. To change the speed, you must create and configure a new connection.
* The configuration process does not have automatic access to routing information for the MCR and you need to configure the routing manually.
* Maximum VXC speed of 25 Gbps. Higher speeds might be available depending on location and Port capabilities.
* Support for diverse AWS ports for resiliency and to avoid any single-point-of-failure.
* AWS Direct Connect port charges are billed by Amazon.
With Hosted Connections, you can aggregate connections using Transit Gateway and have a single Hosted Connection with dedicated bandwidth instead of multiple Hosted VIFs sharing the bandwidth. With this scenario, a VPC can be affected by other VPCs requiring bandwidth over the same connection.
If you are not co-located in a data center that offers Hosted Connections, you can use a VXC to connect to the closest enabled location.
To get started with Hosted Connections:
* [Configure and maintain an AWS Hosted Connection](/cloud/megaport/aws/hosted-connection)
* [Helpful references](#helpful-references)
## Direct Connect dedicated connections
A Direct Connect dedicated connection can support up to 50 public or private virtual interfaces and up to four transit virtual interfaces. The total number of VIFs cannot exceed 51 per dedicated connection. With this option, you provision a Direct Connect port in the AWS Console and work with Megaport to set up a physical cross connect from the Direct Connect port to a Port at the same data center. Then, using a private untagged VXC, you can connect the Port to a second Port in a different data center.
Key features include:
* You cannot change the port speed after you create the connection request. To change the port speed, you must create and configure a new connection.
* Support for a large number of VPCs.
* Support for Transit Gateway configurations.
* AWS port charges are billed by Amazon.
To get started with a Direct Connect dedicated connection:
* [Configure and maintain a dedicated connection](/cloud/megaport/aws/dedicated-connection)
## Helpful references
To learn more about AWS Direct Connect models and features, explore these resources.
**Additional Megaport Information**
* [Megaport AWS Infopaper](https://www.megaport.com/services/amazon-web-services/)
* [AWS Virtual Gateway vs. Direct Connect Gateway vs. Transit Gateway](https://www.megaport.com/blog/aws-vgw-vs-dgw-vs-tgw/)
* [Enabling Cloud-Native VPN/Encryption Options Over Dedicated Cloud Connectivity Paths](/encryption/cloud-native-vpn-encryption)
**Amazon Documentation**
* [AWS Direct Connect Documentation](https://docs.aws.amazon.com/directconnect/index.html#lang/en_us)
* [AWS Direct Connect Limits](https://docs.aws.amazon.com/directconnect/latest/UserGuide/limits.html)
* [AWS Direct Connect models](https://aws.amazon.com/blogs/aws/new-gigabit-connectivity-options-for-amazon-direct-connect/)
* [AWS PrivateLink](https://aws.amazon.com/privatelink/)
# Configuring AWS Outposts Rack with Private Connectivity
Source: https://docs.megaport.com/cloud/megaport/aws/outposts
This help topic describes how to deploy an AWS Outposts with AWS Direct Connect Hosted Connection via a Megaport Port, a Megaport Cloud Router (MCR), and Virtual Cross Connects (VXCs).
This topic describes how to deploy AWS Outposts Rack with an AWS Direct Connect Hosted Connection via a Megaport Port, a Megaport Cloud Router (MCR), and Virtual Cross Connects (VXCs).
AWS Outposts extends an Amazon virtual private cloud (VPC) from an AWS Region to an Outpost with the VPC components that are accessible in the Region, including internet gateways, virtual private gateways, Amazon Direct Connect gateways, and VPC endpoints. An Outpost is homed to an Availability Zone in the Region and is an extension of that Availability Zone that you can use for resiliency.
Megaport has received the AWS Service Ready accreditation for Outposts.
[Download a PDF](https://media.megaport.com/docs/pdf/aws-outposts-megaport.pdf) version of this topic.
## Why deploy AWS Outposts?
A Megaport Direct Connect solution for AWS Outposts Rack provides a custom hybrid architecture that allows you to:
* Control where your workloads run and where your data resides, meeting certain requirements around local data residency or ultra-low latency processing.
* Process data locally using familiar AWS services, tools, and APIs.
* Streamline hybrid IT operations using a single AWS console to fully manage the same services running in the cloud and locally.
* Enable disaster recovery within the same country at a distance that meets regulatory requirements. This is important in countries where there is only one AWS Region, because you can effectively create a substitute second Region to set up recovery a safe distance from the primary site within the same country.
For more information about AWS Outposts, see the [*Outposts User Guide for Rack*](https://docs.aws.amazon.com/outposts/latest/userguide/what-is-outposts.html). This topic includes excerpts from the AWS user guide.
## Networking components
A Megaport Direct Connect solution for Outpost Rack includes these networking components and deployment roles:
* An AWS Region and an on-premises network
* A VPC with multiple subnets in the Region
* A customer-owned IP address pool
* An Outpost in the on-premises network
* A Megaport MCR for routing between subnets
* A Megaport Port and VXC for AWS Region connectivity
* Physical fiber cross connects to Megaport
### Redundancy
To establish full redundancy between each Outpost Rack Networking Device (OND) and Megaport, we recommend this configuration:
* Each OND is dual connected to Megaport.
* Two MCRs are configured for each Outpost deployment.
* The Racks within the same Outpost deployment (second, third, and so on) use the same MCR pair; each OND for an additional Rack uses the same dual port and link aggregation group (LAG) configuration.
* The MCRs terminate at different AWS Direct Connect locations.
### VPCs and subnets
A VPC spans all Availability Zones in its AWS Region. You can extend any VPC in the Region to your Outpost by adding an Outpost subnet. To add an Outpost subnet to a VPC, specify the Amazon Resource Name (ARN) of the Outpost when you create the subnet. For more information, see [Creating the Outpost subnet](/cloud/megaport/aws/outposts#creating-the-outpost-subnet) in this topic.
Outposts support multiple subnets. You can specify the EC2 instance subnet when you launch the EC2 instance in your Outpost. You cannot specify the underlying hardware where the instance is deployed, because the Outpost is a pool of AWS compute and storage capacity.
Each Outpost can support multiple VPCs that can have one or more Outpost subnets. For information about VPC quotas, see [Amazon VPC Quotas](https://docs.aws.amazon.com/vpc/latest/userguide/amazon-vpc-limits.html) in the *Amazon Virtual Private Cloud User Guide*. You create Outpost subnets from the VPC CIDR range of the VPC where you created the Outpost. You can use the Outpost address ranges for resources, such as EC2 instances that reside in the Outpost subnet. AWS does not directly advertise the VPC CIDR, or the Outpost subnet range to your on-premises location.
## Outpost service link
The connection from an Outpost back to an AWS Region is called a service link. When you select the private connectivity option for your Outpost Region connectivity, AWS establishes the service link connection using the VPC and subnet that you specified.
For an optimal experience and resiliency, AWS recommends that you use redundant connectivity. The service link connection requires a minimum 500 Mbps or greater bandwidth connection. Your bandwidth requirements will vary, depending on:
* The number of Outpost Racks and Outpost capacity configurations.
* The workload characteristics, such as the Amazon Machine Image (AMI) size, application elasticity, burst speed requirements, and the Amazon VPC traffic to the Region.
### Communication paths
You need to consider communication paths for two purposes:
1. **The connection from an Outpost back to an AWS Region, called a service link path** - To establish this path, you specify a VLAN subnet with a range of /30 or /31 and an IP address for the service link VLAN on the OND.
2. **The connection from your on-premises network to a VPC, called a local gateway path** - To establish this path, you specify a VLAN subnet with a range of /30 or /31 and an IP address for the local gateway VLAN on the OND.
This topic covers only the service link path and doesn't include the local gateway path details. For more information about the local gateway, see [Local gateway network parameters](/cloud/megaport/aws/outposts#localgateway) in this topic, and [Local gateway](https://docs.aws.amazon.com/outposts/latest/userguide/outposts-local-gateways.html) in the *Outposts User Guide for Rack*.
### Service link networking parameters
The service link requires a /26 IPv4 address block advertised as two contiguous /27 blocks within your network. These IP blocks can be an [RFC 1918](https://datatracker.ietf.org/doc/html/rfc1918) address space used on your local network, or another range of IPs you use privately. Alternatively, you can provide a /26 that is publicly addressable.
**/26 IPv4 address block**
These OND networking parameters configure the OND end of the LAG connection and the corresponding endpoints on MCR(s). For each MCR, you need:
* A service link BGP autonomous system number (ASN). The ASNs can be the same on each MCR.
* A VLAN that represents the point-to-point connectivity between the MCR and the ONDs.
* An IP address and subnet mask for each MCR (for a total of 2).
Each OND needs a service link BGP ASN and an IP address and subnet mask (for a total of 2). The MCR and Outpost BGP ASNs must be different.
Before you begin, define the networking parameters for the service link connection in this table:
| Component | Networking Parameters |
| - | - |
| Service link BGP ASN | 16 or 32-bit ASN from private ASN range (64512 - 65534 or 4200000000 - 4294967294) |
| First LAG (between the OND and MCR #1) | Outpost IP address and subnet mask (/30 or /31) |
| | Customer IP address and subnet mask (/30 or /31) |
| | Customer BGP ASN (16 or 32-bit) |
| | Service Link VLAN1 (can be the same across LAGs) |
| Second LAG (between the OND and MCR #2) | Outpost IP address and subnet mask (/30 or /31) |
| | Customer IP address and subnet mask (/30 or /31) |
| | Customer BGP ASN (16 or 32-bit) |
| | Service link VLAN1 (can be the same across LAGs) |
### Local gateway networking parameters
This topic covers only the service link path and does not detail the local gateway path configuration. For more information about local gateways, see [Local gateway](https://docs.aws.amazon.com/outposts/latest/userguide/outposts-local-gateways.html) in the *Outposts User Guide for Rack*.
A local gateway serves **two purposes**:
1. It provides a target in your VPC route tables for on-premises destined traffic.
2. It performs network address translation (NAT) for instances that have been assigned addresses from your customer-owned IP pool.
You can also use the local gateway for communication for internet-bound traffic.
You have several different options for local gateway connectivity via the Megaport MCR, depending on your current-state network and objectives.
A local gateway VLAN from the Megaport LAG Ports might have VLANs configured for one of these options:
1. You might only use the service link path for region communication instead of using the local gateway.
2. An Outpost data center LAN via a separate Megaport Port.
3. A local AWS Region via an MCR.
4. Any AWS Region via the Megaport network.
5. Any Megaport-enabled data center globally.
The networking parameters for the local gateway will depend on the current state network and solution requirements.
## Before you order
Ordering an Outpost is a two-step process: first, you order an Outpost from AWS. After installation of your Outpost, you create an Outpost subnet and link it with a VPC.
Before ordering an Outpost:
* Make sure your site meets these detailed physical requirements: [Site requirements for Outpost Rack](https://docs.aws.amazon.com/outposts/latest/userguide/outposts-requirements.html).
* You need an AWS Enterprise Support plan.
## Ordering an Outpost
With the site requirements verified and an AWS support plan in place, follow these steps to order your Outpost.
**To order an Outpost**
1. Open the AWS [Outposts console](https://console.aws.amazon.com/outposts).
2. Select Create Outpost.
3. Select the Racks radio button.
4. Enter the name and description fields for your deployment.
5. Select an Availability Zone for your Outpost from the drop-down list.
6. Select the **Use private connectivity** check box.
Once you select the private connectivity option for your Outpost, AWS automatically creates a private connectivity endpoint and assigns private IPs to it from the VPC subnet’s CIDR that you have selected to use for the AWS Outpost private connectivity.
From then on:
* All service link traffic between your AWS Outpost Rack and the AWS Outpost service endpoints in the Region will use your designated private connectivity.
* AWS Outpost automatically creates a service-linked role in your account that enables it to complete the following tasks on your behalf:
* Create network interfaces in the subnet and VPC that you specify, and creates a security group for the network interfaces.
* Grant permission to the AWS Outpost service to attach the network interfaces to a service link endpoint instance in the account.
* Attach the network interfaces to the service link endpoint instances from the account.
7. For VPC and Subnet, select a VPC and subnet in the same AWS account and Availability Zone as your Outpost.
8. For Site ID, either click **Create a new site**, or select an existing site from the drop-down list. The site settings appear.
9. Click **Create Outpost**.
10. Choose the Outposts catalog from the menu on the left.
11. Select Supported hardware type, and choose a Configuration.
If an appropriate configuration option is not available, contact the [AWS Outpost team](https://pages.awscloud.com/AWS-Outposts-capacity-configuration.html) to request a custom configuration.
12. Click **Place order**.
13. Choose Next.
14. Confirm your configuration, then click Place order.
A dialog confirms that the Outpost order has been created and scheduled. Once you receive confirmation that the Outpost has been installed, the next step is to launch the instance on your Outpost Rack.
## Before you launch an instance
Once your Outpost order is installed and available for use, you can launch your EC2 instance on your Outpost Rack. Before launching an instance, make sure you meet these prerequisites:
1. Configure permissions for an IAM entity (user or role) to allow the user or role to create the service-linked role for private connectivity. The IAM entity needs permission to access the following actions:
`iam:CreateServiceLinkedRole on arn:aws:iam::*:role/aws-service-role/ outposts.amazonaws.com/AWSServiceRoleForOutposts*`\
`iam:PutRolePolicy on arn:aws:iam::*:role/aws-service-role/ outposts.amazonaws.com/AWSServiceRoleForOutposts*`\
`ec2:DescribeVpcs`\
`ec2:DescribeSubnets`
2. In the same AWS account and Availability Zone as your Outpost, create a VPC for the sole purpose of Outpost private connectivity with a subnet /25 or larger that does not conflict with 10.1.0.0/16. (This block is defined and used by AWS for intra-VPC connectivity, including subnets in the Region.)
3. Enable a Megaport AWS Direct Connect (DX) transport between the data center Outpost location and the AWS Region with a Private VIF connection into the VPC.
4. Create an AWS Direct Connect connection, private virtual interface, and virtual private gateway to allow your Outpost to access the VPC.
5. Advertise the subnet CIDR to your on-premises network via AWS Direct Connect. For more information, see [Direct Connect virtual interfaces](https://docs.aws.amazon.com/directconnect/latest/UserGuide/WorkingWithVirtualInterfaces.html) and [Working with AWS Direct Connect gateways](https://docs.aws.amazon.com/directconnect/latest/UserGuide/direct-connect-gateways.html).
## Creating the Outpost subnet
After meeting the prerequisites, you need to create the Outpost subnet.
Once you create an Outpost subnet and link it with a VPC in the associated AWS Region, the VPC will cover the Outpost itself as well.
**To create the Outpost subnet**
1. Open the AWS [Outposts console](https://console.aws.amazon.com/outposts).
2. Select Outposts from the left navigation pane.
3. Select the installed Outpost.
4. Choose Actions, and then click Create Subnet.
5. Select your VPC and determine an IP range for the subnet that you can allocate.
6. Select Create.
AWS establishes the service link connection using the VPC and subnet that you specified. After the service link is established, the Outpost is in service and the AWS configuration is complete.
## Megaport configuration
Now you are ready to set up the Megaport side of the Outposts deployment. The configuration steps are summarized here, with links to the procedure details:
1. [Create a Megaport Port](/cloud/megaport/aws/outposts#createport).
2. [Create one or two MCRs](/cloud/megaport/aws/outposts#mcr) and [VXC connections](/connections/overview).
3. [Create an AWS Direct Connect Hosted Connection](/cloud/megaport/aws/outposts#awshc).
4. [Accept the connection](/cloud/megaport/aws/outposts#accept) in the AWS Portal.
5. [Create the VIF](/cloud/megaport/aws/outposts#vif) in the AWS Portal.
6. [Create a private VXC](/cloud/megaport/aws/outposts#private) between the Port and MCR to connect to an MCR in the current company account. A private VXC is essentially a point-to-point Ethernet connection between an A-End (your Port) and a B-End (the Private VXC destination type), which is the MCR in this case. Select the target MCR as the B-End of the connection.
## Outposts Rack to Megaport Ports physical connection
The standard redundant deployment consists of four physical ports, connected to the Outposts Rack via fiber cross connects, as shown here:
Configuration notes:
* Each OND connects to two physical Ports via a fiber cross connect.
* Each OND connects to separate zones (either Red or Blue) for physical redundancy.
* Each Port must be configured and deployed in a LAG group using the Link Aggregation Control Protocol (LACP). Ports in the red diversity zone are part of a LAG group. Ports in the blue diversity zone in a separate LAG group.
* Ports must be deployed at 10 Gbps.
* Creating the port generates a Letter of Authorization (LOA) for the port assignment on the Megaport network, as described in [Creating a Port](/cloud/megaport/aws/outposts#createport). This LOA is used by the data center operator to connect the fiber facilities. For more information about the terminating port specifications, see [Technical Specifications](/tech-specs).
* For diversity, each red and blue diversity zone is homed to a separate MCR.
* The LAG Ports and the MCR do not have to be in the same data center. They can be in separate locations and virtually connect across the Megaport network.
## Creating a Port
The Megaport Portal steps you through selecting the Port location and provider, specifying the Port details, and placing the order.
Before proceeding, ensure that you have set up your Megaport Portal account. For more information, see [Setting Up a Megaport Account](/setting-up).
**To create a Port**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Services**, then select **Port**.
The Create Port page opens. Complete the sections on this page to configure your Port. An order summary updates as you make selections. On wider screens, it appears as a panel on the right. On narrower screens, it appears as a bar at the bottom of the page that you can click to expand.
3. In the **Details** section, specify these fields:
* **Port Name** -- Specify a name for the Port that is easily identifiable.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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 Port is not automatically updated with the Port service level reference number.
4. In the **Location** section, select the data center where your Outposts Rack is deployed.\
Use the **Search** field to find a location by metro name, country, data center name, or provider name. You can also search by address details, such as a street, city, state, or postcode. Alternatively, browse the region tabs, then select a location.
5. In the **Provider** section, select a data center provider, then select a data center from the drop-down list.\
Only providers and data centers available at your selected location are listed. If your search term in the Location section matches a specific provider or data center, the Provider list narrows to that provider. If the term matches only a metro or country, the Provider list shows every provider available at that location.
6. In the **Configuration** section, specify these fields:
* **Port Speed** -- Select 10 Gbps or higher. The Outposts Rack solution requires this minimum speed.
* **Port Diversity** -- If diversity is available at your selected location and speed, a **Diversity Option** drop-down list appears. You can create two diverse Ports or choose an existing Port for the new Port to be diverse from. For more information about configuring Port diversity, see [Port Diversity](/connections/port-diversity).
* **LACP & LAG Ports** -- The Outposts Rack solution requires that Ports be enabled with LACP. Enable LACP on Port to make the Port a member of a LAG, then select the number of Ports in the LAG, up to a maximum of 8. For more information about LAG, see [Creating a Link Aggregation Group](/connections/lag).
7. In the **Pricing** section, specify these fields:
* **Contract Term** -- Select a contract term. Longer terms result in a lower monthly rate. *12 Months* is selected by default.
* **Contract Renewal** -- Automatically renews the contract at the same price and term length when the current term ends. This is enabled by default. If you disable it, the contract rolls over to a month-to-month term at the end of the current term, without the term discount.
For more information, see [Minimum Term Renewal](/portal-admin/auto-renew).
Partner and partner-managed accounts cannot view or change Port contract terms.
8. In the **Add-ons** section, review the following:
* **Cross Connect** -- If the location has Cross Connect availability, a option appears in the Add-ons section.
Enable the **Cross Connect** add-on to add a Cross Connect to your Port order. The monthly rate and one-time fee for the Cross Connect appear on the card.
For more information, see [Ordering a Cross Connect](/connections/cross-connect/).
9. In the **Resource Tags** section, add any tags you want to apply to this Port.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
The price updates dynamically based on your selections in the order summary. Note that some partner-managed accounts do not display the pricing details.
10. Review the order summary, then click **Add Port**.
The newly created Port is added to your cart. If you create a service in a market that is not enabled, you are prompted to enable it first. For more information, see [Setting Up Financial Details](/setting-up/finance-basics). For full redundancy, repeat these steps for each diverse Port your Outposts Rack deployment requires before proceeding to checkout.
11. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
12. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
13. Click **Order Now**.
In most cases the Port is provisioned immediately, but sometimes it can take longer. After the Port is provisioned, Megaport generates a Letter of Authorization (LOA) specifying the demarcation point to be applied to your service. A PDF of the LOA is sent to you by email.
14. Click the **Download LOA** link next to the new Port on the Services page.\
The **Download LOA** link appears after the Port is available. For more information about the LOA, see [Megaport Letter of Authorization](/portal-admin/loa).
15. Provide the LOA to your data center operator to establish the physical Cross Connect from your network device to your new Port.
The cost of a new cross connection and any related VXC fees are the responsibility of the customer, as outlined in [Megaport's Global Services Agreement](https://www.megaport.com/legal/global-services-agreement/).
## Creating an MCR
This section 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 will only be able to create MCR instances in billing markets you are registered in. For more information, see [Setting Up a Megaport Account](/setting-up).
**To create an MCR**
1. In the Megaport Portal, go to the **Services** page.
2. Click **Add Service**, then select **Cloud Router (MCR)**.
The Create Cloud Router page opens. Complete the sections on this page to configure your MCR. The order summary updates as you make selections. On wider screens, the summary is displayed in a panel on the right. On narrower screens, it is displayed in a bar at the bottom of the page that you can expand.
3. In the **Details** section, specify these fields:
* **MCR Name** -- Specify a name that helps you identify the MCR, particularly if you plan to have more than one MCR.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Project** (optional) -- Select a project to add the MCR to, or leave the default (No Project). To create a project, select **New Project** at the bottom of the list. For more information, see [Creating an MCR](/mcr/creating-mcr).
4. In the **Location** section, specify these fields:
* **Location** -- Select your preferred location. The country you choose must be a market in which you have already registered. Use the **Search** field to find a location by metro name, country, data center name, or provider name. You can also search by address details, such as a street, city, state, or postcode. Alternatively, browse the region tabs, then select a location.
* **Mode** -- Select Auto to have Megaport automatically choose a provider and data center at the selected location. Select Manual to choose the provider and data center yourself.
* **Diversity Zone** -- Select Red or Blue, or select Auto to have Megaport select the zone for you. The selected diversity zone appears in the order summary. For more information, see [MCR Diversity](/mcr/mcr-mve-diversity).
5. If you selected Manual mode, in the **Provider** section, select a data center provider, then select a data center from the **Data Centre** drop-down list.\
Only providers and data centers available at your selected location are listed.
6. In the **Configuration** section, select the required **Rate Limit**.\
The MCR can scale from 1 Gbps to 100 Gbps. Available rate limits depend on the selected location and diversity zone. The rate limit is an aggregate capacity that determines the speed for all connections through the MCR, and is shared between all the Cloud Service Provider (CSP) connections added to it. The rate limit is fixed for the life of the service.
7. In the **BGP & ASN** section, specify these fields:
* **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.
For more information, see [MCR Peering Between Private Clouds](/mcr/mcr-private-cloud) and [Configuring BGP Advanced Settings](/mcr/mcr-bgp-advanced).
* **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 several 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 finish 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 more information about overriding the BGP state for an individual connection, see [Shutting down a BGP connection](/mcr/configuring-mcr#bgpshut).
8. In the **Add-ons** section, review the following:
* **IPsec** (optional) -- Turn on IPsec to add IPsec tunnels to the MCR, then select a **Number of Tunnels** (10, 20, or 30). For more information, see [Using IPsec with MCR](/mcr/ipsec-mcr).
9. In the **Pricing** section, specify these fields:
* **Contract Term** -- Select a contract term: No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate.
* **Contract Renewal** -- Automatically renews the contract at the same price and term length when the current term ends. The initial setting comes from your company default. If you disable it, the contract rolls over to a month-to-month term at the end of the current term, without the term discount. Contract Renewal is not available when you select No Minimum Term.
For more information, see [Managing Minimum Term Renewal](/portal-admin/auto-renew).
For more information about contract terms, see [MCR Pricing and Contract Terms](/finance/mcr-pricing).
10. In the **Resource Tags** section, add any tags you want to apply to this MCR.\
To add a tag, click **Add New Tag**, then specify these fields:
* **Key** -- Specify a lowercase string with a maximum length of 128 characters. Valid characters are lowercase letters, numbers, and `- . _ : / \`.
* **Value** -- Specify a string with a maximum length of 256 characters. Valid characters are letters, numbers, spaces, and `- . _ : @ / + \`.
Repeat for each tag. You can add up to 50 tags.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that identifies a person or company.
The price updates dynamically based on your selections in the order summary. Note that some partner-managed accounts do not display the pricing details.
11. Review the order summary, then click **Add MCR**.
The newly created MCR is added to your cart under Configured Services, ready for checkout.
12. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
13. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
14. Click **Order Now**.
The MCR provisioning takes approximately 59 seconds to complete.
MCR is postpaid. For example, if you place your order on January 15, your first invoice will be issued on February 1, and the charge will cover the period from January 15 to January 31.
Now that you have deployed an MCR, the next step is to add a Virtual Cross Connect (VXC) to AWS Direct Connect.
## Creating MCR connections to AWS
You can create a VXC from an MCR to AWS Direct Connect (DX) through the Megaport Portal. Follow the steps in this section to establish a private VIF connection that can connect either directly to a selected VPC or to a range of VPCs either in a single or multiple AWS regions (within a single AWS account).
### Before you begin
AWS does not support AWS Transit Gateway for AWS Outposts private connectivity; the Amazon Direct Connect gateway is supported for cross-region Direct Connect access if required. Throughout this article, termination to an AWS VGW via a Private Virtual Interface (VIF) will be the default and recommended configuration.
### Private Virtual Interface
Before you create a private connection from an MCR to AWS, make sure you have the following:
* Your [AWS account number](https://docs.aws.amazon.com/general/latest/gr/acct-identifiers.html#FindingYourAccountIdentifiers).
* An [AWS virtual private gateway](https://docs.aws.amazon.com/vpn/latest/s2svpn/SetUpVPNConnections.html) or [Direct Connect gateway](https://docs.aws.amazon.com/directconnect/latest/UserGuide/direct-connect-gateways.html) associated with your VPCs.
* The ASN number for the AWS gateway. When creating the AWS gateway, we recommend private ASNs for private connections and we recommend replacing the AWS default ASN (usually 7224) as routing multiple VXC instances to the same target ASN can result in routing anomalies.
### Connecting a VXC from MCR to AWS Direct Connect
Once you have met the prerequisites, you can create the VXC to AWS from the MCR.
As a best practice, we recommend that you use the AWS Hosted Connection Direct Connect model. This section focuses on the AWS Hosted Connections model for Direct Connect service delivery.
The Hosted Connection configuration process does not have automatic access to routing information for the MCR and you need to configure the routing manually and specify BGP peering details on both the AWS virtual interface and the MCR A-End configuration in the Megaport Portal.
### Creating an AWS Direct Connect Hosted Connection
**To create a Hosted Connection VXC from an MCR to AWS**
1. In the Megaport Portal, go to the **Services** page and select the MCR you want to use.
2. Click **+Connection** and click **Cloud**.
3. Select AWS as the service provider, select Hosted Connection as the AWS Connection Type, select the destination port, then click **Next**.
Each destination port has either a blue or a red icon to indicate its diversity zone. To achieve diversity, you need to create two connections with each one in a different zone.
You can use the Select Destination Port search field to narrow the selection and you can filter by diversity zone.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. You must choose from the provided bandwidth options (50 Mbps to 25 Gbps). The sum of all hosted virtual VXCs to a service can exceed the Port capacity (for example, 10 Gbps, 100 Gbps, or higher), however the total aggregate will never burst beyond the Port capacity.
The minimum supported rate limit for Outpost Rack VXCs is 500 Mbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. For the MCR Connection detail, provide an IP address in CIDR format.
This value is the IP address for the interface and is the MCR IP address used for BGP peering to AWS. Assign a /30 address in private address space.
You can add a secondary IP address, if needed.
You can change these values in the A-End details of the VXC configuration.
7. Click **Add BGP Connection**.
8. Specify these values:
* **Local IP** – The IP address on this interface that communicates with the BGP peer.
The menu is automatically populated based on the address you specified as interface IP addresses.
* **Peer IP** – The IP address for the BGP peer.\
In this example, the local IP is 192.168.100.1 so the peer IP address would be 192.168.100.2.
* **Peer ASN** – The ASN of the AWS gateway.
* **BGP Password** – The shared key to authenticate the peer.
This field is optional for the creation of the VXC, but is required to set up the BGP peering. You can add it after you create the VXC.
The shared key length is from 1 to 25 characters. The key can include any of these characters:\
a-z\
A-Z\
0-9\
! @ # . \$ % ^ & \* + = - \_
* **Description** (optional) – Enter a description that will help identify this connection.\
The minimum description length is from 1 to 100 characters.
* **BGP State** – Shuts down the connection without removing it.
The initial setting will be taken from the setting on the A-End of the MCR. Enabling or shutting down the BGP state does not affect existing BGP sessions. The BGP state only affects new VXCs. This setting overrides the MCR state for an individual connection. For more information, see [Creating an MCR](/cloud/megaport/aws/outposts#mcr).
When you create the virtual interface in the AWS console for this connection, you will match these values.
9. Click **Add**.\
The BGP details appear under BGP Connection details.
10. Click **Next**.
11. Specify the connection details for the AWS service.
* **AWS Connection Name** – This is a text field and will be the name of your virtual interface that appears in the AWS console. The AWS Connection Name is automatically populated with the name specified in a previous step.
* **AWS Account ID** – This is the ID of the account you want to connect. You can find this value in the management section of your AWS console.
12. Click **Next** to proceed to the connection detail summary, click **Add VXC**, and order the connection.
After the VXC connection is deployed successfully, it appears on the Megaport Portal Services page and is associated with the MCR. Click the VXC title to display the details of this connection.
Note that the service status (Layer 2) is up but BGP (Layer 3) will be down because the configuration does not exist yet.
After the connection is deployed in the Megaport Portal, you need to accept the connection in the AWS console.
## Accepting the connection
**To accept the connection**
* In AWS, go to Services > AWS Direct Connect > Connections and click the connection name to review the details and accept. For more information, see the [AWS documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/accept-hosted-connection.html).
The state will be pending for a few minutes while AWS deploys the connection.
## Creating the VIF
**To create the virtual interface**
1. In the AWS console, click Create Virtual Interface. Enter these values for BGP peering:
* **Your router peer IP** – The BGP peer IP configured on the MCR.
* **Amazon router peer IP** – The BGP peer IP configured on the AWS endpoint.
* **BGP authentication key** – The password used to authenticate the BGP session.
* AWS provides [detailed steps](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-vif.html) for creating a Private Virtual Interface.
* The name you provided for the connection in the Megaport Portal appears in the Connection list on this page.
* The VLAN is populated and appears to be editable; however, you will get an error if you try to change it.
After you accept the Hosted Connection in AWS and create a virtual interface with the BGP peering settings, the VXC state changes to configured in the Megaport Portal.
## Creating a private VXC between a Port and an MCR
This section describes how to connect a private Virtual Cross Connect (VXC) between a Port and the Megaport Cloud Router in the Megaport network.
With a Port configured, you can deploy a private VXC to connect to an MCR in the current company account. A private VXC is essentially a point-to-point Ethernet connection between an A-End (your Port) and a B-End (the Private VXC destination type) which is the MCR in this case.
**To deploy a private VXC**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.
2. Select the originating Port (the A-End).
3. Click **+Connection**.
4. Click Private VXC.
5. Select the target MCR (the B-End).
6. Click **Next**.
7. Specify the connection details:
* **Connection Name** – The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** – The speed of your connection in Mbps. The maximum speed is displayed, and is set by the lowest speed at each end.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **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 Port. 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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don’t specify a value, Megaport will assign one. Leave the Port tag setting to Tagged.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
8. Click **Next**.
The next step is to configure the BGP settings for this VXC. 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. In this case, you specify one interface and add one BGP connection.
**To configure the BGP settings for the VXC**
1. On the MCR Connection details page, click **Add BGP Connection**.
2. Select the Local IP on this interface that communicates with the BGP peer from the drop-down menu.
3. Specify the BGP details for the Peer IP, Peer ASN, where the peer settings are related to the OND.
4. Click **Add** to save the VXC.\
Repeat these steps to configure more VXCs.
5. Click **Next**.
6. Click **Review Order** to proceed through the ordering process.
7. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
8. Click **Order Now**.
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.
## Verifying the BGP configuration
The MCR Looking Glass provides single-screen visibility into the BGP configuration. For more information, see [Viewing Traffic Routing Through MCR Looking Glass](/mcr/mcr-looking-glass).
**To view the BGP status**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC.
3. Click MCR A-End or MCR B-End.
4. Choose Details.
## Troubleshooting BGP
If the Services > Connection Detail page displays a status issue, verify these items:
1. Select the VXC and select MCR A-End or B-End.
2. Under BGP Connections, verify that the correct local ASN is in use for the A-End of the VXC.
3. Verify that the correct peer IP address is in use.
4. Verify that the correct BGP MD5 password is in use for the A-End 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
Use this setting to 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, troubleshooting, and so on.
**To temporarily disable a BGP connection**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC and select the A-End or B-End.
3. After the BGP connection details, click **Shut Down**.
4. Click **Yes** to confirm.
## Helpful references
* [AWS Outpost private connectivity blog](https://aws.amazon.com/blogs/networking-and-content-delivery/introducing-aws-outposts-private-connectivity/)
* [AWS Outpost User Guide for Rack](https://docs.aws.amazon.com/outposts/latest/userguide/what-is-outposts.html)
# Integrating Megaport with Snowflake on AWS
Source: https://docs.megaport.com/cloud/megaport/aws/snowflake
This help topic describes how to integrate Megaport with Snowflake on AWS.
You can use Megaport to create an AWS Direct Connect Layer 2 connection between your on-premises or colocation-based infrastructure and your Snowflake environment on AWS.
Before you begin, ensure that you have created a Port. After you create the Port, you can connect a Virtual Cross Connect (VXC) from the Port to the virtual gateway associated with the AWS VPC infrastructure. A VXC is a point-to-point Ethernet connection between an A-End (your Port) and a B-End (in this case, your AWS instance).
If you aren’t a Megaport customer, you can create a 10 Gbps, 100 Gbps, or higher Port in one of our global [data centers/Points of Presence](https://www.megaport.com/megaport-enabled-locations/). If your company is not located in one of our PoPs, you can procure a last mile circuit to one of the sites to connect to Megaport. [Contact Megaport](https://www.megaport.com/contact/) for more information.
If you require a Port in a different location to physically separate this solution from other existing traffic traversing your Ports, we recommend that you [create a new one](/connections/creating-port) before proceeding.
This image shows a high level topology diagram of a solution integrating Megaport with Snowflake Data Warehousing on AWS using a single connection.
## Setting up your Snowflake environment
To set up your Snowflake environment, you will:
* Log in to Snowflake
* Create Snowflake objects
* Stage the data files
* Copy data into the target table
* Query the loaded data
For more information about setting up Snowflake in an AWS environment, see [Snowflake Prerequisites](https://docs.snowflake.com/en/user-guide/getting-started-tutorial-prerequisites.html).
To ensure that data transfer between your Snowflake solution and your VPC remains secure, you can use AWS PrivateLink to connect the two environments. PrivateLink is an AWS service that lets you implement direct and secure connectivity between AWS VPCs. This allows your data to stay within the AWS infrastructure without being exposed to the internet which reduces some of the security risks related to having data traversing the internet.
Enabling AWS PrivateLink can take up to 2 business days. For more information about enabling AWS PrivateLink for your Snowflake on AWS solution, see [AWS PrivateLink & Snowflake](https://docs.snowflake.com/en/user-guide/admin-security-privatelink.html).
## Integrating Megaport with Snowflake Data Warehousing on AWS
You can use the Megaport Portal to create the VXC to the Snowflake on AWS environment.
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.\
If you haven't already created a Port, see [Creating a Port](/connections/creating-port).
2. Add an AWS connection for the Port.\
If this is the first connection for the Port, click the AWS tile. The tile is a shortcut to the configuration page. Alternatively, click **+Connection**, click **Cloud**, then click **AWS**.
3. For AWS Connection Type, click **Hosted VIF** or **Hosted Connection** and click **Next**.\
For this example, we will click **Hosted Connection**.
4. Next, you will create a new VXC. In the Select Destination Port list, select the AWS region and the interconnection point for your connection, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection. You can also filter by diversity zone.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection. You must choose from the provided bandwidth options (50 Mbps to several Gbps for Hosted VIF, or up to 25 Gbps for a Hosted Connection). Higher speeds might be available depending on region and capabilities. The sum of all hosted virtual VXCs to a service can exceed the Port capacity (for example, 10 Gbps, 100 Gbps, or higher), however the total aggregate will never burst beyond the Port capacity.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This VLAN ID must be a unique ID on this Port and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged** to remove the VLAN tagging for this connection. The untagged option limits you to only one VXC deployed on this Port.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.
7. Specify the cloud details:
* **AWS Connection Name** -- This is a text field and will be the name of your virtual interface that appears in the AWS console. For easy mapping, use the same name for this field as you did for the VXC name on the previous screen.
* **AWS Account ID** -- This is the ID of the account you want to connect. You can find this value in the Account Settings section of your AWS console.
8. Click **Next**.
9. Review the connection details and click **Add VXC**.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
Your work in the Megaport Portal is complete. Next, you will connect the new VXC to your AWS environment.
13. In approximately 2 minutes, log in to your AWS account.
The VXC you implemented will appear in your Direct Connect under Connections.
14. Click **Create connection**.\
You will then need to connect to a Direct Connect Gateway. For more information about connecting to various types of gateways, see [Working with Direct Connect gateways - AWS Direct Connect](https://docs.aws.amazon.com/directconnect/latest/UserGuide/direct-connect-gateways.html).
### Redundancy
To achieve redundancy for the connectivity portion of this solution, establish an additional VXC to a diverse edge router within the AWS environment. Follow the [Integrating Megaport with Snowflake Data Warehousing on AWS](#integrating) procedure from step 3, and choose the alternate Diversity Zone (identified by the blue circle icon) when choosing the AWS region.
The Diversity Zones identified in the Megaport Portal only refer to AWS edge router locations, and not to the Availability Zones within the AWS infrastructure.
Complete the procedure, including the required steps within the AWS console.
This image shows a high-level topology diagram of a solution integrating Megaport with diverse connections into the Snowflake Data Warehousing on AWS infrastructure.
For additional physical redundancy for the connectivity, you can implement the VXCs on separate Ports:
## Background information
Snowflake is a data warehouse service that is purpose-built for the cloud. The infrastructure is built within the AWS cloud and allows for fast and simple implementation and integration with your AWS VPC environment and on-premises infrastructure. In a Snowflake on AWS environment, you can take advantage of benefits such as elasticity and scalability while only paying for the resources that you use. It provides metadata management, security of data, and an ANSI compliant engine on a resilient and redundant platform that allows you to store, query, and analyze all of your data in one place. Snowflake is available within the AWS Marketplace; it competes with services that are offered directly by AWS, but can offer more functionality at lower costs. We recommend that you review available options to determine which is best for your business requirements.
For more information about Snowflake, see these additional links:
* [The Modern Cloud Data Platform Built for Any Cloud](https://www.snowflake.com/product/)
* [AWS PrivateLink for Snowflake: No Internet Required](https://www.snowflake.com/blog/privatelink-for-snowflake-no-internet-required/?did=pa_card\&trk=pa_card)
* [AWS Marketplace: Snowflake On Demand - Premier](https://aws.amazon.com/marketplace/seller-profile?id=18d60ae8-2c99-4881-a31a-e74770d70347)
* [Data Warehouse Architecture](https://www.snowflake.com/product/architecture/)
# Megaport Cloud Connectivity Overview
Source: https://docs.megaport.com/cloud/megaport/index
This help topic provides an overview of Megaport cloud connectivity.
The Megaport network lets you connect directly and securely to worldwide cloud regions enabling you to distribute workloads and run the applications from the optimal location. The Megaport global, carrier-grade network is directly connected to the networks of our cloud partners, otherwise commonly referred to as a (network-to-network interface) connection.
With the Megaport network, you can achieve a seamless end-to-end solution to connect directly to major cloud providers, such as Alibaba Cloud, Amazon Web Service (AWS), Google Cloud Platform, IBM Cloud, Microsoft Azure, Oracle Cloud Infrastructure, Salesforce Express Connect, and SAP HANA Enterprise Cloud.
Benefits include:
* ** ecosystem** -- Provision direct connectivity to multiple leading cloud and network providers on our ecosystem.
* **Multiple cloud regions** -- Connect to multiple cloud regions from a single interconnection point for cost-effective multi-region redundancy.
* **Cloud-to-cloud connectivity** -- Establish seamless connectivity between regions and Cloud Service Providers (CSPs) without the need to own and manage physical infrastructure or bring multiple connections back to a data center.
To get started, select a service (Port, MCR, or MVE) and a CSP topic from the side navigation.
# Diversity in Azure Connections
Source: https://docs.megaport.com/cloud/megaport/microsoft/azure-diversity
This help topic describes how to identify and create diverse connections in Microsoft Azure.
Diverse connections improve the robustness of your network by using different physical infrastructure to provide network services. Diverse connections build in redundancy and eliminate single points of failure. A redundant connectivity configuration is a requirement for the Azure Service Level Agreement (SLA) to be valid.
For more information, see [Site Resiliency for ExpressRoute](https://learn.microsoft.com/en-us/azure/expressroute/design-architecture-for-resiliency#site-resiliency-for-expressroute).
## ExpressRoute resiliency
High Availability, or Resiliency, has three levels in :
* **Maximum** -- Structured to eliminate any single point of failure within the network path.
* **High** -- Offers site diversity by splitting a single circuit connections across two sites.
* **Standard** -- A single circuit with two connections configured at a single site with built-in redundancy.
For more information about the Microsoft SLA associated with each of the ExpressRoute resiliency solutions, see [Service Level Agreements for Online Services](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services?lang=1).
## Maximum resiliency
Maximum resiliency provides a network that eliminates a single point of failure within the network path. When you construct a maximum resiliency architecture on ExpressRoute using Megaport, you will create one Port at each of four Megaport-enabled data centers. You will use a VXC to connect each Port to an MSEE in a peering location. Two peering locations are used in the maximum resiliency architecture, with two MSEEs in each.\
Maximum resiliency is recommended for business with mission-critical workloads.
Due to the intent of this architecture, we recommend that four Megaport Ports are used for improved resiliency, but this is not required.\
You can deploy the ExpressRoute circuits from a single Megaport Port, or dual Ports. If you deploy dual Megaport Ports in a single data center, create each in a different diversity zone. For more information about Megaport Diversity zones, see [Port Diversity](/connections/port-diversity).
## High resiliency
High resiliency provides an ExpressRoute network that routes through multiple sites in a metropolitan area. This is called ExpressRoute Metro.
When you use ExpressRoute Metro with Megaport, you will create one or two Megaport Ports and use VXCs to connect to MSEEs in two data centers in a Metro area. Microsoft designates which data centers in a metropolitan peering locations are configured for ExpressRoute Metro. You will use a VXC to connect each Port to an MSEE in each metro peering location. Two peering locations are used within the same metropolitan area, with two MSEEs in each.\
The peering locations used will be at less than 5km or 3.2 miles apart.
High resiliency is recommended for business and mission-critical workloads within a metropolitan area.
## Standard resiliency
Standard resiliency uses a single circuit with two connections configured at a single site. Device redundancy (Active-Active) is configured to facilitate failover across the two connections of the circuit.\
When you configure standard resiliency with Megaport, you create two Megaport Ports and use two VXCs to connect to dual MSEEs in an ExpressRoute peering location.
You can use just one Megaport Port, but we recommend that you use two Ports.
You must use VXC diversity when provisioning the connections. For more information, see [Creating a VXC](/connections/overview#create_vxc).
## Helpful references
* [Azure Paired Regions - HA Design](/cloud/megaport/microsoft/azure-ha-design)
* [Azure ExpressRoute - Redundancy](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-introduction#redundancy)
# Azure Paired Regions - HA Design
Source: https://docs.megaport.com/cloud/megaport/microsoft/azure-ha-design
This help topic describes the requirements for creating diverse paths into an Azure region through Megaport.
When using Azure ExpressRoute to transport production Azure workloads, the recommended configuration uses ExpressRoute circuits in both Azure regions in an Azure region pair using ExpressRoute on-ramps at each region. The Megaport solution connecting the customer's network could be a single Port, a pair of physical Port connections (either discrete or in a LAG/LACP bundle) in a single data center, or a pair of physical Port connections diversified across multiple data center locations.
## Creating diverse paths in an Azure paired region
These are the components required for creating diverse paths into an Azure paired region through Megaport in different data center locations:
#### Microsoft Azure
* ExpressRoute Circuit in region 1 of the region pair
* ExpressRoute Circuit in region 2 of the region pair
* Virtual Network Gateway in region 1 attached to Virtual Network (vNet)
* Virtual Network Gateway in region 2 attached to Virtual Network (vNet)
#### Megaport
* 1 (or 2 in a Link Aggregation/LAG configuration) Port in a Megaport-enabled location
* 1 (or 2 in a LAG configuration) Port in a Megaport-enabled location
* 4 VXCs with each connecting to different Azure on-ramp locations
See Microsoft FAQ entries on multiple ExpressRoute circuits connecting a vNet at same (or different) peering location:
* [Can I have multiple ExpressRoute circuits in the same metro?](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-faqs#can-i-have-multiple-expressroute-circuits-in-the-same-metro-can-i-link-them-to-the-same-virtual-network)
* [Can I have one virtual network connected to more than one ExpressRoute circuit?](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-faqs#can-i-have-one-virtual-network-connected-to-more-than-one-expressroute-circuit)
* [Can I have ExpressRoute circuits from different service providers?](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-faqs#can-i-have-expressroute-circuits-from-different-service-providers)
## Helpful references
* [Microsoft ExpressRoute HA FAQ](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-faqs#how-do-i-ensure-high-availability-on-a-virtual-network-connected-to-expressroute)
* [Business continuity and disaster recovery (BCDR): Azure Paired Regions](https://docs.microsoft.com/en-us/azure/best-practices-availability-paired-regions)
* [SLA for Azure ExpressRoute](https://azure.microsoft.com/en-us/support/legal/sla/expressroute/v1_3/)
# Configuring a Microsoft Azure ExpressRoute Direct Connection
Source: https://docs.megaport.com/cloud/megaport/microsoft/expressroute-direct
This help topic describes how to create a direct connection between Megaport and Microsoft Azure ExpressRoute.
Megaport offers two types of connection to : you can order virtual cross-connections to the Microsoft Cloud through Megaport or you can connect directly to the Microsoft Cloud through point-to-point Ethernet links (ExpressRoute Direct).
Connecting through a VXC is described in [Connecting to Microsoft Azure ExpressRoute](/cloud/megaport/microsoft).
This topic describes ExpressRoute Direct.
With ExpressRoute Direct through Megaport, you can take advantage of the functionality of ExpressRoute and connect directly to the global Microsoft backbone.
Key features of ExpressRoute Direct through Megaport include:
* High-capacity dual connectivity options (including 10 Gbps and higher), supporting Active/Active connectivity at scale
* Data Ingestion into services like Storage and Cosmos DB
* Physical isolation for industries that require dedicated and isolated connectivity
* Granular control of circuit distribution
* Dedicated capacity on the Microsoft network
With ExpressRoute Direct, you provision an ExpressRoute port in the Azure console and work with Megaport to set up a physical cross connect from the ExpressRoute port to a Port at the same data center.
You extend your deployment by using a private VXC and you can connect the Port in the Azure-enabled data center to a second Port in a different data center.
Through Megaport, you can connect with ExpressRoute physical port pairs in a range of capacities (10 Gbps and higher, where available). Circuits support multiple virtual connections with configurable bandwidth options to meet enterprise needs.
For complete technical requirements, port details, and SLAs, see the Microsoft topic [About ExpressRoute Direct](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-erdirect-about).
**To create an ExpressRoute Direct connection**
1. Provision a ExpressRoute port in the Azure console and designate Megaport as the vendor.
2. Download an LOA from Azure.
3. Provision a Port in the same data center as the ExpressRoute port.
4. Contact your Megaport Account Manager to set up a physical cross connect from the ExpressRoute port to the Port.
5. Configure a private VXC to connect the Port attached to the
ExpressRoute port to a second Port in a different data center.
This connection is not set up exclusively through the Megaport Portal, but instead requires direct coordination with your Megaport Account Manager.
## Helpful references
* [About ExpressRoute Direct](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-erdirect-about)
* [Configure ExpressRoute Direct](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-erdirect)
# Configuring a Microsoft Azure ExpressRoute Metro Connection
Source: https://docs.megaport.com/cloud/megaport/microsoft/expressroute-metro
This help topic describes how to create a direct connection between Megaport and Microsoft Azure ExpressRoute Metro
Microsoft solutions can be deployed in different architectures, to meet a range of resiliency requirements. For more information about the ExpressRoute standard, high and maximum resiliency options supported by Microsoft and Megaport, see [Diversity in Azure Connections](/cloud/megaport/microsoft/azure-diversity).
The ExpressRoute Metro solution is categorized by Microsoft as the [High resiliency](https://learn.microsoft.com/en-us/azure/expressroute/design-architecture-for-resiliency#high-resiliency) option. It allows you to create a low-latency geo-diverse access solution in defined metropolitan locations, using private connections between your on-premises networks and Azure workloads in designated ExpressRoute data center peering locations. Using this option, ExpressRoute Metro provides multi-site redundancy. Using Megaport, you can create connections to redundant ExpressRoute ports in two distinct ExpressRoute Metro peering locations within a city.
ExpressRoute Metro data center pairs are pre-determined by Microsoft in a given metropolitan area. For example, the ExpressRoute Metro offering in Amsterdam consists of two specified data center locations (Equinix and Digital Realty). When the ExpressRoute service key is generated in your Azure console, it is enabling ExpressRoute circuits for these two pre-defined and designated data center locations in that metro.
## ExpressRoute Metro locations
ExpressRoute Metro locations are being created all the time. See [ExpressRoute Metro Locations](https://learn.microsoft.com/en-us/azure/expressroute/metro#expressroute-metro-locations) for current locations.
## Configuring an ExpressRoute Metro connection with Megaport
This section describes how to set up your ExpressRoute Metro connection with Megaport. You will need access to the Azure console and the Megaport Portal.
This overview is specific to the configuration and deployment of ExpressRoute Metro using a Megaport Port. You can also create an ExpressRoute Metro solution using Megaport Cloud Router (MCR) and Megaport Virtual Edge (MVE).
### Creating an ExpressRoute Metro connection
To create an ExpressRoute Metro connection, you will need to generate a ExpressRoute Metro service key in your Azure console. You then have to provision at least one Port in your chosen Megaport-enabled data center. From here, you will create VXC connections to the Microsoft ExpressRoute Microsoft Enterprise Edge (MSEE) devices installed in the ExpressRoute Metro locations.
ExpressRoute Metro pairs will typically follow the same naming convention established by Microsoft by metro. In Amsterdam, the ExpressRoute Metro pair names are Amsterdam and Amsterdam2. Similarly in Singapore, ExpressRoute Metro site names are Singapore and Singapore2. This naming convention will be consistent as new Metro support is established globally.\
For complete technical requirements, port details, and SLAs, see the Microsoft topic [About ExpressRoute Metro](https://learn.microsoft.com/en-us/azure/expressroute/metro#expressroute-metro).
**To create an ExpressRoute Metro connection**
1. Provision an ExpressRoute Metro circuit in the Azure console and designate Megaport as the vendor.\
For more information, see [Configure ExpressRoute Metro](https://learn.microsoft.com/en-us/azure/expressroute/metro#configure-expressroute-metro).
2. Copy the ExpressRoute Metro service key.
3. In the Megaport Portal, create a Port in a Megaport-enabled data center.
4. Create a VXC connection to the MSEE port in the ExpressRoute Metro Primary data center using the ExpressRoute Metro service key.\
The Megaport Portal will validate the service key and present the ExpressRoute options for VXC termination.
5. If required, create a second Port in a Megaport-enabled data center. It can be the same data center as the first Port, or a different data center, depending on your architecture and requirements.
6. Create a second VXC connection to the MSEE port in the ExpressRoute Metro Secondary data center using the ExpressRoute Metro service key. The VXC can originate from either the original Port created above, or the second Port if it has been created.
We recommend that dual Megaport Ports are used for improved resiliency but this is not required. You can deploy ExpressRoute Metro from a single Megaport Port or dual Ports.\
When deploying from dual Megaport Ports, deploy each in a different diversity zone. For more information about diversity zones, see [Port Diversity](/connections/port-diversity).
### Creating the Megaport Ports
For a single Megaport Port solution, you will create two VXCs from the same Port. Each VXC will be provisioned to two different B-End ExpressRoute Metro data center locations.
With a dual Port solution, you will create one VXC from each Port to the B-End ExpressRoute Metro data center locations.
With one Port, you will create two VXCs from the same Port. Each VXC will be provisioned to one of the two different B-End ExpressRoute Metro data center locations in a diverse manner from each other.
For more information about how to create a Port, see [Creating a Port](/connections/creating-port).
## Creating an ExpressRoute connection
For ExpressRoute Metro, you must create two VXCs from your Megaport Port or Ports to connect to the MSEE at each of the ExpressRoute Metro locations. To do this, you will need the ExpressRoute Metro service key.\
For more information about how to create a VXC, see [Creating a VXC](/connections/overview#create_vxc).
## Helpful references
* [About ExpressRoute Metro](https://learn.microsoft.com/en-us/azure/expressroute/metro#expressroute-metro)
* [Configure ExpressRoute Metro](https://learn.microsoft.com/en-us/azure/expressroute/metro#configure-expressroute-metro)
# Connecting to Microsoft Azure ExpressRoute
Source: https://docs.megaport.com/cloud/megaport/microsoft/index
This help topic describes how to create a connection between Megaport and Microsoft Azure ExpressRoute.
Megaport makes it easy to provision fast, secure, and private connections between your data center and Microsoft Azure and provides dedicated access to Azure private and Microsoft public resources from hundreds of locations worldwide.
## Azure ExpressRoute connection overview
Megaport offers two types of connection to . You can order virtual cross-connections to the Microsoft Cloud through Megaport or you can connect directly to the Microsoft Cloud through point-to-point Ethernet links (ExpressRoute Direct).
This topic describes connecting to Azure through a VXC. For more information about a direct connection, see [Configuring a Microsoft Azure ExpressRoute Direct Connection](/cloud/megaport/microsoft/expressroute-direct).
When connecting to the Microsoft Cloud (Azure) through an ExpressRoute with Megaport, the VXC forms the Layer 2 component of the connection and Layer 3 BGP connectivity is established directly between the customer
and Azure.
There are two elements involved with an ExpressRoute connection. The first is your
[ExpressRoute plan](https://azure.microsoft.com/en-au/pricing/details/expressroute/)
and is billed directly from Microsoft. (Make sure to select the correct
region and currency for accurate pricing). The second is the VXC with
Megaport to connect to your ExpressRoute location.
To check the latency and price of connecting to a particular Azure Partner location, start the procedure to [add a connection to Microsoft Azure](#azure-vxc) but instead of providing a **Microsoft Azure Service Key**, click **View all Azure Partner locations**. You can proceed to the Connection Details page without a service key and review the pricing of the selected port. To place an order for a Microsoft Azure connection, you need to provide a service key.
Each ExpressRoute subscription includes two Virtual Ports on the Microsoft Cloud side. Microsoft offers an SLA on its ExpressRoute connectivity, but to comply you must deploy ExpressRoute VXCs to each Microsoft virtual port for redundancy.
Megaport supports ExpressRoute access to both peering interfaces: Azure
Private and Microsoft (Public) peering. Azure Private does not require
approval and is available instantly, but Microsoft (Public) peering
requires manual validation of public IP space by Microsoft, and some
public endpoints (such as Office 365) require additional validation.
Both of these peering interfaces are delivered through a single VXC
using 802.1ad configuration. When provisioning an ExpressRoute circuit, you can connect multiple VNETs to a single circuit (up to 10 by default, but more are possible depending on your plan).
This image shows a typical ExpressRoute deployment.
The VXC connecting to Microsoft contains two "inner" VLANs. These
are referred to as the C-Tagged VLANs and are configured in the Azure
console. The "outer" VLAN tag is called the S-Tag and is the VLAN
assigned to the VXC in the Megaport Portal.
## ExpressRoute Metro
Megaport supports ExpressRoute Metro. ExpressRoute Metro is the [high resiliency](/cloud/megaport/microsoft/azure-diversity) version of ExpressRoute. It provides a low-latency geo-diverse access solution in defined metropolitan locations, using private connections between your on-premises networks and Azure workloads in designated ExpressRoute data center peering locations. For more information about creating an ExpressRoute Metro connection using Megaport, see [ExpressRoute Metro](/cloud/megaport/microsoft/expressroute-metro).
## Creating an ExpressRoute connection
To deploy an ExpressRoute connection, you need to choose your ExpressRoute plan
and deploy the ExpressRoute circuit in the Azure Portal. When deployed, you get a service key. Copy the service key and log in to the Megaport Portal.
**To create a connection to ExpressRoute**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.
If you haven't already created a Port, see [Creating a Port](/connections/creating-port).
2. Add a VXC connection for the Port.\
Click **+Connection**, click **Cloud**, then click **Microsoft Azure**.
3. Add the ExpressRoute service key into the **Microsoft Azure Service Key** field.
The Portal verifies the key then displays the available port locations based on the Peering Location chosen when creating the ExpressRoute in the Azure Portal. For example, if your ExpressRoute service is deployed in Peering Location Sydney, you can only select the Sydney locations.
If you are creating a VXC for ExpressRoute Metro, the Ports available in your chosen metro will be shown. You will have to create a VXC for each Port.
4. Select the connection point for your first connection.
Some helpful resource links appear on the configuration screen, including the Azure Resource Manager console and links to tutorial videos.
5. Click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. It is auto-populated from the configuration in the Azure console.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** -- By default Q-in-Q is enabled. Specify an unused VLAN ID for this connection (for ExpressRoute this is the S-Tag for your data center). This must be a unique VLAN ID for this connection and can range from 2 to 4093. Enabling Q-in-Q has the benefit of deploying both Microsoft and private peering and both primary and secondary Azure ExpressRoute circuits but your routing and switching hardware must support Q-in-Q to be capable of terminating dual tags at the customer end.
For clarity, your on-premises device is configured with the inner (C-Tag) and outer (S-Tag) tags. A corresponding outer tag is configured in the Megaport Portal as described above. The inner tag is provisioned in the Microsoft Azure Portal under the ExpressRoute peering VLAN ID.
You must use untagged VLANs if you are creating a MACsec connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next**.
8. To deploy a second connection (and this is recommended), repeat these steps, reusing the service key. Adding a second connection ensures that you receive the Azure ExpressRoute SLA. Azure does not provide an SLA for a single connection.
9. Click **Next**.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
## Connecting to ExpressRoute on equipment that does not support Q-in-Q
Q-in-Q is a technology that not all organizations use. If your equipment does not support Q-in-Q, this section describes your options.
### Configure single Azure peering VLAN
You can configure the VXC with a single tag VLAN solution. You configure peering in Azure with the Port VLAN (A-End) and the peer VLAN (B-End). Note that you can have only one peering type (private or Microsoft) per VXC with single Azure peering VLAN, so you need at least two VXCs to use both peering types.
We recommend using single Azure peering VLAN. This option provides full functionality and the simplest implementation. With single Azure peering VLAN, you can use both private and Microsoft peering with a single ExpressRoute circuit without the need for Q-in-Q capable equipment, an MCR, or an untagged port.
You can reuse an Azure service key multiple times to provision the primary and secondary VXCs and both peerings.
For example, if your environment does not support Q-in-Q but you want to use both private and Microsoft peering, you can provision 4 VXCs with single Azure peering VLAN:
* VXC 1 - The primary private peering with B-End VLAN 100.
* VXC 2 - The secondary private peering with B-End VLAN 100.
* VXC 3 - The primary Microsoft peering with B-End VLAN 200, reusing the primary option.
* VXC 4 - The secondary Microsoft peering with B-End VLAN 200, reusing the secondary option.
### Other options for connecting to ExpressRoute on equipment that does not support Q-in-Q
* You can remove the Q-in-Q requirement by dedicating a Port to Microsoft Azure by untagging the connection (selecting **Untagged** for the preferred A-End VLAN). Megaport will still correctly apply or strip the outer VLAN S-Tag depending on the traffic direction. This means you can only deploy a single VXC on this Port, so it does not scale well and you will not receive the Azure SLA. However, an untagged connection can be useful as a temporary solution.
* Deploy a Megaport Cloud Router (MCR) to take care of Q-in-Q for you.
For more information about Q-in-Q, see [Configuring Q-in-Q](/connections/q-in-q).
## Enabling the single Azure peering VLAN
By enabling Azure peering VLAN, you can specify a single Azure peering VLAN that will match with the value that you configure (in step 8) for the selected peering type configuration for the Azure ExpressRoute configuration (via the Microsoft Azure Portal).
**To enable the single Azure peering VLAN**
1. Follow steps 1 through 5 in the procedure [To create a connection to ExpressRoute](#ERconnect).
2. Under Azure peering VLAN, enable the Configure single Azure peering VLAN option.
3. Enter the peering VLAN tag for the ExpressRoute peering required, from 2 to 4093.
Megaport uses this to set a peering VLAN tag that maps directly back to the ExpressRoute peering VLAN ID on the B-End. The tag must be a valid ExpressRoute VLAN ID, and it must match the VLAN ID of the Azure B-End of the VXC to configure the correct pairing.
4. Click **Next**.\
A summary page appears that includes the monthly cost.
5. Click **Back** to make changes or click **Add VXC**.
6. To deploy a second connection (and this is recommended), create a second VXC. Enter the same service key, select the other connection target, and enter the same Peering VLAN ID for the ExpressRoute peering configured in step 3.
7. Click **Next** and proceed through the ordering process.
8. Configure the peer in the Azure Portal, matching the C-Tag VLAN ID to the single Azure peering VLAN tag entered in the Megaport Portal.
This image shows where the VLAN C-Tag is configured in the Azure Portal.
9. Configure your on-premises equipment.
**To change an existing single Azure peering VLAN**
1. On the Services page, click the gear icon next to the connection in the Megaport Portal.
2. Change the single Azure peering VLAN ID.
3. Click **Save**.
4. Click **Next**.
5. Configure the peer in the Azure Portal, matching the C-Tag VLAN ID to the single Azure peering VLAN tag entered in the Megaport Portal.
**To verify the single Azure peering VLAN**
* On the Services page, click the gear icon next to the connection in the Megaport Portal.\
The Connection Details page shows the single Azure peering VLAN value.
## Converting an untagged VXC to a tagged VXC
An existing Azure service on an untagged VXC can now be tagged, allowing you to instantly order additional services on the existing Port without adding any more physical Ports.
Converting an untagged VXC to a tagged VXC will cause a service disruption.
**To convert an existing untagged VXC to a tagged VXC**
1. On the Services page, click the gear icon next to the connection in the Megaport Portal.
2. Select **Tagged**.
3. Enter the Preferred A-End VLAN tag for the customer Megaport-facing VLAN.
4. Enable the Configure single Azure peering VLAN option.
5. Enter the Peering VLAN ID for the ExpressRoute Peering, from 2 to 4093.\
Megaport uses this to set a Peering VLAN tag that maps directly back to the ExpressRoute peering VLAN ID on the B-End. The tag must be a valid Azure ExpressRoute VLAN ID, and it must match the VLAN ID of the Azure B-End of the VXC to configure the correct pairing.
6. Click **Save**.
7. Click **Next**.
8. Configure the peer in the Azure Portal, matching the C-Tag VLAN ID to the single Azure peering VLAN tag entered in the Megaport Portal.
## Deleting an ExpressRoute connection
You might need to delete an ExpressRoute connection from time to time. ExpressRoute connections cannot be removed directly from the Megaport Portal if there is active BGP peering on the Azure side. Therefore, follow these steps to successfully delete an ExpressRoute connection.
**To delete an ExpressRoute connection**
1. Delete the peering on the ExpressRoute connection in the Azure Portal (Private or Microsoft).
2. Delete the VXC in the Megaport Portal.\
For more information, see [Terminating a VXC](/connections/terminating-vxc).
3. Delete the ExpressRoute connection in the Azure Portal.\
This will release the network resources reserved between Megaport and Azure.
## Helpful references
* [Azure Paired Regions - HA Design](/cloud/megaport/microsoft/azure-ha-design)
* [Azure Resource Manager Console](https://portal.azure.com/)
* [Enabling Cloud-Native VPN/Encryption Options Over Dedicated Cloud Connectivity Paths](/encryption/cloud-native-vpn-encryption)
* [Q-in-Q Router Configuration Samples](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-config-samples-routing)
* [What is Azure ExpressRoute?](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-introduction)
# Creating MVE Connections to AWS Direct Connect with Aruba EdgeConnect SD-WAN
Source: https://docs.megaport.com/cloud/mve/aruba/aws/index
This help topic describes how to create a VXC from an MVE to AWS Direct Connect and integrate the connection with Aruba EdgeConnect SD-WAN.
You can create a network connection from an MVE (an Aruba EC-V) to AWS with Virtual Cross Connects (VXCs) and AWS Direct Connect. You can create either a Hosted Connection or a Hosted VIF.
You start the AWS connection through the Megaport Portal, accept the connection in AWS, and create an interface for the EC-V in Aruba Orchestrator.
Aruba provides documentation for their SD-WAN product, including Orchestrator and cloud connections, at the [Aruba Documentation Library](https://arubanetworking.hpe.com/techdocs/sdwan/).
## Before you begin
Before you can create a connection to AWS, you need to satisfy these requirements:
* Create an MVE (Aruba EC-V). For more information, see [Creating an MVE](/mve/aruba/creating).
* In AWS, ensure that you have configured the Direct Connect gateway, AWS gateway, VPCs, and related attachments and associations.
## Creating a connection to AWS from the MVE
With an MVE already created, you can create a connection to AWS. The VXC connection can be one of two AWS models:
* [Hosted Connections](/cloud/mve/aruba/aws/mve-aws-hosted) -- A Hosted Connection can support one private, public, or transit virtual interface. Hosted Connections are dedicated connections and are recommended for production environments.
* [Hosted Virtual Interfaces (Hosted VIFs)](/cloud/mve/aruba/aws/mve-aws-hvif) -- Hosted VIFs can connect to public or private AWS cloud services: a Hosted VIF cannot connect to a transit virtual interface. Hosted VIF connections share bandwidth.
Click the link for your preferred connection type for detailed configuration steps.
Creating a connection from the MVE instance to AWS is very similar to creating a connection from a Port or an MCR. The primary difference is the process with Aruba SD-WAN does not include automatically configure the MVE in Aruba and you need to manually create a LAN interface and define VLANs, IP addresses, MD5 values, and BGP peers in the Aruba Orchestrator console.
# Creating an AWS Hosted Connection for an MVE with Aruba EdgeConnect SD-WAN
Source: https://docs.megaport.com/cloud/mve/aruba/aws/mve-aws-hosted
This help topic describes how to create a Hosted Connection from an MVE to AWS Direct Connect and integrate the connection with Aruba EdgeConnect SD-WAN.
A Hosted Connection can support one private, public, or transit virtual interface. These are dedicated connections and are recommended for production environments.
**To create a connection to an AWS Hosted Connection from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select AWS as the service provider, select Hosted Connection as the AWS Connection Type, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.\
Each destination port has either a blue or red icon to indicate its diversity zone. To achieve diversity, you need to create two connections with each one in a different zone.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection. This value cannot be changed after deployment. The drop-down list displays predefined rate limits available for your MVE, with speeds varying by location and service capabilities.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/aruba/creating-mve-manual#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Specify the connection details for the AWS service.
* **AWS Connection Name** -- This is a text field and will be the name of your virtual interface that appears in the AWS console. The AWS Connection Name is automatically populated with the name specified in a previous step.
* **AWS Account ID** -- This is the ID of the account you want to connect. You can find this value in the management section of your AWS console.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Once the VXC connection is deployed successfully, it appears on the Megaport Portal Services page and is associated with the MVE. Click the VXC title to display the details of this connection. Note that the service status (Layer 2) is up but BGP (Layer 3) will be down because the configuration does not exist yet.
Once deployed in the Megaport Portal, you need to accept the connection in the AWS console and create a Virtual Interface for the connection:
**To accept a Hosted Connection**
1. In AWS, go to **Services > AWS Direct Connect > Connections** and click the connection name.
2. Click **Accept** at the top right of the window.
The state will be pending for a few minutes while AWS deploys the
connection. After it is deployed, the state changes from *ordering* to
*available.*
The connection is now available, however you need to create a VIF to connect to AWS services.
For more information about accepting AWS connections, see the
[AWS documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/accept-hosted-connection.html).
## Creating a virtual interface
Once you have created and accepted a Hosted Connection, create a VIF and attach the Hosted Connection to a gateway.
AWS provides
[detailed instructions](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-vif.html) for creating Public, Private, and Transit interfaces.
**To create and attach a VIF**
1. In the AWS console, click **Create Virtual Interface**.
2. Select the interface type.
The type will vary depending on the type of service you need to access.
* **Private** -- Access resources running into a VPC using their private IP addresses. You can choose to terminate a private virtual interface on a private virtual gateway (to access a single VPC) or to a Direct Connect gateway (and map up to 10 VPCs to the VIF).
* **Public** -- Access all AWS public endpoints, as well as all AWS resources that are reachable by a public IP address.
* **Transit** -- Transport traffic from a Direct Connect gateway to one or more transit gateways.
3. Specify the configuration details:
* **Virtual interface name** -- Enter a name for the virtual interface.
* **Connection** -- The physical connection where you want this virtual interface to be provisioned. The name you provided for the Hosted Connection in the Megaport Portal appears here.
* **Virtual interface owner** -- The account that will own the virtual interface. Select My AWS account.
* **Direct Connect gateway** -- Select the Direct Connect gateway to attach this virtual interface to. A transit VIF is not directly attached to a Transit gateway, but to a Direct Connect gateway.
* **VLAN** -- The VLAN assigned to the virtual interface. Leave this value as is. The VLAN address is populated and appears to be editable; however, you will get an error if you try to change it.
* **BGP ASN** -- Enter the Border Gateway Protocol (BGP) autonomous system number (ASN) for the MVE side of the BGP session.
The following BGP details can be filled out or left blank. When left blank, they are auto-populated by AWS.
You can also choose whether you want the virtual interface to support Jumbo frames. Enable Jumbo MTU to support an Ethernet packet of 8500 bytes.
4. Click **Create virtual interface**.
To view the VIF details and state, navigate to **Services > AWS Direct Connect > Connections > Name of the Megaport-Created-Hosted Connection**.
BGP hasn’t been configured, so the interface state appears as *down*.
Once you accept the connection and create the VIF in AWS, the VXC state changes to *Configured* in the Megaport Portal.
## Adding AWS connection details to Aruba Orchestrator
After you create the connection from your MVE to AWS and set up the connection in the AWS console, you need to configure it in Aruba Orchestrator. This involves adding a LAN interface to the appliance and configuring BGP settings, ASNs, VLANs, and MD5 values.
**To add a LAN interface in Aruba Orchestrator**
1. Collect the connection details from the AWS console.\
Display the details of the Virtual Interface you created in AWS for this Hosted Connection. Note the values for the **BGP ASN**, **BGP Auth Key**, **Your Peer IP**, and **Amazon Peer IP**.
2. Collect the connection details from the Megaport Portal.
To display the details, click the gear icon for the AWS connection from your MVE and click the **Details** view. Note the value for the **A-End VLAN**.
3. Log in to Aruba Orchestrator.
4. Go to Configuration > Networking | Routing | Deployment.
5. Locate the appliance by the hostname and click the Edit (pencil) icon.
6. If you do not have a wan0 LAN side interface: Click **+Add** next to LAN Interfaces and in the Interface drop-down menu, choose wan0.
If you already have a wan0 LAN interface, click **+IP** to add a new configuration.
7. In the **VLAN** field, enter the A-End VLAN for the AWS connection (found in the Megaport Portal in Step 2).
8. (Optional) Select a preconfigured Label or select None.
9. In the **IP/Mask** field, enter the IP address and mask for the MVE side of the AWS connection.
This value is the **Your Peer IP** value from the AWS console from Step 1.
10. For the Next Hop, enter the IP address for the Amazon side of the connection.
This value is the **Amazon Peer IP** value from the AWS console.
11. Specify in and out bandwidth values.
The bandwidth must be equal to or less than the MVE bandwidth limit.
This image shows sample configuration values.
12. Click **Apply**.
13. If prompted, reboot the appliance.
A reboot is required only when adding the first LAN interface, as the system switches the appliance from server mode to router mode.
Once the device is reachable from Orchestrator, you can configure a BGP session.
1. In Orchestrator, go to Configuration > Networking | Routing | BGP.
2. Click the Edit (pencil) icon for the appliance.
3. Move the slider to **Enable BGP**.
4. Provide the autonomous system number (ASN).
This is the BGP ASN (for the MVE), collected in Step 1.
5. In the **Router ID** field, enter the loopback 0 IP specified during the initial acceptance of the appliance or another system IP, as required by your network.
You can use any IP address on the appliance, such as the interface IP on the MVE side of the VXC or the transit IP address.
6. In the BGP Peers section, click **Add** and provide the following information:
* **Peer IP** -- This is the Amazon Peer IP address, collected in Step 1 from the AWS console.
* **Local Interface** -- Choose the associated LAN interface (the interface is in the format *wan0+VLAN*).
* **Peer ASN** -- This is the AWS ASN. By default, this value is 64512.
* **Peer Type** -- Choose Branch.
* **Enable Password** -- If required, select this and then enter and confirm your MD5 password.
7. Click **Add**.
8. Click **Apply**.
It takes several seconds for the configuration to be pushed to the appliance.
Click the refresh icon to update the data from the appliance.
When successful, the Peer State is *Established*:
You can also check the BGP status for the VIF in the AWS console and verify the AWS BGP session is up:
## Validating your AWS connection
You can review connection details, including the connection state, from the CLI with these commands:
* `show interface wan0.` -- Displays configuration details and current status for the appliances.
* `show bgp neighbors` or `show bgp summary` -- Displays configuration details and current status for the BGP neighbors.
**To start a CLI session from Orchestrator**
1. In Orchestrator, use the mouse to hover over the appliance and click the Appliance Menu icon to the right of the appliance name.
2. Choose CLI Session from the menu.
3. Enter **enable** mode to use the recommended CLI commands to display configuration details.
# Creating an AWS Hosted VIF for an MVE with Aruba EdgeConnect SD-WAN
Source: https://docs.megaport.com/cloud/mve/aruba/aws/mve-aws-hvif
This help topic describes how to create a Hosted VIF from an MVE to AWS Direct Connect and integrate the connection with Aruba EdgeConnect SD-WAN.
Hosted VIFs can connect to public or private AWS cloud services: a Hosted VIF cannot connect to a transit virtual interface. These connections share bandwidth.
AWS Hosted Virtual Interfaces (Hosted VIF) do not support diversity zones. To ensure connection diversity for Hosted VIFs, create VXCs to two destination ports in different data centers, instead of two ports in separate diversity zones.
**To create a connection to an AWS Hosted VIF from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select AWS as the service provider, select Hosted VIF as the AWS Connection Type, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
Match this to the AWS Connection Name on the next screen for easy mapping.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Accepted values start at 1 Mbps and scale in 1 Mbps increments. Maximum available speed depends on location and service availability. Note the sum of all hosted virtual VXCs to a service can exceed the MVE capacity, but the total aggregate will never burst beyond the MVE capacity.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/aruba/creating-mve-manual#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Specify the details for the AWS service.
Here are details for each field:
* Select **Public** or **Private**.
* **Private** -- Access private AWS services such as a VPC, EC2
instances, load balancers, RDS DB instances, on private IP address
space.
* **Public** -- Access public AWS services such as Amazon Simple Storage
Service (S3), DynamoDB, CloudFront, and Glacier. You will also receive
[Amazon's global IP
prefixes](https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html)
(approximately 2,000 prefixes).
Public VIFs require manual intervention from Amazon and could take up to 72 hours. For more information, see [Configuring Public AWS Connections with IP Addresses Provided by AWS](/cloud/megaport/aws/aws-public-ip).
* **AWS Connection Name** -- This is a text field and will be the name
of your virtual interface that appears in the AWS console. The AWS
Connection Name is automatically populated with the name specified in a
previous step.
* **AWS Account ID** -- This is the ID of the account you want to
connect. You can find this value in the management section of your
AWS console.
* **Customer ASN** (optional) -- Specify the ASN used for BGP peering sessions on any VXCs connected to the MVE. This value is defined when you configure the MVE and, once defined, it cannot be changed.
* **BGP Auth Key** (optional) -- Specify the BGP key. If you leave this blank, Megaport negotiates a key automatically for you with AWS which will be displayed in the Megaport Portal. The key is not displayed in the AWS console.
The BGP Auth Key is generated during the ordering process when this field is left blank. It will not be displayed on the Summary page when ordering. To see the key, view the Connection Settings after the service has been deployed and is live.
* **Customer IP Address** -- The IP address space (in CIDR format) used on your network for peering. This field is optional for private connections and if left blank, Megaport assigns an address.
* **Amazon IP Address** -- The IP address space in CIDR format
assigned in the AWS VPC network for peering. This field is
optional for private connections and if left blank, Megaport automatically assigns an
address.
* **Prefixes** (optional) -- (visible for Public connections only) Specify IP Prefixes to announce to AWS. Specify the prefixes you will advertise when deploying a Public Direct Connect (RIR-assigned IPv4 addresses only).
Once you configure Prefixes for a Public connection, you cannot change them and the field is grayed out. To change this value, create a support ticket with AWS so they can make this change in a non-impacting way. Or, you can cancel the Hosted VIF and reorder. In both cases, you need to wait for AWS to manually approve the request.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
The AWS VXC appears as a connection for the MVE in the Megaport Portal.
Next, accept the connection in AWS.
#### Accepting the Virtual Interface for Private Connections
A few minutes after ordering a private Hosted VIF VXC, the corresponding inbound VIF request is visible on the AWS Direct Connect > Virtual Interfaces page in the AWS console. (This is specific to the region associated with the target AWS port.) If your VIF doesn't appear after a few minutes, confirm you are viewing the correct region.
**To review and accept the private virtual interface**
1. From the AWS Direct Connect > Virtual Interfaces page, click the ID
of the interface to display the configuration and peering details.
The name and account ID of the VIF should match the values supplied in
the Portal and the BGP ASN should match the Customer ASN configured with
the VXC. The Amazon ASN is the default region's AWS ASN and
not the value specified during the configuration - this is
updated when the virtual interface is accepted and assigned.
2. Click **Accept**.
3. Select the gateway type and then the specific gateway for this new
virtual interface.
4. Click **Accept virtual interface**.
The state of the connection changes from *confirming* to *pending*, and then changes to *available* once BGP is established. Note that sometimes there is a delay in the *available* BGP status appearing on the AWS end, though you can confirm the current state of the Layer 3 link through the Portal view.
#### Accepting the Virtual Interface for Public Connections
Several minutes after ordering a public Hosted VIF VXC, the
corresponding inbound VIF request appears on the **AWS Direct
Connect > Virtual Interfaces** page in the AWS console. (This is specific to the region associated with the target AWS port.)
**To review and accept the public virtual interface**
1. From the AWS Direct Connect > Virtual Interfaces page, click the ID
of the interface to display the configuration and peering details.
2. Review the configuration details and click **Accept**, and when
prompted, click **Confirm**.
The state of the connection changes from *confirming* to *verifying*. At
this point, the connection needs to be verified by Amazon - a process
that can take up to 72 hours. When verified, the state changes to
*available*.
## Adding AWS connection details to Aruba Orchestrator
After you create the connection from your MVE to AWS and set up the connection in the AWS console, you need to configure it in Aruba Orchestrator. This involves adding a LAN interface and configuring BGP settings, ASNs, VLANs, and MD5 values.
**To add a LAN interface in Aruba Orchestrator**
1. Collect the connection details from the Megaport Portal.
To display the details, click the gear icon for the AWS connection from your MVE and click the **Details** view. Note the values for the **A-End VLAN**, **Customer Address** (and **CIDR**), **Amazon Address**, and **Customer ASN**.
2. Log in to Aruba Orchestrator.
3. Go to Configuration > Networking | Deployment.
4. Locate the appliance by the hostname and click the Edit (pencil) icon.
5. If you do not have a wan0 LAN side interface: Click **+Add** next to LAN Interfaces and in the Interface drop-down menu, choose wan0.
If you already have a wan0 LAN interface, click **+IP** to add a new configuration.
6. In the **VLAN** field, enter the A-End VLAN for the AWS connection from the Megaport Portal.
7. (Optional) Select a preconfigured Label or select None.
8. In the **IP/Mask** field, enter the IP address and mask for the MVE side of the AWS connection.
This value is the Customer Address from the AWS connection details in the Portal.
9. For the Next Hop, enter the IP address for the Amazon side of the connection.
10. Specify in and out bandwidth values.
The bandwidth must be equal to or less than the MVE bandwidth limit.
This image shows sample configuration values.
11. Click **Apply**.
12. If prompted, reboot the appliance.
A reboot is required only when adding the first LAN interface, as the system switches the appliance from server mode to router mode.
Once the device is reachable from Orchestrator, you can configure a BGP session.
1. In Orchestrator, go to Configuration > Networking | Routing | BGP.
2. Click the Edit (pencil) icon for the appliance.
3. Move the slider to **Enable BGP**.
4. Provide the autonomous system number (ASN).
This is the Customer ASN (your local MVE), collected in Step 1.
5. In the **Router ID** field, enter a system IP as required by your network design.
You can use any IP address on the MVE, such as the loopback 0 IP specified during the initial acceptance of the appliance, the interface IP on the MVE side of the VXC, or the transit IP address.
6. In the BGP Peers section, click **Add** and provide the following information:
* **Peer IP** -- This is the Amazon IP address, collected in Step 1 from the connection details.
* **Local Interface** -- Choose the associated LAN interface (the interface is in the format *wan0+VLAN*).
* **Peer ASN** -- This is the AWS ASN. By default, this value is 64512.
* **Peer Type** -- Choose Branch.
* **Enable Password** -- If required, select this and then enter and confirm your MD5 password.
7. Click **Add**.
8. Click **Apply**.
It takes several seconds for the configuration to be pushed to the appliance.
Click the refresh icon to update the data from the appliance.
When successful, the Peer State is *Established*:
You can also check the BGP status for the VIF in the AWS console and verify the AWS BGP session is up:
## Validating your AWS connection
You can review connection details, including the connection state, from the CLI with these commands:
* `show interface wan0.` -- Displays configuration details and current status for the appliances.
* `show bgp neighbors` or `show bgp summary` -- Displays configuration details and current status for the BGP neighbors.
**To start a CLI session from Orchestrator**
1. In Orchestrator, use the mouse to hover over the appliance and click the Appliance Menu icon to the right of the appliance name.
2. Choose CLI Session from the menu.
3. Enter **enable** mode to use the recommended CLI commands to display configuration details.
# Creating an Azure Connection for an MVE with Aruba EdgeConnect SD-WAN
Source: https://docs.megaport.com/cloud/mve/aruba/azure/index
This help topic describes how to create a VXC from an MVE to Microsoft Azure ExpressRoute and integrate the connection with Aruba EdgeConnect SD-WAN.
You can create a network connection from an MVE (an Aruba EdgeConnect) to Azure ExpressRoute with Virtual Cross Connects (VXCs). You can create either a private connection or a public (Microsoft) connection.
Before you begin, create an MVE in Aruba Orchestrator. For more information, see [Creating an MVE Integrated with Aruba Overview](/mve/aruba/creating).
There are three parts to adding an ExpressRoute connection to your MVE and Aruba SD-WAN.
1. Set up your ExpressRoute plan and deploy the ExpressRoute circuit in the Azure console. When deployed, you get a service key. For additional details, see the Microsoft [ExpressRoute documentation](https://docs.microsoft.com/en-us/azure/expressroute/).
To check the latency and price of connecting to a particular Azure Partner location, start the procedure to [add a connection to Microsoft Azure](#azure-vxc) but instead of providing a **Microsoft Azure Service Key**, click **View all Azure Partner locations**. You can proceed to the Connection Details page without a service key and review the pricing of the selected port. To place an order for a Microsoft Azure connection, you need to provide a service key.
2. In the Megaport Portal, create a connection (VXC) from your MVE to your ExpressRoute location.
3. In Aruba Orchestrator, add the ExpressRoute connection details to a LAN interface.
The instructions in this topic describe the second and third parts.
MVE for Aruba SD-WAN requires configuration steps in both Orchestrator and the Megaport Portal for all cloud connections.
## Adding the ExpressRoute connection in the Megaport Portal
To set up the ExpressRoute connection, you need to create the connection in the Megaport Portal.
**To create a connection to ExpressRoute from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. Click **+Connection** on the MVE.
3. Click the **Cloud** tile.
4. Select Microsoft Azure as the provider.
5. Add the ExpressRoute service key into the **Microsoft Azure Service Key** field.\
The Portal verifies the key then displays the available port locations based on the ExpressRoute region. For example, if your ExpressRoute service is deployed in the Australia East region in Sydney, you can select the Sydney locations.
6. Select the connection point for your first connection.\
To deploy a second connection (and this is recommended), you can create a second VXC - enter the same service key and select the other connection location.
Some helpful links appear on the configuration screen to resources including the Azure Resource Manager console and some tutorial videos.
7. Click **Next**.
8. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit for the VXC will be capped at the maximum allowable based on the ExpressRoute service key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/aruba/creating-mve-manual#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection (for ExpressRoute this is the S-Tag). This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
* **Configure Single Azure Peering VLAN** -- By default, this option is enabled for MVE and we strongly recommend keeping it enabled with Aruba SD-WAN.\
This option provides a single tag VLAN solution. You configure peering in Azure with the MVE VLAN (A-End) and the peer VLAN set in Azure (B-End). Note, you can have only one peering type (Private or Microsoft) per VXC with this option.
If you do not enable this option, the VXC appears active but it does not recognize traffic.
* **Azure Peering VLAN** -- This value needs to match the A-End VLAN for single tag VLAN peering. A different Azure peering VLAN can also be set, if required.
9. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
When the VXC configuration completes, the VXC icon is green.
In the Azure Resource Management console, the provider status will be `Provisioned`.
When provisioned, you need to configure peerings. You can configure private and Microsoft peering. Click the peer to configure and provide these details:
* **Peer ASN** -- Enter the ASN for the MVE.
* **IPv4 Subnets** -- From each of these subnets, MVE uses the first usable IP address and Microsoft uses the second usable IP for its router.
* **VLAN ID** -- Enter the A-End VLAN from the MVE. (Note, the VLAN ID in the Azure console can be different from the A-End VLAN.)
* **Shared Key** (optional) -- Enter an password for BGP.
## Adding the ExpressRoute connection to Aruba Orchestrator
After you create the connection from your MVE to Azure and set up the connection in the Azure console, you need to configure it in Aruba Orchestrator. This involves creating a LAN interface and configuring BGP settings, ASNs, VLANs, and MD5 values.
**To add the Azure Cloud connection in Aruba Orchestrator**
1. Collect the connection details from the Azure console.\
Note the values for the **Peer ASN**, **Shared Key**, **VLAN ID**, and **IPv4 Primary Subnet**.
2. Collect the connection details from the Megaport Portal.\
Click the gear icon for the Azure connection from your MVE and click the Details view.
Note the value for the **A-End VLAN**.
3. Log in to Aruba Orchestrator.
4. Go to Configuration > Networking | Deployment.
5. Locate the appliance by the hostname and click the Edit (pencil) icon.
6. If you do not have a wan0 LAN side interface: Click **+Add** next to LAN Interfaces and in the Interface drop-down menu, choose wan0.
If you already have a wan0 LAN interface, click **+IP** to add a new configuration.
7. In the **VLAN** field, enter the A-End VLAN for the Azure connection (found in the Megaport Portal in Step 2).
8. Optionally, select a preconfigured Label or select None.
9. In the **IP/Mask** field, enter the IP address and mask for the MVE side of the Azure connection.
This value is available in the Azure console. The IP addresses and CIDR appear in the **IPv4 Primary Subnet** field; MVE uses the first usable IP address and Azure uses the second usable IP for its router. For this field, enter the MVE (first usable) IP address.
10. For the Next Hop, enter the IP address for the Azure side of the connection.
From the **IPv4 Primary Subnet** field in the Azure console, use the second usable IP for the Azure router.
11. Specify in and out bandwidth values.
The bandwidth must be equal to or less than the MVE bandwidth limit.
This image shows sample configuration values (in this example, the Azure interface is added by clicking the **+IP** link).
12. Click Apply.
13. If prompted, reboot the appliance.
A reboot is required only when adding the first LAN interface, as the system switches the appliance from server mode to router mode.
Once the device is reachable from Orchestrator, you can configure a BGP session.
1. In Orchestrator, go to Configuration > Networking | Routing | BGP.
2. Click the Edit (pencil) icon for the appliance.
3. Move the slider to **Enable BGP**.
4. Provide the autonomous system number (ASN).
This is the Peer ASN (for the MVE), collected in Step 1.
5. In the **Router ID** field, enter a system IP as required by your network design.
You can use any IP address on the MVE, such as the loopback 0 IP specified during the initial acceptance of the appliance, the interface IP on the MVE side of the VXC, or the transit IP address.
6. In the BGP Peers section, click **Add** and provide the following information:
* **Peer IP** -- This is the Azure IP address. From the **IPv4 Primary Subnet** field in the Azure console, use the second usable IP for the Azure router.
* **Local Interface** -- Choose the associated LAN interface (the interface is in the format *wan0+VLAN*).
* **Peer ASN** -- Enter the Azure-side ASN of 12076. This is a fixed value, and appears in the connection details on the Azure console.
* **Peer Type** -- Choose Branch.
* **Enable MD5 Password** -- If required, select this and then enter and confirm your MD5 password.
7. Click **Add**.
8. Click **Apply**.
It takes several seconds for the configuration to be pushed to the appliance.
Click the refresh icon to update the data from the appliance.
When successful, the Peer State is *Established*:
You can also check the BGP status for the connection in the Azure console and verify the BGP session is up.
## Validating your Azure connection
You can review connection details, including the connection state, from the CLI with these commands:
* `show interface wan0.` -- Displays configuration details and current status for the appliances.
* `show bgp neighbors` or `show bgp summary` -- Displays configuration details and current status for the BGP neighbors.
**To start a CLI session from Orchestrator**
1. In Orchestrator, use the mouse to hover over the appliance and click the Appliance Menu icon to the right of the appliance name.
2. Choose CLI Session from the menu.
3. Enter **enable** mode to use the recommended CLI commands to display configuration details.
# Creating MVE Connections to AWS Direct Connect with Aviatrix Secure Edge
Source: https://docs.megaport.com/cloud/mve/aviatrix/aws/index
This help topic describes how to create a VXC from an MVE to AWS Direct Connect and integrate the connection with Aviatrix Secure Edge.
You can create a network connection from an MVE (an Aviatrix Secure Edge) to AWS with Virtual Cross Connects (VXCs) and AWS Direct Connect. You can create either a Hosted Connection or a Hosted VIF.
You start the AWS connection through the Megaport Portal, accept the connection in AWS, then create an interface for the Edge in Aviatrix CoPilot.
Aviatrix provides documentation for their product, including CoPilot and cloud connections. For more information, see the [Aviatrix Documentation](https://docs.aviatrix.com/documentation/latest/building-your-network/edge-spoke-workflow-megaport.html#aviatrix-secure-edge-hybrid-cloud-solution-in-megaport-virtual-edge).
## Before you begin
Before you can create a connection to AWS, you need to satisfy these requirements:
* Create an MVE (Aviatrix Secure Edge). For more information, see [Creating an MVE Integrated with Aviatrix](/mve/aviatrix/creating-mve-aviatrix).
* In AWS, ensure that you have configured the Direct Connect gateway, AWS gateway, VPCs, and related attachments and associations.
## Creating a connection to AWS from the MVE
With an MVE already created, you can create a connection to AWS. The VXC connection can be one of two AWS models:
* [Hosted Connections](/cloud/mve/aviatrix/aws/mve-aws-hosted) -- A Hosted Connection can support one private, public, or transit virtual interface. Hosted Connections are dedicated connections and are recommended for production environments.
* [Hosted Virtual Interfaces (Hosted VIFs)](/cloud/mve/aviatrix/aws/mve-aws-hvif) -- Hosted VIFs can connect to public or private AWS cloud services: a Hosted VIF cannot connect to a transit virtual interface. Hosted VIF connections share bandwidth.
Click the link for your preferred connection type for detailed configuration steps.
Creating a connection from the MVE instance to AWS is very similar to creating a connection from a Port or an MCR. The primary difference is the process with Aviatrix Secure Edge does not include automatically configuring the MVE in Aviatrix. You need to configure IP addresses, MD5 values, and BGP peers in the Aviatrix console.
# Creating an AWS Hosted Connection for an MVE with Aviatrix Secure Edge
Source: https://docs.megaport.com/cloud/mve/aviatrix/aws/mve-aws-hosted
This help topic describes how to create a Hosted Connection from an MVE to AWS Direct Connect and integrate the connection with Aviatrix Secure Edge.
A Hosted Connection can support one private, public, or transit virtual interface. These are dedicated connections and are recommended for production environments.
**To create a connection to an AWS Hosted Connection from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select AWS as the service provider, select **Hosted Connection** as the AWS Connection Type, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.\
Each destination port has either a blue or red icon to indicate its diversity zone. To achieve diversity, you need to create two connections with each one in a different zone.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection. This value cannot be changed after deployment. The drop-down list displays predefined rate limits available for your MVE, with speeds varying by location and service capabilities.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/aviatrix/creating-mve-aviatrix#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Specify the connection details for the AWS service.
* **AWS Connection Name** -- This is a text field and will be the name of your virtual interface that appears in the AWS console. The AWS Connection Name is automatically populated with the name specified in a previous step.
* **AWS Account ID** -- This is the ID of the account you want to connect. You can find this value in the management section of your AWS console.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Once the VXC connection is deployed successfully, it appears on the Megaport Portal Services page and is associated with the MVE. Click the VXC title to display the details of this connection. Note that the service status (Layer 2) is up but BGP (Layer 3) will be down because the configuration does not exist yet.
Once deployed in the Megaport Portal, you need to accept the connection in the AWS console and create a Virtual Interface for the connection:
**To accept a Hosted Connection**
1. In AWS, go to **Services > AWS Direct Connect > Connections** then click the connection name.
2. Click **Accept** at the top right of the window.
The state will be pending for a few minutes while AWS deploys the
connection. After it is deployed, the state changes from *ordering* to
*available.*
The connection is now available, however you need to create a VIF to connect to AWS services.
For more information about accepting AWS connections, see the
[AWS documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/accept-hosted-connection.html).
## Creating a virtual interface
Once you have created and accepted a Hosted Connection, create a VIF and attach the Hosted Connection to a gateway.
AWS provides
[detailed instructions](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-vif.html) for creating Public, Private, and Transit interfaces.
**To create and attach a VIF**
1. In the AWS console, click **Create Virtual Interface**.
2. Select the interface type.
The type will vary depending on the type of service you need to access.
* **Private** -- Access resources running into a VPC using their private IP addresses. You can choose to terminate a private virtual interface on a private virtual gateway (to access a single VPC) or to a Direct Connect gateway (and map up to 10 VPCs to the VIF).
* **Public** -- Access all AWS public endpoints, as well as all AWS resources that are reachable by a public IP address.
* **Transit** -- Transport traffic from a Direct Connect gateway to one or more transit gateways.
3. Specify the configuration details:
* **Virtual interface name** -- Enter a name for the virtual interface.
* **Connection** -- The physical connection where you want this virtual interface to be provisioned. The name you provided for the Hosted Connection in the Megaport Portal appears here.
* **Virtual interface owner** -- The account that will own the virtual interface. Select My AWS account.
* **Direct Connect gateway** -- Select the Direct Connect gateway to attach this virtual interface to. A transit VIF is not directly attached to a Transit gateway, but to a Direct Connect gateway.
* **VLAN** -- The VLAN assigned to the virtual interface. Leave this value as is. The VLAN address is populated and appears to be editable; however, you will get an error if you try to change it.
* **BGP ASN** -- Enter the Border Gateway Protocol (BGP) autonomous system number (ASN) for the MVE side of the BGP session.
The following BGP details can be filled out or left blank. When left blank, they are auto-populated by AWS.
You can also choose whether you want the virtual interface to support Jumbo frames. Enable Jumbo MTU to support an Ethernet packet of 8500 bytes.
4. Click **Create virtual interface**.
To view the VIF details and state, navigate to **Services > AWS Direct Connect > Connections > Name of the Megaport-Created-Hosted Connection**.
BGP hasn’t been configured, so the interface state appears as *down*.
Once you accept the connection and create the VIF in AWS, the VXC state changes to *Configured* in the Megaport Portal.
## Adding AWS connection details to Aviatrix
After creating a connection from your MVE to AWS and setting it up in the AWS console, you must configure it in Aviatrix CoPilot. This includes configuring interface IPs, BGP settings, ASNs, and MD5 authentication values.
**Configuring the WAN Interface for BGP**
1. **AWS Connection Details**
Collect the following connection details from AWS:
* BGP ASN
* BGP Auth Key
* Your Peer IP
* Amazon Peer IP
2. **Megaport Connection Details**
Collect the A-End vNIC details associated with the AWS connection from the Megaport Portal. To display the details, click the gear icon for the AWS connection from your MVE then click the **Details** view.
Note the **A-End vNIC** value associated with the AWS connection. Aviatrix orders vNICs in the same order they are created in the Megaport Portal. For example:
* 0: eth0
* 1: eth1
* 2: eth2
Collect the vNIC number associated with the AWS connection, as this number will be used to associate the Aviatrix interface with the same number. For example, vNIC **0** in the Megaport Portal corresponds to **eth0** in Aviatrix.
Ensure all vNICs remain untagged as the Aviatrix MVE does not support VLAN tagging.
3. **Aviatrix CoPilot Configuration**
Log in to Aviatrix and configure the Edge Gateway Interface with the AWS details as follows:
* Turn on BGP.
* For the **Interface CIDR**, enter the **Your Peer IP** from the AWS console.
* For the **Default Gateway IP**, enter your **Amazon Peer IP** from the AWS console.
* For the **Remote ASN**, enter the Amazon side **BGP ASN**.
* For password, enter the MD5 **BGP Auth Key** provided by Amazon.
* For the **Local ASN**, enter your MVE's **BGP ASN**.
* For the interface **VLAN**, specify the **A-End vNIC** value collected from the Megaport Portal.
For more information, see the [Aviatrix Documentation](https://docs.aviatrix.com/documentation/latest/building-your-network/edge-spoke-workflow-megaport.html).
**Validation**
* Use CoPilot's diagnostic tools to review connection details and perform a ping test to check IP connectivity to AWS.
* Verify that BGP is established using BGP diagnostics and relevant BGP CLI commands.
# Creating an AWS Hosted VIF for an MVE with Aviatrix Secure Edge
Source: https://docs.megaport.com/cloud/mve/aviatrix/aws/mve-aws-hvif
This help topic describes how to create a Hosted VIF from an MVE to AWS Direct Connect and integrate the connection with Aviatrix Secure Edge.
Hosted VIFs can connect to public or private AWS cloud services: a Hosted VIF cannot connect to a transit virtual interface. These connections share bandwidth.
AWS Hosted Virtual Interfaces (Hosted VIF) do not support diversity zones. To ensure connection diversity for Hosted VIFs, create VXCs to two destination ports in different data centers, instead of two ports in separate diversity zones.
**To create a connection to an AWS Hosted VIF from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select AWS as the service provider, select **Hosted VIF** as the AWS Connection Type, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
Match this to the AWS Connection Name on the next screen for easy mapping.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Accepted values start at 1 Mbps and scale in 1 Mbps increments. Maximum available speed depends on location and service availability. Note the sum of all hosted virtual VXCs to a service can exceed the MVE capacity, but the total aggregate will never burst beyond the MVE capacity.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/aviatrix/creating-mve-aviatrix#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Specify the details for the AWS service.
Here are details for each field:
* Select **Public** or **Private**.
* **Private** -- Access private AWS services such as a VPC, EC2
instances, load balancers, RDS DB instances, on private IP address
space.
* **Public** -- Access public AWS services such as Amazon Simple Storage
Service (S3), DynamoDB, CloudFront, and Glacier. You will also receive
[Amazon's global IP
prefixes](https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html)
(approximately 2,000 prefixes).
Public VIFs require manual intervention from Amazon and could take up to 72 hours. For more information, see [Configuring Public AWS Connections with IP Addresses Provided by AWS](/cloud/megaport/aws/aws-public-ip).
* **AWS Connection Name** -- This is a text field and will be the name
of your virtual interface that appears in the AWS console. The AWS
Connection Name is automatically populated with the name specified in a
previous step.
* **AWS Account ID** -- This is the ID of the account you want to
connect. You can find this value in the management section of your
AWS console.
* **Customer ASN** (optional) -- Specify the ASN used for BGP peering sessions on any VXCs connected to the MVE. This value is defined when you configure the MVE and, once defined, it cannot be changed.
* **BGP Auth Key** (optional) -- Specify the BGP key. If you leave this blank, Megaport negotiates a key automatically for you with AWS which will be displayed in the Megaport Portal. The key is not displayed in the AWS console.
The BGP Auth Key is generated during the ordering process when this field is left blank. It will not be displayed on the Summary page when ordering. To see the key, view the Connection Settings after the service has been deployed and is live.
* **Customer IP Address** -- The IP address space (in CIDR format) used on your network for peering. This field is optional for private connections and if left blank, Megaport assigns an address.
* **Amazon IP Address** -- The IP address space in CIDR format
assigned in the AWS VPC network for peering. This field is
optional for private connections and if left blank, Megaport automatically assigns an
address.
* **Prefixes** (optional) -- (visible for Public connections only) Specify IP Prefixes to announce to AWS. Specify the prefixes you will advertise when deploying a Public Direct Connect (RIR-assigned IPv4 addresses only).
Once you configure Prefixes for a Public connection, you cannot change them and the field is grayed out. To change this value, create a support ticket with AWS so they can make this change in a non-impacting way. Or, you can cancel the Hosted VIF and reorder. In both cases, you need to wait for AWS to manually approve the request.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
The AWS VXC appears as a connection for the MVE in the Megaport Portal.
Next, accept the connection in AWS.
#### Accepting the Virtual Interface for Private Connections
A few minutes after ordering a private Hosted VIF VXC, the corresponding inbound VIF request is visible on the AWS Direct Connect > Virtual Interfaces page in the AWS console. (This is specific to the region associated with the target AWS port.) If your VIF doesn't appear after a few minutes, confirm you are viewing the correct region.
**To review and accept the private virtual interface**
1. From the AWS Direct Connect > Virtual Interfaces page, click the ID
of the interface to display the configuration and peering details.
The name and account ID of the VIF should match the values supplied in
the Portal and the BGP ASN should match the Customer ASN configured with
the VXC. The Amazon ASN is the default region's AWS ASN and
not the value specified during the configuration - this is
updated when the virtual interface is accepted and assigned.
2. Click **Accept**.
3. Select the gateway type and then the specific gateway for this new
virtual interface.
4. Click **Accept virtual interface**.
The state of the connection changes from *confirming* to *pending*, and then changes to *available* once BGP is established. Note that sometimes there is a delay in the *available* BGP status appearing on the AWS end, though you can confirm the current state of the Layer 3 link through the Portal view.
#### Accepting the Virtual Interface for Public Connections
Several minutes after ordering a public Hosted VIF VXC, the
corresponding inbound VIF request appears on the **AWS Direct
Connect > Virtual Interfaces** page in the AWS console. (This is specific to the region associated with the target AWS port.)
**To review and accept the public virtual interface**
1. From the AWS Direct Connect > Virtual Interfaces page, click the ID
of the interface to display the configuration and peering details.
2. Review the configuration details then click **Accept**, and when
prompted, click **Confirm**.
The state of the connection changes from *confirming* to *verifying*. At
this point, the connection needs to be verified by Amazon - a process
that can take up to 72 hours. When verified, the state changes to
*available*.
## Adding AWS connection details to Aviatrix
After you create the connection from your MVE to AWS and set up the connection in the AWS console, you need to configure it in Aviatrix. This involves configuring an interface and BGP, ASNs, VLANs, and MD5 values.
**To configure an AWS connection between an Aviatrix MVE and AWS**
1. **Megaport Connection Details**
Collect the connection details from the Megaport Portal. To display the details, click the gear icon for the AWS connection from your MVE then click the **Details** view.
Note the values for the **A-End VLAN**, **Customer Address** (and CIDR), **Amazon Address**, and **Customer ASN**.
Aviatrix orders vNICs in the same order they are created in the Megaport Portal. For example:
* 0: eth0
* 1: eth1
* 2: eth2
Collect the vNIC number associated with the AWS connection, as this number will be used to associate the Aviatrix interface with the same number. For example, vNIC **0** in the Megaport Portal corresponds to **eth0** in Aviatrix.
Ensure all vNICs remain untagged as the Aviatrix MVE does not support VLAN tagging.
2. **Aviatrix CoPilot Configuration**
Log in to Aviatrix and configure Aviatrix CoPilot with the details you have copied.
For more information, see the [Aviatrix Documentation](https://docs.aviatrix.com/documentation/latest/building-your-network/edge-spoke-workflow-megaport.html).
**Validation**
* Use CoPilot's diagnostic tools to review connection details and perform a ping test to check IP connectivity to AWS.
* Verify that BGP is established using BGP diagnostics and relevant BGP CLI commands.
# Creating an Azure Connection for an MVE with Aviatrix Secure Edge
Source: https://docs.megaport.com/cloud/mve/aviatrix/azure/index
This help topic describes how to create a VXC from an MVE to Microsoft Azure ExpressRoute and integrate the connection with Aviatrix Secure Edge.
You can create a network connection from an MVE (an Aviatrix Secure Edge) to Azure ExpressRoute with Virtual Cross Connects (VXCs). You can create either a private connection or a public (Microsoft) connection.
Before you begin, create an MVE. For more information, see [Creating an MVE Integrated with Aviatrix](/mve/aviatrix/creating-mve-aviatrix).
There are three parts to adding an ExpressRoute connection to your MVE and Aviatrix Secure Edge.
1. Set up your ExpressRoute plan and deploy the ExpressRoute circuit in the Azure console. When deployed, you get a service key. For additional details, see the Microsoft [ExpressRoute documentation](https://docs.microsoft.com/en-us/azure/expressroute/).
To check the latency and price of connecting to a particular Azure Partner location, start the procedure to [add a connection to Microsoft Azure](#azure-vxc) but instead of providing a **Microsoft Azure Service Key**, click **View all Azure Partner locations**. You can proceed to the Connection Details page without a service key and review the pricing of the selected port. To place an order for a Microsoft Azure connection, you need to provide a service key.
2. In the Megaport Portal, create a connection (VXC) from your MVE to your ExpressRoute location.
3. In Aviatrix CoPilot, configure an interface and Border Gateway Protocol (BGP).
MVE for Aviatrix Secure Edge requires configuration steps in both CoPilot and the Megaport Portal for all cloud connections.
## Adding the ExpressRoute connection in the Megaport Portal
To set up the ExpressRoute connection, you need to create the connection in the Megaport Portal.
**To create a connection to ExpressRoute from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. Click **+Connection** on the MVE.
3. Click the **Cloud** tile.
4. Select Microsoft Azure as the provider.
5. Add the ExpressRoute service key into the **Microsoft Azure Service Key** field.\
The Portal verifies the key then displays the available port
locations based on the ExpressRoute region. For example, if your
ExpressRoute service is deployed in the Australia East region in
Sydney, you can select the Sydney locations.
6. Select the connection point for your first connection.\
To deploy a second connection (and this is recommended), you can create
a second VXC - enter the same service key and select the other
connection location.
Some helpful links appear on the configuration screen to resources
including the Azure Resource Manager console and some tutorial videos.
7. Click **Next**.
8. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit for the VXC will be capped at the maximum allowable based on the ExpressRoute service key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/aviatrix/creating-mve-aviatrix#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection (for ExpressRoute this is the S-Tag). This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
* **Configure Single Azure Peering VLAN** -- By default, this option is enabled for MVE and we strongly recommend keeping it enabled with Aviatrix Secure Edge.\
This option provides a single tag VLAN solution. You configure peering in Azure with the MVE VLAN (A-End) and the peer VLAN set in Azure (B-End). Note, you can have only one peering type (Private or Microsoft) per VXC with this option.
If you do not enable this option, the VXC appears active but it does not recognize traffic.
* **Azure Peering VLAN** -- This value needs to match the A-End VLAN for single tag VLAN peering. A different Azure peering VLAN can also be set, if required.
9. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
When the VXC configuration completes, the VXC icon is green.
In the Azure Resource Management console, the provider status will be *Provisioned*.
When provisioned, you need to configure peerings. You can configure private and Microsoft peering. Click the peer to configure and provide these details:
* **Peer ASN** -- Enter the ASN for the MVE.
* **IPv4 Subnets** -- From each of these subnets, MVE uses the first usable IP address and Microsoft uses the second usable IP for its router.
* **VLAN ID** -- Enter the A-End VLAN from the MVE. (Note, the VLAN ID in the Azure console can be different from the A-End VLAN.)
* **Shared Key** (optional) -- Enter an password for BGP.
## Adding the ExpressRoute connection to Aviatrix
After you create the connection from your MVE to Azure and set up the connection in the Azure console, you need to configure it in Aviatrix. This involves configuring an interface and BGP settings, ASNs, VLANs, and MD5 values.
**To add the Azure Cloud connection in Aviatrix**
1. **Azure Connection Details**
Collect the connection details from the Azure console for the connection you created.
Note the values for the **Peer ASN**, **Shared Key**, **VLAN ID**, and **IPv4 Primary Subnet**.
2. **Megaport Connection Details**
Collect the A-End vNIC details associated with the Azure connection from the Megaport Portal. To display the details, click the gear icon for the Azure connection from your MVE then click the **Details** view.
Note the **A-End vNIC** value associated with the Azure connection. Aviatrix orders vNICs in the same order they are created in the Megaport Portal. For example:
* 0: eth0
* 1: eth1
* 2: eth2
Collect the vNIC number associated with the connection, as this number will be used to associate the Aviatrix interface with the same number. For example, vNIC **0** in the Megaport Portal corresponds to **eth0** in Aviatrix.
Ensure all vNICs remain untagged as the Aviatrix MVE does not support VLAN tagging.
3. **Aviatrix CoPilot Configuration**
Log in to Aviatrix and configure Aviatrix CoPilot with the details you have copied.
For more information, see the [Aviatrix Documentation](https://docs.aviatrix.com/documentation/latest/building-your-network/edge-spoke-workflow-megaport.html).
**Validation**
* Use CoPilot's diagnostic tools to review connection details and perform a ping test to check IP connectivity to Azure.
* Verify that BGP is established using BGP diagnostics and relevant BGP CLI commands.
# Creating MVE Connections to AWS Direct Connect with Cisco SD-WAN
Source: https://docs.megaport.com/cloud/mve/cisco/aws/index
This help topic describes how to create a VXC from an Cisco SD-WAN MVE to AWS Direct Connect.
You can create a network connection from an MVE (a Cisco interconnect gateway) to AWS with Virtual Cross Connects (VXCs) and AWS Direct Connect. You can create either a Hosted Connection or a Hosted VIF. You create the connection through vManage.
Although you can create the AWS connection from the MVE in the Portal, Megaport strongly recommends creating this connection in vManage for seamless integration with your Cisco SD-WAN environment.
Cisco provides documentation for their SD-WAN product integration with Megaport, including cloud connections, in the [Cisco SD-WAN Cloud OnRamp Configuration Guide](https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/cloudonramp/ios-xe-17/cloud-onramp-book-xe/m-cloud-onramp-sdci.html).
## Before you begin
Before you can create a connection to AWS, you need to satisfy these requirements:
* Create an MVE (Cisco interconnect gateway) in vManage. For more information, see [Creating an MVE](/mve/cisco/creating/creating-mve).
* Register your [AWS Account number](https://docs.aws.amazon.com/general/latest/gr/acct-identifiers.html#FindingYourAccountIdentifiers) with vManage. You can add your AWS account to vManage in Configuration > Cloud OnRamp For Multi-Cloud and in the Setup tile click Associate Cloud Account or from Navigation > Cloud > Add | Account.
* In AWS, ensure that you have configured the Direct Connect gateway, AWS gateway, VPCs, and related attachments and associations. With your AWS account linked, these values populate in vManage in the Cloud OnRamp for Multi-Cloud > Host Private Networks page.
* For the VPC, you need a VPC tag and ensure the VPC is Interconnect Enabled. (You will provide the VPC tag when you configure your virtual interface.)\
On the Host Private Networks page, select the VPCs to be tagged for interconnection with the SD-WAN and choose Add Tag from the Tag Actions drop-down menu. Enter a tag name and select the box for **Enable for InterConnect** and click **Add**.
## Creating a connection to AWS
With your AWS account linked and the VPC details, you can create the connection.
**To create an AWS connection**
1. In vManage, go to Configuration > Cloud OnRamp for Multi-Cloud.
2. From the vManage Navigation menu in the upper-right, go to Interconnect > Add | Connectivity.
3. Choose Megaport as your Interconnect Provider.
4. Choose your Interconnect Account.\
This is the Megaport account that is associated with your vManage platform.
5. Choose your Interconnect Gateway.\
Configured interconnect gateways appear in the drop-down menu.
The status for the selected gateway appears in the pane to the right. A fully operational gateway displays a checkmark in a green circle.
6. Click **+Add Connection** and enter details for the connection destination.
Provide these details:
* **Destination Type** -- Choose Cloud.
* **Provider** -- Choose AWS.
* **Connection Name** - Specify a name for the AWS connection that is easily identifiable.
* **Connection Type** - Select one of these options:
* [Hosted Virtual Interfaces (Hosted VIFs)](/cloud/megaport/aws#vif) -- a connection that shares bandwidth and can connect to public or private AWS cloud services.
* [Hosted Connections](/cloud/megaport/aws#hosted) -- a dedicated connection that can support transit gateways. (Recommended for production environments.)
* **AWS Account** -- Select your AWS Account. The menu populates the accounts registered with vManage.
7. Click **Next**.
8. Select your Connection VIF Type.
* **Private** -- Access private AWS services such as a VPC, EC2 instances, load balancers, RDS DB instances, on private IP address space.
* **Public** -- Access public AWS services such as Amazon Simple Storage Service (S3), DynamoDB, CloudFront, and Glacier.
* **Transit** -- (for Hosted Connections only) connect to direct connect gateways and multiple VPCs.
When you select the Connection VIF Type, more options appear.
9. Enter a location.\
This is the AWS on-ramp identified by region. Select a location close to your MVE (Interconnect Gateway) and the AWS region with your data.
10. Specify your bandwidth (in Mbps).\
Hosted VIFs support speeds up to several Gbps. Hosted Connections support speeds up to several Gbps.
11. For Private and Transit VIFs, select your Direct Connect Gateway.\
Available gateways from your registered AWS account appear in the menu. You can also build a new gateway.
12. For Private and Transit VIFs, choose your Settings.
* **Global** -- Use the default template values and an automated process to determine the IP addresses for BGP peers for this connection.
* **Custom** -- Use your own /30 values to assign IP addresses for BGP peering on the interconnect gateway and on the Direct Connect Gateway. You can also specify your source BGP ASN. When you specify an ASN, the value overrides the MVE ASN and the connection uses the specified value for this connection.
13. For Public VIFs, specify these settings.
* **Interconnect IP Address** -- The IP Address space (in CIDR format) you will use on your MVE for peering.
* **Amazon IP Address** -- The IP address space in CIDR format assigned in the AWS VPC network for peering.
* **Prefixes** -- IP Prefixes to announce to AWS. RIR-assigned IPv4 addresses only.
14. Choose a Segment.\
The drop-down menu shows the configured and available VPN segments for this connection.
For more information, see the [Cisco Segmentation Configuration Guide](https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/segmentation/ios-xe-17/segmentation-book-xe/segmentation.html).
15. Specify an attachment.
* Hosted VIF (Private) and Hosted Connection (Private): Select VPC and enter your VPC tag. You can enter up to ten VPG tags for each Direct Connect Gateway.
* Hosted Connection (Transit): Select Transit Gateway. Choose a gateway populated from your AWS account (or create a new gateway) and enter your VPC tag. Add prefixes to advertise from your gateway. Click **Save**.
* Public connections do not have attachments.
16. Click **Next**.\
A summary page appears.
17. Review the details of the configuration.
18. Click **Save**.
vManage switches to TaskView and creates the connection. You can monitor the status in this view.
Creating the connection takes up to 5 minutes. When complete, the message “Successfully Created Interconnect Connectivity” appears.
The AWS connection is fully configured from vManage.
You can edit or delete the AWS connection from vManage. If you delete the MVE, the associated connections are also deleted.
## Validating your AWS connection
You can review connection details, including the connection state, from the Interconnect Connectivity page (available from the Intent Management tile or the Navigation menu).
By clicking the ellipsis (**...**) at the end of the connection row, you can view more detailed information for the connection. (This is also where you can delete the connection.)
You can validate the connection details (the link /30 IP address and BGP ASN) on the AWS side by selecting Virtual Interface and examining the Peerings section.
The VLAN ID in AWS will not match the VLAN ID in vManage as Megaport will map different VLANs on the NNI interconnections.
You can also review the connection details from the Megaport Portal for the AWS connection attached to the MVE.
# Creating an Azure ExpressRoute Connection for an MVE with Cisco SD-WAN
Source: https://docs.megaport.com/cloud/mve/cisco/azure/index
This help topic describes how to create a VXC from a Cisco SD-WAN MVE to Microsoft Azure ExpressRoute.
You can create a network connection from an MVE (a Cisco interconnect gateway) to Azure ExpressRoute with Virtual Cross Connects (VXCs). You can create either a private connection or a public (Microsoft) connection.
Before you begin, create an MVE (Cisco interconnect gateway) in vManage based on the Megaport\_ICGW\_C8000 template. For more information, see [Creating a Cisco SD-WAN MVE in vManage](/mve/cisco/creating/creating-mve).
There are three parts to adding an ExpressRoute connection to your MVE and vManage.
1. Set up your ExpressRoute plan and deploy the ExpressRoute circuit in the Azure console. When deployed, you get a service key. For additional details, see the Microsoft [ExpressRoute documentation](https://docs.microsoft.com/en-us/azure/expressroute/).
To check the latency and price of connecting to a particular Azure Partner location, start the procedure to [add a connection to Microsoft Azure](#azure-vxc) but instead of providing a **Microsoft Azure Service Key**, click **View all Azure Partner locations**. You can proceed to the Connection Details page without a service key and review the pricing of the selected port. To place an order for a Microsoft Azure connection, you need to provide a service key.
2. In the Megaport Portal, create a connection (VXC) from your MVE to your ExpressRoute location.
3. In vManage, create a custom MVE device template and add the details of the ExpressRoute connection.
The instructions in this topic describe the second and third parts.
The initial release of MVE requires configuration steps in both Cisco vManage and the Megaport Portal for Azure cloud connections (as described in this topic). Subsequent updates by Cisco let you configure Azure connections completely in vManage. When possible, we recommend creating Azure connections in vManage for seamless integration with your Cisco SD-WAN environment. Cisco provides instructions for the vManage steps: [Create Interconnects to Microsoft Azure](https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/cloudonramp/ios-xe-17/cloud-onramp-book-xe/m-cloud-onramp-sdci.html#d27774e6312a1635).
## Adding the ExpressRoute connection in the Megaport Portal
To set up the ExpressRoute connection, you need to create the connection in the Megaport Portal.
**To create a connection to ExpressRoute from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. Click **+Connection** on the MVE.
3. Click the **Cloud** tile.
4. Select Microsoft Azure as the provider.
5. Add the ExpressRoute service key into the **Microsoft Azure Service Key** field.\
The Portal verifies the key then displays the available port locations based on the ExpressRoute region. For example, if your ExpressRoute service is deployed in the Australia East region in
Sydney, you can select the Sydney locations.
6. Select the connection point for your first connection.\
To deploy a second connection (and this is recommended), you can create
a second VXC - enter the same service key and select the other
connection location.
Some helpful links appear on the configuration screen to resources including the Azure Resource Manager console and some tutorial videos.
7. Click **Next**.
8. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit for the VXC will be capped at the maximum allowable based on the ExpressRoute service key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/cisco/creating-mve-autonomous#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection (for ExpressRoute this is the S-Tag). This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
* **Configure Single Azure Peering VLAN** -- By default, this option is enabled for MVE.\
This option provides a single tag VLAN solution. You configure peering in Azure with the MVE VLAN (A-End) and the peer VLAN set in Azure (B-End). Note, you can have only one peering type (Private or Microsoft) per VXC with this option. If you want to set up an inner VLAN and Q-n-Q, turn off this option.
* **Azure Peering VLAN** -- This value needs to match the A-End VLAN for single tag VLAN peering. A different Azure peering VLAN can also be set, if required.
9. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
When the VXC configuration completes, the VXC icon is green.
In the Azure Resource Management console, the provider status will be `Provisioned`.
When provisioned, you need to configure peerings. You can configure private and Microsoft peering. Click the peer to configure and provide these details:
* **Peer ASN** -- Enter the ASN for the MVE.
* **IPv4 Subnets** -- From each of these subnets, MVE uses the first usable IP address and Microsoft uses the second usable IP for its router.
* **VLAN ID** -- Enter the second .1Q value configured for the connection in the vManage CLI add-on template.
* **Shared Key** -- This value is not required.
## Adding the ExpressRoute connection to vManage
Follow the steps in each of these sections to create, edit, and attach the vManage templates for an MVE with the connection details.
To set up the connection in vManage, you need a dedicated device template and you need to provide feature templates for device-specific configuration details. You need to create a Service VPN template, a Cisco BGP template, as well as a CLI add-on template.
### Step 1 -- Copy the default device template
You need a dedicated template for the MVE so you can edit the template with the connection details for the VXC. You need a dedicated template because if other devices are attached to the template, the change affects each attached device.
**To create a copy of the device template**
1. In vManage, go to Configure > Templates and select the **Device** tab.
2. Find the Default\_MEGAPORT\_ICGW\_C8000V\_Template\_V01 template and copy it.\
Click the ellipsis (**...**) at the end of the row and choose Copy from the drop-down menu.
3. Enter a name for the template and a description and click **Copy**.\
This name can contain only uppercase and lowercase letters, the digits 0 through 9, hyphens, and underscores. It cannot contain spaces or any other characters.
### Step 2 -- Create a Cisco VPN feature template
You need to create a VPN template so you can specify the VPN ID of the GCP connection. The VPN ID is the same as the corporate network.
**To create a VPN feature template**
1. In vManage, go to Configure > Templates and select the **Feature** tab.
2. Find a template for the C8000v device model and a type of Cisco VPN and copy it.\
Click the ellipsis (**...**) at the end of the row and choose Copy from the drop-down menu.
Instead of copying the template, you can also add a new Cisco VPN template for a C8000v device and populate it with the same values.
3. Enter a name for the template and a description and click **Copy**.
4. Edit the template and add the VPN ID in the Basic Configuration.\
Click the ellipsis (**...**) and choose Edit.\
The VPN ID can be any number 1 -- 511 or 513 -- 65530.
VPN 0 is reserved for Transport VPN and VPN 512 is reserved for Managed VPN. The number is normally identical to the VPN ID assigned for corporate networks to communicate between the corporate network and cloud service.
5. Click **Update**.
### Step 3 -- Create a BGP feature template
You also need a BGP template for the connection peering details.
**To create a Cisco BGP feature template**
1. In the Feature tab of vManage Templates, find a template for the C8000v device model and a type of Cisco BGP and copy it.
Instead of copying the template, you can also add a new Cisco BGP template for a C8000v device and populate it with the same values.
2. Enter a name for the template and a description and click **Copy**.
3. Edit the template (click the ellipsis **...** for the new template and choose Edit) and enter the AS Number for the MVE in the Basic Configuration section.\
This value is device specific.
4. In the Neighbor section, click **+New Neighbor** and specify these values for the cloud side of the connection:
* **Address** -- Specify the peer IP address of the cloud side.
* **Description** -- Enter a meaningful description of the template.
* **Remote AS** -- Enter the AS Number of the cloud side: the AS number of Azure is 12076.
5. Click **Update**.
### Step 4 -- Create a CLI Add-On feature template
You also need an add-on CLI template.
**To create a CLI Add-On feature template:**
1. Find a template for the C8000v device model and a type of CLI Template and copy it.\
The CLI template configures the subinterface for the MVE.
2. Enter a name for the template and a description and click **Copy**.
3. Edit the template (click the ellipsis **...** for the new template and choose Edit) and copy the following lines into the CLI Configuration section.
If you enabled Single Azure Peering VLAN:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
interface GigabitEthernet1. {{interface-tag}}
encapsulation dot1Q {{dot1Q-tag-s-tag-01}}
vrf forwarding 100
ip address {{ip-address-subinterface-01}}
ip mtu 1500
!
```
If you did not enable Single Azure Peering VLAN:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
interface GigabitEthernet1. {{interface-tag}}
encapsulation dot1Q {{dot1Q-tag-s-tag-01}} second-dot1q {{dot1Q-tag-c-tag-01}}
vrf forwarding 100
ip address {{ip-address-subinterface-01}}
ip mtu 1500
!
```
Here's an explanation for each line.
| **CLI Entry** | **Description** |
| - | - |
| interface GigabitEthernet1. \{\{interface-tag-01}} | A description field for the sub interface. |
| encapsulation dot1Q \{\{dot1Q-tag-s-tag-01}} second-dot1q \{\{dot1Q-tag-c-tag-01}} | The first dot1Q is the S-tag. This tag is set as the A-End tag with the VXC in the Megaport Portal. The second dot1Q is the C-tag. This tag is set in the Azure console with the peer. (If you have Single Azure Peering VLAN enabled, you do not need to configure the second dot1Q interface.) |
| vrf forwarding | This is the VPN for your peer. This example defines VPN 100 and adds it to the template. |
| ip address \{\{ip-address-subinterface-01}} | The IP address of the interface - assigned by Microsoft. |
| ip mtu | ExpressRoute supports an MTU value of 1500. |
4. Click **Update**.
### Step 5 -- Update your device template
Next, we need to add the feature templates to the copy of the default device template and then define the values for the added features.
**To add the feature templates to the device template**
1. In the Device tab of vManage Templates,find the copy of the device template that you created in Step 1 and click the ellipsis (**...**) and choose Edit.
2. In the Service VPN tab, click **+Add VPN**.
3. In the Available VPN Templates, highlight the template created in Step 2, click the arrow to move it to the Selected VPN Templates, and click **Next**.\
The select sub-templates step appears.
4. From the Additional Cisco VPN Templates, click **Cisco BGP**.
5. From the Cisco BGP menu, choose the BGP template you created in Step 3 and click **Add**.
6. In the Additional Templates tab, select the CLI Add-On template you created in Step 4 and click **Update**.\
A screen appears that lists the updated device template. You need to edit this template to add values for the new fields and associate an MVE.
7. Click the ellipsis (**...**) and choose Edit.\
The device settings appear with new fields defined in the feature templates.
8. Enter values for these new fields:
* **ip-address-subinterface** -- Specify the IP address of the interface. This is the first IP address from the /30 Primary subnet assigned with the peer in the Azure console.
* **interface-tag** -- This value is the same as dot-1q-s-tag. You can find this value in the VXC connection details on the Megaport Portal: click the gear icon for the VXC, choose Details, and use the A-End VLAN value.
* **dot-1q-s-tag** -- The dot1Q S-tag. This value is the same as interface-tag. You can find this value in the VXC connection details on the Megaport Portal: click the VXC name, choose Details, and use the A-End VLAN value. (If you have Single Azure Peering VLAN enabled, you do not need to configure this interface.)
* **dot-1q-c-tag** -- The dot1Q C-tag. This tag is set in the Azure console with the peer.
* **Remote AS(bgp\_neighbor\_remote\_as)** -- The AS number for ExpressRoute is 12076.
* **Description(bgp\_neighbor\_description)** -- Enter a meaningful description of the template for the BGP peer.
* **Address(bgp\_neighbor\_address)** -- Specify the peer IP address of the ExpressRoute MSEE router. This is the second available IP address from the /30 Primary subnet assigned with the peer in the Azure console.
* **AS Number** -- Specify the AS number of the MVE.
9. Click **Update**.\
vManage displays a preview of the configuration.
Click Config Diff to review the changes. (Changes are highlighted in green.)
10. Select the MVE in the device list.
11. Review the changes and click **Configure Devices**.\
vManage loads the template. When complete, the status indicates success.
## Verify the ExpressRoute connection
You can verify the ExpressRoute connection from the Azure console. Review the ARP and route table.
You can also verify from vManage.
**To verify from vManage**
1. Go to Tools > SSH Terminal and log in to your MVE.
2. Enter the following command to see the routes advertised by the VPN peer:\
`show ip route vrf 100`
## Adding a secondary connection
To add a secondary VXC, repeat the process of adding a VPN to the device template and update the CLI template with a second subinterface.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
interface GigabitEthernet1. {{interface-tag}}
encapsulation dot1Q {{dot1Q-tag-s-tag-01}} second-dot1q {{dot1Q-tag-c-tag-01}}
vrf forwarding 100
ip address {{ip-address-subinterface-01}}
ip mtu 1500
!
interface GigabitEthernet1. {{interface-tag}}
encapsulation dot1Q {{dot1Q-tag-s-tag-01}} second-dot1q {{dot1Q-tag-c-tag-01}}
vrf forwarding 100
ip address {{ip-address-subinterface-01}}
ip mtu 1500
!
```
# Creating MVE Connections to AWS Direct Connect with Fortinet SD-WAN
Source: https://docs.megaport.com/cloud/mve/fortinet/aws/index
This help topic describes how to create a VXC from an MVE to AWS Direct Connect and integrate the connection with Fortinet SD-WAN.
You can create a network connection from an MVE (a FortiGate) to AWS with Virtual Cross Connects (VXCs) and AWS Direct Connect. You can create either a Hosted Connection or a Hosted VIF.
You start the AWS connection through the Megaport Portal, accept the connection in AWS, and create an interface for the Edge in FortiManager.
Fortinet provides documentation for their SD-WAN product, including FortiManager and cloud connections, at [Fortinet SD-WAN Documentation Library](https://docs.fortinet.com/sdwan).
## Before you begin
Before you can create a connection to AWS, you need to satisfy these requirements:
* Create an MVE (FortiGate). For more information, see [Creating an MVE](/mve/fortinet/creating-mve).
* In AWS, ensure that you have configured the Direct Connect gateway, AWS gateway, VPCs, and related attachments and associations.
## Creating a connection to AWS from the MVE
With an MVE already created, you can create a connection to AWS. The VXC connection can be one of two AWS models:
* [Hosted Connections](/cloud/mve/fortinet/aws/mve-aws-hosted) -- A Hosted Connection can support one private, public, or transit virtual interface. Hosted Connections are dedicated connections and are recommended for production environments.
* [Hosted Virtual Interfaces (Hosted VIFs)](/cloud/mve/fortinet/aws/mve-aws-hvif) -- Hosted VIFs can connect to public or private AWS cloud services: a Hosted VIF cannot connect to a transit virtual interface. Hosted VIF connections share bandwidth.
Click the link for your preferred connection type for detailed configuration steps.
Creating a connection from the MVE instance to AWS is very similar to creating a connection from a Port or an MCR. The primary difference is the process with Fortinet SD-WAN does not include automatically configure the MVE in Fortinet and you need to manually create a subinterface and define VLANs, IP addresses, MD5 values, and BGP peers in the FortiManager console.
# Creating an AWS Hosted Connection for an MVE with Fortinet SD-WAN
Source: https://docs.megaport.com/cloud/mve/fortinet/aws/mve-aws-hosted
This help topic describes how to create a Hosted Connection from an MVE to AWS Direct Connect and integrate the connection with Fortinet SD-WAN.
A Hosted Connection can support one private, public, or transit virtual interface. These are dedicated connections and are recommended for production environments.
**To create a connection to an AWS Hosted Connection from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select AWS as the service provider, select Hosted Connection as the AWS Connection Type, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.\
Each destination port has either a blue or red icon to indicate its diversity zone. To achieve diversity, you need to create two connections with each one in a different zone.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection. This value cannot be changed after deployment. The drop-down list displays predefined rate limits available for your MVE, with speeds varying by location and service capabilities.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/fortinet/creating-mve#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Specify the connection details for the AWS service.
* **AWS Connection Name** -- This is a text field and will be the name of your virtual interface that appears in the AWS console. The AWS Connection Name is automatically populated with the name specified in a
previous step.
* **AWS Account ID** -- This is the ID of the account you want to connect. You can find this value in the management section of your AWS console.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Once the VXC connection is deployed successfully, it appears on the Megaport Portal Services page and is associated with the MVE. Click the VXC title to display the details of this connection. Note that the service status (Layer 2) is up but BGP (Layer 3) will be down because the configuration does not exist yet.
Once deployed in the Megaport Portal, you need to accept the connection in the AWS console and create a Virtual Interface for the connection:
**To accept a Hosted Connection**
1. In AWS, go to **Services > AWS Direct Connect > Connections** and
click the connection name.
2. Click **Accept** at the top right of the window.
The state will be pending for a few minutes while AWS deploys the
connection. After it is deployed, the state changes from *ordering* to
*available.*
The connection is now available, however you need to create a VIF to connect to AWS services.
For more information about accepting AWS connections, see the
[AWS documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/accept-hosted-connection.html).
## Creating a virtual interface
Once you have created and accepted a Hosted Connection, create a VIF and attach the Hosted Connection to a gateway.
AWS provides
[detailed instructions](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-vif.html) for creating Public, Private, and Transit interfaces.
**To create and attach a VIF**
1. In the AWS console, click **Create Virtual Interface**.
2. Select the interface type.
The type will vary depending on the type of service you need to access.
* **Private** -- Access resources running into a VPC using their private IP addresses. You can choose to terminate a private virtual interface on a private virtual gateway (to access a single VPC) or to a Direct Connect gateway (and map up to 10 VPCs to the VIF).
* **Public** -- Access all AWS public endpoints, as well as all AWS resources that are reachable by a public IP address.
* **Transit** -- Transport traffic from a Direct Connect gateway to one or more transit gateways.
3. Specify the configuration details:
* **Virtual interface name** -- Enter a name for the virtual interface.
* **Connection** -- The physical connection where you want this virtual interface to be provisioned. The name you provided for the Hosted Connection in the Megaport Portal appears here.
* **Virtual interface owner** -- The account that will own the virtual interface. Select My AWS account.
* **Direct Connect gateway** -- Select the Direct Connect gateway to attach this virtual interface to. A transit VIF is not directly attached to a Transit gateway, but to a Direct Connect gateway.
* **VLAN** -- The VLAN assigned to the virtual interface. Leave this value as is. The VLAN address is populated and appears to be editable; however, you will get an error if you try to change it.
* **BGP ASN** -- Enter the Border Gateway Protocol (BGP) autonomous system number (ASN) for the MVE side of the BGP session.
The following BGP details can be filled out or left blank. When left blank, they are auto-populated by AWS.
You can also choose whether you want the virtual interface to support Jumbo frames. Enable Jumbo MTU to support an Ethernet packet of 8500 bytes.
4. Click **Create virtual interface**.
To view the VIF details and state, navigate to **Services > AWS Direct Connect > Connections > Name of the Megaport-Created-Hosted Connection**.
BGP hasn’t been configured, so the interface state appears as *down*.
Once you accept the connection and create the VIF in AWS, the VXC state changes to *configured* in the Megaport Portal.
## Adding AWS connection details to FortiManager
After you create the connection from your MVE to AWS and set up the connection in the AWS console, you need to configure it in FortiManager. This involves creating an interface and configuring BGP settings, ASNs, VLANs, and MD5 values.
**To add the AWS connection in FortiManager**
1. Collect the connection details from the AWS console.\
Display the details of the Virtual Interface you created in AWS for this Hosted Connection. Note the values for the **BGP ASN**, **BGP Auth Key**, **Your Peer IP**, and **Amazon Peer IP**.
2. Collect the connection details from the Megaport Portal.\
Click the gear icon for the AWS connection from your MVE then click the Details view.
Note the value for the **A-End VLAN**.
3. Log in to the FortiManager.
You can also log in on your MVE instance: https\://\
4. From your managed device, go to the **System** menu and choose **Interface**.
The page displays **port1** as your physical interface.
5. Click **+Create New > Interface** and provide this information:
* **Interface Name** -- Specify a meaningful name for the interface.
* **Alias Name** (optional) -- Enter an alternate name. For easy reference, use the AWS Virtual Interface ID for this connection as the alias.
* **Type** -- Choose VLAN.
* **Interface** -- Choose the parent interface: `port1`.
* **VLAN ID** -- Specify the A-End VLAN listed for this AWS Connection in the Megaport Portal.
* **Role** -- Choose Undefined.
* **Addressing Mode** -- Select Manual.
* **IP/Netmask** -- These values are available in the virtual interface details in the AWS console. The IP address and netmask appear in the **Your Peer IP** field.
* **Administrative Access** - Specify how you want to access this interface, such as HTTPS, PING, and SSH.
* **DHCP Server** - Click **OFF**.
6. Click **OK**.\
The new VLAN interface appears with your `port1` physical interface.
You can run an `execute ping` command from FortiOS to verify the connection.
You need to push the configuration to the MVE, which happens when you have AutoUpdate configured. If you cannot successfully ping the connection, go to Manage Devices in FortiManager, select the MVE, and choose **Refresh Device** from the More menu. If prompted, select AutoUpdate for the **Config Status**.
At this point, we have created the interface and next we need to create the BGP session.
1. In FortiManager, go to **Router > BGP**.
2. Provide this information:
* **Local AS** -- Provide the ASN for the MVE connection. Use the **BGP ASN** from the virtual interface details in the AWS console.
* **Router ID** -- Enter the IP address that appears in the **Your Peer IP** field for the virtual interface details in the AWS console.
3. In Neighbors, click **+Create New**.
4. For the neighbor **IP**, add the **Amazon Peer IP** from the virtual interface details in the AWS console.
5. For **Remote ASN**, enter the Amazon-side ASN.\
By default this is 64512.
6. Click **OK**.
7. Click **Apply**.\
The neighbor is configured but we need to add the BGP Auth information. The web interface does not let you define this and you need to use the command line to add the BGP details.
8. SSH to the MVE instance using your private key file.\
For example\
`ssh -i ~/.ssh/megaport-mve-instance-1-2048 admin@162.43.143.XX`
9. Use these commands to add a password for the BGP neighbor.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
config router bgp
config neighbor
edit ""
set password
next
end
```
## Validating your AWS connection
You can review connection details, including the connection state, from the CLI with these commands:
* `get system interface` -- Displays configuration details and current status for the device interfaces.
* `get router info bgp neighbor ` -- Displays configuration details and current status for the BGP neighbors.
# Creating an AWS Hosted VIF for an MVE with Fortinet SD-WAN
Source: https://docs.megaport.com/cloud/mve/fortinet/aws/mve-aws-hvif
This help topic describes how to create a Hosted VIF from an MVE to AWS Direct Connect and integrate the connection with Fortinet SD-WAN.
Hosted VIFs can connect to public or private AWS cloud services: a Hosted VIF cannot connect to a transit virtual interface. These connections share bandwidth.
AWS Hosted Virtual Interfaces (Hosted VIF) do not support diversity zones. To ensure connection diversity for Hosted VIFs, create VXCs to two destination ports in different data centers, instead of two ports in separate diversity zones.
**To create a connection to an AWS Hosted VIF from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select AWS as the service provider, select Hosted VIF as the AWS Connection Type, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
Match this to the AWS Connection Name on the next screen for easy mapping.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Accepted values start at 1 Mbps and scale in 1 Mbps increments. Maximum available speed depends on location and service availability. Note the sum of all hosted virtual VXCs to a service can exceed the MVE capacity, but the total aggregate will never burst beyond the MVE capacity.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/fortinet/creating-mve#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Specify the details for the AWS service.
Here are details for each field:
* Select **Public** or **Private**.
* **Private** -- Access private AWS services such as a VPC, EC2
instances, load balancers, RDS DB instances, on private IP address
space.
* **Public** -- Access public AWS services such as Amazon Simple Storage
Service (S3), DynamoDB, CloudFront, and Glacier. You will also receive
[Amazon's global IP
prefixes](https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html)
(approximately 2,000 prefixes).
Public VIFs require manual intervention from Amazon and could take up to 72 hours. For more information, see [Configuring Public AWS Connections with IP Addresses Provided by AWS](/cloud/megaport/aws/aws-public-ip).
* **AWS Connection Name** -- This is a text field and will be the name
of your virtual interface that appears in the AWS console. The AWS
Connection Name is automatically populated with the name specified in a
previous step.
* **AWS Account ID** -- This is the ID of the account you want to
connect. You can find this value in the management section of your
AWS console.
* **Customer ASN** (optional) -- Specify the ASN used for
BGP peering sessions on any VXCs connected to the MVE. This value
is defined when you configure the MVE and, once defined, it cannot
be changed.
* **BGP Auth Key** (optional) -- Specify the BGP key. If you leave this blank, Megaport negotiates a key automatically for you with AWS which will be displayed in the Megaport Portal. The key is not displayed in the AWS console.
The BGP Auth Key is generated during the ordering process when this field is left blank. It will not be displayed on the Summary page when ordering. To see the key, view the Connection Settings after the service has been deployed and is live.
* **Customer IP Address** -- The IP address space (in CIDR format) used on your network for peering. This field is optional for private connections and if left blank, Megaport assigns an address.
* **Amazon IP Address** -- The IP address space in CIDR format
assigned in the AWS VPC network for peering. This field is
optional for private connections and if left blank, Megaport automatically assigns an
address.
* **Prefixes** (optional) -- (visible for Public connections only) Specify IP Prefixes to announce to AWS. Specify the prefixes you will advertise when deploying a Public Direct Connect (RIR-assigned IPv4 addresses only).
Once you configure Prefixes for a Public connection, you cannot change them and the field is grayed out. To change this value, create a support ticket with AWS so they can make this change in a non-impacting way. Or, you can cancel the Hosted VIF and reorder. In both cases, you need to wait for AWS to manually approve the request.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
The AWS VXC appears as a connection for the MVE in the Megaport Portal.
Next, accept the connection in AWS.
#### Accepting the Virtual Interface for Private Connections
A few minutes after ordering a private Hosted VIF VXC, the
corresponding inbound VIF request is visible on the AWS Direct
Connect > Virtual
Interfaces page in the AWS console. (This is specific to the region associated with
the target AWS port.) If your VIF doesn't appear after a few minutes,
confirm that you are viewing the correct region.
**To review and accept the private virtual interface**
1. From the **AWS Direct Connect > Virtual Interface** page, click the ID
of the interface to display the configuration and peering details.
The name and account ID of the VIF should match the values supplied in
the Portal and the BGP ASN should match the Customer ASN configured with
the VXC. The Amazon ASN is the default region's AWS ASN and
not the value specified during the configuration - this is
updated when the virtual interface is accepted and
assigned.
2. Click **Accept**.
3. Select the gateway type and then the specific gateway for this new
virtual interface.
4. Click **Accept virtual interface**.
The state of the connection changes from *confirming* to *pending*, and then changes to *available* once BGP is established. Note that sometimes there is a delay in the *available* BGP status appearing on the AWS end, though you can confirm the current state of the Layer 3 link through the Portal view.
#### Accepting the Virtual Interface for Public Connections
Several minutes after ordering a public Hosted VIF VXC, the corresponding inbound VIF request appears on the **AWS Direct Connect > Virtual Interfaces** page in the AWS console (This is specific to the region associated with the target AWS port).
**To review and accept the public virtual interface**
1. From the AWS Direct Connect > Virtual Interface page, click the ID
of the interface to display the configuration and peering details.
2. Review the configuration details and click **Accept**, and when
prompted, click **Confirm**.
The state of the connection changes from *confirming* to *verifying*. At
this point, the connection needs to be verified by Amazon - a process
that can take up to 72 hours. When verified, the state changes to
*available*.
## Adding AWS connection details to FortiManager
After you create the connection from your MVE to AWS and set up the connection in the AWS console, you need to configure it in FortiManager. This involves adding a device interface and configuring BGP settings, ASNs, VLANs, and MD5 values.
**To configure an AWS connection between a Fortinet MVE and AWS**
1. Collect the connection details from the Megaport Portal.\
To display the details, click the gear icon for the AWS connection from your MVE and click the Details view. Note the values for the **A-End VLAN**, **Customer Address** (and CIDR), **Amazon Address**, and **Customer ASN**.
2. Log in to the FortiManager.
You can also log in on your MVE instance: https\://\
3. From your managed device, go to the **System** menu and choose **Interface**.
The page displays **port1** as your physical interface.
4. Click **+Create New > Interface** and provide this information:
* **Interface Name** -- Specify a meaningful name for the interface.
* **Alias Name** (optional) -- Enter an alternate name. For easy reference, use the AWS Virtual Interface ID for this connection as the alias.
* **Type** -- Choose VLAN.
* **Interface** -- Choose the parent interface: `port1`.
* **VLAN ID** -- Specify the A-End VLAN listed for this AWS Connection in the Megaport Portal.
* **Role** -- Choose Undefined.
* **Addressing Mode** -- Select Manual.
* **IP/Netmask** -- Specify the Customer Address from the VXC details in the Megaport Portal.
* **Administrative Access** - Select how you want to access this interface, such as HTTPS, PING, and SSH.
* **DHCP Server** - Click **OFF**.
5. Click **OK**.\
The new VLAN interface appears with your `port1` physical interface.
You can run an `execute ping` command from FortiOS to verify the connection.
You need to push the configuration to the MVE, which happens when you have AutoUpdate configured. If you cannot successfully ping the connection, go to Manage Devices in FortiManager, select the MVE, and choose **Refresh Device** from the More menu. If prompted, select AutoUpdate for the **Config Status**.
At this point, we have created the interface and next we need to create the BGP session.
**To create the BGP session**
1. In FortiManager, go to **Router > BGP**.
2. Provide this information:
* **Local AS** -- Add the **Customer ASN** value from the Megaport connection details.
* **Router ID** -- Add the **Customer Address** value from the Megaport connection details.
3. In Neighbors, click **+Create New**.
4. For the neighbor **IP**, add the **Amazon Address** from the Megaport connection details.
5. For **Remote ASN**, enter the Amazon-side ASN.\
By default this is 64512.
6. Click **OK**.
7. Click **Apply**.
The neighbor is configured but you need to add the BGP Auth information. The web interface does not let you define this and you need to use the command line to add the BGP details.
**To add the BGP authorization**
1. SSH to the MVE instance using your private key file.\
For example\
`ssh -i ~/.ssh/megaport-mve-instance-1-2048 admin@162.43.143.XX`
2. Use these commands to add a password for the BGP neighbor.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
config router bgp
config neighbor
edit ""
set password
next
end
```
## Validating your AWS connection
You can review connection details, including the connection state, from the CLI with these commands:
* `get system interface` -- Displays configuration details and current status for the device interfaces.
* `get router info bgp neighbor ` -- Displays configuration details and current status for the BGP neighbors.
# Creating an Azure Connection for an MVE with Fortinet SD-WAN
Source: https://docs.megaport.com/cloud/mve/fortinet/azure/index
This help topic describes how to create a VXC from an MVE to Microsoft Azure ExpressRoute and integrate the connection with Fortinet SD-WAN.
You can create a network connection from an MVE (a FortiGate) to Azure ExpressRoute with Virtual Cross Connects (VXCs). You can create either a private connection or a public (Microsoft) connection.
Before you begin, create an MVE (FortiGate) in FortiManager. For more information, see [Creating an MVE Integrated with Fortinet](/mve/fortinet/creating-mve).
There are three parts to adding an ExpressRoute connection to your MVE and FortiManager.
1. Set up your ExpressRoute plan and deploy the ExpressRoute circuit in the Azure console. When deployed, you get a service key. For additional details, see the Microsoft [ExpressRoute documentation](https://docs.microsoft.com/en-us/azure/expressroute/).
To check the latency and price of connecting to a particular Azure Partner location, start the procedure to [add a connection to Microsoft Azure](#azure-vxc) but instead of providing a **Microsoft Azure Service Key**, click **View all Azure Partner locations**. You can proceed to the Connection Details page without a service key and review the pricing of the selected port. To place an order for a Microsoft Azure connection, you need to provide a service key.
2. In the Megaport Portal, create a connection (VXC) from your MVE to your ExpressRoute location.
3. In FortiManager, create a new interface and add the details of the ExpressRoute connection.
The instructions in this topic describe the second and third parts.
MVE for Fortinet SD-WAN requires configuration steps in both FortiManager and the Megaport Portal for all cloud connections.
## Adding the ExpressRoute connection in the Megaport Portal
To set up the ExpressRoute connection, you need to create the connection in the Megaport Portal.
**To create a connection to ExpressRoute from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. Click **+Connection** on the MVE.
3. Click the **Cloud** tile.
4. Select Microsoft Azure as the provider.
5. Add the ExpressRoute service key into the **Microsoft Azure Service Key** field.\
The Portal verifies the key then displays the available port locations based on the ExpressRoute region. For example, if your ExpressRoute service is deployed in the Australia East region in Sydney, you can select the Sydney locations.
6. Select the connection point for your first connection.\
To deploy a second connection (and this is recommended), you can create a second VXC - enter the same service key and select the other connection location.
Some helpful links appear on the configuration screen to resources including the Azure Resource Manager console and some tutorial videos.
7. Click **Next**.
8. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit for the VXC will be capped at the maximum allowable based on the ExpressRoute service key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/fortinet/creating-mve#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection (for ExpressRoute this is the S-Tag). This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
* **Configure Single Azure Peering VLAN** -- By default, this option is enabled for MVE and we strongly recommend keeping it enabled with Fortinet SD-WAN.\
This option provides a single tag VLAN solution. You configure peering in Azure with the MVE VLAN (A-End) and the peer VLAN set in Azure (B-End). Note, you can have only one peering type (Private or Microsoft) per VXC with this option.
If you do not enable this option, the VXC appears active but it does not recognize traffic.
* **Azure Peering VLAN** -- This value needs to match the A-End VLAN for single tag VLAN peering. A different Azure peering VLAN can also be set, if required.
9. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
When the VXC configuration completes, the VXC icon is green.
In the Azure Resource Management console, the provider status will be `Provisioned`.
When provisioned, you need to configure peerings. You can configure private and Microsoft peering. Click the peer to configure and provide these details:
* **Peer ASN** -- Enter the ASN for the MVE.
* **IPv4 Subnets** -- From each of these subnets, MVE uses the first usable IP address and Microsoft uses the second usable IP for its router.
* **VLAN ID** -- Enter the A-End VLAN from the MVE. (Note, the VLAN ID in the Azure console can be different from the A-End VLAN.)
* **Shared Key** (optional) -- Enter an MD5 password for BGP.
## Adding the ExpressRoute connection to FortiManager
After you create the connection from your MVE to Azure and set up the connection in the Azure console, you need to configure it in FortiManager. This involves creating an interface and configuring BGP settings, ASNs, VLANs, and MD5 values.
**To add the Azure Cloud connection in FortiManager**
1. Collect the connection details from the Azure console.\
Display the details of the connection you created in Azure for this connection. Note the values for the **Peer ASN**, **Shared Key**, **VLAN ID**, and **IPv4 Primary Subnet**.
2. Collect the connection details from the Megaport Portal.\
Click the gear icon for the Azure connection from your MVE and click the Details view.
Note the value for the **A-End VLAN**.
3. Log in to the FortiManager.
You can also log in on your MVE instance: https\://\
4. From your managed device, go to the **System** menu and choose **Interface**.
The page displays **port1** as your physical interface.
5. Click **+Create New > Interface** and provide this information:
* **Interface Name** -- Specify a meaningful name for the interface.
* **Alias Name** (optional) -- Enter an alternate name.
* **Type** -- Choose VLAN.
* **Interface** -- Choose the parent interface: `port1`.
* **VLAN ID** -- Specify the A-End VLAN listed for this Azure Connection in the Megaport Portal.
* **Role** -- Choose Undefined.
* **Addressing Mode** -- Select Manual.
* **IP/Netmask** -- These values are available in the Azure console. The IP addresses and CIDR appear in the **IPv4 Primary Subnet** field; MVE uses the first usable IP address and Azure uses the second usable IP for its router. For this field, enter the MVE (first usable) IP address.
* **Administrative Access** - Specify how you want to access this interface, such as HTTPS, PING, and SSH.
* **DHCP Server** - Click **OFF**.
6. Click **OK**.\
The new VLAN interface appears with your `port1` physical interface.
You can run an `execute ping` command from FortiOS to verify the connection.
You need to push the configuration to the MVE, which happens when you have AutoUpdate configured. If you cannot successfully ping the connection, go to Manage Devices in FortiManager, select the MVE, and choose **Refresh Device** from the More menu. If prompted, select AutoUpdate for the **Config Status**.
At this point, we have created the interface and next we need to create the BGP session.
1. In FortiManager, go to **Router > BGP**.
2. Provide this information:
* **Local AS** -- Provide the ASN for the MVE connection. Use the **Peer ASN** from the Azure console.
* **Router ID** -- Enter the first usable IP address from the **IPv4 Primary Subnet** from the Azure console.
3. In Neighbors, click **+Create New**.
4. For the neighbor **IP**, add the second usable IP address from the **IPv4 Primary Subnet** from the Azure console.
5. For **Remote ASN**, enter the Azure-side ASN of 12076.\
This is a fixed value, and appears in the connection details on the Azure console.
6. Click **OK**.
7. Click **Apply**.\
The neighbor is configured but we need to add the BGP Auth information if you defined this in the Azure console. (This was optional.) The web interface does not let you define this and you need to use the command line to add the BGP details.
8. SSH to the MVE instance using your private key file.\
For example\
`ssh -i ~/.ssh/megaport-mve-instance-1-2048 admin@162.43.143.XX`
9. Use these commands to add a password for the BGP neighbor.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
config router bgp
config neighbor
edit ""
set password
next
end
```
## Validating your Azure connection
You can review connection details, including the connection state, from the CLI with these commands:
* `get system interface` -- Displays configuration details and current status for the device interfaces.
* `get router info bgp neighbor ` -- Displays configuration details and current status for the BGP neighbors.
# Creating MVE Connections to AWS Direct Connect with Palo Alto VM-Series
Source: https://docs.megaport.com/cloud/mve/palo-alto/aws/index
This help topic describes how to create a VXC from an MVE to AWS Direct Connect and integrate the connection with Palo Alto.
You can create a network connection from a Palo Alto MVE to AWS with Virtual Cross Connects (VXCs) and AWS Direct Connect. You can create either a Hosted Connection or a Hosted VIF.
You start the AWS connection through the Megaport Portal, accept the connection in AWS, and create an interface for the Edge in VM-Series.
Palo Alto Networks provides documentation for VM-Series at [VM-Series Tech Docs](https://docs.paloaltonetworks.com/vm-series).
## Before you begin
Before you can create a connection to AWS, you need to satisfy these requirements:
* Create an MVE (VM-Series firewall). For more information, see [Creating an MVE](/mve/palo-alto/creating-mve).
* In AWS, ensure that you have configured the Direct Connect gateway, AWS gateway, VPCs, and related attachments and associations.
## Creating a connection to AWS from the MVE
With an MVE already created, you can create a connection to AWS. The VXC connection can be one of two AWS models:
* [Hosted Connections](/cloud/mve/palo-alto/aws/mve-aws-hosted) -- A Hosted Connection can support one private, public, or transit virtual interface. Hosted Connections are dedicated connections and are recommended for production environments.
* [Hosted Virtual Interfaces (Hosted VIFs)](/cloud/mve/palo-alto/aws/mve-aws-hvif) -- Hosted VIFs can connect to public or private AWS cloud services: a Hosted VIF cannot connect to a transit virtual interface. Hosted VIF connections share bandwidth.
Click the link for your preferred connection type for detailed configuration steps.
Creating a connection from the MVE instance to AWS is very similar to creating a connection from a Port or an MCR. The primary difference is the process with Palo Alto Networks VM-Series does not include automatically configuring the MVE in Palo Alto. You need to manually create a subinterface and define VLANs, IP addresses, MD5 values, and BGP peers in the VM-Series console.
# Creating an AWS Hosted Connection for an MVE with Palo Alto VM-Series
Source: https://docs.megaport.com/cloud/mve/palo-alto/aws/mve-aws-hosted
This help topic describes how to create a Hosted Connection from an MVE to AWS Direct Connect and integrate the connection with Palo Alto VM-Series.
A Hosted Connection can support one private, public, or transit virtual interface. These are dedicated connections and are recommended for production environments.
**To create a connection to an AWS Hosted Connection from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select AWS as the service provider, select Hosted Connection as the AWS Connection Type, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.\
Each destination port has either a blue or red icon to indicate its diversity zone. To achieve diversity, you need to create two connections with each one in a different zone.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection. This value cannot be changed after deployment. The drop-down list displays predefined rate limits available for your MVE, with speeds varying by location and service capabilities.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/palo-alto/creating-mve#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Specify the connection details for the AWS service.
* **AWS Connection Name** -- This is a text field and will be the name of your virtual interface that appears in the AWS console. The AWS Connection Name is automatically populated with the name specified in a previous step.
* **AWS Account ID** -- This is the ID of the account you want to connect. You can find this value in the management section of your AWS console.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Once the VXC connection is deployed successfully, it appears on the Megaport Portal Services page and is associated with the MVE. Click the VXC name to display the details of this connection. Note that the service status (Layer 2) is up but BGP (Layer 3) will be down because the configuration does not exist yet.
Once deployed in the Megaport Portal, you need to accept the connection in the AWS console and create a Virtual Interface for the connection:
**To accept a Hosted Connection**
1. In AWS, go to **Services > AWS Direct Connect > Connections** and click the connection name.
2. Click **Accept** at the top right of the window.
The state will be pending for a few minutes while AWS deploys the connection. After it is deployed, the state changes from *ordering* to *available*.
The connection is now available, however you need to create a VIF to connect to AWS services.
For more information about accepting AWS connections, see the [AWS documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/accept-hosted-connection.html).
## Creating a virtual interface
Once you have created and accepted a Hosted Connection, create a VIF and attach the Hosted Connection to a gateway.
AWS provides [detailed instructions](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-vif.html) for creating Public, Private, and Transit interfaces.
**To create and attach a VIF**
1. In the AWS console, click **Create Virtual Interface**.
2. Select the interface type.
The type will vary depending on the type of service you need to access.
* **Private** -- Access resources running into a VPC using their private IP addresses. You can choose to terminate a private virtual interface on a private virtual gateway (to access a single VPC) or to a Direct Connect gateway (and map up to 10 VPCs to the VIF).
* **Public** -- Access all AWS public endpoints, as well as all AWS resources that are reachable by a public IP address.
* **Transit** -- Transport traffic from a Direct Connect gateway to one or more transit gateways.
3. Specify the configuration details:
* **Virtual interface name** -- Enter a name for the virtual interface.
* **Connection** -- The physical connection where you want this virtual interface to be provisioned. The name you provided for the Hosted Connection in the Megaport Portal appears here.
* **Virtual interface owner** -- The account that will own the virtual interface. Select My AWS account.
* **Direct Connect gateway** -- Select the Direct Connect gateway to attach this virtual interface to. A transit VIF is not directly attached to a Transit gateway, but to a Direct Connect gateway.
* **VLAN** -- The VLAN assigned to the virtual interface. Leave this value as is. The VLAN address is populated and appears to be editable; however, you will get an error if you try to change it.
* **BGP ASN** -- Enter the Border Gateway Protocol (BGP) autonomous system number (ASN) for the MVE side of the BGP session.
The following BGP details can be filled out or left blank. When left blank, they are auto-populated by AWS.
You can also choose whether you want the virtual interface to support Jumbo frames. Enable Jumbo MTU to support an Ethernet packet of 8500 bytes.
4. Click **Create virtual interface**.
To view the VIF details and state, navigate to **Services > AWS Direct Connect > Connections > Name of the Megaport-Created-Hosted Connection**.
BGP hasn't been configured, so the interface state appears as *down*.
Once you accept the connection and create the VIF in AWS, the VXC state changes to *configured* in the Megaport Portal.
## Adding AWS connection details to VM-Series
After you create the connection from your MVE to AWS and set up the connection in the AWS console, you need to configure it in VM-Series. This involves creating an interface and configuring BGP settings.
**To add the AWS connection in VM-Series**
1. Collect the connection details from the AWS console.\
Display the details of the Virtual Interface you created in AWS for this Hosted Connection. Note the values for the **BGP ASN**, **BGP Auth Key**, **Your Peer IP**, and **Amazon Peer IP**.
2. Collect the connection details from the Megaport Portal.\
To display the details, click the gear icon for the AWS connection from your MVE and click the Details view.
Note the value for the **A-End VLAN**.
3. Log in to the VM-Series.
4. Choose Network > Interfaces.
5. Click **Add Subinterface**.
6. Provide these details:
* **Interface Name** -- Enter a name for the subinterface. In the adjacent field, enter a number to identify the subinterface.
* **Comment** -- Enter an alternate name, for example, `AWS VIF dxvif-fh9aokej`.
* **Tag** -- Specify the A-End inner VLAN value associated with the AWS VXC you created in the Megaport Portal.
* **Virtual Router** -- Select a virtual router to the interface, as required by your network.
7. Select the **IPv4** tab.
8. Select **Static** as the Type.
9. Click **+Add** to add a new IP address.
10. Enter the IPv4 address and netmask.\
These values are available in the virtual interface details in the AWS console. The IP address and netmask appear in the **Your Peer IP** field.
11. Click **OK**.
12. Click **Commit** in the top right corner.
13. Review the changes and click **Commit**.
The new VLAN interface appears with your `ethernet1/1` physical interface.
Next, you will create a security zone so the interface can route traffic.
**To create a security zone**
1. Select the `ethernet1/1.1010` subinterface.
2. Select New Zone from the Security Zone drop-down list.
3. Specify a name for the security zone.
4. Click **+Add** under Interfaces and add `ethernet1/1.1010` to the security zone.
5. Specify any additional details as required for your network security.
6. Select New Zone Protection Profile from the Zone Protection Profile drop-down list.
7. Specify any details as required for your network security. This example uses all the defaults.
8. Click **OK**.
9. Click **OK** in the Layer3 Subinterface screen.
10. Click **Commit** in the top right corner.
11. Review the changes and click **Commit**.
At this point, you have created the interface. Next, you will create the BGP session.
**To create the BGP session**
1. In VM-Series, choose Network > Virtual Routers.
2. Select the virtual router.
3. In the left pane, select BGP.
4. Provide the following BGP details:
* **Enable** -- Select this check box to start the BGP session after committing these changes.
* **Router ID** -- Enter the IP address that appears in the **Your Peer IP** field for the virtual interface details in the AWS console.
* **AS Number** -- Provide the ASN for the MVE connection. Use the **BGP ASN** from the virtual interface details in the AWS console.
5. Click **+Add** under Auth Profiles.
6. Specify a Profile Name.
7. Enter and confirm the auth password.
8. Click **OK**.
9. Select the **Peer Group** tab.
10. Click **+Add** to add a peer group.
11. Specify a name for the peer group. For example, AWS-xxxx.
12. Specify eBGP as the session type.
13. Specify any additional details as required for your network.
14. Click **+Add** to add a new peer.
15. Specify the details for the peer:
* **Name** -- Specify a name for the peer.
* **Peer AS** -- Specify the Amazon-side autonomous system number (ASN). By default this is 64512.
* **Local Address** -- Select the proper subinterface and IP address from the drop-down list.
* **Peer Address** -- Enter the AWS side IPv4 address. This is the **Amazon Peer IP** from the virtual interface details in the AWS console.
16. Select the **Connection Options** tab.
17. Select the previously created Auth Profile.
18. Click **OK** in the Peer Group - Peer screen.
19. Click **OK** in the BGP - Peer Group/Peer screen.
20. Click **OK** in the Virtual Router screen.
21. Click **Commit** in the top right corner.
22. Review the changes and click **Commit**.
## Validating the AWS connection
**To check the status of the BGP peer**
1. Choose Network > Virtual Routers.
2. Locate your virtual router (default).
3. Click **More Runtime Stats** in the Runtime Stats column on the right.
4. Select the **BGP** tab, and then select the **Peer** tab.
5. Verify that the peer status is *Established*.
You can also check the status in your AWS Direct Connect portal (this might take a few minutes to refresh).
# Creating an AWS Hosted VIF for an MVE with Palo Alto SD-WAN
Source: https://docs.megaport.com/cloud/mve/palo-alto/aws/mve-aws-hvif
This help topic describes how to create a Hosted VIF from an MVE to AWS Direct Connect and integrate the connection with Palo Alto SD-WAN.
Hosted VIFs can connect to public or private AWS cloud services: a Hosted VIF cannot connect to a transit virtual interface. These connections share bandwidth.
AWS Hosted Virtual Interfaces (Hosted VIF) do not support diversity zones. To ensure connection diversity for Hosted VIFs, create VXCs to two destination ports in different data centers, instead of two ports in separate diversity zones.
**To create a connection to an AWS Hosted VIF from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select AWS as the service provider, select Hosted VIF as the AWS Connection Type, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
Match this to the AWS Connection Name on the next screen for easy mapping.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Accepted values start at 1 Mbps and scale in 1 Mbps increments. Maximum available speed depends on location and service availability. Note the sum of all hosted virtual VXCs to a service can exceed the MVE capacity, but the total aggregate will never burst beyond the MVE capacity.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/palo-alto/creating-mve#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Specify the details for the AWS service.
Here are details for each field:
* Select **Public** or **Private**.
* **Private** -- Access private AWS services such as a VPC, EC2 instances, load balancers, RDS DB instances, on private IP address space.
* **Public** -- Access public AWS services such as Amazon Simple Storage Service (S3), DynamoDB, CloudFront, and Glacier. You will also receive [Amazon's global IP prefixes](https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html) (approximately 2,000 prefixes).
Public VIFs require manual intervention from Amazon and could take up to 72 hours. For more information, see [Configuring Public AWS Connections with IP Addresses Provided by AWS](/cloud/megaport/aws/aws-public-ip).
* **AWS Connection Name** -- This is a text field and will be the name of your virtual interface that appears in the AWS console. The AWS Connection Name is automatically populated with the name specified in a previous step.
* **AWS Account ID** -- This is the ID of the account you want to connect. You can find this value in the management section of your AWS console.
* **Customer ASN** (optional) -- Specify the ASN used for BGP peering sessions on any VXCs connected to the MVE. This value is defined when you configure the MVE and, once defined, it cannot be changed.
* **BGP Auth Key** (optional) -- Specify the BGP key. If you leave this blank, Megaport negotiates a key automatically for you with AWS which will be displayed in the Megaport Portal. The key is not displayed in the AWS console.
The BGP Auth Key is generated during the ordering process when this field is left blank. It will not be displayed on the Summary page when ordering. To see the key, view the Connection Settings after the service has been deployed and is live.
* **Customer IP Address** -- The IP address space (in CIDR format) used on your network for peering. This field is optional for private connections and if left blank, Megaport assigns an address.
* **Amazon IP Address** -- The IP address space in CIDR format assigned in the AWS VPC network for peering. This field is optional for private connections and if left blank, Megaport automatically assigns an address.
* **Prefixes** (optional) -- (visible for Public connections only) Specify IP Prefixes to announce to AWS. Specify the prefixes you will advertise when deploying a Public Direct Connect (RIR-assigned IPv4 addresses only).
Once you configure Prefixes for a Public connection, you cannot change them and the field is grayed out. To change this value, create a support ticket with AWS so they can make this change in a non-impacting way. Or, you can cancel the Hosted VIF and reorder. In both cases, you need to wait for AWS to manually approve the request.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
The AWS VXC appears as a connection for the MVE in the Megaport Portal.
Next, accept the connection in AWS.
#### Accepting the Virtual Interface for Private Connections
A few minutes after ordering a private Hosted VIF VXC, the corresponding inbound VIF request is visible on the AWS Direct Connect > Virtual Interfaces page in the AWS console. (This is specific to the region associated with the target AWS port.) If your VIF doesn't appear after a few minutes, confirm that you are viewing the correct region.
**To review and accept the private virtual interface**
1. From the **AWS Direct Connect > Virtual Interface** page, click the ID of the interface to display the configuration and peering details.
The name and account ID of the VIF should match the values supplied in the Portal and the BGP ASN should match the Customer ASN configured with the VXC. The Amazon ASN is the default region's AWS ASN and not the value specified during the configuration - this is updated when the virtual interface is accepted and assigned.
2. Click **Accept**.
3. Select the gateway type and then the specific gateway for this new virtual interface.
4. Click **Accept virtual interface**.
The state of the connection changes from *confirming* to *pending*, and then changes to *available* once BGP is established. Note that sometimes there is a delay in the *available* BGP status appearing on the AWS end, though you can confirm the current state of the Layer 3 link through the Portal view.
#### Accepting the Virtual Interface for Public Connections
Several minutes after ordering a public Hosted VIF VXC, the corresponding inbound VIF request appears on the **AWS Direct
Connect > Virtual Interfaces** page in the AWS console. This is specific to the region associated with the target AWS port.
**To review and accept the public virtual interface**
1. From the AWS Direct Connect > Virtual Interface page, click the ID of the interface to display the configuration and peering details.
2. Review the configuration details and click **Accept**, and when prompted, click **Confirm**.
The state of the connection changes from *confirming* to *verifying*. At this point, the connection needs to be verified by Amazon - a process that can take up to 72 hours. When verified, the state changes to *available*.
## Adding AWS connection details to Palo Alto VM-Series
After you create the connection from your MVE to AWS and set up the connection in the AWS console, you need to configure it in VM-Series. This involves adding a device interface and configuring BGP settings.
**To configure an AWS connection between a Palo Alto MVE and AWS**
1. Collect the connection details from the Megaport Portal.\
Click the gear icon for the AWS connection from your MVE and click the Details view. Note the values for the **A-End VLAN**, **Customer Address** (and CIDR), **Amazon Address**, and **Customer ASN**.
2. Log in to the VM-Series.
3. Choose Network > Interfaces.
4. Select the A-End MVE (`ethernet1/1`).
5. Click **Add Subinterface** at the bottom of the screen.
6. Provide these details:
* **Interface Name** -- Enter a name for the subinterface. In the adjacent field, enter a number to identify the subinterface.
* **Comment** -- Enter an alternate name, for example, `AWS VIF dxvif-fh9aokej`.
* **Tag** -- Specify the A-End inner VLAN value associated with the AWS VXC you created in the Megaport Portal.
* **Virtual Router** -- Select a virtual router to the interface, as required by your network.
7. Select the **IPv4** tab.
8. Select **Static** as the Type.
9. Click **+Add** to add a new IP address.
10. Enter the IPv4 address and netmask.
11. Click **OK**.
12. Click **Commit** in the top right corner.
13. Review the changes and click **Commit**.
The new VLAN interface appears with your `ethernet1/1` physical interface.
Next, you will create a security zone so the interface can route traffic.
**To create a security zone**
1. Select the `ethernet1/1.1010` subinterface.
2. Select New Zone from the Security Zone drop-down list.
3. Specify a name for the security zone.
4. Click **+Add** under Interfaces and add `ethernet1/1.1010` to the security zone.
5. Specify any additional details as required for your network security.
6. Select New Zone Protection Profile from the Zone Protection Profile drop-down list.
7. Specify any details as required for your network security. This example uses all the defaults.
8. Click **OK**.
9. Click **OK** in the Layer3 Subinterface screen.
10. Click **Commit** in the top right corner.
11. Review the changes and click **Commit**.
At this point, you have created the interface. Next, you will create the BGP session.
**To create the BGP session**
1. Choose Network > Virtual Routers.
2. Select the virtual router.
3. In the left pane, select BGP.
4. Provide the following BGP details:
* **Enable** -- Select this check box to start the BGP session after committing these changes.
* **Router ID** -- Specify an IP address on this Palo Alto system to use as Router ID. This is the **Customer Address** value from the Megaport connection details.
* **AS Number** -- Specify the ASN you used in the AWS VIF order. This is the Customer ASN value from the AWS connection in the Megaport Portal.
5. Click **+Add** under Auth Profiles.
6. Specify a Profile Name.
7. Enter and confirm the auth password.
8. Click **OK**.
9. Select the **Peer Group** tab.
10. Click **+Add** to add a peer group.
11. Specify a name for the peer group. For example, AWS-VIF-xxxx.
12. Specify eBGP as the session type.
13. Specify any additional details as required for your network.
14. Click **+Add** to add a new peer.
15. Specify the details for the peer:
* **Name** -- Specify a name for the peer.
* **Peer AS** -- Specify the autonomous system number (ASN) for the peer.
* **Local Address** -- Select the proper subinterface and IP address from the drop-down list.
* **Peer Address** -- Enter the AWS side IPv4 address. This is the **Amazon Address** from the Megaport Portal Connection Details.
16. Select the **Connection Options** tab.
17. Select the previously created Auth Profile.
18. Click **OK** in the Peer Group - Peer screen.
19. Click **OK** in the BGP - Peer Group/Peer screen.
20. Click **OK** in the Virtual Router screen.
21. Click **Commit** in the top right corner.
22. Review the changes and click **Commit**.
## Validating your AWS connection
**To check the status of the BGP peer**
1. Choose Network > Virtual Routers.
2. Locate your virtual router (default).
3. Click **More Runtime Stats** in the Runtime Stats column on the right.
4. Select the **BGP** tab, then select the **Peer** tab.
5. Verify that the peer status is *Established*.
You can also check the status in your AWS Direct Connect portal (this might take a few minutes to refresh).
# Creating an Azure Connection for an MVE with Palo Alto VM-Series
Source: https://docs.megaport.com/cloud/mve/palo-alto/azure/index
This help topic describes how to create a VXC from an MVE to Microsoft Azure ExpressRoute and integrate the connection with Palo Alto VM-Series.
You can create a network connection from an MVE (a Palo Alto VM-Series firewall) to Azure ExpressRoute with Virtual Cross Connects (VXCs). You can create either a private connection or a public (Microsoft) connection.
Before you begin, create an MVE (VM-Series). For more information, see [Creating a VM-Series MVE](/mve/palo-alto/creating-mve).
There are three parts to adding an ExpressRoute connection to your MVE and VM-Series.
1. Set up your ExpressRoute plan and deploy the ExpressRoute circuit in the Azure console. When deployed, you get a service key. For additional details, see the Microsoft [ExpressRoute documentation](https://docs.microsoft.com/en-us/azure/expressroute/).
To check the latency and price of connecting to a particular Azure Partner location, start the procedure to [add a connection to Microsoft Azure](#azure-vxc) but instead of providing a **Microsoft Azure Service Key**, click **View all Azure Partner locations**. You can proceed to the Connection Details page without a service key and review the pricing of the selected port. To place an order for a Microsoft Azure connection, you need to provide a service key.
2. In the Megaport Portal, create a connection (VXC) from your MVE to your ExpressRoute location.
3. In VM-Series, create a new interface and add the details of the ExpressRoute connection.
The instructions in this topic describe the second and third parts.
MVE for Palo Alto requires configuration steps in both VM-Series and the Megaport Portal for all cloud connections.
## Adding the ExpressRoute connection in the Megaport Portal
To set up the ExpressRoute connection, you need to create the connection in the Megaport Portal.
**To create a connection to ExpressRoute from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. Click **+Connection** on the MVE.
3. Click the **Cloud** tile.
4. Select Microsoft Azure as the provider.
5. Add the ExpressRoute service key into the **Microsoft Azure Service Key** field.\
The Portal verifies the key then displays the available port locations based on the ExpressRoute region. For example, if your ExpressRoute service is deployed in the Australia East region in Sydney, you can select the Sydney locations.
6. Select the connection point for your first connection.\
To deploy a second connection (and this is recommended), you can create a second VXC - enter the same service key and select the other connection location.
Some helpful links appear on the configuration screen to resources including the Azure Resource Manager console and some tutorial videos.
7. Click **Next**.
8. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit for the VXC will be capped at the maximum allowable based on the ExpressRoute service key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/palo-alto/creating-mve#creating-mve).
* **Preferred A-End VLAN** -- Specify an unused VLAN ID for this connection (for ExpressRoute this is the S-Tag). This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
* **Configure Single Azure Peering VLAN** -- By default, this option is enabled for MVE and we strongly recommend keeping it enabled with Palo Alto VM-Series.\
This option provides a single tag VLAN solution. You configure peering in Azure with the MVE VLAN (A-End) and the peer VLAN set in Azure (B-End). Note, you can have only one peering type (Private or Microsoft) per VXC with this option.
If you do not enable this option, the VXC appears active but it does not recognize traffic.
* **Azure Peering VLAN** -- This value needs to match the A-End VLAN for single tag VLAN peering. A different Azure peering VLAN can also be set, if required.
9. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
When the VXC configuration completes, the VXC icon is green.
In the Azure Resource Management console, the provider status will be `Provisioned`.
When provisioned, you need to configure peerings. You can configure private and Microsoft peering. Click the peer to configure and provide these details:
* **Peer ASN** -- Enter the ASN for the MVE.
* **IPv4 Subnets** -- From each of these subnets, MVE uses the first usable IP address and Microsoft uses the second usable IP for its router.
* **VLAN ID** -- Enter the A-End VLAN from the MVE. (Note, the VLAN ID in the Azure console can be different from the A-End VLAN.)
* **Shared Key** (optional) -- Enter an password for BGP.
## Adding the ExpressRoute connection to VM-Series
After you create the connection from your MVE to Azure and set up the connection in the Azure console, you need to configure it in VM-Series. This involves creating an interface and configuring BGP settings, ASNs, VLANs, and MD5 values.
**To add the Azure Cloud connection in VM-Series**
1. Collect the connection details from the Azure console.\
Display the details of the connection you created in Azure for this connection. Note the values for the **Peer ASN**, **Shared Key**, **VLAN ID**, and **IPv4 Primary Subnet**.
2. Collect the connection details from the Megaport Portal.\
Click the gear icon for the Azure connection from your MVE and click the Details view.
Note the value for the **A-End VLAN**.
3. Log in to the VM-Series.
4. Choose Network > Interfaces.
5. Select the A-End MVE (`ethernet1/1`).
6. Click **Add Subinterface**.
7. Provide these details:
* **Interface Name** -- Enter a name for the subinterface. In the adjacent field, enter a number to identify the subinterface.
* **Comment** -- Enter an alternate name.
* **Tag** -- Specify the A-End VLAN associated with this Azure Connection in the Megaport Portal.
* **Virtual Router** -- Select a virtual router to the interface, as required by your network.
8. Select the **IPv4** tab.
9. Select **Static** as the Type.
10. Click **+Add** to add a new IP address.
11. Enter the IPv4 address and netmask.\
These values are available in the Azure console. The IP addresses and CIDR appear in the **IPv4 Primary Subnet** field; MVE uses the first usable IP address and Azure uses the second usable IP for its router. For this field, enter the MVE (first usable) IP address.
12. Click **OK**.
13. Click **Commit** in the top right corner.
14. Review the changes and click **Commit**.
The new VLAN interface appears with your `ethernet1/1` physical interface.
Next, you will create a security zone so the interface can route traffic.
**To create a security zone**
1. Select the `ethernet1/1.1010` subinterface.
2. Select New Zone from the Security Zone drop-down list.
3. Specify a name for the security zone.
4. Click **+Add** under Interfaces and add `ethernet1/1.1010` to the security zone.
5. Specify any additional details as required for your network security.
6. Select New Zone Protection Profile from the Zone Protection Profile drop-down list.
7. Specify any details as required for your network security. This example uses all the defaults.
8. Click **OK**.
9. Click **OK** in the Layer3 Subinterface screen.
10. Click **Commit** in the top right corner.
11. Review the changes and click **Commit**.
At this point, you have created the interface. Next, you need to create the BGP session.
**To create the BGP session**
1. In VM-Series, choose Network > Virtual Routers.
2. Select the virtual router.
3. In the left pane, select BGP.
4. Provide the following BGP details:
* **Enable** -- Select this check box to start the BGP session after committing these changes.
* **Router ID** -- Enter the first usable IP address from the **IPv4 Primary Subnet** from the Azure console.
* **AS Number** -- Provide the ASN for the MVE connection. Provide the ASN for the MVE connection. Use the **Peer ASN** from the Azure console.
5. Click **+Add** under Auth Profiles.
6. Specify a Profile Name.
7. Enter and confirm the auth password.
8. Click **OK**.
9. Select the **Peer Group** tab.
10. Click **+Add** to add a peer group.
11. Specify a name for the peer group. For example, AWS-xxxx.
12. Specify eBGP as the session type.
13. Specify any additional details as required for your network.
14. Click **+Add** to add a new peer.
15. Specify the details for the peer:
* **Name** -- Specify a name for the peer.
* **Peer AS** -- Specify the Azure-side ASN of 12076. This is a fixed value, and appears in the connection details on the Azure console.
* **Local Address** -- Select the proper subinterface and IP address from the drop-down list.
* **Peer Address** -- Enter the second usable IP address from the **IPv4 Primary Subnet** from the Azure console.
## Validating your Azure connection
**To check the status of the BGP peer**
1. Choose Network > Virtual Routers.
2. Locate your virtual router (default).
3. Click **More Runtime Stats** in the Runtime Stats column on the right.
4. Select the **BGP** tab, and then select the **Peer** tab.
5. Verify that the peer status is *Established*.
# Creating MVE Connections to AWS Direct Connect with Versa Secure SD-WAN
Source: https://docs.megaport.com/cloud/mve/versa/aws/index
This help topic describes how to create a VXC from an MVE to AWS Direct Connect and integrate the connection with Versa Secure SD-WAN.
You can create a network connection from an MVE (a Versa Controller) to AWS with Virtual Cross Connects (VXCs) and AWS Direct Connect. You can create either a Hosted Connection or a Hosted VIF.
You start the AWS connection through the Megaport Portal, accept the connection in AWS, and create an interface for the Edge in Versa Director.
Versa provides documentation for their SD-WAN product, including Versa Director and cloud connections, at [VOS SD-WAN Configuration Product Documentation](https://docs.versa-networks.com/Versa_Operating_System/VOS_SD-WAN_Configuration).
## Before you begin
Before you can create a connection to AWS, you need to satisfy these requirements:
* Create an MVE (Versa Controller). For more information, see [Creating an MVE](/mve/versa/creating-mve).
* In AWS, ensure that you have configured the Direct Connect gateway, AWS gateway, VPCs, and related attachments and associations.
## Creating a connection to AWS from the MVE
With an MVE already created, you can create a connection to AWS. The VXC connection can be one of two AWS models:
* [Hosted Connections](/cloud/mve/versa/aws/mve-aws-hosted) -- A Hosted Connection can support one private, public, or transit virtual interface. Hosted Connections are dedicated connections and are recommended for production environments.
* [Hosted Virtual Interfaces (Hosted VIFs)](/cloud/mve/versa/aws/mve-aws-hvif) -- Hosted VIFs can connect to public or private AWS cloud services: a Hosted VIF cannot connect to a transit virtual interface. Hosted VIF connections share bandwidth.
Click the link for your preferred connection type for detailed configuration steps.
Creating a connection from the MVE instance to AWS is very similar to creating a connection from a Port or an MCR. The primary difference is the process with Versa SD-WAN does not include automatically configure the MVE in Versa and you need to manually create a subinterface and define VLANs, IP addresses, MD5 values, and BGP peers in the Versa Director console.
# Creating an AWS Hosted Connection for an MVE with Versa Secure SD-WAN
Source: https://docs.megaport.com/cloud/mve/versa/aws/mve-aws-hosted
This help topic describes how to create a Hosted Connection from an MVE to AWS Direct Connect and integrate the connection with Versa Secure SD-WAN.
A Hosted Connection can support one private, public, or transit virtual interface. These are dedicated connections and are recommended for production environments.
**To create a connection to an AWS Hosted Connection from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select AWS as the service provider, select Hosted Connection as the AWS Connection Type, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.\
Each destination port has either a blue or red icon to indicate its diversity zone. To achieve diversity, you need to create two connections with each one in a different zone.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection. This value cannot be changed after deployment. The drop-down list displays predefined rate limits available for your MVE, with speeds varying by location and service capabilities.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/versa/creating-mve#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Specify the connection details for the AWS service.
* **AWS Connection Name** -- This is a text field and will be the name of your virtual interface that appears in the AWS console. The AWS Connection Name is automatically populated with the name specified in a
previous step.
* **AWS Account ID** -- This is the ID of the account you want to connect. You can find this value in the management section of your AWS console.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Once the VXC connection is deployed successfully, it appears on the Megaport Portal Services page and is associated with the MVE. Click the VXC title to display the details of this connection. Note that the service status (Layer 2) is up but BGP (Layer 3) will be down because the configuration does not exist yet.
Once deployed in the Megaport Portal, you need to accept the connection in the AWS console and create a Virtual Interface for the connection:
**To accept a Hosted Connection**
1. In AWS, go to **Services > AWS Direct Connect > Connections** and
click the connection name.
2. Click **Accept** at the top right of the window.
The state will be pending for a few minutes while AWS deploys the
connection. After it is deployed, the state changes from *ordering* to
*available.*
The connection is now available, however you need to create a VIF to connect to AWS services.
For more information about accepting AWS connections, see the
[AWS documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/accept-hosted-connection.html).
## Creating a virtual interface
Once you have created and accepted a Hosted Connection, create a VIF and attach the Hosted Connection to a gateway.
AWS provides
[detailed instructions](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-vif.html) for creating Public, Private, and Transit interfaces.
**To create and attach a VIF**
1. In the AWS console, click **Create Virtual Interface**.
2. Select the interface type.
The type will vary depending on the type of service you need to access.
* **Private** -- Access resources running into a VPC using their private IP addresses. You can choose to terminate a private virtual interface on a private virtual gateway (to access a single VPC) or to a Direct Connect gateway (and map up to 10 VPCs to the VIF).
* **Public** -- Access all AWS public endpoints, as well as all AWS resources that are reachable by a public IP address.
* **Transit** -- Transport traffic from a Direct Connect gateway to one or more transit gateways.
3. Specify the configuration details:
* **Virtual interface name** -- Enter a name for the virtual interface.
* **Connection** -- The physical connection where you want this virtual interface to be provisioned. The name you provided for the Hosted Connection in the Megaport Portal appears here.
* **Virtual interface owner** -- The account that will own the virtual interface. Select My AWS account.
* **Direct Connect gateway** -- Select the Direct Connect gateway to attach this virtual interface to. A transit VIF is not directly attached to a Transit gateway, but to a Direct Connect gateway.
* **VLAN** -- The VLAN assigned to the virtual interface. Leave this value as is. The VLAN address is populated and appears to be editable; however, you will get an error if you try to change it.
* **BGP ASN** -- Enter the Border Gateway Protocol (BGP) autonomous system number (ASN) for the MVE side of the BGP session.
The following BGP details can be filled out or left blank. When left blank, they are auto-populated by AWS.
You can also choose whether you want the virtual interface to support Jumbo frames. Enable Jumbo MTU to support an Ethernet packet of 8500 bytes.
4. Click **Create virtual interface**.
To view the VIF details and state, navigate to **Services > AWS Direct Connect > Connections > Name of the Megaport-Created-Hosted Connection**.
BGP hasn’t been configured, so the interface state appears as *down*.
Once you accept the connection and create the VIF in AWS, the VXC state changes to *configured* in the Megaport Portal.
## Adding AWS connection details to Versa Director
After you create the connection from your MVE to AWS and set up the connection in the AWS console, you need to configure it in Versa Director. This involves revising Versa Director templates to add a subinterface for the device and configure BGP settings, ASNs, VLANs, and MD5 values.
**To add a subinterface in Versa Director**
1. Collect the connection details from the AWS console.\
Display the details of the Virtual Interface you created in AWS for this Hosted Connection. Note the values for the **BGP ASN**, **BGP Auth Key**, **Your Peer IP**, and **Amazon Peer IP**.
2. Collect the connection details from the Megaport Portal.
To display the details, click the gear icon for the AWS connection from your MVE and click the **Details** view. Note the values for the **A-End VLAN**.
3. Log in to Versa Director.
4. Select the **Workflows** tab in the top menu bar.
5. Select Template > Templates in the left navigation.
6. Click the template you want to edit, then select the **Interfaces** tab.
7. In the WAN Interfaces section, locate the Sub Interface column and click (Add) to add a subinterface.
A new row appears in the table.
8. Specify these values for the new subinterface.
* **VLAN ID** -- Enter the A-End VLAN value from the Megaport Portal (collected in step 2).
* **Network Name** -- Choose **+ Create WAN Network** from the drop-down menu to open the Create WAN Network window. Specify a meaningful name for the network, click **OK**, and then select the WAN network you created.
* **IPv4** -- Choose Static from the drop-down menu.
9. Select the **Routing** tab to add BGP configuration information.
10. In the BGP section, select the network name in the Network column.
11. Specify the following values according to your MVE configuration:
* **Local AS** -- This is the BGP ASN (your local MVE), collected in Step 1.
* **Neighbor IP Address** -- This is the Amazon Peer IP address, collected in Step 1.
* **Peer AS** -- This is the AWS ASN. By default, this value is 64512.
* Optionally, you can enable BFD (as appropriate for your network).
12. Click (Add) to the right of the settings.
13. Select the **Management Servers** tab, then click **Recreate** or **Create** (at the bottom of the page).
A window opens that shows the differences of the configuration. The auto-merged version is recommended, and selected by default.
14. Click **Deploy**.
You can use variables in the template to specify values per device for these fields: **Router ID**, **Local AS**, **Peer AS**, **Static IP address**, and **Password**.
The Instance ID cannot be modified (the system automatically specifies a value) and Static Address is parameterized by default.
**To parameterize Router ID, BGP Local AS, Peer AS, and Password**
1. Select the **Configuration** tab in the top menu bar.
2. Select **Templates** > **Device Templates** in the horizontal menu bar.
3. Click your template.
By default, the Interfaces column appears.
4. In the left navigation, select **Virtual Routers**, and click your device to open the Edit window.
5. In the Edit window, select BGP, then click the Instance ID to open the Edit BGP Instance window.
6. In the Edit BGP Instance window, click (Parameterize) next to each of the following fields: **Router ID**, **Local AS**, **Peer AS**, and **Password**.
7. Click **OK** two times to update.
8. Select the **Workflows** tab in the top menu bar, then select Devices > Devices in the left navigation.
9. Click your device to specify values for the variables you just created.
The Add Device window opens.
10. Select the **Bind Data** tab.
11. Specify values for the variables.
* **Local AS** -- Enter the Customer (MVE) ASN.
* **Password** -- Enter the MD5 password.
* **Peer AS** -- Enter the Amazon-side ASN.
* **Router ID** -- Enter the Customer (MVE) IP address (your local IP address).
* **Hop Address** -- Enter the Amazon IP address.
* **Static Address** -- Enter the Customer IP address (your MVE IP address, including the mask value).
12. Click **Redeploy** when finished.
When the new configurations for the device are prepared successfully, a green checkmark appears at the bottom of the Versa Director window.
13. To push the changes to the device, click **Commit Template** (on the upper right).
The Commit Template to Devices window opens.
14. Specify the following in the Commit Template to Devices window:
* **Organization** -- Select your organization from the drop-down menu.
* **Select Template** -- Select the template to push to the device from the drop-down menu.
Note that the Template State is OUT\_OF\_SYNC.
15. Click the eye icon in the Differences column to verify your configuration changes.
16. Click **Commit to Device**.
A green checkmark appears at the bottom right of the screen when the push is successful. The Template State is now IN\_SYNC.
## Validating your AWS connection
1. Select the **Monitor** tab in the top navigation bar, select Devices in the horizontal navigation bar, and then select your device to view details in the Summary screen.
2. In the Summary screen you can review your subinterface in the Interface column, and the Operational and Admin Status.
3. In the AWS Direct Connect portal, refresh the screen and verify that the Virtual interface state is available and BGP Status is up. An AWS BGP session that is up looks like this:
# Creating an AWS Hosted VIF for an MVE with Versa Secure SD-WAN
Source: https://docs.megaport.com/cloud/mve/versa/aws/mve-aws-hvif
This help topic describes how to create a Hosted VIF from an MVE to AWS Direct Connect and integrate the connection with Versa Secure SD-WAN.
Hosted VIFs can connect to public or private AWS cloud services: a Hosted VIF cannot connect to a transit virtual interface. These connections share bandwidth.
AWS Hosted Virtual Interfaces (Hosted VIF) do not support diversity zones. To ensure connection diversity for Hosted VIFs, create VXCs to two destination ports in different data centers, instead of two ports in separate diversity zones.
**To create a connection to an AWS Hosted VIF from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select AWS as the service provider, select Hosted VIF as the AWS Connection Type, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
Match this to the AWS Connection Name on the next screen for easy mapping.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Accepted values start at 1 Mbps and scale in 1 Mbps increments. Maximum available speed depends on location and service availability. Note the sum of all hosted virtual VXCs to a service can exceed the MVE capacity, but the total aggregate will never burst beyond the MVE capacity.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/versa/creating-mve#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Specify the details for the AWS service.
Here are details for each field:
* Select **Public** or **Private**.
* **Private** -- Access private AWS services such as a VPC, EC2
instances, load balancers, RDS DB instances, on private IP address space.
* **Public** -- Access public AWS services such as Amazon Simple Storage
Service (S3), DynamoDB, CloudFront, and Glacier. You will also receive
[Amazon's global IP prefixes](https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html)
(approximately 2,000 prefixes).
Public VIFs require manual intervention from Amazon and could take up to 72 hours. For more information, see [Configuring Public AWS Connections with IP Addresses Provided by AWS](/cloud/megaport/aws/aws-public-ip).
* **AWS Connection Name** -- This is a text field and will be the name
of your virtual interface that appears in the AWS console. The AWS
Connection Name is automatically populated with the name specified in a
previous step.
* **AWS Account ID** -- This is the ID of the account you want to
connect. You can find this value in the management section of your
AWS console.
* **Customer ASN** (optional) -- Specify the ASN used for
BGP peering sessions on any VXCs connected to the MVE. This value
is defined when you configure the MVE and, once defined, it cannot
be changed.
* **BGP Auth Key** (optional) -- Specify the BGP key. If you leave this blank, Megaport negotiates a key automatically for you with AWS which will be displayed in the Megaport Portal. The key is not displayed in the AWS console.
The BGP Auth Key is generated during the ordering process when this field is left blank. It will not be displayed on the Summary page when ordering. To see the key, view the Connection Settings after the service has been deployed and is live.
* **Customer IP Address** -- The IP address space (in CIDR format) used on your network for peering. This field is optional for private connections and if left blank, Megaport assigns an address.
* **Amazon IP Address** -- The IP address space in CIDR format
assigned in the AWS VPC network for peering. This field is
optional for private connections and if left blank, Megaport automatically assigns an
address.
* **Prefixes** (optional) -- (visible for Public connections only) Specify IP Prefixes to announce to AWS. Specify the prefixes you will advertise when deploying a Public Direct Connect (RIR-assigned IPv4 addresses only).
Once you configure Prefixes for a Public connection, you cannot change them and the field is grayed out. To change this value, create a support ticket with AWS so they can make this change in a non-impacting way. Or, you can cancel the Hosted VIF and reorder. In both cases, you need to wait for AWS to manually approve the request.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
The AWS VXC appears as a connection for the MVE in the Megaport Portal.
Next, accept the connection in AWS.
#### Accepting the Virtual Interface for Private Connections
A few minutes after ordering a private Hosted VIF VXC, the
corresponding inbound VIF request is visible on the AWS Direct
Connect > Virtual Interfaces page in the AWS console. (This is specific to the region associated with the target AWS port.) If your VIF doesn't appear after a few minutes, confirm you are viewing the correct region.
**To review and accept the private virtual interface**
1. From the AWS Direct Connect > Virtual Interfaces page, click the ID
of the interface to display the configuration and peering details.
The name and account ID of the VIF should match the values supplied in
the Portal and the BGP ASN should match the Customer ASN configured with
the VXC. The Amazon ASN is the default region's AWS ASN and
not the value specified during the configuration - this is
updated when the virtual interface is accepted and
assigned.
2. Click **Accept**.
3. Select the gateway type and then the specific gateway for this new
virtual interface.
4. Click **Accept virtual interface**.
The state of the connection changes from *confirming* to *pending*, and then changes to *available* once BGP is established. Note that sometimes there is a delay in the *available* BGP status appearing on the AWS end, though you can confirm the current state of the Layer 3 link through the Portal view.
#### Accepting the Virtual Interface for Public Connections
Several minutes after ordering a public Hosted VIF VXC, the
corresponding inbound VIF request appears on the **AWS Direct
Connect > Virtual Interfaces** page in the AWS console. (This is specific to the region associated with the target AWS port.)
**To review and accept the public virtual interface**
1. From the AWS Direct Connect > Virtual Interfaces page, click the ID
of the interface to display the configuration and peering details.
2. Review the configuration details and click **Accept**, and when
prompted, click **Confirm**.
The state of the connection changes from *confirming* to *verifying*. At
this point, the connection needs to be verified by Amazon - a process
that can take up to 72 hours. When verified, the state changes to
*available*.
## Adding AWS connection details to Versa Director
After you create the connection from your MVE to AWS and set up the connection in the AWS console, you need to configure it in Versa Director. This involves revising Versa Director templates to add a device interface and configure BGP settings, ASNs, VLANs, and MD5 values.
**To add a subinterface in Versa Director**
1. Collect the connection details from the Megaport Portal.
To display the details, click the gear icon for the AWS connection from your MVE and click the **Details** view. Note the values for the **A-End VLAN**, **Customer Address** (and **CIDR**), **Amazon IP Address**, and **Customer ASN**.
2. Log in to Versa Director.
3. Select the **Workflows** tab in the top menu bar.
4. Select Template > Templates in the left navigation.
5. Click the template you want to edit, then select the **Interfaces** tab.
6. In the WAN Interfaces section, locate the Sub Interface column and click (Add) to add a subinterface.
A new row appears in the table.
7. Specify these values for the new subinterface.
* **VLAN ID** -- Enter the VLAN value from the Megaport Portal.
* **Network Name** -- Choose **+ Create WAN Network** from the drop-down menu to open the Create WAN Network window. Specify a meaningful name for the network, click **OK**, and then select the WAN network you created.
* **IPv4** -- Choose Static from the drop-down menu.
8. Select the **Routing** tab to add BGP configuration information.
9. In the BGP section, select the network name for the connection in the Network column.
10. Specify the following values according to your MVE configuration:
* **Local AS** -- This is the Customer ASN (your local MVE), collected in Step 1.
* **Neighbor IP Address** -- This is the Amazon IP address, collected in Step 1.
* **Peer AS** -- This is the AWS ASN. By default, this value is 64512.
* Optionally, you can enable BFD (as appropriate for your network).
11. Click (Add) to the right of the settings.
12. Click **Recreate** (at the bottom of the page).
A window opens that shows the differences of the configuration. The auto-merged version is recommended, and selected by default.
13. Click **Deploy**.
You can use variables in the template to specify values per device for these fields: **Router ID**, **Local AS**, **Peer AS**, **Static IP address**, and **Password**.
The Instance ID cannot be modified (the system automatically specifies a value) and **Static IP Address** is parameterized by default.
**To parameterize Router ID, BGP Local AS, Peer AS, and Password**
1. Select the **Configuration** tab in the top menu bar.
2. Select **Templates** > **Device Templates** in the horizontal menu bar.
3. Click your template.
By default, the Interfaces column appears.
4. In the left navigation, select **Virtual Routers**, and click your device to open the Edit window.
5. In the Edit window, select BGP, then click the Instance ID to open the Edit BGP Instance window.
6. In the Edit BGP Instance window, click (Parameterize) next to each of the following fields: **Router ID**, **Local AS**, **Peer AS**, and **Password**.
7. Click **OK** two times to update.
8. Select the **Workflows** tab in the top menu bar, then select Devices > Devices in the left navigation.
9. Click your device to specify values for the variables you just created.
The Add Device window opens.
10. Select the **Bind Data** tab.
11. Specify values for the variables.
* **Local AS** -- Enter the Customer ASN.
* **Password** -- Enter the MD5 password.
* **Peer AS** -- Enter the Amazon side ASN.
* **Router ID** -- Enter the Customer IP address (your local IP address).
* **Hop Address** -- Enter the Amazon IP address.
* **Static Address** -- Enter the Customer IP address (your local IP address, including the mask value).
12. Click **Redeploy** when finished.
When the new configurations for the device are prepared successfully, a green checkmark appears at the bottom of the Versa Director window.
13. To push the changes to the device, click **Commit Template** (on the upper right).
The Commit Template to Devices window opens.
14. Specify the following in the Commit Template to Devices window:
* **Organization** -- Select your organization from the drop-down menu.
* **Select Template** -- Select the template to push to the device from the drop-down menu.
Note that the Template State is OUT\_OF\_SYNC.
15. Click the eye icon in the Differences column to verify your configuration changes.
16. Click **Commit to Device**.
A green checkmark appears at the bottom right of the screen when the push is successful. The Template State is now IN\_SYNC.
17. Close the window.
## Validating your AWS connection
1. Select the **Monitor** tab in the top navigation bar, select Devices in the horizontal navigation bar, and then select your device to view details in the Summary screen.
2. In the Summary screen you can review your subinterface in the Interface column, and the Operational and Admin Status.
3. In the AWS Direct Connect portal, refresh the screen and verify that the Virtual interface state is available and BGP Status is up. An AWS BGP session that is up looks like this:
**To view the BGP status for a device in Versa Director**
1. Log in to Versa Director.
2. Select the **Monitor** tab in the top menu bar.
3. Select your device from the list.
4. Scroll to the Health Monitor.
5. Click **BGP Adjacencies** to view the BGP status.
6. Verify whether the BGP status for the device is *Established*.
# Creating Connections from MVE to AWS Direct Connect with Arista VeloCloud SD-WAN
Source: https://docs.megaport.com/cloud/mve/vmware/aws/index
This help topic describes how to create a VXC from an MVE to AWS Direct Connect and integrate the connection with Arista VeloCloud SD-WAN.
You can create a network connection from an MVE for Arista VeloCloud SD-WAN (an *Edge*) to AWS with a Virtual Cross Connects (VXC) and AWS Direct Connect. You can create either a [Hosted Connection](/cloud/megaport/aws#hosted) or a [Hosted Virtual Interface (Hosted VIF)](/cloud/megaport/aws#vif).
You start the AWS connection through the Megaport Portal, accept the connection in AWS, and create a subinterface for the edge in Orchestrator.
Arista provides documentation for their SD-WAN product, including cloud connections, at [VeloCloud SD-WAN Documentation](https://www.arista.com/en/admin-guide-vc-6-4).
## Before you begin
Before you can create a connection to AWS, you need to satisfy these requirements:
* Create an MVE (Edge). For more information, see [Creating an MVE](/mve/vmware/creating-mve).
* In AWS, ensure that you have configured the Direct Connect gateway, AWS gateway, VPCs, and related attachments and associations.
## Creating a connection to AWS from the MVE
With an MVE already created, you can create a connection to AWS.
The VXC connection can be one of two AWS models:
* [Hosted Connections](/cloud/mve/vmware/aws/mve-aws-hosted) -- A Hosted Connection can support one private, public, or transit virtual interface. Hosted Connections are dedicated connections and are recommended for production environments.
* [Hosted Virtual Interfaces (Hosted VIFs)](/cloud/mve/vmware/aws/mve-aws-hvif) -- Hosted VIFs can connect to public or private AWS cloud services: a Hosted VIF cannot connect to a transit virtual interface. Hosted VIF connections share bandwidth.
Click the link for your preferred connection type for detailed configuration steps.
Creating a connection from the MVE instance to AWS is very similar to creating a connection from a Port or an MCR. The primary difference is the process with Arista VeloCloud SD-WAN does not automatically configure the MVE in Orchestrator and you need to manually create a subinterface and define VLANs, IP addresses, MD5 values, and BGP peers in the Orchestrator console.
# Creating an AWS Hosted Connection for an MVE with Arista VeloCloud SD-WAN
Source: https://docs.megaport.com/cloud/mve/vmware/aws/mve-aws-hosted
This help topic describes how to create a Hosted Connection from an MVE to AWS Direct Connect and integrate the connection with Arista VeloCloud SD-WAN.
A Hosted Connection can support one private, public, or transit virtual interface. Hosted Connections are dedicated connections and are recommended for production environments.
**To create a connection to an AWS Hosted Connection from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select AWS as the service provider, select Hosted Connection as the AWS Connection Type, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.\
Each destination port has either a blue or red icon to indicate its diversity zone. To achieve diversity, you need to create two connections with each one in a different zone.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection. This value cannot be changed after deployment. The drop-down list displays predefined rate limits available for your MVE, with speeds varying by location and service capabilities.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/vmware/creating-mve#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Specify the connection details for the AWS service.
* **AWS Connection Name** -- This is a text field and will be the name
of your virtual interface that appears in the AWS console. The AWS
Connection Name is automatically populated with the name specified in a
previous step.
* **AWS Account ID** -- This is the ID of the account you want to
connect. You can find this value in the management section of your
AWS console.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
Once the VXC connection is deployed successfully, it appears on the Megaport Portal Services page and is associated with the MVE. Click the VXC title to display the details of this connection. Note that the service status (Layer 2) is up but BGP (Layer 3) will be down because the configuration does not exist yet.
Once deployed in the Megaport Portal, you need to accept the connection in the AWS console and create a Virtual Interface for the connection:
**To accept a Hosted Connection**
1. In AWS, go to **Services > AWS Direct Connect > Connections** and
click the connection name.
2. Click **Accept** at the top right of the window.
The state will be pending for a few minutes while AWS deploys the
connection. After it is deployed, the state changes from *ordering* to
*available*.
The connection is now available, however you need to create a VIF to connect to AWS services.
For more information about accepting AWS connections, see the
[AWS documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/accept-hosted-connection.html).
## Creating a virtual interface
Once you have created and accepted a Hosted Connection, create a VIF and attach the Hosted Connection to a gateway.
AWS provides
[detailed instructions](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-vif.html) for creating Public, Private, and Transit interfaces.
**To create and attach a VIF**
1. In the AWS console, click **Create Virtual Interface**.
2. Select the interface type.
The type will vary depending on the type of service you need to access.
* **Private** -- Access resources running into a VPC using their private IP addresses. You can choose to terminate a private virtual interface on a private virtual gateway (to access a single VPC) or to a Direct Connect gateway (and map up to 10 VPCs to the VIF).
* **Public** -- Access all AWS public endpoints, as well as all AWS resources that are reachable by a public IP address.
* **Transit** -- Transport traffic from a Direct Connect gateway to one or more transit gateways.
3. Specify the configuration details:
* **Virtual interface name** -- Enter a name for the virtual interface.
* **Connection** -- The physical connection where you want this virtual interface to be provisioned. The name you provided for the Hosted Connection in the Megaport Portal appears here.
* **Virtual interface owner** -- The account that will own the virtual interface. Select My AWS account.
* **Direct Connect gateway** -- Select the Direct Connect gateway to attach this virtual interface to. A transit VIF is not directly attached to a Transit gateway, but to a Direct Connect gateway.
* **VLAN** -- The VLAN assigned to the virtual interface. Leave this value as is. The VLAN address is populated and appears to be editable; however, you will get an error if you try to change it.
* **BGP ASN** -- Specify the Border Gateway Protocol (BGP) autonomous system number (ASN) for the MVE side of the BGP session.
The following BGP details can be specified or left blank. When left blank, they are auto-populated by AWS.
You can also choose whether you want the virtual interface to support Jumbo frames. Enable Jumbo MTU to support an Ethernet packet of 8500 bytes.
4. Click **Create virtual interface**.
To view the VIF details and state, navigate to **Services > AWS Direct Connect > Connections > Name of the Megaport-Created-Hosted Connection**.
BGP hasn’t been configured, so the interface state appears as *down*.
Once you accept the connection and create the VIF in AWS, the VXC state changes to *configured* in the Megaport Portal.
## Adding AWS connection details to Orchestrator
After you create the connection from your MVE to AWS and set up the connection in the AWS console, you need to configure it in Orchestrator. This involves configuring BGP settings, ASNs, VLANs, and MD5 values.
**To add the AWS connection in Orchestrator**
1. Collect the connection details from the AWS console.\
Display the details of the Virtual Interface you created in AWS for this Hosted Connection. Note the values for the **BGP ASN**, **BGP Auth Key**, **Your Peer IP**, and **Amazon Peer IP**.
2. Collect the connection details from the Megaport Portal.\
Click the gear icon for the AWS connection from your MVE and click the Details view.
Note the value for the **A-End VLAN**.
For more information about adding an AWS connection in Orchestrator, see [Amazon Web Services (AWS) Configuration Procedure (Arista)](https://www.arista.com/en/admin-guide-vc-6-4/sd-wan-6-4-configuring-amazon-web-services#:~:text=Create%20a%20Connect%20Attachment%20using,configured%20on%20the%20VeloCloud%20Edge.).
**To configure BGP for the AWS connection in Orchestrator**
For more information about how to configure BGP for the AWS connection in Orchestrator, see [Configuring BGP (Arista)](https://www.arista.com/en/admin-guide-vc-6-4/sd-wan-6-4-configuring-dynamic-routing-with-ospf-or-bgp#configure_bgp).
You can also check connectivity and BGP status from the CLI of the edge device. For more information, see [Reviewing your VeloCloud MVE connection settings](/cloud/mve/vmware/generic/mve-vxc-details).
# Creating an AWS Hosted VIF for an MVE with Arista VeloCloud SD-WAN
Source: https://docs.megaport.com/cloud/mve/vmware/aws/mve-aws-hvif
This help topic describes how to create a Hosted VIF from an MVE to AWS Direct Connect and integrate the connection with Arista VeloCloud SD-WAN.
Hosted VIFs can connect to public or private AWS cloud services: a Hosted VIF cannot connect to a transit virtual interface. These connections share bandwidth.
AWS Hosted Virtual Interfaces (Hosted VIF) do not support diversity zones. To ensure connection diversity for Hosted VIFs, create VXCs to two destination ports in different data centers, instead of two ports in separate diversity zones.
**To create a connection to an AWS Hosted VIF from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select AWS as the service provider, select Hosted VIF as the AWS Connection Type, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
Match this to the AWS Connection Name on the next screen for easy mapping.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Accepted values start at 1 Mbps and scale in 1 Mbps increments. Maximum available speed depends on location and service availability. Note the sum of all hosted virtual VXCs to a service can exceed the MVE capacity, but the total aggregate will never burst beyond the MVE capacity.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/vmware/creating-mve#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Specify the details for the AWS service.
Here are details for each field:
* Select **Public** or **Private**.
* **Private** -- Access private AWS services such as a VPC, EC2
instances, load balancers, RDS DB instances, on private IP address
space.
* **Public** -- Access public AWS services such as Amazon Simple Storage
Service (S3), DynamoDB, CloudFront, and Glacier. You will also receive
[Amazon's global IP
prefixes](https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html)
(approximately 2,000 prefixes).
Public VIFs require manual intervention from Amazon and could take up to 72 hours. For more information, see [Configuring Public AWS Connections with IP Addresses Provided by AWS](/cloud/megaport/aws/aws-public-ip).
* **AWS Connection Name** -- This is a text field and will be the name
of your virtual interface that appears in the AWS console. The AWS
Connection Name is automatically populated with the name specified in a
previous step.
* **AWS Account ID** -- This is the ID of the account you want to
connect. You can find this value in the management section of your
AWS console.
* **Customer ASN** (optional) -- Specify the ASN used for
BGP peering sessions on any VXCs connected to the MVE. This value
is defined when you configure the MVE and, once defined, it cannot
be changed.
* **BGP Auth Key** (optional) -- Specify the BGP key. If you leave this blank, Megaport negotiates a key automatically for you with AWS which will be displayed in the Megaport Portal. The key is not displayed in the AWS console.
The BGP Auth Key is generated during the ordering process when this field is left blank. It will not be displayed on the Summary page when ordering. To see the key, view the Connection Settings after the service has been deployed and is live.
* **Customer IP Address** -- The IP address space (in CIDR format) used on your network for peering. This field is optional for private connections and if left blank, Megaport assigns an address.
* **Amazon IP Address** -- The IP address space in CIDR format
assigned in the AWS VPC network for peering. This field is
optional for private connections and if left blank, Megaport automatically assigns an
address.
* **Prefixes** (optional) -- (visible for Public connections only) Specify IP Prefixes to announce to AWS. Specify the prefixes you will advertise when deploying a Public Direct Connect (RIR-assigned IPv4 addresses only).
Once you configure Prefixes for a Public connection, you cannot change them and the field is grayed out. To change this value, create a support ticket with AWS so they can make this change in a non-impacting way. Or, you can cancel the Hosted VIF and reorder. In both cases, you need to wait for AWS to manually approve the request.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
The AWS VXC appears as a connection for the MVE in the Megaport Portal.
Next, accept the connection in AWS.
#### Accepting the Virtual Interface for Private Connections
A few minutes after ordering a private Hosted VIF VXC, the
corresponding inbound VIF request is visible on the AWS Direct
Connect > Virtual
Interfaces page in the AWS console. (This is specific to the region associated with
the target AWS port.) If your VIF doesn't appear after a few minutes,
confirm that you are viewing the correct region.
For more information about accepting a Direct Connect virtual interface, see [Accept a hosted Direct Connect virtual interface](https://docs.aws.amazon.com/directconnect/latest/UserGuide/accepthostedvirtualinterface.html).
The state of the connection changes from *Confirming* to *Pending*, and then changes to *Available* once BGP has established. Note that sometimes there is a delay in the *Available* BGP status appearing on the AWS end, though you can confirm the current state of the Layer 3 link through the Portal view.
#### Accepting the Virtual Interface for Public Connections
Several minutes after ordering a public Hosted VIF VXC, the
corresponding inbound VIF request appears on the AWS Direct
Connect > Virtual Interfaces page in the AWS console. (This is specific to the region associated with
the target AWS port.)
For more information about accepting a Direct Connect virtual interface, see [Accept a hosted Direct Connect virtual interface](https://docs.aws.amazon.com/directconnect/latest/UserGuide/accepthostedvirtualinterface.html).
The state of the connection changes from *Confirming* to *Verifying*. At this point, the connection needs to be verified by Amazon - a process that can take up to 48 hours. When verified, the state changes to *Available*.
## Adding AWS connection details to Orchestrator
After you create the connection from your MVE to AWS and set up the connection in the AWS console, you need to configure it in Orchestrator. This involves configuring BGP settings, ASNs, VLANs, and MD5 values.
**To add the AWS connection in Orchestrator**
1. Collect the connection details from the Megaport Portal.\
To display the details, click the gear icon for the AWS connection from your MVE and click the Details view. Note the values for the **A-End VLAN**, **Customer Address** (and CIDR), and **Amazon Address**.
2. In Orchestrator, go to Configure > Edges and click the MVE device.
3. Select the **Device** tab and scroll down to the Interface Settings.
4. Click **+Add Subinterface**.
The Select Interface dialog box appears.
5. From the Select Interface menu, choose GE3 and for the **Subinterface ID** enter the A-End VLAN ID configured on the MVE in the Megaport Portal.
The subinterface settings appear.
6. Change the **Addressing Type** to Static and provide the **IP Address**, **CIDR value**, and **Gateway**.\
These values are available in the connection details on the Megaport Portal. The IP address and CIDR appear in the **Customer Address** field; the Gateway appears in the **Amazon Address** field.
7. Ensure **Enable VLAN Tagging** is enabled.\
The field is automatically populated with the VLAN ID you specified for the subinterface ID.
8. Click \*\*Update GE3:\*\**vlan-id*.
9. In the upper-right corner of the Configure > Edges window, click **Save Changes** and then confirm.\
This configures the interface, VLAN tags, and IP addresses so you can test with ping commands through the CLI. (BGP is not yet configured.)
Adding the subinterface momentarily disrupts the connection.
**To configure BGP for the AWS connection in Orchestrator**
1. In Orchestrator, go to Configure > Edges and click the MVE device.
2. Select the **Device** tab and in the Configure Segments section click **Enable Edge Override** for BGP Settings.\
This override lets us define BGP values specific for this device beyond the profile definition.
3. Click the toggle button to turn on BGP and click **Edit**.\
The BGP Editor appears.
4. For **Local ASN**, add the **Customer ASN** from the Megaport connection details.
5. For the **Neighbor IP**, add the **Amazon Address** from the Megaport connection details.
6. Add the Amazon ASN to the **ASN** field for the neighbor.\
By default this is 64512.
7. View all Additional Options and select **MD5 Auth** and enter your **MD5 Password** from the Megaport connection details.
8. Click **OK** and then click **Save Changes**.
## Validating your connection
The BGP connection can take approximately 5 minutes to establish. Once connected, you can verify the connection in both Orchestrator and AWS.
Under Test & Troubleshoot > Remote Diagnostics, select the MVE and click **Run** for **Troubleshoot BGP - Show BGP Summary** to verify the BGP session and ensure the AWS router is up.
For more information, see [Testing and Troubleshooting (Arista)](https://www.arista.com/en/admin-guide-vc-6-4/sd-wan-6-4-testing-and-troubleshooting)
You can also check connectivity and BGP status from the CLI of the edge device. For more information, see [Reviewing MVE MVE Connection Settings in Arista VeloCloud SD-WAN](/cloud/mve/vmware/generic/mve-vxc-details).
From the AWS console, confirm the state of the Virtual Interface (under the General Configuration tab) is *available*. The state changes to available when the BGP connection is established.
# Creating an Azure ExpressRoute Connection for an MVE with Arista VeloCloud SD-WAN
Source: https://docs.megaport.com/cloud/mve/vmware/azure/index
This help topic describes how to create a VXC from an MVE to Microsoft Azure ExpressRoute and integrate the connection with Arista VeloCloud SD-WAN.
You can create a network connection from an MVE (an Arista VeloCloud edge) to Azure ExpressRoute with Virtual Cross Connects (VXCs). You can create either a private connection or a public (Microsoft) connection.
Before you begin, create an MVE in Orchestrator. For more information, see [Creating an MVE Integrated with Arista VeloCloud SD-WAN](/mve/vmware/creating-mve).
There are three parts to adding an ExpressRoute connection to your MVE and Orchestrator.
1. Set up your ExpressRoute plan and deploy the ExpressRoute circuit in the Azure console. When deployed, you get a service key. For additional details, see the Microsoft [ExpressRoute documentation](https://docs.microsoft.com/en-us/azure/expressroute/).
To check the latency and price of connecting to a particular Azure Partner location, start the procedure to [add a connection to Microsoft Azure](#azure-vxc) but instead of providing a **Microsoft Azure Service Key**, click **View all Azure Partner locations**. You can proceed to the Connection Details page without a service key and review the pricing of the selected port. To place an order for a Microsoft Azure connection, you need to provide a service key.
2. In the Megaport Portal, create a connection (VXC) from your MVE to your ExpressRoute location.
3. In Orchestrator, create a new interface and add the details of the Azure connection.
The instructions in this topic describe the second and third parts.
MVE for Arista VeloCloud SD-WAN requires configuration steps in both VMware Orchestrator and the Megaport Portal for all cloud connections.
## Adding the ExpressRoute connection in the Megaport Portal
To set up the ExpressRoute connection, you need to create the connection in the Megaport Portal.
**To create a connection to ExpressRoute from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. Click **+Connection** on the MVE.
3. Click the **Cloud** tile.
4. Select Microsoft Azure as the provider.
5. Add the ExpressRoute service key into the **Microsoft Azure Service Key** field.\
The Portal verifies the key then displays the available port locations based on the ExpressRoute region. For example, if your ExpressRoute service is deployed in the Australia East region in Sydney, you can select the Sydney locations.
6. Select the connection point for your first connection.\
To deploy a second connection (and this is recommended), you can create a second VXC - enter the same service key and select the other connection location.
Some helpful links appear on the configuration screen to resources including the Azure Resource Manager console and some tutorial videos.
7. Click **Next**.
8. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit for the VXC will be capped at the maximum allowable based on the ExpressRoute service key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/vmware/creating-mve#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection (for ExpressRoute this is the S-Tag). This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
* **Configure Single Azure Peering VLAN** -- By default, this option is enabled for MVE and we strongly recommend keeping it enabled.\
This option provides a single tag VLAN solution. You configure peering in Azure with the MVE VLAN (A-End) and the peer VLAN set in Azure (B-End). Note, you can have only one peering type (Private or Microsoft) per VXC with this option.
If you do not enable this option, the VXC appears active but it does not recognize traffic.
* **Azure Peering VLAN** -- This value needs to match the A-End VLAN for single tag VLAN peering. A different Azure peering VLAN can also be set, if required.
9. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
When the VXC configuration completes, the VXC icon is green.
In the Azure Resource Management console, the provider status will be `Provisioned`.
When provisioned, you need to configure peerings. You can configure private and Microsoft peering. Click the peer to configure and provide these details:
* **Peer ASN** -- Enter the ASN for the MVE.
* **IPv4 Subnets** -- From each of these subnets, MVE uses the first usable IP address and Microsoft uses the second usable IP for its router.
* **VLAN ID** -- Enter the A-End VLAN from the MVE. (Note, the VLAN ID in the Azure console can be different from the A-End VLAN.)
* **Shared Key** (optional) -- Enter a password for BGP.
## Adding Azure connection details to Orchestrator
After you create the connection from your MVE to Azure and set up the connection in the Azure console, you need to configure it in Orchestrator. This involves configuring BGP settings, ASNs, VLANs, and MD5 values.
**To add the Azure Cloud connection in Orchestrator**
1. Collect the connection details from the Azure console.\
Display the details of the connection you created in Azure for this connection. Note the values for the **Peer ASN**, **Shared Key**, **VLAN ID**, and **IPv4 Primary Subnet**.
2. Collect the connection details from the Megaport Portal.\
Click the gear icon for the Azure connection from your MVE and click the Details view.
Note the value for the **A-End VLAN**.
3. For the Orchestrator steps, see [Adding edge details to Orchestrator](/mve/vmware/connect-mve-to-mve#adding-edge-details-to-orchestrator) in the [Connect MVE to MVE topic](/mve/vmware/connect-mve-to-mve). The steps are the same for adding the Azure connection details to Orchestrator.
## Validating your connection
Use Orchestrator to validate your connection.
For more information, see the [VeloCloud Orchestrator Guide](https://www.arista.com/en/orchestrator-guide-vc-6-4)
You can also check connectivity and BGP status from the CLI of the edge device. For more information, see [Reviewing your VMware MVE connection settings](/cloud/mve/vmware/generic/mve-vxc-details).
# NAT Gateway Cloud Connectivity Overview
Source: https://docs.megaport.com/cloud/nat/index
This help topic provides an overview of NAT Gateway cloud connectivity.
Megaport NAT Gateway (NAT Gateway) provides virtual routing capabilities for on-demand private connectivity at Layer 3.
NAT Gateway is preconfigured in data centers in key routing zones around the world, enabling data transfer between:
* Multicloud and hybrid cloud environments
* Network service providers
* Cloud service providers
Without physical infrastructure, you can use cloud-to-cloud networking, private peering between leading public cloud, and providers, and direct connectivity to any provider on the Megaport software-defined network (SDN). There is no need to own and maintain equipment and no IP address or autonomous system numbers to procure.
Click a Cloud Service Provider link in the site navigation to get started.
For more information about NAT Gateway, see [Megaport NAT Gateway Overview](/nat).
## Using a service key
You can create a service key that allows you to share your service with another Megaport account holder.
For more information, see [Setting up Service Keys](/marketplace/service-keys/).
# AMS-IX Connectivity
Source: https://docs.megaport.com/ix/ams
This help topic describes how Megaport works with the AMS internet peering exchange.
AMS-IX operates a series of Internet Peering Exchanges (IXs) globally and partners with Megaport in several cities. IXs can exchange data traffic between networks more directly and efficiently, reducing bandwidth usage on network uplink connections.
**To join an Internet Exchange for an AMS-IX location**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.\
If you haven't already created a Port, see
[Creating a Port](/connections/creating-port).
2. Add a connection for the Port.\
If this is the first connection for the Port, click the AMS-IX tile. The tile is a shortcut to the configuration page. Alternatively, click **+Connection**, click **Cloud**, then click **AMS-IX**.
3. Select the AMS-IX location for peering and click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Enter the purchase order number specified when registering the billing market.
* **Rate Limit** -- The speed of your connection in Mbps, up to the maximum speed of the Port.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
This must be a unique VLAN ID on this Port and can range from 2 to 4093.\
Alternatively, you can select **Untagged** to remove the VLAN tagging for this connection. The untagged option limits you to only one IX (or VXC) deployed on this Port.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Specify the AMS-IX details:
* **Peer with Route Servers?** -- The route server facilitates the implementation of peering arrangements. Normally, you maintain separate BGP sessions to each peer's routers. With a route server, you can replace all or a subset of these sessions with one session.
There are two main types of IX peering arrangements: multilateral and bilateral. A multilateral session connects to BGP peers with the available route servers, you advertise your routes to the route servers, and all routes available from all other multilaterally peered connections are advertised to your peer from the route servers. The second type of peering is bilateral peering. This method is required for peers that do not participate in multilateral peering through the route servers.
Click **Yes** unless you plan to configure only bilateral sessions.
For detailed information including BGP peering addresses for AMS-IX route servers, see the [AMS-IX Peering website](https://www.ams-ix.net/ams).
* **Peering Policy** -- An IX member’s peering policy and policy URL go hand in hand and are generally used when other members want to peer with you.
* **Open** -- The member opens peering on simple demand from any member present on the IX. Generally open to all requests.
* **Closed** -- The member evaluates every demand before opening the peering. Generally closed to all requests.
* **Selective** -- The member publishes restrictive objective criteria (through the policy URL) the other member must meet to establish a peering.
* **ASN** -- You must have an ASN assigned by a local or regional internet registry:
[RIPE-NCC](https://www.ripe.net/), [APNIC](https://www.apnic.net/),
[LACNIC](https://www.lacnic.net/), [ARIN](https://www.arin.net/), or
[AFRINIC](https://afrinic.net/).
* **Contact Information** -- Select a Technical Contact and NOC Contact from the drop-down lists, and specify a contact phone number.
* **Policy URL** -- If you have a peering policy, enter the URL for the policy. If you do not have a policy, you can enter your website or a link to your peeringdb page.
* **Peering Email** -- Specify an email address for peers to contact your organization for peering requests.
* **Company Information** -- Specify the requested company contact information.
7. Click **Next** to view the Summary page.
8. Confirm the configuration and pricing, then click **Add VXC**.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
When deployed, Megaport sends an email to your registered email address with additional information on how to finish the BGP configuration.
## Technical detail and troubleshooting
Standard BGP implementations require the first ASN in the path to match the ASN of the peer, however, when engaged in multi-lateral peering the first ASN will not be that of the peer (RS) but that of the downstream peer providing the routes. This is expected behavior and is required to reduce AS path lengths for correct routing decisions. To allow multi-lateral peering, configure your devices to not enforce the first AS requirement. For example, on a Cisco router the command is **no bgp enforce-first-as**.
### Allowed traffic types on unicast peering LANs
The AMS-IX NOC reserves the right to disable ports that violate [the rules](https://www.ams-ix.net/ams/documentation/allowed-traffic).
### Looking glass
The [AMS-IX looking glass](https://my.ams-ix.net/login) is available to members.
# BGP Communities
Source: https://docs.megaport.com/ix/communities
This help topic describes the BGP communities that can be used to filter routing policy.
This topic describes the BGP communities that can be used to control routing policy. For example, peers can tag their routes to the route servers to adjust the route preference on the network or to control the distribution of advertised prefixes. This can be useful in cases where you want to peer with the entire IX except for one or two specific networks.
You can also filter routes based on a geographic location by specifying a METRO\_ID. For a list of IDs, see [Metro IDs](/ix/metro-ids).
MegaIX route servers support several traffic engineering communities to assist peers in controlling route preference and distribution. BGP communities in the range
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
64990-65512:*
```
are stripped while all others are passed on to peers.
## BGP community values
You can use standard BGP communities to define export policy to peers with 2-byte ASNs, and extended BGP communities for both 2-byte and 4-byte ASN peers.
| Standard BGP Community Value | Extended BGP Community Value | Large BGP Community Value | Description |
| - | - | - | - |
| **Action** | | | |
| 65000:0 | rt:65000:0 | RS\_ASN:65000:0 | Do not announce this route to any ASN |
| 65000:ASN | rt:65000:ASN | RS\_ASN:65000:ASN | Do not announce this route to ASN |
| 64960:ASN | rt:64960:ASN | RS\_ASN:64960:ASN | Do announce this route to ASN if (65000:0) is set |
| 65001:0 | rt:65001:0 | RS\_ASN:65001:0 | Prepend peer AS 1 time to all |
| 65001:ASN | rt:65001:ASN | RS\_ASN:65001:ASN | Prepend peer AS 1 time to ASN |
| 65002:0 | rt:65002:0 | RS\_ASN:65002:0 | Prepend peer AS 2 time to all |
| 65002:ASN | rt:65002:ASN | RS\_ASN:65002:ASN | Prepend peer AS 2 time to ASN |
| 65003:0 | rt:65003:0 | RS\_ASN:65003:0 | Prepend peer AS 3 time to all |
| 65003:ASN | rt:65003:ASN | RS\_ASN:65003:ASN | Prepend peer AS 3 time to ASN |
| 65050:0 | rt:65050:0 | RS\_ASN:65050:0 | Do not announce this route to local peers |
| 65050:1 | rt:65050:1 | RS\_ASN:65050:1 | Do not announce this route to remote peers |
| 65070:0 | rt:65070:0 | RS\_ASN:65070:0 | Do not send this route to any METRO\_ID |
| 65070:METRO\_ID | rt:65070:METRO\_ID | RS\_ASN:65070:METRO\_ID | Do not send this route to METRO\_ID |
| 64970:METRO\_ID | rt:64970:METRO\_ID | RS\_ASN:64970:METRO\_ID | Do announce this route to METRO\_ID if (64970:0) is set |
| **Informational actions are advertised to the peers on route export:** | | | |
| 65040:0 | Not used | Not used | This route comes from a local peer |
| 65040:1 | Not used | Not used | This route comes from a remote peer |
| 65060:METRO\_ID | Not used | Not used | This route comes from a peer in METRO\_ID |
## Euro-IX communities
### Large communities
| BGP Community Value | Description |
| - | - |
| **Action** | |
| RS\_ASN:0:ASN | Do not announce this route to ASN |
| RS\_ASN:0:0 | Do not announce this route to any ASN |
| RS\_ASN:1:ASN | Do announce this route to ASN if (65000:0) is set |
| RS\_ASN:101:0 | Prepend peer AS 1 time to all |
| RS\_ASN:101:ASN | Prepend peer AS 1 time to ASN |
| RS\_ASN:102:0 | Prepend peer AS 2 times to all |
| RS\_ASN:102:ASN | Prepend peer AS 2 times to ASN |
| RS\_ASN:103:0 | Prepend peer AS 3 times to all |
| RS\_ASN:103:ASN | Prepend peer AS 3 times to ASN |
| **Informational actions are advertised to the peers on route export:** | |
| RS\_ASN:1900:0 | This route comes from a local peer |
| RS\_ASN:1900:1 | This route comes from a local peer |
| RS\_ASN:1903:METRO\_ID | This route comes from a peer in METRO\_ID |
# Editing an IX
Source: https://docs.megaport.com/ix/editing-an-ix
This help topic provides an overview of editing an IX.
After you have joined an IX, you can edit the connection settings. You can change any of the settings defined when joining the IX, as well as the IX reverse DNS, and decide whether to shut down or enable the service.
For more information about the connection settings, see [Joining an IX](/ix/joining-an-ix).
**To edit an IX**
1. In the Megaport Portal, go to the **Services** page and locate the IX.
2. Click the gear icon next to the IX to make changes.
The Connection Configuration page appears.
3. You can edit any field on the Connection Configuration page. When editing an IX, you can also change the reverse DNS.
* **Reverse DNS** (optional) -- A reverse DNS is a Domain Name Service (DNS) lookup of a domain name from an IP address. This is the 'reverse' of a regular DNS request which resolves an IP address from a domain name. A PTR record type is used to store reverse DNS entries.
When editing an IX, the **Reverse DNS** field shows the default configured value assigned from the PTR record when the IX service was set up. You can change this field to a non \*.megaport.com value to define a custom hostname for your IP address. If later you want to revert to the default value, simply clear the field.
The reverse DNS can include any of these characters:\
a-z\
A-Z\
0-9
4. Click **Save**.
# Amazon Bilateral Peering on Extreme IX
Source: https://docs.megaport.com/ix/extreme-ix/amazon-bilateral-peering
This help topic describes how to request a bilateral BGP session with Amazon over Extreme IX.
The process for requesting a bilateral BGP session with Amazon depends on whether you already have an established session with Amazon at another location.
## New members with no established bilateral BGP sessions with Amazon
To request direct peering with Amazon over an existing Extreme IX link, send the following email to Amazon:
* To: `peering-india@amazon.com`
* Subject: `Direct Amazon Bilateral Peering over Extreme IX for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear Amazon Peering team,
We would like to Peer with you over Extreme IX in .
Kindly find the details below:
ASN: --> your AS Number
Network name: --> Your Network Name
Contact name and email: --> Contact Details
v4 address: - this is your Extreme IX IP
v4 prefix count: --> all of your prefix counts (number of /24 IP Pools)
NOC contact: --> your NOC contact details
Kindly please tell us further steps.
```
The estimated time to complete this request is 4 to 8 weeks.
## Existing members with one or more established bilateral BGP sessions with Amazon
If you already have one or more bilateral BGP sessions established with Amazon, use Amazon's peering portal to register more requests. Do not send an email to Amazon's peering team.
1. Go to [Amazon's PeeringDB entry](https://www.peeringdb.com/net/1418).
2. On the PeeringDB entry, click the link to the [Amazon Peering Portal](https://interconnect.amazon/).
3. Authorize Amazon Peering. The portal requests these permissions: OpenID Connect scope, user profile, email address, and list of user networks and permissions.
4. After you authorize the request, the portal takes you to the Amazon Peering Portal.
5. Click **Create New Peering Session**.
6. Complete the four steps in the peering session creation process:
* **Select Peering Endpoints** -- Choose the endpoints that match your peering needs and network location.
* **Verify the Sessions to Create** -- Confirm that the suggested sessions align with your network's presence on the exchange and with Amazon's peering policy.
* **Verify Contact Details** -- Select who to notify when the request completes. These contacts are also used if any issues arise during the process.
* **Review and Create** -- Confirm the sessions to create and review any more request data.
# Azure Bilateral Peering on Extreme IX
Source: https://docs.megaport.com/ix/extreme-ix/azure-bilateral-peering
This help topic describes how to request bilateral exchange peering with Microsoft using the Azure portal.
Microsoft peering over Extreme IX is set up through the Azure portal. If the [Microsoft peering documentation](https://learn.microsoft.com/en-gb/azure/internet-peering/policy) is not clear enough on its own, follow the steps in this topic.
1. Before you proceed, confirm that you meet Microsoft's peering requirements. For details, see the [Microsoft peering documentation](https://learn.microsoft.com/en-gb/azure/internet-peering/policy).
2. Create an Azure account.
To associate your Autonomous System Number (ASN) with an Azure account, you need a [Microsoft Azure account](https://azure.microsoft.com/en-gb/pricing/purchase-options/azure-account). An active Azure subscription is required to set up peering, since peerings are modeled as resources within Azure subscriptions. A payment card is required to create the account, but the peering service itself is free. If you are new to Azure, the Basic or Free tier is usually sufficient for exchange peering.
3. Once your account is ready, use the [ASN association link](https://go.microsoft.com/fwlink/?linkid=2129592) to associate your ASN with your Azure account.
After you submit this request, wait 24 to 48 hours before continuing.
4. Submit a peering request for your ASN using the [peering request link](https://go.microsoft.com/fwlink/?linkid=2129593).
Microsoft sends a confirmation email once your request is accepted. If you do not receive an automated reply, or if BGP session establishment is delayed by more than two weeks, contact the Extreme team at `support@x3me.net`.
# Extreme IX BGP Communities and Configuration Guide
Source: https://docs.megaport.com/ix/extreme-ix/bgp-communities
This help topic describes how to use BGP communities and Route Server behavior to manage traffic propagation on Extreme IX.
Extreme IX Route Servers remove the need for individual bilateral BGP sessions between members. Use BGP communities to control how the Route Servers propagate your routes to other peers.
## Route Server behavior: AS-path hiding
Extreme IX Route Servers (RS) do not prepend or include their own Autonomous System Number (ASN) in the `AS_PATH` attribute. This removes the RS AS from the path, so participating members appear directly connected without requiring individual bilateral BGP sessions between each member network.
### Disable the first-AS check
Because the Route Server hides its ASN, some BGP router implementations discard incoming updates from eBGP peers by default if the peer's ASN does not appear first in the `AS_PATH`. Disable this check on your router when you peer with Extreme IX Route Servers:
* **Cisco** -- `no bgp enforce-first-as` or `bgp enforce-first-as disable`
* **Huawei** -- `undo check-first-as` under the BGP context
* **Fortinet** -- `set enforce-first-as disable`
## BGP community controls
All members peering with Extreme IX Route Servers can use communities to control incoming and outgoing route propagation.
* **Incoming traffic control** -- Managed on the member side. You control which prefixes received from the Route Server are accepted into your routing table.
* **Outgoing traffic control** -- Use BGP communities to control which peers receive your announced prefixes through the Route Server.
Do not mix standard communities with large communities in the same policy. Choose one format for your configuration.
### Standard BGP communities
Communities originated from the Extreme IX RS:
* `0:peer AS` -- The prefix is announced from `peer AS`.
Standard communities accepted by the Extreme IX RS:
* `49378:0` -- Block your prefix to all peers.
* `49378:0 49378:ASPEER` -- Block your prefix to all peers except `ASPEER`.
* `49378:ASPEER` -- Block your prefix to `ASPEER`.
### Large BGP communities
Announcement control:
* `49378:0:0` -- Block your prefix to all peers.
* `49378:1:ASPEER` -- Announce a route to a specific `ASPEER`.
* `49378:0:ASPEER` -- Prevent announcement of a prefix to an `ASPEER`.
For the full list of AS mappings and technical requirements, see the [Extreme IX Technical Requirements page](http://extreme-ix.org/technical/technical-requirements/).
Large BGP communities also let you prepend your prefixes to a specific Route Server member while advertising to the rest of the peers without prepends:
* `49378:101:ASPEER` -- Prepend to `ASPEER` once.
* `49378:102:ASPEER` -- Prepend to `ASPEER` twice.
* `49378:103:ASPEER` -- Prepend to `ASPEER` three times.
For example, attaching `49378:103:ASN1` prepends your prefixes to `ASN1` three times, while advertising to the rest of the members without prepends.
## Operational notices
IPv6 Router Advertisements (RA) are ICMPv6 NDP messages required for LAN/SLAAC environments. They have no use case for point-to-point (PtP) links, inter-AS links, IP transit, PNI, and IXP LAN connectivity. Confirm that these default behaviors are disabled on your network devices. For information about how to disable IPv6 RA per vendor, and why this matters, see [this article](https://www.daryllswer.com/ipv6-router-advertisement-why-is-it-enabled-by-default-on-some-network-vendors/).
## Vendor configuration examples
The following examples show how to manage route propagation to and from specific BGP peers through the Route Server (RS) using BGP communities (ASN `49378`).
### Scenario 1: block specific BGP peers through the Route Server
Use these configurations to block receiving prefixes from specific target Autonomous Systems (`AS: xxx`, `AS: yyy`) and prevent sending your routes to them.
Deny received routes matching the targeted AS in the inbound filter, then accept the remaining routes. Attach the control community to every prefix pool you advertise toward the Route Server.
```text Huawei theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
# BGP Peer Configuration
peer as-number
#
ipv4-family unicast
peer enable
peer route-policy MyPool-IN import
peer route-policy MyPool-OUT export
peer advertise-community
#
# Define Local Prefixes
ip ip-prefix MyPool index 10 permit x.x.x.x 24
ip ip-prefix MyPool index 15 permit x.x.x.x 24
#
# Outbound Route Policy (Do not advertise to AS xxx, yyy)
route-policy MyPool-OUT permit node 10
if-match ip-prefix MyPool
apply community 49378:xxx 49378:yyy additive
#
# Inbound Route Policy (Block routes from AS xxx, yyy)
route-policy MyPool-IN deny node 10
if-match community-filter 11 12
route-policy MyPool-IN permit node 20
#
# Community Filters
ip community-filter 11 permit 0:xxx
ip community-filter 12 permit 0:yyy
```
```text Cisco theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
! BGP Peer Configuration
neighbor remote-as
neighbor route-map MyPool-IN in
neighbor route-map MyPool-OUT out
neighbor send-community
!
! Define Local Prefixes
ip prefix-list MyPool seq 10 permit x.x.x.x/22 le 24
!
! Outbound Route Map
route-map MyPool-OUT permit 10
match ip address prefix-list MyPool
set community 49378:xxx 49378:yyy additive
!
! Inbound Route Map
route-map MyPool-IN deny 10
match community filter
!
route-map MyPool-IN permit 20
!
! Community List Definition
ip community-list standard filter permit 0:xxx
ip community-list standard filter permit 0:yyy
```
```text Juniper theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
# BGP Protocol Setup
set protocols bgp group to_EIX type external
set protocols bgp group to_EIX import inbound-routes-EIX
set protocols bgp group to_EIX export outbound-routes-EIX
set protocols bgp group to_EIX neighbor 103.77.108.200 peer-as 49378
# Prefix List Definition
set policy-options prefix-list EIX-Download-PREFIX x.x.x.x/24
# Outbound Policy Statement
set policy-options policy-statement outbound-routes-EIX term OUT from prefix-list EIX-Download-PREFIX
set policy-options policy-statement outbound-routes-EIX term OUT then community add COMMUNITY_out
set policy-options policy-statement outbound-routes-EIX term OUT then accept
set policy-options policy-statement outbound-routes-EIX term LAST then reject
# Inbound Policy Statement
set policy-options policy-statement inbound-routes-EIX term Block-COMMUNITY from community COMMUNITY_in
set policy-options policy-statement inbound-routes-EIX term Block-COMMUNITY then reject
set policy-options policy-statement inbound-routes-EIX term EIX-UPLOAD from protocol bgp
set policy-options policy-statement inbound-routes-EIX term EIX-UPLOAD then local-preference xx
set policy-options policy-statement inbound-routes-EIX term EIX-UPLOAD then accept
# Community Definitions
set policy-options community COMMUNITY_out members [ 49378:xxx 49378:yyy ]
set policy-options community COMMUNITY_in members [ 0:xxx 0:yyy ]
```
```text MikroTik RouterOS v6 theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
/routing filter
add action=discard chain=EIX-RS-IN bgp-communities=0:xxx
add action=discard chain=EIX-RS-IN bgp-communities=0:yyy
add action=accept chain=EIX-RS-IN
add action=accept chain=EIX-RS-OUT prefix= set-bgp-communities=49378:xxx,49378:yyy
```
```text MikroTik RouterOS v7.x theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
/routing filter rule
add chain=Extreme-RS-in disabled=no rule="if (bgp-communities equal 0:xxx) { reject }"
add chain=Extreme-RS-in disabled=no rule="if (bgp-communities equal 0:yyy) { reject }"
add chain=Extreme-RS-in disabled=no rule="accept"
add chain=Extreme-RS-out disabled=no rule="if (dst==x.x.x.x/24) { set bgp-communities 49378:xxx,49378:yyy; accept }"
add chain=Extreme-RS-out disabled=no rule="reject"
```
For Route Server members using 32-bit ASNs, see the [Extreme IX Technical Requirements page](https://extreme-ix.org/resources/technical-requirements) for the mapped short community values, so you avoid using BGP extended communities.
### Scenario 2: allow selective peers only, and block all others
Use these configurations to block route exchange with all members by default, and allow route exchange only with specific target networks -- for example, Google (`AS15169`) and Akamai (`AS20940`).
```text MikroTik RouterOS v6 theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
/routing filter
# Outbound: Block advertise to all (49378:0), permit only Akamai & Google
add action=accept chain=EIX-RS-OUT prefix= set-bgp-communities=49378:0,49378:20940,49378:15169
add action=accept chain=EIX-RS-OUT prefix= set-bgp-communities=49378:0,49378:20940,49378:15169
add action=discard chain=EIX-RS-OUT
# Inbound: Accept only Akamai & Google routes, discard all others
add action=accept chain=EIX-RS-IN bgp-communities=0:20940
add action=accept chain=EIX-RS-IN bgp-communities=0:15169
add action=discard chain=EIX-RS-IN
```
```text MikroTik RouterOS v7.x theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
/routing filter rule
# Inbound Filter
add chain=Extreme-RS-in disabled=no rule="if (bgp-communities equal 0:20940) { accept }"
add chain=Extreme-RS-in disabled=no rule="if (bgp-communities equal 0:15169) { accept }"
add chain=Extreme-RS-in disabled=no rule="reject"
# Outbound Filter
add chain=Extreme-RS-out disabled=no rule="if (dst==x.x.x.x/24) { set bgp-communities 49378:0,49378:20940,49378:15169; accept }"
add chain=Extreme-RS-out disabled=no rule="reject"
```
The following example establishes dual Route Server sessions (primary and secondary) on Huawei, accepting prefixes exclusively from Akamai (`AS20940`) and blocking all others.
```text Huawei Primary Route Server theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
peer 45.120.248.200 as-number 49378
#
ipv4-family unicast
peer 45.120.248.200 enable
peer 45.120.248.200 route-policy MyPool-IN import
peer 45.120.248.200 route-policy MyPool-OUT export
peer 45.120.248.200 advertise-community
#
ip ip-prefix MyPool index 10 permit x.x.x.x 24
ip ip-prefix MyPool index 15 permit x.x.x.x 24
#
# Outbound: Block all peers (49378:0), permit Akamai (49378:20940)
route-policy MyPool-OUT permit node 10
if-match ip-prefix MyPool
apply community 49378:0 49378:20940 additive
#
# Inbound: Accept Akamai (0:20940), deny all others
route-policy MyPool-IN permit node 10
if-match community-filter 11
route-policy MyPool-IN deny node 20
#
ip community-filter 11 permit 0:20940
```
```text Huawei Secondary Route Server theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
peer 45.120.248.240 as-number 49378
#
ipv4-family unicast
peer 45.120.248.240 enable
peer 45.120.248.240 route-policy MyPool-IN import
peer 45.120.248.240 route-policy MyPool-OUT export
peer 45.120.248.240 advertise-community
#
ip ip-prefix MyPool index 10 permit x.x.x.x 24
ip ip-prefix MyPool index 15 permit x.x.x.x 24
#
route-policy MyPool-OUT permit node 10
if-match ip-prefix MyPool
apply community 49378:0 49378:20940 additive
#
route-policy MyPool-IN permit node 10
if-match community-filter 11
route-policy MyPool-IN deny node 20
#
ip community-filter 11 permit 0:20940
```
# Extreme IX Overview
Source: https://docs.megaport.com/ix/extreme-ix/index
This help topic provides an overview of Extreme IX, a carrier-neutral internet exchange in India that is now part of Megaport.
Extreme IX is a carrier-neutral, data-center-neutral internet exchange (IX) built for internet service providers (ISPs) in India, and for local and international content providers.
Extreme IX accepts any network operator with an Autonomous System Number (ASN), assigned IP address space, and an open peering policy. Extreme Infocom Pvt. Ltd., an India-based internet infrastructure operator now owned by Megaport, operates and maintains the exchange.
## Mission and ecosystem
The Extreme IX engineering and operations team drives internet peering adoption across India through community education, technical enablement, and infrastructure development. Extreme IX aims to strengthen the local ISP ecosystem by increasing local traffic exchange and helping network operators reach a target ratio of 1:10 transit to peering traffic.
## Key resources
| Resource | Description | Link |
| - | - | - |
| Official websites | Main portal and service overview | [extremeport.in](https://extremeport.in/), [extreme-ix.org](https://extreme-ix.org/) |
| Status page | Operational health and service availability | [status.extreme-ix.org](https://status.extreme-ix.org/) |
| Looking glass | Routing analysis and network visibility | [lg.extreme-ix.org/lg](https://lg.extreme-ix.org/lg) |
| Traffic statistics | Live aggregate traffic metrics | [extreme-ix.org/technical/statistics](https://extreme-ix.org/technical/statistics/) |
## In this section
* [Peering Request Procedures](/ix/extreme-ix/peering-request-procedures) -- Step-by-step guidance on requesting and establishing peering.
* [Security Policies](/ix/extreme-ix/security-policies) -- Platform safety standards, port security, and compliance.
* [RPKI and IRR Filtering](/ix/extreme-ix/rpki-irr-filtering) -- Route validation, security enforcement, and anti-hijacking controls.
* [BGP Communities and Configuration Guide](/ix/extreme-ix/bgp-communities) -- BGP community tags for route control and traffic engineering.
* [Status Page Subscription](/ix/extreme-ix/status-page-subscription) -- Subscribe to maintenance and outage alerts.
* [PeeringDB Record](/ix/extreme-ix/peeringdb-record) -- Complete and maintain your PeeringDB entry before you submit peering requests with Extreme IX.
# Extreme IX Peering Request Procedures
Source: https://docs.megaport.com/ix/extreme-ix/peering-request-procedures
This help topic describes how to verify content provider availability and establish Route Server and Fast Peering Router sessions with Extreme IX.
Extreme IX operates carrier-neutral internet exchange points across major regional hubs in India. This topic consolidates the location-specific parameters, provider contact details, portal links, and peering instructions you need to set up peering.
## Verify content provider availability
Before you request peering, confirm that the content provider or peer network you want to reach is active at your Extreme IX location: Delhi, Mumbai, Chennai, Hyderabad, Kolkata, Bangalore, or Pune.
1. Go to the [Extreme IX content providers page](https://extreme-ix.org/members/content-providers).
2. Find your target provider's ASN and confirm availability under your location column.
## Establish Route Server and Fast Peering Router sessions
Establish BGP sessions with the Extreme IX Route Servers, and with the Fast Peering Router where available, to automatically receive routes from participating content networks.
### Regional infrastructure connection details
| Component | Remote IPv4 | Remote IPv6 | Remote AS |
| - | - | - | - |
| Route Server 1 | `45.120.248.200` | `2001:df2:1900:1::200` | `49378` |
| Route Server 2 | `45.120.248.240` | `2001:df2:1900:1::240` | `49378` |
| Fast Peering Router | `45.120.248.95` | `2001:df2:1900:1::95` | `135814` |
| Component | Remote IPv4 | Remote IPv6 | Remote AS |
| - | - | - | - |
| Route Server 1 | `103.77.108.200` | `2001:df2:1900:2::200` | `49378` |
| Route Server 2 | `103.77.108.240` | `2001:df2:1900:2::240` | `49378` |
| Fast Peering Router | `103.77.108.12` | `2001:df2:1900:2::12` | `135814` |
| Component | Remote IPv4 | Remote IPv6 | Remote AS |
| - | - | - | - |
| Route Server 1 | `45.120.251.200` | `2001:df2:1900:3::200` | `49378` |
| Route Server 2 | `45.120.251.240` | `2001:df2:1900:3::240` | `49378` |
| Fast Peering Router | `45.120.251.12` | `2001:df2:1900:3::12` | `135814` |
| Component | Remote IPv4 | Remote IPv6 | Remote AS |
| - | - | - | - |
| Route Server 1 | `103.77.110.200` | `2001:df2:1900:4::200` | `49378` |
| Route Server 2 | `103.77.110.240` | `2001:df2:1900:4::240` | `49378` |
| Fast Peering Router | `103.77.110.222` | `2001:df2:1900:4::222` | `135814` |
| Component | Remote IPv4 | Remote IPv6 | Remote AS |
| - | - | - | - |
| Route Server 1 | `45.120.249.200` | `2001:df2:1900:5::200` | `49378` |
| Route Server 2 | `45.120.249.240` | `2001:df2:1900:5::240` | `49378` |
Kolkata has no Fast Peering Router.
| Component | Remote IPv4 | Remote IPv6 | Remote AS |
| - | - | - | - |
| Route Server 1 | `38.10.0.200` | `2001:df2:1900:7::200` | `49378` |
| Route Server 2 | `38.10.0.240` | `2001:df2:1900:7::240` | `49378` |
| Fast Peering Router | `38.10.0.13` | `2001:df2:1900:7::13` | `135814` |
| Component | Remote IPv4 | Remote IPv6 | Remote AS |
| - | - | - | - |
| Route Server 1 | `123.253.159.200` | `2001:df2:1900:6::200` | `49378` |
| Route Server 2 | `123.253.159.240` | `2001:df2:1900:6::240` | `49378` |
| Fast Peering Router | `123.253.159.100` | `2001:df2:1900:6::100` | `135814` |
* **Outgoing BGP filters** -- Create BGP filters for outgoing routes to advertise only your public IP pools. Do not advertise full transit routes or routes received from upstream providers.
* **Re-announcement restriction** -- Never re-announce Extreme IX Route Server or Fast Peering Router IP prefixes to transit providers or third-party peers.
* **Configuration SLA** -- BGP configuration on Extreme IX Route Servers takes 1 to 2 business days after you raise a peering request.
* **Fast Peering Router purpose** -- An L3 solution that provides traffic from providers (notably Google) that reject bilateral BGP requests with new members globally and are not Route Server members.
* **Pune** -- Access to major co-located CDNs (Google GGC, Facebook FNA, Apple) in Pune is available through the Premium CDN add-on service. Contact your Extreme CSM to open a support ticket. Amazon is available for free bilateral peering in Pune.
For information about how to use BGP communities to control route propagation, see [BGP Communities and Configuration Guide](/ix/extreme-ix/bgp-communities).
## Provider-specific peering instructions
Once you confirm availability on the [content providers page](https://extreme-ix.org/members/content-providers), see [Provider Peering Instructions](/ix/extreme-ix/provider-peering-instructions) for the onboarding requirements specific to your target content provider.
# Extreme IX PeeringDB Record
Source: https://docs.megaport.com/ix/extreme-ix/peeringdb-record
This help topic describes the PeeringDB requirements for Extreme IX members and how to add your Extreme IX presence to your PeeringDB profile.
All participating networks must maintain an accurate and up-to-date profile on [PeeringDB](https://www.peeringdb.com/). Completing and maintaining your PeeringDB entry is mandatory before you submit peering requests with Extreme IX.
## Key requirements
Before you request peering, confirm that your profile meets these requirements:
* **IRR AS-SET object** -- Declare an active IRR AS-SET/route-set object in your PeeringDB network profile for automated Route Server filtering.
* **Allow IXP Update permission** -- Enable the **Allow IXP Update** option in your PeeringDB settings. This lets Extreme IX automation maintain accurate port status and IP assignments.
* **Up-to-date contact information** -- Keep your peering contacts (NOC email, phone, and technical contacts) accurate.
## Add Extreme IX to your PeeringDB profile
To register your presence at an Extreme IX exchange location (for example, Extreme IX Delhi):
1. Go to [peeringdb.com](https://www.peeringdb.com/) and log in with your account credentials.
2. Open your network profile by selecting your organization from the profile menu in the upper-right corner, or search for your Autonomous System Number (ASN) in the search bar.
3. Click **Edit** on the right side of your network entry page.
4. In the **Public Peering Exchange Points** section, type `Extreme IX` in the Exchange field, then select your local exchange location (for example, **Extreme IX Delhi**) from the drop-down list.
If your Extreme IX location does not appear in the drop-down list, contact the Extreme IX Operations team.
5. Complete the required technical details for your connection:
* **Assigned IP address** -- Your provisioned IPv4 address, IPv6 address, or both, on Extreme IX.
* **Port Speed** -- Your allocated interface bandwidth (for example, 1G, 10G, 100G).
* **Route Server** -- Select this check box if you peer with the Extreme IX Route Servers.
6. Confirm that your IRR AS-SET is populated and that **Allow IXP Update** is enabled, then click **Save**.
# Extreme IX Provider Peering Instructions
Source: https://docs.megaport.com/ix/extreme-ix/provider-peering-instructions
This help topic lists the peering setup requirements, SLAs, and contact details for individual content providers available on Extreme IX.
Each content provider on Extreme IX has its own peering setup method, service level agreement (SLA), and contact process. Confirm that your target provider is available at your location on the [content providers page](https://extreme-ix.org/members/content-providers), then follow the instructions for that provider below.
For Amazon, see [Amazon Bilateral Peering](/ix/extreme-ix/amazon-bilateral-peering). For Microsoft, see [Azure Bilateral Peering](/ix/extreme-ix/azure-bilateral-peering).
* **Akamai PNI** -- Provided free from Akamai's public nodes. You receive Akamai PNI prefixes through the Extreme Route Servers. There is no bilateral BGP for Akamai PNI traffic.
* **Akamai AANP** -- Paid traffic, provided from nodes installed in Extreme's network. You receive Akamai AANP prefixes through the Extreme Route Servers. Contact your Account Manager to start this traffic, since it is part of the Premium CDN service. There is no bilateral BGP for Akamai AANP traffic.
* **DNS requirement** -- Akamai AANP peering depends on DNS. Do not use public DNS (such as `8.8.8.8` or L3 DNS servers). Use your own DNS server and advertise its IP address through your BGP sessions with the Extreme Route Servers.
Prolexic, part of Akamai, is a DDoS mitigation service. Peering gives you a short path to offload outbound DDoS traffic and improves proximity to mutual Akamai customers.
* **Interconnection details**:
* Mumbai -- IPv4 `103.77.109.140`, IPv6 `2001:df2:1900:2::1140`
* Chennai -- IPv4 `45.120.251.95`, IPv6 `2001:df2:1900:3::95`
* ASN `32787`, AS macro `AS-PROLE`
* Suggested max prefixes: 8000 (IPv4) / 800 (IPv6)
* **Support and peering contacts**:
* Session modification/administrative -- `peering-tix@akamai.com`, +1 617 444-3007
* 24/7 break/fix NOC -- `nocc-tix@akamai.com`, +1 617 444-3007
* **SLA and policy** -- BGP configuration takes up to 10 business days. Akamai Prolexic applies a selective peering policy and can refuse bilateral BGP peering with some members.
* **Route Server note** -- Akamai Prolexic (AS32787) is also a Route Server member, so you also learn its routes through your Route Server sessions.
* **Setup method** -- Register a request using the Amazon peering portal.
* For detailed instructions, see [Amazon Bilateral Peering](/ix/extreme-ix/amazon-bilateral-peering).
* **Route Server note** -- Apple is not a Route Server member. You cannot learn Apple's routes through the Extreme IX Route Servers.
* **Mandatory requirements** -- Apple only establishes bilateral sessions with members that maintain a fully populated PeeringDB record, including NOC contacts.
* **Estimated SLA** -- Up to 2 weeks after you raise the peering request.
* **Email request format**:
* To: `peering@group.apple.com`
* Subject: `Direct Apple Peering over Extreme IX [City Name] for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your NOC contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.
```
* **Setup method** -- Send email to `peering@cachefly.com` (NOC contact: `noc@cachefly.com`).
* **Policy and requirements** -- CacheFly does not peer with everyone. If you use the Route Servers, CacheFly prefers that you do not also request a bilateral session, since it advertises the same prefixes both ways.
* **SLA** -- Less than 2 days for bilateral session establishment.
* **Traffic type** -- CDN content, primarily not DNS-sensitive.
* **Estimated SLA** -- Up to 1 week after you raise the peering request.
* **Email request format**:
* To: `peering@opendns.com`
* Subject: `Direct Cisco Umbrella Peering over Extreme IX [City Name] for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your NOC contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.
```
* **Estimated SLA** -- 1 to 2 business days after you raise the peering request.
* **Email request format**:
* To: `peering@cira.ca`
* Subject: `Direct CIRA Bilateral Peering over Extreme IX [City Name] for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear CIRA team,
We would like to Peer with you over Extreme - IX in [City Name]
Kindly find the details below:
ASN: -> [your AS Number]
Network name: -> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: -> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: -> [your noc contact details]
Kindly please tell us further steps.
```
* **Estimated SLA** -- 2 to 3 weeks after you raise the peering request.
* Public peering is automated through the [Cloudflare Peering Portal](https://peering.cloudflare.com/). We recommend establishing sessions in all mutual locations. Use PeeringDB OIDC to authenticate.
* **Automation note** -- DigitalOcean's automation tool pulls your contact details, v4 address, prefix count, and NOC contact directly from PeeringDB. Keep your PeeringDB information up to date.
* **Estimated SLA** -- 4 to 5 days after you raise the peering request.
* **Email request format**:
* To: `peering@digitalocean.com`
* Subject: `Direct DigitalOcean Bilateral Peering over Extreme IX [City Name] for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear DigitalOcean team,
We would like to Peer with you over Extreme - IX in [City Name]
Kindly find the details below:
ASN: -> [your AS Number]
Network name: -> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: -> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: -> [your noc contact details]
Kindly please tell us further steps.
```
* **Traffic threshold** -- Selective peering policy; your traffic to Facebook peering should exceed 50 Mbps.
* **Estimated SLA** -- 2 to 5 weeks after you raise the peering request.
* **Alternative request method** -- You can also use the [Meta Peering Manager Portal](https://www.facebook.com/peering/) to request bilateral peering.
* **Email request format**:
* To: `peering@fb.com`
* Subject: `Direct Facebook Bilateral Peering over Extreme IX [City Name] for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear Facebook Peering team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your noc contact details]
Kindly please tell us further steps.
```
* **Prerequisite** -- Create an IRR record; Fastly uses IRRs for route filtering.
* **Traffic threshold** -- Selective peering policy; your traffic to Fastly peering should exceed 50 Mbps.
* **Estimated SLA** -- 1 to 2 weeks after you raise the peering request.
* **Email request format**:
* To: `peering@fastly.com`
* Subject: `Direct Fastly Bilateral Peering over Extreme IX [City Name] for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear Fastly Peering team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your noc contact details]
Kindly please tell us further steps.
```
* **Estimated SLA** -- 2 to 3 weeks after you raise the peering request.
* **Email request format**:
* To: `noc@gcore.lu`
* Subject: `Direct Gcore Peering over Extreme IX [City Name] for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your noc contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.
```
* **Estimated SLA** -- 1 to 5 weeks after you raise the peering request.
* **Email request format**:
* To: `peering@softlayer.com`
* Subject: `Direct IBM Cloud Peering Request within Extreme IX [City Name] | `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear IBM Cloud Peering team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [Your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [This is your Extreme IX IP]
v4 prefix count: --> [All of your prefix counts]
v6 address: - [This is your Extreme IX IPv6]
v6 prefix count: --> [All of your prefix counts]
NOC contact: --> [Your noc contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.
```
Joy Services is a Route Server member and also establishes bilateral sessions. For public services, it has DNS/name server routes available through the Route Servers. For end-user content -- hosted files, API, DNS queries, CDN, cache servers, and database CDN cache -- you must establish a bilateral session.
* **Estimated SLA** -- 20 minutes if you use the strict email format below, since it is processed by an automated API. Manual reviews take up to 24 hours.
* **Provider details**:
* Official site -- [joy.services](https://joy.services/)
* BGP tools -- [AS152565](https://bgp.tools/as/152565)
* Technical contact -- `dinesh@joycloud.services`
* Public resolver DNS -- `dns.joy.services`
* **Email request format**:
* To: `support@joycloud.services`
* Subject: `Enabling Bilateral BGP Session - Extreme [City Name] || Joy Services - `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear Peering team,
We would like to Peer with you over Extreme - IX [City Name]
ASN-[company_asn]
Network_name-[network_name]
Contact_email-[contact_team]
v4_address-[peering_address]
v4_prefix count-[total_prefix_count]
NOC-[noc_team_email]
Peering_db_link-[peering_db_link]
Other_Info-[any_general_info_saved_in_notes_by_our_system]
```
In `Other_Info`, specify `1` for India region only, or `2` for full routes for all content over Joy Services.
* **Route Server and bilateral note** -- Kaopu Cloud HK is a Route Server member and accepts bilateral BGP requests.
* **Estimated SLA** -- 3 to 5 working days after you raise the peering request.
* **Contact format** -- Send email to `noc@kaopucloud.com`, with a copy to `apac@kaopucloud.com`, providing your BGP configuration details (ASN, number of prefixes, and MD5 key if configured).
* **Estimated SLA** -- 1 to 3 days after you raise the peering request.
* **Email request format**:
* To: `peering@melbicom.net`
* Subject: `Direct Melbicom Bilateral Peering over Extreme IX [City Name] for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear Melbicom Peering team,
We would like to Peer with you over Extreme - IX in [City Name]
Kindly find the details below:
ASN: -> [your AS Number]
Network name: -> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: -> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: -> [your noc contact details]
Kindly please tell us further steps.
```
* **Setup method** -- Register a request using the Azure portal.
* For step-by-step instructions, see [Azure Bilateral Peering](/ix/extreme-ix/azure-bilateral-peering).
* **Route Server and bilateral note** -- Netskope is a Route Server member and also accepts bilateral BGP requests.
* **Estimated SLA** -- 10 days after you raise the peering request.
* **Contact format** -- Send email to `peering@netskope.com` with your complete BGP configuration details, including ASN, number of prefixes, and MD5 key if configured.
* **Setup method** -- Submit a request through the [Netflix Open Connect Partner Help Center](https://openconnect.netflix.com/).
* **Estimated SLA** -- 2 to 4 weeks after you raise the peering request.
* **Estimated SLA** -- 2 weeks after you raise the peering request.
* **Email request format**:
* To: `peering_ww@oracle.com`
* Subject: `Direct Oracle Cloud Infrastructure Peering over Extreme IX [City Name] for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your NOC contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.
```
* **Email request format**:
* To: `peering-16276@ovh.net`
* Subject: `Direct OVH Peering over Extreme IX [City Name] for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your noc contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.
```
* **Estimated SLA** -- 2 to 3 weeks after you raise the peering request.
* **Email request format**:
* To: `support@psychz.net`
* Subject: `Direct Psychz Network Peering over Extreme IX [City Name] for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear Psychz Network team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your noc contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.
```
* **Estimated SLA** -- 1 week after you raise the peering request.
* **Email request format**:
* To: `peering@riotgames.com`
* Subject: `Direct Riot Games Peering over Extreme IX [City Name] for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your NOC contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.
```
* **Route Server and bilateral note** -- Times Internet is a Route Server member and also establishes bilateral sessions.
* **Request directive** -- Times Internet does not provide a bilateral peering email address. It reaches out to peers directly.
* **Route Server note** -- You receive Verge Cloud prefixes exclusively through the Extreme IX Route Servers. Bilateral BGP sessions are not supported.
* **Public looking glass** -- Not available.
* **Traffic and queries** -- Content includes non-DNS-sensitive OTT, entertainment, trading, and CDN traffic. For peering-related queries, email `peering@vergecloud.com`.
* **Estimated SLA** -- 2 to 3 weeks after you raise the peering request.
* **Email request format**:
* To: `peering-requests@yahooinc.com` (or `peering-requests@oath.com` for Chennai)
* Subject: `Direct Yahoo Peering over Extreme IX [City Name] for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear Yahoo Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your noc contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.
```
* **Estimated SLA** -- Up to 2 weeks after you raise the peering request.
* **Email request format**:
* To: `peering@zenlayer.com` (or `peering@valvesoftware.com` for Valve traffic in Chennai)
* Subject: `Direct Zenlayer Bilateral Peering over Extreme IX [City Name] for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear Zenlayer Peering team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your noc contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.
```
* **Estimated SLA** -- Up to 1 week after you raise the peering request.
* **Email request format**:
* To: `peering@zscaler.com`
* Subject: `Direct ZScaler Softech Peering over Extreme IX [City Name] for `
* Body:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Dear Team,
We would like to Peer with you over Extreme - IX [City Name]
Kindly find the details below:
ASN: --> [your AS Number]
Network name: --> [Your Network Name]
Contact name and email: --> [Contact Details]
v4 address: - [this is your Extreme IX IP]
v4 prefix count: --> [all of your prefix counts (number of /24 IP Pools)]
NOC contact: --> [your NOC contact details]
Link to Peering DB Record --> [Link to your Peering DB record]
Kindly please tell us further steps.
```
The following providers exchange traffic exclusively through the Extreme IX Route Servers and do not accept or support bilateral BGP sessions:
* BitGravity
* Endurance International Group
* F5 Inc.
* Global Network Management (Telegram)
* Infobip Peering
* Leapswitch Networks
* Rediff Peering
Connecting to the Extreme IX Route Servers automatically brings you prefixes from these members. No separate outreach is required.
# RPKI and IRR Filtering on Extreme IX
Source: https://docs.megaport.com/ix/extreme-ix/rpki-irr-filtering
This help topic describes the RPKI and IRR route validation policies that apply to BGP sessions on Extreme IX.
To ensure route security, prevent BGP hijacking, and protect against route leaks, strict route validation policies govern BGP sessions with Extreme IX.
Extreme IX only establishes BGP sessions and accepts route announcements that are RPKI valid and that pass IRR (Internet Routing Registry) filtering.
## RPKI and Route Origin Authorization (ROA)
A Route Origin Authorization (ROA) is a cryptographically signed object that specifies which Autonomous System Number (ASN) is authorized to originate a specific IP address prefix or range.
### Validate your RPKI status
Use these public tools to confirm that your prefixes are correctly signed and validated:
* **HE BGP Toolkit** -- Valid ROAs display a key icon next to the prefix listing on [bgp.he.net](https://bgp.he.net/).
* **RPKI Validator** -- Check your prefix status at the [RIPE RPKI Validator](https://rpki-validator.ripe.net/ui/); a valid prefix shows as Valid.
### Create ROAs by RIR or NIR
#### Option A: IRINN (India)
To start and create ROA objects for resources under IRINN:
1. Send an email to `hostmaster@irinn.in` from your registered account email.
2. Include the following mandatory details:
* **ASN** -- The Autonomous System Number announcing the IP block.
* **IP Prefix** -- The address block (for example, `192.168.0.0/22`).
* **Most Specific Announcement (MSA)** -- The maximum prefix length allowed (for example, `/24`).
For example,
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
ASN: AS24029
IP Prefix: 192.168.0.0/22
MSA: /24
```
For more information, see the [IRINN Resource Certification page](https://irinn.in/resource-certification).
#### Option B: APNIC
1. Log in to MyAPNIC, go to **Resources > Resource Certification > RPKI**, and click **Activate RPKI Engine**.
2. Go to **Resources > Route Management > Routes** to view your registered prefixes and transit ASNs.
3. Click **Create Route** and complete the required fields:
* **Prefix** -- The IP prefix block to authorize.
* **Origin AS** -- The ASN authorized to originate the prefix.
* **Most Specific Announcement (MSA)** -- The smallest allowable sub-route (for example, `/24` for IPv4 or `/48` for IPv6). APNIC marks any prefix announced shorter than this length as Invalid.
* **Whois Option** (optional) -- Automatically creates `route`/`route6` objects alongside your ROA. When enabled, the difference between the prefix length and the MSA must be 8 bits or less (for example, a `/32` IPv6 prefix allows an MSA up to `/40`).
4. Review your configuration, select any sub-routes if applicable, and click **Submit**. APNIC automatically publishes your ROA to the global RPKI repository.
For more information, see APNIC's guide on [creating RPKI ROAs in MyAPNIC](https://blog.apnic.net/2019/09/11/how-to-creating-rpki-roas-in-myapnic/).
## IRR filtering and AS-Set objects
All member networks must maintain accurate prefix and downstream customer records in the Internet Routing Registry (IRR) using RPSL syntax.
### AS-Set configuration guidelines
* **Networks with downstream customers** -- Maintain an updated `as-set` object that contains your ASN and all downstream member ASNs.
* **Networks without downstream customers** -- You do not need to create an `as-set` object. Enter your ASN (for example, `AS135814`) in PeeringDB.
Example IRR `as-set` object:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
as-set: AS135814:AS-CUSTOMERS
descr: Provides Transit to the following ASes
members: AS135814, AS20940, AS63293
admin-c: EIMT1-AP
tech-c: EIMT1-AP
mnt-by: MAINT-IN-EXTREME
last-modified: 2018-06-01T19:12:02Z
source: APNIC
```
Add your updated `as-set` object or ASN to your PeeringDB record. For step-by-step instructions, see [PeeringDB Record](/ix/extreme-ix/peeringdb-record).
For more information about IRR, see [APNIC's guide to using WHOIS: AS-SET](https://www.apnic.net/manage-ip/using-whois/guide/as-set/) and [irr.net](https://irr.net/).
# Security Policies on Extreme IX
Source: https://docs.megaport.com/ix/extreme-ix/security-policies
This help topic describes the technical and security policies that member networks must follow when connecting to Extreme IX.
To preserve platform stability, prevent service degradation, and protect members against security threats, all member networks connected to Extreme IX must meet the following technical and port security requirements.
## Port security and Layer 2 traffic controls
* **MAC address authorization** -- Only one source MAC address is permitted per physical service port. Extreme IX drops traffic from any unapproved MAC address at the port level. For a VLAN interconnect service, one unique source MAC address is allowed per provisioned VLAN ID.
* **VLAN restrictions** -- Native VLAN 1 framing is not permitted on any interface connected to Extreme IX.
* **Prohibited L2 control protocols** -- Disable Spanning Tree Protocol (STP) on all member-facing interfaces connected to Extreme IX. Configure BPDU filtering on your router to prevent BPDU leakage.
* **Proxy ARP prohibition** -- Disable Proxy ARP on all router interfaces connected to the exchange.
## Traffic filtering and broadcast limits
* **Prohibited link-local protocols** -- Do not forward frames addressed to link-local multicast or broadcast destination protocols to Extreme IX ports, including:
* Discovery protocols: CDP, EDP, LLDP
* VLAN/trunking protocols: VTP, DTP
* Router and control traffic: IRDP, ICMP redirects, BOOTP/DHCP
* **Allowed broadcast and multicast packets** -- Extreme IX blocks destination broadcast and multicast frames by default, except for broadcast ARP packets and multicast IPv6 Neighbor Discovery (ND) packets.
* **Broadcast rate limiting** -- Broadcast traffic forwarded from a member's port must not exceed 50 packets per second (pps) per physical interface.
## BGP and routing guidelines
* **Prefix announcement limits** -- The smallest IP address block you can advertise over Extreme IX is a `/24` (IPv4) or `/48` (IPv6).
* **Routing table policy** -- Do not advertise full internet routing tables. Advertise only your authorized local prefixes, DNS IP pools, and end-user IP pools.
## Technical references
For the complete technical specifications, see the [Extreme IX Technical Requirements page](https://extreme-ix.org/resources/technical-requirements).
## PeeringDB record
For step-by-step instructions on updating your network entry, setting your AS-SET, and linking your ports, see [PeeringDB Record](/ix/extreme-ix/peeringdb-record).
# Extreme IX Status Page Subscription
Source: https://docs.megaport.com/ix/extreme-ix/status-page-subscription
This help topic describes how to subscribe to maintenance and outage alerts on the Extreme IX status page.
We recommend that all members subscribe to automated updates on the Extreme IX status page. Subscribing ensures that your operations and NOC teams receive alerts about scheduled maintenance, fiber cuts, or regional platform disruptions.
## Status page incident categories
The status portal categorizes incidents into two areas:
* **Peering updates** -- Content provider issues, traffic disruptions, or third-party maintenance activities that are independent of Extreme IX infrastructure.
* **Network updates** -- Operational issues that directly affect Extreme IX core infrastructure, including local network outages, switch degradation, optical fiber cuts, and planned maintenance windows.
## Subscribe to maintenance and outage alerts
To configure location-specific email notifications:
1. Go to the [Extreme IX status page](https://status.extreme-ix.org/).
2. Click **Subscribe to Updates** at the top right of the page.
3. Select the **Email** tab and enter your NOC or operations team email address.
4. Click **Select Services**, then select only the exchange locations (for example, Mumbai, Delhi, Chennai) where your network has an active presence. This prevents alerts for locations outside your footprint.
5. Click **Subscribe**.
Extreme IX sends a confirmation link to your email address. Click the link to start your subscription.
# France-IX Connectivity
Source: https://docs.megaport.com/ix/france
This help topic describes how Megaport works with the France-IX internet peering exchange.
France-IX operates a series of Internet Peering Exchanges (IXs) throughout France, and partners with Megaport as part of our IX platform. IXs can exchange data traffic between networks more directly and efficiently, reducing bandwidth usage on network uplink connections. For more information about France-IX, see [https://www.franceix.net/en/](https://www.franceix.net/en/).
You can connect to France-IX through a VXC. VXCs can be ordered from any location on the Megaport network to France-IX ports.
VXCs are provisioned and ordered to France-IX using the Megaport Marketplace and Service Key connection types. Megaport Marketplace and Service Key VXCs can be created to France-IX from Ports and MVEs.
There are different ways that you can start the connectivity request process and receive a service key from France-IX. For example, you can contact your Megaport Account Manager or the France-IX sales team at [sales@franceix.net](mailto:sales@franceix.net). This topic describes the standard method where a VXC request is done through the Megaport Marketplace to France-IX as the first step. For more information, see [Request a connection to France-IX by creating a VXC in the Megaport Marketplace](#franceix-marketplace).
You can also create VXCs to France-IX using the public Megaport API. When creating a VXC, first use the *FRANCEIX* connectType in the GET Partner Megaports endpoint to identify the France-IX port to connect to. For more information, see [Megaport API Overview](/api) and [Connections](https://dev.megaport.com/#8d2016b0-1b93-4734-a4ab-89ab2fae8cc3).
## Request a connection to France-IX by creating a VXC in the Megaport Marketplace
Megaport Marketplace is an online hub where global service providers and enterprise customers interconnect. As a Megaport customer, you can order VXCs to public France-IX ports in the Megaport Marketplace.
You can create a VXC to France-IX from a Port or MVE.
After you successfully create a VXC in the Megaport Marketplace, Megaport sends email notifications to both the service provider (France-IX) and the customer (you). The VXC connection request needs to be approved by the service provider. For more information about the notification and approval process, see [Megaport Marketplace Notifications](/marketplace/notifications).
For more information about the Megaport Marketplace, see [Megaport Marketplace Overview](/marketplace/overview).
**To request and deploy a VXC to France-IX from a Port or MVE**
1. In the Megaport Portal, go to the **Services** page and select the Port or MVE you want to use.\
If you haven't already created a Port, see [Creating a Port](/connections/creating-port). For MVEs, see [MVE Overview](/mve).
2. Click **+Connection**.
3. Click **Megaport Marketplace**.
4. Select France-IX as the provider.\
The list of destination ports with availability for the provider appear, including diversity information.
5. Select the destination port then click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The speed tiers available are dependent on the selected location and speed of the Port. For example, you cannot create a 10 Gbps VXC if the A-End Port is 1 Gbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged** to remove the VLAN tagging for this connection. The untagged option limits you to only one VXC deployed on this Port.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next** to view the Summary page.\
The monthly rate is based on the B-End surcharge and VXC price.
8. Confirm the configuration and pricing, then click **Add VXC**.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
After ordering the VXC, France-IX will be notified. France-IX will contact Megaport's IX team to source the mandatory information required for the agreement with France-IX. After your information has been shared with France-IX and your request has been approved, France-IX will send you a service key that can be used to create a VXC. For more information about this process, see [Creating a VXC with a service key](#franceix-servicekey). The previous VXC that was created in the Megaport Marketplace will be removed automatically.
## Creating a VXC with a service key
A service key is a code that is given by one Megaport account holder to another to connect two separate businesses together. Customers who have separate Megaport accounts can connect their Ports to each other across the Megaport network, enabling business-to-business VXCs.
The service key is provided by France-IX with preconfigured settings, and you use this service key to create a VXC between locations. For more information about service keys, see [Setting up Service Keys](/marketplace/service-keys).
You can create a VXC to France-IX from a Port or MVE.
**To create a VXC to France-IX from a Port or MVE**
1. In the Megaport Portal, go to the **Services** page and select the Port or MVE you want to use.\
If you haven't already created a Port, see [Creating a Port](/connections/creating-port). For MVEs, see [MVE Overview](/mve).
2. Click **+Connection**.
3. Click **Enter Service Key**.
4. Enter the service key in the **Megaport Service Key ID** field.\
Megaport validates the key and displays basic information about the key.
5. Click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps up to the maximum limit defined by the service key (or Port speed). For example, if the service key maximum is 1 Gbps and the Port has 10 Gbps, the maximum speed is 1 Gbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.\
The B-End VLAN for the provider side termination is automatically populated based on the service key.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next** to view the Summary page.\
The monthly rate is based on the B-End surcharge and VXC price.
8. Confirm the configuration and pricing then click **Add VXC**.
9. Click **Review Order**.
10. Review the Order Services agreement and click **Order Now**.\
The VXC is automatically provisioned. However, if a speed change is made then it is subject to approval by France-IX.
# Internet Exchange Overview
Source: https://docs.megaport.com/ix/index
This help topic provides an overview of how Megaport works with internet peering exchanges (IXs).
Megaport owns and operates a series of Internet peering exchanges (IXs) in the majority of our global networks. IXs provide greater efficiency between networks and allow traffic to be exchanged directly, reducing latency and bandwidth usage on client internet connections.
There are two main types of IX peering arrangements:
* **Multilateral** - Multilateral peering (MLPA) is the default when you connect to MegaIX. With multilateral peering, you use BGP to peer with both route servers (RS1 and RS2) for an IX market, you advertise your routes to the route servers, and all routes available from all other multilaterally peered connections are advertised to your peer from the route servers.
* **Bilateral** - The second type of peering is bilateral peering (BLPA). This method is required for peers that do not participate in multilateral peering through the route servers and establishes a direct peering relationship with another entity on the exchange. You can participate in both multilateral and bilateral peering across the Megaport IX infrastructure.
If you are connecting to an AMS-IX location, see [AMS-IX Connectivity](/ix/ams).
# IX Requirements
Source: https://docs.megaport.com/ix/ix-requirements
This help topic provides an overview of the (IXs) requirements.
Before configuring your IX connection, ensure that you meet these requirements:
* **Permitted traffic types** -- All frames forwarded to the Internet Exchange must be Ethernet II (DIX), using ARP (0x0806), IPv4 (0x0800), or IPv6 (0x86DD) Ethertypes.
* **First ASN** -- In a standard BGP configuration the first ASN in the path will match the peer ASN. In multi-lateral peering, the first ASN is the downstream peer that provides the routes. This reduces AS path lengths for correct routing decisions. To permit multi-lateral peering, configure your devices so they do not enforce the first AS requirement. For example, on a Cisco router the command is **no bgp enforce-first-as**.
To avoid any unneeded layer 2 frames toward the IX, a VLAN tagged MegaIX service is recommended.
To prevent members from sending all the internet routes to Megaport, we limit the number of prefixes (MaxPFX) that Megaport can receive. The default limit is 1000 IPv4 routes and 100 IPv6 routes. Exceeding this value results in ending the session, however you can contact Megaport support if you require a reset.
## Illegal traffic types
The following frames are **not** permitted on the Internet Exchange:
* **Multiple MAC addresses** -- MegaIX operates on the principle of one router per port, meaning that frames must have the same source MAC address behind each port in each VLAN. Some members connect through intermediate switches or use a Layer 2/Layer 3 hybrid device. If these devices are not configured properly they can cause forwarding loops, STP instabilities, and unwanted traffic on the Exchange.
* **Multicast and broadcast (with the exception of ARP and IPv6 neighbor discovery)** -- Only exchange unicast routes over your BGP sessions in the Peering LANs. Multicast traffic is not permitted on (unicast) Peering LANs.
* **Frames from Proxy ARP** -- Peering VLAN traffic is exchanged based on BGP routes, so it is unnecessary to answer ARP queries for any IP addresses other than those configured on your MegaIX interface. Some vendors enable Proxy ARP by default, which can lead to unwanted traffic on your network. If you have Proxy ARP enabled at MegaIX, it is likely to be enabled at other peering points, which allows parties on both sides to use you as a transit.
* **LLC/SNAP (Subnetwork Access Protocol) frames** -- LLC/SNAP encapsulation (802.2) is not permitted because the IX infrastructure is based on the Ethernet II standard.
* **STP (Spanning Tree)** -- Devices connected to the MegaIX port are not permitted to be visible as Layer 2 bridges, and should not use STP or any other proprietary L2-specific protocol.
* **Vendor discovery protocols (CDP, EDP, FDP, MNDP)** -- Some vendors (e.g. Cisco and Extreme Networks) run discovery protocols by default. Running discovery protocols should be avoided as it can cause unwanted broadcast or multicast traffic.
* **Internal routing protocols (OSPF, EIGRP, IGRP, and ISIS)** -- BGP is the only routing protocol permitted on the Peering VLANs. Interior routing protocols only cause unnecessary multicast and broadcast traffic.
* **Cisco Layer 2 keepalives** -- By default, Cisco routers and switches periodically test their Ethernet links by sending out loopback frames (Ethertype 0x9000) addressed to themselves. In a switched environment, this tests the functionality of the switch and keeps the router's MAC address in the switch's address table. In the MegaIX environment, this is not useful because MAC timeouts are longer than the typical BGP or ARP timeouts.
* **Non-unicast IPv6 (IPv6 ND-RA)** -- IPv6 hosts on the MegaIX are not autoconfigured, and can cause IPv6 router advertisements to generate unnecessary traffic.
* **Non-unicast IPv4 (IGMP, DHCP, TFTP)** -- Do not configure multicast on the MegaIX interface. The Peering LAN is for unicast IP traffic only. The only permitted non-unicast traffic is an ARP query.
* **Trunking protocols** -- On Cisco Layer 2 devices such as the 2900 and 3500 series, disable VTP (VLAN Trunking Protocol), DTP (Dynamic Trunking Protocol), LLDP, and UDLD.
* **Non-IP protocols** -- Some vendors enable protocols other than IP by default. For example, in some versions of IOS Cisco enables MOP (Maintenance Operation Protocol). Non-IP traffic is not appropriate for the MegaIX environment.
Megaport imposes a set of restrictions to ensure smooth operation of the MegaIX. Megaport reserves the right to temporarily disable offending services to maintain the health and stability of the MegaIX.
### Exceptions
Link-local protocols ARP and IPv6 ND (Neighbor Discovery) are exceptions, and are permitted.
## Additional considerations
There are some considerations when thinking about configuring an IX peering arrangement:
* MegaIX route servers do not recognize the BGP community attribute **no-export**. This community attribute is passed transparently to the other peers connected to the route server.
* Multiple Exit Discriminator (MED) values are considered in the route selection rules only when the advertising ASN is the same for candidate routes. MED values are not modified by the route servers. Values advertised to the route servers are passed unaltered to other peers.
* All routes on the IX are given equal local preference by the route servers. The route servers do not compare the BGP router ID for best route selection, instead preferring the oldest route when all other attributes are equal.
* Do not configure "network 194.146.118.0/24" or any of the other peering LANs in your router's BGP configuration.
## IX pricing estimates
Remote (non same metro) IX pricing is the same as VXC. An IX within the same metro as a Port is no charge, an IX in a different metro to a Port is charged at VXC rates. In the Megaport Portal, you can test different IX configurations without any obligation, to obtain a price estimate.\
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing).
## Helpful references
* [Wikipedia: Internet exchange point](https://en.wikipedia.org/wiki/Internet_exchange_point)
* [Resource Public Key Infrastructure (RPKI)](https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/)
* [BGP Origin Validation](https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/bgp-origin-validation/)
* [Read the Docs RPKI Documentation](https://rpki.readthedocs.io/en/latest/)
* [RFC 8210](https://tools.ietf.org/html/rfc8210/)
* [EURO-IX Large BGP Community](https://www.euro-ix.net/en/forixps/large-bgp-communities/)
* [Advertisement of Multiple Paths in BGP](http://tools.ietf.org/html/rfc7911/)
# IX Telemetry
Source: https://docs.megaport.com/ix/ix-telemetry
This help topic provides an overview of IX Telemetry.
IX Flow Telemetry is a generic industry term used for technology that allows measurement of network traffic between peers by a user. The IX Telemetry feature in Megaport allows you to see the peering rates of any IX connections your company has deployed.
You can use IX Telemetry to view and analyze your network traffic flow statistics, check whether a peer is using a lot of network traffic, and diagnose and troubleshoot any configuration or networking issues.
IX Telemetry data is collected every 5 minutes and is available for the last 30 days. The data is collected at the IX level, so it includes all traffic that flows through the IX connection, regardless of the specific peers involved.
IX Telemetry is presented as a **traffic view** graph. The graph shows the traffic flow between peers in a visual way, with the width of the lines representing the amount of traffic.
## Viewing IX Telemetry
To view IX Telemetry in the Megaport Portal, choose **Monitoring and Diagnostics > IX Telemetry**.
## Using IX Telemetry
The IX Telemetry page displays data for all IX connections that your company has deployed.
Use the filters to view the data you want to see:
* **IX service** -- Select the IX service for which you want to view telemetry.
* **Peers** -- Select the top 5 peers by traffic, or select specific peers to view.
* **Date select** -- Select the date range for which you want to view telemetry data.
* **Flow type** -- Select BITS or PACKETS.
### Using the traffic view
The traffic view displays traffic flows between peers, with the width of each line representing the volume of traffic. Hover over a line to view the traffic volume for that peer.
Use the buttons to display incoming traffic, outgoing traffic, or both. You can also filter the data by peer or limit the view to the top five peers by traffic volume.
### Viewing traffic over time
Below the traffic view diagram on the same page, a time-series chart shows when traffic changed over time.
The time-series chart uses the same controls (incoming, outgoing, or both) that the traffic view uses. The chart has no separate toggle or control. For a single direction (incoming or outgoing), the chart shows one line per selected peer. When both directions are shown, there is a solid line for each inbound peer and a dashed line for each outbound peer.
Each peer's line color matches its color in the traffic view diagram. Hover the cursor over a line to view the peer label in the format **Company (ASxxxx)**. When both traffic directions are displayed, the label also indicates **In** or **Out**.
When there is no data, the chart displays "No graph data available".
## Accessing IX Telemetry through the API
Megaport also offers a public API that you can use to access the services available through IX Telemetry. You can use the [GET IX Telemetry API](https://dev.megaport.com/#d9699d8a-38e5-47c7-a55b-3a2de4668bf2) to return telemetry details for a specified IX.
For more information, see [Megaport API Overview](/api).
# Changing the Speed of a Termed IX
Source: https://docs.megaport.com/ix/ix-termed-rate-change
This help topic describes how changing the speed of a termed Internet Exchange (IX) connection works.
If you have an Internet Exchange (IX) connection on a contract term, you can change the speed of the IX.
When you put an IX on a contract term, you specify a rate limit, which is called the **committed term speed**. This is the minimum speed allowed on the IX during that contract term.
There are restrictions on the changes that you can make to the rate limit of a termed IX:
* You can increase the speed above the committed term speed.
* You can reduce the speed to the committed term speed.
* You cannot reduce the speed below the committed term speed.
You can change the speed as many times as you need during a term within these restrictions.
## IX speed change example
As an example, you create an IX on a 12-month term with a rate limit of 1 Gbps. This is the committed term speed.
You can increase the speed to any value above 1 Gbps, such as 1.5 Gbps or 2 Gbps.
You can decrease the speed down to 1 Gbps (the committed term speed), but you cannot decrease it below 1 Gbps while the IX is on term.
## Pricing
The pricing rules for rate limit changes to a termed IX are as follows:
* The term discount is applied as a fixed monthly amount and does not change throughout the term length, regardless of any speed changes.
* The fixed monthly discount amount is calculated off the percentage discount associated with the selected term length and original committed term speed.
This means if you increase the speed of an IX on term, the term discount stays fixed to the original discounted amount based on the original committed term speed.
* If Minimum Term Renewal is enabled and you change the IX speed, the service will be repriced at the current market rate. The contract term will renew at the same market rate and term discount as when the speed change was ordered.
### Pricing example
In this scenario, a 1 Gbps remote IX is created on a contract term. The table below shows the rack rate price, term discount, and total charged for each term duration.
| 1 Gbps IX | No Min Term | 12 Months | 24 Months | 36 Months |
| - | - | - | - | - |
| Rack Rate Price | \$120 | \$120 | \$120 | \$120 |
| Term Discount | \$0 | \$20 | \$25 | \$30 |
| Total | \$120 | \$100 | \$95 | \$90 |
If the speed of this service is increased to 2 Gbps on the 1st of the month, the following pricing will apply:
| 1 Gbps IX updated to 2 Gbps | No Min Term | 12 Months | 24 Months | 36 Months |
| - | - | - | - | - |
| Rack Rate Price | \$240 | \$240 | \$240 | \$240 |
| Term Discount | \$0 | \$20 | \$25 | \$30 |
| Total | \$240 | \$220 | \$215 | \$210 |
| Charge increase | \$120 ⬆ | \$120 ⬆ | \$120 ⬆ | \$120 ⬆ |
Note the rack rate price rises with the speed increase, but the term discount remains the same.
**Invoicing**
You will see two line items on your invoice:
* The service rack rate charge at the Month to Month/No Minimum Term rate.
* The Fixed Monthly Term Discount.
## Canceling the IX
If the termed IX is canceled, the early termination fee (ETF) is calculated based on the committed term speed, not the speed when the IX is canceled.
## Considerations
If you need greater flexibility in terms of increasing or decreasing the IX speed, you might benefit from ordering an IX on term at the minimum speed you require. This way, although the term discount will be lower, you will still get a term discount, with the added benefit of being able to adjust the speed as required. If you order the IX on No Minimum Term, you will receive no discount at all.
If you don’t anticipate the need to adjust the speed of the IX regularly, you should order the IX on term at the speed required to benefit from a higher term discount.
## Helpful references
* [Editing an IX](/ix/editing-an-ix)
* [IX Pricing and Contract Terms](/finance/ix-pricing)
* [Joining an IX](/ix/joining-an-ix)
* [Overview of MegaIX Features](/ix/overview-features)
# Joining an IX
Source: https://docs.megaport.com/ix/joining-an-ix
This help topic provides an overview of joining an IX.
You can join an Internet Exchange for Megaport and MegaIX locations.
Before joining an IX, ensure that you can meet the [requirements](/ix/ix-requirements).
**To join an Internet Exchange for Megaport and MegaIX locations**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.\
If you haven't already created a Port, see [Creating a Port](/connections/creating-port).
2. Add an IX connection for the Port.\
Click **+Connection** then click **Internet Exchange**.
3. Select the IX location then click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your IX to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps.\
For metro connections, the rate limit for an IX cannot exceed the aggregate port speed. For long haul (non-metro) connections, the maximum rate is dynamically calculated based on network routes used to deliver the service. The calculation uses the Ports at each end and bases calculations on the lowest rate. The rate cannot exceed the speed of the physical interface on which it resides.
* **IX State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting down an IX for failover testing](/ix/shutting-down-an-ix).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
The VLAN ID must be unique on this Port and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN ID. Megaport validates the VLAN ID before proceeding with the order. If you don't specify a value, Megaport will assign one. You can also select **Untagged** to remove VLAN tagging for this connection; however, this limits you to only one IX (or VXC) on this Port.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [IX Pricing and Contract Terms](/finance/ix-pricing).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.
6. Specify the IX details:
* **ASN** -- The autonomous system number (ASN) of your network. The ASN can be either a 16-bit or 32-bit ASN (2 or 4 byte) but must be a public AS.
* **MAC Address** -- The MAC Address of the Layer 3 device that will establish the BGP peering session with the IX. Connections to the IX on this VXC will be locked to this address for security purposes. If you do not have the correct MAC available at the time of ordering, enter a placeholder MAC (such as 00:01:00:01:12:34) as this field remains editable after deployment.
* **BGP Password** (optional) -- Add a BGP password to the IX service. This field can be left blank. The password length is from 1 to 25 characters. The password can include any of these characters:\
a-z\
A-Z\
0-9\
! @ # . \$ % ^ & \* + = - \_
Click the eye icon to see the password as you type. The view persists until you click the eye icon again to hide the password.
* **Graph Visibility** -- Specify how to display your traffic graphs in the MegaIX Looking Glass tool. Public lets other clients see your IX throughput; Private hides this information from other clients.
* **Peer AS-SET** (optional) -- The peer AS-SET value defines the AS macro filter for the peer. Megaport uses this value to generate a list of prefixes this AS can originate, and this list filters announcements through the route server.
Another name for this field is AS-MACRO as it contains a list of AS numbers belonging to this peer.
If you don’t have a Peer AS-SET, you can enter your ASN in this field (You can only send routes that originate from your own AS). Invalid prefixes won’t be announced by the route server and an incorrect configuration results in the route server rejecting all your prefixes.
If not specified, your own ASN will be used in the filter and you can only send routes that originate from your own AS and prefixes registered to that AS.
7. Click **Next**.\
A summary page appears that includes the monthly cost. Click **Back** to make changes or click **Add IX** to move this configuration to your cart and proceed through the checkout process.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
After deployment, Megaport sends an email to your registered email address with additional information on how to finish the BGP configuration.
# MegaIX Looking Glass
Source: https://docs.megaport.com/ix/megaix-looking-glass
This help topic provides an overview of MegaIX Looking Glass.
Megaport operates a public, web accessible MegaIX Looking Glass for peers and network operators to investigate the current routing state. You can query both the primary and redundant route servers for live BGP data.
The MegaIX Looking Glass is available at [https://lg.megaport.com](https://lg.megaport.com).
The MegaIX Looking Glass provides full-featured visibility into traffic routing and the IX route server environment. This visibility helps you troubleshoot connections by searching for an AS number, a peer, or a particular IP prefix on the IX route server.
Use the BGP neighbor overview to look at a specific route server. The Looking Glass shows you which networks are available at a specific route server, provides BGP session information (established and down), and provides a summary of received and filtered routes from each peer.
# Metro IDs
Source: https://docs.megaport.com/ix/metro-ids
This help topic shows the Metro ID numbers that can be used to filter routes based on location.
Refer to this list of metro areas when configuring routing policy based on a geographic location.
For more information, see [BGP Communities](/ix/communities).
| ID | Location |
| - | - |
| 1 | Sydney |
| 2 | Brisbane |
| 3 | Melbourne |
| 4 | Singapore |
| 5 | Auckland |
| 6 | Hong Kong |
| 7 | Chicago |
| 9 | Seattle |
| 10 | Los Angeles |
| 11 | Ashburn |
| 12 | New York |
| 13 | Dallas |
| 14 | Toronto |
| 15 | Perth |
| 16 | Amsterdam |
| 17 | London |
| 18 | Dublin |
| 19 | Stockholm |
| 20 | Portland |
| 21 | Las Vegas |
| 22 | Atlanta |
| 23 | Frankfurt |
| 24 | Berlin |
| 25 | Munich |
| 26 | Hamburg |
| 27 | Dusseldorf |
| 28 | Nuremberg |
| 29 | Sofia |
| 34 | Phoenix |
| 35 | Houston |
| 36 | Cincinnati |
| 37 | Norwalk |
| 38 | Austin |
| 39 | Montreal |
| 40 | Quebec City |
| 42 | Culpeper |
| 43 | Miami |
| 44 | Boston |
| 45 | San Antonio |
| 46 | Adelaide |
| 47 | Wellington |
| 48 | Denver |
| 50 | Kansas City |
| 51 | Hamilton |
| 52 | San Diego |
| 53 | Sacramento |
| 54 | St. Louis |
| 55 | Philadelphia |
| 56 | Columbus |
| 57 | Canberra |
| 58 | Minneapolis |
| 59 | Tampa |
| 60 | Pittsburgh |
| 61 | Nashville |
| 62 | Orlando |
| 64 | Warsaw |
| 65 | Zurich |
| 66 | Geneva |
| 68 | Charlotte |
| 69 | Vancouver |
| 70 | Vienna |
| 71 | Dubai |
| 72 | Omaha |
| 73 | Bay Area |
| 74 | Salt Lake City |
| 75 | Raleigh |
| 76 | Helsinki |
| 77 | Oslo |
| 78 | Paris |
| 79 | Birmingham |
| 80 | Brussels |
| 81 | Stamford |
| 82 | Memphis |
| 83 | Wollongong |
| 84 | Wise |
| 85 | Tokyo |
| 86 | Osaka |
| 87 | Calgary |
| 88 | Marseille |
| 89 | Copenhagen |
| 90 | Ottawa |
| 91 | Rogaland |
| 92 | Luxembourg |
| 93 | Manchester |
| 94 | Edinburgh |
| 95 | Grand Rapids |
| 96 | Reno |
| 97 | Madrid |
| 99 | Detroit |
| 100 | Newcastle |
# Moving IXs
Source: https://docs.megaport.com/ix/move-ix
This help topic describes how you can move the A-End of an Internet Exchange in the Megaport Portal.
Once you have created and deployed an Internet Exchange (IX) on the Megaport network, you can move the A-End, effectively moving the IX. This is a useful function for reducing interruptions during maintenance and other tasks that would otherwise cause downtime.
## Which IXs can be moved?
The following rules apply regarding which IXs you can move:
* The IX must at least be in a Configured state
* An IX locked by a Company Admin cannot be moved
* You can move an unlocked IX under a locked Port
* The source and destination Ports must be owned by the same customer account.
## Conditions for moving an IX
There are conditions that must be met before moving an IX. The following criteria must be satisfied before you can move an IX.
* You can only move to a Port within the same metro as the current Port. For more information about metros, see [Metro IDs](/ix/metro-ids).
* The destination Ports must have enough capacity for the selected connection.
* When a VLAN is specified, that VLAN must be available on the destination Port.
* The move must not cause a change to billing.
If a move is regarded as invalid, an error message is displayed and the IX is not moved.
If you cancel the move, the IX is not affected and it remains connected to its original Port.
## Moving one or more IXs
You can move one or more IXs at a time. Select the Port that the IXs are to be moved from, then select the IXs to be moved.
**To move one or more IXs**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.
2. Click the **Move Connections** icon next to the Port or the IX.
The **Move Connections** icon is greyed out if the Port or IX is not valid. For more information, see [rules](#which) and [conditions](#conditions) above.
3. Select one or more connections to move. Each move is subject to the [rules](#which) and [conditions](#conditions) described above. If a connection is not valid, it will be displayed but will not be available to select.
You can select or deselect connections individually, or use the **Select All** button.
4. Select the destination Port in the Move To list.\
The Port selection list is filtered by the rules described in the [rules](#which) and [conditions](#conditions) described above. If a connection is not valid, it will be displayed but will not be available to select.
You can filter the Ports by selecting a diversity zone at the top of the Move To list.
5. Click **Next**.
6. Review your selection and click **Move**.
7. In the prompt that shows the intended move, review the details again and click **Confirm**.
The Summary table shows the status of the move. It will either show a *working* hourglass, a message saying *success*, or an error message.
The *Success* status means that the request was successfully submitted and the IX(s) have been moved. The change might take up to 2 minutes to appear in the Megaport Portal.
A *Failure* message shows that the move has failed. The IX(s) will not be moved.
# Overview of MegaIX Features
Source: https://docs.megaport.com/ix/overview-features
This help topic provides an overview of MegaIX features.
This topic provides an overview of key MegaIX features, including advanced tools for visibility, robust routing enhancements, and support for industry standards.
## MegaIX Looking Glass
The MegaIX Looking Glass provides full-featured visibility into traffic routing and the IX route server environment. This visibility helps you troubleshoot connections by searching for an AS number, a peer, or a particular IP prefix on the IX route server. For more information, see [MegaIX Looking Glass](/ix/megaix-looking-glass).
## Route server filtering
The invalid routes are filtered and are easy to identify using the Looking Glass. For more information about RPKI, see any of these helpful references:
* [Resource Public Key Infrastructure (RPKI)](https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/)
* [BGP Origin Validation](https://www.ripe.net/manage-ips-and-asns/resource-management/rpki/bgp-origin-validation/)
* [Read the Docs RPKI Documentation](https://rpki.readthedocs.io/en/latest/)
* [RFC 8210](https://tools.ietf.org/html/rfc8210/)
## Peer AS-SET
The Peer AS-SET option is enabled for all connections. This value defines the AS macro filter for the peer. Megaport uses it to generate a list of prefixes and origin AS values that an AS can originate, and this list filters announcements through the route server.
## Large BGP community support
The upgraded route servers support an [extended range of action communities](/ix/communities) that Megaport IX route servers are able to recognize. As part of this, the [EURO-IX Large BGP Community](https://www.euro-ix.net/en/forixps/large-bgp-communities/) standard is also supported. Megaport recommends migrating to these communities.
MegaIX communities will be supported for 12 months before they are deprecated by Megaport.
## BFD support
The route server upgrade passively enables the Bidirectional Forwarding Detection (BFD) protocol on route servers in all Megaport IX locations with a 300 millisecond interval. The BFD protocol detects any path failures between BGP neighbors.
## BGP Add Path
IX supports the BGP add-path feature to enable advertisements of multiple paths to a single address prefix, without the new paths implicitly replacing any previous paths.
Add-path support provides:
* Optimal routing and routing convergence in a network by providing potential alternate or backup paths.
* BGP traffic load balancing across more than one path.
For more information, see [Advertisement of Multiple Paths in BGP](http://tools.ietf.org/html/rfc7911/).
Your network must support BGP add-path functionality to benefit from its features.
## IX Telemetry
You can use IX Telemetry page to view and analyze your network traffic flow statistics, check whether a peer is using a lot of network traffic, and diagnose and troubleshoot any configuration or networking issues.
For more information, see [IX Telemetry](/ix/ix-telemetry).
# Configuring IX Redundancy
Source: https://docs.megaport.com/ix/redundancy
This help topic provides an overview of how IX redundancy works.
To ensure high availability and reliability of your IX service, it's critical to follow best practices for redundancy. This topic describes the recommended configuration, along with the configurations to avoid.
The following is a summary of requirements:
* **Peering**: Every IX service must peer with both route servers.
* **Layer 2 isolation**: Customer routers must not share the same Layer 2 domain.
* **Redundancy**:
* Requires two separate Ports.
* Both IX services must peer with both route servers.
* Each router must operate on a distinct Layer 2 domain.
## Recommended configuration: single and redundant IX
### Single IX configuration
For basic configuration:
* Peer with both route servers to ensure redundancy within the IX.
* Do not share a Layer 2 domain on the customer side, that is, avoid using a switched network.
### Redundant IX configuration (recommended method)
For optimal redundancy and reliability, we recommend the following configuration:
* Use two separate Ports to connect to the same IX.
* Each IX service must peer with both route servers.
* Ensure each router is on its own Layer 2 domain (do not share a switched network between routers).
This approach ensures high availability and minimizes the risk of service disruptions caused by network failures.
## Configurations to avoid
### Not recommended or unsupported configuration
These configurations are problematic and prone to outages:
* Using a switched Layer 2 network on the customer side, which can introduce loops and instability.
* Using two services for redundancy and only peering with one route server.
### Invalid configuration
This configuration will not work and is unsupported:
* Connecting a single IX service to a switched network with multiple customer routers.
# Shutting Down an IX for Failover Testing
Source: https://docs.megaport.com/ix/shutting-down-an-ix
This help topic provides an overview of shutting down an IX for failover testing.
Once you have joined an IX on the Megaport network, you can temporarily shut down the IX for failover testing, redundancy, or network design testing purposes.
When an IX has been shut down, you can view the IX service that has been shut down, and re-enable the IX service.
For more information about shutting down a Megaport service, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
You can also decide whether to set the initial state of the connection to enabled (default) or shut down when creating the IX service. For more information, see [Joining an IX](/ix/joining-an-ix).
**To shut down an IX**
1. In the Megaport Portal, go to the **Services** page and locate the IX.
2. Click the gear icon next to the IX to make changes.
The Connection Configuration page appears.
3. In the **IX State** field, click **Shut Down**.\
A prompt appears, asking you to confirm the action.
4. Read the prompt then click **Confirm** and **Save**.\
The IX is shut down. This can take up to two minutes to take effect and be updated in the Megaport Portal.
**To re-enable an IX**
1. In the Megaport Portal, go to the **Services** page and locate the IX that is shut down.
2. Click the gear icon next to the IX.
3. In the **IX State** field, click **Enabled**.
4. Click **Save**.\
The IX is now enabled. This can take up to two minutes to take effect and be updated in the Megaport Portal.
# Terminating an IX
Source: https://docs.megaport.com/ix/terminating-an-ix
This help topic provides an overview of terminating an IX.
You can terminate an IX directly from the Megaport Portal.
IXs can be individually terminated or are terminated as part of terminating the attached Port.
Terminating an IX on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. For more information about IX contract terms, see [IX Pricing and Contract Terms](/finance/ix-pricing/).
You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate an IX**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the IX you want to terminate.
The Terminate Services window appears. Early termination fees will be shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the IX. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the IX termination, or click **No, Keep Services** to cancel.\
The IX is deleted from the Megaport network.
# Requesting a Connection to a Service Provider
Source: https://docs.megaport.com/marketplace/connections
This help topic describes how to request a connection to a service provider in the Megaport Marketplace.
This topic describes how to request a connection to a service provider in the Megaport Marketplace.
Customers can start a service request from a Port, MCR, MVE, or NAT Gateway to service providers with a [Megaport Marketplace profile](/marketplace/profile). When a customer starts the connection request, the service provider is notified of the request by email and the service provider can accept or deny the request.
**To create a connection request to a service provider**
1. In the Megaport Portal, go to the **Services** page.
2. Select the Port, MCR, MVE, or NAT Gateway for the connection then click **+Connection**.
3. Click **Megaport Marketplace** as the destination type.
4. Search for and then select the provider.\
The destination services for the service provider appear.
5. Select a destination service.\
Typically, you would select the service closest to your Port, MCR, MVE, or NAT Gateway.
6. Click **Next**.
7. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Enter the purchase order number specified when registering the billing market.
* **Rate Limit** -- The speed of your connection in Mbps up to the maximum limit defined by the key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection. This must be a unique VLAN ID on this port and can range from 2 to 4093.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
8. Click **Next**.
9. If you are connecting from an MCR or NAT Gateway, review and edit the A-End Connection Details.\
Use this page to enable , IP address and subnet mask, , and connections. For more information, see [Creating an MCR VXC](/mcr/mcr-vxc) and [Configuring an MCR](/mcr/configuring-mcr), or for NAT Gateway see [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc).
10. Click **Next**.
11. If the service provider has configured a form to collect additional information, complete the **Service Request Form** step. Forms streamline onboarding by gathering all necessary details upfront.\
For more information, see [Completing a form (customers)](/marketplace/forms#marketplace-form).
12. Click **Next**.
13. Click **Add VXC**.
14. Click **Review Order**.
15. Review the Order Services agreement and click **Order Now**.
After the customer makes the connection request, Megaport sends email notifications to both the service provider and the customer. For more information about the notification and approval process, see [Megaport Marketplace Notifications](/marketplace/notifications).
## Helpful references
* [Creating a Megaport Marketplace Profile](/marketplace/profile)
* [Megaport Marketplace FAQs](/marketplace/marketplace-faqs)
* [Megaport Marketplace Forms](/marketplace/forms)
* [Megaport Marketplace Notifications](/marketplace/notifications)
* [Megaport Marketplace Overview](/marketplace/overview)
# Megaport Marketplace Forms
Source: https://docs.megaport.com/marketplace/forms
This help topic describes how service providers can create forms to collect customer information during connection requests, and how customers complete these forms.
Megaport Marketplace forms let service providers collect onboarding information from customers during connection requests. Forms simplify onboarding by gathering necessary details upfront, reducing manual communication.
This topic describes how service providers can create forms to collect customer information during connection requests, and how customers complete these forms.
## Megaport Marketplace Forms overview
When a customer submits a connection request to a Megaport Marketplace service provider, the provider might require additional information before approving and provisioning the service. Megaport Marketplace service providers can create forms to collect the information needed to evaluate the connection request. These forms provide a structured way to gather required details as part of the connection request.
**For service providers**, forms let you:
* Define exactly what information you need from customers
* Link forms to specific services for reusability
* Receive completed form data by email or optionally by webhook
**For customers**, when you connect to a provider with a form configured:
* A **Service Request Form** step appears in the connection wizard
* You complete the form fields as part of the connection request
* After deployment, your submitted information appears on a read-only **Service Request Form** tab under the service configuration
## Creating a form (service providers)
As a service provider, you can create forms under your Megaport Marketplace profile and link them to your services. This lets you reuse forms across different services.
* You must be a Company Admin to create and manage forms.
* Form details cannot be changed after a VXC connection has been requested. If you need to change the form details, you must create a new form and link it to the service. Then customers will need to submit a new connection request with the updated form.
**To create a form**
1. In the Megaport Portal, choose User Menu > Admin Settings > Megaport Marketplace.
2. Click the **Service Request Forms** tab of your profile.
3. Click **Create Form**.
4. Enter a name for the form.
5. Define the form fields and validation requirements.\
These field types are supported:
* **Text** -- A free text field for short answers.
* **Email** -- A field for entering a contact email address.
* **Text Area** -- A free text field for answers that might require longer or more detailed responses.
* **Select** -- A drop-down field for selecting a single option from a list of choices. You must define at least 2 options, with a maximum of 100 options per field.
6. Click **Preview Form** to see how the form will appear to customers when they complete it as part of a connection request.
7. Click **Back to Editor** to make any changes to the form, including reordering the fields using the up and down arrows.\
Otherwise, click **Next** to continue.
8. Select the **I confirm this form only collects information strictly necessary to facilitate a connection** check box to confirm that the form complies with Megaport data collection policies.
9. Click **Save Form**.\
You can create as many forms as required.
## Linking forms to your services
After you create a form, you can link it to a specific service to enable data collection when customers connect to that service. Only one form can be linked to each service, but the same form can be reused across multiple services.
**To link a form to a service**
1. In your Megaport Marketplace profile, go to the **Services** tab.
2. Click **Edit** next to the service you want to configure.
3. In the **Ask for additional information** drop-down, select the form to associate with this service.
4. Click **Save**.
## Completing a form (customers)
When you request a connection to a Megaport Marketplace service provider that has a form configured, the connection wizard includes an additional **Service Request Form** step. The service provider has requested this information and your responses will be visible to them.
**To complete a service request form**
1. Start a connection request to a Megaport Marketplace service provider.\
For more information, see [Requesting a Connection to a Service Provider](/marketplace/connections).
2. When you reach the **Service Request Form** step, complete the form fields.
3. Continue through the remaining steps in the connection wizard.
4. Review and submit your order.
## Viewing submitted form data
Both parties can view the submitted form data during the connection request and approval process.
**For customers**, your submitted information appears on a read-only **Service Request Form** tab when viewing the VXC in the Portal.
**For service providers**, you can view the submitted data:
* On the **Service Request Form** step when reviewing and approving the connection request
* By email at the VXC approval stage, so you have the information before you approve the connection
* By webhook (optional) for integration with your systems
## Email notifications
When a customer submits a connection request that includes form data, the form fields are included in the email notification sent to the service provider for VXC approval. This allows the customer-provided information to be reviewed before the service provider accepts or denies the request.
For more information about the notification and approval process, see [Megaport Marketplace Notifications](/marketplace/notifications).
## Webhook integration
Service providers can also receive VXC approval requests via webhooks to automate onboarding. When a customer requests a connection, Megaport sends an HTTP payload with the VXC details directly to your backend systems.
Webhooks are configured and managed globally by Company Admins in the Webhooks section of the Megaport Portal, rather than at the individual form or service level. For more information about configuring webhooks, see [Using Webhooks in the Megaport Portal](/portal-admin/using-webhooks).
## Helpful references
* [Creating a Megaport Marketplace Profile](/marketplace/profile)
* [Managing Megaport Marketplace Forms with the API](/api/api-marketplace-forms)
* [Megaport Marketplace FAQs](/marketplace/marketplace-faqs)
* [Megaport Marketplace Notifications](/marketplace/notifications)
* [Megaport Marketplace Overview](/marketplace/overview)
* [Requesting a Connection to a Service Provider](/marketplace/connections)
# Megaport Marketplace Frequently Asked Questions (FAQs)
Source: https://docs.megaport.com/marketplace/marketplace-faqs
This help topic provides answers to common questions about the Megaport Marketplace.
## How can my customers connect to my services?
Your customers can connect via the internet or privately using on-ramps (Port, MCR, or MVE) on Megaport's network. Private connectivity, similar to how enterprises connect to Amazon Web Services (AWS) or Google Cloud Platform (GCP), offers better performance, security, and resilience. Creating on-ramps is simple and enables your customers to connect to your services seamlessly.
## What other services and platforms can I connect with on the Megaport Marketplace?
Megaport Marketplace includes hundreds of service providers, ranging from AI and UCaaS-focused to industry-specific platforms. You can connect to these providers using Megaport's network the same way you access the cloud or data centers.
If a service provider is not yet on the Megaport Marketplace, we can help onboard them quickly.
## How do I connect to AIx or FSx?
AIx is an ecosystem of service providers offering high-performance infrastructure for AI workloads. You can access hyperscale AI services like Amazon Bedrock and SageMaker, or specialized compute providers such as DigitalOcean, Vultr, and Latitude.sh. FSx is an ecosystem of enterprises and service providers in the financial services industry, built for high-speed data exchange over a resilient private connection.
To connect to AIx or FSx, create an access service (Port, MCR, or MVE) on our network, and then create a Virtual Cross Connect (VXC) to any service provider in the AIx or FSx Exchange. You can discover all AIx and FSx service providers through the Megaport Marketplace.
## How do I offer my services on the Megaport Marketplace?
To list your services:
1. Log in to the Megaport Portal.
2. Create a Megaport Marketplace profile.
For more information, see [Creating a Megaport Marketplace Profile](/marketplace/profile).
3. Create your on-ramps (Port, MCR, or MVE).
Your on-ramps will be publicly visible access points for customers to connect to via a VXC. If you prefer private connections, you can create a Megaport Marketplace profile and use private service keys.
## Do I need to pay to join the Megaport Marketplace?
No, there are no costs associated with listing your services on the Megaport Marketplace.
## Do I need to sign more contracts to list in the Megaport Marketplace?
No additional contracts are needed to list services. If you plan to resell Megaport, you can sign a Global Reseller Agreement (GRA).
## Helpful references
* [Creating a Megaport Marketplace Profile](/marketplace/profile)
* [Megaport Marketplace Forms](/marketplace/forms)
* [Megaport Marketplace Notifications](/marketplace/notifications)
* [Megaport Marketplace Overview](/marketplace/overview)
* [Requesting a Connection to a Service Provider](/marketplace/connections)
# Megaport Marketplace Notifications
Source: https://docs.megaport.com/marketplace/notifications
This help topic describes Megaport Marketplace notifications during the service provider connection process.
With a [profile](/marketplace/profile), service providers can receive connection requests.
When a customer starts the connection request, the service provider is notified of the request by email and the service provider can accept or deny the request.
This topic describes:
* The notifications emailed by Megaport to the service provider and the customer requesting the connection.
* How the service provider can accept or deny the request.
* How to configure email notification groups so Megaport Portal users receive only email updates relevant to their position.
## Requirements for customers of service providers
For an end user to connect to a service provider, they need:
* Access to the Megaport Portal
* A Port or Megaport Cloud Router (MCR) on the Megaport network
* Support for Layer 2/Layer 3
## Service provider and customer notifications
After the customer makes the connection request, Megaport sends email notifications to both the service provider and the customer.
When the service provider is approving a connection, they have the option to make configuration changes for their end of the VXC before granting approval.
**Notification to Service Provider**
If you have configured a form to collect additional information from customers, the submitted form data is included in this notification. For more information, see [Megaport Marketplace Forms](/marketplace/forms).
**Notification to Customer**
## Service provider approval
After receiving the email notification about the connection request, the service provider must log in to the Megaport Portal, navigate to the Approvals section on the right side of the screen, and select either **Accept Request** or **Deny Request**.
If you have configured a form to collect additional information from customers, a **Service Request Form** step appears in the approval workflow where you can view the submitted data before making your decision. For more information, see [Megaport Marketplace Forms](/marketplace/forms).
After the service provider accepts or denies the request, Megaport sends a second notification to the customer with the outcome details.
Megaport sends another email to the customer when the VXC is available.
This establishes the Layer 2 connection from the customer to the service provider.
For connectivity to multiple destination ports, repeat the creation and approval process for each new connection.
Service providers can also use service keys to control customer access to their ports. For more information, see [Setting up Service Keys](/marketplace/service-keys).
If a customer requests a speed change to a higher bandwidth after deployment, Megaport notifies the service provider and they can accept or reject the change.
## Configuring Portal users for email notifications
Each Megaport Portal user is assigned a user role that includes privilege levels. Users configured for Company Admin, Technical Contact, and Technical Admin can subscribe to notifications.
For more information, see [Managing User Roles](/portal-admin/user-management/roles).
Users can choose to receive email notifications from each of these groups:
* Financial
* Company
* Ordering
* Services
* Service Status
Notifications can be selected individually or at the group level. For VXC approvals, enable notifications for the Ordering group.
For more information, see [Configuring Email Notifications](/portal-admin/email-notifications).
## Helpful references
* [Creating a Megaport Marketplace Profile](/marketplace/profile)
* [Megaport Marketplace FAQs](/marketplace/marketplace-faqs)
* [Megaport Marketplace Forms](/marketplace/forms)
* [Megaport Marketplace Overview](/marketplace/overview)
* [Requesting a Connection to a Service Provider](/marketplace/connections)
# Megaport Marketplace Overview
Source: https://docs.megaport.com/marketplace/overview
This help topic describes the features of the Megaport Marketplace.
Megaport Marketplace is an online hub where global service providers and enterprise customers interconnect.
Service providers can showcase their brand, reach global enterprises, scale to new markets, and provide solutions for businesses worldwide.
Enterprises can connect to a broad range of internet services, cloud providers, managed services, and many others.
Key features of the Megaport Marketplace include:
* **Neutral and inclusive** -- Megaport is data center agnostic, meaning that customers can access the Megaport Marketplace and tap into services by some of the world’s leading technology providers without being locked to a single data center provider.
* **Rapid and agile connectivity** -- Customers can find and connect to service providers around the world in minutes.
* **Self-serve** -- Customers can connect with who they want and when they want to meet their specific business needs.
To browse the list of available providers, click the **Marketplace** menu item in the left navigation of the Portal page.
To make your company available on the Megaport Marketplace, you need a Megaport Marketplace profile. If you don't have one, you will be invited to create one when you go to the Megaport Marketplace.
For more information, see [Creating a Megaport Marketplace Profile](/marketplace/profile).
If you have a Megaport Marketplace profile and it is private, you will see a message on the top of the Megaport Marketplace page. The message tells you that you can change your profile to make it visible to other customers.\
Click the **Edit Profile** button to go to the Megaport Marketplace profile page.
You can hide this message by clicking the **Hide This Message** button and selecting a duration from the drop-down list.
If you cannot see the message, it means it has already been hidden or your profile is already available to the Megaport Marketplace.
**To filter the Megaport Marketplace providers**
The Megaport Marketplace displays a list of all providers in the format of functional groups, or a list. You can filter based on functional grouping, as shown on the tabs, or on any of the search criteria shown below the tabs.
**To filter Megaport Marketplace providers using the Exchange tabs**
The Exchange tabs on the search banner represent functional groups chosen on their profiles by the Megaport Marketplace providers.
* **Ecosystem** -- This tab shows all the Megaport Marketplace providers.
* **Financial Services Exchange** -- This exchange tab shows all the Megaport Marketplace providers that provide Financial Services.
* **AI Exchange** -- This exchange tab shows all the Megaport Marketplace providers that provide AI services.
* **Voice+Video Exchange** -- This exchange tab shows all the Megaport Marketplace providers that provide voice and video services.
You can use the Company Name, Provider Type, Rate Limit, and Country fields to further filter the entries on the exchanges.
* **Company Name** -- Filter by name or character string to find matching companies.
* **Rate Limit** -- Filter by the maximum possible speed of the Port.
The speed does not reflect the actual speed for the connection, but only the maximum possible.
* **Provider Type** -- Filter by the type of service. Each service type includes various sub-categories to allow more granular filtering.
* **Country** -- Filter the providers based on the country locations of their Ports.
From the results, click a provider to go to their profile page.
The profile page displays information about the provider and a list of their port locations available for connections. You can create a VXC to any of these locations.
**To create a VXC to a Megaport Marketplace provider**
1. From the provider profile page, find the interconnect location you want then click **+Connect**.
2. In the New VXC Connection page, select one of your Ports as the source of the connection.
3. Click **Next**.
4. Complete the connection details.\
The details will vary based on the service provider. For more information about the connection details, see [Requesting a Connection to a Service Provider](/marketplace/connections).
5. Click **Next**.
6. If the service provider has configured a form to collect additional information, complete the **Service Request Form** step. Forms streamline onboarding by gathering all necessary details upfront.\
For more information, see [Completing a form (customers)](/marketplace/forms#marketplace-form).
7. Click **Next**.
8. Click **Add VXC**.
9. Click **Review Order**.
10. Review the Order Services agreement and click **Order Now**.
After you deploy the VXC, the provider will receive a notification of your connection request. The provider will be prompted to log in to their Megaport Portal account and authorize this request. After the provider approves the connection, the VXC will be configured and usable within 59 seconds.
## Helpful references
* [Creating a Megaport Marketplace Profile](/marketplace/profile)
* [Megaport Marketplace FAQs](/marketplace/marketplace-faqs)
* [Megaport Marketplace Forms](/marketplace/forms)
* [Megaport Marketplace Notifications](/marketplace/notifications)
* [Requesting a Connection to a Service Provider](/marketplace/connections)
# Creating a Megaport Marketplace Profile
Source: https://docs.megaport.com/marketplace/profile
This help topic describes how to set up a Megaport Marketplace profile so customers can connect to your services.
If you are a service provider, create a Megaport Marketplace profile so customers can find and connect to your services.
Partner-managed accounts do not have permission to view or edit Megaport Marketplace profile information.
Before you can create a Megaport Marketplace profile, you must create a customer profile and have login credentials to the Megaport Portal. You must be a Company Admin to create or manage a Megaport Marketplace profile.\
For more information, see [Setting Up a Megaport Account](/setting-up).
**To create a Megaport Marketplace profile**
To create a Megaport Marketplace profile, click **Marketplace** or choose User Menu > Admin Settings > Megaport Marketplace. If you don't have a Megaport Marketplace profile, you will see a message that invites you to create one.
1. Click **+ Set Up Profile** to create your profile.\
This will take you to the **Set Up Profile** window.
2. Add these details:
* **Company Bio** -- Add a short description of your company's services.\
This is a free text field where you can enter company biographical or profile information. There is a 200 word limit.
* **Email** -- Add a contact email address for your company.
* **Website** -- Add your company's website address.
* **Phone** -- Add a contact number.
3. Click **Create Profile**.
The name of your Megaport Marketplace profile will be taken from your company profile. For more information about where this name comes from, see [Updating a Company Profile](/setting-up/company-profile).
You now have a basic Megaport Marketplace profile. You can add more details and update your profile visibility on the Megaport Marketplace by editing your profile.
**To complete your Megaport Marketplace profile**
After you have set up the initial profile details, you can add more information to complete your profile. The profile details are entered on these tabs:
* **About** -- Provide company details and manage your company's visibility on the Marketplace.
* **Contact** -- Add your company's contact details, social media links, and headquarters address.
* **Services** -- Manage the visibility of all your company’s services on the Megaport Marketplace.
* **Service Request Form** -- Create forms to collect additional information from customers during connection requests. For more information, see [Megaport Marketplace Forms](/marketplace/forms).
1. From the Megaport Portal, click **Marketplace** or choose User Menu > Admin Settings > Megaport Marketplace.
2. **Profile Visibility** -- Set your profile visibility. The options are Public or Private. When public, your profile is visible on the Megaport Marketplace. You can set your profile to Public even if you do not have public services.\
When private, your profile is hidden on the Megaport Marketplace. Select Private when editing or pending completion of the profile.\
To change the profile visibility, click **Edit**, choose the required setting from the drop-down list, then click **Save**.
3. Click **Edit** to provide these details on the **About** tab:
* **Company Logo** -- Upload an image to display on the tile on the Megaport Marketplace. The recommended image size is 200px by 200px and in PNG (best) or JPG format.
* **Provider Types** -- Select the appropriate category of services you offer. You can change the categories at any time. The categories you choose will affect the services available to you on the **Services** tab.
* Some provider types have sub-categories. You can see and select the sub-categories when you edit a service on the **Services** tab.
* Provider type sub-categories can be used to search for the exact service you require in the Megaport Marketplace search criteria.
* **Exchanges** -- You can add your entry to an exchange, which is a functional grouping that helps customers easily find your services.
4. Click **Save**.
5. Click **Edit** to provide these details on the **Contacts** tab:
* **Social** -- Add the social media links you want attached to your profile.
* **Headquarters** -- Add the address of your company’s primary location.
6. Click **Save**.
7. The **Services** tab shows the services provisioned to your company. Use this tab to manage the Megaport Marketplace visibility of each service:
* **Filter** -- Use this field to manage what you see on this list. You can see all your services, only public services, or only private services.
* **Sort** -- Choose a sort order for your services from the drop-down list.
* **Expand All Services** -- Show the details for all the services. You will see the Megaport Marketplace display name, description, and the date created.
To return to the collapsed state, click the same button again.
You can use the up/down arrow button on each service to individually display the details.
* Each service displays the service identifier. Click the button to copy the service identifier.
* For each service, you can update the Megaport Marketplace visibility by editing the service. For information about changing the visibility for a service, see [Adding services to your profile](#adding-services-to-your-profile).
8. The **Service Request Form** tab shows any forms you have created. Use this tab to create and manage the Megaport Marketplace forms used to collect required information from users when they order your services.\
For more information, see [Megaport Marketplace Forms](/marketplace/forms).
## Changing your profile
You can make changes to your profile at any time.
**To change your Megaport Marketplace profile**
1. From the Megaport Portal, click **Marketplace** or choose User Menu > Admin Settings > Megaport Marketplace.
2. Make your changes using the tabs and click **Save** on each tab.
**Access your profile from the Megaport Marketplace page**
If your Megaport Marketplace profile is private, you will see a message on the top of the Megaport Marketplace page. The message tells you that you can change your profile to make it visible to other customers.\
Click the **Edit Profile** button to go to the Megaport Marketplace profile page.
You can hide this message by clicking the **Hide This Message** button and selecting a duration from the drop-down list.
If you cannot see this message, it means it has already been hidden or your profile is already available to the Megaport Marketplace.
## Adding services to your profile
With a Megaport Marketplace profile, all services associated with your account are visible on the Service tab of your profile. To make them available for inbound connection requests as Megaport Marketplace services, you must set the Megaport Marketplace visibility individually for each service. You can change it at any time by editing the service configuration.
**To add a service to your profile**
You can add a service to your profile on the Services tab of your Megaport Marketplace profile.
1. Go to your Megaport Marketplace profile by choosing User Menu > Admin Settings > Megaport Marketplace.
2. Click the **Services** tab of your profile.
3. Click **Edit** on the service you want to update.
4. Select a profile visibility from the drop-down list. The choices are **Visible on Marketplace** and **Hidden from Marketplace**.
5. You can also add a Megaport Marketplace display name, description, and contact email address. When you make a service public, it defaults to **CompanyName** at **Location** on the Megaport Marketplace. If required, you can give it a different display name and description here.
Changing the Megaport Marketplace display name will not affect the name given to the service in the Services section of the Megaport Portal.
6. If provider type sub-categories are available for the provider types you selected on the **About** tab, they will be displayed at the bottom of the **Edit Service** window. You can select as many as you need. Sub-categories are searchable and add an extra layer of detail about your service on the Megaport Marketplace.
7. Click **Save**.
## Helpful references
* [Megaport Marketplace FAQs](/marketplace/marketplace-faqs)
* [Megaport Marketplace Forms](/marketplace/forms)
* [Megaport Marketplace Notifications](/marketplace/notifications)
* [Megaport Marketplace Overview](/marketplace/overview)
* [Requesting a Connection to a Service Provider](/marketplace/connections)
# Terminating a Megaport Internet Connection
Source: https://docs.megaport.com/megaport-internet/terminating-connection
This help topic describes how to terminate a Megaport Internet Connection directly from the Megaport Portal.
You can terminate a Megaport Internet connection directly from the Megaport Portal.
Megaport Internet connections can be individually terminated or are automatically terminated as part of terminating the attached Port, MCR, MVE, or NAT Gateway.
Terminating a Megaport Internet connection on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. For more information about Megaport Internet contract terms, see [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing/).
You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate a Megaport Internet connection**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the Megaport Internet connection you want to terminate.
The Terminate Services window appears. Early termination fees will be shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason that you are terminating the connection. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the connection termination, or click **No, Keep Services** to cancel.\
The Megaport Internet connection is deleted from the Megaport network.
# Configuring Advanced BGP Settings
Source: https://docs.megaport.com/nat/bgp-advanced
This help topic describes how to configure advanced Border Gateway Protocol (BGP) settings in the Megaport NAT Gateway (NAT).
This topic describes how to manage advanced Border Gateway Protocol (BGP) settings in the Megaport NAT Gateway (NAT Gateway).
## Overriding the NAT Gateway ASN
The default assigned to the NAT Gateway is 133937. For most configurations, the default ASN is appropriate. Optionally, you can specify another local ASN to override the default ASN on a per-peer basis.
Cloud service providers (CSPs) can have restrictions on the ASN value. See the documentation for your CSP before overriding the default value.
**To override the NAT Gateway ASN**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC and select the NAT Gateway A-End or B-End.
3. Next to the BGP connection, click **Edit**.
4. Select the **Advanced** tab.
5. In the **Local ASN** field, specify a public or private ASN (for example, specify a number from 64512 to 65534).
The ASN range is from 2 to 4294967294, but the following ASNs are reserved:
* 8074, 8075, 12076, 65515 - 65520 (reserved in Azure)
* 23456, 64496-64511, 65535 - 65551 (reserved by Internet Assigned Numbers Authority (IANA))
6. Click **Update**.
7. Click **Save**.
## Setting route advertisement priority with ASN prepend
The path length determines the route advertisement priority for outgoing BGP paths. The route with the shortest AS path has the highest preference, and it is preferred over any longer path advertisements. Longer path lengths have a lower priority. AS path prepending lengthens the path to lower the path priority.
Setting an ASN prepend value is optional.
**To set the path advertisement priority on an existing BGP connection**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC and select the NAT Gateway A-End or B-End.
3. Next to the BGP connection, click **Edit**.
4. Select the **Advanced** tab.
5. In the **AS Path Prepend** field, specify the number of additional times to add the local ASN to the BGP path. You can specify an integer from 1 to 10. For example, an AS path prepend value of *2* prepends the ASN to the existing AS path twice, creating an AS path length of 3. Higher numbers deprioritize the path.
6. Click **Update**.
7. Click **Save**.
**To set the path advertisement priority on a new BGP connection**
1. Add a new BGP connection.
2. Select the **Advanced** tab.
3. In the **AS Path Prepend** field, specify the number of additional times to add the local ASN to the BGP path. You can specify an integer from 1 to 10. For example, an AS path prepend value of *2* prepends the ASN to the existing AS path twice, creating an AS path length of 3. Higher numbers deprioritize the path.
4. Click **Add**.
5. Click **Save**.
## Enabling the BFD protocol
BGP shares network reachability information with adjacent BGP systems, which are referred to as *neighbors* or *peers*. The protocol runs independent of BGP and detects path failure between directly connected BGP neighbors, allowing for a faster BGP routing re-convergence time.
BGP sends keepalive messages at regular intervals to maintain the BGP session. If a BGP neighbor doesn't receive a keepalive message within the specified BGP timer interval, the BGP session is torn down and failover occurs to another BGP neighbor.
BFD provides a faster method for detecting path failure between directly connected BGP neighbors. BFD sends control messages at regular, shorter intervals to maintain the BFD session. If a BFD neighbor doesn't receive a control message within the specified BFD timer interval, the BFD session is torn down and notifications are sent to the BGP process, which then tears down the BGP session and fails over to another BGP neighbor.
When you enable BFD, the system automatically applies these fixed settings:
* : 300 milliseconds
* : 300 milliseconds
* : 3
These settings apply to all BGP connections on the VXC where BFD is enabled.
**To enable BFD**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC and select the A-End or B-End.
3. Next to the BGP connection, click **Edit**.
4. Select the **Advanced** tab.
5. Next to the **Use BFD** field, click **On**.
6. Click **Update**.
7. Click **Save**.
You must enable BFD on the BGP neighbor as well.
**Default BFD values by Cloud Service Provider (CSP)**
* **AWS Direct Connect** -- BFD is supported natively by AWS Direct Connect connections. AWS automatically enables asynchronous BFD for virtual interfaces. However, you must enable BFD on NAT Gateway VXCs to AWS Direct Connect for your connection.
By default, the AWS BFD liveness detection minimum interval is 300 milliseconds and the multiplier is 3 packets.
Confirm support for other neighbors with your CSP, as well as specific default values.
* **Azure ExpressRoute** -- BFD is supported natively by Azure ExpressRoute on private peering. Azure configures BFD by default for all newly created ExpressRoute private peering interfaces on the Microsoft Enterprise Edge (MSEE). You must configure the NAT Gateway VXCs to Azure ExpressRoute private peering for BFD to enable it for your connection. Between BFD peers, the slowest peer determines the transmission rate.
* **Microsoft Enterprise Edge (MSEE) ExpressRoute routers** -- MSEE ExpressRoute routers have BFD transmit and receive intervals of 300 milliseconds.
* **Google Cloud Services** -- You can enable and configure BFD on Google Cloud Partner Interconnects. For more information, see the Google Cloud documentation to [Configure BFD for Cloud Router](https://docs.cloud.google.com/network-connectivity/docs/router/how-to/configuring-bfd#configure-peer-router).
## Enabling AS Override
Each participant in a BGP session is identified by an AS number (autonomous system number). BGP has a built-in mechanism for preventing routing loops; if a router receives a route that already contains its own AS number in the path, the router rejects it.
When you enable AS Override, the replaces the peer's AS number with its own in the route advertisement, bypassing the loop-detection check of the downstream device.
For example, a company has two sites (New York and London) that use the same AS number (AS 65001) and are connected through (AS 100):
1. The New York site (AS 65001) advertises a route to the (AS 100).
2. The (AS 100) passes that route to the London site.
3. The London router (AS 65001) sees AS 65001 in the AS\_PATH and rejects the prefix.
In the same scenario with AS Override enabled:
1. The New York site (AS 65001) advertises a route to the (AS 100).
2. The (AS 100) passes that route to the London site. The replaces AS 65001 with AS 100 in the AS\_PATH.
3. The London router (AS 65001) sees AS 100 in the AS\_PATH and accepts the prefix because it doesn't match its own AS number.
You can only enable AS override on eBGP (external BGP) connections, where the Peer ASN and Local ASN are different. You cannot apply AS override to iBGP (internal BGP) connections, where the Peer ASN and Local ASN are the same.
**To enable AS override**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC, then select the A-End or B-End.
3. Next to the BGP connection, click **Edit**.
4. Select the **Advanced** tab.
5. Next to **AS Override**, click **On** to enable it.
6. Click **Update**.
7. Click **Save**.
**To disable AS override**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC, then select the A-End or B-End.
3. Next to the BGP connection, click **Edit**.
4. Select the **Advanced** tab.
5. Next to **AS Override**, click **Off** to disable it.
6. Click **Update**.
7. Click **Save**.
## Configuring a preferred route with MED
Autonomous systems consider other BGP attributes before the MED attribute. The MED attribute breaks the tie between two routes when the weight, local preference, AS path, and origin type are the same. The exit point with the lowest MED metric is preferred.
For example, if you have a configuration that consists of two BGP neighbor devices, which are both members of the same autonomous systems (AS), AS 4 and AS 5:
* R2, with a MED metric of 10
* R3, with a MED metric of 20
AS 4 will prefer the path through R2 to reach AS 5.
Adding or changing an MED metric doesn't disrupt the service.
**To configure the MED**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC and select the A-End or B-End.
3. Next to the BGP connection, click **Edit**.
4. Select the **Advanced** tab.
5. In the **Inbound** field, specify a 32-bit integer MED metric to apply to all routes received on this BGP connection. Leave blank to use the value received from the BGP neighbor.
6. In the **Outbound** field, specify a 32-bit integer MED metric to apply to all routes transmitted by this BGP connection.
7. Click **Update**.
8. Click **Save**.
**Using MED with Google Cloud Platform**
Google Cloud Platform Cloud Router egress is determined by the first condition that is met:
* All egress traffic is sent to the route with the shortest AS path length.
* If routes have the same AS path lengths, all egress traffic is sent to the route with the lowest MED value (the lowest route metric).
* If routes have the same AS path lengths and MED values (the same route metrics), egress traffic is balanced across all routes using equal-cost multipath (ECMP).
Confirm support for other neighbors with your CSP, along with any specific routing metric influences that might have a higher priority than the MED.
## Helpful references
* [Configuring BGP for Megaport NAT Gateway](/nat/configure-bgp)
* [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc)
* [Megaport NAT Gateway Route Filtering](/nat/route-filtering)
* [NAT Gateway Features](/nat/nat-gateway-features)
# Megaport NAT Gateway BGP Peer Filtering
Source: https://docs.megaport.com/nat/bgp-peer-filtering
This help topic describes BGP peer filtering for Megaport NAT Gateway.
This topic describes Megaport NAT Gateway (NAT Gateway) BGP peer filtering, which provides simple connection-level control over route exchange between BGP neighbors.
For an overview of route filtering concepts, see [Megaport NAT Gateway Route Filtering](/nat/route-filtering).
## Before you begin
Before configuring a route filter, plan the implementation by determining your requirements. Then create a route filter based on these requirements.
### Deployment considerations
* You need to create a NAT Gateway, as described in [Creating a NAT Gateway](/nat/creating-nat-gateway).
* You can configure route filters before or after configuring BGP, as route filters work on existing or new BGP connections.
* You might want to shut down BGP route exchange if you plan to add several BGP sessions across your Virtual Cross Connects (VXCs) before they exchange route information and route filters are applied. When you are finished configuring, you can then go into the relevant BGP sessions and enable them. For more information, see [Configuring a NAT Gateway VXC](/nat/configuring-nat-vxc).
NAT Gateway route filtering supports and relies on the BGP Route Refresh mechanism to update routes using a soft reset when filters change the routing. If Route Refresh is not enabled on all active BGP connections, you need to shut down and re-enable the connection in the Megaport Portal to update routes. If you have enabled the BGP Shut Down option, routes will be updated when you disable BGP Shut Down, that is, re-enable BGP.
## Filtering by BGP peer
By default, NAT Gateway permits all routes unless otherwise filtered by the peer type policy. For more information, see [Default peering route advertisements](/nat/route-filtering#defaultroutes).
You can configure a policy for each pair of BGP connections configured on the NAT Gateway to fine-tune routing. The BGP pairings are unidirectional, meaning that each pair of BGP connections has two policies - one for A to B, and another for B to A.
A BGP peer filter policy has three possible actions:
* **Default** -- Follows the default policy defined by the source peering type BGP connection.
* **Permit** -- Allows routes received from neighbor A to be advertised to neighbor B.
* **Deny** -- Prevents routes received from neighbor A from being advertised to neighbor B.
### BGP peer filter example
BGP connections A, B, and C are connected to the same NAT Gateway.
Connection A has a global permit policy. To filter routes toward connection B, the A to B policy can be set to Deny without affecting any routes advertised to C.
Connection C has a global deny policy. To allow routes to be advertised only to A, the C to A policy can be set to Permit. If a new BGP peer is added later, routes from C will follow the global policy and not be advertised.
### Creating a BGP peer filter
A BGP peer filter limits the number of routes that are advertised or received from BGP neighbors.
**To create a BGP peer filter**
1. Select the VXC attached to the NAT Gateway, then select A-End.
2. Next to the BGP connection, click **Edit**.
3. Select the **Filters** tab.
4. Under BGP Peer Filter, select whether the NAT Gateway should advertise routes received by this BGP connection to BGP peers by default or by exception.
5. Select an action for the BGP peer from the Actions drop-down list:
* **Default** -- Follows the default policy defined by the source peering type BGP connection.
* **Permit** -- Allows routes received from neighbor A to be advertised to neighbor B.
* **Deny** -- Prevents routes received from neighbor A from being advertised to neighbor B.
6. Click **Update**.
7. Click **Save**.
## Helpful references
* [Configuring BGP for Megaport NAT Gateway](/nat/configure-bgp)
* [Megaport NAT Gateway BGP Prefix Filtering](/nat/bgp-prefix-filtering)
* [Megaport NAT Gateway Route Advertisement](/nat/route-advertisement)
* [Megaport NAT Gateway Route Filtering](/nat/route-filtering)
* [Megaport NAT Gateway Route Summarization](/nat/route-summarization)
# Megaport NAT Gateway BGP Prefix Filtering
Source: https://docs.megaport.com/nat/bgp-prefix-filtering
This help topic describes BGP prefix filtering for Megaport NAT Gateway, including creating, applying, and maintaining prefix filters.
This topic describes Megaport NAT Gateway (NAT Gateway) BGP prefix filtering, which provides advanced control over route advertisements using CIDR-based prefix lists.
For an overview of route filtering concepts, see [Megaport NAT Gateway Route Filtering](/nat/route-filtering).
## Before you begin
Before configuring a route filter, plan the implementation by determining your requirements. Then create a route filter based on these requirements.
### Deployment considerations
* You need to create a NAT Gateway, as described in [Creating a NAT Gateway](/nat/creating-nat-gateway).
* You can configure route filters before or after configuring BGP, as route filters work on existing or new BGP connections.
* You might want to shut down BGP route exchange if you plan to add several BGP sessions across your Virtual Cross Connects (VXCs) before they exchange route information and route filters are applied. When you are finished configuring, you can then go into the relevant BGP sessions and enable them. For more information, see [Configuring a NAT Gateway VXC](/nat/configuring-nat-vxc).
NAT Gateway route filtering supports and relies on the BGP Route Refresh mechanism to update routes using a soft reset when filters change the routing. If Route Refresh is not enabled on all active BGP connections, you need to shut down and re-enable the connection in the Megaport Portal to update routes. If you have enabled the BGP Shut Down option, routes will be updated when you disable BGP Shut Down, that is, re-enable BGP.
## Filtering by BGP prefix
A prefix is the destination network of the route. An IP network is a group of IP addresses. The network address is the prefix.
* IPv4 address: 192.0.2.1
* IPv4 network prefix: 192.0.2.0/24 (includes 192.0.2.0 - 192.0.2.255)
A *prefix filter* is a named list of IP networks. Each entry consists of an IPv4 or IPv6 CIDR prefix or range of prefixes that you define and manage. A CIDR range means that you can filter several networks using a single routing entry.
A prefix filter can be applied to a BGP connection to selectively identify routes to advertise or receive from neighboring routers. You can also make a list of routes *not* to advertise or receive, allowing everything else. When you define a prefix filter, the NAT Gateway accepts only routes matching the prefix information. This filter type is useful in environments with a large list of prefixes and peers to manage. You can apply the same prefix filter to more than one BGP peer, reducing manual work and eliminating potential errors.
A prefix filter contains:
* A list of IPv4 or IPv6 prefixes (for example, 10.0.0.0/16) and a name associated with the list.
* A match condition. You can specify exact matches with specific routes or less precise matches based on prefix length.
* An action that is carried out if the prefix and the match condition are both true (for example, Permit).
In a prefix filter, rules are evaluated from the top down. Evaluation stops with the first match. An implicit deny is applied to routes that don't match any prefix list entry.
### Prefix filter list actions
* **Inbound prefix filtering using a permit action** -- NAT Gateway applies the prefix filter to inbound BGP route advertisements from the neighbor. Routes not matching the prefixes on this list are denied at the earliest possible point and are never used by the NAT Gateway.
* **Inbound prefix filtering using a deny action** -- NAT Gateway applies the prefix filter to inbound BGP route advertisements from the neighbor. Routes matching the prefixes on this list are blocked. All other prefixes are allowed to enter the NAT Gateway routing table.
* **Outbound prefix filtering using a permit action** -- NAT Gateway applies the prefix filter to outbound routes. Routes matching the prefix list are advertised to the BGP neighbor and all other routes are filtered.
* **Outbound prefix filtering using a deny action** -- NAT Gateway applies the prefix filter to outbound routes. Routes matching the prefix list are blocked from the BGP neighbor and all other routes are advertised.
### Creating a BGP prefix filter
Each NAT Gateway can manage up to 50 prefix filters. Each prefix filter can contain up to 200 prefix entries.
Each prefix filter is independent and you can apply only one list per BGP neighbor at a time.
**To create a prefix filter**
1. On the Megaport Portal Services page, select a NAT Gateway.\
The NAT Gateway must have a Live status before you can create a prefix filter.\
The NAT Gateway Configuration page appears.
2. Under NAT Gateway Configuration, select the **Prefix Filter Lists** tab.
3. Click **New List**.
4. Enter a unique descriptive name to identify the filter. The description length can range between 1 and 100 characters.\
This prefix name will appear in the drop-down list of prefix lists in the Filters tab of the BGP Configuration screen.
Prefix filters cannot be shared among NAT Gateways. You must re-create prefix filters for each NAT Gateway.
5. Select either IPv4 or IPv6 format.\
The prefixes must use the same address format. A warning appears if you try to mix the two formats within the same list.
6. Select a position for the rule.\
The rule position is critical because evaluation stops with the first match and the rest of the list is ignored. If no conditions match, NAT Gateway applies an implicit deny.
7. Select the action to take for the filter: Match or Don't Match.
8. Enter the prefix subnets in CIDR notation. For IPv4, use a.b.c.d/x, where *a.b.c.d* is the exact prefix and *x* is the exact prefix length.
This field also accepts a dotted-quad notation for the subnet mask (for example, 255.255.255.0 instead of /24).
9. Prefixes can be exact-match-only or you can specify the number of bits in the mask to use as matching criteria. Select the subnet mask criteria:
* **Exact** -- Limits the filter to only this specific prefix. Any smaller prefixes contained within the prefix are not matched.
* **Min and Max** -- Specify a range of subnet mask lengths to match for more flexibility. Specify how many bits of the subnet mask the filter needs to match, starting with the most significant bit in the leftmost position of the address. When you specify a subnet mask range, the filter now has two conditions to match: the route must be within the a.b.c.d/x boundary and it must have a mask length between the minimum and maximum range. Shorter prefixes match more addresses, while longer prefixes match fewer.
* **Min** -- The minimum prefix length to be matched. Routes with a prefix length greater than or equal to this value will be matched. Valid values are from 0 to 32 (IPv4), or 0 to 128 (IPv6). The Min must be less than or equal to the Max value.
* **Max** -- The maximum prefix length to be matched. Routes with a prefix length less than or equal to this value will be matched. Valid values are from 0 to 32 (IPv4), or 0 to 128 (IPv6). The Max must be greater than or equal to the Min value.
For example, 10.0.0.0/8 with a Min of 16 matches 10.0.0.0/16, 10.0.1.0/24, 10.0.0.1/30 but does not match 10.2.0.0/15.
The Min and Max values on a NAT Gateway are similar to Cisco's **ge** and **le** values used with the **ip prefix-list** CLI command.
When using the Min and Max values, you must satisfy this condition:
Prefix length \< Max ≤ Min
10. Click **Save**.
11. Click **Next**.
Use a CIDR calculator to ensure that all data is valid and within range.
The next step is to apply the filter to the BGP connection, as described in [Applying a prefix filter to a BGP connection](#applyprefixfilter).
#### Example filter entries
* Exact match on 1.2.3.0/24 -- Exactly matches the prefix 1.2.3.0 with a subnet mask of 255.255.255.0
* Match 192.2.3.0/24 min 32 -- Checks the first 24 bits of the prefix 192.2.3.0 that have a subnet mask of 32
* Match 10.0.12.0/24 max 32 -- Matches all 10.0.12.*x* networks that have a subnet mask less than or equal to 32
### Creating a prefix filter based on an existing prefix filter
If you want to create a filter that is similar to an existing filter, you can make a copy of the existing filter.
**To create a prefix filter based on an existing filter**
1. Select a NAT Gateway.\
The NAT Gateway Details page appears.
2. Under NAT Gateway Configuration, select the **Prefix Filter Lists** tab.
3. In the **Prefix Filter List**, select the filter list you want to copy.
4. Click **Duplicate List**.
5. Enter a unique descriptive name to identify the new filter.\
This prefix name will appear in the drop-down list of prefix lists in the Filters tab of the BGP Configuration screen.
6. Make any changes to the parameters unique to this filter.
7. Click **Save**.
8. Click **Next**.
### Applying a prefix filter to a BGP connection
Prefix filters are configured directly on NAT Gateway and then attached to a BGP connection.
**To apply a prefix filter**
1. Select the VXC attached to the NAT Gateway, then select A-End.
2. Next to the BGP connection, click **Edit**.
3. Select the **Filters** tab.
4. Under BGP Prefix Filter, you can apply an import filter and an export filter:
* **Import** -- The NAT Gateway applies the prefix filter to inbound advertisements from the neighbor.
* **Export** -- The NAT Gateway applies the prefix filter to outbound advertisements to the neighbor.
Select whether the filter will limit the set of routes that the NAT Gateway will receive from, or advertise to the peer. These options are available:
* **No Prefix Filter** -- Allows all routes. No routes will be filtered.
* **Permit List** -- Allows only routes that match the prefix list. Other routes will be filtered.
* **Deny List** -- Allows all routes except those that match the selected prefix list.
5. Select the prefix filter you want to apply from the drop-down list.
6. Click **Update**.
7. Click **Save**.
After applying the filter, re-enable route exchange if it is disabled. For more information, see [Configuring a NAT Gateway VXC](/nat/configuring-nat-vxc).
A prefix filter can be attached to more than one BGP connection.
## Maintaining prefix filters
In a prefix filter list, rules can be added, deleted, and reordered.
### Adding a rule to an existing prefix filter
Each prefix filter can contain up to 200 rules. Duplicate rules are not allowed.
**To add a rule to an existing filter**
1. Select a NAT Gateway on the Services page.\
The NAT Gateway Details page appears.
2. Under NAT Gateway Configuration, select the **Prefix Filter Lists** tab.
3. Select a prefix list from the **Prefix Filter List** drop-down list.
4. Add the rule.
5. Click **Save**.\
You must click **Save** to apply rule changes. Switching to another list without saving prompts a warning that the changes will be lost.
### Deleting a rule from a prefix filter
**To delete a rule from a filter**
1. Select a NAT Gateway on the Services page.\
The NAT Gateway Details page appears.
2. Under NAT Gateway Configuration, select the **Prefix Filter Lists** tab.
3. Select a prefix list from the Prefix Filter List drop-down list.
4. At the end of the rule row, click the trash icon.
5. Click **Delete**.
6. Click **Save**.
### Reordering rules in a prefix filter
In a prefix filter list, the rule position is critical because rules are evaluated one at a time, starting at the top of the list down. Evaluation stops with the first match.
**To reorder a rule position**
* Drag the icon in the Position column to a different location and release.
### Deleting a prefix filter list
To delete a prefix filter list, you must first remove any other resources that reference it, such as VXCs. If you try to delete a prefix filter list before removing its resources, a dialog lists the resources in use.
All prefix lists are automatically removed from a NAT Gateway when it is terminated.
**To delete a prefix filter**
1. Select a NAT Gateway on the Services page.\
The NAT Gateway Details page appears.
2. Under NAT Gateway Configuration, select the **Prefix Filter Lists** tab.
3. Select a prefix list from the Prefix Filter List drop-down list.
4. Click **Delete List**.
5. Click **OK**.
## Helpful references
* [Configuring BGP for Megaport NAT Gateway](/nat/configure-bgp)
* [Megaport NAT Gateway BGP Peer Filtering](/nat/bgp-peer-filtering)
* [Megaport NAT Gateway Route Advertisement](/nat/route-advertisement)
* [Megaport NAT Gateway Route Filtering](/nat/route-filtering)
* [Megaport NAT Gateway Route Summarization](/nat/route-summarization)
# Configuring BGP for Megaport NAT Gateway
Source: https://docs.megaport.com/nat/configure-bgp
This help topic describes how to configure advanced Border Gateway Protocol (BGP) settings in the Megaport NAT Gateway (NAT).
## Configuring BGP
You can enable BGP on VXC connections from your NAT Gateway. Your NAT Gateway supports up to 50 BGP peers in total, and each VXC supports up to five interfaces.
**To configure BGP**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC, then select the NAT Gateway A-End or B-End.
3. Click **Add BGP Connection**.
4. Specify these values:
* **Local IP** -- Select the IP address on this interface that communicates with the BGP peer. The drop-down menu is auto-populated based on the interface IP addresses you provided on the Connection Details page.
* **Peer IP** -- Specify 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** -- Specify the ASN of the target routing device that will terminate the BGP connection. The ASN range is from 2 to 4294967294. 4-byte ASNs are supported in the [asplain format](https://www.rfc-editor.org/rfc/rfc5396.html#section-2).
* **BGP Password** (optional) -- The shared key to authenticate the BGP peer. 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. The shared key length is from 1 to 25 characters. The key can include any of these characters:
* a-z
* A-Z
* 0-9
* Special characters: ! @ # . \$ % ^ & \* + = - \_
Click the eye icon to see the password as you type. The view persists until you click the eye icon again to hide the password.
* **Description** (optional) -- Enter a description that will help identify this connection. The description length can range between 1 and 100 characters.
* **BGP State** -- Shuts down the connection without removing it. The initial setting will be taken from the setting on the A-End of the NAT Gateway. Enabling or shutting down the BGP state does not affect existing BGP sessions. The BGP state only affects new VXCs. This setting overrides the NAT Gateway state for an individual connection. For more information, see [Shutting down a BGP connection](#bgp-shut) and [Creating a NAT Gateway](/nat/creating-nat-gateway).
- If you have entered multiple CIDR ranges, the IP addresses are available for selection.
- Use a CIDR calculator to ensure that all data is valid and within range.
5. Click **Add**.
6. Click **Next**.
## Editing a BGP connection
You can edit existing BGP connections, including the IP addresses, peer ASN, BGP password, description, BGP state, and advanced settings, such as route filters.
**To edit a BGP connection**
1. Select the VXC, then select the NAT Gateway A-End or B-End.
2. Under **BGP Connections**, click **Edit** next to the BGP connection you want to edit.
3. Make your changes.
4. Click **Update**.
5. Click **Save**.
For information about the BGP Advanced tab settings, see [Configuring Advanced BGP Settings](/nat/bgp-advanced).
For information about the BGP Filters tab settings, see [Megaport NAT Gateway Route Filtering](/nat/route-filtering).
## Verifying the BGP configuration
After you configure BGP, verify that the BGP session is up and that BGP is advertising and receiving routes as expected.
**To view the BGP status**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC.
3. Choose **Details**.\
The Configuration Details page shows the provisioning, service, and BGP status.
## Troubleshooting BGP
If the Services > Connection Details page displays a status issue, verify these items:
1. Select the VXC, then select the NAT Gateway A-End or B-End.
2. Under BGP Connections, verify that the correct local ASN is in use for the A-End of the VXC.
3. Verify that the correct Peer IP address is in use.
4. Verify that the correct BGP MD5 password is in use for the A-End 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
Use this setting to 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, troubleshooting, and so on.
**To temporarily disable a BGP connection**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC, then select the NAT Gateway A-End or B-End.
3. Under BGP Connections, click **Shut Down** next to the BGP connection you want to disable.
4. Click **Yes** to confirm.
## Setting up NAT Gateway BGP notifications
You can receive email notifications whenever a session status changes on your NAT Gateway. These changes can include a BGP going up, down, or flapping. If a session is flapping, only one email per hour will be sent.
You can opt in or out of receiving these email notifications.
**NAT Gateway BGP notifications email specifications**
The NAT Gateway BGP notification system is designed to provide timely notifications for BGP up, down, or flapping events while minimizing alert noise.
The notification system implements rate limiting for rapidly changing status, as described below.
* The initial notification is sent immediately.
* Subsequent events within one hour are suppressed.
* The email body will indicate if the event has repeated during the suppression period.
**To receive BGP email notifications**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > User Settings > Notifications.
3. Click the Service Status notification group to view the BGP email notification types.
4. Select the notification group check box to subscribe to all notifications in that group, or subscribe to individual notification types. Any notification subscription changes are automatically saved.
## Helpful references
* [Configuring Advanced BGP Settings](/nat/bgp-advanced)
* [Creating a NAT Gateway](/nat/creating-nat-gateway)
* [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc)
* [Megaport NAT Gateway Route Advertisement](/nat/route-advertisement)
* [Megaport NAT Gateway Route Filtering](/nat/route-filtering)
* [Megaport NAT Gateway Route Summarization](/nat/route-summarization)
# Configuring a NAT Gateway
Source: https://docs.megaport.com/nat/configuring-nat
This help topic describes how to configure a NAT Gateway, including editing service settings and BGP default state.
This topic describes how to edit and configure a Megaport NAT Gateway (NAT Gateway). Before you begin, you need to create a NAT Gateway, as described in [Creating a NAT Gateway](/nat/creating-nat-gateway).
For each NAT Gateway, you can edit any field on the NAT Gateway Configuration page, except the rate limit, session count, and ASN, which are fixed for the duration of the service.
You can add your NAT Gateway to your Megaport Marketplace profile. For more information about how to make your service visible to the Megaport Marketplace, see [Adding services to your profile](/marketplace/profile#adding-services-to-your-profile).
**To edit a NAT Gateway**
1. Log in to the Megaport Portal and choose **Services**.
2. Click the gear icon next to the NAT Gateway you want to edit.
3. Edit any field on the NAT Gateway Configuration page as required, except for the NAT Gateway Rate Limit, Session Count, NAT Gateway ASN, or Megaport Marketplace visibility.
* **Prefix filter lists** -- Click the **Prefix Filter Lists** tab to manage the prefix filter lists on this NAT Gateway.\
For more information, see [BGP prefix filtering](/nat/bgp-prefix-filtering/).
* **Packet filter lists** -- Click the **Packet Filter Lists** tab to manage the packet filter lists on this NAT Gateway.\
For more information, see [Using packet filters](/nat/packet-filters/).
* **NAT Gateway Name** -- Change the name shown in the Megaport Portal. For example, `gcp-aws-nat-gateway`.
* **BGP Default State** -- Specify whether newly created BGP connections are enabled or shut down by default. Select **Enabled** (the default) to activate new BGP sessions immediately when you save the configuration. Select **Shutdown** to place new BGP sessions in a shut-down state when you save the configuration.
For example, you might want to select the **Shutdown** option if you plan to add several BGP sessions across your Virtual Cross Connects (VXCs) but need to complete other router setup before they exchange route information. After you finish configuring your routers, navigate to the relevant BGP sessions and enable them.
For more information about overriding the BGP state for an individual connection, see [Shutting down a BGP connection](/nat/configure-bgp#bgp-shut).
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Contract Terms** -- Click **Change Contract Term** to increase the contract term for the NAT Gateway.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information about contract terms, see [NAT Gateway Pricing and Contract Terms](/finance/nat-gateway-pricing).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
4. Click **Save**.
## Helpful references
* [Configuring a NAT Gateway VXC](/nat/configuring-nat-vxc)
* [Configuring BGP for Megaport NAT Gateway](/nat/configure-bgp)
* [Creating a NAT Gateway](/nat/creating-nat-gateway)
* [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc)
* [NAT Gateway Features](/nat/nat-gateway-features)
* [NAT Gateway Pricing and Contract Terms](/finance/nat-gateway-pricing)
# Configuring a NAT Gateway VXC
Source: https://docs.megaport.com/nat/configuring-nat-vxc
This help topic describes how to configure a VXC connected to a NAT Gateway, including interfaces, IP addresses, BGP connections, and static routes.
For each VXC connected to a Megaport NAT Gateway (NAT Gateway), you can configure one or more interfaces, IP addresses, BGP connections, or static routes. You can also select a NAT source IPv4 address and specify the IP MTU value.
For information about creating a new connection from a Megaport NAT Gateway, see [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc).
Depending on the VXC destination or cloud service provider, the NAT Gateway connection settings might have been auto-configured during VXC creation. Follow the steps in this task to configure the connection settings as required.
If the VXC provisioning status is LIVE, CONFIGURED, or DEPLOYABLE, the connection configuration fields are available when editing a VXC, regardless of provider.
**To edit a VXC interface**
1. Select the NAT Gateway VXC you want to edit.
2. Select the VXC A-End or B-End.
3. Enter a description for the connection.
4. Enter one or more interface IP addresses and subnet masks to configure on the A-End interface.
5. (Optional) Enter an value (in bytes) for the VXC.\
The IP MTU can range from 1280 to 9070 (9074 if Q-in-Q is disabled). The default value is 1500.
6. Enter any details specific to the VXC type.
* For more information about using NAT Gateway Pools, see [Using NAT Gateway Pools](/nat/nat-gateway-pools).
* For more information about using packet filters, see [Using Packet Filters](/nat/packet-filters).
* For more information about adding a BGP connection, see [Configuring BGP for Megaport NAT Gateway](/nat/configure-bgp).
* For more information about enabling Bidirectional Forwarding Detection (BFD) settings, see [Enabling the BFD protocol](/nat/bgp-advanced#bfd-protocol).
* For more information about adding a static route, see [Configuring Static Routing on a Megaport NAT Gateway](/nat/static-routing).
7. Click **Save**.
## Helpful references
* [Configuring Advanced BGP Settings](/nat/bgp-advanced)
* [Configuring BGP for Megaport NAT Gateway](/nat/configure-bgp)
* [Configuring Static Routing on a Megaport NAT Gateway](/nat/static-routing)
* [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc)
* [NAT Gateway Features](/nat/nat-gateway-features)
# Creating a NAT Gateway
Source: https://docs.megaport.com/nat/creating-nat-gateway
This help topic describes how to create a Megaport NAT Gateway in the Megaport Portal.
This topic describes how to create a Megaport NAT Gateway (NAT Gateway). The Megaport Portal guides you through selecting a location, specifying NAT Gateway configuration details, and placing the order.
Before you begin, you need to set up your Portal account. You will only be able to create NAT Gateways in billing markets you are registered in. For more information, see [Setting Up a Megaport Account](/setting-up).
**To create a Megaport NAT Gateway**
1. Log in to the Megaport Portal and choose **Services**.
2. Click **Add Services**, then select **NAT Gateway**.
3. Select a diversity zone.\
You can select either Red or Blue, or select Auto and have Megaport select the zone for you. The selected or allocated diversity zone will be displayed on the location details through the rest of the provisioning, and on the summary page at the end.\
For more information, see [NAT Gateway Diversity](/nat/nat-gateway-diversity).
4. Select the preferred data center location for the NAT Gateway. The country you choose must be a market in which you have already registered.\
You can use the **Search** field to find the data center name, Country, Metro City, or address of your preferred data center.
5. Click **Next**.\
The NAT Gateway configuration page appears.
6. Select a **Session Count**.\
This is the maximum number of concurrent sessions the NAT Gateway can manage.\
The session count is fixed for the life of the service.
7. Select the **Rate Limit**.\
The rate limit is an aggregate capacity that determines the speed for all connections through the NAT Gateway.\
The rate limit is fixed for the life of the service.
8. Specify the details for the NAT Gateway:
* **NAT Gateway ASN** – Specify the autonomous system number (ASN) of this NAT Gateway, or use the default public ASN, 133937, supplied by Megaport. For most configurations, the default ASN is suitable. The ASN is used for BGP peering sessions on any VXCs connected to this NAT Gateway. 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 more information about overriding the NAT Gateway ASN, see [Configuring Advanced BGP Settings](/nat/bgp-advanced).
* **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 **Shutdown** 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 select **Shutdown** if you plan to add multiple BGP sessions across your Virtual Cross Connects (VXCs) but want to complete additional router configuration before allowing them to exchange 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 more information about overriding the BGP state for an individual connection, see [Shutting down a BGP connection](/nat/configure-bgp#bgp-shut).
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information about contract terms, see [NAT Gateway Pricing and Contract Terms](/finance/nat-gateway-pricing).
9. Click **Next** to finalize the configuration.
* **NAT Gateway Name** – Specify a name for the NAT Gateway, which will be shown on the Megaport Portal. For example, `gcp-aws-nat-gateway`. You can change the name later, if needed.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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 NAT Gateway is not automatically updated with the NAT Gateway service level reference number.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
10. Confirm the selected options, then click **Add NAT Gateway**.
11. (Recommended) Create a second NAT Gateway, selecting the alternate diversity zone. For example, if the first NAT Gateway was created in the blue diversity zone, create a second NAT Gateway in the red diversity zone.
12. Click **Review Order**.
13. Review the Order Services agreement.
* Click **Save** to save the configured NAT Gateway before placing the order.
* Click **Add Promo Code** to enter a promotional code, and click **Add Code**.
* Click **Order Now** to order and provision the NAT Gateway.
NAT Gateways are postpaid. For example, if you place your order on the 15th of January, your first invoice will be on the 1st of February, and will have a proportional charge for the period from the 15th of January to the 31st of January.
Now that you have deployed a Megaport NAT Gateway, 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 NAT Gateway using a private VXC or connect to a service provider in the Megaport Marketplace. For more information about adding VXCs, see [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc).
## Helpful references
* [Configuring a NAT Gateway](/nat/configuring-nat)
* [Configuring a NAT Gateway VXC](/nat/configuring-nat-vxc)
* [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc)
* [Megaport NAT Gateway Overview](/nat)
* [NAT Gateway Diversity](/nat/nat-gateway-diversity)
* [NAT Gateway Features](/nat/nat-gateway-features)
* [NAT Gateway Pricing and Contract Terms](/finance/nat-gateway-pricing)
# Megaport NAT Gateway Overview
Source: https://docs.megaport.com/nat/index
This help topic describes the Megaport Network Address Translation Gateway (Megaport NAT Gateway) service.
A Megaport NAT Gateway (NAT Gateway) is a Network Address Translation () service that enables devices in a private network to access the internet without requiring each device to have a public IP address.
NAT Gateways provide several key benefits:
* Hides internal IP addresses using Source NAT (SNAT), keeping your private network topology invisible to external endpoints.
* Improves security by blocking incoming connections and preventing external entities from directly accessing private resources.
* Provides internet access for private subnets so devices can access the internet or external services.
* Conserves IP addresses by using a single public IP address or a pool of public IP addresses for all outbound traffic from private resources.
* Scales to manage high traffic volumes and a high number of concurrent translations efficiently.
* Lowers egress costs by routing outbound internet traffic through a single centralized service rather than individual cloud-provider NAT offerings.
## How it works
Devices inside private networks have private IP addresses. When a device in a private network starts a connection to a resource outside the private network, a NAT Gateway translates the device’s private IP address into a public IP address.
NAT allows devices on the private network to communicate with external networks while keeping internal IP addresses hidden.
A Megaport NAT Gateway can translate all traffic to an IP address or to a range of addresses based on rules.
When a device on a private network requests information from the internet through a NAT Gateway:
1. The device in a private subnet sends a request to the internet. This request is routed through the NAT Gateway.
2. The NAT Gateway replaces the source IP with its own public IP address and adds an identifier so that it can forward the response to the source device.
3. The request is sent to the destination, such as a web server or an API server on the internet.
4. The response comes back to the NAT Gateway, which translates the public IP back to the original private IP.
5. The response is sent to the source device, completing the request.
## Megaport NAT Gateway sizes
Megaport NAT Gateways are available with the following limits:
| Session Count | Rate Limits in Gbps |
| :-: | :-: |
| 250,000 | 1, 2.5, 5, and 10 |
| 500,000 | 10 and 25 |
| 1,000,000 | 10, 25, and 50 |
| 2,500,000 | 10, 25, 50, and 100 |
| 5,000,000 | 10, 25, 50, and 100 |
| 10,000,000 | 10, 25, 50, and 100 |
## Difference between MCR NAT and Megaport NAT Gateway
### How MCR NAT works
The Megaport Cloud Router (MCR) employs Overload NAT, a combination of Source NAT (SNAT) and Port Address Translation (PAT) to map multiple internal IP addresses to a single, globally unique IP address for outbound connectivity.
By assigning unique source ports to each session, the MCR ensures distinct communication paths while hiding internal network topologies from external partners, such as cloud providers or the internet.
Although typically used to translate private IP addresses to public IP addresses for egress traffic, the system is flexible enough to translate any IP address type on either interface, making it an essential tool for navigating addressing requirements and resolving subnet overlaps. For more information, see [How MCR Performs NAT](/mcr/mcr-nat).
### How Megaport NAT Gateway works
NAT Gateways also employ Overload NAT, Source NAT (SNAT), and Port Address Translation (PAT). They can manage larger traffic volumes, supporting over 1 million connections per second and up to 30 million total translations.
NAT Gateways specialize in processing intensive NAT operations, ensuring that they do not bottleneck the system, maintaining the high-speed throughput required for 100 Gbps networking environments.
## Helpful references
* [A Guide to NAT Gateway](https://www.megaport.com/blog/a-guide-to-nat-gateway/)
* [Creating a NAT Gateway](/nat/creating-nat-gateway)
* [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc)
* [Configuring a NAT Gateway](/nat/configuring-nat)
* [Configuring a NAT Gateway VXC](/nat/configuring-nat-vxc)
* [Configuring Advanced BGP Settings](/nat/bgp-advanced)
* [Configuring BGP for Megaport NAT Gateway](/nat/configure-bgp)
* [How MCR Performs NAT](/mcr/mcr-nat)
* [Introducing Megaport NAT Gateway](https://www.megaport.com/blog/introducing-megaport-nat-gateway/)
* [NAT Gateway Diversity](/nat/nat-gateway-diversity)
* [NAT Gateway Features](/nat/nat-gateway-features)
* [NAT Gateway Limits and Quotas](/limits-quotas#nat-gateway)
* [NAT Gateway Pricing and Contract Terms](/finance/nat-gateway-pricing)
* [Terminating a Megaport NAT Gateway](/nat/terminating-nat-gateway)
* [Using NAT Gateway Pools](/nat/nat-gateway-pools)
# NAT Gateway Diversity
Source: https://docs.megaport.com/nat/nat-gateway-diversity
This help topic describes the architecture and importance of diversity options for the Megaport NAT Gateway service.
Diverse connections improve the robustness of your network by using different physical infrastructure to provide network services. Diverse connections build in redundancy and eliminate single points of failure.
() simplifies the deployment of diverse connections by establishing diversity zones. A diversity zone is a group of devices at a single Megaport location. s in different diversity zones are physically separated on Megaport devices and connected to different devices.
During Megaport scheduled maintenance, no more than one diversity zone in a given metro will experience downtime at any time. Whenever possible, diversity zones in the same city have maintenance periods scheduled for different days.
Each indicates its diversity zone with either a red or blue icon.
## Selecting a diversity zone
When you select the location for your , you can select the diversity zone.
When you choose a diversity zone, the location results list will be filtered by that zone:
* **Auto (default)** -- This will show all locations where is available.
* **Red or Blue diversity zone** -- If you select Red or Blue diversity zone, only locations that have availability in that zone will be displayed.
| Icon | Meaning | Use case |
| :-: | :- | :- |
| | Auto select diversity zone | Allow Megaport to allocate the diversity zone |
| | Red diversity zone | Allocate the to the red diversity zone |
| | Blue diversity zone | Allocate the to the blue diversity zone |
### Auto diversity zone
If you choose the Auto diversity zone option, Megaport will select the zone to which your service is allocated.\
The following rules apply:
* If both diversity zones are available, one zone will be chosen.
* If only one zone is available, that zone will be chosen.
# NAT Gateway Features
Source: https://docs.megaport.com/nat/nat-gateway-features
This help topic describes the features of Megaport NAT Gateways.
A Megaport NAT Gateway (NAT Gateway) provides and routing services for your network traffic. This topic describes the features of NAT Gateways, including supported routing features, public IP address allocation, and security options.
## VXC connections
NAT Gateway supports VXC connections to Cloud Service Providers (CSPs), other Megaport services, and private networks. You can create multiple connections from a NAT Gateway.
For more information, see [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc).
## Secure VLANs
The Connection option allows either a single VLAN (non Q-in-Q, also known as 802.1Q) or stacked VLANs (Q-in-Q, also known as 802.1ad) to be carried over a VXC. In most cases, you will 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 NAT Gateway being configured.
For certain use cases, you might need multiple inner VLANs exposed to a Port using Q-in-Q.
For more information about Q-in-Q, see [Configuring Q-in-Q](/connections/q-in-q).
NAT Gateway supports the standard Ethernet MTU of 1500 bytes.
## Public IP address allocation
When ordering the NAT Gateway, public IP addresses are provided as required, based on specific CSP requirements. Megaport allocates up to a /29 free of charge from the Megaport address space for this connectivity. You can also use your own public IP addresses.
For an Azure ExpressRoute primary and secondary IP address, Megaport provides a /30 or 4 addresses for each.
## IP MTU (Maximum Transmission Unit)
You can set the IP MTU value on a NAT Gateway up to a maximum of 9070 (if Q-in-Q is enabled) or 9074 (if Q-in-Q is disabled).
Fewer, larger packets ensure faster data transfer with reduced packet processing overhead. This is ideal for transferring large files between clouds or improving performance for high-throughput applications, such as machine learning workloads.
## Dynamic routing with BGP
Dynamic routing propagates route table updates from the NAT Gateway across VXCs to destination ports. NAT Gateway uses the Border Gateway Protocol (BGP) to provide flexible routing by exchanging routing information between peers.
NAT Gateway supports these BGP routing features:
* [AS Override](#as-override)
* [Bidirectional forwarding detection (BFD)](#bidirectional-forwarding-detection-bfd)
* [Multiple exit discriminator (MED)](#multiple-exit-discriminator-med)
* [BGP administrative shutdown](#bgp-administrative-shutdown)
### AS Override
AS Override replaces the peer's autonomous system number (ASN) in the AS\_PATH attribute of outbound BGP routes with the local ASN. This feature helps connect sites that share the same ASN by allowing BGP routes to be advertised to peers that would otherwise reject them due to loop detection.
AS Override is valid only for eBGP connections. The local ASN must differ from the peer ASN to enable this option.
### Bidirectional forwarding detection (BFD)
Enabling BFD on a VXC connection provides fast link failure detection and failover when connecting to services that support BFD on the remote peer. After BFD is enabled, a BGP peer relationship can be torn down quickly after notifications from BFD, failing over to another BGP peer.
For more information, see [Enabling the BFD protocol](/nat/bgp-advanced#bfd-protocol).
### Multiple exit discriminator (MED)
You can enable MED on VXC connections. For more information, see [Configuring a preferred route with MED](/nat/bgp-advanced#med).
### BGP administrative shutdown
BGP shutdown provides an easy way to administratively shut down a BGP connection without removing it. This feature can be useful while setting up a new route, performing maintenance, and so on.
For more information, see [Shutting down a BGP connection](/nat/configure-bgp#bgp-shut).
## Static routing
Without BGP, NAT Gateways use static routing to directly connect manually configured routes that access a single route. Static routing is generally used in place of BGP when a customer device does not support BGP or the target device requires manually configured IP addressing and routes.
For more information, see [Configuring Static Routing on a Megaport NAT Gateway](/nat/static-routing).
## Autonomous system number (ASN) support
An autonomous system (AS) is a single network or a set of networks and routers that are managed and supervised by a common network administrator (or group of administrators) on behalf of a single administrative entity, such as a business division. An AS is assigned a globally unique number that identifies the network to the world. NAT Gateway supports both 2-byte and 4-byte autonomous system numbers (ASNs).
ASN support includes per-peer local ASNs.
## Limitations
Only Source NAT (outbound) is supported. The NAT Gateway translates private source addresses to a public IP for traffic initiated from within your private network. Destination NAT, which would translate a public IP address originating from the internet to a private destination address, is not supported.
For workloads requiring fewer than 128,000 concurrent NAT sessions, a Megaport Cloud Router (MCR) might be more appropriate. MCRs include built-in NAT functionality suited to lower-volume use cases. For more information, see [How MCR Performs NAT](/mcr/mcr-nat).
## Helpful references
* [Configuring a NAT Gateway VXC](/nat/configuring-nat-vxc)
* [Configuring Advanced BGP Settings](/nat/bgp-advanced)
* [Configuring BGP for Megaport NAT Gateway](/nat/configure-bgp)
* [Configuring Q-in-Q](/connections/q-in-q)
* [Configuring Static Routing on a Megaport NAT Gateway](/nat/static-routing)
* [Creating a NAT Gateway](/nat/creating-nat-gateway)
* [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc)
* [Megaport NAT Gateway Overview](/nat)
# Using NAT Gateway Pools
Source: https://docs.megaport.com/nat/nat-gateway-pools
This help topic describes how to configure NAT Gateway Pools.
NAT Gateway pools define how the NAT Gateway translates outgoing traffic to public IP addresses. Each pool contains one or more IP address ranges (IP Networks), which are the public addresses to which the NAT Gateway translates outgoing traffic.
NAT Gateway Pools should be defined on VXCs connecting to resources outside your network, such as the internet. You do not need to define NAT Gateway Pools on VXCs connecting resources inside your network, such as connecting the company's offices to the NAT Gateway.
You can define rules for each pool to control which traffic the pool manages. Each rule specifies a source address, which is a range that identifies the outgoing traffic the NAT Gateway should translate using that pool's IP Networks. You can add up to 16 rules per pool and up to 16 pools per NAT Gateway.
## How pools and rules work
When the NAT Gateway receives outgoing traffic, it evaluates the traffic against your configured pools and rules:
* If the traffic's source address matches a rule in a pool, the NAT Gateway translates the source address to one of the IP addresses in that pool's IP networks.
* If a pool has no rules, the NAT Gateway uses it for any traffic that does not match a rule in another pool.
* If you have not defined any rules across any pool, the NAT Gateway translates all traffic using IP addresses from the first pool.
NAT Gateway performs Source NAT, translating the source address of outgoing traffic from your private network. It does not translate incoming traffic from the internet.
## Configuring pools and rules
You configure NAT Gateway pools and rules on VXCs connected to the NAT Gateway. Pools apply only to the VXCs on which they are configured.
The A-End (or B-End) can be configured in some VXCs during creation, others you have to come back and edit.
### Before you begin
Before you can configure NAT Gateway pools and rules, you need to:
* have at least one Megaport NAT Gateway.\
For more information, see [Creating a NAT Gateway](/nat/creating-nat-gateway).
* have at least one VXC connected to the NAT Gateway, or be creating one.\
For more information, see [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc).
### Configure pools and rules when creating a VXC
You can configure NAT Gateway pools and rules when creating a new VXC on the NAT Gateway A-End or B-End configuration page. If you cannot configure pools and rules when creating the VXC, you can configure them after you order the VXC.
**To configure NAT Gateway pools and rules when creating a VXC**
1. On the NAT Gateway A-End or B-End configuration page, in the NAT Gateway Pools section, specify the pool details:
* **IP Address Pool Name** (optional) -- A name for the pool.
* **IP Networks** -- One or more CIDR ranges that define the public IP addresses to which the NAT Gateway translates outgoing traffic.
2. To add rules to the pool, click **Show Rules** and specify the rule details:
* **Source Address** -- A CIDR range that identifies the outgoing traffic the NAT Gateway should translate using that pool's IP Networks. You can add additional rules by clicking the add rule (**+**) button.
3. To add additional pools, click the add pool (**+**) tab and repeat steps 1 and 2.
4. When you are finished, click **Next** to continue creating the VXC.
### Configure pools and rules on an existing VXC
You can configure NAT Gateway pools and rules on an existing VXC connected to a NAT Gateway.
**To configure NAT Gateway pools and rules on an existing VXC**
1. On the Services page, select the NAT Gateway VXC you want to edit.
2. Select the VXC A-End or B-End.
3. In the NAT Gateway Pools section, specify the pool details:
* **IP Address Pool Name** (optional) -- A name for the pool.
* **IP Networks** -- One or more CIDR ranges that define the public IP addresses to which the NAT Gateway translates outgoing traffic.
4. To add rules to the pool, click **Show Rules** and specify the rule details:
* **Source Address** -- A CIDR range that identifies the outgoing traffic the NAT Gateway should translate using that pool's IP Networks. You can add additional rules by clicking the add rule (**+**) button.
5. To add additional pools, click the add pool (**+**) tab, then repeat steps 1 and 2.
6. When you are finished, click **Save**.
## Helpful references
* [Creating a NAT Gateway](/nat/creating-nat-gateway)
* [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc)
* [Configuring a NAT Gateway VXC](/nat/configuring-nat-vxc)
# Creating a NAT Gateway VXC
Source: https://docs.megaport.com/nat/nat-gateway-vxc
This help topic describes how to create Virtual Cross Connects (VXCs) on a Megaport NAT Gateway (NAT) to connect to services on the Megaport network.
With a Megaport NAT Gateway (NAT Gateway) configured, you can add a Virtual Cross Connect (VXC) to a cloud service provider, a local port, or a third-party network. You can optionally connect a physical Port to the NAT Gateway using a private VXC or connect to a service provider in the Megaport Marketplace.
A VXC 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 NAT Gateway.
The VXC target destination type determines the peering type. The peering type determines which routes are advertised. For more information, see [Megaport NAT Gateway Route Advertisement](/nat/route-advertisement).
**To create and connect a VXC**
1. Log in to the Megaport Portal, select **Services**, then select the NAT Gateway.\
If you haven't already created a NAT Gateway, see [Creating a NAT Gateway](/nat/creating-nat-gateway).
2. If this is the first connection for the NAT Gateway, 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:
* **Cloud** -- Provision a dedicated interconnect to a public cloud service provider. After selecting Cloud, select a provider. Some providers require a service key.
For specific CSP configuration details:
* Latitude.sh -- See [Creating NAT Gateway Connections to Latitude.sh](/cloud/nat/latitude-sh)
* **Private VXC** -- Connect to other Ports local to the current company account. After selecting Private VXC, select a destination Port.\
For more information, see [Creating a Private VXC](/connections/private-vxc).
* **Megaport Internet** -- Connect to the internet. After selecting Megaport Internet, select a destination port (internet router).\
For more information, see [Creating a Megaport Internet Connection for a NAT Gateway](/megaport-internet/nat-gateway).
* **Megaport Marketplace** -- Connect to any service provider present in the Megaport Marketplace. After selecting Megaport Marketplace, select a provider.\
For more information, see [Megaport Marketplace](/marketplace/overview).
* **Enter Service Key** -- Connect to a third-party on the Megaport network that isn’t publicly listed in the Megaport Marketplace. Select this destination if you have been given a service key, and enter the service key.\
For more information, see [Creating a Connection using a Service Key](/marketplace/create-connection-service-key).
3. Click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Specify a rate limit that doesn't exceed the total rate limit for the NAT Gateway. Allow enough bandwidth for any connections that you might add later.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.\
The NAT Gateway A-End Connection Details page appears. For each VXC connected to a NAT Gateway, you can configure one or more interfaces, IP addresses, BGP connections, packet filter lists, and static routes. Most VXCs will use one interface, however, you can configure multiple interfaces by enabling a connection and specifying an inner VLAN tag for each interface. Each VLAN ID must be unique and you can add up to five VLAN IDs.
The NAT Gateway A-End Connection Details page is not displayed during NAT Gateway VXC creation in some situations, and is dependent on the VXC destination. The NAT Gateway VXC configuration will be auto-configured in these situations. If you are creating a single-use service key on a NAT Gateway, the configuration is not auto-configured and the page will be displayed. For information about configuring connection details when they are auto-configured, see [Configuring a NAT Gateway](/nat/configuring-nat).
6. Enter a description for the current interface connection.
7. If required, click **Enable Q-in-Q** to enable multiple interfaces or click **+ Add Interface** to add an additional interface, automatically enabling Q-in-Q.
8. Enter one or more interface IP addresses and subnet masks to configure on the A-End (or B-End) interface.
9. (Optional) Enter an value (in bytes) for the VXC.\
The IP MTU can range from 1280 to 9070 (9074 if Q-in-Q is disabled). The default value is 1500.\
For more information, see [NAT Gateway Features](/nat/nat-gateway-features).
10. Define the NAT Gateway Pools and their rules for this VXC.\
For more information, see [Using NAT Gateway Pools](/nat/nat-gateway-pools).
11. Enter any details specific to the VXC type, such as:
* Packet filters
* BGP connections
* Static routes
12. Click **Next**.
13. Configure the B-End.\
The requirements will vary by destination or provider.
14. Click **Next**.\
The Summary page appears.
15. Review the Summary details.\
Click each down arrow to view A-End and B-End configuration details.
16. Click **Add VXC**.
17. Click **Review Order**.
18. Click **Order Now**.
## Helpful references
* [Configuring a NAT Gateway VXC](/nat/configuring-nat-vxc)
* [Configuring BGP for Megaport NAT Gateway](/nat/configure-bgp)
* [Configuring Static Routing on a Megaport NAT Gateway](/nat/static-routing)
* [Creating a NAT Gateway](/nat/creating-nat-gateway)
* [Creating a Private VXC](/connections/private-vxc)
* [Megaport NAT Gateway Overview](/nat)
# Using Packet Filters with NAT Gateway
Source: https://docs.megaport.com/nat/packet-filters
This help topic describes how to create, edit, and apply packet filter lists on a NAT Gateway.
Packet filters control which traffic flows through your Megaport NAT Gateway (NAT Gateway). Packet filters allow data from defined IP addresses to pass through, and deny access to data from other defined IP addresses.
Packet filters are defined on a NAT Gateway after it has been ordered and has gone live. You then edit the configuration of your NAT Gateway to add the packet filters that you need. When you configure a connection to your NAT Gateway, you can add your packet filters to either the A-End or B-End of the connection, depending on your NAT Gateway's location.
## Packet filter rules
* Packet filter lists are defined on a deployed NAT Gateway.
* Packet filter lists are applied to the VXC interface - either A-End or B-End, depending where your NAT Gateway is located.
* If no packet filters are applied to the connection, then all traffic is allowed to flow through your NAT Gateway.
* When a packet filter is applied to the connection, any traffic not permitted by the packet filter is denied.
* Packet filters support the following matches:
* Source IP Address
* Destination IP Address
* IP Protocol
* Source Port/Port Range (for TCP and UDP protocols)
* Destination Port/Port Range (for TCP and UDP protocols)
* Packet filters support both IPv4 and IPv6.
* You can create up to 20 packet filter lists.
* Each packet filter list can contain up to 50 entries.
## Creating packet filters
You can only create packet filters on a deployed NAT Gateway. You can create a maximum of 20 packet filter lists per NAT Gateway.
**To create a packet filter list**
1. Create, order, and deploy a NAT Gateway.\
For more information, see [Creating a NAT Gateway](/nat/creating-nat-gateway).
2. On the Services page, find your new NAT Gateway and click the gear icon next to the NAT Gateway in the Portal.
The NAT Gateway Configuration page appears.
3. Select the **Packet Filter Lists** tab.\
The Packet Filter List page appears.
4. Click **New List** to add a new list.
5. Enter a name for your packet filter list in the **Name** field.
6. Enter your filter details.
* **Action** -- Select Permit or Deny from the drop-down list.
* **Source IP Address** -- Enter the source IP address you want to filter traffic from.
* **Destination IP Address** -- Enter the destination IP address of your filter.
The source IP address and destination IP address must be the same format. For example, they must both be IPv4 or IPv6.
* **Protocol** -- Select the protocol to filter traffic on. If the protocol you require is not on the list, you can select **Custom**.
* **IP Protocol Number** -- This will be populated automatically when you choose a protocol from the drop-down list. If you choose **Custom**, you must enter a number from the list of assigned internet protocol numbers.
* **Source Ports** -- You can specify a source port or a range of ports in the format 1111-9999.
* **Destination Ports** -- Specify a destination port or a range of ports.
* **Description** (optional) -- Add a description.
Use the position icon at the beginning of the row to reorder the list using drag and drop.\
Click the trash icon at the end of the row to delete an entry in a list.
7. Add as many entries to the list as you need, up to a maximum of 50 per list.
8. Click **Save**.
## Editing a packet filter list
Add or delete entries from a packet filter list, or update the settings of each entry.
**To edit a packet filter list**
1. Select the list you want to edit from the drop-down list.
2. Make your changes.\
You can change any part of the list.
3. Click **Save**.
## Duplicating a packet filter list
You can duplicate a list to speed up filter configuration.
**To duplicate a packet filter list**
1. Select the list you want to duplicate from the drop-down list.
2. Click **Duplicate List**.
3. Enter a name for the list in the **Name** field.
4. Edit the required details in the list to make it unique.
5. Click **Save**.
## Deleting a packet filter list
You can delete entire lists if they are not required any more or are out of date.
**To delete a packet filter list**
1. Select the list you want to delete from the drop-down list.
2. Click **Delete List**.
3. Click **OK** to confirm.
## Applying a packet filter list
You can apply a packet filter list to the VXC when you create a connection from your NAT Gateway.
**To apply a packet filter list**
1. Create a connection from the NAT Gateway with the packet filter lists defined.\
For more information, see [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc).
2. In the VXC definition, enter the connection details then click **Next**.
3. On the NAT Gateway A-End page, enter these details:
* **Interface IP Addresses** -- Enter the A-End interface IP address and subnet mask as required for your network.
* **Packet Filters** -- Select a packet filter list from the **Inbound** or **Outbound** drop-down list, as required for your configuration.
You can also fill in other fields here, such as IP addresses or BGP connections.\
For more information, see [Configuring a NAT Gateway VXC](/nat/configuring-nat-vxc).
4. Click **Next**.
5. Read the Summary page and click **Add VXC**.
## Helpful references
* [Creating a NAT Gateway](/nat/creating-nat-gateway)
* [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc)
* [Megaport NAT Gateway Route Filtering](/nat/route-filtering)
* [NAT Gateway Features](/nat/nat-gateway-features)
# Megaport NAT Gateway Route Advertisement
Source: https://docs.megaport.com/nat/route-advertisement
This help topic describes NAT Gateway peering types and the routes advertised by each type.
This topic describes NAT Gateway peering types and the routes advertised by each peering type.
The Megaport NAT Gateway (NAT Gateway) works in architectures that are connected using different combinations of peering types. In addition to private peering connectivity, NAT Gateway can connect to public peering types such as AWS, Azure, Oracle, and other Cloud Service Providers (CSPs).
NAT Gateway uses a Virtual Cross Connect (VXC) to connect to other endpoints on the Megaport network. The VXCs support different types of peers. NAT Gateway employs routing policies aligned with the VXC peering type.
The peering type defined for the VXC determines which routes are advertised.
## NAT Gateway peering types
NAT Gateway supports the peering types shown in this table:
| **Peering Type** | **Megaport Peering Attribute** | **Routes Advertised** |
| - | - | - |
| Non-cloud | NON\_CLOUD | Routes from the Border Gateway Protocol (BGP) peer behind a Port and AWS Hosted Connections. |
| Private cloud | PRIV\_CLOUD | Routes from AWS Hosted VIF Private, Azure Private Peer, and Google Cloud Platform. |
| Public cloud | PUB\_CLOUD | Routes from AWS Hosted VIF Public, Azure MS Peer, Salesforce, and other cloud providers. |
* Although you can configure private cloud and public cloud peering types simultaneously, NAT Gateway does not exchange routes between the two.
* AWS Direct Connect Hosted Connection partners cannot see the VIF type created within AWS. As a result, traffic from these hosted connections is categorized as NON\_CLOUD. NAT Gateway users should take care not to advertise public cloud routes to other cloud providers. NAT Gateway route filtering is available to help manage this.
### Non-cloud VXCs
NON\_CLOUD VXCs are categorized into these types:
* **Physical Port Connections** -- VXCs connected to a physical port in a data center, typically referring to private network infrastructure.
* **AWS Hosted Connections** -- These are classified as NON\_CLOUD because AWS connectivity partners do not have a mechanism to identify the VIF type created within AWS.
* **Megaport Marketplace Service Providers** -- Connections to various service providers listed in the Megaport Marketplace.
* **Business-to-Business (B2B) VXCs** -- Connections established between multiple Megaport accounts using service keys.\
For more information, see [Setting up Service Keys](/marketplace/service-keys).
| **Megaport Endpoint** | **Peering Type** |
| - | - |
| Physical Port | Private VXC |
| NAT Gateway | AWS Hosted Connection on VXC |
| Megaport Marketplace | Private VXC |
| B2B VXC | Service Key |
### Private cloud VXCs
Private cloud (PRIV\_CLOUD) VXCs connect to private peering options with public Cloud Service Providers (CSPs). Private peering typically involves exchanging [RFC 1918](https://www.rfc-editor.org/rfc/rfc1918) routes with the service provider.
| **Cloud Service Provider** | **Peering Type** |
| - | - |
| AWS Direct Connect | Hosted VIF with Private VIF |
| Azure ExpressRoute | Private Peering |
| Google Cloud Interconnect | Partner Interconnect Attachment |
| Oracle Cloud Infrastructure | FastConnect Private Peering |
Similar connectivity is available from IBM Cloud, Alibaba, SAP HANA Enterprise Cloud, and many other CSPs.
### Public cloud VXCs
Public cloud (PUB\_CLOUD) VXCs provide direct connectivity to public peering options from public CSPs. Public peering options typically involve exchanging public address space with a service provider.
| **Cloud Service Provider** | **Peering Type** |
| - | - |
| AWS Direct Connect | Hosted VIF with Public VIF |
| Azure ExpressRoute | Microsoft Peering |
| Salesforce | ExpressConnect |
| Oracle Cloud Infrastructure | FastConnect Public Peering |
## Route advertisement scenarios
### Non-cloud and private cloud
A combination of non-cloud and private cloud connectivity is fairly straightforward when it comes to route advertisement. Using network virtualization and segmentation mechanisms allow multi-tenant networks to exchange private RFC 1918 address space between each environment. The private cloud is introduced as a private node on your internal network.
This image shows a corporation using a firewall to segment its cloud connectivity. The cloud network is connecting from their firewall in the data center to their NAT Gateway via a private NON\_CLOUD VXC. The NAT Gateway is, in turn, connecting to AWS via a PRIV\_CLOUD VXC.
### Public cloud
The public cloud connectivity option requires the exchange of public address space, similar to peering with an internet service provider (ISP). Large organizations that require connectivity to multiple ISPs employ network engineers and architects that are familiar with all of the nuanced requirements necessary to participate in exchanging public routes on the internet.
NAT Gateway alleviates some of these nuances by providing default policies that ensure you don't inadvertently advertise public routes of one CSP to another CSP.
For example, consider route advertisement in a network topology with an ExpressRoute Microsoft peering to Azure and a public virtual interface (VIF) to AWS.
If any-to-any connectivity were allowed between the two public cloud peerings, all traffic between AWS and Azure would traverse NAT Gateway. This would cause a global service disruption for both CSPs. To avoid service disruption, the CSPs protect their customers with policies that prevent this type of misconfiguration. However, because mistakes can happen, NAT Gateway also has routing mechanisms in place to restrict the public cloud peering types from exchanging public address spaces.
### NAT Gateway route advertisement configurations
The supported NAT Gateway route advertisement configuration types are:
* Public cloud → Non-cloud
* Private cloud → Non-cloud, Private cloud
* Non-cloud → Non-cloud, Private cloud, Public cloud
Support for these peering configuration types enables a globally available platform that allows rapid, on-demand deployment of routing services in a secure manner, with best practice routing policies already applied.
## Helpful references
* [Configuring BGP for Megaport NAT Gateway](/nat/configure-bgp)
* [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc)
* [Megaport NAT Gateway BGP Peer Filtering](/nat/bgp-peer-filtering)
* [Megaport NAT Gateway BGP Prefix Filtering](/nat/bgp-prefix-filtering)
* [Megaport NAT Gateway Route Filtering](/nat/route-filtering)
# Megaport NAT Gateway Route Filtering
Source: https://docs.megaport.com/nat/route-filtering
This help topic describes Megaport NAT Gateway route filtering concepts and filter types.
This topic provides an overview of Megaport NAT Gateway (NAT Gateway) route filtering concepts.
## Route filtering overview
Route filtering provides control over NAT Gateway route installation and propagation, typically between two or more networks. The networks can be either on-premises or a Cloud Service Provider (CSP).
Route filters are optional and can be used to:
* redistribute or prevent redistribution of routes between Virtual Cross Connects (VXCs).
* create a BGP prefix filter that includes a set of IPv4 or IPv6 CIDR blocks to manage as a group.
* allow or deny specific routes on specific connections.
## Default peering route advertisements
NAT Gateways use to exchange network reachability information with adjacent BGP systems, known as *neighbors*, or *peers*. NAT Gateways work in architectures that are connected using different combinations of peering types. In addition to private peering connectivity, NAT Gateways can connect to public peering types such as AWS, Azure, Oracle, and other Cloud Service Providers (CSPs).
BGP communicates between two neighbors using a standard TCP connection. By default, once the BGP neighbors are connected, they share routing information with each other. The connection between the neighbors is called a BGP connection or session.
Without using any route filters, Megaport advertises routes to BGP connections based on these peering types:
| **Peering Type** | **Routes Advertised** | **Advertised To** |
| - | - | - |
| Non-cloud | Routes from the Border Gateway Protocol (BGP) peer behind a Port. | Non-cloud, private cloud, public cloud |
| Private cloud | Routes from AWS Private, Azure Private Peer, and Google Cloud Platform. | Non-cloud, private cloud |
| Public cloud | Routes from AWS Public, Azure MS Peer, Salesforce, and other cloud providers. | Non-cloud |
As an example, a route received from a public cloud BGP connection will not be advertised to a private cloud BGP connection.
You cannot override or control the peering type route advertisement.
Route filtering doesn't change this existing peer type policy but provides finer control when you need to filter specific routes or prefixes that would have otherwise been discovered and exchanged between BGP neighbors. Route filters cannot be used to advertise routes that are already filtered based on the peer type.
For the default route advertisement details, see [Megaport NAT Gateway Route Advertisement](/nat/route-advertisement).
## Selecting a filter type
You can set a route filter to define which route advertisements the NAT Gateway permits or denies from BGP neighbors. You can filter routes by BGP connection or by prefix. Route filtering supports IPv4 and/or IPv6 routes for each format.
The two filter types are:
* **BGP peer filter** -- A filter that permits or denies all routes exchanged between BGP neighbors. For example, in a network deployment with BGP neighbors A, B, and C, A and B are allowed to exchange routes with each other but not with C, while all neighbors can exchange routes with headquarters. BGP peer filtering provides a simple way to filter routes between the neighbors to meet these requirements.
For more information, see [Megaport NAT Gateway BGP Peer Filtering](/nat/bgp-peer-filtering).
* **BGP prefix filter** -- An advanced filter that permits or denies specific routes using route prefixes (IP addresses or ranges) to identify individual neighbors. You can apply the same prefix filter to more than one BGP neighbor, eliminating the need to type manual, redundant prefix entries. You can specify a permit or deny action for each prefix in the filter list. You can apply different lists using import or export directions.
For more information, see [Megaport NAT Gateway BGP Prefix Filtering](/nat/bgp-prefix-filtering).
## Helpful references
* [Configuring BGP for Megaport NAT Gateway](/nat/configure-bgp)
* [Megaport NAT Gateway BGP Peer Filtering](/nat/bgp-peer-filtering)
* [Megaport NAT Gateway BGP Prefix Filtering](/nat/bgp-prefix-filtering)
* [Megaport NAT Gateway Route Advertisement](/nat/route-advertisement)
* [Megaport NAT Gateway Route Summarization](/nat/route-summarization)
# Megaport NAT Gateway Route Summarization
Source: https://docs.megaport.com/nat/route-summarization
This help topic describes how to achieve route summarization-like behavior on a Megaport NAT Gateway.
This topic describes how to achieve a similar outcome to route summarization on NAT Gateway using a combination of static routes and filtering. This helps you avoid exceeding CSP limits when advertising routes.
This image shows how route summarization can be configured, with the customer-facing VXC originating several prefixes when you want to advertise only a summary route to the CSP.
If you configure a static on the VXC facing the source of the smaller networks, the NAT Gateway also advertises the supernet to the CSP. You can then use prefix filters to prevent the NAT Gateway from advertising the specifics to the CSP, which achieves approximately the same behavior as route summarization.
## Helpful references
* [Configuring BGP for Megaport NAT Gateway](/nat/configure-bgp)
* [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc)
* [Filtering by BGP prefix](/nat/bgp-prefix-filtering#bgpprefixfilter)
* [Introduction to Route Summarization](https://networklessons.com/rip/introduction-route-summarization)
* [Megaport NAT Gateway Route Filtering](/nat/route-filtering)
* [Route Summarization](https://networklessons.com/subnetting/route-summarization)
# Configuring Static Routing on a Megaport NAT Gateway
Source: https://docs.megaport.com/nat/static-routing
This help topic describes how to configure static routing on a Megaport NAT Gateway.
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 the route when there are any topology changes.
A NAT Gateway supports up to 100 static routes.
**To add a static route**
1. In the Megaport Portal, go to the **Services** page.
2. Select the VXC and select the NAT Gateway A-End.
3. In the NAT Gateway Connection detail page, under Static Routes, specify the IPv4 or IPv6 destination network address in CIDR notation.
4. Specify the IPv4 or IPv6 address of the next-hop router.\
The address must be in the same subnet as the interface but it cannot match the interface IP address.
5. (Optional) In the **Description** field, include any notes that will help identify this static route.\
The description range is from 1 to 100 characters.
6. Click **Next**.
7. Update the NAT Gateway B-End, if necessary.
8. Click **Next**.
9. Click **Update**.
## Helpful references
* [Configuring a NAT Gateway VXC](/nat/configuring-nat-vxc)
* [Configuring BGP for Megaport NAT Gateway](/nat/configure-bgp)
* [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc)
# Terminating a Megaport NAT Gateway
Source: https://docs.megaport.com/nat/terminating-nat-gateway
This help topic describes how to cancel and remove a Megaport NAT Gateway service from the Megaport Portal.
You can terminate a Megaport NAT Gateway (NAT Gateway) directly from the Megaport Portal. Terminating a NAT Gateway on a contract term will result in an early termination fee (ETF) equal to 100% of the remainder of the term.
For more information about Megaport NAT Gateway contract terms, see [NAT Gateway Pricing and Contract Terms](/finance/nat-gateway-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate a NAT Gateway**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the NAT Gateway you want to terminate.
The Terminate Services window appears. Early termination fees will be shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason you are terminating the NAT Gateway. We use this information to help us improve your customer experience.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm the NAT Gateway termination, or click **No, Keep Services** to cancel.\
The NAT Gateway and its associated VXCs are deleted from the Megaport network.
# Creating a Megaport Object Storage Connection
Source: https://docs.megaport.com/storage/object/creating-storage-connection
This help topic describes how to create a Megaport Object Storage connection in the Megaport Portal.
This topic describes how to create a Megaport Object Storage connection from a Port, MCR, MVE, or NAT Gateway in the Megaport Portal.
## Before you begin
Before creating a connection you need:
* Object Storage provisioned in the Latitude.sh Portal.\
For more information, see Latitude.sh Object Storage.
* A Port, MCR, MVE, or NAT Gateway provisioned in the Megaport Portal.\
For more information, see the [Quick Start Guide](/getting-started).
## Creating a Megaport Object Storage connection
You can create a Megaport Object Storage connection from an existing Port, MCR, MVE, or NAT Gateway at any time.
There are two ways to start:
* If this is the first connection for the service, click the **Megaport Object Storage** tile on the service on the Services page.
* Click **+Connection** on any Port, MCR, MVE, or NAT Gateway, then select **Megaport Object Storage**.
**To create a Megaport Object Storage connection**
1. In the Megaport Portal, go to the **Services** page and select the Port, MCR, MVE, or NAT Gateway you want to use.
2. Click the **Megaport Object Storage** tile, or click **+Connection** and select **Megaport Object Storage**.
3. Select the storage location.\
Select the location where you provisioned your storage in the Latitude.sh Portal. Connecting to a different location will not provide access to your buckets.
4. Click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your Megaport Object Storage connection to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. You can adjust this after the connection is created.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service remains active while shut down.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Megaport Object Storage Pricing and Contract Terms](/finance/storage-pricing).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.
7. Specify the connection details for the storage:
* **ASN** -- Specify a private or public ASN. You can also use the default Megaport ASN: 133937.
* **BGP Password** (optional) -- The shared key to authenticate the BGP peer. 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. The shared key length is from 1 to 25 characters. The key can include any of these characters:
* a-z
* A-Z
* 0-9
* Special characters: ! @ # . \$ % ^ & \* + = - \_
Click the eye icon to see the password as you type. The view persists until you click the eye icon again to hide the password.
* **Prefixes** (optional) -- Specify prefixes to announce to Latitude.sh. You can add up to 20 public IPv4 prefixes. Regional Internet Registry (RIR) assigned IPv4 address ranges only, [RFC 1918](https://tools.ietf.org/html/rfc1918) addresses are not allowed. Once configured, you cannot add new prefixes to the VXC.\
If you do not have public IP ranges, leave the field blank and you can source NAT to the /31 IPs provided by Megaport.
8. Click **Next**.
9. If an A-End Connection Details page appears, click **Next**.\
You can configure the A-End connection details after the service is live.
* For more information about configuring the A-End for MCRs, see [Configuring an MCR](/mcr/configuring-mcr).
* For more information about configuring the A-End for NAT Gateways, see [Configuring a NAT Gateway VXC](/nat/configuring-nat-vxc).
10. Confirm the configuration and price, then click **Add VXC**.
11. Click **Review Order**.
12. Click **Order Now** to complete the order.
## After ordering
Megaport will assign a /31 public customer IP address for you to configure on your MCR, MVE, or network device attached to a Port.
Use the endpoint URL and access credentials from the Latitude.sh Portal to connect to your storage using S3-compatible tools.
For more information, see the Latitude.sh Object Storage documentation.
## Helpful references
* [Connecting to Latitude.sh](/portal-admin/connect-latitude)
* [Creating a Megaport Object Storage Connection with the API](/api/api-storage)
* [Megaport Object Storage Billing](/finance/storage-billing)
* [Megaport Object Storage Overview](/storage/object)
* [Megaport Object Storage Pricing and Contract Terms](/finance/storage-pricing)
* [Terminating a Megaport Object Storage Connection](/storage/object/terminating-connection)
# Megaport Object Storage Overview
Source: https://docs.megaport.com/storage/object/index
This help topic describes Megaport Object Storage, a VXC connection to S3-compatible object storage provisioned on Latitude.sh.
Megaport Object Storage is S3-compatible object storage provisioned on Latitude.sh and connected to the Megaport network through a dedicated Virtual Cross Connect (VXC). You provision and manage storage, including buckets, access credentials, and storage usage, in the Latitude.sh Portal. You create and manage the dedicated network connection in the Megaport Portal.
To set up Megaport Object Storage, complete these steps:
1. Log in to the Latitude.sh Portal using your Megaport account.
2. Verify your Latitude.sh account.\
For more information, see Verifying Your Account.
3. Provision object storage in the Latitude.sh Portal.
4. Log in to the Megaport Portal and [create a Megaport Object Storage connection](/storage/object/creating-storage-connection).
5. Access your storage with the endpoint and credentials from the Latitude.sh Portal using any S3-compatible tool.
For more information about provisioning and using storage, see the Latitude.sh Object Storage documentation.
Megaport Object Storage requires you to use two portals. You provision and manage object storage in the Latitude.sh Portal. You create and manage the dedicated network connection in the Megaport Portal, as described in this documentation.
You need both the Latitude.sh Object Storage and Megaport Object Storage connection before you can access your storage over the Megaport network. Before provisioning storage, log in to the Latitude.sh Portal with your Megaport Portal credentials and verify your account.\
For more information, see [Connecting to Latitude.sh](/portal-admin/connect-latitude).
## How it works
Megaport provides dedicated VXC connectivity between your existing service (Port, MCR, MVE, or NAT Gateway) and your object storage. Latitude.sh manages storage provisioning, bucket management, and access credentials.
You can also access your storage over the public internet using the endpoint and credentials from the Latitude.sh Portal. When required, the connection will be routed over the public internet as a failsafe to ensure connectivity to your storage.
## Features and benefits
Using a Megaport Object Storage connection can benefit users and organizations in the following ways:
* **Dedicated network connectivity** -- The Megaport Object Storage connection routes traffic over the Megaport network rather than the public internet, providing consistent and predictable data transfer to your object storage.
* **Works with existing services** -- Connect to your object storage from a Port, MCR, MVE, or NAT Gateway already provisioned on the Megaport network without additional infrastructure.
* **Scalable bandwidth** -- Adjust the connection rate limit at any time to match your workload requirements.
* **Flexible contract terms** -- Choose from no minimum term through to multi-year contracts. Discounts are available for longer terms.
* **BGP support** -- Announce public IP prefixes to Latitude.sh over the connection for customers that need routing control from their own address space.
* **Built-in resilience** -- If the dedicated connection is unavailable, traffic fails over to the public internet to maintain access to your object storage. When traffic fails over to the public internet, the benefits of the dedicated connection do not apply.
## Megaport Object Storage use cases
Megaport Object Storage is available in two tiers to suit different workload requirements:
* **Standard Object Storage** -- Best for backup and disaster recovery storage, long-term retention, and general-purpose storage where cost efficiency and scalability matter more than peak performance.
* **High-performance Object Storage** -- Best for data lakes, analytics pipelines, and active datasets that require high throughput and consistent low-latency object storage.
## Megaport Object Storage connection terms
These contract terms apply only to the Megaport Object Storage connection. Use the Latitude.sh Portal to manage storage consumption and billing separately. For more information about storage consumption billing, see Latitude.sh Billing.
You can specify an optional term for your connection. The choices are:
* No Minimum Term
* 12 months (this is the default)
* 24 months
* 36 months
* 48 months
* 60 months
Discounts are applied depending on the term duration. For more information, see [Megaport Object Storage Pricing and Contract Terms](/finance/storage-pricing).
## Move or shut down the connection
After a Megaport Object Storage connection is created, it can be managed like any other VXC. You can move a Megaport Object Storage connection between services of the same type. You can also shut it down temporarily for failover testing or maintenance.\
For more information, see [Moving VXCs](/connections/move-vxc) and [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
## Helpful references
* [Connecting to Latitude.sh](/portal-admin/connect-latitude)
* [Creating a Megaport Object Storage Connection](/storage/object/creating-storage-connection)
* Latitude.sh Object Storage documentation
* [Megaport Object Storage Billing](/finance/storage-billing)
* [Megaport Object Storage Pricing and Contract Terms](/finance/storage-pricing)
* [Terminating a Megaport Object Storage Connection](/storage/object/terminating-connection)
# Terminating a Megaport Object Storage Connection
Source: https://docs.megaport.com/storage/object/terminating-connection
This help topic describes how to terminate a Megaport Object Storage connection in the Megaport Portal.
You can terminate a Megaport Object Storage connection directly from the Megaport Portal.
Megaport Object Storage connections can be individually terminated or are automatically terminated as part of terminating the attached Port, MCR, MVE, or NAT Gateway.
Terminating a Megaport Object Storage connection in the Megaport Portal only removes the dedicated network connection to the storage on Latitude.sh. To delete your storage allocation, use the Latitude.sh Portal.
Terminating a Megaport Object Storage connection on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about Megaport Object Storage contract terms, see [Megaport Object Storage Pricing and Contract Terms](/finance/storage-pricing). You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees (ETF Management)](/finance/etf-management).
**To terminate a Megaport Object Storage connection**
1. In the Megaport Portal, go to the **Services** page.
2. Click the trash icon next to the Megaport Object Storage connection you want to terminate.
The **Terminate Services** window appears. Early termination fees are shown here, if applicable.
3. In the **Cancellation Reason** drop-down list, select the reason you are terminating the connection.
These options are available:
* Moving to a Cloud-Native Solution
* Changing Data Centers
* Ordered in Error or Reordering
* Proof of Concept / Test
* Project Ended
* Switching to Alternative Provider
* Pricing
* Product Performance
* Reason not Listed
- **Ordered in Error or Reordering** should be selected if you have upgraded or downgraded the service speed and re-ordered.
- **Reason not Listed** should be selected to specify a different reason to those listed. Use the free text field to explain the reason for terminating the service. This field has a maximum of 400 characters.
- You can also provide additional details in the free text field for any of the cancellation reasons.
4. Click **Yes, Terminate Service** to confirm, or click **No, Keep Services** to cancel.\
The Megaport Object Storage connection is removed from the Megaport network.
# Azure Service Key API Response Fields
Source: https://docs.megaport.com/api/api-azure-servicekey
This help topic shows the response to an Azure service key lookup request and describes the response fields.
This topic shows the response to an Azure service key lookup request and describes the response fields.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/secure/azure/{service_key}
```
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Successful lookup",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"managed": true,
"connectType": "AZURE",
"resource_type": "csp_connection",
"bandwidth": 200,
"service_key": "3e2480b2-b4d5-424b-976a-7b0de65a1b62",
"vlan": 3289,
"megaports": [
{
"portSpeed": 10000,
"name": "Washington DC Primary",
"state": "VA",
"description": "Azure ExpressRoute at Equinix DC2/6",
"productUid": "a7ae8a35-433e-44aa-87cb-a1b7995ab008",
"nServiceId": 32832,
"companyUid": "c40de5ed-4707-4471-a78c-69436de2c505",
"country": "USA",
"vxc": 60574,
"port": 14570,
"companyName": "Azure ExpressRoute",
"locationId": 67,
"productId": 14570,
"type": "primary",
"companyId": 1475
},
{
"portSpeed": 10000,
"name": "Washington DC Secondary",
"state": "VA",
"description": "Azure ExpressRoute at Equinix DC2/6",
"productUid": "07ab0ee6-7f77-41ac-bbe6-335e3ee6d182",
"nServiceId": 36431,
"companyUid": "c40de5ed-4707-4471-a78c-69436de2c505",
"country": "USA",
"vxc": 60575,
"port": 16108,
"companyName": "Azure ExpressRoute",
"locationId": 67,
"productId": 16108,
"type": "secondary",
"companyId": 1475
}
],
"peers": [
{
"peer_asn": 133937,
"shared_key": null,
"primary_subnet": "169.254.167.176/30",
"secondary_subnet": "169.254.167.180/30",
"vlan": 100,
"type": "private"
},
{
"peer_asn": 133937,
"shared_key": null,
"prefixes": "117.18.81.116/30,117.18.81.120/30",
"primary_subnet": "117.18.81.116/30",
"secondary_subnet": "117.18.81.120/30",
"vlan": 200,
"type": "microsoft"
}
]
}
}
```
These tables describe each field in the response.
| **Parameter** | **Description** | **Values** |
| - | - | - |
| managed | Indicates if Megaport manages the peer information | true/false |
| connectType | | AZURE |
| resource\_type | | csp\_connection |
| bandwidth | The bandwidth set on the ExpressRoute configuration in the Azure portal | • 50 Mbps • 100 Mbps • 200 Mbps • 500 Mbps • 1 Gbps • 2 Gbps • 5 Gbps • 10 Gbps For more information, see the Microsoft help topic with [bandwidth options](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-introduction). |
| service\_key | The ID for the service key | UUID |
| vlan | | VLAN ID |
| megaports | Array of Megaport details, including attached VXCs. The array contains information for both a primary and secondary port. | For more information, see the **Ports** table (next). |
| peers | Array of peer information, with maximum of two: private and microsoft. If peers are not configured, they will not be present. | For more information, see the **Peers** table (below). |
### Ports
| **Parameter** | **Description** |
| - | - |
| portSpeed | Speed of the Port: 1000, 10000, or 100000 Mbps |
| name | Name of the Port |
| state | Location of the Port (State) |
| description | Description of the Port |
| productUid | Port UUID - used for ordering |
| nServiceId | Used by Megaport |
| companyUid | Used by Megaport |
| country | Location of the Port (Country) |
| vxc | Numeric ID of VXC associated with this key/Port combination. Null if a VXC is not configured |
| port | Numeric ID of the Port |
| companyName | Name of company that owns the Port |
| locationId | The ID of the location of this Port |
| productId | Same as the Port |
| companyId | Numeric ID of the company |
### Peers
For a Port, you configure peering through the Azure portal. When configured, the peering details appear in the response.
For an MCR, you can set the peering type through the API and Megaport automatically configures the BGP details.
When configured, these peering details appear in the service key validation response.
| **Parameter** | **Description** | **Values** |
| - | - | - |
| peer\_asn | The ASN of the peer | Valid ASN (do not use 65515) |
| shared\_key | Shared BGP key | Null or up to 25 alphanumeric characters |
| prefixes | IP address prefixes | Comma separated list of public IP address prefixes associated with the primary and secondary subnets - only present for Microsoft peering. |
| primary\_subnet | Primary IP subnet associated with this peer type. | IP prefix |
| secondary\_subnet | Secondary IP subnet associated with this peer type. | IP prefix |
| vlan | Inner VLAN associated with this peer type | int |
| type | Peering type | microsoft or private |
# Creating a Service Key with the API
Source: https://docs.megaport.com/api/api-create-servicekey
This help topic describes how to create a service key using APIs.
This topic describes the API procedure to create a service key, including how to get the Port ID (productUid) and create a VXC with a service key.
For an overview of service keys, see [Setting up Service Keys](/marketplace/service-keys) and [Managing service keys](/deployment/csp-integration#managing-service-keys). For more information about service key APIs, see [Service Keys (API Documentation)](https://dev.megaport.com/#eb681bb1-1149-4d24-bcc5-b3ac88791022).
## Prerequisites
Before you create a , ensure that you have:
* Access to the Megaport Portal.
* A Port, MCR, MVE, or NAT Gateway on the Megaport network.
- A valid access token. For more information, see [Creating an API Key](/api/api-key).
**To get the productUid for the Port**
1. In Postman, click **Product Details** in the left navigation and select **GET Product List**.
2. Click **Send**.
3. From the returned product details, locate the `productUid` value for the Port for which you want to create the service key.
This example uses the following Port:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"productName": "CoreSite LA1" in "city": "Los Angeles"
with "productUid": "8611b645-ea50-46eb-b400-1c2fb858a303"
```
## Creating a service key
After locating the `productUid` value for the product for which you want to create the service key, you can use the Megaport API to create the service key.
**To create a service key**
1. In Postman, click **Connections** in the left navigation and select **Service Keys > POST Generate Service Key**.
2. Copy the `productUid` of your on-ramp (Port) and update the Body.
For this example, the value of the `productUid` of the Port is `8611b645-ea50-46eb-b400-1c2fb858a303`.
```json {2} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"productUid": "8611b645-ea50-46eb-b400-1c2fb858a303",
"description": "Documentation Service Key - Single Use",
"active": true,
"singleUse": true,
"maxSpeed": "500",
"preApproved": true,
"vlan": 3,
"validFor": {
"start": 1608506197135,
"end": 1612015200000
}
}
```
3. Specify additional parameters in the Body, for example, rate limit (`maxSpeed`), how long the key will be valid (`validFor`), and if you need a single-use key (`"singleUse": true`) or multi-use key (`"singleUse": false`). The dates are entered in UNIX timestamp date format. You can use tools such as
[https://www.epochconverter.com/](https://www.epochconverter.com/) or [https://it-tools.tech/date-converter](https://it-tools.tech/date-converter) to determine the correct value to enter.
For single-use keys only, specify a VLAN ID (`vlan`) or set `vlan` to `-1` to create an untagged VXC.
You can create a single-use untagged service key only if no untagged connections already exist on the relevant MVE vNIC or Port.
This is the VLAN ID for the B-End. If you have specified a VLAN ID, Megaport checks that the requested VLAN ID is available. When a customer uses this service key to create a connection to your Port, they can specify a VLAN ID for the A-End.
For more information about VLAN IDs, see [Managing VLAN IDs](/deployment/csp-integration#managing-vlans).
4. When you are done, click **Send** to make the request.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST /v2/service/key
```
A successful response passes validation and has a 200 OK status.
```json {5} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "New service key [106e38ae-eb59-415f-ac81-526a5299851d] generated",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"key": "106e38ae-eb59-415f-ac81-526a5299851d",
"createDate": 1712277262872,
"companyId": 1153,
"companyUid": "160208ae-01e4-4cb9-8d57-03a197bd47a8",
"companyName": "Megaport Lab",
"description": "Documentation Service Key - Single Use",
"productId": 193076,
"productUid": "8611b645-ea50-46eb-b400-1c2fb858a303",
"productName": "My new Port",
"vlan": 3,
"maxSpeed": 500,
"preApproved": true,
"singleUse": true,
"lastUsed": null,
"active": true,
"validFor": {
"start": 1608506197135,
"end": 1612015200000
},
"expired": true,
"valid": false,
"promoCode": null,
"productDto": {
"productUid": "8611b645-ea50-46eb-b400-1c2fb858a303",
"productName": "My new Port",
"portSpeed": 1000,
"locationId": 60,
"vxcPermitted": true,
"companyUid": "160208ae-01e4-4cb9-8d57-03a197bd47a8",
"companyName": "Megaport Lab",
"connectType": "DEFAULT",
"productId": 193076,
"productType": "MEGAPORT",
"provisioningStatus": "LIVE",
"createDate": 1712268634020,
"createdBy": "0b367492-186d-47ab-96e0-34ca03d29dcd",
"terminateDate": null,
"liveDate": 1712268694790,
"market": "US",
"costCentre": "Optional finance reference",
"usageAlgorithm": "NOT_POST_PAID",
"marketplaceVisibility": false,
"secondaryName": null,
"lagPrimary": false,
"lagId": null,
"aggregationId": null,
"contractStartDate": 1712268694807,
"contractEndDate": 1714831200000,
"contractTermMonths": 1,
"associatedVxcs": [],
"associatedIxs": [],
"attributeTags": {},
"virtual": false,
"buyoutPort": false,
"locked": false,
"adminLocked": false,
"diversityZone": null,
"nserviceId": 521477,
"cancelable": true
}
}
}
```
The new service key now appears in the Megaport Portal.
## Editing or disabling the key
You can edit the details of a service key or permanently disable it.
There might be several reasons why you would want to disable the key. For example, you create a service key to one of your Ports and share it with your customer but before your customer creates a connection with the service key, the Port becomes unavailable and you want to prevent your customer from using that service key.
**To edit or disable the service key**
1. In Postman, open the **Connections** folder in the left navigation and select **Service Keys > PUT Update Service Key**.
2. Edit the details of the service key as required.
3. To permanently disable the service key, set the `active` parameter to `false`.
## Sharing the key
You can share the service key however you prefer, such as email or messaging.
The recipient of the service key cannot alter or modify the service key parameters.
## Creating a VXC with a service key
After you receive a service key, you can create a VXC with the service key to connect the A-End on-ramp defined in the service key and your B-End on-ramp.
**To create a VXC with a service key**
1. In Postman, open the **Connections** folder in the left navigation and select **Service Keys > POST Create VXC with a Service Key**.
2. Specify the configuration details in the Body of the request.
* `productUid` - Enter the `productUid` of the Port in your Megaport location.
* `bEnd: productUid` - Enter the `productUid` location from the service key lookup.
* `serviceKey`- Enter the full service key.
* `ratelimit` - Specify a `ratelimit` up to the maximum rate limit set on the service key.
* `term` - Specify the contract term for the VXC. Valid values are 1, 12, 24, 36, 48, and 60 months. If you don't specify `term` when ordering a VXC, it defaults to 1 (No Minimum Term).
* `shutdown` - You can temporarily shut down and re-enable the VXC. Valid values are `true` (shut down) and `false` (enabled). If not provided, it defaults to `false` (enabled).
* `promoCode` - You can enter a promotional code for the service order. The code is not validated, so if the code doesn’t exist or doesn’t work for the service, the call will still be successful.
* `vlan` (optional) - Preferred A-End VLAN. Specify an unused VLAN ID for this connection.
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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don’t specify a value, Megaport will assign one.
The B-End VLAN for the provider side termination will be automatically populated based on the service key.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"productUid": "7fba50bb-ac35-465b-9b8b-9a6d7335ec7a",
"associatedVxcs": [
{
"productName": "VXC from service key",
"rateLimit": 100,
"term": 12,
"shutdown": false,
"promoCode": "promox3mnthfree2",
"serviceKey": "106e38ae-eb59-415f-ac81-526a5299851d",
"aEnd": {
"vlan": 2
},
"bEnd": {
"productUid": "8611b645-ea50-46eb-b400-1c2fb858a303"
}
}
]
}
```
3. When you are done, click **Send** to make the request.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST /v3/networkdesign/buy
```
To test your request before you order and see pricing details, use the `/v3/networkdesign/validate` endpoint with the same Body configuration.
A successful response passes validation and has a 200 OK status.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "VXC [399f0fd8-8a69-4e15-abdb-537b0cb8a858] created. ",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"createDate": 1610140443499,
"vxcOrderId": 55791,
"payerMegaPortId": 74841,
"nonPayerMegaPortId": 39950,
"payerMegaPortName": "My LA API Port",
"nonPayerMegaPortName": "BNE5-01-10G",
"payerCompanyId": 15,
"nonPayerCompanyId": 28,
"payerLocationId": 60,
"nonPayerLocationId": 44,
"salesId": null,
"payerCompanyName": "Megaport Lab",
"nonPayerCompanyName": "6YS",
"payerMegaPortNsId": 167551,
"nonPayerMegaPortNsId": 90147,
"payerVlanId": 2,
"nonPayerVlanId": 373,
"payerInnerVlanId": null,
"nonPayerInnerVlanId": null,
"payerApproverName": "Test Name",
"payerApproverId": 32278,
"nonPayerApproverName": null,
"nonPayerApproverId": null,
"payerApproval": 1610140443263,
"nonPayerApproval": 1610140443308,
"fixedTerm": true,
"duration": 1,
"rollover": true,
"serviceName": "from My LA API Port to BNE5-01-10G",
"payerStatus": "APPROVED",
"nonPayerStatus": "APPROVED",
"speed": 100,
"distanceBand": "ZONE",
"intercapPath": "",
"awsId": null,
"promoCode": null,
"rateType": "MONTHLY",
"vxcJTechnicalServiceId": 74842,
"vxcJTechnicalServiceUid": "399f0fd8-8a69-4e15-abdb-537b0cb8a858",
"provisionDate": 1610140443232,
"orderType": "NEW",
"monthlyDiscountAmount": null,
"discountMonths": null,
"amazonDirectConnectConfigDto": null,
"amsixConnectConfigDto": null,
"webAirProvItem": null,
"sdrcProvItem": null,
"rate": null,
"setup": null,
"asn": null,
"bgpPassword": null,
"usageAlgorithm": "POST_PAID_HOURLY_SPEED_LONG_HAUL_VXC",
"costCentre": null,
"azureServiceKey": null,
"oracleVirtualCircuitId": null,
"serviceKey": "106e38ae-eb59-415f-ac81-526a5299851d",
"connectType": "DEFAULT",
"payerConfig": {},
"nonPayerConfig": {},
"attributeTags": {},
"fullyApproved": true
}
]
}
```
After ordering the service key VXC, a notification is sent to the company that you are connecting to, and the receiving company can either accept or reject the key. They cannot alter the key but can request modifications to the service key parameters before accepting it.
The service key VXC will appear in the Megaport Portal for both companies.
# Managing IPFIX Targets with the API
Source: https://docs.megaport.com/api/api-ipfix-targets
This help topic describes how to use the Megaport API to manage IPFIX flow export targets on MCRs and NAT Gateways.
This topic describes the API procedure to manage IPFIX flow export targets on Megaport Cloud Router (MCR) and Megaport NAT Gateway (NAT Gateway) services.
(IP Flow Information Export) is a standard protocol for exporting network flow information to monitoring systems. You can configure IPFIX targets on your MCR or NAT Gateway to send flow records to external collectors for traffic analysis, capacity planning, and security monitoring.
Each MCR or NAT Gateway supports up to three IPFIX targets. Flow records are exported to the configured collector using either UDP or TCP transport.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
## MCR IPFIX target endpoints
### Creating an IPFIX target
To create an IPFIX target on an MCR, send a POST request with the target configuration.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v2/product/mcr2/{productUid}/flowExport
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier (UUID) of the MCR. |
**Request Body**
| Field | Required | Description |
| :- | :- | :- |
| description | Yes | A description of the IPFIX target, up to 100 characters. Must be unique per service. |
| mtu | No | The maximum size, in bytes, of IPFIX export packets sent to this collector, independent of the MCR MTU. Valid range: 512-9074. Set this when a collector rejects oversized packets, for example on a service that uses jumbo frames. When omitted, the export packet size follows the service MTU. |
| protocol | Yes | The transport protocol: `udp` or `tcp`. |
| sourceIpAddress | No | The source IP address on the MCR for the flow export stream. Must be an address configured on the service. The `sourceIpAddress` and `targetIpAddress` must be the same address family (IPv4 or IPv6). |
| targetIpAddress | Yes | The IPv4 or IPv6 address of the flow collector. The `sourceIpAddress` and `targetIpAddress` must be the same address family (IPv4 or IPv6). |
| targetPort | Yes | The port of the flow collector. Valid range: 1-65535. |
**Example Request**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"description": "Primary Collector",
"sourceIpAddress": "10.1.1.1",
"protocol": "udp",
"targetIpAddress": "192.168.0.1",
"targetPort": 2055,
"mtu": 1500
}
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Created a new flow export target for MCR",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"id": 159,
"description": "Primary Collector",
"sourceIpAddress": "10.1.1.1",
"protocol": "udp",
"targetIpAddress": "192.168.0.1",
"targetPort": 2055,
"mtu": 1500
}
}
```
### Getting an IPFIX target
Retrieve a specific IPFIX target by its ID.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/product/mcr2/{productUid}/flowExport/{flowExportId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier (UUID) of the MCR. |
| flowExportId | The unique identifier (integer) of the flow export target. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/product/mcr2/7f5f9574-315e-4527-af44-122605a411de/flowExport/159
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Flow export target details",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"id": 159,
"description": "Primary Collector",
"sourceIpAddress": "10.1.1.1",
"protocol": "udp",
"targetIpAddress": "192.168.0.1",
"targetPort": 2055,
"mtu": 1500
}
}
```
### Updating an IPFIX target
Update an existing IPFIX target configuration.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
PUT {baseUrl}/v2/product/mcr2/{productUid}/flowExport/{flowExportId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier (UUID) of the MCR. |
| flowExportId | The unique identifier (integer) of the flow export target to update. |
**Request Body**
The request body uses the same fields as the create request.
| Field | Required | Description |
| :- | :- | :- |
| description | Yes | A description of the IPFIX target, up to 100 characters. Must be unique per service. |
| mtu | No | The maximum size, in bytes, of IPFIX export packets sent to this collector, independent of the MCR MTU. Valid range: 512-9074. Set this when a collector rejects oversized packets, for example on a service that uses jumbo frames. When omitted, the export packet size follows the service MTU. |
| protocol | Yes | The transport protocol: `udp` or `tcp`. |
| sourceIpAddress | No | The source IP address on the MCR for the flow export stream. Must be an address configured on the service. The `sourceIpAddress` and `targetIpAddress` must be the same address family (IPv4 or IPv6). |
| targetIpAddress | Yes | The IPv4 or IPv6 address of the flow collector. The `sourceIpAddress` and `targetIpAddress` must be the same address family (IPv4 or IPv6). |
| targetPort | Yes | The port of the flow collector. Valid range: 1-65535. |
**Example Request**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"description": "Primary Collector - Updated",
"sourceIpAddress": "10.1.1.2",
"protocol": "tcp",
"targetIpAddress": "192.168.0.2",
"targetPort": 4739,
"mtu": 1500
}
```
### Deleting an IPFIX target
Delete a specific IPFIX target from an MCR.
A target cannot be deleted if it is still assigned to an interface.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
DELETE {baseUrl}/v2/product/mcr2/{productUid}/flowExport/{flowExportId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier (UUID) of the MCR. |
| flowExportId | The unique identifier (integer) of the flow export target to delete. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
DELETE {baseUrl}/v2/product/mcr2/7f5f9574-315e-4527-af44-122605a411de/flowExport/159
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Flow export target '159' deleted successfully",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy"
}
```
### Listing IPFIX targets
Retrieve all IPFIX targets configured on an MCR.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/product/mcr2/{productUid}/flowExports
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier (UUID) of the MCR. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/product/mcr2/7f5f9574-315e-4527-af44-122605a411de/flowExports
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "List flow export targets for MCR",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"id": 159,
"description": "Primary Collector"
},
{
"id": 160,
"description": "Secondary Collector"
}
]
}
```
## NAT Gateway IPFIX target endpoints
### Creating an IPFIX target
To create an IPFIX target on a NAT Gateway, send a POST request with the target configuration.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/products/nat_gateways/{productUid}/flow_exports
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier (UUID) of the NAT Gateway. |
**Request Body**
| Field | Required | Description |
| :- | :- | :- |
| description | Yes | A description of the IPFIX target, up to 100 characters. Must be unique per service. |
| mtu | No | The maximum size, in bytes, of IPFIX export packets sent to this collector, independent of the NAT Gateway MTU. Valid range: 512-9074. Set this when a collector rejects oversized packets, for example on a service that uses jumbo frames. When omitted, the export packet size follows the service MTU. |
| protocol | Yes | The transport protocol: `udp` or `tcp`. |
| sourceIpAddress | No | The source IP address on the NAT Gateway for the flow export stream. Must be an address configured on the service. The `sourceIpAddress` and `targetIpAddress` must be the same address family (IPv4 or IPv6). |
| targetIpAddress | Yes | The IPv4 or IPv6 address of the flow collector. The `sourceIpAddress` and `targetIpAddress` must be the same address family (IPv4 or IPv6). |
| targetPort | Yes | The port of the flow collector. Valid range: 1-65535. |
**Example Request**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"description": "Primary Collector",
"sourceIpAddress": "10.1.1.1",
"protocol": "udp",
"targetIpAddress": "192.168.0.1",
"targetPort": 2055,
"mtu": 1500
}
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Created a new flow export target for NAT Gateway",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"id": 159,
"description": "Primary Collector",
"sourceIpAddress": "10.1.1.1",
"protocol": "udp",
"targetIpAddress": "192.168.0.1",
"targetPort": 2055,
"mtu": 1500
}
}
```
### Getting an IPFIX target
Retrieve a specific IPFIX target by its ID.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/{productUid}/flow_exports/{flowExportId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier (UUID) of the NAT Gateway. |
| flowExportId | The unique identifier (integer) of the flow export target. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/7f5f9574-315e-4527-af44-122605a411ef/flow_exports/159
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Flow export target details",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"id": 159,
"description": "Primary Collector",
"sourceIpAddress": "10.1.1.1",
"protocol": "udp",
"targetIpAddress": "192.168.0.1",
"targetPort": 2055,
"mtu": 1500
}
}
```
### Updating an IPFIX target
Update an existing IPFIX target configuration.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
PUT {baseUrl}/v3/products/nat_gateways/{productUid}/flow_exports/{flowExportId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier (UUID) of the NAT Gateway. |
| flowExportId | The unique identifier (integer) of the flow export target to update. |
**Request Body**
The request body uses the same fields as the create request.
| Field | Required | Description |
| :- | :- | :- |
| description | Yes | A description of the IPFIX target, up to 100 characters. Must be unique per service. |
| mtu | No | The maximum size, in bytes, of IPFIX export packets sent to this collector, independent of the NAT Gateway MTU. Valid range: 512-9074. Set this when a collector rejects oversized packets, for example on a service that uses jumbo frames. When omitted, the export packet size follows the service MTU. |
| protocol | Yes | The transport protocol: `udp` or `tcp`. |
| sourceIpAddress | No | The source IP address on the NAT Gateway for the flow export stream. Must be an address configured on the service. The `sourceIpAddress` and `targetIpAddress` must be the same address family (IPv4 or IPv6). |
| targetIpAddress | Yes | The IPv4 or IPv6 address of the flow collector. The `sourceIpAddress` and `targetIpAddress` must be the same address family (IPv4 or IPv6). |
| targetPort | Yes | The port of the flow collector. Valid range: 1-65535. |
**Example Request**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"description": "Primary Collector - Updated",
"sourceIpAddress": "10.1.1.2",
"protocol": "tcp",
"targetIpAddress": "192.168.0.2",
"targetPort": 4739,
"mtu": 1500
}
```
### Deleting an IPFIX target
Delete a specific IPFIX target from a NAT Gateway.
A target cannot be deleted if it is still assigned to an interface.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
DELETE {baseUrl}/v3/products/nat_gateways/{productUid}/flow_exports/{flowExportId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier (UUID) of the NAT Gateway. |
| flowExportId | The unique identifier (integer) of the flow export target to delete. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
DELETE {baseUrl}/v3/products/nat_gateways/7f5f9574-315e-4527-af44-122605a411ef/flow_exports/159
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Flow export target '159' deleted successfully",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy"
}
```
### Listing IPFIX target summaries
Retrieve summaries of all IPFIX targets configured on a NAT Gateway.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/{productUid}/flow_export_summaries
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier (UUID) of the NAT Gateway. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/7f5f9574-315e-4527-af44-122605a411ef/flow_export_summaries
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "List flow export targets for NAT Gateway",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"id": 159,
"description": "Primary Collector"
},
{
"id": 160,
"description": "Secondary Collector"
}
]
}
```
## Error responses
When a request fails, the API returns an error response with details about the issue.
| HTTP Status | Description |
| :- | :- |
| 400 | Bad request. The request body is invalid or missing required fields. |
| 401 | Unauthorized. The access token is missing or invalid. |
| 403 | Forbidden. You don't have permission to access this resource. |
| 404 | Not found. The specified MCR, NAT Gateway, or IPFIX target doesn't exist. |
| 409 | Conflict. The IPFIX target description is not unique, or the maximum number of targets (3) has been reached. |
## Helpful references
* [Configuring an MCR](/mcr/configuring-mcr)
* [Creating an MCR](/mcr/creating-mcr)
* [Creating a NAT Gateway](/nat/creating-nat-gateway)
* [Megaport API Overview](/api)
# Joining an IX with the API
Source: https://docs.megaport.com/api/api-ix
This help topic describes how to use the Megaport API to join an Internet Exchange (IX).
This topic describes the API procedure to join an Internet Exchange (IX) from a Port.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
## Use cases
Using the API to join an IX allows you to:
* Automate IX provisioning as part of your network deployment workflows.
* Integrate IX ordering into your infrastructure-as-code processes.
* Programmatically manage peering infrastructure across multiple locations.
## Prerequisites
Before joining an IX, ensure that:
* You have an active Port in a location where an IX is available.
* You can meet the [IX requirements](/ix/ix-requirements).
## Steps to join an IX
To join an IX using the API:
1. Get the `productUid` for your Port
2. Find available IX locations
3. Validate the IX order
4. Order the IX
## Getting your Port product ID
To join an IX, you need the `productUid` for the Port.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/products/
```
From the returned product details, locate the `productUid` value for the Port you want to connect from.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"productName": "My API Port",
"productUid": "7f5f9574-315e-4527-af44-122605a411de"
}
```
## Finding available IX locations
To find IX locations where you can connect, query the partner megaports endpoint with the IX connect type.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/dropdowns/partner/megaports
```
**Query Parameters**
| Parameter | Required | Description |
| :- | :- | :- |
| connectType | No | Filter by connection type. Use `IX` for Internet Exchange. |
| vxcPermitted | No | Filter to locations accepting new connections. Use `true`. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/dropdowns/partner/megaports?connectType=IX&vxcPermitted=true
```
**Response**
The response includes available IX locations with their `productUid` and `locationId` values.
```json {3,7} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"connectType": "IX",
"productUid": "f274bd09-1796-43af-8837-28fa4fa2a1ab",
"vxcPermitted": true,
"companyName": "MegaIX Sydney",
"title": "MegaIX Sydney",
"locationId": 3
}
```
## Validating the IX order
Before ordering, validate the IX configuration to review pricing details and confirm the settings are correct.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/validate
```
**Request Body Parameters**
| Parameter | Required | Description |
| :- | :- | :- |
| productUid | Yes | The `productUid` of the Port to connect from. |
| associatedIxs | Yes | An array containing the IX configuration. |
**IX Configuration Parameters**
| Parameter | Required | Description |
| :- | :- | :- |
| productName | Yes | The name of the IX connection. |
| rateLimit | Yes | The speed of the connection in Mbps. Cannot exceed the port speed for metro connections. |
| term | No | Contract term in months. Valid values: 1 (month-to-month), 12, 24, 36, 48, or 60. Default: 12. |
| shutdown | No | Initial state of the connection. `true` shuts down the IX (no traffic flows); `false` enables it. Default: `false`. |
| vlan | No | Preferred VLAN ID (2-4093). If not specified or in use, Megaport assigns one. |
| asn | Yes | Your autonomous system number (ASN). Must be a public 16-bit or 32-bit ASN. |
| macAddress | Yes | The MAC address of the Layer 3 device establishing the BGP session. Format: `XX:XX:XX:XX:XX:XX`. |
| password | No | BGP password (1-25 characters). Allowed characters: a-z, A-Z, 0-9, ! @ # . \$ % ^ & \* + = - \_ |
| publicGraph | No | Whether your traffic graphs are visible to other IX participants. `true` for public; `false` for private. |
| asSet | No | The peer AS-SET (AS macro) for route filtering. If not specified, your ASN is used. |
| bEndProductUid | Yes | The `productUid` of the IX destination from the partner megaports lookup. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/validate
```
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "7f5f9574-315e-4527-af44-122605a411de",
"associatedIxs": [
{
"productName": "My API IX",
"rateLimit": 1000,
"term": 12,
"shutdown": false,
"vlan": 100,
"asn": 136999,
"macAddress": "01:02:0f:04:58:20",
"password": "mybgppassword",
"publicGraph": false,
"asSet": "AS-EXAMPLE",
"bEndProductUid": "f274bd09-1796-43af-8837-28fa4fa2a1ab"
}
]
}
]
```
**Response**
A successful validation returns pricing details and confirms the configuration is valid.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Validation passed",
"data": [
{
"productUid": "7f5f9574-315e-4527-af44-122605a411de",
"associatedIxs": [
{
"productName": "My API IX",
"rateLimit": 1000,
"term": 12,
"monthlyRate": 250.00,
"currency": "USD"
}
]
}
]
}
```
## Ordering the IX
After validation, use the same Request body to order the IX.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
**Example Request**
Copy the validated body and send it to the buy endpoint.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "7f5f9574-315e-4527-af44-122605a411de",
"associatedIxs": [
{
"productName": "My API IX",
"rateLimit": 1000,
"term": 12,
"shutdown": false,
"vlan": 100,
"asn": 136999,
"macAddress": "01:02:0f:04:58:20",
"password": "mybgppassword",
"publicGraph": false,
"asSet": "AS-EXAMPLE",
"bEndProductUid": "f274bd09-1796-43af-8837-28fa4fa2a1ab"
}
]
}
]
```
**Response**
A successful order returns details about the ordered IX, including its `productUid`.
```json {5} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "IX ordered successfully",
"data": [
{
"productUid": "9e8ad9d7-85ab-46f9-ab13-c0966891341b",
"productName": "My API IX",
"provisioningStatus": "DEPLOYABLE"
}
]
}
```
After deployment, Megaport sends an email to your registered email address with additional information on how to finish the BGP configuration.
## Helpful references
* [Changing an IX Configuration with the API](/api/api-ix-change)
* [IX Requirements](/ix/ix-requirements)
* [Joining an IX](/ix/joining-an-ix)
* [Moving a VXC and IX with the API](/api/api-vxc-move)
* [Shutting Down a VXC and IX with the API](/api/api-vxc-shut-down)
# Changing an IX Configuration with the API
Source: https://docs.megaport.com/api/api-ix-change
This help topic describes how to use the Megaport API to change the configured details of an IX.
This topic describes how to change configuration details of an existing IX. For more information, see [PUT Update IX](https://dev.megaport.com/#6ae89dd9-e4bd-4fb5-8533-f8a4a0d02385) in the API reference.
You can change the IX service name, rate limit, cost center, contract term, VLAN ID, MAC address, ASN, BGP password, whether your IX traffic graphs are public or private, reverse DNS, A-End productUid (for moving an IX), and whether to shut down or re-enable an IX, by updating any of these parameters in the Body of the request:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"name": "My updated API created IX",
"rateLimit": 500,
"costCentre": "My Port Account",
"term": 12,
"vlan": 1650,
"macAddress": "01:02:0f:04:58:20",
"asn": 136999,
"password": "gbixpassword",
"publicGraph": false,
"reverseDns": "as6533.charlotte.com",
"aEndProductUid": "9e8ad9d7-85ab-46f9-ab13-c0966891341b",
"shutdown": true
}
```
If the IX is on a contract term, there are restrictions on speed changes. You can increase the speed above the committed term speed or reduce it to the committed term speed, but you cannot reduce it below the committed term speed. Attempting to reduce the speed below the committed term speed will result in a `409 Conflict` error. For more information, see [Changing the Speed of a Termed IX](/ix/ix-termed-rate-change).
For details on moving an IX, see [Moving a VXC and IX with the API](/api/api-vxc-move).
For details on shutting down an IX, see [Shutting Down a VXC and IX with the API](/api/api-vxc-shut-down).
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
**To change the IX details in the Postman collection**
1. In Postman, expand **Internet Exchange (IX)** in the left navigation and click **PUT Update IX**.
2. Identify the IX to update by adding the `productUid` to the endpoint.
3. Select the **Body** tab and update IX details for name, rate limit, VLAN ID, BGP password, and so on. You only need to include the values you want to change.\
This example changes the following values.
4. Click **Send**.\
The changes will be reflected in the Portal within two minutes.
# Creating an API Key
Source: https://docs.megaport.com/api/api-key
This help topic describes how to create an API key for authenticating Megaport Portal users.
Megaport API calls require an access token that you can generate after creating an API key. An access token is required for authenticating API users, and allows temporary access to only the parts of the Megaport Portal that are required.
We recommend using a dedicated, machine to machine (M2M), Company Admin account for accessing the Megaport API and creating API keys. In the event that a human user is deactivated or locked out of their account, the API keys created by that user will also be suspended, which might stop any API integrations from working.
API keys are valid only in the environment in which they were generated. If you need API keys to access a different environment, log in to the Megaport Portal in that environment and generate the API keys there.
You must be logged in to the Megaport Portal as a Company Admin to create an API key. For more information, see [Managing User Roles](/portal-admin/user-management/roles).
This topic describes the following tasks:
* To create an API key in the Megaport Portal
* To generate an access token in Postman
**To create an API key in the Megaport Portal**
1. In the Megaport Portal, choose Tools > API Key Generator.\
The API Keys screen allows you to create API keys, and to view and edit existing API keys.
2. Specify the details for the API key.
* **Name** -- Enter a name for the API key.\
This should be a descriptive name to identify the purpose of the key.
* A minimum of three characters is required for the API key name.
* No special characters are allowed except for dash and hyphen.
* **Role** -- Select the role of the user who will be using the API.\
The following options are available:
* Read Only
* Company Admin
* Technical Admin
* Technical Contact
* Finance
* Financial Contact
For more information about what each role can do, see [Managing User Roles](/portal-admin/user-management/roles).
* **Token Expiry (Minutes)** -- Enter the amount of time (in minutes) after which the token generated from this key will expire. The minimum is 5 minutes and the maximum is 24 hours (1440 minutes). After the token expires, you need to generate a new access token.
3. Click **Generate Key**.\
The API key is created and the Your API Key prompt appears.
Copy your new API Key and API Key Secret, and store these credentials somewhere secure. You will need to use them to generate access tokens. Make sure you copy the API Key Secret because it won't be shown again after you close this prompt.
4. Click **Copy** to the right of the **API Key** field and paste the key (Client Id) in a safe place.
5. Click **Copy** to the right of the **API Key Secret** field and paste the Client secret in a safe place.
6. Click **Close**.\
The API key is created and displayed in the Active API Keys area of the screen.\
In the Active API Keys area, you can edit the name of the key, delete the key, and view the history of changes that have occurred for the key.
## Generating an access token
After you have created the API key, consisting of a client ID and client secret, you can generate an access token for authenticating API users. These instructions describe how you can do this using Postman and the Megaport collection. For Postman setup details, see [Megaport API](/api).
The request URL that you need to use depends on the environment in which you are generating an access token. In each environment, these request URLs should be used:
* **Production environment** -- `https://auth-m2m.megaport.com/oauth2/token`
* **Staging (test) environment** -- `https://auth-m2m-staging.megaport.com/oauth2/token`
These instructions describe how to generate an access token in the Production environment.
For more information, see [Megaport API](/api) and [Megaport Authentication - API Keys](https://dev.megaport.com/#82876b33-a332-4b5d-8bf2-cef672f104b5).
Which API endpoints an access token can call depends on the role selected for the API key when it was created. For example, Read Only API keys will have more restrictions on the data that can be accessed than Company Admin API keys.
**To generate an access token in Postman**
1. In the imported Megaport collection in Postman, click the plus icon to add a new request.
2. In the drop-down list to the left of the **Request URL** field, select POST.
3. In the **Request URL** field, enter the following request URL:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
https://auth-m2m.megaport.com/oauth2/token
```
4. Select the **Authorization** tab and enter the following parameter details:
* **Username** -- The client ID that you copied earlier when creating the API key.
* **Password** -- The client secret that you copied earlier when creating the API key.
These parameters contain sensitive data. If you are working in a collaborative environment, you might want to set the client ID and client secret as the variables `{ apiKeyClientId }` and `{ apiKeyClientSecret }` respectively. For more information about variables, see the Postman documentation.
5. Select the **Body** tab and enter a key called *grant\_type* which is set to a value of *client\_credentials*.
6. Click **Save**.\
The Save Request screen appears.
7. In the **Request name** field, enter a meaningful name for the new request.\
For example, Generate Access Token.
8. (Optional) Enter a description of the request.
9. Select where you would like to save the request then click **Save**.\
The new request is created and added to the Megaport API Documentation collection.
10. Click **Send**.
You should receive a response that includes your access token, similar to the example below. Once an access token is generated, it can be used to authenticate API users for various endpoints in the Megaport Portal.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"access_token":
"eyJraWQ......2cOQGA",
"expires_in": 86400,
"token_type": "Bearer"
}
```
11. Copy the access token.
12. In the variables for the collection (click the three dots after the imported Megaport collection > Edit > Variables), add an entry for *access\_token* and paste the access token into the **CURRENT VALUE** field.
13. For each API call that you need to send, in the **Authorization** tab, the *Type* should be set to Bearer Token and the *Token* should be set to the access token variable `{ access_token }`.
The API call is now ready to use.
All API calls are made over SSL/TLS, and every call is validated against the access token for appropriate permissions.
Access tokens will expire so you need to regularly generate new tokens for your API calls. The expiry period is determined by the value that was entered for the **Token Expiry (Minutes)** field when the API key was created. The default expiry period is 24 hours.
API requests include two important header parameters: Authorization and Content-Type. The Authorization parameter points to the Authorization tab where the token variable is set.
## cURL token generation
Another way to generate an access token is using cURL from a command console in the following format:
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
curl -X "POST" "https://auth-m2m.megaport.com/oauth2/token" \
-H 'Content-Type: application/x-www-form-urlencoded' \
-u ':' \
--data-urlencode "grant_type=client_credentials"
```
The [dev.megaport.com](https://dev.megaport.com) site lets you see each API endpoint in multiple programming languages.
# Managing Users with the API
Source: https://docs.megaport.com/api/api-managing-users
This help topic describes how to manage users with the API.
This topic provides an overview of managing user accounts using the Megaport API. It describes how to invite new users, update user details, deactivate users, and delete invited users.
If your organization uses an Identity Provider (IdP), Megaport recommends setting up Single Sign-On (SSO) with Security Assertion Markup Language (SAML) to centrally manage users.
SSO offers these advantages:
* **Automatic user management** -- Disabling a user in your IdP automatically revokes their Megaport access.
* **Reduced manual work** -- No need to manually deactivate users through the API.
* **Improved security** -- You can configure a whitelist of IP addresses or domains to restrict access, providing centralized control over user access and reducing the risk of unauthorized access.
For more information, see [Setting up Single Sign-On](/setting-up/enforcing-sso).
The following procedures are intended for environments where SSO integration is not in use.
## Invite new users
A Company Admin can create new user accounts by inviting users to an existing company using the `/v2/employment` endpoint.
The email address must be unique and cannot be from a free email domain (such as Gmail, Yahoo, or Outlook). If an invalid email domain is used, the API will return a `400 Bad Request` error.
For more information, see [Invite (Add) a New User to an Existing Company](https://dev.megaport.com#870aded3-cee3-4338-8d8b-0bdb6e144d81).
## View user details
You can view the details of a specific user, such as position, name, email address, phone number, username, whether the user is active or not, Megaport user role, and Megaport permissions using the `v2/employee/:employeeId` endpoint.
For more information, see [Show User Details](https://dev.megaport.com/#ff4a7c6a-6bc7-4f9b-a417-4a3afddf7c05).
## Update user details
You can update user details, such as name, phone number, and roles using the `/v2/employee/:employeeId` endpoint.
Additionally, you can deactivate users by setting the `active` parameter to `false`.
* You cannot permanently delete users who have once logged in. Instead, you must deactivate them to revoke their access while retaining their information in the system.
* Only invited users who have not yet accepted the invitation can be deleted.
For more information, see [Update User Details](https://dev.megaport.com/#b951a109-b283-4da1-a1eb-5338d0b2699a).
## Delete invited users
You can delete users who have been invited to your company but have not yet logged in by using the `/v2/employee/:employeeId` endpoint. This is useful if the wrong user was invited or there was an error in the email address provided. Since the email address of a user cannot be modified once created, you can delete the user and then recreate the account with the correct details.
* You cannot permanently delete users who have logged in. Instead, you must deactivate them to revoke their access while retaining their information in the system. To deactivate a user, set the `active` parameter to `false` using the `/v2/employee/:employeeId` endpoint.
* Only invited users who have not yet accepted the invitation can be deleted.
For more information, see [Delete Invited User](https://dev.megaport.com/#9b9f90ef-3d5b-4c03-8d85-156d1bca09f6).
## List all company users
You can create a list of all users associated with your company, including their details and statuses, using the `/v2/employment` endpoint.
For large user lists, you can retrieve the results in pages then sort and filter them. If you do not supply any of the `pageNumber`, `pageSize`, `sort`, or `filter` query parameters, the endpoint returns the complete, unpaginated list of users. Supplying any of these parameters returns a single page of results, along with `Pagination-*` response headers that give the total number of matching users and total number of pages. You can sort by `firstName`, `lastName`, or `email`, and filter by a case-insensitive partial match against a user's first name, last name, or email address.
For more information, see [List Company Users](https://dev.megaport.com/#c6db60b5-686a-4dac-9d6e-68307622f56a).
## View user activity
Access logs and activity details to track user actions in the Portal. This feature helps monitor and audit user behavior.
For more information, see [User Activity](https://dev.megaport.com/#c1ec70f7-a5bc-4550-b7ec-7ce392e69800).
## Reset Multi-Factor Authentication (MFA)
If a user encounters issues with MFA or wants to enroll a new mobile device, you can reset MFA using the `/v2/employee/:employeeId/mfa` endpoint.
For more information, see [Reset Person Multi-Factor Authentication](https://dev.megaport.com/#5a78f67f-5ea4-45f8-b72d-e2b0be065bf8).
# Managing Megaport Marketplace Forms with the API
Source: https://docs.megaport.com/api/api-marketplace-forms
This help topic describes how to use the Megaport API to create and manage Megaport Marketplace forms for collecting customer information during connection requests.
This topic describes how to use the Megaport API to create and manage Megaport Marketplace forms.
Service providers use these forms to collect onboarding information from customers during connection requests and integrate customer-provided information into provisioning workflows. This helps automate onboarding, accelerate approvals, and reduce manual communication. For more information, see [Megaport Marketplace Forms](/marketplace/forms).
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
You must be a Company Admin to create and manage forms via the API.
## Use cases
These API endpoints help service providers automate form management for their Megaport Marketplace services.
Common use cases include:
* Creating custom forms to collect specific onboarding information from customers.
* Linking forms to services so customers can complete them when requesting connections.
* Retrieving submitted form data for processing connection requests.
* Integrating form data into your provisioning workflows.
## Prerequisites
* You must have a Megaport Marketplace profile. For more information, see [Creating a Megaport Marketplace Profile](/marketplace/profile).
* You must be a Company Admin to create and manage forms.
## Managing form definitions
Form definitions define the structure and fields of forms that customers complete. Each form can contain multiple fields of different types.
### Supported field types
Form field structure and validation are defined in JSON. These field types are supported in form definitions:
| Type | Format | Description |
| :- | :- | :- |
| string | | A text field for short answers. |
| string | format: "email" | A field for entering a contact email address. |
| string | multiline: true | A text area for longer or more detailed responses. |
| string | enum: \[...] | A drop-down field for selecting a single option from a list. You must define at least 2 options, with a maximum of 100 options per field. |
| integer | | A whole number value. |
| number | | A numeric value (integer or decimal). |
| boolean | | A true/false value, typically rendered as a check box. |
| array | | A list of values. |
| object | | A nested group of fields. |
An example for adding an email:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"type": "object",
"properties": {
"email": {
"type": "string",
"format": "email"
}
}
}
```
and an example for adding a drop-down field:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"type": "object",
"properties": {
"status": {
"type": "string",
"enum": [
"active",
"inactive",
"pending"
]
}
}
}
```
### Creating a form
To create a new form definition, send a POST request to the forms endpoint with the form structure. After the form is created, it is set to the *Active* status by default and can be linked to your services.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/marketplace/forms
```
**Request Body**
| Field | Required | Description |
| :- | :- | :- |
| name | Yes | The name of the form. |
| formStructure | Yes | A JSON object that defines the form fields and validation rules. |
**Example Request**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"name": "Customer Onboarding Form",
"formStructure": {
"type": "object",
"properties": {
"companyName": {
"type": "string",
"title": "Company Name"
},
"contactEmail": {
"type": "string",
"format": "email",
"title": "Contact Email"
},
"serviceType": {
"type": "string",
"title": "Service Type",
"enum": ["Standard", "Premium", "Enterprise"]
},
"additionalNotes": {
"type": "string",
"title": "Additional Notes",
"multiline": true
}
},
"required": ["companyName", "contactEmail", "serviceType"]
}
}
```
**Example Response**
A successful request returns the created form definition with its unique identifier.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Form created",
"data": {
"formUid": "abc12345-6789-0def-ghij-klmnopqrstuv",
"name": "Customer Onboarding Form",
"status": "ACTIVE",
"formStructure": { ... },
"createDate": "2026-01-15T10:30:00.000Z",
"lastUpdate": "2026-01-15T10:30:00.000Z"
}
}
```
### Listing forms
To retrieve all form definitions for your company, send a GET request to the forms endpoint.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/marketplace/forms
```
**Query Parameters**
| Parameter | Required | Description |
| :- | :- | :- |
| status | No | Filter by form status: `ACTIVE` or `ARCHIVED`. By default, active forms are included and archived forms are excluded. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/marketplace/forms?status=ACTIVE
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Forms retrieved",
"data": [
{
"formUid": "abc12345-6789-0def-ghij-klmnopqrstuv",
"name": "Customer Onboarding Form",
"status": "ACTIVE",
"formStructure": { ... },
"createDate": "2026-01-15T10:30:00.000Z",
"lastUpdate": "2026-01-15T10:30:00.000Z"
}
]
}
```
### Retrieving a form
To retrieve a specific form definition, send a GET request with the form UID.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/marketplace/forms/{formUid}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| formUid | The unique identifier of the form. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/marketplace/forms/abc12345-6789-0def-ghij-klmnopqrstuv
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Form retrieved",
"data": {
"formUid": "abc12345-6789-0def-ghij-klmnopqrstuv",
"name": "Customer Onboarding Form",
"status": "ACTIVE",
"formStructure": { ... },
"createDate": "2026-01-15T10:30:00.000Z",
"lastUpdate": "2026-01-15T10:30:00.000Z"
}
}
```
### Updating a form
To update an existing form definition, send a PUT request with the updated fields.
Form definitions can be updated after a VXC connection has been requested using the form. Form requirements might change over time, so forms can be updated as required without affecting existing submissions.
Form status cannot be updated. To change the form status to *Archived*, use the delete endpoint. This marks the form as *Archive* if it has submissions against it or permanently deletes it if there are no submissions. To reactivate an archived form, use the activate endpoint. For more information, see [Activating a form](#activate-form) and [Deleting a form](#delete-form).
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
PUT {baseUrl}/v3/marketplace/forms/{formUid}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| formUid | The unique identifier of the form to update. |
**Request Body**
Include only the fields you want to update. You can update the `name` and `formStructure` fields.
**Example Request**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"name": "Updated Customer Onboarding Form",
"formStructure": {
"type": "object",
"properties": {
"companyName": {
"type": "string",
"title": "Updated Company Name"
},
}
}
}
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Form updated",
"data": {
"formUid": "abc12345-6789-0def-ghij-klmnopqrstuv",
"name": "Updated Customer Onboarding Form",
"status": "ACTIVE",
"formStructure": { ... },
"createDate": "2026-01-15T10:30:00.000Z",
"lastUpdate": "2026-01-16T14:00:00.000Z"
}
}
```
### Activating a form
To activate an archived or draft form, send a POST request to the activate endpoint.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/marketplace/forms/{formUid}/activate
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| formUid | The unique identifier of the form to activate. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/marketplace/forms/abc12345-6789-0def-ghij-klmnopqrstuv/activate
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Form activated",
"data": {
"formUid": "abc12345-6789-0def-ghij-klmnopqrstuv",
"status": "ACTIVE"
}
}
```
### Deleting a form
To delete a form definition, send a DELETE request. If the form has service associations, these associations will be removed and the form will be deleted. If the form has linked submissions, it will be archived instead of deleted.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
DELETE {baseUrl}/v3/marketplace/forms/{formUid}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| formUid | The unique identifier of the form to delete. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
DELETE {baseUrl}/v3/marketplace/forms/abc12345-6789-0def-ghij-klmnopqrstuv
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Form deleted"
}
```
## Linking forms to services
After creating a form definition, link it to your Megaport Marketplace services so customers can complete the form when requesting a connection.
### Attaching a form to a service
To attach a form to a service, send a POST request to the service forms endpoint.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/marketplace/service_forms
```
**Request Body**
| Field | Required | Description |
| :- | :- | :- |
| serviceUid | Yes | The unique identifier of the Megaport Marketplace service. |
| formUid | Yes | The unique identifier of the form to attach. |
**Example Request**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"serviceUid": "svc12345-6789-0def-ghij-klmnopqrstuv",
"formUid": "abc12345-6789-0def-ghij-klmnopqrstuv"
}
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Service form association created",
"data": {
"serviceFormUid": "assoc123-4567-89ab-cdef-ghijklmnopqr",
"serviceUid": "svc12345-6789-0def-ghij-klmnopqrstuv",
"formUid": "abc12345-6789-0def-ghij-klmnopqrstuv"
}
}
```
Each service can be linked to only one form, but a form can be linked to multiple services.
### Listing service-form associations
To list all service-form associations, send a GET request with optional parameter filters.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/marketplace/service_forms
```
**Query Parameters**
| Parameter | Required | Description |
| :- | :- | :- |
| serviceUid | No | Filter by service UID. |
| formUid | No | Filter by form UID. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/marketplace/service_forms?serviceUid=svc12345-6789-0def-ghij-klmnopqrstuv
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Service form associations retrieved",
"data": [
{
"serviceFormUid": "assoc123-4567-89ab-cdef-ghijklmnopqr",
"serviceUid": "svc12345-6789-0def-ghij-klmnopqrstuv",
"formUid": "abc12345-6789-0def-ghij-klmnopqrstuv",
"formStructure": { ... }
}
]
}
```
### Updating a service-form association
To change the form associated with a service, send a PUT request with the UID of the new form. This replaces the form currently associated with the service.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
PUT {baseUrl}/v3/marketplace/service_forms/{serviceFormUid}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| serviceFormUid | The unique identifier of the service-form association. |
**Request Body**
| Field | Required | Description |
| :- | :- | :- |
| formUid | Yes | The unique identifier of the new form to link. |
**Example Request**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"formUid": "newform12-3456-789a-bcde-fghijklmnopq"
}
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Service form association updated",
"data": {
"serviceFormUid": "assoc123-4567-89ab-cdef-ghijklmnopqr",
"serviceUid": "svc12345-6789-0def-ghij-klmnopqrstuv",
"formUid": "newform12-3456-789a-bcde-fghijklmnopq"
}
}
```
### Detaching a form from a service
To remove a form from a service, send a DELETE request.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
DELETE {baseUrl}/v3/marketplace/service_forms/{serviceFormUid}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| serviceFormUid | The unique identifier of the service-form association to remove. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
DELETE {baseUrl}/v3/marketplace/service_forms/assoc123-4567-89ab-cdef-ghijklmnopqr
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Service form association deleted"
}
```
## Managing form submissions
When customers request a connection to a service with a form configured, they submit the form data. Service providers can retrieve this data to review connection requests.
### Listing all form submissions
To list all form submissions for your company's forms, send a GET request to the submissions endpoint.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/marketplace/form_submissions
```
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/marketplace/form_submissions
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Action completed successfully",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"companyId": 123,
"createDate": "2025-11-12T10:15:30.123Z",
"formData": {
"company_name": "Acme Corp",
"industry": "technology",
"number_of_locations": 3,
"requires_redundancy": true
},
"formDefinitionId": 42,
"formStructure": {
"type": "object",
"properties": {
"company_name": {
"type": "string"
},
"industry": {
"type": "string",
"enum": [
"technology",
"finance",
"healthcare",
"other"
]
},
"number_of_locations": {
"type": "integer"
},
"requires_redundancy": {
"type": "boolean"
}
},
"required": [
"company_name",
"industry"
]
},
"lastUpdate": "2025-11-12T10:15:30.123Z",
"uid": "e900d0d5-1030-4e29-b2d8-816ad4263190",
"vxcOrderId": 100
}
]
}
```
### Retrieving a form submission
To retrieve a specific form submission, send a GET request with the submission UID.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/marketplace/form_submissions/{submissionUid}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| submissionUid | The unique identifier of the form submission. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/marketplace/form_submissions/sub12345-6789-0def-ghij-klmnopqrstuv
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Action completed successfully",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"companyId": 123,
"createDate": "2025-11-12T10:15:30.123Z",
"formData": {
"company_name": "Acme Corp",
"industry": "technology",
"number_of_locations": 3,
"requires_redundancy": true
},
"formDefinitionId": 42,
"formStructure": {
"type": "object",
"properties": {
"company_name": {
"type": "string"
},
"industry": {
"type": "string",
"enum": [
"technology",
"finance",
"healthcare",
"other"
]
},
"number_of_locations": {
"type": "integer"
},
"requires_redundancy": {
"type": "boolean"
}
},
"required": [
"company_name",
"industry"
]
},
"lastUpdate": "2025-11-12T10:15:30.123Z",
"uid": "sub12345-6789-0def-ghij-klmnopqrstuv",
"vxcOrderId": 100
}
}
```
### Listing submissions by form
To retrieve all submissions for a specific form, send a GET request with the form UID.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/marketplace/form_submissions/form/{formUid}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| formUid | The unique identifier of the form. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/marketplace/form_submissions/form/abc12345-6789-0def-ghij-klmnopqrstuv
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Action completed successfully",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"companyId": 123,
"createDate": "2025-11-12T10:15:30.123Z",
"formData": {
"company_name": "Acme Corp",
"industry": "technology",
"number_of_locations": 3,
"requires_redundancy": true
},
"formDefinitionId": 42,
"formStructure": {
"type": "object",
"properties": {
"company_name": {
"type": "string"
},
"industry": {
"type": "string",
"enum": [
"technology",
"finance",
"healthcare",
"other"
]
},
"number_of_locations": {
"type": "integer"
},
"requires_redundancy": {
"type": "boolean"
}
},
"required": [
"company_name",
"industry"
]
},
"lastUpdate": "2025-11-12T10:15:30.123Z",
"uid": "abc12345-6789-0def-ghij-klmnopqrstuv",
"vxcOrderId": 100
}
]
}
```
### Listing submissions by service
To retrieve all submissions for a specific service, send a GET request with the service UID.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/marketplace/form_submissions/service/{serviceUid}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| serviceUid | The unique identifier of the service. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/marketplace/form_submissions/service/svc12345-6789-0def-ghij-klmnopqrstuv
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Action completed successfully",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"companyId": 123,
"createDate": "2025-11-12T10:15:30.123Z",
"formData": {
"company_name": "Acme Corp",
"industry": "technology",
"number_of_locations": 3,
"requires_redundancy": true
},
"formDefinitionId": 42,
"formStructure": {
"type": "object",
"properties": {
"company_name": {
"type": "string"
},
"industry": {
"type": "string",
"enum": [
"technology",
"finance",
"healthcare",
"other"
]
},
"number_of_locations": {
"type": "integer"
},
"requires_redundancy": {
"type": "boolean"
}
},
"required": [
"company_name",
"industry"
]
},
"lastUpdate": "2025-11-12T10:15:30.123Z",
"uid": "svc12345-6789-0def-ghij-klmnopqrstuv",
"vxcOrderId": 100
}
]
}
```
### Deleting a form submission
To delete a form submission, send a DELETE request to the submissions endpoint.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
DELETE {baseUrl}/v3/marketplace/form_submissions/{submissionUid}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| submissionUid | The unique identifier of the form submission to delete. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
DELETE {baseUrl}/v3/marketplace/form_submissions/e900d0d5-1030-4e29-b2d8-816ad4263190
```
**Example Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Action completed successfully",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy"
}
```
## Helpful references
* [Creating a Megaport Marketplace Profile](/marketplace/profile)
* [Megaport Marketplace Forms](/marketplace/forms)
* [Megaport Marketplace Notifications](/marketplace/notifications)
* [Using Webhooks in the Megaport Portal](/portal-admin/using-webhooks)
# Creating an MCR with the API
Source: https://docs.megaport.com/api/api-mcr
This help topic describes how to use the Megaport API to create a Megaport Cloud Router (MCR).
This topic describes the API procedure to create an MCR, including how to look up locations for the MCR, and how to validate and complete the order.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
**To look up MCR location details in the Postman collection**
1. Expand the **Locations** folder in the left navigation and click **GET Locations (v3)**.\
This request is not expecting Parameters or Body information.
2. Click **Send** to make a GET request.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/locations
```
Ensure the request was successful by looking for Status: 200 OK and display the response in the Body section in the Pretty format.
The request returns hundreds of Megaport locations.
3. Click the magnifying glass and search the response for a site that includes `mcrSpeedMbps` in the `diversityZones` object and is in the US market.
To provision an MCR at a location, the port speed must be available in the `diversityZones` object. Check that the location has the available speed and diversity zone for the MCR.
```json {2,17,22,24,39} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"id": 60,
"name": "CoreSite LA1",
"address": {
"street": "624 South Grand Avenue",
"suburb": null,
"city": "Los Angeles",
"state": "CA",
"postcode": "90017",
"country": "USA"
},
"dataCentre": {
"id": 18,
"name": "CoreSite"
},
"metro": "Los Angeles",
"market": "US",
"status": "Active",
"longitude": -118.25554,
"latitude": 34.04791,
"orderingMessage": null,
"diversityZones": {
"red": {
"mcrSpeedMbps": [
2500,
5000,
10000,
1000
],
"megaportSpeedMbps": [
1000,
10000,
100000
],
"mveMaxCpuCoreCount": null,
"mveAvailable": true
},
"blue": {
"mcrSpeedMbps": [
5000,
1000,
2500,
10000
],
"megaportSpeedMbps": [
1000,
100000,
10000
],
"mveMaxCpuCoreCount": null,
"mveAvailable": true
}
},
"productAddOns": {
"crossConnect": {
"available": true,
"type": "STANDARD"
}
}
}
```
To create an MCR, you need the `id` value. In this example, the location ID is 60.
**To test and validate the MCR order**
1. In Postman, expand **Megaport Cloud Router (MCR)** in the left navigation and select **Validate MCR Order (v3)**.
2. Update the Body with the `locationId` (60), `productName` (whatever name you want for your MCR), `term` (the minimum number of months in the committed term: 1, 12, 24, 36, 48, or 60), and `portSpeed` (1000, 2500, 5000, or 10000 Mbps) and click **Send**.\
An ASN value is only required if you don’t want to use the Megaport default ASN of 133937.\
Add a diversity zone. Check the location results to see which diversity zones are available for your MCR location under `diversityZones`.\
If the diversity zone is not explicitly selected, one will be automatically allocated when the MCR is created.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/validate
```
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"locationId":60,
"term": 12,
"promoCode": "promox3mnthfree2",
"productName":"Test MCR",
"productType":"MCR2",
"portSpeed":2500,
"config": {
"mcrAsn": 133937,
"diversityZone":"blue"
}
}
]
```
A successful response passes validation and has a 200 OK status. The response also includes pricing details of the service.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Validation passed",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"price": {
"hourlySetup": 0,
"dailySetup": 0,
"monthlySetup": 0,
"hourlyRate": 0,
"dailyRate": 0,
"monthlyRate": 1440.00,
"fixedRecurringCharge": 0,
"postPaidBaseRate": "no base rate",
"longHaulMbpsRate": 0,
"mbpsRate": 6.000000000000000,
"currency": "USD",
"key": "no key",
"productType": "MCR2",
"empty": false
},
"serviceName": "API Test MCR",
"productType": "MCR2",
"productUid": "78aebd6b-7601-4331-82bc-dcd07f9f21a6",
"string": "Los Angeles"
}
]
}
```
**To order the validated MCR**
1. With a validated MCR request and reviewed cost information, copy the Body from **POST Validate MCR Order (v3)** and paste into the Body of **POST Buy MCR (v3)**.
If you make this call on api.megaport.com, your account will be charged for the service. Alternatively, you can use the API in the staging (test) environment without charges, as in these examples.
2. Send the request.
This output shows a successful response.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "MCR2 [426fa830-4b66-41ad-95a1-197d55e074b1] created.",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"serviceName": "Test MCR",
"name": "Test MCR",
"secondaryName": null,
"technicalServiceId": 187964,
"technicalServiceUid": "426fa830-4b66-41ad-95a1-197d55e074b1",
"requestedDate": 1707800936928,
"configuredDate": null,
"currentEstimatedDelivery": null,
"companyName": "Megaport Lab",
"companyId": 1153,
"billingContactName": null,
"billingContactId": null,
"adminContactName": null,
"adminContactId": null,
"technicalContactName": null,
"technicalContactId": null,
"salesName": null,
"salesId": null,
"billableId": 179527,
"billableUsageAlgorithm": null,
"productType": "MCR2",
"provisioningStatus": "DEPLOYABLE",
"failedReason": null,
"inAdvanceBillingStatus": null,
"provisioningItems": [],
"tags": [],
"vxcDistanceBand": null,
"intercapPath": null,
"marketplaceVisibility": false,
"vxcPermitted": true,
"vxcAutoApproval": false,
"createDate": 1707800936928,
"terminationDate": null,
"contractStartDate": null,
"contractTermMonths": 12,
"rateType": "MONTHLY",
"trialAgreement": false,
"payerCompanyId": null,
"nonPayerCompanyId": null,
"minimumSpeed": null,
"maximumSpeed": null,
"rateLimit": 2500,
"errorMessage": null,
"lagId": null,
"aggregationId": null,
"lagPrimary": null,
"market": "USA",
"accountManager": null,
"promptUid": null,
"components": [],
"attributes": [],
"aLocation": "lax-cs1",
"bLocation": null,
"aMetro": "Los Angeles",
"aCountry": "USA",
"aLocationId": 60,
"bLocationId": null,
"bMetro": null,
"bCountry": null,
"attributeTags": {},
"createdBy": "f39b8983-256e-4643-adec-9f0b5da09ab7",
"buyoutPort": false,
"virtual": true,
"locked": false,
"adminLocked": false,
"bgpShutdownDefault": false
}
]
}
```
The new MCR now appears in your working environment, either portal.megaport.com or portal-staging.megaport.com.
To see all options for the requests used in this example, see [https://dev.megaport.com](https://dev.megaport.com).
The next step is to create VXCs to this MCR.\
For more information, see:
* [Creating an MCR VXC with the API](/api/api-mcr-vxc-csp)
* [Creating a VXC between an MCR and Microsoft Azure with the API](/api/api-mcr-vxc-azure)
# Running MCR Diagnostics with the API
Source: https://docs.megaport.com/api/api-mcr-diagnostics
This help topic describes how to use the Megaport API to run ping and traceroute diagnostics from a Megaport Cloud Router (MCR).
This topic describes how to use the Megaport API to run ping and traceroute diagnostics from a Megaport Cloud Router (MCR). Use these diagnostics to test network connectivity and troubleshoot routing issues from the perspective of your MCR.
Both diagnostics run asynchronously. You initiate the request, which returns an operation ID, then use a separate endpoint to retrieve the results when the operation completes. Results are available for approximately 10 minutes after the operation completes.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
The ping and traceroute endpoints are rate limited and intended for troubleshooting, not regular monitoring.
## Use cases
These diagnostics help you troubleshoot network connectivity issues by testing reachability and path visibility from the MCR itself.
Common use cases include:
* Verifying connectivity to cloud provider endpoints before configuring BGP sessions.
* Testing reachability to on-premises networks connected via VXCs.
* Diagnosing routing issues by confirming whether the MCR can reach specific destinations.
* Validating network paths and measuring round-trip latency.
* Identifying routing hops and potential bottlenecks using traceroute.
* Troubleshooting asymmetric routing or path issues.
## Prerequisites
The MCR must have at least one active VXC attached. Running a diagnostic on an MCR with no VXCs returns a 400 Bad Request error with the message: "MCR has no VXCs attached. Ping/traceroute requires at least one active VXC."
## Ping
Use the ping diagnostic to test basic connectivity and measure round-trip latency to a destination IP address.
### Initiating a ping request
To start a ping diagnostic from your MCR, send a GET request to the ping endpoint with the destination IP address and optional parameters.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/product/mcr2/{productUid}/diagnostics/ping
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier of the MCR from which to run the diagnostic. |
**Query Parameters**
| Parameter | Required | Description |
| :- | :- | :- |
| destination\_address | Yes | The target IPv4 or IPv6 address to ping. Must be an IP address literal, not a hostname. Cannot be a loopback, multicast, or any-local address. Private (RFC1918) and link-local addresses are allowed for testing connectivity to VPC/VNet resources. |
| source\_address | No | The source IPv4 or IPv6 address for the ping. Must be the same address family as the destination address. |
| packet\_count | No | The number of ICMP packets to send. Valid range: 1-60. Default: 3. |
| packet\_size | No | The size of each ICMP packet in bytes. Valid range: 1-9186. Default: 56. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/product/mcr2/abc12345-6789-0def-ghij-klmnopqrstuv/diagnostics/ping?destination_address=192.0.2.1&packet_count=5
```
**Response**
A successful request returns an `operationId` that you use to retrieve the ping results.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Please retrieve the result with the operation id: 12345678-90ab-cdef-1234-567890abcdef",
"terms": "This data is subject to the Acceptable Use Policy.",
"data": "12345678-90ab-cdef-1234-567890abcdef"
}
```
### Retrieving ping results
After initiating a ping request, use the diagnostics operation endpoint to retrieve the results. The operation runs asynchronously, so you might need to poll until the results are ready.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/product/mcr2/{productUid}/diagnostics/routes/operation?operationId={operationId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier of the MCR. |
**Query Parameters**
| Parameter | Required | Description |
| :- | :- | :- |
| operationId | Yes | The operation ID returned from the ping initiation request. |
**Response Codes**
| Code | Description |
| :- | :- |
| 200 | The ping operation has completed. Results are included in the response. |
| 202 | The ping operation is still pending or running. Poll again after a short delay. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/product/mcr2/abc12345-6789-0def-ghij-klmnopqrstuv/diagnostics/routes/operation?operationId=12345678-90ab-cdef-1234-567890abcdef
```
**Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Diagnostic result retrieved successfully",
"data": {
"rawOutput": "PING 192.0.2.1 (192.0.2.1) 56(84) bytes of data...",
"statistics": {
"packetsTransmitted": 5,
"packetsReceived": 5,
"packetLossPct": 0.0,
"rttMinMs": 0.987,
"rttAvgMs": 1.234,
"rttMaxMs": 1.567,
"rttMdevMs": 0.123,
"totalTimeMs": 4012.0,
"duplicates": 0,
"errors": 0
}
}
}
```
The response includes `rawOutput` containing the raw ping command output, and `statistics` with detailed packet and timing metrics. If the ping fails, an `error` field contains the error message.
## Traceroute
Use the traceroute diagnostic to discover the network path between your MCR and a destination IP address, showing each hop along the route.
### Initiating a traceroute request
To start a traceroute diagnostic from your MCR, send a GET request to the traceroute endpoint with the destination IP address.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/product/mcr2/{productUid}/diagnostics/traceroute
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier of the MCR from which to run the diagnostic. |
**Query Parameters**
| Parameter | Required | Description |
| :- | :- | :- |
| destination\_address | Yes | The target IPv4 or IPv6 address to trace. Must be an IP address literal, not a hostname. Cannot be a loopback, multicast, or any-local address. Private (RFC1918) and link-local addresses are allowed for testing connectivity to VPC/VNet resources. |
| source\_address | No | The source IPv4 or IPv6 address for the traceroute. Must be the same address family as the destination address. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/product/mcr2/abc12345-6789-0def-ghij-klmnopqrstuv/diagnostics/traceroute?destination_address=192.0.2.1
```
**Response**
A successful request returns an `operationId` that you use to retrieve the traceroute results.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Please retrieve the result with the operation id: 12345678-90ab-cdef-1234-567890abcdef",
"terms": "This data is subject to the Acceptable Use Policy.",
"data": "12345678-90ab-cdef-1234-567890abcdef"
}
```
### Retrieving traceroute results
After initiating a traceroute request, use the diagnostics operation endpoint to retrieve the results. The operation runs asynchronously, so you might need to poll until the results are ready.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/product/mcr2/{productUid}/diagnostics/routes/operation?operationId={operationId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier of the MCR. |
**Query Parameters**
| Parameter | Required | Description |
| :- | :- | :- |
| operationId | Yes | The operation ID returned from the traceroute initiation request. |
**Response Codes**
| Code | Description |
| :- | :- |
| 200 | The traceroute operation has completed. Results are included in the response. |
| 202 | The traceroute operation is still pending or running. Poll again after a short delay. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/product/mcr2/abc12345-6789-0def-ghij-klmnopqrstuv/diagnostics/routes/operation?operationId=12345678-90ab-cdef-1234-567890abcdef
```
**Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Diagnostic result retrieved successfully",
"data": {
"hops": [
{
"hop": "1",
"probes": [
{ "host": "198.51.100.1", "rttMs": 0.543 },
{ "host": "198.51.100.1", "rttMs": 0.487 },
{ "host": "198.51.100.1", "rttMs": 0.512 }
]
},
{
"hop": "2",
"probes": [
{ "host": "203.0.113.254", "rttMs": 1.234 },
{ "host": "203.0.113.254", "rttMs": 1.156 },
{ "host": "203.0.113.254", "rttMs": 1.298 }
]
},
{
"hop": "3",
"probes": [
{ "host": "192.0.2.1", "rttMs": 2.876 },
{ "host": "192.0.2.1", "rttMs": 2.654 },
{ "host": "192.0.2.1", "rttMs": 2.789 }
]
}
],
"rawOutput": "traceroute to 192.0.2.1, 30 hops max, 60 byte packets..."
}
}
```
The response includes an array of `hops`, where each hop contains a `hop` number and an array of `probes`. Each probe shows the responding `host` (IP address or hostname) and the `rttMs` (round-trip time in milliseconds). If a probe receives no response, `host` may be null. The `rawOutput` field contains the raw traceroute command output.
## Helpful references
* [Creating an MCR with the API](/api/api-mcr)
* [Troubleshooting an MCR Routing Issue](/troubleshooting/mcr/routing)
* [Viewing Traffic Routing through MCR Looking Glass](/mcr/mcr-looking-glass)
# Creating a VXC between an MCR and AWS with the API
Source: https://docs.megaport.com/api/api-mcr-vxc-aws
This help topic describes how to use the Megaport API to create a VXC between a Megaport Cloud Router (MCR) and AWS Direct Connect.
This topic describes the API procedure to create a VXC from an MCR to AWS Direct Connect, including how to look up AWS interconnect locations and order VXCs.
You can set up two types of AWS connections from an MCR; an AWS Hosted VIF and an AWS Hosted Connection.
* **Hosted VIF** – Connects to public or private AWS cloud services. Hosted VIFs are fully integrated with AWS and provide access to routing information for automatic configuration of your MCR BGP peering.
* **Hosted Connection** – Supports one private, public, or transit virtual interface. The Hosted Connection configuration process does not have automatic access to routing information for the MCR, so you need to configure routing manually and specify BGP peering details on both the AWS virtual interface and the MCR A-End configuration.
The MCR to AWS deployment includes these tasks:
1. **Look up AWS port location details**
To create a VXC to AWS, you first need to identify the `productUid` of the AWS port to which you want to connect.
2. **Create and deploy a VXC**
With the port details identified, you can create the VXC to AWS from the MCR.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
## Look up AWS port location details
Use the API to look up the `productUid` of the AWS port you want to connect to. The response includes details of the available ports. You need the port details to create the VXC.
The `connectType` indicates the type of connection:
* `AWS` – Hosted VIF
* `AWSHC` – Hosted Connection
**To look up AWS port location details**
1. Make a GET request to the Partner Megaports endpoint.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/dropdowns/partner/megaports
```
This request returns all the interfaces Megaport has with Cloud Service Providers (CSPs). In the response, locate the required port by searching on location, data center, or other parameter.
You can filter the results by `connectType` and `vxcPermitted`.
For Hosted VIF connections:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/dropdowns/partner/megaports?connectType=AWS&vxcPermitted=true
```
For Hosted Connections:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/dropdowns/partner/megaports?connectType=AWSHC&vxcPermitted=true
```
In the response, available ports that accept VXCs are listed as `"vxcPermitted": true`.
Here is a sample response for a Hosted VIF port in the EU (Ireland) region:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"connectType": "AWS",
"productUid": "6cc21ccb-5ecc-4869-ab0e-b3fa17f5110f",
"vxcPermitted": true,
"companyUid": "623cb950-abb4-4b07-b372-8cf55756c322",
"companyName": "AWS",
"title": "EU (Ireland) (eu-west-1)",
"locationId": 96,
"speed": 10000,
"rank": 61,
"lag_id": 2,
"lag_primary": true,
"aggregation_id": 54188
}
```
Here is a sample response for a Hosted Connection port with diversity zone information:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"connectType": "AWSHC",
"productUid": "f274bd09-1796-43af-8837-28fa4fa2a1ab",
"vxcPermitted": true,
"companyUid": "605cb850-dfb4-4a05-a171-8bf17757b3a2",
"companyName": "AWS",
"title": "US West (Oregon) (us-west-2) [DZ-RED]",
"locationId": 57,
"speed": 10000,
"rank": 275,
"lag_id": 5,
"lag_primary": true,
"aggregation_id": 106462
}
```
\[DZ-RED] and \[DZ-BLUE] indicate diversity zones. Each AWS Hosted Connection site provides two diversity zones to provide redundancy.
## Creating a VXC with a Hosted VIF
With the port details from the **GET Partner Megaports** endpoint, you can create a VXC with a Hosted VIF. For Hosted VIF connections, Megaport can set up the IP addressing and BGP details on both the MCR and the AWS side, ensuring a working BGP setup.
This autoconfiguration is triggered when the `interfaces` key in `partnerConfig` does not exist or is null.
**To create the VXC**
1. Create a request with this URL:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
To test your request before you order, you can use:
`POST {baseUrl}/v3/networkdesign/validate`
2. Create the Body of the request with the configuration details.
### Hosted VIF with autoconfiguration
Use this template to create a Hosted VIF with automatic BGP configuration. The `interfaces` key is omitted, which triggers autoconfiguration:
```json hl_lines="4 11 15 16" theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "{ mcrid }",
"associatedVxcs": [
{
"productName": "Test AWS VIF MCR VXC",
"rateLimit": "100",
"aEnd": {
"vlan": 101
},
"bEnd": {
"productUid": "6cc21ccb-5ecc-4869-ab0e-b3fa17f5110f",
"vlan": 0,
"partnerConfig": {
"connectType": "AWS",
"type": "private",
"asn": 133937,
"amazonAsn": 64555,
"ownerAccount": "{ AWSAccount }",
"authKey": "123455",
"customerIpAddress": null,
"amazonIpAddress": null
}
}
}
]
}
]
```
The `type` field specifies the VIF type:
* `private` – Access private AWS services such as a VPC, EC2 instances, load balancers, and RDS DB instances on private IP address space.
* `public` – Access public AWS services such as Amazon S3, DynamoDB, CloudFront, and Glacier. You will also receive Amazon's global IP prefixes.
### Hosted VIF with manual configuration
If you need more control over the BGP configuration, you can specify the `interfaces` array in the A-End `partnerConfig`:
```json {3,12-31,35,36} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "{ mcrid }",
"associatedVxcs": [
{
"productName": "AWS VIF with Manual BGP",
"rateLimit": 100,
"term": 12,
"shutdown": false,
"aEnd": {
"vlan": 0,
"partnerConfig": {
"connectType": "VROUTER",
"interfaces": [
{
"ipAddresses": ["10.191.0.25/29"],
"bgpConnections": [
{
"peerAsn": 64555,
"localIpAddress": "10.191.0.25",
"peerIpAddress": "10.191.0.26",
"password": "yourBGPpassword",
"shutdown": false,
"description": "BGP to AWS",
"bfdEnabled": true
}
]
}
]
}
},
"bEnd": {
"productUid": "6cc21ccb-5ecc-4869-ab0e-b3fa17f5110f",
"partnerConfig": {
"name": "awshc",
"connectType": "AWS",
"type": "private",
"ownerAccount": "{ yourAWSAccountNumber }",
"asn": 65105,
"amazonAsn": 64555,
"authKey": "yourBGPpassword",
"customerIpAddress": "10.191.0.25/29",
"amazonIpAddress": "10.191.0.26/29"
}
}
}
]
}
]
```
### B-End partnerConfig fields for Hosted VIF
| **Field** | **Description** | **Required** |
| - | - | - |
| name | The name of the virtual interface in the AWS console. | No |
| connectType | The connection type. Use `AWS` for Hosted VIF. | Yes |
| type | The VIF type: `private` or `public`. | Yes |
| ownerAccount | Your 12-digit AWS account number. | Yes |
| asn | The ASN for your network (Customer ASN). | No |
| amazonAsn | The ASN of the AWS gateway. | No |
| authKey | The shared key used to authenticate the BGP peer. | No |
| customerIpAddress | The IP address on your network for peering (CIDR format). | No |
| amazonIpAddress | The IP address on the AWS side for peering (CIDR format). | No |
| prefixes | IP prefixes to announce to AWS (for public VIFs only). | No |
## Creating a VXC with a Hosted Connection
Hosted Connections support private, public, and transit virtual interfaces. Because Hosted Connections do not have automatic access to routing information, you need to configure BGP peering details manually.
**To create the VXC**
1. Create a request with this URL:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
To test your request before you order, you can use:
`POST {baseUrl}/v3/networkdesign/validate`
2. Create the Body of the request with the configuration details.
Use this template to create a Hosted Connection:
```json {3,13-38,41,44,45,46} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "{ mcrid }",
"associatedVxcs": [
{
"rateLimit": 100,
"productName": "awshc",
"term": 12,
"shutdown": false,
"aEnd": {
"locationId": 96,
"vlan": 0,
"partnerConfig": {
"connectType": "VROUTER",
"interfaces": [
{
"ipAddresses": [
"10.191.0.27/29"
],
"bgpConnections": [
{
"peerAsn": 62511,
"localIpAddress": "10.191.0.27",
"peerIpAddress": "10.191.0.28",
"password": "cnn23049asdkfj",
"shutdown": false,
"description": "BGP without MED or BFD",
"medIn": null,
"medOut": null,
"bfdEnabled": false
}
],
"natIpAddresses": []
}
]
}
},
"bEnd": {
"locationId": 89,
"ownerUid": "{ ownerUid }",
"productUid": "f274bd09-1796-43af-8837-28fa4fa2a1ab",
"vlan": 0,
"partnerConfig": {
"name": "awshc",
"ownerAccount": "{ AWSAccount }",
"connectType": "AWSHC"
}
},
"productType": "VXC",
"connectType": "AWSHC"
}
]
}
]
```
### B-End partnerConfig fields for Hosted Connection
| **Field** | **Description** | **Required** |
| - | - | - |
| name | The name of the connection in the AWS console. | No |
| ownerAccount | Your 12-digit AWS account number. | Yes |
| connectType | The connection type. Use `AWSHC` for Hosted Connection. | Yes |
## Static routes and BGP connections
You can create static routes and BGP connections per interface by adding `ipRoutes` and `bgpConnections` arrays to the interfaces array of the A-End partner configuration object.
For detailed information about configuring static routes and BGP connections, including field descriptions and examples, see [Creating an MCR VXC with the API](/api/api-mcr-vxc-csp).
## Example successful order response
Here is a sample response for a successful Hosted VIF order:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "VXC [47d6cc4d-6a1a-4301-b06c-cebb5f9b8f3e] created.",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"createDate": 1588868593704,
"vxcOrderId": 42328,
"payerMegaPortId": 68124,
"nonPayerMegaPortId": 52786,
"payerMegaPortName": "MCR",
"nonPayerMegaPortName": "EU (Ireland) (eu-west-1)",
"payerCompanyId": 2278,
"nonPayerCompanyId": 117,
"serviceName": "from MCR to EU (Ireland) (eu-west-1)",
"payerStatus": "APPROVED",
"nonPayerStatus": "APPROVED",
"speed": 100,
"vxcJTechnicalServiceUid": "47d6cc4d-6a1a-4301-b06c-cebb5f9b8f3e",
"amazonDirectConnectConfigDto": {
"type": "private",
"asn": 65105,
"ownerAccount": "123456789012",
"authKey": "yourBGPpassword",
"customerIpAddress": null,
"amazonIpAddress": null,
"prefixes": null,
"name": "Test AWS VIF VXC"
},
"connectType": "AWS",
"fullyApproved": true
}
]
}
```
## Accepting the connection in AWS
After you create the VXC, you need to accept the connection in the AWS console.
**For Hosted VIF**
1. In the AWS console, go to **Direct Connect > Virtual Interfaces**.
2. Click the ID of the interface to display the configuration and peering details.
3. Click **Accept**.
4. For private VIFs, select the gateway type and the specific gateway for the new virtual interface.
5. Click **Accept virtual interface**.
The state of the connection changes from *confirming* to *pending*, and then changes to *available* once BGP has established.
Public VIFs require manual verification by Amazon, which can take up to 72 hours.
**For Hosted Connection**
1. In the AWS console, go to **Direct Connect > Connections**.
2. Click the connection name to review the details.
3. Click **Accept**.
4. After the connection is accepted, click **Create Virtual Interface** and create a virtual interface for the hosted connection.
When you create the virtual interface in AWS, make sure the BGP peering values match the configuration you specified in the MCR A-End.
For more information about creating virtual interfaces in AWS, see the [AWS Direct Connect documentation](https://docs.aws.amazon.com/directconnect/latest/UserGuide/create-vif.html).
# Creating a VXC between an MCR and Microsoft Azure with the API
Source: https://docs.megaport.com/api/api-mcr-vxc-azure
This help topic describes how to use the Megaport API to create a VXC between a Megaport Cloud Router (MCR) and an Azure ExpressRoute circuit.
This topic describes the API procedure to create a VXC from an MCR to Microsoft Azure ExpressRoute, including how to look up Azure interconnect locations and order VXCs.
The MCR to Azure deployment includes these tasks:
1. **Set up an ExpressRoute circuit in the Azure console**
When deployed, you get a service key. When you validate a service key, you are presented with primary and secondary ports and can choose the port for the connection. You can use the key a second time and create another connection to the unused port.
For more information, see the Microsoft help topic [Tutorial: Create and modify an ExpressRoute circuit](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-circuit-portal-resource-manager).
2. **With the service key, create and deploy your VXC**
As part of the VXC configuration, you can choose the peering type.
The peering type can be either private or Microsoft.
A defined peering type results in automatically configured peering with peers matched on both the Azure and Megaport sides and a deployed system with a known working configuration. You can modify the configuration once deployed.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
## Validate the service key
When you use the API to validate an Azure service key, the response includes ExpressRoute details of the associated ports and peers. You need the port details to create the VXCs.
**To validate the service key in the Postman collection**
1. In Postman, expand **Cloud Connectivity > MCR > Azure** in the left navigation and select **GET Look Up Azure Service Key**.
2. Add the service key to the endpoint.
3. Click **Send** to make a GET request to the API server.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/secure/azure/{service_key}
```
Here is a sample response for a new key (without configured VXCs):
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Successful lookup",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"managed": false,
"connectType": "AZURE",
"resource_type": "csp_connection",
"bandwidth": 200,
"service_key": "3e2480b2-b4d5-424b-976a-7b0de65a1b62",
"vlan": 3289,
"megaports": [
{
"portSpeed": 10000,
"name": "Washington DC Primary",
"state": "VA",
"description": "Azure ExpressRoute at Equinix DC2/6",
"productUid": "a7ae8a35-433e-44aa-87cb-a1b7995ab008",
"nServiceId": 32832,
"companyUid": "c40de5ed-4707-4471-a78c-69436de2c505",
"country": "USA",
"vxc": null,
"port": 14570,
"companyName": "Azure ExpressRoute",
"locationId": 67,
"productId": 14570,
"type": "primary",
"companyId": 1475
},
{
"portSpeed": 10000,
"name": "Washington DC Secondary",
"state": "VA",
"description": "Azure ExpressRoute at Equinix DC2/6",
"productUid": "07ab0ee6-7f77-41ac-bbe6-335e3ee6d182",
"nServiceId": 36431,
"companyUid": "c40de5ed-4707-4471-a78c-69436de2c505",
"country": "USA",
"vxc": null,
"port": 16108,
"companyName": "Azure ExpressRoute",
"locationId": 67,
"productId": 16108,
"type": "secondary",
"companyId": 1475
}
],
"peers": []
}
}
```
For more information about each response field, see [Azure Service Key Response Fields](/api/api-azure-servicekey).
## Ordering a VXC with peering options
With the details from the service key, create a VXC to the primary port and another VXC to the secondary port. Make sure that you select an MCR in the same region as the Azure ports from the service key lookup request.
If you specify the peering type in the API request for the VXC, Megaport will set up the IP addressing and BGP details on both the MCR and the Azure side to ensure a working BGP setup.
To specify the peering type, add a peering type to the peers array in the `partnerConfig` section. If a peers array does not exist, peers are retrieved from Azure. If peers are not specified when creating the VXC and there are no peers in Azure (which is normally the case for new service keys), the MCR peering will not be autoconfigured.
The MCR creates a VLAN for each configured peering type. If both private and Microsoft peering options are specified, the MCR configures two inner VLANs.
The peering types are remembered and cannot be changed if a key has been previously used.
**To create the VXC**
1. Create a request with the **POST Create VXC to Azure (v3)** endpoint:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
To test your request before you order, you can use:
`POST {baseUrl}/v3/networkdesign/validate`
2. Update the Body of the request with the `productUid` of the MCR, the name of the VXC, the `productUid` of the Azure port, and the service key. Include the appropriate peering option. The maximum speed (`rateLimit`) is defined in the bandwidth value of the service key response. In this case, it is 200.
The Azure VLAN (if specified) is the outer tag VLAN for Q-in-Q. If you don't specify the VLAN, it will be autoprovisioned.
To use an Azure key with private peering option, use this template:
```json {3,6,15,19,20} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "{ mcrid }",
"associatedVxcs": [
{
"productName": "Azure Primary VXC",
"rateLimit": 200,
"term": 12,
"shutdown": false,
"promoCode": "promox3mnthfree2",
"aEnd": {
"vlan": 0
},
"bEnd": {
"productUid": "{ azurepuid }",
"vlan": "{ azurevlan }",
"partnerConfig" : {
"connectType": "AZURE",
"serviceKey": "{ azurekey }",
"peers": [{"type": "private"}]
}
}
}
]
}
]
```
For Microsoft peering, use this line for the peers:
```json {1} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"peers":[{"type":"microsoft"}]
```
For both Microsoft and private peering, use this line:
```json {1} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"peers":[{"type":"microsoft"}, {"type": "private"}]
```
After you create a VXC for the primary Azure port, create another VXC to connect to the `productUid` of the secondary Azure port (change the `productName` and the `bEnd: productUid`).
## Configured response
When you create the VXCs with peering, another service key validation request displays the full configuration.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Successful lookup",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"managed": true,
"connectType": "AZURE",
"resource_type": "csp_connection",
"bandwidth": 200,
"service_key": "3e2480b2-b4d5-424b-976a-7b0de65a1b62",
"vlan": 3289,
"megaports": [
{
"portSpeed": 10000,
"name": "Washington DC Primary",
"state": "VA",
"description": "Azure ExpressRoute at Equinix DC2/6",
"productUid": "a7ae8a35-433e-44aa-87cb-a1b7995ab008",
"nServiceId": 32832,
"companyUid": "c40de5ed-4707-4471-a78c-69436de2c505",
"country": "USA",
"vxc": 60574,
"port": 14570,
"companyName": "Azure ExpressRoute",
"locationId": 67,
"productId": 14570,
"type": "primary",
"companyId": 1475
},
{
"portSpeed": 10000,
"name": "Washington DC Secondary",
"state": "VA",
"description": "Azure ExpressRoute at Equinix DC2/6",
"productUid": "07ab0ee6-7f77-41ac-bbe6-335e3ee6d182",
"nServiceId": 36431,
"companyUid": "c40de5ed-4707-4471-a78c-69436de2c505",
"country": "USA",
"vxc": 60575,
"port": 16108,
"companyName": "Azure ExpressRoute",
"locationId": 67,
"productId": 16108,
"type": "secondary",
"companyId": 1475
}
],
"peers": [
{
"peer_asn": 133937,
"shared_key": null,
"primary_subnet": "169.254.167.176/30",
"secondary_subnet": "169.254.167.180/30",
"vlan": 100,
"type": "private"
},
{
"peer_asn": 133937,
"shared_key": null,
"prefixes": "117.18.81.116/30,117.18.81.120/30",
"primary_subnet": "117.18.81.116/30",
"secondary_subnet": "117.18.81.120/30",
"vlan": 200,
"type": "microsoft"
}
]
}
}
```
# Creating an MCR VXC with the API
Source: https://docs.megaport.com/api/api-mcr-vxc-csp
This help topic describes how to use the Megaport API to create an MCR VXC.
This topic describes the API procedure to create an MCR VXC. The first example creates an AWS Hosted Connection in the US market - one of the more involved configurations. Templates for other CSPs appear later in the topic.
For more information, see [POST Validate MCR VXC Order (v3)](https://dev.megaport.com/#88537ea2-f3de-49c1-907d-d4037a2082e9) in the API reference.
## Creating a VXC between an MCR and AWS with a Hosted Connection
This example creates an AWS Hosted Connection in the US market. The steps include how to:
* get the MCR product ID
* find the location ID for an available US market
* validate and order the VXC
* configure two static routes
* configure connections -- one connection with details and one without.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
To create the VXC, we need the `productUid` for the MCR.
**To get the productUid for the MCR**
1. Get the product list.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/products/
```
2. From the returned product details, locate the `productUid` value for the MCR you want to connect.
This example uses this value: fee85cc0-f06f-4ad7-bce7-36aef7dbe0d0
Next, find the location ID for the US market you want with support for AWS Hosted Connections.
**To find the locationId in US market where AWS Hosted Connections are available**
1. Get the list for all interfaces Megaport has with Cloud Service Providers.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/dropdowns/partner/megaports
```
You can filter the results by `connectType` and `vxcPermitted`.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/dropdowns/partner/megaports?connectType=AWSHC&vxcPermitted=true
```
2. Click the magnifying glass and search through the response for a site matching your location criteria.
For this example, select "US West (Oregon) (us-west-2) \[DZ-RED]" with "locationId": 57.
```json {2,4,7,8} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"connectType": "AWSHC",
"productUid": "f274bd09-1796-43af-8837-28fa4fa2a1ab",
"vxcPermitted": true,
"companyUid": "605cb850-dfb4-4a05-a171-8bf17757b3a2",
"companyName": "AWS",
"title": "US West (Oregon) (us-west-2) [DZ-RED]",
"locationId": 57,
"speed": 10000,
"rank": 275,
"lag_id": 5,
"lag_primary": true,
"aggregation_id": 106462
},
```
\[DZ-RED] means Red diversity zone. Each AWS Hosted Connection site provides two diversity zones to provide redundancy: DZ-Red and DZ-Blue.
With the MCR ID and the AWS location ID, you can create a VXC.
**To create the VXC**
1. Create a request with this URL:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
To test your request before you order, you can use:
`POST {baseUrl}/v3/networkdesign/validate`
2. Add these headers to the request:
* Content-Type: application/json
* Authorization: Bearer \{your accessToken}
3. Create the Body of the request with the configuration details.
This example uses MCR product ID, the AWS location ID for the B-End, creates two static routes, and configures BGP connections – one connection with MED details and one without. The following sections provide details about the static routes and BGP connections.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "fee85cc0-f06f-4ad7-bce7-36aef7dbe0d0",
"associatedVxcs": [
{
"rateLimit": 100,
"productName": "awshc",
"term": 12,
"shutdown": false,
"promoCode": "promox3mnthfree2",
"aEnd": {
"locationId": 320,
"vlan": 0,
"partnerConfig": {
"connectType": "VROUTER",
"interfaces": [
{
"vlan": null,
"ipMtu": 5000,
"ipAddresses": [
"10.191.0.25/29",
],
"bgpConnections": [
{
"peerAsn": 62512,
"localIpAddress": "10.191.0.25",
"peerIpAddress": "10.191.0.26",
"password": "cnn6eaeaETSjvjvjvjv",
"importWhitelist": null,
"importBlacklist": null,
"exportWhitelist": null,
"exportBlacklist": null,
"shutdown": false,
"description": "BGP with MED and BFD enabled",
"medIn": 100,
"medOut": 100,
"bfdEnabled": true
},
{
"peerAsn": 62511,
"localIpAddress": "10.191.0.27",
"peerIpAddress": "10.191.0.28",
"password": "cnn23049asdkfj",
"importWhitelist": null,
"importBlacklist": null,
"exportWhitelist": null,
"exportBlacklist": null,
"shutdown": false,
"description": "BGP without MED or BFD",
"medIn": null,
"medOut": null,
"bfdEnabled": false
}
],
"ipRoutes": [
{
"prefix": "10.0.0.0/24",
"nextHop": "10.191.0.26",
"description": "test static route 1"
},
{
"prefix": "10.0.1.9/24",
"nextHop": "10.191.0.27",
"description": "test static route 2"
}
],
"natIpAddresses": []
}
]
}
},
"bEnd": {
"locationId": 57,
"ownerUid": "605cb850-dfb4-4a05-a171-8bf17757b3a2",
"productUid": "d5518ee1-e915-4e3d-a4e1-a2c7e04f2fdd",
"vlan": 0,
"partnerConfig": {
"name": "awshc",
"ownerAccount": "XXXXXXXXXXXX",
"connectType": "AWSHC"
}
},
"productType": "VXC",
"connectType": "AWSHC"
}
]
}
]
```
## Static routes
You can create multiple static routes per interface by adding an `ipRoutes` array to the interfaces array of the A-End partner configuration object:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"ipRoutes": [
{
"prefix": "10.0.0.0/24",
"nextHop": "10.191.0.26",
"description": "test static route 1"
},
{
"prefix": "10.0.1.9/24",
"nextHop": "10.191.0.27",
"description": "test static route 2"
}
],
```
An empty ipRoutes array indicates there are no static routes.
| **Parameter** | **Description** | **Required** | **Valid Input** |
| - | - | - | - |
| prefix | IP prefix (V4 & V6) to route to nextHop | Yes | IP prefix v4/v6 - If no mask is presented address is treated as a host address (/32) |
| nextHop | Next Hop address | Yes | IP Address v4/v6 - Must be in the same subnet as the interface but not the interface IP |
| description | Optional description of the static route | No | String - Max length 100 characters |
## BGP connections
You can create multiple BGP connections per interface by adding a bgpConnections array to the interfaces array of the A-End partner configuration object:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"bgpConnections": [
{
"peerAsn": 62512,
"localIpAddress": "10.191.0.25",
"peerIpAddress": "10.191.0.26",
"password": "cnn6eaeaETSjvjvjvjv",
"importWhitelist": null,
"importBlacklist": null,
"exportWhitelist": null,
"exportBlacklist": null,
"shutdown": false,
"description": "BGP with MED and BFD enabled",
"medIn": 100,
"medOut": 100,
"bfdEnabled": true,
"asOverride": true
},
{
"peerAsn": 62511,
"localIpAddress": "10.191.0.27",
"peerIpAddress": "10.191.0.28",
"password": "cnn23049asdkfj",
"importWhitelist": null,
"importBlacklist": null,
"exportWhitelist": null,
"exportBlacklist": null,
"shutdown": false,
"description": "BGP without MED or BFD",
"asPathPrependCount": "3",
"bfdEnabled": false,
"asOverride": false
}
],
```
| **Parameter** | **Description** | **Required** | **Valid Input** |
| - | - | - | - |
| peerAsn | The ASN of the remote BGP peer. | Yes | Valid ASN - Integers between 1 - 4294967294 |
| localAsn | Local ASN can override the ASN of the MCR for this BGP peer. In most cases it should be left default. | No | Valid ASN - Integers between 1 - 4294967294
localAsn cannot be set if peerAsn == mcrAsn
localAsn cannot match peerAsn if peerAsn != mcrAsn |
| localIpAddress | The IPv4 or IPv6 address on this interface to use for communication with the BGP peer. | Yes | Valid IP address v4/v6. Must be an IP address of the interface |
| peerIpAddress | The IP address of the BGP peer. | Yes | Valid IP address v4/v6 |
| password | A shared key used to authenticate the BGP peer, up to 32 characters. | No | 0-32 characters |
| importWhitelist | Inbound prefix filtering using a permit action. MCR applies the prefix filter to inbound BGP route advertisements from the neighbor. Routes not matching the prefixes on this list are denied at the earliest possible point and are never used by the MCR. | No | 1-100 characters |
| importBlacklist | Inbound prefix filtering using a deny action. MCR applies the prefix filter to inbound BGP route advertisements from the neighbor. Routes matching the prefixes on this list are blocked. All other prefixes are allowed to enter the MCR routing table. | No | 1-100 characters |
| exportWhitelist | Outbound prefix filtering using a permit action. MCR applies the prefix filter to outbound routes. Routes matching the prefix list are advertised to the BGP neighbor and all other routes are filtered. | No | 1-100 characters |
| exportBlacklist | Outbound prefix filtering using a deny action. MCR applies the prefix filter to outbound routes. Routes matching the prefix list are blocked from the BGP neighbor and all other routes are advertised. | No | 1-100 characters |
| shutdown | By default, BGP connections are enabled and will actively attempt to connect to the peer. Select shutdown to temporarily disable the BGP session without removing it. This can be useful for troubleshooting or testing failover scenarios. | No | true/false - Defaults to false |
| description | Optional description of the BGP connection | No | 0-100 characters |
| medIn | The MED will be applied to all routes received on this BGP connection. Leave blank to use the value received from the BGP peer. The route with the lowest value will be preferred. | No | Supports values between 0 and 4,294,967,295 |
| medOut | The MED will be applied to all routes transmitted on this BGP connection. The neighboring autonomous system might prefer the lowest value at their discretion. | No | Supports values between 0 and 4,294,967,295 |
| asPathPrependCount | asPathPrependCount is an integer representing the number of times that the local AS number will be prepended on outgoing BGP announcements to the peer. | No | Acceptable values are in the range 1-10 |
| bfdEnabled | Bidirectional Forwarding Detection allows for rapid fault detection on this BGP connection. When connectivity is disrupted the BGP session is torn down without waiting for the BGP hold timer to expire. BFD might improve fail over time when multiple routes are available. | No | true/false - Defaults to false Optional |
| asOverride | Enables AS Override for eBGP peering. When enabled, replaces the peer's ASN with the local ASN in the AS path. This is useful when connecting sites that share the same ASN. Only valid for eBGP connections. | No | true/false - Defaults to false Optional |
## Bidirectional Forwarding Detection (BFD)
The `bfd` configuration object applies to all BGP connections on the interface that have `bfdEnabled = true`.
The BFD settings are not editable. The default values configured when BFD is enabled are:
* : 300 milliseconds
* : 300 milliseconds
* : 3
These settings will be used for all BGP connections on the VXC where BFD is enabled.
## DHCP pools
You can configure a DHCP server pool on an MCR VXC interface. A DHCP pool enables the MCR to act as a DHCP server, assigning IP addresses to devices connected through the interface.
Add a `dhcpPools` array to the interfaces array of the A-End or B-End partner configuration object:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"dhcpPools": [
{
"network": "192.168.1.0/24",
"startIpAddress": "192.168.1.10",
"endIpAddress": "192.168.1.100",
"defaultGateway": "192.168.1.1",
"description": "Office LAN DHCP pool",
"dnsServers": ["8.8.8.8", "8.8.4.4"]
}
]
```
| **Parameter** | **Description** | **Required** | **Valid Input** |
| - | - | - | - |
| network | The IPv4 network in CIDR notation for the DHCP pool. | Yes | IPv4 CIDR, for example `192.168.1.0/24`. |
| startIpAddress | The first IP address in the range of IP addresses to assign to DHCP clients. | Yes | IPv4 address within the network. |
| endIpAddress | The last IP address in the range of IP addresses to assign to DHCP clients. | Yes | IPv4 address within the network. |
| defaultGateway | The IP address of the default gateway to provide to DHCP clients. | No | IPv4 address. |
| description | A description for the DHCP pool. | No | 0-100 characters. |
| dnsServers | A list of DNS resolver IP addresses to provide to DHCP clients. | No | Array of up to 5 IPv4 addresses. |
* DHCP pools are supported only on MCR products.
* DHCP pools are not supported when the opposite end of the VXC is a Transit or IX connection.
* DHCP pools are not supported on IPsec tunnel interfaces.
* Each interface supports a maximum of one DHCP pool.
## Autoconfiguration with AWS, Azure, and Google
For Azure, AWS Hosted VIF, and Google, Megaport can set up the IP addressing and BGP details on both the MCR and the CSP side ensuring a working BGP setup. This also minimizes the amount of switching between the CSP and Megaport portals.
While the Portal handles the autoconfiguration by default, you can also use the API to trigger the BGP autoconfiguration.
The functionality is triggered when the interfaces key in partnerConfig does not exist or is null.
**To configure BGP peering for CSPs**
1. Create a request with this URL:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
2. Add these headers to the request:
* Content-Type: application/json
* Authorization: Bearer \{your accessToken}
3. Create the Body of the request with the configuration details.
Different templates are available here for the most popular CSPs.
#### AWS Hosted VIF
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"productUid": "{{ mcrid }}",
"associatedVxcs": [
{
"productName": "Test AWS VIF VXC",
"rateLimit": 100,
"term": 12,
"aEnd": {
"vlan": 0
},
"bEnd": {
"productUid": "{{ awsPortUid }}",
"partnerConfig": {
"connectType": "AWS",
"type": "private",
"ownerAccount": "{{ yourAWSAccountNumber }}"
}
}
}
]
}
```
For more information about creating a Hosted VIF, see [Creating a VXC between an MCR and AWS with the API](/api/api-mcr-vxc-aws).
#### Google Cloud
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"productUid": "{{ mcrid }}",
"associatedVxcs": [
{
"productName": "Test Google VXC",
"rateLimit": 100,
"term": 12,
"aEnd": {
"vlan": 0
},
"bEnd": {
"productUid": "{{ googlePortUid }}",
"partnerConfig": {
"connectType": "GOOGLE",
"pairingKey": "{{ googlekey }}"
}
},
"productType": "VXC"
}
]
}
```
#### Microsoft Azure
For Azure configuration details, see [Creating a VXC between an MCR and Microsoft Azure with the API](/api/api-mcr-vxc-azure).
# Creating a Megaport Internet Connection from a Port with the API
Source: https://docs.megaport.com/api/api-mic
This help topic describes how to use the Megaport API to create a Megaport Internet connection from a Port.
This topic describes the API procedure to create a Megaport Internet connection from a Port.
This process includes these steps:
* Look up the A-End `productUid` using GET Product List to identify the Port in your Megaport location.
* Look up the B-End `productUid` using GET Partner Megaports to identify the internet router (Port). Use vxcPermitted *True* and connectType *TRANSIT*.
* Validate the configuration with the required request Body.
* Buy the Megaport Internet connection with the validated request Body.
For more information about creating a Megaport Internet connection for an MVE to provide connectivity, and to register and communicate with the SD-WAN overlay network, see [Megaport Virtual Edge (MVE)](https://dev.megaport.com/#e44a2c7c-a066-4d31-80b9-1a17db837c39) in the API developer portal.
For more information about Megaport Internet connections, see [Megaport Internet Overview](/megaport-internet).
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
**To get the productUid of the Port**
1. In Postman, click **Product Details** in the left navigation and click **GET Product List**.
2. Click **Send**.
3. From the returned product details, locate the `productUid` value for the Port you want to connect from.\
This example uses this Port:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"productName": "GB Megaport Internet Port"
"productUid": "ecdc7ee9-a197-4686-8b16-046cfc07797a"
```
**To get the productUid of the internet router (B-End Port)**
1. In Postman, click **Locations** in the left navigation and click **GET Partner Megaports**.
2. Update the Query Parameters so that connectType is set to *TRANSIT* and vxcPermitted is set to *True*.\
This will return Ports that support a Megaport Internet connection and where new connections are accepted.
3. Click **Send**.
4. From the returned Partner Megaport details, locate the `productUid` value for the internet router or Port you want to connect to.\
This example uses this Port:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"productUid": "874dbcff-a1f9-4328-9c08-112cd87c20f6"
```
**To review pricing details and validate the Megaport Internet connection configuration**
1. In Postman, expand **Connections > Megaport Internet** in the left navigation and click **POST Validate Megaport Internet Order (v3)**.
2. Update the Body with the `productUid` for each end of the connection.\
You can also change additional values, such as name, rate limit, and contract terms.
3. Click **Send** to make a POST request.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/validate
```
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "ecdc7ee9-a197-4686-8b16-046cfc07797a",
"associatedVxcs": [
{
"rateLimit": 10000,
"term": 12,
"productName": "Example Megaport Internet Connection",
"aEnd": {
"productName": "GB Megaport Internet Port"
},
"bEnd": {
"productUid": "874dbcff-a1f9-4328-9c08-112cd87c20f6"
},
"productType": "VXC",
"connectType": "TRANSIT",
"shutdown": false,
"promoCode": "promox3mnthfree2"
}
]
}
]
```
After you validate the request and review the pricing details in the response, order the Megaport Internet connection.
**To order the Megaport Internet connection**
1. Copy the validated Body from **POST Validate Megaport Internet Order (v3)** and paste it into the Body of **POST Buy Megaport Internet (v3)**.
2. Click **Send** to post the request.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
The resulting Megaport Internet connection appears in the Megaport Portal.
# Creating an MVE with the API
Source: https://docs.megaport.com/api/api-mve
This help topic describes how to use the Megaport API to create a Megaport Virtual Edge (MVE).
This topic describes the API procedure to create a Megaport Virtual Edge (MVE), including how to look up a deployment location, check available vendor images, and validate and complete the order.
Creating an MVE with the API involves these steps:
1. **Look up the MVE location** -- Identify a location where MVE is available and note its location ID.
2. **Check available MVE images** -- Retrieve the vendor images and software versions available for MVE.
3. **Validate the order** -- Test your configuration and review pricing before you order.
4. **Order the MVE** -- Submit the validated configuration to create the MVE.
You select the vendor appliance and software version through the required `imageId` field, taken from the images endpoint. There is no `vendor` field in the request. Each vendor also requires specific fields inside the `vendorConfig` object. For more information, see [Vendor-specific configurations](#vendor-specific-configurations).
Every request in this workflow requires the `Authorization: Bearer ` header, including the two GET requests that look up locations and images. You reuse the same access token for every request. The requests use the `{baseUrl}` placeholder. Replace it with the production or staging API host. For more information, see [Environments](/api#environments).
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
For more information about the APIs and parameters mentioned in this topic, see the API reference at
[https://dev.megaport.com](https://dev.megaport.com).
## Look up MVE location details
To create an MVE, first identify a location where MVE is available. The location response includes `mveAvailable` in each diversity zone to indicate MVE support.
**To look up MVE location details**
1. Send a GET request to the locations endpoint.
This request requires no parameters or request body.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/locations
```
Confirm the request was successful by looking for Status: 200 OK.
The request returns hundreds of Megaport locations.
2. Search the response for a site where `mveAvailable` is `true` in the `diversityZones` object.
To provision an MVE at a location, `mveAvailable` must be `true` in at least one diversity zone.
```json {2,24,30} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"id": 60,
"name": "CoreSite LA1",
"address": {
"street": "624 South Grand Avenue",
"suburb": null,
"city": "Los Angeles",
"state": "CA",
"postcode": "90017",
"country": "USA"
},
"dataCentre": {
"id": 18,
"name": "CoreSite"
},
"metro": "Los Angeles",
"market": "US",
"status": "Active",
"diversityZones": {
"red": {
"mcrSpeedMbps": [2500, 5000, 10000, 1000],
"megaportSpeedMbps": [1000, 10000, 100000],
"mveMaxCpuCoreCount": null,
"mveAvailable": true
},
"blue": {
"mcrSpeedMbps": [5000, 1000, 2500, 10000],
"megaportSpeedMbps": [1000, 100000, 10000],
"mveMaxCpuCoreCount": null,
"mveAvailable": true
}
}
}
```
To create an MVE, you need the `id` value. In this example, the location ID is 60.
## Check available MVE images
Before you create an MVE, retrieve the list of available vendor images. This endpoint returns the vendors and software versions available for MVE.
Send a GET request to the images endpoint.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v4/product/mve/images
```
The response groups the available MVE images by vendor and product under `mveImages`. The following example is representative and is trimmed to a few vendor groups.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "MVE images",
"terms": "This data is subject to the Acceptable Use Policy...",
"data": {
"mveImages": [
{
"vendor": "6WIND",
"product": "6WIND Virtual Service Router",
"vendorProductId": 1,
"images": [
{
"id": 46,
"version": "6.0",
"productCode": "6wind-mve",
"releaseImage": true,
"availableSizes": ["MVE 2/8", "MVE 4/16", "MVE 8/32"],
"vendorDescription": "6WIND Virtual Service Router"
}
]
},
{
"vendor": "ARUBA",
"product": "Aruba EC-V",
"vendorProductId": 2,
"images": [
{
"id": 67,
"version": "ECOS-V 9.3",
"productCode": "aruba-ecv-v2",
"releaseImage": true,
"availableSizes": ["MVE 2/8", "MVE 4/16", "MVE 8/32"],
"vendorDescription": "Aruba EdgeConnect SD-WAN"
}
]
},
{
"vendor": "PALO_ALTO",
"product": "Palo Alto VM-Series",
"vendorProductId": 3,
"images": [
{
"id": 52,
"version": "11.1",
"productCode": "palo-vm",
"releaseImage": true,
"availableSizes": ["MVE 2/8", "MVE 4/16", "MVE 8/32"],
"vendorDescription": "Palo Alto VM-Series"
}
]
}
]
}
}
```
Each group carries the `vendor` code and `product` name, and lists the software versions under `images`. Note the `id` value for the image you want to deploy. The image `id` selects both the vendor appliance and the software version, and it is passed as `imageId` when you create the MVE. The `vendorProductId` in the response is informational only; you do not include it in the order body.
## Validate the MVE order
Before you order, validate the configuration to confirm that it passes validation and to review pricing.
**To test and validate the MVE order**
1. Send a POST request to the validate endpoint with the request body.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/validate
```
2. Confirm the response returns "Validation passed" and review the pricing details.
The request body is a JSON array that contains one order object. This example validates a 6WIND MVE.
```json {8,9,10} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"locationId": 60,
"productName": "Test MVE",
"productType": "MVE",
"term": 12,
"promoCode": null,
"vendorConfig": {
"imageId": 46,
"mveLabel": "MVE 4/16",
"sshPublicKey": "ssh-rsa AAAA...user@host"
},
"vnics": [
{ "description": "Data Plane" }
]
}
]
```
The following table describes the request parameters.
| Parameter | Required | Description |
| :- | :- | :- |
| locationId | Required | The `id` of the location where you deploy the MVE, from the locations endpoint. |
| productName | Required | A name for the MVE. |
| productType | Required | Must be `MVE`. |
| term | Required | The contract term in months: 1, 12, 24, 36, 48, or 60. |
| promoCode | Optional | A promotional code, or `null` if none applies. |
| vendorConfig | Required | The configuration object for the MVE. It holds `imageId`, the size field, and the vendor-specific fields together, with no `vendor` field. See [Vendor-specific configurations](#vendor-specific-configurations). |
| vendorConfig.imageId | Required | The `id` of the vendor image from the images endpoint. This value selects both the vendor appliance and the software version. |
| vendorConfig.mveLabel | Required | The instance size, for example `MVE 4/16`. See [Instance sizes](#instance-sizes). |
| vendorConfig.productSize | Optional | Deprecated. A legacy alternative to `mveLabel`, retained for backward compatibility. See [Instance sizes](#instance-sizes). |
| vnics | Optional | An array of vNIC objects, as a sibling of `vendorConfig`. If omitted, the vendor's minimum number of vNICs is allocated automatically. See [vNIC configuration](#vnic-configuration). |
A successful response passes validation and includes pricing details.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Validation passed",
"terms": "This data is subject to the Acceptable Use Policy...",
"data": [
{
"price": {
"monthlyRate": 500.00,
"currency": "USD",
"productType": "MVE"
},
"serviceName": "Test MVE",
"productType": "MVE",
"productUid": "78aebd6b-7601-4331-82bc-dcd07f9f21a6"
}
]
}
```
## Order the MVE
After validating the request and reviewing the pricing, place the same order object in the `networkDesign` array of the v4 request body, then POST the request to the buy endpoint to create the MVE.
**To order the validated MVE**
1. Send a POST request to the order endpoint with the v4 request body shown below.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v4/networkdesign/buy
```
If you make this call on api.megaport.com, your account will be charged for the service. Alternatively, you can use the API in the staging (test) environment without charges, as in these examples.
2. Review the response to confirm the MVE was created.
The v4 request body is an envelope object that wraps the order object in a `networkDesign` array. This example orders a standalone 6WIND MVE.
```json {2,18,19} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"networkDesign": [
{
"locationId": 60,
"productName": "Test MVE",
"productType": "MVE",
"term": 12,
"promoCode": null,
"vendorConfig": {
"imageId": 46,
"mveLabel": "MVE 4/16",
"sshPublicKey": "ssh-rsa AAAA...user@host"
},
"vnics": [
{ "description": "Data Plane" }
]
}
],
"discountCodes": []
}
```
The following table describes the envelope parameters.
| Parameter | Required | Description |
| :- | :- | :- |
| networkDesign | Required | The array of order objects to create. Place the MVE order object you validated here. For its inner fields, see [Validate the MVE order](#validate-the-mve-order). |
| discountCodes | Required | Include discount-code strings, or an empty array when no discount applies. |
| solutions | Optional | An array used only when the order includes bundled products in the same request. Omit it when you order a standalone MVE. |
A successful response confirms the MVE was created.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "MVE [426fa830-4b66-41ad-95a1-197d55e074b1] created.",
"terms": "This data is subject to the Acceptable Use Policy...",
"data": [
{
"serviceName": "Test MVE",
"technicalServiceUid": "426fa830-4b66-41ad-95a1-197d55e074b1",
"productType": "MVE",
"provisioningStatus": "DEPLOYABLE",
"contractTermMonths": 12
}
]
}
```
The new MVE appears in your working environment, either portal.megaport.com or portal-staging.megaport.com.
For the authoritative list of endpoints and parameters, and to confirm the current endpoint version, see [https://dev.megaport.com](https://dev.megaport.com).
## Vendor-specific configurations
Each MVE vendor requires specific fields inside the `vendorConfig` object. The `vendorConfig` object contains no `vendor` key, the vendor appliance is chosen by the `imageId` value. Find your vendor below for its configuration requirements.
The per-vendor examples below show only the vendor-specific fields. In a real order, the `vendorConfig` object also includes `imageId` and the size field (`mveLabel`) alongside these fields. A complete order can also include the top-level `vnics` array, a sibling of `vendorConfig`, to control the number and naming of vNICs. If you omit `vnics`, the vendor's minimum number of vNICs is allocated automatically. For more information, see [Validate the MVE order](#validate-the-mve-order).
Obtain vendor licenses and credentials from the vendor. Consult the vendor's documentation for vNIC requirements. Available sizes and vendors vary by location. For more information, see [https://dev.megaport.com](https://dev.megaport.com).
### 6WIND VSR
6WIND Virtual Service Router (VSR) requires an SSH public key for administrative access.
Prerequisites:
* Valid 6WIND license, obtained from 6WIND.
* SSH public key (RSA 2048-bit, in OpenSSH or RFC4716 format).
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"sshPublicKey": "ssh-rsa AAAA...user@host"
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| sshPublicKey | Required | RSA 2048-bit public SSH key in OpenSSH or RFC4716 format, for administrative access. |
### Anapaya Alliance
Anapaya Alliance requires an SSH public key for administrative access.
Prerequisites:
* Valid Anapaya license.
* SSH public key (RSA 2048-bit).
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"sshPublicKey": "ssh-rsa AAAA...user@host"
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| sshPublicKey | Required | RSA 2048-bit public SSH key for administrative access. |
### Arista VeloCloud
Arista VeloCloud requires SSH access and activation against your VeloCloud Orchestrator.
Prerequisites:
* Valid Arista VeloCloud license.
* Access to your VeloCloud Orchestrator.
* SSH public key (RSA 2048-bit).
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"sshPublicKey": "ssh-rsa AAAA...user@host",
"vcoAddress": "orchestrator.example.com",
"vcoActivationCode": ""
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| sshPublicKey | Required | RSA 2048-bit public SSH key for administrative access. |
| vcoAddress | Required | The IPv4 address, IPv6 address, or FQDN of your VeloCloud Orchestrator. |
| vcoActivationCode | Required | The activation code for the edge device from the Orchestrator. |
### Aruba EC-V
Aruba EdgeConnect Virtual (EC-V) requires your Orchestrator account credentials.
Prerequisites:
* Valid Aruba EdgeConnect license.
* Aruba Orchestrator account name and account key.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"accountName": "",
"accountKey": ""
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| accountName | Required | The account name from your Aruba Orchestrator or CSP account. |
| accountKey | Required | The account key from your Aruba Orchestrator or CSP account. |
### Aviatrix
Aviatrix requires a cloud-init configuration file from your Aviatrix Controller.
Prerequisites:
* Aviatrix Controller with the appropriate edge license.
* Cloud-init configuration file from the controller.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"cloudInit": ""
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| cloudInit | Required | Base64-encoded cloud-init configuration file from your Aviatrix Controller. |
### Check Point CloudGuard
Check Point CloudGuard requires an administrator password and an SSH public key.
Prerequisites:
* Valid Check Point CloudGuard license.
* SSH public key (RSA 2048-bit).
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"adminPassword": "",
"sshPublicKey": "ssh-rsa AAAA...user@host"
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| adminPassword | Required | Plain text administrator password, 9 to 100 characters. The double-quote, carriage return, and line feed characters are not permitted. |
| sshPublicKey | Required | RSA 2048-bit public SSH key for administrative access. |
### Cisco
Cisco offers multiple MVE appliances. Select the configuration for your deployment model.
#### Cisco C8000 SD-WAN mode
Cisco C8000 in SD-WAN mode joins a Cisco Catalyst SD-WAN overlay and requires a cloud-init configuration.
Prerequisites:
* Cisco SD-WAN subscription and vManage access.
* Cloud-init configuration file.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"cloudInit": ""
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| cloudInit | Required | Base64-encoded cloud-init configuration file. |
Cisco SD-WAN MVEs are typically created through vManage rather than through the Megaport API directly. For more information, see [Creating an MVE Integrated with Cisco SD-WAN](/mve/cisco/creating/creating-mve).
#### Cisco C8000 autonomous mode
Cisco C8000 in autonomous mode operates as a standalone router and requires an SSH public key.
Prerequisites:
* Valid Cisco C8000V license.
* SSH public key (RSA 2048-bit).
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"sshPublicKey": "ssh-rsa AAAA...user@host"
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| sshPublicKey | Required | RSA 2048-bit public SSH key for administrative access. |
#### Cisco Secure Firewall Threat Defense Virtual (FTDV)
Cisco Secure Firewall Threat Defense Virtual (FTDV) requires an administrator password and a management mode. When you manage the firewall through a Firewall Management Center (FMC), set `manageLocally` to `false` and provide the FMC details.
Prerequisites:
* Valid Cisco Secure Firewall license.
* For remote management, a reachable Firewall Management Center (FMC).
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"adminPassword": "",
"manageLocally": false,
"fmcIpAddress": "198.51.100.10",
"fmcRegistrationKey": "",
"fmcNatId": ""
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| adminPassword | Required | Plain text administrator password, 9 to 100 characters. The double-quote, carriage return, and line feed characters are not permitted. |
| manageLocally | Required | Boolean. Set to `true` to manage the firewall locally, or `false` to manage it through an FMC. |
| fmcIpAddress | Required when `manageLocally` is `false` | The IPv4 address, IPv6 address, or FQDN of the FMC. |
| fmcRegistrationKey | Required when `manageLocally` is `false` | FMC registration key, 1 to 37 characters. Allowed characters are A-Z, a-z, 0-9, and hyphen. |
| fmcNatId | Optional | NAT ID for FMC registration, 1 to 37 characters, using the same character set as `fmcRegistrationKey`. Applicable only when `manageLocally` is `false`. |
Cisco Secure Firewall does not support the MVE 2/8 size.
#### Cisco Meraki vMX
Cisco Meraki vMX requires an authentication token from the Meraki dashboard.
Prerequisites:
* Valid Meraki SD-WAN license.
* Authentication token from the Meraki dashboard.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"token": ""
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| token | Required | The API token generated in the Cisco Meraki dashboard. |
### F5 BIG-IP
F5 BIG-IP requires an administrator password hash and an SSH public key.
Prerequisites:
* Valid F5 BIG-IP license.
* SSH public key (RSA 2048-bit or ED25519).
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"adminPasswordHash": "$6$example...sha512crypt...hash",
"adminSshPublicKey": "ssh-rsa AAAA...user@host"
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| adminPasswordHash | Required | sha512crypt hash of the administrator password. |
| adminSshPublicKey | Required | Public SSH key (RSA 2048-bit or ED25519) for administrative access. |
### Fortinet FortiGate-VM
Fortinet FortiGate-VM requires an SSH public key and optionally a license file.
Prerequisites:
* SSH public key (RSA 2048-bit).
* Optionally, a FortiGate-VM license file. If you do not provide one, apply a license after deployment, for example through FortiFlex.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"sshPublicKey": "ssh-rsa AAAA...user@host",
"licenseData": ""
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| sshPublicKey | Required | RSA 2048-bit public SSH key for administrative access. |
| licenseData | Optional | Base64-encoded license file. If omitted, apply a license after deployment or use FortiFlex. |
### Juniper
Juniper offers two MVE appliances. Select the configuration for your product.
#### Juniper SSR
Juniper Session Smart Router (SSR) requires a registration code from Juniper.
Prerequisites:
* Juniper Mist subscription.
* Registration code from Juniper.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"registrationCode": ""
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| registrationCode | Required | Registration code from Juniper. |
#### Juniper vSRX
Juniper vSRX requires an administrator password hash and an SSH public key, with optional Mist onboarding.
Prerequisites:
* Valid Juniper vSRX license.
* SSH public key (RSA 2048-bit).
* Optionally, Juniper Mist onboarding details.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"adminPasswordHash": "$6$example...sha512crypt...hash",
"adminSshPublicKey": "ssh-rsa AAAA...user@host",
"mistDeviceId": "00000000-0000-4000-8000-000000000000",
"mistPasswordHash": "$6$example...sha512...hash",
"mistSecret": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
"mistSshPublicKey": "ssh-rsa AAAA...user@host"
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| adminPasswordHash | Required | sha512crypt hash of the administrator password. |
| adminSshPublicKey | Required | RSA 2048-bit public SSH key for administrative access. |
| mistDeviceId | Optional | Juniper Mist device ID (UUID version 4). |
| mistPasswordHash | Optional | SHA-512 hash for Mist onboarding. |
| mistSecret | Optional | Mist secret, a 128-character lowercase hexadecimal string. |
| mistSshPublicKey | Optional | RSA 3072-bit public SSH key for Mist onboarding. |
### Netskope One Edge
Netskope One Edge requires an SSH public key and an administrator password hash, with optional activation details.
Prerequisites:
* Valid Netskope One license.
* SSH public key (RSA 2048-bit).
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"adminSshPublicKey": "ssh-rsa AAAA...user@host",
"adminPasswordHash": "$6$example...sha512...hash",
"activationToken": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
"activationUri": "https://example.goskope.com/activation"
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| adminSshPublicKey | Required | RSA 2048-bit public SSH key for administrative access. |
| adminPasswordHash | Required | SHA-512 hash of the administrator password. |
| activationToken | Optional | 64-character hexadecimal activation token. If provided, `activationUri` is also required. |
| activationUri | Optional | Activation URI. If provided, `activationToken` is also required. |
### OPNsense
OPNsense from Deciso requires an SSH public key and a bcrypt administrator password hash.
Prerequisites:
* Valid OPNsense license from Deciso.
* SSH public key (RSA 2048-bit, RSA 4096-bit, or ED25519).
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"adminSshPublicKey": "ssh-rsa AAAA...user@host",
"adminPasswordHash": "$2y$11$exampleBcryptHashPaddedToFiftyThreeCharacters01234567"
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| adminSshPublicKey | Required | Public SSH key (RSA 2048-bit, RSA 4096-bit, or ED25519) for administrative access. |
| adminPasswordHash | Required | bcrypt hash in the format `$2y$NN$` followed by 53 characters, 60 characters in total. |
### Peplink Fusion Hub
Peplink Fusion Hub requires an administrator password hash and a valid Peplink Fusion Hub license.
Prerequisites:
* Valid Peplink Fusion Hub license.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"adminPasswordHash": "0000000000000000000000000000000000000000",
"licenseData": "EXAMPLE1LICENSE9"
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| adminPasswordHash | Required | SHA-1 hash of the administrator password, 40 hexadecimal characters. |
| licenseData | Required | License, exactly 16 alphanumeric characters. |
### Palo Alto
Palo Alto Networks offers two MVE appliances. Select the configuration for your product.
#### Palo Alto Prisma SD-WAN
Palo Alto Networks Prisma SD-WAN requires an ION key and a secret key from your Prisma SD-WAN controller.
Prerequisites:
* Valid Prisma SD-WAN license.
* ION key and secret key from the Prisma SD-WAN controller.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"ionKey": "0000000000-00000000-0000-0000-0000-000000000000",
"secretKey": "0000000000000000000000000000000000000000"
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| ionKey | Required | ION key. Format: 10 hexadecimal characters, hyphen, 8 hexadecimal, hyphen, 4, hyphen, 4, hyphen, 4, hyphen, 12 hexadecimal. |
| secretKey | Required | Secret key, 40 hexadecimal characters. |
Prisma SD-WAN is available as two models. The 3108v model supports the MVE 2/8, MVE 4/16, and MVE 8/32 sizes. The 7108v model supports the MVE 8/32 size only.
#### Palo Alto VM-Series
Palo Alto Networks VM-Series requires an SSH public key and an administrator password hash, with an optional authorization code.
Prerequisites:
* Valid VM-Series license (authorization code).
* SSH public key (RSA 2048-bit).
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"sshPublicKey": "ssh-rsa AAAA...user@host",
"adminPasswordHash": "$5$example...sha256crypt...hash",
"licenseData": "000000000"
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| sshPublicKey | Required | RSA 2048-bit public SSH key for administrative access. |
| adminPasswordHash | Required | sha256crypt hash of the administrator password. |
| licenseData | Optional | VM-Series authorization code, 8 or 9 digits. Leading zeros are allowed. |
### Versa FlexVNF
Versa FlexVNF requires Director and Controller addresses and authentication identifiers.
Prerequisites:
* Valid Versa license.
* Access to your Versa Director and Controller.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"directorAddress": "director.example.com",
"controllerAddress": "controller.example.com",
"localAuth": "branch-01@example.com",
"remoteAuth": "controller-01@example.com",
"serialNumber": ""
}
```
| Parameter | Required | Description |
| :- | :- | :- |
| directorAddress | Required | The IPv4 address or FQDN of the Versa Director. |
| controllerAddress | Required | The IPv4 address or FQDN of the Versa Controller. |
| localAuth | Required | Local authentication identifier, an ID string or email, up to 100 characters. |
| remoteAuth | Required | Remote authentication identifier, an ID string or email, up to 100 characters. |
| serialNumber | Required | The device serial number, up to 100 characters. |
## Instance sizes
MVE instances are available in different sizes. Specify the size using the `mveLabel` field. The `productSize` field is a deprecated, legacy alternative that is retained for backward compatibility.
| Size (mveLabel) | Legacy productSize | vCPU | RAM |
| :- | :- | :- | :- |
| MVE 2/8 | SMALL | 2 | 8 GB |
| MVE 4/16 | MEDIUM | 4 | 16 GB |
| MVE 8/32 | LARGE | 8 | 32 GB |
| MVE 16/64 | X\_LARGE\_16 | 16 | 64 GB |
| MVE 32/128 | X\_LARGE\_32 | 32 | 128 GB |
Available sizes depend on the vendor and location. Confirm the sizes available for your deployment with the [MVE images endpoint](#check-available-mve-images) or the product variants endpoint (`{baseUrl}/v3/product/mve/variants`).
The following per-vendor size restrictions apply:
* Cisco Secure Firewall does not support the `MVE 2/8` size.
* Palo Alto Prisma SD-WAN 3108v supports the `MVE 2/8`, `MVE 4/16`, and `MVE 8/32` sizes.
* Palo Alto Prisma SD-WAN 7108v supports the `MVE 8/32` size only.
## vNIC configuration
Each MVE has 1 to 5 virtual network interfaces (vNICs). The maximum is 5 for all vendors, except Arista VeloCloud and Check Point, which support only 1, and Cisco Meraki vMX, which supports only 2. The number of vNICs cannot be changed after the MVE is created.
Provide the vNICs in the `vnics` array, as a sibling of `vendorConfig` on the order object. This example is trimmed to show the placement.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"vendorConfig": {
"imageId": 46,
"mveLabel": "MVE 4/16",
"sshPublicKey": "ssh-rsa AAAA...user@host"
},
"vnics": [
{ "description": "Data Plane" },
{ "description": "Management Plane" }
]
}
```
The following table describes the vNIC parameters.
| Parameter | Required | Description |
| :- | :- | :- |
| vnics | Optional | An array of 1 to 5 vNIC objects, as a sibling of `vendorConfig`. The maximum is 5. Per-vendor minimums are listed in the following note. If omitted, the vendor's minimum number of vNICs is allocated automatically. |
| description | Optional | A label for the vNIC, for example `Data Plane` or `Management Plane`. |
Consult your vendor's documentation for vNIC requirements. The confirmed per-vendor minimums are:
* **6WIND VSR** -- minimum 1
* **Anapaya Alliance** -- minimum 1
* **Arista VeloCloud** -- exactly 1
* **Aruba EC-V** -- minimum 2
* **Aviatrix** -- minimum 1
* **Check Point CloudGuard** -- exactly 1
* **Cisco C8000** (autonomous and SD-WAN) -- minimum 1
* **Cisco Secure Firewall (FTDV)** -- minimum 4
* **Cisco Meraki vMX** -- exactly 2
* **F5 BIG-IP** -- minimum 1
* **Fortinet FortiGate-VM** -- minimum 1
* **Juniper SSR** -- minimum 3
* **Juniper vSRX** -- minimum 2
* **Netskope One Edge** -- minimum 1
* **OPNsense** -- minimum 2
* **Palo Alto Prisma SD-WAN** -- minimum 4 (3108v) or 3 (7108v)
* **Palo Alto VM-Series** -- minimum 2
* **Versa FlexVNF** -- minimum 1
## Next steps
After you create an MVE, the next steps include:
* Create a Megaport Internet connection for management and initial setup. For more information, see [Megaport Internet Overview](/megaport-internet).
* Connect VXCs to Cloud Service Providers. For more information, see:
* [Creating a VXC between an MVE and AWS with the API](/api/api-mve-vxc-aws)
* [Creating a VXC between an MVE and Azure with the API](/api/api-mve-vxc-azure)
* [Creating a VXC between an MVE and Google Cloud with the API](/api/api-mve-vxc-google)
## Helpful references
* [Creating a Megaport Internet Connection for an MVE](/megaport-internet/mve)
* [Megaport API Documentation](https://dev.megaport.com)
* [Megaport Virtual Edge Locations](/mve/locations)
* [MVE Overview](/mve)
* [Types of vNIC Connections](/mve/vnic-connections)
# Creating a VXC between an MVE and AWS with the API
Source: https://docs.megaport.com/api/api-mve-vxc-aws
This help topic describes how to use the Megaport API to create a VXC between a Megaport Virtual Edge (MVE) and AWS Direct Connect.
This topic describes the API procedure to create a VXC from an MVE to AWS, including how to look up AWS locations and order VXCs on specific vNICs.
You can set up two types of AWS connections to an MVE: an AWS Hosted VIF and an AWS Hosted Connection.
You can distinguish the type of connection supported by partner locations using the connectType parameter. Hosted VIF connections are connectType=AWS and Hosted Connections are connectType=AWSHC.
The MVE to AWS deployment includes these tasks:
1. **Look up AWS location details**
To create a VXC to AWS, you first need to identify the `productUid` of the port you want to connect to.
You can look up AWS locations for the B-End of the connection with the `v2/dropdowns/partner/megaports` endpoint.
2. **Create and deploy a VXC**
With the port details identified, you can create the VXC to AWS from the MVE.
Configuration details are specified in the Body of the request. Some of the key information you need to specify include the `productUid` of the MVE, the `productUid` of the AWS port, and the AWS account ID.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
## Look up AWS location details
Use the API to look up the `productUid` of the port you want to connect to. The response includes details of the available ports. You need the port details to create the VXC.
In the API response, available ports that accept VXCs are listed as `"vxcPermitted": true`.
**To look up AWS location details**
1. Expand the **Locations** folder in the left navigation and click **GET Partner Megaports**.
2. Click **Send** to make a GET request to the API server.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/dropdowns/partner/megaports
```
This request returns all the interfaces Megaport has with Cloud Service Providers. You can search by clicking the magnifying glass and entering a location, data center, or other parameter in the search field.
The connectType indicates the Cloud Service Provider. AWS includes "AWS" for Hosted VIFs and "AWSHC" for Hosted Connections.
You can filter the results by `connectType` and `vxcPermitted`.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/dropdowns/partner/megaports?connectType=AWS&vxcPermitted=true
```
This example uses a port in the region eu-west-2 (London) that accepts VXCs (`"vxcPermitted": true`).
```json {2,5,9} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"productUid": "b9dcbdca-b73a-4fc9-9ac9-98cecde81ba2",
"companyUid": "605cb850-dfb4-4a05-a171-8bf17757b3a2",
"companyName": "AWS",
"title": "EU (London) (eu-west-2)",
"locationId": 90,
"speed": 10000,
"maxVxcSpeed": 10000,
"vxcPermitted": true,
"diversityZone": null,
"rank": 378,
"lag_id": null,
"lag_primary": false,
"aggregation_id": null,
"connectType": "AWS"
},
```
## Create and deploy a VXC Hosted VIF
With the port details, create the VXC to AWS from the MVE.
You specify the configuration details in the Body of the request. The first `productUid` identifies the MVE ID and the `bEnd: productUid` identifies the AWS port location from the Partner Megaports lookup. You also need to provide your AWS account number in the request.
This example uses the Hosted VIF connection type, connectType=AWS.
To test your request before you order and see pricing details, use the `/v3/networkdesign/validate` endpoint with the same Body configuration.
**To create a VXC**
1. Create a request with the **POST Buy AWS - Hosted VIF (v3)** endpoint:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
2. Update the Body of the request with the `productUid` of the MVE, the name of the VXC, the `productUid` of the AWS port, and the AWS account ID (`ownerAccount`).\
You can also change additional values, such as rate limit, contract term, VLAN ID, ASN values, authKey, and IP addressing. The vNIC is determined by `vNicIndex`, innerVlan identifies VLAN number run within the vNIC, in this case 103.
The vNIC number relates to the following MVE interfaces:
* vNIC 0 = interface 1 on the MVE
* vNIC 1 = interface 2 on the MVE
* vNIC 2 = interface 3 on the MVE
* vNIC 3 = interface 4 on the MVE
* vNIC 4 = interface 5 on the MVE
Here is a sample request:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "{ mveid }",
"associatedVxcs": [
{
"productName": "Test AWS VIF MVE VXC",
"rateLimit": "100",
"term": 12,
"shutdown": false,
"promoCode": "promox3mnthfree2",
"aEnd": {
"vNicIndex":2,
"vlan": null,
"innerVlan": 103
},
"bEnd": {
"productUid": "{ awsPortUid }",
"partnerConfig": {
"connectType": "AWS",
"Name": "Test Megaport",
"type": "private",
"asn": 65105,
"ownerAccount": "XXXXXXXXXXXX",
"authKey": "123455",
"customerIpAddress": null,
"amazonIpAddress": null
}
}
}
]
}
]
```
After sending the request, you will receive a successful response when the VXC has been ordered.
Here is a sample response:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "VXC [0d22feee-8d06-4041-98be-5b827c33c78a] created.",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"createDate": 1709811450016,
"vxcOrderId": 139933,
"payerMegaPortId": 190079,
"nonPayerMegaPortId": 6199,
"payerMegaPortName": "MVE for VNIC config",
"nonPayerMegaPortName": "EU (London) (eu-west-2)",
"payerCompanyId": 1153,
"nonPayerCompanyId": 117,
"payerLocationId": 89,
"nonPayerLocationId": 89,
"salesId": null,
"payerCompanyName": "Megaport Lab",
"nonPayerCompanyName": "AWS",
"payerMegaPortNsId": 510708,
"nonPayerMegaPortNsId": 13055,
"payerVlanId": 0,
"nonPayerVlanId": 0,
"payerInnerVlanId": 103,
"nonPayerInnerVlanId": null,
"payerApproverName": "name",
"payerApproverId": number,
"nonPayerApproverName": "name",
"nonPayerApproverId": number,
"payerApproval": number,
"nonPayerApproval":number,
"fixedTerm": true,
"duration": 1,
"rollover": true,
"serviceName": "from MVE for VNIC config to EU (London) (eu-west-2)",
"payerStatus": "APPROVED",
"nonPayerStatus": "APPROVED",
"speed": 100,
"distanceBand": "METRO",
"intercapPath": "",
"awsId": null,
"promoCode": null,
"rateType": "MONTHLY",
"vxcJTechnicalServiceId": 190085,
"vxcJTechnicalServiceUid": "0d22feee-8d06-4041-98be-5b827c33c78a",
"provisionDate": 1709811449985,
"orderType": "NEW",
"monthlyDiscountAmount": null,
"discountMonths": null,
"amazonDirectConnectConfigDto": {
"type": "private",
"asn": 65105,
"ownerAccount": "aws account ID",
"authKey": "123455",
"customerIpAddress": null,
"amazonIpAddress": null,
"prefixes": null,
"name": null
},
"amsixConnectConfigDto": null,
"sdrcProvItem": null,
"rate": null,
"setup": null,
"asn": null,
"bgpPassword": null,
"usageAlgorithm": "POST_PAID_HOURLY_SPEED_METRO_VXC",
"costCentre": null,
"azureServiceKey": null,
"oracleVirtualCircuitId": null,
"serviceKey": null,
"vxc": {
"serviceName": "Test AWS VIF MVE VXC",
"name": "Test AWS VIF MVE VXC",
"secondaryName": null,
"technicalServiceId": 190085,
"technicalServiceUid": "0d22feee-8d06-4041-98be-5b827c33c78a",
"requestedDate": 1709811449985,
"configuredDate": null,
"currentEstimatedDelivery": null,
"companyName": "Megaport Lab",
"companyId": 1153,
"billingContactName": null,
"billingContactId": null,
"adminContactName": null,
"adminContactId": null,
"technicalContactName": null,
"technicalContactId": null,
"salesName": null,
"salesId": null,
"billableId": 181633,
"billableUsageAlgorithm": null,
"productType": "VXC",
"provisioningStatus": "DEPLOYABLE",
"failedReason": null,
"inAdvanceBillingStatus": null,
"provisioningItems": [],
"tags": [],
"vxcDistanceBand": "METRO",
"intercapPath": "",
"marketplaceVisibility": true,
"vxcPermitted": true,
"vxcAutoApproval": false,
"createDate": 1709811450003,
"terminationDate": null,
"contractStartDate": null,
"contractTermMonths": 1,
"rateType": "MONTHLY",
"trialAgreement": false,
"payerCompanyId": null,
"nonPayerCompanyId": null,
"minimumSpeed": null,
"maximumSpeed": null,
"rateLimit": 100,
"errorMessage": null,
"lagId": null,
"aggregationId": null,
"lagPrimary": null,
"market": "UK",
"accountManager": null,
"promptUid": null,
"components": [],
"attributes": [],
"aLocation": null,
"bLocation": null,
"aMetro": null,
"aCountry": null,
"aLocationId": null,
"bLocationId": null,
"bMetro": null,
"bCountry": null,
"attributeTags": {},
"createdBy": "b0dedbd2-ecc7-4bad-a13b-6c34b4005115",
"buyoutPort": null,
"virtual": false,
"locked": false,
"adminLocked": false,
"bgpShutdownDefault": false
},
"connectType": "AWS",
"payerConfig": {},
"nonPayerConfig": {},
"attributeTags": {},
"serviceLicense": null,
"fullyApproved": true
}
]
}
```
The VXC will now appear in the Megaport Portal.
For this example, the AWS Hosted VIF will appear in the AWS portal account under Direct Connect - Virtual Interfaces. The account holder can accept the Virtual Interface and connect it to a Virtual Private Gateway or a Direct Connect Gateway and then to their VPCs.
## Create and deploy a VXC Hosted Connection
With the port details, create the VXC to AWS from the MVE.
You specify the configuration details in the Body of the request. The first `productUid` identifies the MVE ID and the `bEnd: productUid` identifies the AWS port location from the Partner Megaports lookup. You also need to provide your AWS account number in the request.
This example uses the Hosted Connection connection type, connectType=AWSHC.
To test your request before you order and see pricing details, use the `/v3/networkdesign/validate` endpoint with the same Body configuration.
**To create a VXC**
1. Create a request with the **POST Buy AWS - Hosted Connection (v3)** endpoint:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
2. Update the Body of the request with the `productUid` of the MVE, the name of the VXC, the `productUid` of the AWS port, and the AWS account ID (`ownerAccount`).\
You can also change additional values, such as rate limit, contract term, VLAN ID, ASN values, authKey, and IP addressing. The vNIC is determined by `vNicIndex`, innerVlan identifies VLAN number run within the vNIC, in this case 666.
The vNIC number relates to the following MVE interfaces:
* vNIC 0 = interface 1 on the MVE
* vNIC 1 = interface 2 on the MVE
* vNIC 2 = interface 3 on the MVE
* vNIC 3 = interface 4 on the MVE
* vNIC 4 = interface 5 on the MVE
Here is a sample request:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "{ mveid }",
"associatedVxcs": [
{
"productName": "Test AWS over Vnic2",
"rateLimit": 100,
"term": 12,
"shutdown": false,
"promoCode": "promox3mnthfree2",
"aEnd": {
"vNicIndex":2,
"vlan":null,
"innerVlan":666
},
"bEnd": {
"productUid": "{ awshcPortUid }",
"partnerConfig": {
"connectType":"AWSHC",
"ownerAccount": "XXXXXXXXXXXX",
"name": "AWS link MVE link 2"
}
}
}
]
}
]
```
After sending the request, you will receive a successful response when the VXC has been ordered.
Here is a sample response:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "VXC [5668c467-17eb-47e3-beba-87b9e7784a17] created.",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"createDate": 1709812459883,
"vxcOrderId": 139936,
"payerMegaPortId": 190079,
"nonPayerMegaPortId": 114147,
"payerMegaPortName": "MVE for VNIC config",
"nonPayerMegaPortName": "EU (London) (eu-west-2)",
"payerCompanyId": 1153,
"nonPayerCompanyId": 117,
"payerLocationId": 89,
"nonPayerLocationId": 90,
"salesId": null,
"payerCompanyName": "Megaport Lab",
"nonPayerCompanyName": "AWS",
"payerMegaPortNsId": 510708,
"nonPayerMegaPortNsId": 271398,
"payerVlanId": 0,
"nonPayerVlanId": 0,
"payerInnerVlanId": 666,
"nonPayerInnerVlanId": null,
"payerApproverName": "David Sloan",
"payerApproverId": 41315,
"nonPayerApproverName": "David Sloan",
"nonPayerApproverId": 41315,
"payerApproval": number,
"nonPayerApproval": number,
"fixedTerm": true,
"duration": 1,
"rollover": true,
"serviceName": "from MVE for VNIC config to EU (London) (eu-west-2)",
"payerStatus": "APPROVED",
"nonPayerStatus": "APPROVED",
"speed": 100,
"distanceBand": "METRO",
"intercapPath": "",
"awsId": null,
"promoCode": null,
"rateType": "MONTHLY",
"vxcJTechnicalServiceId": 190089,
"vxcJTechnicalServiceUid": "5668c467-17eb-47e3-beba-87b9e7784a17",
"provisionDate": 1709812459853,
"orderType": "NEW",
"monthlyDiscountAmount": null,
"discountMonths": null,
"amazonDirectConnectConfigDto": null,
"amsixConnectConfigDto": null,
"sdrcProvItem": null,
"rate": null,
"setup": null,
"asn": null,
"bgpPassword": null,
"usageAlgorithm": "POST_PAID_HOURLY_SPEED_METRO_VXC",
"costCentre": null,
"azureServiceKey": null,
"oracleVirtualCircuitId": null,
"serviceKey": null,
"vxc": {
"serviceName": "Test AWS over Vnic2",
"name": "Test AWS over Vnic2",
"secondaryName": null,
"technicalServiceId": 190089,
"technicalServiceUid": "5668c467-17eb-47e3-beba-87b9e7784a17",
"requestedDate": 1709812459853,
"configuredDate": null,
"currentEstimatedDelivery": null,
"companyName": "Megaport Lab",
"companyId": 1153,
"billingContactName": null,
"billingContactId": null,
"adminContactName": null,
"adminContactId": null,
"technicalContactName": null,
"technicalContactId": null,
"salesName": null,
"salesId": null,
"billableId": 181637,
"billableUsageAlgorithm": null,
"productType": "VXC",
"provisioningStatus": "DEPLOYABLE",
"failedReason": null,
"inAdvanceBillingStatus": null,
"provisioningItems": [],
"tags": [],
"vxcDistanceBand": "METRO",
"intercapPath": "",
"marketplaceVisibility": true,
"vxcPermitted": true,
"vxcAutoApproval": false,
"createDate": 1709812459869,
"terminationDate": null,
"contractStartDate": null,
"contractTermMonths": 1,
"rateType": "MONTHLY",
"trialAgreement": false,
"payerCompanyId": null,
"nonPayerCompanyId": null,
"minimumSpeed": null,
"maximumSpeed": null,
"rateLimit": 100,
"errorMessage": null,
"lagId": null,
"aggregationId": null,
"lagPrimary": null,
"market": "UK",
"accountManager": null,
"promptUid": null,
"components": [],
"attributes": [],
"aLocation": null,
"bLocation": null,
"aMetro": null,
"aCountry": null,
"aLocationId": null,
"bLocationId": null,
"bMetro": null,
"bCountry": null,
"attributeTags": {},
"createdBy": "b0dedbd2-ecc7-4bad-a13b-6c34b4005115",
"buyoutPort": null,
"virtual": false,
"locked": false,
"adminLocked": false,
"bgpShutdownDefault": false
},
"connectType": "AWSHC",
"payerConfig": {},
"nonPayerConfig": {},
"attributeTags": {},
"serviceLicense": null,
"fullyApproved": true
}
]
}
```
The VXC will now appear in the Megaport Portal.
For this example, the AWS Hosted Connection will appear in the AWS portal account under Direct Connect - connection. The account holder can accept the Hosted Connection and create one private, one public or one transit VIF, and connect it to a Virtual Private Gateway or a Direct Connect Gateway or Transit Gateway, and then to their VPCs.
# Creating a VXC between an MVE and Microsoft Azure with the API
Source: https://docs.megaport.com/api/api-mve-vxc-azure
This help topic describes how to use the Megaport API to create a VXC between a Megaport Virtual Edge (MVE) and an Azure ExpressRoute circuit.
This topic describes the API procedure to create a VXC from an MVE to Microsoft Azure ExpressRoute. Configuration is a two step process: first, you look up Azure interconnect locations with the Azure service key, then you can create the VXC to a specific vNIC on your MVE.
Before you can connect to Azure, you need to set up an ExpressRoute circuit in the Azure console. When set up, you receive a service key with connection details. To configure your MVE connection to Azure, you look up the service key details and then create VXCs to the Azure ports.
The MVE to Azure deployment includes these tasks:
1. **Set up an ExpressRoute circuit in the Azure console**
When deployed, you get a service key. When you validate a service key, you are presented with primary and secondary ports and can choose the port for the connection. You can use the key a second time and create another connection to the unused port.
For more information, see the Microsoft help topic [Tutorial: Create and modify an ExpressRoute circuit](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-circuit-portal-resource-manager).
2. **Validate the Azure service key**
When ordering an Azure service, use the service key and ensure there is a free port for a connection.
The API response includes ExpressRoute details of the associated ports and peers. You need the Azure port details to create the VXC.
3. **Create and deploy a VXC**
With the validated service key and port details, create the VXC to Microsoft Azure from the MVE.
As part of the VXC configuration, you can choose the peering type. The peering type can be either private or Microsoft.
A defined peering type results in automatically configured peering with peers matched on both the Azure and Megaport sides and a deployed system with a known working configuration. You can modify the configuration once deployed.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
## Validate the service key
Use the API to validate a Microsoft Azure service key. The response includes ExpressRoute details of the associated ports and peers. You need the Azure port details to create the VXC.
Review the service key and ensure there is a free Port for a connection. In the API response, available ports are listed as `"vxc":null` and ports with an assigned value are not available.
For more information about each response field, see [Azure Service Key Response Fields](/api/api-azure-servicekey).
**To validate the service key**
* Use the **GET Look Up Azure Service Key** API to look up Microsoft Azure location details with the service key:
`GET {baseUrl}/v2/secure/azure/{service_key}`
Here is a sample response for a pairing key with an available port (vxc = null).
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Successful lookup",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"bandwidth": 50,
"connectType": "AZURE",
"managed": false,
"megaports": [
{
"productId": 53013,
"productUid": "83f95deb-a537-485e-80d9-c442c776ddc9",
"name": "London Primary",
"nServiceId": 119129,
"description": "Azure ExpressRoute at Equinix LD5",
"companyId": 1475,
"companyUid": "c40de5ed-4707-4471-a78c-69436de2c505",
"companyName": "Azure ExpressRoute",
"portSpeed": 10000,
"locationId": 90,
"state": null,
"country": "United Kingdom",
"port": 53013,
"type": "primary",
"vxc": null
},
{
"productId": 53014,
"productUid": "d84ad163-8e22-4150-8cb7-44f1aecf9e90",
"name": "London Secondary",
"nServiceId": 119130,
"description": "Azure ExpressRoute at Equinix LD5",
"companyId": 1475,
"companyUid": "c40de5ed-4707-4471-a78c-69436de2c505",
"companyName": "Azure ExpressRoute",
"portSpeed": 10000,
"locationId": 90,
"state": null,
"country": "United Kingdom",
"port": 53014,
"type": "secondary",
"vxc": null
}
],
"peers": [],
"resource_type": "csp_connection",
"service_key": "3f0f66b9-0c82-4d61-ae31-f5985c841a4a",
"vlan": 19
}
}
```
## Create and deploy a VXC to a specific vNIC
With the Azure ExpressRoute port details from the service key lookup, create the VXC to Azure.
You specify the configuration details in the Body of the request. The first `productUid` identifies the MVE and the `bEnd: productUid` identifies the Azure interface. You also need to provide the Azure ExpressRoute service key in `serviceKey` field.
Look up Azure locations for the B-End of the connection with the `v2/dropdowns/partner/megaports` endpoint.
You can create multiple connections to an Azure interface, for example, if you need to connect both private and Microsoft peers to the same interface.
### Single Azure Peering VLAN
In this example, Single Azure Peering VLAN is used. You can tell this because the aEnd innerVlan and the bEnd innerVlan are specified. For Single Azure Peering VLAN both are set to the same value.
If this value is set to `0`, a valid inner VLAN will be allocated and set by the system.
To test your request before you order and see pricing details, use the `/v3/networkdesign/validate` endpoint with the same Body configuration.
**To create a VXC**
1. Create a request with the **POST Create VXC to Azure (v3)** endpoint:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
2. Update the Body of the request with the `productUid` of the MVE, the name of the VXC, the `productUid` of the Azure port, and set the service key `innerVlan` to 501 and `vNicIndex` to 0 (interface 1).
The vNIC number relates to the following MVE interfaces:
* vNIC 0 = interface 1 on the MVE
* vNIC 1 = interface 2 on the MVE
* vNIC 2 = interface 3 on the MVE
* vNIC 3 = interface 4 on the MVE
* vNIC 4 = interface 5 on the MVE
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "{ mveid }",
"associatedVxcs": [
{
"productName": "Link to Azure ",
"partnerConfigs" : {
"connectType": "AZURE",
"serviceKey": "((azureServiceKey}}"
},
"rateLimit": 1000,
"term": 12,
"shutdown": false,
"promoCode": "promox3mnthfree2",
"aEnd": {
"vNicIndex":0,
"innerVlan": 501
},
"bEnd": {
"productUid": "{ azurePortUid }",
"innerVlan": 501
}
}
]
}
]
```
After sending the request, you will receive a successful response when the VXC has been ordered.
Here is a sample response:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "VXC [7f7c22f6-5cde-45d7-8603-f3546c714118] created.",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"createDate": 1709822378799,
"vxcOrderId": 139947,
"payerMegaPortId": 190079,
"nonPayerMegaPortId": 53013,
"payerMegaPortName": "MVE for VNIC config",
"nonPayerMegaPortName": "London Primary",
"payerCompanyId": 1153,
"nonPayerCompanyId": 1475,
"payerLocationId": 89,
"nonPayerLocationId": 90,
"salesId": null,
"payerCompanyName": "Megaport Lab",
"nonPayerCompanyName": "Azure ExpressRoute",
"payerMegaPortNsId": 510708,
"nonPayerMegaPortNsId": 119129,
"payerVlanId": 0,
"nonPayerVlanId": 0,
"payerInnerVlanId": 501,
"nonPayerInnerVlanId": 501,
"payerApproverName": "name",
"payerApproverId": 41315,
"nonPayerApproverName": "name",
"nonPayerApproverId": number,
"payerApproval": number,
"nonPayerApproval": number,
"fixedTerm": true,
"duration": 1,
"rollover": true,
"serviceName": "from MVE for VNIC config to London Primary",
"payerStatus": "APPROVED",
"nonPayerStatus": "APPROVED",
"speed": 1000,
"distanceBand": "METRO",
"intercapPath": "",
"awsId": null,
"promoCode": null,
"rateType": "MONTHLY",
"vxcJTechnicalServiceId": 190104,
"vxcJTechnicalServiceUid": "7f7c22f6-5cde-45d7-8603-f3546c714118",
"provisionDate": 1709822378782,
"orderType": "NEW",
"monthlyDiscountAmount": null,
"discountMonths": null,
"amazonDirectConnectConfigDto": null,
"amsixConnectConfigDto": null,
"sdrcProvItem": null,
"rate": null,
"setup": null,
"asn": null,
"bgpPassword": null,
"usageAlgorithm": "POST_PAID_HOURLY_SPEED_METRO_VXC",
"costCentre": null,
"azureServiceKey": "{ azureServiceKey }",
"oracleVirtualCircuitId": null,
"serviceKey": null,
"vxc": {
"serviceName": "Link to Azure ",
"name": "Link to Azure ",
"secondaryName": null,
"technicalServiceId": 190104,
"technicalServiceUid": "7f7c22f6-5cde-45d7-8603-f3546c714118",
"requestedDate": 1709822378782,
"configuredDate": null,
"currentEstimatedDelivery": null,
"companyName": "Megaport Lab",
"companyId": 1153,
"billingContactName": null,
"billingContactId": null,
"adminContactName": null,
"adminContactId": null,
"technicalContactName": null,
"technicalContactId": null,
"salesName": null,
"salesId": null,
"billableId": 181652,
"billableUsageAlgorithm": null,
"productType": "VXC",
"provisioningStatus": "DEPLOYABLE",
"failedReason": null,
"inAdvanceBillingStatus": null,
"provisioningItems": [],
"tags": [],
"vxcDistanceBand": "METRO",
"intercapPath": "",
"marketplaceVisibility": true,
"vxcPermitted": true,
"vxcAutoApproval": false,
"createDate": 1709822378792,
"terminationDate": null,
"contractStartDate": null,
"contractTermMonths": 1,
"rateType": "MONTHLY",
"trialAgreement": false,
"payerCompanyId": null,
"nonPayerCompanyId": null,
"minimumSpeed": null,
"maximumSpeed": null,
"rateLimit": 1000,
"errorMessage": null,
"lagId": null,
"aggregationId": null,
"lagPrimary": null,
"market": "UK",
"accountManager": null,
"promptUid": null,
"components": [],
"attributes": [],
"aLocation": null,
"bLocation": null,
"aMetro": null,
"aCountry": null,
"aLocationId": null,
"bLocationId": null,
"bMetro": null,
"bCountry": null,
"attributeTags": {},
"createdBy": "b0dedbd2-ecc7-4bad-a13b-6c34b4005115",
"buyoutPort": null,
"virtual": false,
"locked": false,
"adminLocked": false,
"bgpShutdownDefault": false
},
"connectType": "AZURE",
"payerConfig": {},
"nonPayerConfig": {},
"attributeTags": {},
"serviceLicense": null,
"fullyApproved": true
}
]
}
```
### Multiple Microsoft peerings (Q-in-Q)
If you do not want to use Single Azure Peering VLAN and want to use Q-in-Q to have multi Microsoft peerings on a single VXC, only specify the aEnd innerVlan value.
With Q-in-Q in play, the Azure peering VLAN ID set in Azure is not shown in the Megaport APIs or Portal. It is configured by the customer in the Azure ExpressRoute peerings and matched on the MVE instance configuration.
In the example below, the aEnd innerVlan field of 100 is actually an outer vlan or s-tag on the MVE. The Q-in-Q inner VLAN (c-tag) running inside the innerVlan is transparent to Megaport.
Azure VXCs are the only cloud VXC type that allow you to specify a double-tagged VXC.
Here is a sample request:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "02ec2091-46bb-4904-bd17-96c752ff826e",
"associatedVxcs": [
{
"productName": "My New Azure VXC",
"partnerConfigs" : {
"connectType": "AZURE",
"serviceKey": "{ service_key }"
},
"rateLimit": 1000,
"term": 12,
"shutdown": false,
"aEnd": {
"innerVlan": 100
},
"bEnd": {
"productUid": "{ azurepuid }"
}
}
]
}
]
```
# Creating a VXC between an MVE and Google Cloud with the API
Source: https://docs.megaport.com/api/api-mve-vxc-google
This help topic describes how to use the Megaport API to create a VXC between a Megaport Virtual Edge (MVE) and Google Cloud Services.
This topic describes the API procedure to create a VXC from an MVE to Google Cloud services. Configuration is a two step process: first, you look up connection details with the Google pairing key, then you create the VXC to a specific vNIC on your MVE.
Before you can create a connection to Google Cloud, you need to create a Partner Interconnect attachment in Google Cloud Console or gcloud CLI. As part of the attachment creation, you are provided a pairing key that contains the Google connection details.
The MVE to Google Cloud deployment includes these tasks:
1. **Create a Partner Interconnect attachment in Google Cloud Console or gcloud CLI**
Create a Partner Interconnect attachment in Google Cloud Console or gcloud CLI. Copy the pairing key that is provided as part of the attachment creation.
For additional details, see the Google documentation on
[Google Partner Interconnects](https://cloud.google.com/interconnect/docs/how-to/partner/provisioning-overview).
2. **Validate the Google pairing key**
When ordering a Google Cloud service, use the pairing key and ensure there is a free port for a connection.
Google requires that the bandwidth on the VXC matches one of the predefined bandwidths in the list returned by the pairing key lookup.
3. **Create and deploy a VXC**
With the validated pairing key and port details, create the VXC to Google Cloud from the MVE.
Configuration details are specified in the Body of the request.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
## Validate the Google pairing key
Use the API to validate a Google Cloud pairing key. The response includes details of the associated ports and peers. You need the port details to create the VXC.
In the API response, available ports are listed as `"vxc":null` and ports with an assigned value are not available.
Google requires that the bandwidth on the VXC matches one of the predefined bandwidths in the list returned by the pairing key lookup.
**To validate the pairing key**
* Use the **GET Look Up Google Pairing Key** API to look up Google Cloud location details with the pairing key:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/secure/google/{pairing_key}
```
Here is a sample response for a pairing key with an available port (vxc = null).
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Successful lookup",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"bandwidths": [
50,
100,
200,
300,
400,
500,
1000,
2000,
5000,
10000,
20000,
50000
],
"megaports": [
{
"productId": 28845,
"productUid": "5b693428-8cc6-4634-a44a-2e9e6ba556af",
"name": "Stockholm (arn-zone1-208)",
"nServiceId": 65391,
"description": "Google inc.. at Interxion STO5",
"companyId": 90,
"companyUid": "29ba879b-45c8-48eb-bd97-618d0f20ea04",
"companyName": "Google inc..",
"portSpeed": 10000,
"locationId": 98,
"state": null,
"country": "Sweden",
"port": 28845,
"vxc": null
},
{
"productId": 45873,
"productUid": "832a017d-74ca-45e8-a225-e3d794a079d7",
"name": "Zurich (zrh-zone1-81)",
"nServiceId": 103010,
"description": "Google inc.. at Interxion ZH1",
"companyId": 90,
"companyUid": "{ companyUid }",
"companyName": "Google inc..",
"portSpeed": 10000,
"locationId": 557,
"state": null,
"country": "Switzerland",
"port": 45873,
"vxc": null
},
{
"productId": 81531,
"productUid": "6e587057-f012-4600-896f-9ee171fdd444",
"name": "Frankfurt (fra-zone1-683)",
"nServiceId": 181786,
"description": "Google inc.. at Equinix FR5",
"companyId": 90,
"companyUid": "{ companyUid }",
"companyName": "Google inc..",
"portSpeed": 100000,
"locationId": 131,
"state": null,
"country": "Germany",
"port": 81531,
"vxc": null
},
{
"productId": 84769,
"productUid": "f25e581b-3c0e-4069-8147-78cce082357e",
"name": "Amsterdam (ams-zone1-1236)",
"nServiceId": 188925,
"description": "Google inc.. at Equinix AM1",
"companyId": 90,
"companyUid": "29ba879b-45c8-48eb-bd97-618d0f20ea04",
"companyName": "Google inc..",
"portSpeed": 100000,
"locationId": 85,
"state": null,
"country": "Netherlands",
"port": 84769,
"vxc": null
},
{
"productId": 95335,
"productUid": "9fde43f5-2f00-41ed-bb60-45c446ea43df",
"name": "London (lhr-zone1-832)",
"nServiceId": 217347,
"description": "Google inc.. at Equinix LD5",
"companyId": 90,
"companyUid": "29ba879b-45c8-48eb-bd97-618d0f20ea04",
"companyName": "Google inc..",
"portSpeed": 100000,
"locationId": 90,
"state": null,
"country": "United Kingdom",
"port": 95335,
"vxc": null
},
{
"productId": 153623,
"productUid": "ae8d21b5-2db6-4f72-a465-624c914f4918",
"name": "Paris (cdg-zone1-1536)",
"nServiceId": 391882,
"description": "Google inc.. at Interxion PAR5",
"companyId": 90,
"companyUid": "29ba879b-45c8-48eb-bd97-618d0f20ea04",
"companyName": "Google inc..",
"portSpeed": 100000,
"locationId": 527,
"state": null,
"country": "France",
"port": 153623,
"vxc": null
},
{
"productId": 162678,
"productUid": "7d1cca03-eb3d-4be4-a145-de8e8dffec3f",
"name": "Frankfurt (fra-zone1-58)",
"nServiceId": 420550,
"description": "Google inc.. at Interxion FRA6",
"companyId": 90,
"companyUid": "29ba879b-45c8-48eb-bd97-618d0f20ea04",
"companyName": "Google inc..",
"portSpeed": 100000,
"locationId": 130,
"state": null,
"country": "Germany",
"port": 162678,
"vxc": null
}
],
"resource_type": "csp_connection",
"ports": [
{
"service_id": 38286,
"vxc_service_ids": []
},
{
"service_id": 65391,
"vxc_service_ids": []
},
{
"service_id": 103010,
"vxc_service_ids": []
},
{
"service_id": 125905,
"vxc_service_ids": []
},
{
"service_id": 154694,
"vxc_service_ids": []
},
{
"service_id": 181786,
"vxc_service_ids": []
},
{
"service_id": 188925,
"vxc_service_ids": []
},
{
"service_id": 217347,
"vxc_service_ids": []
},
{
"service_id": 391882,
"vxc_service_ids": []
},
{
"service_id": 420550,
"vxc_service_ids": []
}
]
}
}
```
## Create and deploy a VXC to a specific vNIC
With the validated pairing key and port details, create the VXC to Google Cloud from the MVE.
You specify the configuration details in the Body of the request. The first `productUid`identifies the MVE ID and the `bEnd: productUid` identifies the Google Cloud location from the pairing key. You also need to provide your Google pairing key in the request. Only the aEnd innerVlan needs to be specified.
To test your request before you order and see pricing details, use the `/v3/networkdesign/validate` endpoint with the same Body configuration.
**To create a VXC**
1. Create a request with the **POST Create VXC to Google Cloud (v3)** endpoint:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
2. Update the Body of the request with the `productUid` of the MVE, the name of the VXC, the `productUid` of the Google Cloud port, set the `vNicIndex` to 2 (interface 3), and the pairing key.
The vNIC number relates to the following MVE interfaces:
* vNIC 0 = interface 1 on the MVE
* vNIC 1 = interface 2 on the MVE
* vNIC 2 = interface 3 on the MVE
* vNIC 3 = interface 4 on the MVE
* vNIC 4 = interface 5 on the MVE
Here is a sample request:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "{ mveid }",
"associatedVxcs": [
{
"productName": "VXC to test VNIC",
"rateLimit": 100,
"term": 12,
"shutdown": false,
"promoCode": "promox3mnthfree2",
"aEnd": {
"vNicIndex":2,
"innerVlan": 144
},
"bEnd": {
"productUid" : "{ googleProductUid }",
"partnerConfig": {
"connectType": "GOOGLE",
"pairingKey": "{ googlePairingKey }"
}
}
}
]
}
]
```
Once you have completed and deployed the VXC, go back to the Google Cloud Console and accept the attachment.
After sending the request, you will receive a successful response when the VXC has been ordered.
Here is a sample response:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "VXC [27139b23-0afe-4e48-9322-eea95d2d6b74] created.",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"createDate": 1709823461856,
"vxcOrderId": 139952,
"payerMegaPortId": 190079,
"nonPayerMegaPortId": 95335,
"payerMegaPortName": "MVE for VNIC config",
"nonPayerMegaPortName": "London (lhr-zone1-832)",
"payerCompanyId": 1153,
"nonPayerCompanyId": 90,
"payerLocationId": 89,
"nonPayerLocationId": 90,
"salesId": null,
"payerCompanyName": "Megaport Lab",
"nonPayerCompanyName": "Google inc..",
"payerMegaPortNsId": 510708,
"nonPayerMegaPortNsId": 217347,
"payerVlanId": 0,
"nonPayerVlanId": 0,
"payerInnerVlanId": 144,
"nonPayerInnerVlanId": null,
"payerApproverName": "David Sloan",
"payerApproverId": 41315,
"nonPayerApproverName": "David Sloan",
"nonPayerApproverId": 41315,
"payerApproval": 1709823461831,
"nonPayerApproval": 1709823461850,
"fixedTerm": true,
"duration": 1,
"rollover": true,
"serviceName": "from MVE for VNIC config to London (lhr-zone1-832)",
"payerStatus": "APPROVED",
"nonPayerStatus": "APPROVED",
"speed": 100,
"distanceBand": "METRO",
"intercapPath": "",
"awsId": null,
"promoCode": null,
"rateType": "MONTHLY",
"vxcJTechnicalServiceId": 190111,
"vxcJTechnicalServiceUid": "27139b23-0afe-4e48-9322-eea95d2d6b74",
"provisionDate": 1709823461826,
"orderType": "NEW",
"monthlyDiscountAmount": null,
"discountMonths": null,
"amazonDirectConnectConfigDto": null,
"amsixConnectConfigDto": null,
"sdrcProvItem": null,
"rate": null,
"setup": null,
"asn": null,
"bgpPassword": null,
"usageAlgorithm": "POST_PAID_HOURLY_SPEED_METRO_VXC",
"costCentre": null,
"azureServiceKey": null,
"oracleVirtualCircuitId": null,
"serviceKey": null,
"vxc": {
"serviceName": "VXC to test VNIC",
"name": "VXC to test VNIC",
"secondaryName": null,
"technicalServiceId": 190111,
"technicalServiceUid": "27139b23-0afe-4e48-9322-eea95d2d6b74",
"requestedDate": 1709823461826,
"configuredDate": null,
"currentEstimatedDelivery": null,
"companyName": "Megaport Lab",
"companyId": 1153,
"billingContactName": null,
"billingContactId": null,
"adminContactName": null,
"adminContactId": null,
"technicalContactName": null,
"technicalContactId": null,
"salesName": null,
"salesId": null,
"billableId": 181659,
"billableUsageAlgorithm": null,
"productType": "VXC",
"provisioningStatus": "DEPLOYABLE",
"failedReason": null,
"inAdvanceBillingStatus": null,
"provisioningItems": [],
"tags": [],
"vxcDistanceBand": "METRO",
"intercapPath": "",
"marketplaceVisibility": true,
"vxcPermitted": true,
"vxcAutoApproval": false,
"createDate": 1709823461844,
"terminationDate": null,
"contractStartDate": null,
"contractTermMonths": 1,
"rateType": "MONTHLY",
"trialAgreement": false,
"payerCompanyId": null,
"nonPayerCompanyId": null,
"minimumSpeed": null,
"maximumSpeed": null,
"rateLimit": 100,
"errorMessage": null,
"lagId": null,
"aggregationId": null,
"lagPrimary": null,
"market": "UK",
"accountManager": null,
"promptUid": null,
"components": [],
"attributes": [],
"aLocation": null,
"bLocation": null,
"aMetro": null,
"aCountry": null,
"aLocationId": null,
"bLocationId": null,
"bMetro": null,
"bCountry": null,
"attributeTags": {},
"createdBy": "b0dedbd2-ecc7-4bad-a13b-6c34b4005115",
"buyoutPort": null,
"virtual": false,
"locked": false,
"adminLocked": false,
"bgpShutdownDefault": false
},
"connectType": "GOOGLE",
"payerConfig": {},
"nonPayerConfig": {},
"attributeTags": {},
"serviceLicense": null,
"fullyApproved": true
}
]
}
```
# Running NAT Gateway Diagnostics with the API
Source: https://docs.megaport.com/api/api-nat-gateway-diagnostics
This help topic describes how to use the Megaport API to run ping and traceroute diagnostics from a Megaport NAT Gateway.
This topic describes how to use the Megaport API to run ping and traceroute diagnostics from a Megaport NAT Gateway (NAT Gateway). Use these diagnostics to test network connectivity and troubleshoot routing issues from the perspective of your NAT Gateway.
Both diagnostics run asynchronously. You initiate the request, which returns an operation ID, then use a separate endpoint to retrieve the results when the operation completes.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
The ping and traceroute endpoints are rate limited and intended for troubleshooting, not regular monitoring.
## Use cases
These diagnostics help you troubleshoot network connectivity issues by testing reachability and path visibility from the NAT Gateway itself.
Common use cases include:
* Verifying connectivity to cloud provider endpoints before configuring BGP sessions
* Testing reachability to on-premises networks connected via VXCs
* Diagnosing routing issues by confirming whether the NAT Gateway can reach specific destinations
* Validating network paths and measuring round-trip latency
* Identifying routing hops and potential bottlenecks using traceroute
* Troubleshooting asymmetric routing or path issues
## Prerequisites
The NAT Gateway must have at least one active VXC attached. Running a diagnostic on an NAT Gateway with no VXCs returns a 400 Bad Request error with the message: "NAT Gateway has no VXCs attached. Ping/traceroute requires at least one active VXC."
## Ping
Use the ping diagnostic to test basic connectivity and measure round-trip latency to a destination IP address.
### Initiating a ping request
To start a ping diagnostic from your NAT Gateway, send a GET request to the ping endpoint with the destination IP address and optional parameters.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/{productUid}/diagnostics/ping
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier of the NAT Gateway from which to run the diagnostic. |
**Query Parameters**
| Parameter | Required | Description |
| :- | :- | :- |
| destination\_address | Yes | The target IPv4 or IPv6 address to ping. Must be an IP address literal, not a hostname. Cannot be a loopback, multicast, or any-local address. Private (RFC1918) and link-local addresses are allowed for testing connectivity to VPC/VNet resources. |
| source\_address | No | The source IPv4 or IPv6 address for the ping. Must be the same address family as the destination address. |
| packet\_count | No | The number of ICMP packets to send. Valid range: 1-60. Default: 3. |
| packet\_size | No | The size of each ICMP packet in bytes. Valid range: 1-9186. Default: 56. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/abc12345-6789-0def-ghij-klmnopqrstuv/diagnostics/ping?destination_address=192.0.2.1&packet_count=5
```
**Response**
A successful request returns an `operationId` that you use to retrieve the ping results.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Please retrieve the result with the operation id: 12345678-90ab-cdef-1234-567890abcdef",
"terms": "This data is subject to the Acceptable Use Policy.",
"data": "12345678-90ab-cdef-1234-567890abcdef"
}
```
### Retrieving ping results
After initiating a ping request, use the diagnostics operation endpoint to retrieve the results. The operation runs asynchronously, so you might need to poll until the results are ready.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/{productUid}/diagnostics/routes/operation?operationId={operationId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier of the NAT Gateway. |
**Query Parameters**
| Parameter | Required | Description |
| :- | :- | :- |
| operationId | Yes | The operation ID returned from the ping initiation request. |
**Response Codes**
| Code | Description |
| :- | :- |
| 200 | The ping operation has completed. Results are included in the response. |
| 202 | The ping operation is still pending or running. Poll again after a short delay. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/abc12345-6789-0def-ghij-klmnopqrstuv/diagnostics/routes/operation?operationId=12345678-90ab-cdef-1234-567890abcdef
```
**Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Diagnostic result retrieved successfully",
"data": {
"rawOutput": "PING 192.0.2.1 (192.0.2.1) 56(84) bytes of data...",
"statistics": {
"packetsTransmitted": 5,
"packetsReceived": 5,
"packetLossPct": 0.0,
"rttMinMs": 0.987,
"rttAvgMs": 1.234,
"rttMaxMs": 1.567,
"rttMdevMs": 0.123,
"totalTimeMs": 4012.0,
"duplicates": 0,
"errors": 0
}
}
}
```
The response includes `rawOutput` containing the raw ping command output, and `statistics` with detailed packet and timing metrics. If the ping fails, an `error` field contains the error message.
## Traceroute
Use the traceroute diagnostic to discover the network path between your NAT Gateway and a destination IP address, showing each hop along the route.
### Initiating a traceroute request
To start a traceroute diagnostic from your NAT Gateway, send a GET request to the traceroute endpoint with the destination IP address.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/{productUid}/diagnostics/traceroute
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier of the NAT Gateway from which to run the diagnostic. |
**Query Parameters**
| Parameter | Required | Description |
| :- | :- | :- |
| destination\_address | Yes | The target IPv4 or IPv6 address to trace. Must be an IP address literal, not a hostname. Cannot be a loopback, multicast, or any-local address. Private (RFC1918) and link-local addresses are allowed for testing connectivity to VPC/VNet resources. |
| source\_address | No | The source IPv4 or IPv6 address for the traceroute. Must be the same address family as the destination address. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/abc12345-6789-0def-ghij-klmnopqrstuv/diagnostics/traceroute?destination_address=192.0.2.1
```
**Response**
A successful request returns an `operationId` that you use to retrieve the traceroute results.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Please retrieve the result with the operation id: 12345678-90ab-cdef-1234-567890abcdef",
"terms": "This data is subject to the Acceptable Use Policy.",
"data": "12345678-90ab-cdef-1234-567890abcdef"
}
```
### Retrieving traceroute results
After initiating a traceroute request, use the diagnostics operation endpoint to retrieve the results. The operation runs asynchronously, so you might need to poll until the results are ready.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/{productUid}/diagnostics/routes/operation?operationId={operationId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| productUid | The unique identifier of the NAT Gateway. |
**Query Parameters**
| Parameter | Required | Description |
| :- | :- | :- |
| operationId | Yes | The operation ID returned from the traceroute initiation request. |
**Response Codes**
| Code | Description |
| :- | :- |
| 200 | The traceroute operation has completed. Results are included in the response. |
| 202 | The traceroute operation is still pending or running. Poll again after a short delay. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/abc12345-6789-0def-ghij-klmnopqrstuv/diagnostics/routes/operation?operationId=12345678-90ab-cdef-1234-567890abcdef
```
**Response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Diagnostic result retrieved successfully",
"data": {
"hops": [
{
"hop": "1",
"probes": [
{ "host": "198.51.100.1", "rttMs": 0.543 },
{ "host": "198.51.100.1", "rttMs": 0.487 },
{ "host": "198.51.100.1", "rttMs": 0.512 }
]
},
{
"hop": "2",
"probes": [
{ "host": "203.0.113.254", "rttMs": 1.234 },
{ "host": "203.0.113.254", "rttMs": 1.156 },
{ "host": "203.0.113.254", "rttMs": 1.298 }
]
},
{
"hop": "3",
"probes": [
{ "host": "192.0.2.1", "rttMs": 2.876 },
{ "host": "192.0.2.1", "rttMs": 2.654 },
{ "host": "192.0.2.1", "rttMs": 2.789 }
]
}
],
"rawOutput": "traceroute to 192.0.2.1, 30 hops max, 60 byte packets..."
}
}
```
The response includes an array of `hops`, where each hop contains a `hop` number and an array of `probes`. Each probe shows the responding `host` (IP address or hostname) and the `rttMs` (round-trip time in milliseconds). If a probe receives no response, `host` may be null. The `rawOutput` field contains the raw traceroute command output.
## Helpful references
* [NAT Gateway Features](/nat/nat-gateway-features)
* [Creating a NAT Gateway](/nat/creating-nat-gateway)
* [Creating a NAT Gateway VXC](/nat/nat-gateway-vxc)
# Creating a Megaport NAT Gateway with the API
Source: https://docs.megaport.com/api/api-nat-gateways
This help topic describes how to use the Megaport API to create a Megaport NAT Gateway.
This topic describes the API procedure to create a Megaport NAT Gateway (NAT Gateway), including how to look up locations, check available session counts, and place the order.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
To create a NAT Gateway, you need to:
1. Look up NAT Gateway location details to find a location that supports the NAT Gateway speed you require.
2. Look up available session counts to choose a valid session count for your NAT Gateway.
3. Create the NAT Gateway design to generate a `productUid` for the NAT Gateway.
4. Validate the NAT Gateway order using the `productUid`.
5. Buy the NAT Gateway to provision the service.
**To look up NAT Gateway location details**
1. Send a GET request to retrieve available locations.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/locations
```
2. Search the response for a location that includes `natGatewaySpeedMbps` in the `diversityZones` object.
To provision a NAT Gateway at a location, your required speed must appear in `natGatewaySpeedMbps`. Check that the location has your required speed and an available diversity zone.
To create a NAT Gateway, you need the location `id` value. In this example, the location ID is 60.
```json {2,19,25} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"id": 60,
"name": "CoreSite LA1",
"address": {
"street": "624 South Grand Avenue",
"suburb": null,
"city": "Los Angeles",
"state": "CA",
"postcode": "90017",
"country": "USA"
},
"metro": "Los Angeles",
"market": "US",
"status": "Active",
"diversityZones": {
"red": {
"mcrSpeedMbps": [1000, 2500, 5000, 10000],
"megaportSpeedMbps": [1000, 10000, 100000],
"natGatewaySpeedMbps": [1000, 2500, 10000],
"mveAvailable": true
},
"blue": {
"mcrSpeedMbps": [1000, 2500, 5000, 10000],
"megaportSpeedMbps": [1000, 10000, 100000],
"natGatewaySpeedMbps": [1000, 2500, 10000],
"mveAvailable": true
}
}
}
```
**To look up available session counts**
1. Send a GET request to retrieve the available session count and speed combinations for NAT Gateways.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/sessions
```
The response shows the valid session counts for each supported speed.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Success",
"data": [
{ "speedMbps": 1000, "sessionCount": [250000, 500000] },
{ "speedMbps": 2500, "sessionCount": [250000, 500000, 1000000] },
{ "speedMbps": 5000, "sessionCount": [250000, 500000, 1000000] },
{ "speedMbps": 10000, "sessionCount": [250000, 500000, 1000000, 2500000, 5000000, 10000000] },
{ "speedMbps": 25000, "sessionCount": [500000, 1000000, 2500000, 5000000, 10000000] },
{ "speedMbps": 50000, "sessionCount": [1000000, 2500000, 5000000, 10000000] }
]
}
```
2. Choose a speed and session count for your NAT Gateway. Both values are fixed for the life of the service.
**To create the NAT Gateway design**
1. Create a request with this URL:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/products/nat_gateways
```
This request creates the NAT Gateway configuration but does not purchase or provision the service. To purchase the NAT Gateway, you need to validate and buy using the `productUid`.
2. Create the request Body. You must include the `locationId`, `productName`, `speed`, `term`, and `config` fields. The `config` object requires an `asn` and a `sessionCount`. You can use the Megaport ASN: `133937`.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"locationId": 60,
"productName": "Test NAT Gateway",
"speed": 1000,
"term": 12,
"config": {
"asn": 133937,
"sessionCount": 250000,
"bgpShutdownDefault": false,
"diversityZone": "blue"
}
}
```
A successful response returns the `productUid` for the new NAT Gateway. You need this ID to order the NAT Gateway.
```json {4} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Success",
"data": {
"productUid": "abc12345-1234-1234-1234-abc123456789",
"provisioningStatus": "DESIGN",
"productName": "Test NAT Gateway",
"speed": 1000,
"locationId": 60,
"config": {
"asn": 133937,
"sessionCount": 250000,
"bgpShutdownDefault": false,
"diversityZone": "blue"
},
"term": 12,
"autoRenewTerm": false,
"createDate": "2024-01-15T10:00:00Z",
"createdBy": "user@example.com"
}
}
```
**To validate the NAT Gateway order**
1. Create a request with this URL:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/validate
```
2. Create the request Body with the `productUid` from the previous step.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "abc12345-1234-1234-1234-abc123456789"
}
]
```
A successful response (HTTP 200) confirms the order is valid. Proceed to purchase the NAT Gateway.
**To purchase the NAT Gateway**
1. Send a POST request to purchase and provision the NAT Gateway.
Use the same request Body as the validate step.
If you make the buy API call on api.megaport.com, your account will be charged for the service. Alternatively, you can use the API in the staging environment (api-staging.megaport.com) without charges. For more information, see [API Environments](/api#environments).
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
**Example Request Body**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "abc12345-1234-1234-1234-abc123456789"
}
]
```
If the purchase is successful, the response shows the `ORDERED` provisioning status and the NAT Gateway provisioning begins.
```json {5} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Success",
"data": {
"productUid": "abc12345-1234-1234-1234-abc123456789",
"provisioningStatus": "ORDERED",
"productName": "Test NAT Gateway",
"speed": 1000,
"locationId": 60,
"config": {
"asn": 133937,
"sessionCount": 250000,
"bgpShutdownDefault": false,
"diversityZone": "blue"
},
"term": 12,
"autoRenewTerm": false,
"createDate": "2024-01-15T10:00:00Z",
"createdBy": "user@example.com"
}
}
```
The new NAT Gateway now appears in your working environment, either portal.megaport.com or portal-staging.megaport.com.
The next step is to create VXCs on the NAT Gateway.\
For more information, see [Creating a NAT Gateway VXC with the API](/api/api-nat-gateways-vxc).
# Creating a NAT Gateway VXC with the API
Source: https://docs.megaport.com/api/api-nat-gateways-vxc
This help topic describes how to use the Megaport API to create a VXC on a Megaport NAT Gateway.
This topic describes the API procedure to create a Virtual Cross Connect (VXC) on a Megaport NAT Gateway (NAT Gateway). The example shows how to create a VXC to an AWS cloud service and configure BGP peering on the NAT Gateway A-End.
## Prerequisites
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
You also need a provisioned NAT Gateway. For more information, see [Creating a NAT Gateway with the API](/api/api-nat-gateways).
## Creating a VXC between a NAT Gateway and AWS
This example creates an AWS private VXC. The steps include how to:
* get the NAT Gateway product ID
* find the AWS location ID
* configure a BGP connection on the NAT Gateway A-End
* validate and order the VXC
To create the VXC, you need the `productUid` for the NAT Gateway.
**To get the productUid for the NAT Gateway**
1. Send a GET request to retrieve your NAT Gateway products.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways
```
2. From the response, locate the `productUid` for the NAT Gateway you want to connect.
This example uses this value: `abc12345-1234-1234-1234-abc123456789`
**To find the locationId where AWS is available**
1. Get the list of all interfaces Megaport has with Cloud Service Providers (CSPs).
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/dropdowns/partner/megaports
```
You can filter the response to show only interfaces from a specific cloud provider using the `connectType` query parameter, such as:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/dropdowns/partner/megaports?connectType=AWS&vxcPermitted=true
```
2. Search the response for a site in your preferred region.
For this example, select a US West site with `"locationId": 57`.
```json {2,3,5,8} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"connectType": "AWS",
"productUid": "d5518ee1-e915-4e3d-a4e1-a2c7e04f2fdd",
"vxcPermitted": true,
"companyUid": "605cb850-dfb4-4a05-a171-8bf17757b3a2",
"companyName": "AWS",
"title": "US West (Oregon) (us-west-2) [DZ-RED]",
"locationId": 57
}
```
To order the VXC, you need the following IDs from the response:
* `locationId` - The ID of the location.
* `productUid` - The port to connect to.
* `companyUid` - The ID of the Cloud Service Provider (CSP).
**To create the VXC**
The A-End `partnerConfig` uses `connectType: "VROUTER"`, and includes IP addresses and BGP connections for the NAT Gateway interface. The B-End specifies the AWS connection details.
The B-End configuration needs the following IDs from the previous step:
* `locationId` -- The `locationId` of the location
* `productUid` -- The `productUid` of the port at the location
* `OwnerUid` -- The `companyUid` of the CSP
In the request Body, you need to specify the UID of the NAT Gateway (`productUid`).
1. Create a request with this URL:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
2. Create the request Body with the configuration details.
To test your request before you order, use `POST {baseUrl}/v3/networkdesign/validate`.
**Example Request Body**
```json {3,32-34} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "abc12345-1234-1234-1234-abc123456789",
"associatedVxcs": [
{
"productName": "Test NAT Gateway VXC",
"rateLimit": 100,
"term": 12,
"shutdown": false,
"aEnd": {
"partnerConfig": {
"connectType": "VROUTER",
"interfaces": [
{
"ipAddresses": ["10.0.0.1/30"],
"bgpConnections": [
{
"peerAsn": 64512,
"localIpAddress": "10.0.0.1",
"peerIpAddress": "10.0.0.2",
"shutdown": false,
"description": "BGP to AWS",
"bfdEnabled": false
}
],
"ipRoutes": []
}
]
}
},
"bEnd": {
"locationId": 57,
"ownerUid": "605cb850-dfb4-4a05-a171-8bf17757b3a2",
"productUid": "d5518ee1-e915-4e3d-a4e1-a2c7e04f2fdd",
"partnerConfig": {
"connectType": "AWS",
"type": "private",
"ownerAccount": "123456789012"
}
},
"productType": "VXC"
}
]
}
]
```
If the request is successful, the response includes the details of the created VXC.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "VXC [xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] created.",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"serviceName": "Test NAT Gateway VXC",
"technicalServiceUid": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"provisioningStatus": "DEPLOYABLE",
"productType": "VXC",
"rateLimit": 100,
...
}
]
}
```
## NAT Gateway pools
You can configure NAT Gateway pools to control how the NAT Gateway translates outgoing traffic to public IP addresses. Each pool contains IP address ranges that are used as the source addresses for translated traffic.
NAT Gateway pools are only required on VXCs connecting to resources outside your private network, such as CSPs or the internet. VXCs connecting resources inside your network to the NAT Gateway do not require pool configuration.
You can configure pools on a VXC when you create it or after it is provisioned. To configure pools using the Portal, see [Using NAT Gateway Pools](/nat/nat-gateway-pools).
## BGP connections
You can configure multiple BGP connections per interface by adding a `bgpConnections` array to the `interfaces` array of the A-End partner configuration:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"bgpConnections": [
{
"peerAsn": 64512,
"localIpAddress": "10.0.0.1",
"peerIpAddress": "10.0.0.2",
"password": "yourBgpPassword",
"shutdown": false,
"description": "Primary BGP session",
"medIn": 100,
"medOut": 100,
"bfdEnabled": true,
"asOverride": false,
"importWhitelist": 1,
"exportWhitelist": 2
},
{
"peerAsn": 64513,
"localIpAddress": "10.0.0.5",
"peerIpAddress": "10.0.0.6",
"shutdown": false,
"description": "Secondary BGP session",
"bfdEnabled": false
}
]
```
| Parameter | Description | Required | Valid input |
| - | - | - | - |
| peerAsn | The ASN of the remote BGP peer. | Yes | 1 -- 4294967294 |
| localAsn | Overrides the NAT Gateway ASN for this peer. | No | 1 -- 4294967294 |
| localIpAddress | The IPv4 address on this interface to use for the BGP peer. | Yes | Valid IPv4 address |
| peerIpAddress | The IPv4 or IPv6 address of the BGP peer. | Yes | Valid IP address |
| password | A shared key to authenticate the BGP peer. | No | 0 -- 32 characters |
| importWhitelist | Permit filter applied to inbound BGP advertisements. Must be the `id` of an existing prefix list. See [Prefix lists](#prefix-lists). | No | Integer (prefix list ID) |
| importBlacklist | Deny filter applied to inbound BGP advertisements. Must be the `id` of an existing prefix list. See [Prefix lists](#prefix-lists). | No | Integer (prefix list ID) |
| exportWhitelist | Permit filter applied to outbound BGP advertisements. Must be the `id` of an existing prefix list. See [Prefix lists](#prefix-lists). | No | Integer (prefix list ID) |
| exportBlacklist | Deny filter applied to outbound BGP advertisements. Must be the `id` of an existing prefix list. See [Prefix lists](#prefix-lists). | No | Integer (prefix list ID) |
| shutdown | Temporarily disables the BGP session without removing it. | No | `true`/`false`. Defaults to `false`. |
| description | Description of the BGP connection. | No | 0 -- 100 characters |
| medIn | MED applied to all routes received on this BGP connection. | No | 0 -- 4,294,967,295 |
| medOut | MED applied to all routes transmitted on this BGP connection. | No | 0 -- 4,294,967,295 |
| asPathPrependCount | Number of times the local AS number is prepended on outgoing announcements. | No | 1 -- 10 |
| bfdEnabled | Enables Bidirectional Forwarding Detection on this BGP connection. | No | `true`/`false`. Defaults to `false`. |
| asOverride | Enables AS Override for eBGP peering. When enabled, replaces the peer's ASN with the local ASN in the AS path. This is useful when connecting sites that share the same ASN. Only valid for eBGP connections. | No | `true`/`false`. Defaults to `false`. |
## Bidirectional Forwarding Detection (BFD)
The `bfd` configuration object applies to all BGP connections on the interface that have `bfdEnabled = true`.
When you enable BFD, the system automatically applies these fixed settings:
* : 300 milliseconds
* : 300 milliseconds
* : 3
These settings apply to all BGP connections on the VXC where BFD is enabled.
## Static routes
You can configure static routes per interface by adding an `ipRoutes` array to the `interfaces` array of the A-End partner configuration:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"ipRoutes": [
{
"prefix": "10.1.0.0/24",
"nextHop": "10.0.0.2",
"description": "Route to private subnet"
}
]
```
| Parameter | Description | Required | Valid input |
| - | - | - | - |
| prefix | The IP prefix (IPv4 or IPv6) to route to the next hop. | Yes | IPv4 or IPv6 CIDR |
| nextHop | The next hop address. Must be in the same subnet as the interface. | Yes | IPv4 or IPv6 address |
| description | Description of the static route. | No | Max 100 characters |
## Prefix lists
Prefix lists are named sets of IP prefixes that you can apply to BGP connections to filter route advertisements. You reference a prefix list by its `id` in the BGP connection parameters `importWhitelist`, `importBlacklist`, `exportWhitelist`, and `exportBlacklist`.\
For more information, see [BGP connections](#bgp-connections).
For more information about prefix filtering, see [Megaport NAT Gateway BGP Prefix Filtering](/nat/bgp-prefix-filtering).
The tasks in this section include how to:
* get a summary of all prefix lists
* create a prefix list
* get a prefix list
* update a prefix list
* delete a prefix list
**To get a summary of all prefix lists**
Send a GET request to retrieve all prefix lists on a NAT Gateway.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/{productUid}/prefix_list_summaries
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| `productUid` | The unique identifier of the NAT gateway product. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/abc12345-1234-1234-1234-abc123456789/prefix_list_summaries
```
**Response**
The response includes the ID, description, and address family for each prefix list:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "List prefix list summaries.",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"id": 1,
"description": "Allowed routes",
"addressFamily": "IPv4"
}
]
}
```
**To create a prefix list**
Send a POST request to the prefix lists endpoint with the configuration as the request Body.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/products/nat_gateways/{productUid}/prefix_lists
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| `productUid` | The unique identifier of the NAT gateway product. |
**Example Request Body**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"description": "Allowed routes",
"addressFamily": "IPv4",
"entries": [
{
"prefix": "10.0.0.0/8",
"action": "permit",
"ge": "24",
"le": "32"
},
{
"prefix": "192.168.0.0/16",
"action": "deny"
}
]
}
```
**Response**
A successful response (HTTP 200) includes the created prefix list with its assigned `id`.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Prefix list created.",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"id": 1,
"description": "Allowed routes",
"addressFamily": "IPv4",
"entries": [
{
"prefix": "10.0.0.0/8",
"action": "permit",
"ge": "24",
"le": "32"
},
{
"prefix": "192.168.0.0/16",
"action": "deny"
}
]
}
}
```
| Parameter | Description | Required | Valid input |
| - | - | - | - |
| description | The name used to reference this prefix list in BGP connection configuration. | Yes | String |
| addressFamily | The IP address family for all entries in this list. | Yes | `IPv4`, `IPv6` |
| entries | The list of prefix rules. | Yes | Array |
| entries.prefix | The network address in CIDR notation. | Yes | IPv4 or IPv6 CIDR |
| entries.action | The action to take for matching prefixes. | Yes | `permit`, `deny` |
| entries.ge | The minimum prefix length to match (greater than or equal). | No | 0 -- 32 (IPv4), 0 -- 128 (IPv6) |
| entries.le | The maximum prefix length to match (less than or equal). Must be >= `ge` if both are specified. | No | 0 -- 32 (IPv4), 0 -- 128 (IPv6) |
**To get a prefix list**
Send a GET request. Replace `{prefixListId}` with the ID from the prefix list summary.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/{productUid}/prefix_lists/{prefixListId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| `productUid` | The unique identifier of the NAT gateway product. |
| `prefixListId` | The unique identifier of the prefix list. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/abc12345-1234-1234-1234-abc123456789/prefix_lists/1
```
**Response**
A successful response (HTTP 200) returns the prefix list details.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Action completed successfully",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"id": 1,
"description": "Allowed routes",
"addressFamily": "IPv4",
"entries": [
{
"prefix": "10.0.0.0/8",
"action": "permit",
"ge": "24",
"le": "32"
},
{
"prefix": "192.168.0.0/16",
"action": "deny"
}
]
}
}
```
**To update a prefix list**
To replace all existing entries in the list, send a PUT request with the full prefix list configuration in the request Body.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
PUT {baseUrl}/v3/products/nat_gateways/{productUid}/prefix_lists/{prefixListId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| `productUid` | The unique identifier of the NAT gateway product. |
| `prefixListId` | The unique identifier of the prefix list. |
**Example Request Body**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"description": "Allowed routes",
"addressFamily": "IPv4",
"entries": [
{
"prefix": "10.0.0.0/8",
"action": "permit",
"ge": "24",
"le": "32"
},
{
"prefix": "192.168.0.0/16",
"action": "deny"
}
]
}
```
**Response**
A successful response (HTTP 200) returns the updated prefix list.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Action completed successfully",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"id": 1,
"description": "Allowed routes",
"addressFamily": "IPv4",
"entries": [
{
"prefix": "10.0.0.0/8",
"action": "permit",
"ge": "24",
"le": "32"
},
{
"prefix": "192.168.0.0/16",
"action": "deny"
}
]
}
}
```
**To delete a prefix list**
Send a DELETE request to the prefix lists endpoint.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
DELETE {baseUrl}/v3/products/nat_gateways/{productUid}/prefix_lists/{prefixListId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| `productUid` | The unique identifier of the NAT gateway product. |
| `prefixListId` | The unique identifier of the prefix list. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
DELETE {baseUrl}/v3/products/nat_gateways/abc12345-1234-1234-1234-abc123456789/prefix_lists/1
```
**Response**
A successful response (HTTP 200) confirms the prefix list was deleted.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Prefix List '1' deleted successfully",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy"
}
```
## Packet filters
Packet filters control traffic flow to and from the NAT Gateway by defining ordered rules that match packets based on protocol, source and destination addresses, and ports. Entries are evaluated in order, and the first matching rule determines the action.\
For more information, see [Using Packet Filters with NAT Gateway](/nat/packet-filters).
The tasks in this section include how to:
* get a summary of all packet filters
* create a packet filter
* get a packet filter
* update a packet filter
* delete a packet filter
**To get a summary of all packet filters**
Send a GET request to retrieve all packet filters on a NAT Gateway.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/{productUid}/packet_filter_summaries
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| `productUid` | The unique identifier of the NAT gateway product. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/abc12345-1234-1234-1234-abc123456789/packet_filter_summaries
```
**Response**
The response includes the ID and description for each packet filter:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "List packet filter summaries.",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"id": 1,
"description": "Allow web traffic"
}
]
}
```
**To create a packet filter**
Send a POST request to the packet filters endpoint with the configuration as the request Body.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/products/nat_gateways/{productUid}/packet_filters
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| `productUid` | The unique identifier of the NAT gateway product. |
**Example Request Body**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"description": "Allow web traffic",
"entries": [
{
"action": "permit",
"sourceAddress": "10.0.0.0/8",
"destinationAddress": "0.0.0.0/0",
"ipProtocol": 6,
"sourcePorts": "1-65535",
"destinationPorts": "443",
"description": "Allow outbound HTTPS"
},
{
"action": "deny",
"sourceAddress": "0.0.0.0/0",
"destinationAddress": "0.0.0.0/0",
"description": "Deny all other traffic"
}
]
}
```
**Response**
A successful response (HTTP 200) includes the created packet filter with its assigned `id`.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Packet filter created.",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"id": 1,
"description": "Allow web traffic",
"entries": [
{
"action": "permit",
"sourceAddress": "10.0.0.0/8",
"destinationAddress": "0.0.0.0/0",
"ipProtocol": 6,
"sourcePorts": "1-65535",
"destinationPorts": "443",
"description": "Allow outbound HTTPS"
},
{
"action": "deny",
"sourceAddress": "0.0.0.0/0",
"destinationAddress": "0.0.0.0/0",
"description": "Deny all other traffic"
}
]
}
}
```
| Parameter | Description | Required | Valid input |
| - | - | - | - |
| description | The name for this packet filter. | Yes | String |
| entries | The list of packet filter rules, evaluated in order. | Yes | Array |
| entries.action | The action to take on matching packets. | Yes | `permit`, `deny` |
| entries.sourceAddress | The source IP address or CIDR range. | Yes | IPv4 or IPv6 CIDR |
| entries.destinationAddress | The destination IP address or CIDR range. | Yes | IPv4 or IPv6 CIDR |
| entries.ipProtocol | The IP protocol number. Common values: `1` (ICMP), `6` (TCP), `17` (UDP). | No | Integer |
| entries.sourcePorts | Source port or port range. Only applies to TCP and UDP. | No | Integer or range (for example, `80` or `1-65535`) |
| entries.destinationPorts | Destination port or port range. Only applies to TCP and UDP. | No | Integer or range (for example, `443` or `8080-8090`) |
| entries.description | Description of the entry. | No | String |
**To get a packet filter**
Send a GET request. Replace `{packetFilterId}` with the ID from the packet filter summary.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/{productUid}/packet_filters/{packetFilterId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| `productUid` | The unique identifier of the NAT gateway product. |
| `packetFilterId` | The unique identifier of the packet filter. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/products/nat_gateways/abc12345-1234-1234-1234-abc123456789/packet_filters/1
```
**Response**
A successful response (HTTP 200) returns the packet filter details.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Action completed successfully",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"id": 1,
"description": "Allow web traffic",
"entries": [
{
"action": "permit",
"sourceAddress": "10.0.0.0/8",
"destinationAddress": "0.0.0.0/0",
"ipProtocol": 6,
"sourcePorts": "1-65535",
"destinationPorts": "443",
"description": "Allow outbound HTTPS"
},
{
"action": "deny",
"sourceAddress": "0.0.0.0/0",
"destinationAddress": "0.0.0.0/0",
"description": "Deny all other traffic"
}
]
}
}
```
**To update a packet filter**
To replace all existing entries in the configuration, send a PUT request with the full packet filter configuration in the request Body.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
PUT {baseUrl}/v3/products/nat_gateways/{productUid}/packet_filters/{packetFilterId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| `productUid` | The unique identifier of the NAT gateway product. |
| `packetFilterId` | The unique identifier of the packet filter. |
**Example Request Body**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"description": "Allow web traffic",
"entries": [
{
"action": "permit",
"sourceAddress": "10.0.0.0/8",
"destinationAddress": "0.0.0.0/0",
"ipProtocol": 6,
"sourcePorts": "1-65535",
"destinationPorts": "443",
"description": "Allow outbound HTTPS"
},
{
"action": "deny",
"sourceAddress": "0.0.0.0/0",
"destinationAddress": "0.0.0.0/0",
"description": "Deny all other traffic"
}
]
}
```
**Response**
A successful response (HTTP 200) returns the updated packet filter.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Action completed successfully",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"id": 1,
"description": "Allow web traffic",
"entries": [
{
"action": "permit",
"sourceAddress": "10.0.0.0/8",
"destinationAddress": "0.0.0.0/0",
"ipProtocol": 6,
"sourcePorts": "1-65535",
"destinationPorts": "443",
"description": "Allow outbound HTTPS"
},
{
"action": "deny",
"sourceAddress": "0.0.0.0/0",
"destinationAddress": "0.0.0.0/0",
"description": "Deny all other traffic"
}
]
}
}
```
**To delete a packet filter**
Send a DELETE request to the packet filters endpoint.
**Endpoint**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
DELETE {baseUrl}/v3/products/nat_gateways/{productUid}/packet_filters/{packetFilterId}
```
**Path Parameters**
| Parameter | Description |
| :- | :- |
| `productUid` | The unique identifier of the NAT gateway product. |
| `packetFilterId` | The unique identifier of the packet filter. |
**Example Request**
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
DELETE {baseUrl}/v3/products/nat_gateways/abc12345-1234-1234-1234-abc123456789/packet_filters/1
```
**Response**
A successful response (HTTP 200) confirms the packet filter was deleted.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Packet Filter '1' deleted successfully",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy"
}
```
## Autoconfiguration for CSPs
For AWS Hosted VIF, Azure, and Google Cloud, Megaport can set up IP addressing and BGP on both the NAT Gateway and the CSP side. This minimizes the amount of switching between the CSP and Megaport portals.
While the Portal handles autoconfiguration by default, you can also use the API to trigger it. The functionality is triggered when the `interfaces` key in `partnerConfig` does not exist or is `null`.
**To configure BGP peering for CSPs**
1. Create a request with this URL:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
2. Create the request Body with the configuration details. Templates for the most popular CSPs are available below.
### AWS Hosted VIF
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"productUid": "{ natGatewayUid }",
"associatedVxcs": [
{
"productName": "Test AWS VIF VXC",
"rateLimit": 100,
"term": 12,
"aEnd": {
"partnerConfig": {
"connectType": "VROUTER"
}
},
"bEnd": {
"productUid": "{ awsPortUid }",
"partnerConfig": {
"connectType": "AWS",
"type": "private",
"ownerAccount": "{ yourAWSAccountNumber }"
}
}
}
]
}
```
### Google Cloud
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"productUid": "{ natGatewayUid }",
"associatedVxcs": [
{
"productName": "Test Google VXC",
"rateLimit": 100,
"term": 12,
"aEnd": {
"partnerConfig": {
"connectType": "VROUTER"
}
},
"bEnd": {
"productUid": "{ googlePortUid }",
"partnerConfig": {
"connectType": "GOOGLE",
"pairingKey": "{ googlekey }"
}
},
"productType": "VXC"
}
]
}
```
### Microsoft Azure
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"productUid": "{ natGatewayUid }",
"associatedVxcs": [
{
"productName": "Azure Primary VXC",
"rateLimit": 200,
"aEnd": {
"partnerConfig": {
"connectType": "VROUTER"
}
},
"bEnd": {
"productUid": "{ azurePortUid }",
"innerVlan": 12,
"partnerConfig": {
"connectType": "AZURE",
"serviceKey": "{ azureServiceKey }",
"peers": [{"type": "private"}]
}
}
}
]
}
```
To see all options for the requests used in this example, see [https://dev.megaport.com](https://dev.megaport.com).
# Creating a Port with the API
Source: https://docs.megaport.com/api/api-port
This help topic describes how to use the Megaport API to create a Megaport.
This topic describes the API procedure to create a Port, including how to look up Port locations, validate the Port and determine the cost, order the Port, and download the .
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
**To look up Port location details in the Postman collection**
1. Click **Locations** in the left navigation and click **GET Locations (v3)**.\
This request is not expecting Parameters or Body information.
2. Click **Send** to make the request.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v3/locations
```
Ensure the request was successful by looking for Status: 200 OK and display the response in the Body section in the Pretty format.
The request returns hundreds of Port locations. You can search by clicking the magnifying glass and entering a specific city, data center, or other parameter in the search field. This example uses the Digital Realty, London location.
```json {2,17} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"id": 89,
"name": "Digital Realty London LHR20",
"address": {
"street": "227 Marsh Wall",
"suburb": null,
"city": "London",
"state": null,
"postcode": "E14 9SD",
"country": "United Kingdom"
},
"dataCentre": {
"id": 3,
"name": "Digital Realty"
},
"metro": "London",
"market": "UK",
"status": "Active",
"longitude": -0.012144,
"latitude": 51.499714,
"orderingMessage": null,
"diversityZones": {
"red": {
"mcrSpeedMbps": [
5000,
100000,
1000,
25000,
10000,
2500,
50000
],
"megaportSpeedMbps": [
100000,
10000,
1000
],
"mveMaxCpuCoreCount": null,
"mveAvailable": true
},
"blue": {
"mcrSpeedMbps": [
1000,
2500,
5000,
10000
],
"megaportSpeedMbps": [
1000,
10000,
100000
],
"mveMaxCpuCoreCount": null,
"mveAvailable": true
}
},
"productAddOns": {
"crossConnect": {
"available": false,
"type": null
}
}
}
```
To create a Port, you need the `market` value and `id` value. In this example, the market is UK and the data center ID is 89.
**To test and validate the Port order**
1. In Postman, open the **Ports** folder in the left navigation and select **POST Validate Port Order (v3)**.
2. Update the Body with the `locationId` (89), `term` (number of months - 1, 12, 24, 36, 48, or 60), `productName` (whatever name you want for your Port), `portSpeed` (1000, 10000, or 100000 Mbps), and `market` (UK) and click **Send**.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"locationId": 89,
"term": 1,
"locationUid": null,
"productName": "API Port",
"productType": "MEGAPORT",
"createDate": 1452475039656,
"portSpeed": 1000,
"virtual": false,
"promoCode": "promox3mnthfree2",
"market": "UK"
}
]
```
A successful response passes validation and has a 200 OK status. The response also includes pricing details of the service.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Validation passed",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"price": {
"hourlySetup": 0,
"dailySetup": 0,
"monthlySetup": 0,
"hourlyRate": 0,
"dailyRate": 0,
"monthlyRate": 500.00,
"fixedRecurringCharge": 500.00,
"postPaidBaseRate": "no base rate",
"longHaulMbpsRate": 0,
"mbpsRate": 0,
"currency": "GBP",
"key": "no key",
"productType": "MEGAPORT",
"empty": false
},
"serviceName": "API Port",
"productType": "MEGAPORT",
"productUid": "f9859fd3-344d-4a33-8cd2-a3b6ebfaaef0",
"market": "UK",
"string": "London"
}
]
}
```
**To order the validated Port**
1. With a validated Port request and reviewed cost information, copy the Body from **POST Validate Port Order (v3)** and paste into the Body of **POST Buy Port (v3)**.
If you make this call on api.megaport.com, your account will be charged for the service. Alternatively, you can provision against the staging API without charges, as in these examples.
2. Send the request.\
A successful response includes a `technicalServiceUid`, which is the same as the `productUid`.\
For our example, this value is a49cf3f1-20a1-4390-93aa-5005bdafe3d7.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "MEGAPORT [a49cf3f1-20a1-4390-93aa-5005bdafe3d7] created. ",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"serviceName": "API Port",
"name": "API Port",
"secondaryName": null,
"technicalServiceId": 68124,
"technicalServiceUid": "a49cf3f1-20a1-4390-93aa-5005bdafe3d7",
"requestedDate": 1588862976322,
"configuredDate": null,
"currentEstimatedDelivery": null,
"companyName": "Megaport Lab",
"companyId": 2278,
"aggregationId": null,
"lagPrimary": false,
"billingContactName": null,
"billingContactId": null,
"adminContactName": null,
"adminContactId": null,
"technicalContactName": null,
"technicalContactId": null,
"salesName": null,
"salesId": null,
"billableId": 56333,
"billableUsageAlgorithm": "NOT_POST_PAID",
"productType": "MEGAPORT",
"provisioningStatus": "DEPLOYABLE",
"inAdvanceBillingStatus": "NOT_ACTIVATED",
"provisioningItems": [],
"tags": [],
"vxcDistanceBand": null,
"intercapPath": null,
"marketplaceVisibility": true,
"vxcPermitted": true,
"vxcAutoApproval": false,
"createDate": 1588862976322,
"terminationDate": null,
"contractStartDate": 1588860000000,
"contractTermMonths": 1,
"rateType": "MONTHLY",
"trialAgreement": false,
"payerCompanyId": null,
"nonPayerCompanyId": null,
"minimumSpeed": null,
"maximumSpeed": null,
"rateLimit": 10000,
"errorMessage": null,
"market": "UK",
"accountManager": null,
"promptUid": null,
"components": [],
"attributes": [],
"aLocation": null,
"bLocation": null,
"aLocationId": null,
"bLocationId": null,
"attributeTags": {},
"createdBy": "a51cc1c6-95a0-48c7-a5a0-e49d77a6c536",
"buyoutPort": false,
"virtual": false,
"locked": false,
"adminLocked": false
}
]
}
```
The new Port now appears in your working environment, either portal.megaport.com or portal-staging.megaport.com.
To see all options for the requests used in this example, see [https://dev.megaport.com](https://dev.megaport.com).
## Download the Letter of Authorization (LOA)
After you create your Port, you can download the LOA.
Before you can download the LOA, the Provisioning Status of the Port must be Configured.
**To download the LOA**
1. In Postman, expand **Ports** in the left navigation and select **GET Regenerate LOA for Megaport Service**.
2. In the GET command, replace the `productID` with the value created during Port creation.
3. Send the request.
With a successful 200 OK response, this message appears in the Body section:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
This response could not be previewed.
Download the response to open it with an appropriate application.
```
This message appears because the LOA is a PDF document and must be downloaded. To download, click **Save Response** in Postman and save the PDF to a convenient location.
# Creating a Megaport Object Storage Connection with the API
Source: https://docs.megaport.com/api/api-storage
This help topic describes how to use the Megaport API to create a Megaport Object Storage connection.
This topic describes the API procedure to create a Megaport Object Storage connection from a Port, MCR, MVE, or NAT Gateway that you own. A Megaport Object Storage connection is a Virtual Cross Connect (VXC) with your existing service as the A-End and a storage destination as the B-End.
The steps include how to:
* get the `productUid` for the service to use as the A-End
* find the storage destination to use as the B-End
* validate and order the VXC
## Prerequisites
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
You also need:
* Object Storage provisioned in the Latitude.sh Portal. For more information, see [Megaport Object Storage Overview](/storage/object).
* A provisioned Port, MCR, MVE, or NAT Gateway to use as the A-End of the connection.
For the equivalent Megaport Portal procedure, see [Creating a Megaport Object Storage Connection](/storage/object/creating-storage-connection).
## Getting the productUid for the A-End service
To create the VXC, you need the `productUid` of the service to connect from.
**To get the productUid for the A-End service**
1. Get the product list.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/products/
```
2. From the returned product details, locate the `productUid` value for the Port, MCR, MVE, or NAT Gateway you want to connect from.
This example uses this value: `ef59ff80-7f50-11f1-b1ba-59b488c88b57`
## Finding the storage destination for the B-End
The storage destination is the B-End of the connection. Discover the available storage destinations by filtering the Megaport partner interfaces on the `STORAGE` connect type.
**To find the storage destination**
1. Get the list of interfaces Megaport has with partners, filtered on the `STORAGE` connect type.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/dropdowns/partner/megaports?connectType=STORAGE
```
2. From the response, select the storage destination that matches the location where you provisioned your storage.
Connect to the location where you provisioned your storage. Connecting to a different location does not provide access to your buckets.
To order the VXC, you need the following IDs for the B-End from the response:
* `locationId` -- The ID of the storage location.
* `productUid` -- The storage port to connect to.
* `companyUid` -- The ID of the storage provider, used as the `ownerUid` on the B-End.
## Validating and ordering the connection
You set the storage configuration on the B-End `partnerConfig`, where you specify the BGP details for the connection. The A-End `partnerConfig` is empty.
A storage connection requires BGP. At a minimum, specify the `asn`. You can add the BGP `password` when you create the VXC or after it is provisioned.
Set the B-End `vlan` to `-1` so that the storage port assigns the VLAN rather than you choosing one. Set the A-End `vlan` to `0`.
The validate endpoint uses v3 of the API while the buy endpoint uses v4.
**To validate the configuration**
1. Create a request with this URL:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/validate
```
2. Add these headers to the request:
* `Content-Type: application/json`
* `Authorization: Bearer {your accessToken}`
3. Create the request Body with the configuration details.
The validate request Body is an array of design objects. Each design object identifies the A-End service with `productUid` and carries the storage VXC in `associatedVxcs`.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "ef59ff80-7f50-11f1-b1ba-59b488c88b57",
"associatedVxcs": [
{
"productName": "Storage Test",
"rateLimit": 1000,
"term": 12,
"shutdown": false,
"aEnd": {
"vlan": 0,
"partnerConfig": {}
},
"bEnd": {
"locationId": 85,
"ownerUid": "2f83dc65-5d4c-4730-a66d-926db48a0326",
"productUid": "41bbbdbe-8aa4-4af2-91b4-d1d56f1db4aa",
"vlan": -1,
"partnerConfig": {
"asn": "65333",
"password": "new-password",
"prefixes": null,
"route_table": null,
"connectType": "STORAGE",
"complete": true
}
},
"productType": "VXC",
"connectType": "STORAGE"
}
]
}
]
```
A successful response returns `"message": "Validation passed"` and the pricing details for the connection.
**To order the connection**
1. After you validate the configuration, create a request with this URL:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v4/networkdesign/buy
```
2. Create the request Body.\
The buy request wraps the design objects from the validate step in a `networkDesign` array, alongside a `discountCodes` array.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"discountCodes": [],
"networkDesign": [
{
"productUid": "ef59ff80-7f50-11f1-b1ba-59b488c88b57",
"associatedVxcs": [
{
"productName": "Storage Test",
"rateLimit": 1000,
"term": 12,
"shutdown": false,
"aEnd": {
"vlan": 0,
"partnerConfig": {}
},
"bEnd": {
"locationId": 85,
"ownerUid": "2f83dc65-5d4c-4730-a66d-926db48a0326",
"productUid": "41bbbdbe-8aa4-4af2-91b4-d1d56f1db4aa",
"vlan": -1,
"partnerConfig": {
"asn": "65333",
"password": "new-password",
"prefixes": null,
"route_table": null,
"connectType": "STORAGE",
"complete": true
}
},
"productType": "VXC",
"connectType": "STORAGE"
}
]
}
]
}
```
3. Send the request.
If the request is successful, the response confirms the created VXC, including its `technicalServiceUid`. The VXC then appears in the Megaport Portal.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "VXC [a10475cd-6ca3-4c1d-ae31-90af53efb945] created.",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"serviceName": "Storage Test",
"technicalServiceUid": "a10475cd-6ca3-4c1d-ae31-90af53efb945",
"provisioningStatus": "DEPLOYABLE",
"productType": "VXC",
"connectType": "STORAGE"
}
]
}
```
## Storage connection parameters
The storage configuration is set on the B-End `partnerConfig`.
| Parameter | Description | Required | Valid input |
| - | - | - | - |
| connectType | Identifies the connection as a storage connection. | Yes | `STORAGE` |
| asn | The ASN used for the BGP session to your storage. Specify a private or public ASN, or use the default Megaport ASN, `133937`. | Yes | String |
| password | The shared key used to authenticate the BGP peer. You can add it when you create the VXC or after it is provisioned. | No | 1 -- 25 characters |
| prefixes | Public IPv4 prefixes to announce to Latitude.sh. `null` in this example. For guidance on prefixes, see [Creating a Megaport Object Storage Connection](/storage/object/creating-storage-connection). | No | String |
| route\_table | Present in the payload; `null` in this example. | No | String |
| complete | Indicates the storage configuration is complete. | No | `true` |
In this example, `prefixes` and `route_table` are set to `null`. The format for populated values for these parameters is not covered in this example.
To see all options for the requests used in this example, see [https://dev.megaport.com](https://dev.megaport.com).
## Helpful references
* [Creating a Megaport Object Storage Connection](/storage/object/creating-storage-connection)
* [Megaport Object Storage Billing](/finance/storage-billing)
* [Megaport Object Storage Overview](/storage/object)
* [Megaport Object Storage Pricing and Contract Terms](/finance/storage-pricing)
* [Terminating a Megaport Object Storage Connection](/storage/object/terminating-connection)
# Creating a VXC Between Two Ports with the API
Source: https://docs.megaport.com/api/api-vxc
This help topic describes how to use the Megaport API to create a VXC Between two configured Megaports.
This topic describes the API procedure to create a VXC between two Ports that you own, including how to get the Port IDs, validate the VXC, and order the VXC.
The example in this topic creates a VXC between a Port in Digital Realty, London, UK and another Port in Iron Mountain, Ashburn, US.
To create the VXC, we need the `productUid` for each Port.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
**To get the productUid for the Ports to connect**
1. In Postman, click **Product Details** in the left navigation and click **GET Product List**.
2. Click **Send**.
3. From the returned product details, locate the `productUid` values for the two Ports you want to connect.\
This example uses these Ports:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"productName": "API Port London" with "productUid": "7f5f9574-315e-4527-af44-122605a411de"
"productName": "API Port2 Ashburn" with "productUid": "1f751b96-87c5-4bbf-8a7a-a93a04f71a70",
```
**To review pricing details and validate the configuration for the point-to-point VXC**
1. In Postman, expand **Connections > Virtual Cross Connects** in the left navigation and click **POST Validate VXC Order (v3)**.
2. Update the Body with the `productUids` for each end of the connection.\
You can also change additional values, such as name, rate limit, contract term, whether the connection is enabled or shut down, and VLAN ID.
3. Click **Send** to make a POST request.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/validate
```
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "7f5f9574-315e-4527-af44-122605a411de",
"associatedVxcs": [
{
"productName": "My API created VXC",
"rateLimit": 500,
"term":12,
"shutdown": false,
"promoCode": "promox3mnthfree2",
"aEnd": {
"vlan": 102
},
"bEnd": {
"productUid": "1f751b96-87c5-4bbf-8a7a-a93a04f71a70",
"vlan": 101
}
}
]
}
]
```
After you validate the request and review the pricing details in the response, create the VXC.
**To create the VXC between the Ports**
1. Copy the validated Body from **POST Validate VXC Order (v3)** and paste it into the Body of **POST Buy VXC (v3)**.
2. Click **Send** to post the request.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
The resulting point-to point VXC appears in the Megaport Portal.
# Creating a VXC to AWS with the API
Source: https://docs.megaport.com/api/api-vxc-aws
This help topic describes how to use the Megaport API to create a VXC for a Hosted VIF connection to AWS.
This topic describes the API procedure to create a VXC from a Port to AWS, including how to look up cloud interconnect locations, validate the connection, and order the VXC.
The example in this topic creates a Hosted VIF connection to AWS with a data rate of 500 Mbps. To step through this example, use the staging environment URL, which lets you configure the connections but does not deploy or charge for the services.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
To see all options for the requests used in this example, see [https://dev.megaport.com](https://dev.megaport.com).
## Look up AWS port location details
To create a VXC to AWS, you need to know the AWS port details. Use the API to return the interfaces Megaport has with cloud service providers, to identify the required AWS port details.
**To look up AWS port location details in the Postman collection**
1. Expand the **Locations** folder in the left navigation and click **GET Partner Megaports**.
2. Click **Send** to make a GET request to the API server.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/dropdowns/partner/megaports
```
This request returns all the interfaces Megaport has with Cloud Service Providers. You can search by clicking the magnifying glass and entering a location, data center, or other parameter in the search field.
The connectType indicates the Cloud Service Provider. AWS includes "AWS" for Hosted VIFs and "AWSHC" for Hosted Connections.
You can filter the results by `connectType` and `vxcPermitted`.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/dropdowns/partner/megaports?connectType=AWS&vxcPermitted=true
```
This example uses a port in Interxion DUB2 that is accepting VXCs (`"vxcPermitted": true`) and is in the region eu-west-1.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"connectType": "AWS",
"productUid": "6cc21ccb-5ecc-4869-ab0e-b3fa17f5110f",
"vxcPermitted": true,
"companyUid": "623cb950-abb4-4b07-b372-8cf55756c322",
"companyName": "AWS",
"title": "EU (Ireland) (eu-west-1)",
"locationId": 96,
"speed": 10000,
"rank": 61,
"lag_id": 2,
"lag_primary": true,
"aggregation_id": 54188
},
```
## Create and deploy a VXC
With the AWS port details from the **GET Partner Megaports** API, you can validate and then create a VXC.
**To test and validate the order**
1. In Postman, expand **Cloud Connectivity > Port > AWS Direct Connect** in the left navigation and select **POST Validate AWS - Hosted VIF (v3)**.
2. Update the Body of the request with the `productUid` of the Port, the `productUid` of the AWS port, and the AWS account ID.\
You can also change additional values, such as name, rate limit, contract term, VLAN ID, ASN values, authKey, and IP addressing.
3. Click **Send** to POST the request.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/validate
```
```json {3,15,22} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "a49cf3f1-20a1-4390-93aa-5005bdafe3d7",
"associatedVxcs": [
{
"productName": "My Amazon Direct Connect",
"rateLimit": "500",
"term": 12,
"shutdown": false,
"promoCode": "promox3mnthfree2",
"aEnd": {
"vlan": 777
},
"bEnd": {
"productUid": "6cc21ccb-5ecc-4869-ab0e-b3fa17f5110f",
"partnerConfig": {
"connectType": "AWS",
"name": "Amazon name for service",
"type": "private",
"asn": 65105,
"amazonAsn": 64555,
"ownerAccount": "XXXXXXXXXXXX",
"authKey": "123456",
"prefixes": "10.0.1.0/24",
"customerIpAddress": null,
"amazonIpAddress": null
}
}
}
]
}
]
```
When validated, you are ready to place the VXC order.
**To create a VXC**
1. Copy the validated Body from **POST Validate AWS - Hosted VIF (v3)** and paste into the Body of **POST Buy AWS - Hosted VIF (v3)**.
2. Click **Send** to post the request.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
Here is an example of a successful response.
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "VXC [47d6cc4d-6a1a-4301-b06c-cebb5f9b8f3e] created. ",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": [
{
"createDate": 1588868593704,
"vxcOrderId": 42328,
"payerMegaPortId": 68124,
"nonPayerMegaPortId": 52786,
"payerMegaPortName": "API Port",
"nonPayerMegaPortName": "EU (Ireland) (eu-west-1)",
"payerCompanyId": 2278,
"nonPayerCompanyId": 117,
"payerLocationId": 89,
"nonPayerLocationId": 96,
"salesId": null,
"payerCompanyName": "Megaport Lab",
"nonPayerCompanyName": "AWS",
"payerMegaPortNsId": 138231,
"nonPayerMegaPortNsId": 221182,
"payerVlanId": 777,
"nonPayerVlanId": 0,
"payerApproverName": "Paul McGuinness",
"payerApproverId": 12695,
"nonPayerApproverName": "Paul McGuinness",
"nonPayerApproverId": 12684,
"payerApproval": 1582268553574,
"nonPayerApproval": 1228868693614,
"fixedTerm": true,
"duration": 1,
"rollover": true,
"serviceName": "from API Port to EU (Ireland) (eu-west-1)",
"payerStatus": "APPROVED",
"nonPayerStatus": "APPROVED",
"speed": 500,
"distanceBand": "ZONE",
"intercapPath": "",
"awsId": null,
"promoCode": null,
"rateType": "MONTHLY",
"vxcJTechnicalServiceId": 57115,
"vxcJTechnicalServiceUid": "47d6cc4d-6a1a-4301-b06c-cebb5f9b8f3e",
"provisionDate": 1588868593517,
"orderType": "NEW",
"monthlyDiscountAmount": null,
"discountMonths": null,
"amazonDirectConnectConfigDto": {
"type": "private",
"asn": 65105,
"ownerAccount": "XXXXXXXXXXXX",
"authKey": "123456",
"customerIpAddress": null,
"amazonIpAddress": null,
"prefixes": "10.0.1.0/24",
"name": "Amazon name for service"
},
"amsixConnectConfigDto": null,
"webAirProvItem": null,
"sdrcProvItem": null,
"rate": null,
"setup": null,
"asn": null,
"bgpPassword": null,
"usageAlgorithm": "POST_PAID_HOURLY_SPEED_LONG_HAUL_VXC",
"costCentre": null,
"azureServiceKey": null,
"oracleVirtualCircuitId": null,
"serviceKey": null,
"connectType": "AWS",
"payerConfig": {},
"nonPayerConfig": {},
"attributeTags": {},
"fullyApproved": true
}
]
}
```
The Port and VXC now appear in the Megaport Portal.
For this example, the AWS Hosted VIF will appear in the AWS portal account under Direct Connect - Virtual Interfaces. The account holder can accept the Virtual Interface and connect it to a Virtual Private Gateway or a Direct Connect Gateway and then to their VPCs.
# Creating a VXC between a Port and Microsoft Azure with the API
Source: https://docs.megaport.com/api/api-vxc-azure
This help topic describes how to use the Megaport API to create a VXC to Microsoft Azure.
This topic describes the API procedure to create a VXC from a Port to Microsoft Azure ExpressRoute, including how to look up Azure port locations and order the VXCs.
The Port to Azure deployment includes these tasks:
1. **Set up an ExpressRoute circuit in the Azure console**
When deployed, you get a service key. The service key is linked to the assigned ports in Azure. When you validate a service key, the response shows the assigned primary and secondary ports in Azure. You can use the service key twice - once to connect to the primary and a second time and create another connection to the secondary port.\
For more information, see the Microsoft help topic [Tutorial: Create and modify an ExpressRoute circuit](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-circuit-portal-resource-manager).
2. **With the service key, create and deploy your VXCs from the Megaport Portal**
This step uses the API -- the other steps are outside of Megaport in the Azure environment.
3. **With a VXC deployed to your circuit, configure peering in the Azure portal**
Peering information is shared between the primary and secondary circuits, as is the inner VLAN assigned to the peer.\
For more information, see the Microsoft help topic [Create and modify peering for an ExpressRoute circuit](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-routing-portal-resource-manager).
4. **Configure customer premises equipment (CPE) device**
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
## Validate the service key
When you use the API to validate an Azure service key, the response includes ExpressRoute details of the associated ports and peers. You need the port details to create the VXCs.
**To validate the service key in the Postman collection**
1. In Postman, expand **Cloud Connectivity > Port > Azure** in the left navigation and select **GET Look Up Azure Service Key**.
2. Add the service key to the endpoint.
3. Click **Send** to make a GET request to the API server.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/secure/azure/{service_key}
```
Here is a sample response for a new key (without configured VXCs):
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Successful lookup",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"managed": false,
"connectType": "AZURE",
"resource_type": "csp_connection",
"bandwidth": 200,
"service_key": "3e2480b2-b4d5-424b-976a-7b0de65a1b62",
"vlan": 3289,
"megaports": [
{
"portSpeed": 10000,
"name": "Washington DC Primary",
"state": "VA",
"description": "Azure ExpressRoute at Equinix DC2/6",
"productUid": "a7ae8a35-433e-44aa-87cb-a1b7995ab008",
"nServiceId": 32832,
"companyUid": "c40de5ed-4707-4471-a78c-69436de2c505",
"country": "USA",
"vxc": null,
"port": 14570,
"companyName": "Azure ExpressRoute",
"locationId": 67,
"productId": 14570,
"type": "primary",
"companyId": 1475
},
{
"portSpeed": 10000,
"name": "Washington DC Secondary",
"state": "VA",
"description": "Azure ExpressRoute at Equinix DC2/6",
"productUid": "07ab0ee6-7f77-41ac-bbe6-335e3ee6d182",
"nServiceId": 36431,
"companyUid": "c40de5ed-4707-4471-a78c-69436de2c505",
"country": "USA",
"vxc": null,
"port": 16108,
"companyName": "Azure ExpressRoute",
"locationId": 67,
"productId": 16108,
"type": "secondary",
"companyId": 1475
}
],
"peers": []
}
}
```
The `megaports:vxc` value is null for both Ports, indicating they are available for new VXCs.
For more information about each response field, see [Azure Service Key Response Fields](/api/api-azure-servicekey).
## Create and deploy the VXCs
With the details from the service key, create a VXC to the primary port and another VXC to the secondary port.
**To create the VXCs**
1. Select **POST Create VXC to Azure (v3)**.
To test your request before you order and see pricing details, you can use:
`POST {baseUrl}/v3/networkdesign/validate`
2. Update the Body of the request with the `productUid` of the Port, the name of the VXC, the `productUid` of the primary Azure port, and the service key. The maximum speed (`rateLimit`) is defined in the bandwidth value of the service key response. In this case, it is 200.
3. Click **Send** to post the request.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
```json {3,6,15,18} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "1544f278-ec03-11e5-9ce9-5e5517507c66", //port UID of your Megaport (A-End)
"associatedVxcs": [
{
"productName": "Primary Azure VXC",
"rateLimit": 200,
"term":12,
"shutdown": false,
"promoCode": "promox3mnthfree2",
"aEnd": {
"vlan": 102
},
"bEnd": {
"productUid": "a7ae8a35-433e-44aa-87cb-a1b7995ab008", //retrieved port UID from the Azure service key lookup
"partnerConfig" : {
"connectType": "AZURE",
"serviceKey": "3e2480b2-b4d5-424b-976a-7b0de65a1b62" //service key from lookup response
}
}
}
]
}
]
```
When you have configured your primary and secondary VXCs to the Azure ports, another service key lookup shows the VXCs associated with the Azure ports. The VXCs are identified by an ID number (`megaports:vxc`).
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Successful lookup",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"managed": false,
"connectType": "AZURE",
"resource_type": "csp_connection",
"bandwidth": 200,
"service_key": "3e2480b2-b4d5-424b-976a-7b0de65a1b62",
"vlan": 3289,
"megaports": [
{
"portSpeed": 10000,
"name": "Washington DC Primary",
"state": "VA",
"description": "Azure ExpressRoute at Equinix DC2/6",
"productUid": "a7ae8a35-433e-44aa-87cb-a1b7995ab008",
"nServiceId": 32832,
"companyUid": "c40de5ed-4707-4471-a78c-69436de2c505",
"country": "USA",
"vxc": 60621,
"port": 14570,
"companyName": "Azure ExpressRoute",
"locationId": 67,
"productId": 14570,
"type": "primary",
"companyId": 1475
},
{
"portSpeed": 10000,
"name": "Washington DC Secondary",
"state": "VA",
"description": "Azure ExpressRoute at Equinix DC2/6",
"productUid": "07ab0ee6-7f77-41ac-bbe6-335e3ee6d182",
"nServiceId": 36431,
"companyUid": "c40de5ed-4707-4471-a78c-69436de2c505",
"country": "USA",
"vxc": 60622,
"port": 16108,
"companyName": "Azure ExpressRoute",
"locationId": 67,
"productId": 16108,
"type": "secondary",
"companyId": 1475
}
],
"peers": []
}
}
```
To complete the configuration, [configure peering](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-routing-portal-resource-manager) in the Azure portal and configure your CPE devices.
# Changing a VXC Configuration with the API
Source: https://docs.megaport.com/api/api-vxc-change
This help topic describes how to use the Megaport API to change the configured details of a VXC.
This topic describes how to change configuration details of an existing VXC. For more information, see [PUT Update VXC (v3)](https://dev.megaport.com/#4293df4a-545d-45a2-bfa1-90f41df13160) in the API reference.
You can change the VXC service name, rate limit, VLAN IDs, contract term, VXC state (enabled or shut down), and A-End and B-End productUids, by updating any of these parameters in the Body of the request:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"name": "My updated API created VXC",
"rateLimit": 100,
"aEndVlan": 301,
"bEndVlan": 402,
"term":12,
"shutdown": true,
"aEndProductUid": "a3ec7ef6-7e29-4a3f-a37d-582b468fd68b",
"bEndProductUid": "9be424c0-87c7-480e-9d62-57f619bf6e2f"
}
```
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
**To change the VXC details in the Postman collection**
1. In Postman, expand **Connections > Virtual Cross Connects** in the left navigation and click **PUT Update VXC (v3)**.
2. Identify the VXC to update by adding the `productUid` to the endpoint.
3. Select the **Body** tab and update VXC details for name, rate limit, VLAN IDs, contract term, A-End productUid, or B-End productUid.\
Change the productUid if you want to move the A-End or B-End of the VXC.\
The update request only needs to include the parameters you want to change.\
This example changes the following values.
4. Click **Send**.\
The changes will be reflected in the Portal within two minutes.
## Helpful references
* [Moving a VXC and IX with the API](/api/api-vxc-move)
* [Shutting Down a VXC and IX with the API](/api/api-vxc-shut-down)
# Creating a VXC between a Port and Google Cloud with the API
Source: https://docs.megaport.com/api/api-vxc-google
This help topic describes how to use the Megaport API to create a VXC to Google Cloud.
This topic describes the API procedure to create a VXC from a Port to Google Cloud, including how to look up Google Cloud port locations and order the VXC.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
## Look up Google pairing key
A connection between a Port and Google Cloud requires a pairing key. You get this key from the Google Cloud portal. You use the API to validate a Google Cloud pairing key and the response includes details of the associated ports and peers. You need the port details to create the VXC.
**To look up the pairing key in the Postman collection**
1. In Postman, expand **Cloud Connectivity > Port > Google Cloud** in the left navigation and select **GET Look Up Google Pairing Key**.
2. Add the pairing key to the endpoint.
3. Click **Send** to make a GET request to the API server.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/secure/google/{pairing_key}
```
Here is a sample response for a pairing key with the first VXC configured but the second VXC available (vxc = null):
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Successful lookup",
"data": {
"bandwidths": [
50,
100,
200,
300,
400,
500,
1000,
2000,
5000,
10000
],
"megaports": [
{
"port": 13687,
"vxc": {
// existing vxc object
},
"productId": 13687,
"productUid": "2c9337ba-b6a6-44cc-851c-58315060a0e3",
"name": "New York (lga-zone2-1422)",
"nServiceId": 30890,
"description": "Google Inc at Digital Realty NYC1",
"companyId": 90,
"companyUid": "29ba879b-45c8-48eb-bd97-618d0f20ea04",
"companyName": "Google Inc",
"portSpeed": 10000,
"locationId": 62,
"state": "NY",
"country": "USA"
},
{
"port": 12515,
"vxc": null,
"productId": 12515,
"productUid": "2fa8c6c5-314f-4d14-8fb6-e1f7f86bdacc",
"name": "Ashburn (iad-zone2-1)",
"nServiceId": 28349,
"description": "Google Inc at zColo 21635 Red Rum Drive",
"companyId": 90,
"companyUid": "29ba879b-45c8-48eb-bd97-618d0f20ea04",
"companyName": "Google Inc",
"portSpeed": 10000,
"locationId": 84,
"state": "VA",
"country": "USA"
}
],
"resource_type": "csp_connection"
}
}
```
## Create and deploy a VXC
With the details from the pairing key, create a VXC to the available port.
**To create a VXC**
1. Select **POST Create VXC to Google Cloud (v3)**.
To test your request before you order and see pricing details, you can use:
`POST {baseUrl}/v3/networkdesign/validate`
2. Update the Body of the request with the `productUid` of the Port, the name of the VXC, the `productUid` of the Google Cloud port, and the pairing key. The bandwidth options are defined in the list returned by the pairing key and you must use a predefined bandwidth.
3. Click **Send** to post the request.
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
POST {baseUrl}/v3/networkdesign/buy
```
```json {3,10,15,18} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
[
{
"productUid": "d5f4a3c6-06d3-4cfa-9d4e-8ce6ec0b6dbd", //UID of your Megaport (A-End)
"associatedVxcs": [
{
"rateLimit": 100, // from list of supported bandwidths in key lookup
"term":12,
"shutdown": false,
"promoCode": "promox3mnthfree2",
"productName": "Example Google VXC",
"aEnd": {
"vlan": 90,
},
"bEnd": {
"productUid": "7bab4547-ff88-43f9-a1de-3df637522fa5", // port UID from pairing key lookup
"partnerConfig": {
"connectType": "GOOGLE",
"pairingKey": "fbbf41b1-9513-4837-a91a-22a8bb065704/us-west1/2"
}
},
"productType": "VXC"
}
]
}
]
```
Once you have completed and deployed the VXC, go back to the Google Cloud Console and accept the attachment. You will be provided your private IP address from Google to configure BGP.
This completes your Layer 2 VXC deployment.
# Moving a VXC and IX with the API
Source: https://docs.megaport.com/api/api-vxc-move
This help topic describes how to use the Megaport API to move a VXC and IX for failover testing.
This topic describes how to move a VXC and IX service.
Once you have created and deployed a VXC or IX on the Megaport network, you can move the A-End (VXC and IX) or B-End (VXC only), effectively moving the service. This is a useful function for reducing interruptions during maintenance and other tasks that would otherwise cause downtime.
For more information, see [Moving VXCs](/connections/move-vxc) and [Moving IXs](/ix/move-ix).
You can move a VXC or IX by changing the `productUid` of the A-End or B-End, depending on the service. You can use the optional `aEndProductUid` or `bEndProductUid` parameters in the Body of the request:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"aEndProductUid": "0ee41f61-4f03-5555-8afe-77fcc949c804"
}
```
When moving a VXC for an MVE, you can also select the vNICs at the A-End and B-End using the parameters `aVnicIndex` and `bVnicIndex`. For more information, see [PUT Update VXC (v3)](https://dev.megaport.com/#4293df4a-545d-45a2-bfa1-90f41df13160) in the API developer portal.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
**To move a VXC in the Postman collection**
1. In Postman, expand **Connections > Virtual Cross Connects** in the left navigation and click **PUT Update VXC (v3)**.
2. Identify the VXC to update by adding the `productUid` to the endpoint.
3. Select the **Body** tab and add the `aEndProductUID` with the UID of the new A-End.\
You can update the A-End or B-End of a VXC, but you can only move one end per API call.
4. Click **Send**.\
The changes will be reflected in the Portal within two minutes. The Services page shows the VXC moved to the new A-End or B-End, depending on the specification.
**To move an IX in the Postman collection**
1. In Postman, expand **Internet Exchange (IX)** in the left navigation and click **PUT Update IX**.
2. Identify the IX to update by adding the `productUid` to the endpoint.
3. Select the **Body** tab and add the `aEndProductUID`.
4. Click **Send**.\
The changes will be reflected in the Portal within two minutes. The Services page shows the IX moved to the new A-End.
# Shutting Down a VXC and IX with the API
Source: https://docs.megaport.com/api/api-vxc-shut-down
This help topic describes how to use the Megaport API to shut down a VXC and IX for failover testing.
This topic describes how to shut down and re-enable a VXC and IX service that has been deployed on the Megaport network. You can also shut down a VXC and IX service when creating the service, if required.
After you have created and deployed a VXC or IX on the Megaport network, you can temporarily shut down the service for failover testing, redundancy, or network design testing purposes. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
You can shut down a VXC/IX by setting the optional `shutdown` parameter to true in the Body of the request. If not provided, it defaults to false (enabled):
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"shutdown": true
}
```
To re-enable the VXC/IX, set the `shutdown` parameter to false:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"shutdown": false
}
```
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
**To shut down a VXC in the Postman collection**
1. In Postman, expand **Connections > Virtual Cross Connects** in the left navigation and click **PUT Update VXC (v3)**.
2. Identify the VXC to update by adding the `productUid` to the endpoint.
3. Select the **Body** tab and update the `shutdown` parameter to true.
4. Click **Send**.\
The changes will be reflected in the Portal within two minutes. The Services page shows the gear icon next to the VXC in blue when the service has been shut down, and the text (Shut Down) is displayed next to the service ID.
5. To re-enable the VXC, change the `shutdown` parameter to false and run the **PUT Update VXC (v3)** API again.
**To shut down an IX in the Postman collection**
1. In Postman, expand **Internet Exchange (IX)** in the left navigation and click **PUT Update IX**.
2. Identify the IX to update by adding the `productUid` to the endpoint.
3. Select the **Body** tab and update the `shutdown` parameter to true.
4. Click **Send**.\
The changes will be reflected in the Portal within two minutes. The Services page shows the gear icon next to the IX in blue when the service has been shut down, and the text (Shut Down) is displayed next to the service ID.
5. To re-enable the IX, change the `shutdown` parameter to false and run the **PUT Update IX** API again.
# Megaport API Overview
Source: https://docs.megaport.com/api/index
This help topic describes the Megaport public API to access to Megaport services.
Megaport offers a public API for access to all the services available through the Megaport Portal.
You can use this API to automate your Megaport provisioning to save time and effort.
The Megaport API is based on REST. The API has predictable URLs, accepts form-encoded request bodies, returns json-encoded responses, and uses standard HTTP response codes.
The topics in this section step you through the API calls needed to perform common tasks such as logging in, creating a Port, and creating a VXC from the Port to a cloud provider.
Beyond these topics, you can view a complete API reference at
[https://dev.megaport.com](https://dev.megaport.com).
From time to time we update, change versions, and deprecate APIs when releasing new functionality. We recommend that you keep up to date with these changes and plan any API integration updates accordingly. For more information, see [API Deprecation Notices and Frequently Asked Questions (FAQs)](/troubleshooting/api-v2-faq).
## Environments
There are two server environments for the APIs:
* **Production environment** -- `https://api.megaport.com`\
You are responsible for any services and associated costs ordered in this system.
API changes through `https://api.megaport.com` are reflected in the Megaport Portal.
* **Staging (test) environment** -- `https://api-staging.megaport.com`\
You can test any action in this staging environment and the API calls and responses mirror the production system, but services will not be deployed and you will not be billed for any activity.
Your staging portal account reflects the staging services created; however, these will be reset every 24 hours.
You can use your production credentials to log in to the staging environment and order or edit services. (New user accounts take 24 hours before they are available for use in staging.)
API changes through `https://api-staging.megaport.com` are reflected in the [Staging Portal](https://portal-staging.megaport.com/).
The requests in the API topics use the `{baseUrl}` variable. You can replace this with the staging URL (`https://api-staging.megaport.com`) or the production URL (`https://api.megaport.com`) depending on whether you want to test configurations or work with your production deployment. If you use the Postman collection (described in the next section), you can define [environment variables](https://learning.postman.com/docs/sending-requests/managing-environments/) in the collection to automatically populate the baseUrl value in API requests and easily switch between staging and production environments.
## Getting started with the API and Postman
When writing and deploying your client-side code to call the Megaport API, you can use any language you prefer from Java to Python.
To step through the tutorials in these API topics, we recommend the Postman client with the imported Megaport Collection.
Postman is a straightforward, powerful HTTP client that helps build, test, and modify APIs. You can use it to interact with any functionality on any API. Postman Collections are simply a set of pre-built requests organized into folders, and they can be easily exported and shared with others.
Before you can get started with the Megaport Collection in Postman, you need a Megaport Account and you need to [install Postman](https://www.postman.com/downloads/).
**To set up the Megaport Collection in Postman**
* Download the postman API collection from [dev.megaport.com](https://dev.megaport.com/).\
Click the **Run In Postman** button in the top right corner of the linked page.
# Setting up OpenMetrics for Service Monitoring
Source: https://docs.megaport.com/api/monitoring/api-openmetrics
This help topic describes how to set up the Prometheus / OpenMetrics Megaport API to monitor the status of Megaport services.
This feature is currently in Beta and the format is subject to change.
This topic describes an example configuration for setting up the Prometheus / OpenMetrics endpoint in Megaport's API.
OpenMetrics is a specification for representing and exchanging metrics data in a standardized format, primarily influenced by the Prometheus exposition format.
With the OpenMetrics endpoint integrated into Megaport's API, this allows you to expose existing service monitoring information.
In the Prometheus configuration example below, the scrape interval is set to one minute, but the network is only polled every five minutes. You will need to consider this in your PromQL/Grafana dashboarding.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
### Megaport API details
* **API**: /v1/openmetrics
* **Authentication**: API key/OAuth2
## Example Prometheus Configuration
```yaml theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
global:
scrape_interval: 5m
scrape_configs:
- job_name: megaport
static_configs:
- targets: ["api.megaport.com"]
scheme: https
metrics_path: /v1/openmetrics
oauth2:
token_url: https://auth-m2m.megaport.com/oauth2/token
client_id:
client_secret:
```
## Metrics
The endpoint currently exports these metrics for all services.
### Port
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
# HELP megaport_service_input_errors_total The total number of input errors.
# TYPE megaport_service_input_errors_total counter
# HELP megaport_service_optical_receive_power_dbm Optical receive power level in dBm.
# TYPE megaport_service_optical_receive_power_dbm gauge
# HELP megaport_service_optical_transmit_power_dbm Optical transmit power level in dBm.
# TYPE megaport_service_optical_transmit_power_dbm gauge
# HELP megaport_service_output_errors_total The total number of output errors.
# TYPE megaport_service_output_errors_total counter
# HELP megaport_service_receive_bytes_total The total number of bytes received.
# TYPE megaport_service_receive_bytes_total counter
# HELP megaport_service_receive_packets_total The total number of packets received.
# TYPE megaport_service_receive_packets_total counter
# HELP megaport_service_transmit_bytes_total The total number of bytes transmitted.
# TYPE megaport_service_transmit_bytes_total counter
# HELP megaport_service_transmit_packets_total The total number of packets transmitted.
# TYPE megaport_service_transmit_packets_total counter
# HELP megaport_service_up Operational status of the service.
# TYPE megaport_service_up gauge
```
### VXC
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
# HELP megaport_service_receive_bytes_total The total number of bytes received.
# TYPE megaport_service_receive_bytes_total counter
# HELP megaport_service_receive_packets_total The total number of packets received.
# TYPE megaport_service_receive_packets_total counter
# HELP megaport_service_transmit_bytes_total The total number of bytes transmitted.
# TYPE megaport_service_transmit_bytes_total counter
# HELP megaport_service_transmit_packets_total The total number of packets transmitted.
# TYPE megaport_service_transmit_packets_total counter
# HELP megaport_service_up Operational status of the service.
# TYPE megaport_service_up gauge
```
### MCR
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
# HELP megaport_service_receive_bytes_total The total number of bytes received.
# TYPE megaport_service_receive_bytes_total counter
# HELP megaport_service_receive_packets_total The total number of packets received.
# TYPE megaport_service_receive_packets_total counter
# HELP megaport_service_transmit_bytes_total The total number of bytes transmitted.
# TYPE megaport_service_transmit_bytes_total counter
# HELP megaport_service_transmit_packets_total The total number of packets transmitted.
# TYPE megaport_service_transmit_packets_total counter
# HELP megaport_service_up Operational status of the service.
# TYPE megaport_service_up gauge
```
### MVE
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
# HELP megaport_service_receive_bytes_total The total number of bytes received.
# TYPE megaport_service_receive_bytes_total counter
# HELP megaport_service_receive_packets_total The total number of packets received.
# TYPE megaport_service_receive_packets_total counter
# HELP megaport_service_transmit_bytes_total The total number of bytes transmitted.
# TYPE megaport_service_transmit_bytes_total counter
# HELP megaport_service_transmit_packets_total The total number of packets transmitted.
# TYPE megaport_service_transmit_packets_total counter
# HELP megaport_service_up Operational status of the service.
# TYPE megaport_service_up gauge
```
## Helpful references
* [Monitoring Service Status with the API](/api/monitoring)
* [OpenMetrics](https://openmetrics.io/)
* [Grafana](https://grafana.com/)
* [Prometheus Documentation](https://prometheus.io/docs/introduction/overview/)
# Monitoring Service Status with the API
Source: https://docs.megaport.com/api/monitoring/index
This help topic describes how to use the Megaport API to monitor the status of Megaport services.
You can retrieve the status of any Megaport service (such as Port, VXC, MCR, or MVE) with this request available in the Product Details folder of the Postman collection:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/product/{productUid}
```
The response includes the provisioning status of the service in the `provisioningStatus` field.
The `provisioningStatus` field can have the following values:
| Provisioning Status | Description | Port | MCR, MVE, or NAT Gateway | MegaIX, Megaport Internet, Megaport Marketplace, or other VXC connections |
| :- | :- | :- | :- | :- |
| NEW | Only for preordering Ports. This status indicates the service order has been accepted and is waiting on the infrastructure to be available. | This status applies to Port preorders only. The Port cannot accept any connections (such as a VXC) and is not billed. | N/A | N/A |
| DESIGN | The service has been added, but has not been ordered or deployed. | | | |
| DEPLOYABLE | The service order has been confirmed and is waiting for deployment. Services are typically in this state for 1-2 minutes. | | | |
| CONFIGURED | The deployment has completed and the service is configured on the network. | | | |
| LIVE | The meaning of this status depends on the product. | The service has been detected as live on the network. Light has been detected on the Port, meaning a Cross Connect has been attached and the Port activated. | The transition from CONFIGURED to LIVE is instantaneous. | The transition from CONFIGURED to LIVE is instantaneous. |
| CANCELLED, CANCELLED\_PARENT | Termination of the service has been requested. Services are typically in this state for 1-2 minutes. | You can terminate Ports directly and they remain in this state for up to 2 minutes. | You can terminate MCRs, MVEs, and NAT Gateways directly and they remain in this state for up to 2 minutes. | You can terminate VXCs directly or by terminating the attached Port, MCR, MVE, or NAT Gateway. |
| DECOMMISSIONED | The service has been decommissioned from the network. The service is billed only for the time that it was in use before it was decommissioned. Products on a term will incur early termination fees (ETF). | | | |
| FAILED | The service could not be deployed and is not in the deployment queue. | | | |
Additionally, the response to the `/v2/product/` endpoint for any Megaport service includes the current status of the service. The status in the root level `up` parameter indicates if the service is up (a value of true) or down (a value of false). This example shows the `up` parameter for a VXC.
```json {56} theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Found Product 9fbc4f9e-5f59-458e-bb95-6633e77ab121",
"terms": "This data is subject to the Acceptable Use Policy https://www.megaport.com/legal/acceptable-use-policy",
"data": {
"productId": 220451,
"productUid": "9fbc4f9e-5f59-458e-bb95-6633e77ab121",
"productName": "WEST AWS",
"secondaryName": null,
"productType": "VXC",
"rateLimit": 50,
"maximumRate": 10000,
"distanceBand": "METRO",
"provisioningStatus": "LIVE",
"usageAlgorithm": "POST_PAID_VARIABLE",
"createdBy": "cb9c4d7e-4cd2-4f6b-4f4e-89ab263e57e4",
"liveDate": 1733253865042,
"createDate": 1733253767229,
"resources": {
"csp_connection": {
"bandwidth": 50,
"connectType": "AWSHC",
"resource_name": "b_csp_connection",
"resource_type": "csp_connection",
"name": "WEST AWS",
"ownerAccount": "206049248854",
"bandwidths": [
50
],
"connectionId": "dxcon-fftxgi4j"
},
"vll": {
"a_vlan": 2612,
"b_vlan": 2612,
"rate_limit_mbps": 50,
"resource_name": "vll",
"resource_type": "vll",
"up": 1,
"shutdown": false
}
},
"vxcApproval": {
"status": null,
"message": null,
"uid": null,
"type": null,
"newSpeed": null
},
"contractStartDate": 1733253865055,
"contractEndDate": 1735912800000,
"contractTermMonths": 12,
"companyUid": "160408ae-01e4-4cb9-8d57-03a147bd47a8",
"companyName": "Megaport Test",
"locked": false,
"adminLocked": false,
"attributeTags": {},
"up": true,
"shutdown": false,
"cancelable": true,
"aEnd": {
"ownerUid": "160408ae-01e4-4cb9-8d57-03a147bd47a8",
"productUid": "21be60a4-14c8-454f-9636-c6a4ad9f8447",
"productName": "ZW TEST",
"locationId": 147,
"location": "CyrusOne Chandler",
"locationDetail": {
"name": "CyrusOne Chandler",
"city": "Phoenix",
"metro": "Phoenix",
"country": "USA"
},
"vlan": 2612,
"innerVlan": null,
"secondaryName": null,
"connectType": "DEFAULT",
"diversityZone": "red"
},
"bEnd": {
"ownerUid": "605cb840-dfb4-4a05-a171-8bf17757b4a2",
"productUid": "d2b92be4-d85c-4ae5-b511-37c1cfe6e146",
"productName": "US West (N. California) (us-west-1)",
"locationId": 370,
"location": "PhoenixNAP",
"locationDetail": {
"name": "PhoenixNAP",
"city": "Phoenix",
"metro": "Phoenix",
"country": "USA"
},
"vlan": 2612,
"innerVlan": null,
"secondaryName": null,
"connectType": "AWSHC",
"diversityZone": "red"
}
}
}
```
## Helpful references
* [Monitoring MCR](/monitoring/mcr-monitoring)
* [Monitoring MVE](/monitoring/mve-monitoring)
* [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring)
* [Viewing Activity Logs](/portal-admin/activity-logs)
# Telemetry Metric Types
Source: https://docs.megaport.com/api/monitoring/telemetry-metric-types
This help topic describes the Megaport telemetry API endpoints and the metric types they return, including the units and sub-types for each metric.
The Megaport telemetry API returns performance and status metrics for your services. Each request selects a metric through the `type` query parameter, using one of the metric type identifiers described in this topic. The API matches these identifiers case-insensitively.
Each service type has its own telemetry endpoint and its own set of metric types. The endpoints and their parameters are described in [Telemetry API endpoints](#telemetry-api-endpoints), and each metric type is defined in [Metric types](#metric-types).
For the Portal views of the same data, see [Service Telemetry](/monitoring/service-telemetry) and [IX Telemetry](/ix/ix-telemetry).
## Telemetry API endpoints
Retrieve telemetry data by sending a GET request to the endpoint for the service type you are monitoring. Each endpoint accepts a set of metric type values through its `type` query parameter.
Before you begin, obtain a valid access token. For more information, see [Creating an API Key](/api/api-key).
### Request parameters
Each request supports these parameters through its query string or path.
| Parameter | Required | Description |
| - | - | - |
| productUid | Yes | Path parameter. The UID of the service for which to return telemetry. |
| type | Yes | One or more metric type identifiers to return. Repeat the parameter to request more than one metric. |
| from / to | No | The start and end of the time range, as Unix timestamps in milliseconds. Supply both or neither. |
| days | No | The number of days of data to return, as an alternative to `from` and `to`. |
| resolution | No | The sampling resolution: `5min`, `daily`, or `monthly`. Defaults to `5min`. The `5min` resolution is limited to 180 days. |
### Endpoints by service type
Each endpoint accepts these metric type values.
| Service Type | Endpoint | Metric Types |
| - | - | - |
| Port | GET /v2/product/megaport/\{productUid}/telemetry | `BITS`, `PACKETS`, `ERRORS`, `OPTICAL`, `OPTICAL_100G`, `SUBSCRIBED_SPEED`, `SERVICE_COUNT` |
| VXC | GET /v2/product/vxc/\{productUid}/telemetry | `A_BITS`, `B_BITS`, `A_PACKETS`, `B_PACKETS` |
| MCR | GET /v2/product/mcr2/\{productUid}/telemetry | `BITS`, `PACKETS` |
| MVE | GET /v2/product/mve/\{productUid}/telemetry | `BITS`, `PACKETS` |
| IX | GET /v2/product/ix/\{productUid}/telemetry | `BITS`, `PACKETS`, `ROUTES_IMPORTED`, `ROUTES_FILTERED`, `BM_BYTES`, `BM_PACKETS`, `UU_BYTES`, `UU_PACKETS` |
| NAT Gateway | GET /v3/products/nat\_gateways/\{productUid}/telemetry | `BITS`, `PACKETS` |
## Metric types
The following metric types are available through the `type` query parameter. Each entry lists the metric type identifier, the unit its values are returned in, and its sub-types. Not every metric type applies to every service type. See [Telemetry API endpoints](#telemetry-api-endpoints) for the metric types each endpoint accepts.
### Traffic
`BITS` - Traffic on the service, reported separately for each direction. The measured value is returned to users in Megabits per second (Mbps) unit.
Sub-types:
* `In`
* `Out`
* `Configured speed (Mbps)` - The configured speed value, returned alongside In and Out
`A_BITS` - Traffic at the A-End of the connection, reported separately for each direction. The measured value is returned to users in Megabits per second (Mbps) unit.
Sub-types:
* `In`
* `Out`
* `Configured speed (Mbps)` - The configured speed value, returned alongside In and Out
`B_BITS` - Traffic at the B-End of the connection, reported separately for each direction. The measured value is returned to users in Megabits per second (Mbps) unit.
Sub-types:
* `In`
* `Out`
* `Configured speed (Mbps)` - The configured speed value, returned alongside In and Out
### Packets
`PACKETS` - Packets on the service, reported separately for each direction. The measured value is returned to users in packets per second (pps) unit.
Sub-types:
* `In`
* `Out`
`A_PACKETS` - Packets at the A-End of the connection, reported separately for each direction. The measured value is returned to users in packets per second (pps) unit.
Sub-types:
* `In`
* `Out`
`B_PACKETS` - Packets at the B-End of the connection, reported separately for each direction. The measured value is returned to users in packets per second (pps) unit.
Sub-types:
* `In`
* `Out`
### Errors
`ERRORS` - Errors on the service, reported separately for each direction. The measured value is returned to users in errors per second unit.
Sub-types:
* `In`
* `Out`
### Optical
`OPTICAL` - Optical signal levels for the service. The measured value is returned to users in decibel milliwatts (dBm) unit.
Sub-types:
* `Tx Power` - Light level transmitted
* `Rx Power` - Light level received
`OPTICAL_100G` - Optical signal levels for a 100 Gbps Port, reported per lane. Useful for measuring signal loss over the connection. The measured value is returned to users in decibel milliwatts (dBm) unit.
Sub-types:
* `Tx Power Lane` - Light level transmitted, reported for each lane
* `Rx Power Lane` - Light level received, reported for each lane
### Speed and service count
`SUBSCRIBED_SPEED` - The subscribed speed of the service. The measured value is returned to users in Megabits per second (Mbps) unit.
Sub-types:
* `Mbps` - The subscribed speed value
`SERVICE_COUNT` - The number of active services connected to the service. The measured value is returned to users as a count of services.
Sub-types:
* `Count` - The number of active services
### Routing
`ROUTES_IMPORTED` - A count of the BGP routes accepted from the IX peer, reported separately for each route server. The measured value is returned to users as a count of BGP routes.
Sub-types:
* `Primary IPv4`
* `Primary IPv6`
* `Secondary IPv4`
* `Secondary IPv6`
`ROUTES_FILTERED` - A count of the imported BGP routes dropped by Megaport route filters, reported separately for each route server. The measured value is returned to users as a count of BGP routes.
Sub-types:
* `Primary IPv4`
* `Primary IPv6`
* `Secondary IPv4`
* `Secondary IPv6`
### Broadcast, multicast, and unknown unicast
`BM_BYTES` - The volume of broadcast and multicast traffic emitted from the IX peer. The measured value is returned to users in Megabits per second (Mbps) unit.
Sub-types:
* `Bytes`
`BM_PACKETS` - The rate of broadcast and multicast packets emitted from the IX peer. The measured value is returned to users in packets per second (pps) unit.
Sub-types:
* `Packets`
`UU_BYTES` - The volume of unknown unicast traffic emitted from the IX peer. The measured value is returned to users in Megabits per second (Mbps) unit.
Sub-types:
* `Bytes`
`UU_PACKETS` - The rate of unknown unicast packets emitted from the IX peer. The measured value is returned to users in packets per second (pps) unit.
Sub-types:
* `Packets`
## Helpful references
* [Creating an API Key](/api/api-key)
* [IX Telemetry](/ix/ix-telemetry)
* [Service Telemetry](/monitoring/service-telemetry)
* [Setting up OpenMetrics for Service Monitoring](/api/monitoring/api-openmetrics)
# Billing Webhook Events
Source: https://docs.megaport.com/api/webhooks/events/billing
This help topic describes the billing webhook events.
This topic describes the billing events sent by Megaport's webhooks.
## billing.contract.expiring
`billing.contract.expiring` is sent when a billing contract is about to expire.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `billing_market` (string)
* `contract_expiry_date` (string, date-time)
* `is_auto_renew` (boolean)
* `monthly_rate` (number, double)
* `renewal_available_date` (string, date-time)
* `service_name` (string)
* `service_owner_company_uid` (string, UUID)
* `service_type` (string)
* `service_uid` (string, UUID)
* `term_months` (integer, int32)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "billing.contract.expiring",
"data": {
"billing_market": "US",
"contract_expiry_date": "2027-05-12T03:00:00Z",
"is_auto_renew": true,
"monthly_rate": 500,
"renewal_available_date": "2027-04-12T03:00:00Z",
"service_name": "My VXC",
"service_owner_company_uid": "123e4567-e89b-12d3-a456-426614174000",
"service_type": "VXC",
"service_uid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"term_months": 12
}
}
```
## billing.invoice.generated
`billing.invoice.generated` is sent when a billing invoice has been generated.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `billing_market` (string)
* `currency` (string)
* `invoice_amount` (number, double)
* `invoice_id` (string)
* `invoice_url` (string, uri)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "billing.invoice.generated",
"data": {
"billing_market": "US",
"currency": "USD",
"invoice_amount": 1500,
"invoice_id": "INV001234",
"invoice_url": "https://portal.megaport.com/settings/company/markets/market/123/invoice/INV001234"
}
}
```
## billing.service.retermed
`billing.service.retermed` is sent when a billing service has been re-termed.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `billing_market` (string)
* `contract_expiry_date` (string, date-time)
* `is_auto_renew` (boolean)
* `monthly_rate` (number, double)
* `service_name` (string)
* `service_owner_company_uid` (string, UUID)
* `service_type` (string)
* `service_uid` (string, UUID)
* `term_months` (integer, int32)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "billing.service.retermed",
"data": {
"billing_market": "US",
"contract_expiry_date": "2026-05-12T03:00:00Z",
"is_auto_renew": true,
"monthly_rate": 500,
"service_name": "My VXC",
"service_owner_company_uid": "123e4567-e89b-12d3-a456-426614174000",
"service_type": "VXC",
"service_uid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"term_months": 12
}
}
```
## billing.service.started
`billing.service.started` is sent when a service has started billing.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `billing_market` (string)
* `contract_expiry_date` (string, date-time)
* `is_auto_renew` (boolean)
* `monthly_rate` (number, double)
* `service_name` (string)
* `service_owner_company_uid` (string, UUID)
* `service_type` (string)
* `service_uid` (string, UUID)
* `term_months` (integer, int32)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "billing.service.started",
"data": {
"billing_market": "US",
"contract_expiry_date": "2026-05-12T03:00:00Z",
"is_auto_renew": true,
"monthly_rate": 500,
"service_name": "My VXC",
"service_owner_company_uid": "123e4567-e89b-12d3-a456-426614174000",
"service_type": "VXC",
"service_uid": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"term_months": 12
}
}
```
# Maintenance Webhook Events
Source: https://docs.megaport.com/api/webhooks/events/maintenance
This help topic describes the maintenance webhook events.
This topic describes the maintenance events sent by Megaport's webhooks.
## maintenance.cancelled
`maintenance.cancelled` is sent when scheduled maintenance has been cancelled.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `cancel_reason` (string)
* `company_uid` (string, UUID)
* `maintenance_uid` (string, UUID)
* `purpose` (string)
* `service_uids` (array of string, UUID)
* `window_end` (string, date-time)
* `window_start` (string, date-time)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "maintenance.cancelled",
"data": {
"cancel_reason": "Cancelled at vendor request due to upstream change conflict.",
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"maintenance_uid": "5a2c1f3e-7b9d-4f6a-8c11-9e9b1234abcd",
"purpose": "Software upgrade of MCR control plane.",
"service_uids": [
"3a8c0b2d-7f44-49ab-9a85-2bcd9e012345"
],
"window_end": "2026-05-12T03:00:00Z",
"window_start": "2026-05-12T01:00:00Z"
}
}
```
## maintenance.completed
`maintenance.completed` is sent when scheduled maintenance has been completed.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `company_uid` (string, UUID)
* `maintenance_uid` (string, UUID)
* `purpose` (string)
* `service_uids` (array of string, UUID)
* `window_end` (string, date-time)
* `window_start` (string, date-time)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "maintenance.completed",
"data": {
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"maintenance_uid": "5a2c1f3e-7b9d-4f6a-8c11-9e9b1234abcd",
"purpose": "Software upgrade of MCR control plane.",
"service_uids": [
"3a8c0b2d-7f44-49ab-9a85-2bcd9e012345"
],
"window_end": "2026-05-12T03:00:00Z",
"window_start": "2026-05-12T01:00:00Z"
}
}
```
## maintenance.failed
`maintenance.failed` is sent when scheduled maintenance has failed.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `company_uid` (string, UUID)
* `failure_reason` (string)
* `maintenance_uid` (string, UUID)
* `purpose` (string)
* `service_uids` (array of string, UUID)
* `window_end` (string, date-time)
* `window_start` (string, date-time)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "maintenance.failed",
"data": {
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"failure_reason": "Vendor cancelled the change window after the maintenance had already started.",
"maintenance_uid": "0c2f6cf2-7c8b-4a2c-9ff4-2c3a0b8a1d1b",
"purpose": "Replace faulty optic on edge router.",
"service_uids": [
"8a1c2d3e-4f5a-6b7c-8d9e-0f1a2b3c4d5e"
],
"window_end": "2026-05-23T03:00:00Z",
"window_start": "2026-05-23T01:00:00Z"
}
}
```
## maintenance.rescheduled
`maintenance.rescheduled` is sent when a maintenance window is rescheduled.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `company_uid` (string, UUID)
* `impact` (string)
* `maintenance_uid` (string, UUID)
* `message_to_customers` (string)
* `previous_window_end` (string, date-time)
* `previous_window_start` (string, date-time)
* `purpose` (string)
* `service_uids` (array of string, UUID)
* `window_end` (string, date-time)
* `window_start` (string, date-time)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "maintenance.rescheduled",
"data": {
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"impact": "Customer services may experience a brief disconnect during the failover.",
"maintenance_uid": "5a2c1f3e-7b9d-4f6a-8c11-9e9b1234abcd",
"message_to_customers": "Window moved by two hours to accommodate a dependent change.",
"previous_window_end": "2026-05-12T03:00:00Z",
"previous_window_start": "2026-05-12T01:00:00Z",
"purpose": "Software upgrade of MCR control plane.",
"service_uids": [
"3a8c0b2d-7f44-49ab-9a85-2bcd9e012345"
],
"window_end": "2026-05-12T05:00:00Z",
"window_start": "2026-05-12T03:00:00Z"
}
}
```
## maintenance.scheduled
`maintenance.scheduled` is sent when a maintenance window is scheduled.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `company_uid` (string, UUID)
* `impact` (string)
* `maintenance_uid` (string, UUID)
* `purpose` (string)
* `service_uids` (array of string, UUID)
* `window_end` (string, date-time)
* `window_start` (string, date-time)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "maintenance.scheduled",
"data": {
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"impact": "Customer services may experience a brief disconnect during the failover.",
"maintenance_uid": "5a2c1f3e-7b9d-4f6a-8c11-9e9b1234abcd",
"purpose": "Software upgrade of MCR control plane.",
"service_uids": [
"3a8c0b2d-7f44-49ab-9a85-2bcd9e012345"
],
"window_end": "2026-05-12T03:00:00Z",
"window_start": "2026-05-12T01:00:00Z"
}
}
```
# Order Webhook Events
Source: https://docs.megaport.com/api/webhooks/events/order
This help topic describes the order webhook events.
This topic describes the order events sent by Megaport's webhooks.
## order.ix.processed
`order.ix.processed` is sent when an IX order has been processed.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `order_date` (string, date-time)
* `port_service_uid` (string, UUID)
* `service_uid` (string, UUID)
* `term_months` (integer, int32)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "order.ix.processed",
"data": {
"order_date": "2026-04-23T03:30:05Z",
"port_service_uid": "34ee661a-18f0-4c30-8a73-e2d7e0ab641d",
"service_uid": "e513ab3e-8b0c-4d88-bef0-1f7358897d6e",
"term_months": 12
}
}
```
## order.megaport.processed
`order.megaport.processed` is sent when a port order has been processed.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `cross_connect_requested` (boolean)
* `location` (string)
* `order_date` (string, date-time)
* `service_uid` (string, UUID)
* `term_months` (integer, int32)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "order.megaport.processed",
"data": {
"cross_connect_requested": true,
"location": "DC1 Sydney",
"order_date": "2026-04-23T03:30:05Z",
"service_uid": "e513ab3e-8b0c-4d88-bef0-1f7358897d6e",
"term_months": 12
}
}
```
## order.request.approved
`order.request.approved` is sent when an order request is approved.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `approver_company_uid` (string, UUID)
* `order_type` (string)
* `order_uid` (string, UUID)
* `ordered_by_uid` (string, UUID)
* `product_type` (string)
* `service_uid` (string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "order.request.approved",
"data": {
"approver_company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"order_type": "NEW_ORDER",
"order_uid": "3bb5e87d-9b3d-4c43-bbbd-9132cde06616",
"ordered_by_uid": "fd2188e4-2ead-4f46-9a99-de0a333fbee2",
"product_type": "VXC",
"service_uid": "5a1b7c3d-2e9f-4a6b-8c1d-0e2f4a6b8c1d"
}
}
```
## order.request.failed
`order.request.failed` is sent when an order request failed.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `approver_company_uid` (string, UUID)
* `error_summary` (string)
* `order_type` (string)
* `order_uid` (string, UUID)
* `ordered_by_uid` (string, UUID)
* `product_type` (string)
* `service_uid` (string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "order.request.failed",
"data": {
"approver_company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"error_summary": "Provisioning timed out at upstream",
"order_type": "NEW_ORDER",
"order_uid": "3bb5e87d-9b3d-4c43-bbbd-9132cde06616",
"ordered_by_uid": "fd2188e4-2ead-4f46-9a99-de0a333fbee2",
"product_type": "VXC",
"service_uid": "5a1b7c3d-2e9f-4a6b-8c1d-0e2f4a6b8c1d"
}
}
```
## order.request.pending
`order.request.pending` is sent when an order request is pending.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `order_type` (string)
* `order_uid` (string, UUID)
* `ordered_by_uid` (string, UUID)
* `product_type` (string)
* `requester_company_uid` (string, UUID)
* `service_uid` (string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "order.request.pending",
"data": {
"order_type": "NEW_ORDER",
"order_uid": "3bb5e87d-9b3d-4c43-bbbd-9132cde06616",
"ordered_by_uid": "fd2188e4-2ead-4f46-9a99-de0a333fbee2",
"product_type": "VXC",
"requester_company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"service_uid": "5a1b7c3d-2e9f-4a6b-8c1d-0e2f4a6b8c1d"
}
}
```
## order.request.rejected
`order.request.rejected` is sent when an order request is rejected.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `approver_company_uid` (string, UUID)
* `comment` (string)
* `order_type` (string)
* `order_uid` (string, UUID)
* `ordered_by_uid` (string, UUID)
* `product_type` (string)
* `service_uid` (string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "order.request.rejected",
"data": {
"approver_company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"comment": "Budget not approved this quarter",
"order_type": "TERM_CHANGE",
"order_uid": "3bb5e87d-9b3d-4c43-bbbd-9132cde06616",
"ordered_by_uid": "fd2188e4-2ead-4f46-9a99-de0a333fbee2",
"product_type": "VXC",
"service_uid": "5a1b7c3d-2e9f-4a6b-8c1d-0e2f4a6b8c1d"
}
}
```
## order.request.withdrawn
`order.request.withdrawn` is sent when an order request is withdrawn.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `comment` (string)
* `order_type` (string)
* `order_uid` (string, UUID)
* `ordered_by_uid` (string, UUID)
* `product_type` (string)
* `requester_company_uid` (string, UUID)
* `service_uid` (string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "order.request.withdrawn",
"data": {
"comment": "Replacing with a different configuration",
"order_type": "NEW_ORDER",
"order_uid": "3bb5e87d-9b3d-4c43-bbbd-9132cde06616",
"ordered_by_uid": "fd2188e4-2ead-4f46-9a99-de0a333fbee2",
"product_type": "VXC",
"requester_company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"service_uid": "5a1b7c3d-2e9f-4a6b-8c1d-0e2f4a6b8c1d"
}
}
```
## order.vxc.approved
`order.vxc.approved` is sent when a marketplace VXC order request is approved.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `approver_company_uid` (string, UUID)
* `order_date` (string, date-time)
* `request_type` (string)
* `service_uid` (string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "order.vxc.approved",
"data": {
"approver_company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"order_date": "2026-04-23T03:30:05Z",
"request_type": "NEW",
"service_uid": "e513ab3e-8b0c-4d88-bef0-1f7358897d6e"
}
}
```
## order.vxc.pending
`order.vxc.pending` is sent when a marketplace VXC order request is pending.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `order_date` (string, date-time)
* `pending_days` (integer, int32)
* `request_type` (string)
* `requester_company_uid` (string, UUID)
* `service_uid` (string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "order.vxc.pending",
"data": {
"order_date": "2026-04-23T03:30:05Z",
"pending_days": 7,
"request_type": "NEW",
"requester_company_uid": "3bb5e87d-9b3d-4c43-bbbd-9132cde06616",
"service_uid": "e513ab3e-8b0c-4d88-bef0-1f7358897d6e"
}
}
```
## order.vxc.rejected
`order.vxc.rejected` is sent when a marketplace VXC order request is rejected.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `approver_company_uid` (string, UUID)
* `order_date` (string, date-time)
* `request_type` (string)
* `service_uid` (string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "order.vxc.rejected",
"data": {
"approver_company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"order_date": "2026-04-23T03:30:05Z",
"request_type": "NEW",
"service_uid": "e513ab3e-8b0c-4d88-bef0-1f7358897d6e"
}
}
```
## order.vxc.requested
`order.vxc.requested` is sent when a marketplace VXC order is requested.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `approver_company_uid` (string, UUID)
* `form_submission` (object)
* `order_date` (string, date-time)
* `requester_company_uid` (string, UUID)
* `service_uid` (string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "order.vxc.requested",
"data": {
"approver_company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"form_submission": {
"company_name": "Acme Corp",
"contact_email": "james@acme.com",
"requested_bandwidth": "1 Gbps"
},
"order_date": "2026-04-23T03:30:05Z",
"requester_company_uid": "3bb5e87d-9b3d-4c43-bbbd-9132cde06616",
"service_uid": "e513ab3e-8b0c-4d88-bef0-1f7358897d6e"
}
}
```
## order.vxc.servicekey.provisioned
`order.vxc.servicekey.provisioned` is sent when a VXC service is provisioned using a service key.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `owning_service_uid` (string, UUID)
* `service_key` (string)
* `vxc_service_uid` (string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "order.vxc.servicekey.provisioned",
"data": {
"owning_service_uid": "34ee661a-18f0-4c30-8a73-e2d7e0ab641d",
"service_key": "a6ff4g90-431d-1260-9fa6-98ae225e3234",
"vxc_service_uid": "e513ab3e-8b0c-4d88-bef0-1f7358897d6e"
}
}
```
## order.vxc.speed.change.requested
`order.vxc.speed.change.requested` is sent when a speed change is requested.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `order_date` (string, date-time)
* `requester_company_uid` (string, UUID)
* `service_uid` (string, UUID)
* `speed_mbps` (integer, int32)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "order.vxc.speed.change.requested",
"data": {
"order_date": "2026-04-23T03:30:05Z",
"requester_company_uid": "3bb5e87d-9b3d-4c43-bbbd-9132cde06616",
"service_uid": "e513ab3e-8b0c-4d88-bef0-1f7358897d6e",
"speed_mbps": 100
}
}
```
# Outage Webhook Events
Source: https://docs.megaport.com/api/webhooks/events/outage
This help topic describes the outage webhook events.
This topic describes the outage events sent by Megaport's webhooks.
## outage.advised
`outage.advised` is sent when an outage is being investigated.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `advisory_message` (string)
* `company_uid` (string, UUID)
* `label` (string)
* `outage_uid` (string, UUID)
* `service_uids` (array of string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "outage.advised",
"data": {
"advisory_message": "Carrier reports estimated repair time of two hours.",
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"label": "Sydney metro fibre cut affecting MCR2-SYD1.",
"outage_uid": "9f2c1f3e-7b9d-4f6a-8c11-9e9b1234abcd",
"service_uids": [
"3a8c0b2d-7f44-49ab-9a85-2bcd9e012345"
]
}
}
```
## outage.closed
`outage.closed` is sent when an outage has been resolved.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `company_uid` (string, UUID)
* `label` (string)
* `outage_uid` (string, UUID)
* `purpose` (string)
* `resolved_at` (string, date-time)
* `service_uids` (array of string, UUID)
* `started_at` (string, date-time)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "outage.closed",
"data": {
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"label": "Sydney metro fibre cut affecting MCR2-SYD1.",
"outage_uid": "9f2c1f3e-7b9d-4f6a-8c11-9e9b1234abcd",
"purpose": "Carrier outage between Sydney CBD and North Sydney.",
"resolved_at": "2026-04-29T16:08:00Z",
"service_uids": [
"3a8c0b2d-7f44-49ab-9a85-2bcd9e012345"
],
"started_at": "2026-04-29T14:21:00Z"
}
}
```
## outage.notice
`outage.notice` is sent when an outage has been reported.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `company_uid` (string, UUID)
* `description` (string)
* `label` (string)
* `next_update_note` (string)
* `notice_uid` (string, UUID)
* `outage_uid` (string, UUID)
* `service_uids` (array of string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "outage.notice",
"data": {
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"description": "Engineers are still investigating. Customers should expect intermittent BGP flaps in SYD2 until at least 02:30 UTC.",
"label": "SYD2 transit instability.",
"next_update_note": "Awaiting upstream carrier response before issuing the next update.",
"notice_uid": "f4e3d2c1-b0a9-4988-7766-554433221100",
"outage_uid": "1f4e7c0a-2b3d-4e5f-6a7b-8c9d0e1f2a3b",
"service_uids": [
"3a8c0b2d-7f44-49ab-9a85-2bcd9e012345"
]
}
}
```
## outage.reopened
`outage.reopened` is sent when an outage is reopened.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `company_uid` (string, UUID)
* `label` (string)
* `outage_uid` (string, UUID)
* `purpose` (string)
* `reopened_at` (string, date-time)
* `service_uids` (array of string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "outage.reopened",
"data": {
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"label": "Sydney metro fibre cut affecting MCR2-SYD1.",
"outage_uid": "9f2c1f3e-7b9d-4f6a-8c11-9e9b1234abcd",
"purpose": "Issue recurred after the initial fix; investigation continues.",
"reopened_at": "2026-04-29T18:42:00Z",
"service_uids": [
"3a8c0b2d-7f44-49ab-9a85-2bcd9e012345"
]
}
}
```
## outage.resolved
`outage.resolved` is sent when an outage has been resolved.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `company_uid` (string, UUID)
* `label` (string)
* `mitigation_actions` (string)
* `outage_uid` (string, UUID)
* `resolution` (string)
* `resolved_at` (string, date-time)
* `root_cause` (string)
* `service_uids` (array of string, UUID)
* `started_at` (string, date-time)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "outage.resolved",
"data": {
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"label": "Sydney metro fibre cut affecting MCR2-SYD1.",
"mitigation_actions": "Traffic rerouted via alternate path; affected card replaced.",
"outage_uid": "9f2c1f3e-7b9d-4f6a-8c11-9e9b1234abcd",
"resolution": "Carrier completed splice repair on the affected fibre.",
"resolved_at": "2026-04-29T16:08:00Z",
"root_cause": "Third-party fibre cut by civil works contractor.",
"service_uids": [
"3a8c0b2d-7f44-49ab-9a85-2bcd9e012345"
],
"started_at": "2026-04-29T14:21:00Z"
}
}
```
## outage.started
`outage.started` is sent when an outage event has been started.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `company_uid` (string, UUID)
* `label` (string)
* `outage_uid` (string, UUID)
* `purpose` (string)
* `service_uids` (array of string, UUID)
* `started_at` (string, date-time)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "outage.started",
"data": {
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"label": "Sydney metro fibre cut affecting MCR2-SYD1.",
"outage_uid": "9f2c1f3e-7b9d-4f6a-8c11-9e9b1234abcd",
"purpose": "Carrier outage between Sydney CBD and North Sydney.",
"service_uids": [
"3a8c0b2d-7f44-49ab-9a85-2bcd9e012345"
],
"started_at": "2026-04-29T14:21:00Z"
}
}
```
# Webhooks API Event Reference Overview
Source: https://docs.megaport.com/api/webhooks/index
This help topic describes the structure of the JSON payload for webhooks.
When you create a webhook subscription, you specify the event types for which you want to receive notifications.
When a webhook is triggered, your configured endpoint will receive an HTTP POST request with a JSON payload containing details about the event that occurred.
The structure of the JSON payload will vary depending on the event type, but it will always include these fields:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"type": "security.login.failed",
"schema_version": "1",
"timestamp": "2026-01-15T10:30:00Z",
"company_uid": "your-company-uuid",
"data": {
// event-specific fields
}
}
```
The fields in the JSON payload are described below:
| Field | Description |
| - | - |
| type | The event code identifying what happened |
| schema\_version | Payload schema version (currently "1") |
| timestamp | ISO 8601 timestamp of when the event occurred |
| company\_uid | The company UUID that the event relates to |
| data | Event-specific payload — structure varies by event type |
## Event-specific data
For more details about the event-specific fields included in the `data` object for each event type, see the following:
* [Billing Events](/api/webhooks/events/billing)
* [Maintenance Events](/api/webhooks/events/maintenance)
* [Order Events](/api/webhooks/events/order)
* [Outage Events](/api/webhooks/events/outage)
* [Payment Events](/api/webhooks/events/payment)
* [Security Events](/api/webhooks/events/security)
* [Service Events](/api/webhooks/events/service)
* [User Events](/api/webhooks/events/user)
## Managing webhooks using the API
To manage your webhooks programmatically, you can use the [Webhooks API](https://dev.megaport.com/#05a836f0-0294-4d88-bf7b-f81325845a6d) to create, update, and delete webhook subscriptions, list webhooks, and list available event types.
# Megaport Automation & AI Overview
Source: https://docs.megaport.com/automation/index
This help topic introduces the automation and AI tooling available for managing Megaport services.
This topic introduces the tools available for automating and managing Megaport services programmatically.
Megaport offers these tools:
* **[API](/api)** -- A public REST API for accessing and automating all Megaport services available through the Megaport Portal.
* **[Megaport Terraform Provider](/terraform)** -- support for automating the setup and management of your Megaport network connections, alongside your cloud resources.
* **[Megaport CLI (Beta)](/cli)** -- A command line interface for managing Megaport services.
* **[Megaport MCP Server (Open Beta)](/mcp-server)** -- A Model Context Protocol server that lets AI agents retrieve live information and execute tasks against Megaport services.
To get started, select a topic from the side navigation.
# Creating MCR Connections to Alibaba Express
Source: https://docs.megaport.com/cloud/mcr/alibaba
This help topic describes how to create private MCR connections to Alibaba Express.
The Alibaba private interconnection service is called Express Connect. Alibaba Express Connect enables customers to create private connections between their remote network environments and their Virtual Private Cloud (VPC) deployments.
When connecting to Alibaba Cloud services through Express Connect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection and Layer 3 BGP is established directly between the customer and their private environment with Alibaba Cloud VPC.
## Benefits of Alibaba Express connections with MCR
* Enhanced security and higher network performance
* Scalable connectivity options
* API integration between Megaport and Alibaba which simplifies the
provisioning of connections for a fast and seamless experience
* Connect to Alibaba Cloud on-ramp locations through any of the global
[Megaport-enabled locations](https://www.megaport.com/megaport-enabled-locations/)
* Connect with the Alibaba Cloud Enterprise Network (CEN). For more information, see
[What is Cloud Enterprise Network?](https://www.alibabacloud.com/help/doc-detail/59870.htm?spm=a2c63.p38356.b99.9.582b388dhb9eep) in the Alibaba documentation.
## Creating a VXC to the Alibaba Cloud
Before you can create a connection to the Alibaba Cloud, you need to have an Alibaba account (you can create one in the Alibaba Console). Your account number is required to create your Megaport VXC.
If you require a VXC to the Alibaba Cloud with a rate limit higher than 1 Gbps, contact your Alibaba and Megaport Account Managers to request a higher limit before proceeding. VXCs created with a higher rate limit without approval will not be deployed.
**To get your Alibaba account ID**
* Log in to the [Alibaba Cloud Console](https://account.alibabacloud.com/login/login.htm) and retrieve your account ID.\
When logged in, click your avatar icon located in the top right corner and copy your Account ID.
**To create a VXC to your Alibaba Express Connect peer location**
1. In the Megaport Portal, select the MCR to attach your VXC to and click **+Connection**.\
If you haven't already created an MCR, see [Creating an MCR](/mcr/creating-mcr).
2. Click the **Cloud** tile and click **Next**.
3. Select Alibaba Cloud as the provider.
4. Select the target destination for your connection and click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.
7. Enter an IP address with the subnet mask, for example, 192.168.100.1/30.\
Use the first available IP address to assign to the MCR. Alibaba uses the second available IP address for the BGP neighbor. This example uses 192.168.100.0/30. The first available IP address is 192.168.100.1/30, which is assigned to the MCR.\
For more information, see [Creating an MCR VXC](/mcr/mcr-vxc).
8. If the MCR has IPsec enabled, you can add IPsec tunnels.
Click **+ Add IPsec Tunnel Interface**.\
Add the IPsec tunnel details:
* **Description** -- Enter a description of the IPsec tunnel for your reference.
* **Source IP Address** -- Click the box and select the address from the drop-down list.\
This is a list of interface IP addresses defined on this VXC.
* **Destination IP Address** -- Add the destination IP address.\
The destination IP address of the tunnel must not be an IP address configured on the same MCR.
* **Pre-shared key** -- Add a key that is common to both the IKE2 (Internet Key Exchange version 2) initiator and responder. The length must be between 8 and 100 characters.
* **Local Identifier** (optional) -- Enter the identifier used for IKE authentication. This allows you to override the default source IP address with a non-IP address, which is required for some configurations. By default, the source IP address is used. Valid values include IPv4/IPv6 addresses, domain names, and email addresses (lowercase, 5-100 characters). For example, `megaport.com` or `user@example.com`.
* **Remote Identifier** (optional) -- Enter the identifier used for IKE authentication. This allows you to override the default destination IP address with a non-IP address, which is required for some configurations. By default, the destination IP address is used. Valid values include IPv4/IPv6 addresses, domain names, and email addresses (lowercase, 5-100 characters). For example, `megaport.com` or `user@example.com`.
* **Start Action** -- Select either active or passive. Passive indicates that the local MCR is an IPsec responder waiting for the remote to perform IKE2 initiation.
* **Phase 1 Lifetime** -- Enter a value between 300 and 604800 seconds. This is the lifetime of IKE2 session in seconds. The default value is 28800 seconds (8 hours). When it expires, rekeying will occur.
* **Phase 2 Lifetime** -- Enter a value between 300 and 86400 seconds. This is the lifetime in seconds of the IPsec Security Association (SA). The value must be less than the Phase 1 Lifetime. The default value is 3600 seconds (1 hour). When it expires, rekeying will occur.
9. Click **Add BGP Connection**.\
Add the local and peer IP addresses for this BGP connection. You must also add the correct autonomous system number (ASN) for the peer. The Alibaba Cloud ASN is 45104. As a best practice we recommend that you confirm the ASN when configuring the Megaport end.
10. Specify the connection details:
* **Local IP** -- Select the IP address assigned to the MCR from the drop-down list. In this example, the local IP address is 192.168.100.1/30.
* **Peer IP** -- Select the second available IP address in the /30 CIDR. In this example, the peer IP address is 192.168.100.2/30.
* **Peer ASN** -- Enter 45104, which is the peer ASN for Alibaba. The peer ASN is always 45104.
* **BGP Password** (optional) -- Specify a shared key to authenticate the BGP peer. You will need to use this key when you configure your BGP peer group in the Alibaba Console. The shared key length is from 1 to 25 characters. The key can include any of these characters:\
a-z\
A-Z\
0-9\
! @ # ? . \$ % ^ & \* + = -
Click the eye icon to see the password as you type. The view persists until you click the eye icon again to hide the password.
* **Description** (optional) -- Enter a description for the connection.
* **BGP State** -- Shuts down the connection without removing it. The initial setting will be taken from the setting on the A-End of the MCR. Enabling or shutting down the BGP state does not affect existing BGP sessions. The BGP state only affects new VXCs. This setting overrides the MCR state for an individual connection.
11. Click **Add**.\
The details for the new connection are shown:
12. Click **Next**.
13. Enter the Account ID copied from your Alibaba Console and click **Next**.
14. Review your order details and click **Add VXC**.
15. Configure more VXCs or click **Review Order**.
16. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
17. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
18. Click **Order Now**.
After you have completed the order and deployed the VXC in the Megaport Portal, you will accept the connection on the Alibaba end.
**To accept the connection in the Alibaba Console**
1. In the Alibaba Console, choose Express Connect > Physical Connections.
2. Click **Accept and Pay** next to the new physical connection (the connection that was part of your VXC order).
3. Click **OK** to accept the connection.
4. Choose the duration of the contract and verify the other connection details.
5. Click **Buy Now**.
6. Select the payment method in the top right corner and click **Pay**. The process might vary depending on the chosen payment method.
7. Verify the details and click **Purchase**.
Once your payment is complete, a confirmation screen appears. Click **Console** to return to the Alibaba Console.
At this point, the physical connection status changes to *Up*.
Next, you will connect the physical connection to a VBR (Virtual Border Router) to complete the connection with Megaport.
If you already configured a VBR, attach it to the physical connection. If you do not have a VBR, follow the steps in the next section.
**To create a VBR and BGP peer group**
1. In the Alibaba Console, click the instance name of the physical connection.
2. Click **Create VBR**.
3. Specify these VBR details:
* **Name** -- Enter a name for the VBR.
* **Physical Connection Information** -- Confirm the physical connection that this VRB will attach to.
* **VLAN ID** and **Set VBR Bandwidth Value** -- VLAN ID and speed are preconfigured based on the physical connection you selected.
* **Peer details** -- The peer details should match the MCR end of the connection from the Megaport Portal. Enter the correct IP address for the relevant peer.
4. Click **OK**.\
The new VBR appears on the Connected VBRs tab and is attached to the physical connection. The Bandwidth Status of the VBR is *Not Activated* until you configure the BGP details that correspond with those configured on the MCR.
You can also view the connection status in the MCR Looking Glass. The Megaport side of the connection will be down (red X) until BGP is configured.
5. Click the newly created VBR.
6. In the BGP Groups tab, click **Create BGP Group**.
7. Specify these details:
* **Name** (optional) -- Enter a name for the group.
* **Peer ASN** -- Enter the ASN assigned to the MCR. The MCR ASN is typically 133937, unless you choose to override the ASN when creating the BGP peer in the Megaport Portal. If you have specified a local ASN to override the default ASN, enter it here.
* **BGP Key** -- If you entered a BGP password in the Megaport Portal, enter the same password here.
* **Description** (optional) -- Enter a group description.
Once configured, your new BGP group appears in the BGP Groups list:
**To create the BGP Peer**
1. In the Alibaba Console, select the instance name of the physical connection.
2. Select the **BGP Peers** tab and click **Create BGP Peer**.
3. Select the new BGP peer group from the drop-down list (the peer group that maps to the MCR ASN).
4. Enter the MCR IP address as the BGP Peer IP (configured in step 7 of [To create a VXC to your Alibaba Express Connect peer location](#createavxc)).
Initially, when you complete the BGP Peer configuration the BGP Connection Status is *Unestablished*. It might take a few moments for the peers to start communicating. Once the BGP peers are exchanging data, the BGP status in the Alibaba Console changes to *Established*. In the MCR Looking Glass in the Megaport Portal, the BGP status changes to a green checkmark.
For more information about setting up BGP groups and peers, see
[Configure BGP](https://www.alibabacloud.com/help/doc-detail/91267.html?spm=a2c5t.11065259.1996646101.searchclickresult.406ffb19k3apkJ) in the Alibaba Document Center.
## Additional notes when setting up BGP
* You can only specify the data center as the BGP peer of a VBR.
* VBRs support only BGP-4.
* You can create a maximum of eight BGP peers for each VBR.
* Each BGP peer supports at most 110 dynamic routes.
* Bidirectional Forwarding Detection (BFD) is disabled for VBRs by default. To enable BFD, submit a ticket to Alibaba.
## Using a service key
You can create a service key that allows you to share your service with another Megaport account holder.
For more information, see [Setting up Service Keys](/marketplace/service-keys/).
# Creating MCR Connections to DigitalOcean Infrastructure
Source: https://docs.megaport.com/cloud/mcr/digitalocean
This help topic describes how to create connections between MCR and DigitalOcean Infrastructure.
Megaport makes it easy to provision fast, secure, and private connections to DigitalOcean through our global software-defined network (SDN). As a DigitalOcean partner, Megaport provides customers with direct, private access to global DigitalOcean infrastructure via pre-provisioned on-ramps.
DigitalOcean Partner Network Connect lets you establish high-bandwidth, low-latency network connections directly between DigitalOcean Virtual Private Cloud (VPC) networks and other public cloud providers or data centers.
DigitalOcean Partner Network Connect allows you to create partner interconnect attachments, which connect one or more DigitalOcean VPC networks to Megaport. After connecting your DigitalOcean VPC to Megaport, you can connect Megaport to other cloud providers or data center networks.
Establishing multi-hybrid cloud connectivity with DigitalOcean involves three connections. You must create a Partner Network Connect in DigitalOcean, a Megaport Cloud Router (MCR) with two Virtual Cross Connects (VXCs) – one for each end of the connection – on Megaport, and a direct connect link on AWS, GCP, or other providers or data centers.
## Availability
DigitalOcean Partner Network Connect is available in the locations listed below. Customers can access all DigitalOcean data centers in the regions where Partner Network Connect is enabled, such as San Francisco, New York, Amsterdam, Frankfurt, and Singapore.
* DigitalRealty New York JFK10
* Equinix San Jose SV1/10
* Interxion Frankfurt FRA15
* Interxion Amsterdam AMS9/17
* Equinix Singapore SG3
## Prerequisites
Before setting up a DigitalOcean Partner Network Connect, you need:
* **A Megaport account** -- If you have not already created one, see [Creating an Account](/setting-up/registering).
* **An MCR** -- Preferably close to where VXC connections will be made. For more information, see [Creating an MCR](/mcr/creating-mcr).
* **A service key** -- A code that is given to you by DigitalOcean to create a connection from a Megaport MCR to a DigitalOcean service. For more information, see the DigitalOcean documentation at [How to Create a Partner Attachment](https://docs.digitalocean.com/products/networking/vpc/how-to/create-partner-attachment/).
* **Network details** -- For the target resources on the other side of the network, in Classless Inter-Domain Routing (CIDR) notation.
## Creating a DigitalOcean connection
To create a connection from a Megaport MCR to a DigitalOcean service, you need a service key. DigitalOcean generates a service key on request. To create your unique DigitalOcean Partner Network Connect service key, follow the steps provided by DigitalOcean in the DigitalOcean documentation at [How to Create a Partner Attachment](https://docs.digitalocean.com/products/networking/vpc/how-to/create-partner-attachment/).
**How to order**
1. Existing DigitalOcean customers must contact their DigitalOcean Account Manager or pre-sales architect to establish a connection. New customers can contact DigitalOcean through their website to discuss options.
2. DigitalOcean will provide a service key. This key will be unique to your business and will include DigitalOcean’s VLAN ID, speed, and cloud peering location.
3. Create a connection to DigitalOcean in the Megaport Portal using the service key. Data including VLAN ID, speed, and DigitalOcean peering location will populate automatically from the data supplied by the service key.
## Creating a VXC to DigitalOcean
After you receive your service key from DigitalOcean, create your connection to DigitalOcean in the Megaport Portal. These instructions will help you create the connection.
**To create a connection to DigitalOcean**
1. Make sure you have your DigitalOcean service key.
When you use the service key created by DigitalOcean, you are responsible for any VXC charges.
2. In the Megaport Portal, go to the **Services** page.
3. Select the MCR you want to use. If you have not already created an MCR, see [Creating an MCR](/mcr/creating-mcr).
4. Add a DigitalOcean connection for the MCR. If this is the first connection for the MCR, click the **DigitalOcean** tile.\
The tile is a shortcut to the configuration page.\
Alternatively, click **+Connection**, click **Cloud**, then click **DigitalOcean**.
5. Enter the service key provided by DigitalOcean in the Megaport Service Key ID field.
6. Click **Next**.
7. Specify the MCR connection details.
* **Connection Name** – The name of your VXC to be shown in the Megaport Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** – The speed of your connection in Mbps. The speed tiers available are dependent on the selected location, and match the speeds available in DigitalOcean. Select the MCR speed from the drop-down list to match the selected speed in the DigitalOcean portal for the VPC service.
* **VXC State** – Select Enabled or Shut Down to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
8. Click **Next**.
9. Specify the MCR A-End connection details.\
Set the following fields using information from your DigitalOcean partner attachment:
* **Interface IP Address** -- Set the Interface IP Address to the partner attachment's Peer router IP.
* **BGP Connection** -- Click **Add BGP Connection**.\
For Local IP, select the Interface IP Address.\
Retrieve the partner attachment's BGP details from DigitalOcean, and enter them into the fields.
The Local router IP from DigitalOcean is the Peer IP for Megaport.
Use the BGP authentication key for the BGP Password.\
Click **Add** to save your BGP Connection.
For more information about these fields, see [Configuring an MCR](/mcr/configuring-mcr).
10. Click **Next**.\
A summary page appears that includes the monthly cost.
11. Click **Back** to make changes or click **Add VXC**.
12. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
13. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
14. Click **Order Now**.
Once you have finished this configuration, you can configure additional VXCs.
## Helpful references
* [DigitalOcean Create a Partner Attachment](https://docs.digitalocean.com/products/networking/vpc/how-to/create-partner-attachment/)
* [Configuring an MCR](/mcr/configuring-mcr)
* [MCR Pricing and Contract Terms](/finance/mcr-pricing)
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Creating MCR Connections to Google Cloud Services
Source: https://docs.megaport.com/cloud/mcr/google
This help topic describes how to provision connections between MCR and Google Cloud Services.
Megaport makes it easy to provision fast, secure, and private connections between a customer's data center and Google Cloud Platform.
## Partner Interconnect
Partner Interconnect accesses the private address space ([RFC 1918](https://tools.ietf.org/html/rfc1918)).
As part of the Google Cloud Interconnect (GCI) Partner program, Megaport provides users with dedicated access to Google Cloud Platform (GCP) and enables customers to create private connections between their remote network environments and their Virtual Private Cloud (VPC) deployments.
The benefits of creating GCI Partner Connections with Megaport include:
* Enhanced security and higher network performance
* Connectivity reach beyond Google's existing network locations
* Scalable connectivity for those who do not require the full bandwidth of Google's Dedicated Interconnect
* Savings on egress traffic costs from the customer's VPC network to their on-premises network
* API integration between Megaport and Google Cloud which simplifies the provisioning of connections for a fast and seamless experience
* Layer 3 routing capabilities without having a physical router located in a data center
When connecting to Google Cloud Platform (GCP) through Partner Interconnect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection and Layer 3 BGP is established directly between the customer and GCP. Through Partner Interconnect, a customer can access VMs (Virtual Machines) built within a VPC.
### Creating a VXC to the Google Cloud Platform
Before you begin, create a Megaport Cloud Router (MCR). If you don’t have an MCR, create one following the procedures in [Creating an MCR](/mcr/creating-mcr).
**To deploy a VXC to Google Cloud Platform**
1. Log in to your Google Cloud
Console and create a pairing key.
2. From the main menu in the Console, select Hybrid Connectivity > Interconnect.
3. Click **Get Started**.
4. Select Partner Interconnect then click **Continue**.
5. Click **I already have a service provider**.
6. Configure your attachment. Provide these attachment details:
* **Redundancy** -- Select a redundancy option. You can create redundant attachments or a single attachment. For more information about redundancy, see [Diversity in Google Connections](/cloud/megaport/google/google-diversity).
* **Network** -- Select the VPC network you want the VPC to connect.
* **Region** -- Select the region where your attachment will connect.
* **Cloud Router** -- Select a Cloud Router to associate with this attachment.
You can only select a Cloud Router in the VPC network and region that you selected with an ASN of 16550. If you don't have an existing Cloud Router, create one with an ASN of 16550. For redundancy, each VLAN attachment must be associated with a unique Cloud Router. Google automatically adds an interface and a BGP
peer on the Cloud Router.
The Google ASN will always be 16550.
* **VLAN attachment name** -- Enter the VLAN attachment name using lowercase letters only.
* **Description** (optional) -- Enter a description for the attachment.
* **Maximum Transmission Unit (MTU)** -- Set the MTU to match the MTU of your VPC network. The default VPC network MTU is 1460 bytes.
7. Click **Create**.\
A pairing key appears.
8. Copy the pairing key then click **OK**.
9. In the Megaport Portal, create a VXC to your Google peering location:\
Click **+Connection** on the MCR.
10. Click the **Cloud** tile.
11. Select Google as the provider.
To check the latency and price of connecting to a particular Google location, click **View all Google Partner locations**. You can proceed to the Connection Details page without a pairing key and review the pricing of the selected port. To place an order for a Google connection, you need to provide a pairing key.
12. Copy and paste the pairing key from the Google Cloud console into the Google Partner Pairing Key field.\
The relevant Google targets appear based on the region of your GCI Partner connection.
13. Select the target location for your first connection then click **Next**.
14. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- Enter the same rate you selected for your Google port speed.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
15. Click **Next**.
16. Review the Summary then click **Next**.
17. Click **Add VXC** and configure further VXCs or proceed through the ordering process.
18. To deploy a second connection (recommended), repeat these steps and select “Add a redundant VLAN to an existing VLAN” in step 6. Adding a second connection ensures that you receive [redundancy and an SLA from Google](https://cloud.google.com/network-connectivity/docs/interconnect/concepts/partner-overview#redundancy).
19. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
20. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
21. Click **Order Now**.
After placing the order, wait a few minutes until the VXC status changes from red to green. Green indicates Layer 2 connectivity has been established.
This completes your Layer 2 VXC deployment.
After the VXC is established in the Megaport Portal, you need to accept the attachment in the Google Cloud Console and configure BGP. Google provides you with a private IP address to configure BGP.
For more information, see the Google documentation on [Google Partner Interconnects](https://cloud.google.com/interconnect/docs/how-to/partner/provisioning-overview).
**To activate and accept the connection**
1. In Google Console, return to the attachment you just created. The attachment status should be *Activation needed*. If the status shows *Pending partner*, refresh your screen or wait a couple of minutes until it changes to *Activation needed*.
2. Click **Activate**.\
Google asks you to accept the connection.
3. Click **Accept** and wait about a minute.\
The status updates to *BGP configuration needed*.
**To configure BGP**
1. In Google Console, click **Configure BGP**.
2. By default, the ASN assigned to the MCR is 133937. Leave the default peer ASN or enter a private ASN.
3. Click **Save and Continue**.
Wait a few minutes for the BGP peer to establish and then verify the BGP configuration.
**To verify the BGP configuration**
1. In the Megaport Portal, select the VXC.
2. Select the **Logs** tab.\
The VXC status should be *BGP Established*.
3. In the Google Cloud Console, view the VLAN attachment.\
The status should be *BGP Up*.
For more information, see the Google documentation at [Viewing Router Status and Advertised Routes](https://cloud.google.com/router/docs/how-to/viewing-router-details).
## Using a service key
You can create a service key that allows you to share your service with another Megaport account holder.
For more information, see [Setting up Service Keys](/marketplace/service-keys/).
# Creating MCR Connections to IBM Cloud Direct Link
Source: https://docs.megaport.com/cloud/mcr/ibm-2.0
This help topic describes how to create connections between MCR and IBM Cloud Direct Link.
IBM Direct Link lets you seamlessly create private connections between your on-premises and cloud resources. Direct Link Connect with Megaport extends your organization's data center network and to public clouds to offer better performance, higher throughput, and security to IBM Cloud environments.
When connecting to IBM through a Direct Link Connect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection. Layer 3 BGP connectivity is established directly between the customer and IBM Cloud.
This topic describes how to connect to IBM Direct Link from an MCR. For more information about connecting from a Port, see [Connecting to IBM Cloud Direct Link](/cloud/megaport/ibm/direct-link-2.0).
If you edit an older VXC to IBM Cloud Direct Link in the Megaport Portal, a prompt appears stating that Megaport has updated API integrations, and advises you to cancel and reorder the VXC. In this situation, we recommend that you cancel and then reorder the VXC using the latest API integration.
## Benefits of IBM Direct Link through Megaport
The benefits of creating an IBM Direct Link through Megaport include:
* Reduced latency and increased availability
* Reduced data egress cost
* Secure connectivity
## Creating a connection to IBM Direct Link
To set up IBM Direct Link with Megaport, you need to create a VXC from your MCR in the Megaport Portal to the IBM Direct Link cloud location.
Design considerations when setting up your Direct Link to IBM Cloud:
* **Redundancy** -- Megaport supports redundant connections. In each of the Direct Link peering locations, Megaport has established two diverse Direct Links with IBM Cloud. In the Megaport Portal, the Ports are noted as Port 1 and Port 2. A redundant configuration requires two or more VXCs.
* **Local and Global routing options** -- The Local Routing option provides access to data centers with the same three-letter prefix as the Point of Presence (such as DAL, AMS, and MEL). The Global Routing option is required as an add-on to reach data centers outside of those locations. For more information about local and global routing options, see the [IBM cloud documentation](https://cloud.ibm.com/docs/direct-link).
* **Port speed** -- Port speed options for IBM Direct Link Connect are 50 Mbps, 100 Mbps, 200 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, or 5 Gbps. Higher speeds might be available depending on region and IBM capabilities. For pricing details from IBM, see [Pricing for IBM Cloud Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-faqs).
* Megaport-enabled Direct Link locations:
* North America: Ashburn, Chicago, Dallas, San Jose
* Europe: Amsterdam, Frankfurt, London, Paris
* Australia: Sydney
* Asia: Osaka, Tokyo
**To create a VXC to the IBM Direct Link Connect**
1. In the Megaport Portal, go to the **Services** page and select the MCR you want to use.\
If you haven't already created an MCR, see [Creating an MCR](/mcr/creating-mcr).
2. Add an IBM Cloud connection for the MCR.\
If this is the first connection for the MCR, click the IBM Cloud tile. The tile is a shortcut to the configuration page. Alternatively, click **+Connection**, click **Cloud**, then click **IBM Cloud**.
3. Select the IBM Direct Link location where the peer will be set up with IBM Cloud and click **Next**.\
This destination should match the peer location selected in the IBM Cloud.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The speed tiers available are dependent on the selected location, and match the speeds available in IBM. Select the port speed from the drop-down list to match the selected speed in the IBM Cloud portal for the Direct Link service.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.\
The MCR A-End page appears. This page confirms that the MCR connection configuration will be generated automatically, and can be modified later.
1. Click **Next**.\
The Cloud Details page appears.
2. Specify these IBM cloud details:
* **IBM Account ID** -- Your IBM account ID. You can get your account ID from the IBM account setting in the IBM Cloud portal.\
This is used to link the Megaport Portal and IBM Cloud portal. Confirmation for this new connection will be sent to the specified account ID in the IBM Cloud portal.
* **Customer IP Address** (optional) -- The IP address space (in CIDR format) you will use on your network for peering. For private connections, this field is optional and if left blank, Megaport assigns a private /30 address. For public connections, this field is required and needs public IPs (/30) allocated by you for BGP connectivity. You must own the public IPs.
* **Provider IP Address** (optional) -- The IP address space in CIDR format assigned in the IBM network for peering. If left blank, Megaport automatically assigns a private /30 address.
3. Click **Next**.\
A summary page appears with drop-downs containing the MCR A-End and IBM cloud details, and the monthly cost.
4. Click **Back** to make changes or click **Add VXC**.\
Once you have finished this configuration, you can configure additional VXCs or complete the order.
5. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
6. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
7. Click **Order Now**.
The IBM Portal Connection prompt displays. This is a reminder that you need to approve or reject the request in the IBM Cloud portal, and provides a link to the IBM Cloud portal.
Once the VXC is created and ordered in the Megaport Portal, the change is available immediately in the IBM Cloud portal. After you verify and approve the inbound IBM VXC in the IBM Cloud portal, the IBM Direct Link Connect status changes to Provisioned and the Megaport VXC is active.
* When editing a VXC in the Megaport Portal, a prompt listing the changes appears first, then the IBM Portal Connection prompt. If editing an older VXC to IBM Cloud Direct Link, a prompt appears stating that Megaport has updated API integrations, and advises you to cancel and reorder the VXC. In this situation, we recommend that you cancel and then reorder the VXC using the latest API integration.
* When terminating a VXC in the Megaport Portal, confirm the termination in the prompt that appears. The IBM Portal Connection prompt appears to remind you to cancel the service in the IBM Cloud portal also. The VXC is terminated on the Megaport side, but you must do the same in the IBM Cloud portal to fully terminate the service.
**To verify the BGP configuration**
1. In the Megaport Portal, select the VXC.
2. Click the gear icon next to the VXC.
3. On the Connection Details page, click **Details**.\
The Configuration Details page appears.
The Service Status indicator displayed in green means that the service is active.
4. Click **Logs**.\
The Service Log page appears.
A green check mark indicates that the BGP session is working as expected.
## Using a service key
You can create a service key that allows you to share your service with another Megaport account holder.
For more information, see [Setting up Service Keys](/marketplace/service-keys/).
## Helpful references
* [Models for diversity and redundancy in Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-models-for-diversity-and-redundancy-in-direct-link#:~:text=IBM%20Cloud%C2%AE%20Direct%20Link,gateway%20protocol%20\(BGP\)%20schemas)
# Creating MCR Connections to Latitude.sh
Source: https://docs.megaport.com/cloud/mcr/latitude-sh
This help topic describes how to create a connection between a Megaport Cloud Router and Latitude.sh.
BGP is required for all Latitude.sh connections. To create a connection, specify an ASN, BGP password, and the prefixes to advertise. The connection becomes live after Latitude.sh approves the request.
## Prerequisites
## Creating a connection to Latitude.sh
To set up a connection to Latitude.sh with Megaport, you need to create a VXC from your MCR in the Megaport Portal to the Latitude.sh location where you have provisioned your Latitude.sh services.
**To create a connection to Latitude.sh**
1. In the Megaport Portal, go to the **Services** page.
2. Select the MCR you want to use.\
If you haven't created an MCR, see [Creating an MCR](/mcr/creating-mcr).
3. Click **+Connection**, click **Cloud**, then click **Compute via Latitude.sh**.
4. Select the target location for your connection then click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc/).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.
7. Review and configure the MCR A-End connection details.\
For more information about these fields, see [Configuring an MCR](/mcr/configuring-mcr/#editing-a-vxc).
8. Click **Next**.\
A summary page appears that includes the monthly cost.
9. Click **Back** to make changes, or click **Add VXC**.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
The connection becomes live after Latitude.sh approves the request.
After ordering, the connection status shows *Deployable* until it is provisioned. When Latitude.sh approves the connection and provisioning is complete, the status updates to *Configured*.
## Helpful references
* [Connecting to Latitude.sh](/portal-admin/connect-latitude)
* [Connecting to Latitude.sh with Megaport](/cloud/megaport/latitude-sh)
* [Creating an MCR](/mcr/creating-mcr)
* Latitude.sh docs
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Creating MCR Connections to Oracle Cloud Infrastructure
Source: https://docs.megaport.com/cloud/mcr/oracle
This help topic describes how to create connections between MCR and Oracle Cloud Infrastructure - FastConnect.
The Oracle Cloud Infrastructure (OCI) private connection model is called FastConnect. FastConnect provides private connectivity and self-service provisioning, including full API-level integration.
When connecting to the Oracle Cloud Infrastructure (OCI) through FastConnect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection. Layer 3 BGP connectivity is
established directly between you and Oracle.
A common FastConnect deployment might look like this:
This topic describes the basic steps needed to establish a FastConnect connection:
* Create the FastConnect in the Oracle console with Megaport as the provider.
* Provision the VXC in the Megaport Portal to connect to your FastConnect location.
Oracle offers a service level agreement (SLA) for its FastConnect connectivity, as long as you configure two FastConnect VXCs for redundancy.
You can deploy a Megaport MCR using the OCI console without having to switch between the Oracle and Megaport Portals. For more information, see [FastConnect integration with Megaport Cloud Router](https://blogs.oracle.com/cloud-infrastructure/post/fastconnect-integration-megaport-cloud-router).
## Creating the FastConnect
The first task before you connect an MCR to your target Oracle Virtual Cloud Network (VCN) is to create a FastConnect in the Oracle console.
**To create FastConnect in the OCI console**
1. Log in to the OCI console and select the region from the
upper-right corner.
2. Create a compartment or select an existing compartment to deploy
these new resources.
Compartments help you organize resources to make it easier to control access to them. Your root compartment is created for you by Oracle when your tenancy is provisioned. An administrator can create more compartments in the root compartment and then add the access rules to control which users can take action in them.
3. Select Networking > Virtual Cloud Networks.
4. Create your VCN, which is a customizable and private network in OCI.
5. If you plan to use a private virtual circuit (private peering) to advertise private IPv4 addresses such as [RFC 1918](https://tools.ietf.org/html/rfc1918), you need to create a Dynamic Routing Gateway (DRG).
A DRG is a virtual edge router attached to your VCN that provides a single point of entry for private traffic coming into your Virtual Cloud Network (VCN). Use the OCI console to set up a DRG and attach it to your VCN. A DRG can be attached to only one VCN at a time. Next, you need to update routing in your VCN to include a route rule to send traffic to the DRG. It's easy to forget to update the route table but without the route rule, no traffic will flow.
6. Create the FastConnect.
When you create the FastConnect in the Oracle Console, Oracle provides you with an Oracle-assigned unique ID called an Oracle Cloud Identifier (OCID).
7. Click the FastConnect to view its details.
8. Copy the OCID.
9. Confirm the autonomous system number (ASN).
10. Log in to the Megaport Portal.
## Creating a VXC to FastConnect
With an MCR configured, VXCs are needed to connect to services on the Megaport network. A VXC is essentially a private point-to-point Ethernet connection between an A-End (your MCR) and a B-End (a port location based on the FastConnect region).
**To create the VXC to FastConnect**
1. In the Megaport Portal, go to the **Services** page and select the MCR you want to use.\
If you haven't already created an MCR, see
[Creating an MCR](/mcr/creating-mcr).
2. Add a VXC for the MCR.\
If this is the first connection for the MCR, click the Oracle Cloud tile.
The tile is a shortcut to the Oracle Configuration page. Alternatively,
click **+Connection**, click **Cloud**, then click **Oracle Cloud**.
To check the latency and price of connecting to a particular Oracle location, click **View all Oracle Partner locations**. You can proceed to the Connection Details page without a service key and review the pricing of the selected port. To place an order for an Oracle connection, you need to provide a service key.
1. Enter the OCID you copied from the Oracle Console.\
The Megaport Portal verifies the OCID and displays the available port locations based on the FastConnect region. For example, if your FastConnect service is deployed in Ashburn, you only see the Ashburn FastConnect targets.
2. Select a target location for your first connection and click **Next**.
1. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Enter the same rate or up to the rate you specified in the Oracle Console.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
2. Click **Next**.
3. Enter the IP address and mask for the MCR interface facing Oracle.\
This IP address matches the address you entered in the Oracle Console to create the FastConnect.
4. Click **Add BGP Connection**.
5. Specify the connection details:
* **Local IP** -- Select the IP address assigned to the MCR from the drop-down list. In this example, the local IP address is 192.168.100.1/30.
* **Peer IP** -- Specify the second available IP address in the /30 CIDR. In this example, the peer IP address is 192.168.100.2/30.
* **Peer ASN** -- Enter 31898, which is the peer ASN for FastConnect. The peer ASN is always 31898.
* **BGP Password** (optional) -- Specify a shared key to authenticate the BGP peer. The shared key length is from 1 to 32 characters. This is not a mandatory field for Oracle connections because they traverse a private path.
* **BGP State** -- Shuts down the connection without removing it. The initial setting will be taken from the setting on the A-End of the MCR. Enabling or shutting down the BGP state does not affect existing BGP sessions. The BGP state only affects new VXCs. This setting overrides the MCR state for an individual connection.
6. Click **Add**.
7. Click **Next**.\
A summary page appears that includes the monthly cost.
8. Click **Back** to make changes or click **Add VXC**.\
Once you have finished this configuration, you can configure additional VXCs or complete the order.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
## Viewing the VXC status
You can check the VXC status in the Megaport Portal Service page.
**To view the VXC connection details**
1. Click the VXC name.
2. View the service status from the **Details** tab.\
In this example, both Service Status (Layer 2) and BGP IP Address (Layer 3) are green, indicating that the services are up.
3. Return to the Oracle Console to view the FastConnect status.
## Using a service key
You can create a service key that allows you to share your service with another Megaport account holder.
For more information, see [Setting up Service Keys](/marketplace/service-keys/).
## Next steps
* Oracle offers an SLA on its FastConnect connectivity. To comply with the SLA, you need to deploy two FastConnect VXCs for redundancy. You must set up both BGP sessions on separate VXCs. You can configure the VXCs on a single MCR or across two MCR instances, depending on your HA requirements.
* To establish a separate BGP session, create a FastConnect on the Oracle Console and repeat the steps in the Megaport Portal.
# Creating MCR Connections to 3DS Outscale
Source: https://docs.megaport.com/cloud/mcr/outscale
This help topic describes how to create connections between a Megaport Cloud Router and 3DS Outscale.
Megaport makes it easy to provision fast, secure, and private connections to 3DS Outscale Connect through our global software-defined network (SDN). Megaport is a 3DS Outscale partner providing direct private access to the 3DS Outscale infrastructure. You can quickly provision connectivity from hundreds of Megaport-enabled locations to 3DS Outscale Connect regions and 3DS Outscale Connect Points-of-Presence (PoPs) across North America, Europe, and Asia Pacific.
The benefits of direct connectivity to 3DS Outscale Connect through Megaport include:
* Secure, private connectivity throughout Megaport's redundant network infrastructure. Your traffic will not transit the public internet.
* High performance and predictability of your network.
* Improved data and operational security.
* Flexible and scalable cloud networking options.
* Consistent connectivity while scaling bandwidth to 3DS Outscale Connect. This means no downtime when you need to change your Virtual Cross Connect (VXC) speed.
* Connect to multiple regions from a single interconnection point, which uses multi-region redundancy at a fraction of the cost.
## How it works
3DS Outscale Connect consists of a physical network connection at several 3DS Outscale locations. 3DS Outscale locations reside within facilities operated by co-located data centers where Megaport is enabled.
Physical fiber connections (NNIs) at each location between Megaport and 3DS Outscale are established to 3DS Outscale routers. These physical connections are maintained between 3DS Outscale and Megaport. Connecting to 3DS Outscale follows these general steps through the Megaport Portal:
1. Order Megaport Cloud Routers (MCRs) in Megaport locations of your choice. Two MCRs are required for redundancy.
2. Order VXCs to 3DS Outscale. Bandwidth is available in 1 Mbps increments up to several Gbps. Maximum bandwidth depends on the selected region and service configuration.
3. VXCs to 3DS Outscale are established as a Layer 2 service between 3DS Outscale and the MCR. One VXC from each MCR is required for resilience.
4. After you deploy VXCs in the Megaport Portal, establish Layer 3 BGP peering between your routing equipment and 3DS Outscale.
DirectLink connects private 3DS Outscale cloud services to Megaport. Each VXC (DirectLink) lets you manage the bandwidth and as long as the total bandwidth of the VXCs does not exceed the size of the MCR, utilization of each VXC (to the VPC) will not affect the other VPCs.
You can create a VXC from an MCR to 3DS Outscale Connect from the Megaport Portal. You can also create additional VXCs to other Cloud Service Providers (CSPs) for multicloud access from the MCR. Click the appropriate CSP link in the [MCR Cloud Connectivity Overview](/cloud/mcr) navigation.
Key features include:
* Connections can share bandwidth, which is managed and monitored to ensure defined network performance.
* If you connect to 3DS Outscale from an MCR, the DirectLink provides access to the routing information for automatic configuration of your MCR.
* You can change the service speed without any affect to the service.
* 3DS Outscale port charges are included with your Megaport order. Billing details and Megaport rates are shown as you configure the connection.
## Availability
3DS Outscale Connect is available in this location:
* Europe
* Paris (eu-west-2)
For more information about 3DS Outscale locations, see [3DS Outscale Connect](https://docs.outscale.com/en/userguide/Regions-Endpoints-and-Availability-Zones-Reference.html).
## Prerequisites
Before you create a private connection to 3DS Outscale, make sure you have:
* Your [3DS Outscale account number](https://docs.outscale.com/en/userguide/Account.html).
* Requested that 3DS Outscale remove your DirectLink quota limit.
* [OSC CLI](https://docs.outscale.com/en/userguide/Installing-and-Configuring-OSC-CLI.html) installed. OSC CLI is required to confirm the DirectLink connection requests.
* A 3DS Outscale [virtual private gateway](https://docs.outscale.com/en/userguide/Managing-Your-Virtual-Private-Gateways.html) associated with your VPCs.
* The ASN for the 3DS Outscale gateway: 50624
* An MCR. If you don't currently have an MCR, create one following the procedure in [Creating an MCR](/mcr/creating-mcr).
## Connecting an MCR to 3DS Outscale
A DirectLink can connect to private 3DS Outscale cloud services. Before you deploy a 3DS Outscale DirectLink, ensure that you meet all the prerequisites above.
Currently, you can have only one VIF per Virtual Gateway (VGW)/DirectLink connection.
**To create a DirectLink VXC from an MCR to 3DS Outscale**
1. In the Megaport Portal, go to the **Services** page and select the MCR you want to use.\
If you don't have a Megaport account, see [Setting Up a Megaport Account](/setting-up). If this is your first time, you will need to register for an account.
2. Click **+Connection** and click **Cloud**.
3. Select 3DS Outscale as the service provider, select the destination port, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
Match this to the VXC name on the next screen for easy mapping.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Accepted values range from 1 Mbps and can scale to several Gbps, in 1 Mbps increments. The maximum available speed depends on the selected region and service configuration.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next** to acknowledge the MCR Connection details.
6. Click **Next**.
7. Specify the cloud details:
* **Outscale Connection Name** (optional) -- Specify a name for your virtual interface (VIF) that will appear in the 3DS Outscale console (Cockpit/OSC CLI). For easy mapping, use the same name for this field as you did for the VXC name on the previous page.
* **Outscale Account ID** -- This is the ID of the account you want to connect. You can find this value in the management section of your 3DS Outscale console (Cockpit/OSC CLI).
* **Customer ASN** -- Your network’s autonomous system number (ASN). The MCR ASN is applied automatically.
* **BGP Auth Key** (optional) -- Specify the BGP key using alphanumeric characters only. If you leave this blank, Megaport negotiates a key automatically for you with 3DS Outscale which is displayed in the Megaport Portal. The key is also displayed in the OSC CLI API call, but not in the 3DS Outscale Cockpit console.
The BGP Auth Key is generated during the ordering process when this field is left blank. It will not be displayed on the Summary page when ordering. To see the key, view the Connection Settings after the service has been deployed and is live.
* **Customer IP Address** -- The IP Address space (in CIDR format) you will use on your network for peering. For private connections, this field is optional and if left blank, Megaport assigns a private /30 address. For public connections, this field is required and needs public IPs (/30) allocated by you for BGP connectivity. You must own the public IPs.
* **Outscale IP Address** (optional) -- The IP address space in CIDR format assigned in the 3DS Outscale VPC network for peering. If left blank, Megaport automatically assigns a private /30 address.
8. Click **Next**.\
A summary page appears that includes the monthly cost. Click **Back** to make changes or click **Add VXC** to move this configuration to your cart. Once you have finished this configuration, you can configure additional VXCs or proceed through the checkout process.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Megaport will deploy the connection. The deployment can take several minutes.
## Accepting the virtual interface connection
Once you have deployed the VXC, you will accept the virtual interface in 3DS Outscale using the OSC CLI (API calls).
Currently, you cannot accept virtual interface connection requests in 3DS Outscale Cockpit v1. This is only possible through the API.
For more information about the next procedure, see the [3DS Outscale documentation](https://docs.outscale.com/en/userguide/Accepting-a-Hosted-Private-Virtual-Interface.html).
**To review and accept the virtual interface connection**
1. Go to the OSC CLI.
2. Enter this command to show the DirectLink request:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
%osc-cli directlink DescribeVirtualInterfaces --profile "default"
{
"virtualInterfaces": [
{
"virtualInterfaceState": "confirming",
"authKey": "eu4dq8ieBSZJSiOSlHNw",
"asn": 133937,
"vlan": 3977,
"bgpPeers": null,
"customerAddress": "192.168.2.2/29",
"ownerAccount": "XXXXXXXXXXXX",
"connectionId": "dxcon-a7c2eb08",
"addressFamily": null,
"virtualGatewayId": "null",
"virtualInterfaceId": "dxvif-4ae2a10f",
"amazonSideAsn": null,
"routeFilterPrefixes": null,
"location": "PAR4",
"directConnectGatewayId": null,
"customerRouterConfig": null,
"amazonAddress": "192.168.2.1/29",
"virtualInterfaceType": "private",
"virtualInterfaceName": "Direct Link VXC eu-west-2"
}
],
"requestid": "5ad8af40-c0af-4deb-85db-7a8ae5481d18"
}
```
Next, you will ensure that you have a Virtual Private Gateway (VGW) to connect your VIF to.
3. In Cockpit, choose VPC menu > Virtual Private Gateways.
If no VGW is available, see the [3DS Outscale documentation](https://docs.outscale.com/en/userguide/Creating-a-Virtual-Private-Gateway.html) to learn how to create one in Cockpit or the OSC CLI.
4. To accept the VIF creation request, take note of the `virtualInterfaceId` from step 2 and the `virtualGatewayID` from step 3 and enter this command:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
% osc-cli directlink ConfirmPrivateVirtualInterface --profile "default" \
--virtualGatewayId "vgw-76e8160d" \
--virtualInterfaceId "dxvif-4ae2a10f"
{
"virtualInterfaceState": "pending",
"requestid": "9b66a7e8-a02a-45ba-9a21-c01058273190"
}
```
Next, you will verify that the status is now *available* for the VIF.
5. Click the DirectLink name in the Virtual Interfaces screen.
6. Verify the VIF status in the Details screen.
You can also verify the status through the API:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
%osc-cli directlink DescribeVirtualInterfaces --profile "default"
{
"virtualInterfaces": [
{
"virtualInterfaceState": "available",
"authKey": "eu4dq8ieBSZJSiOSlHNw",
"asn": 133937,
"vlan": 3977,
"bgpPeers": null,
"customerAddress": "192.168.2.2/29",
"ownerAccount": "XXXXXXXXXXXX",
"connectionId": "dxcon-a7c2eb08",
"addressFamily": null,
"virtualGatewayId": "vgw-76e8160d",
"virtualInterfaceId": "dxvif-4ae2a10f",
"amazonSideAsn": null,
"routeFilterPrefixes": null,
"location": "PAR4",
"directConnectGatewayId": null,
"customerRouterConfig": null,
"amazonAddress": "192.168.2.1/29",
"virtualInterfaceType": "private",
"virtualInterfaceName": "Direct Link VXC eu-west-2"
}
]
}
```
After you create the VIF, you must accept it within 7 days.
Once you accept the virtual connection in the OSC CLI, the VXC state changes to *Configured* in the Megaport Portal and appears on the Portal Services page associated with the MCR.
To view the details of this connection, click the VXC name. You can review the configuration details to get the A-End VLAN ID, BGP Auth Key, IP addresses and the BGP peering status:
**To edit a VXC**
* Click the gear icon next to the connection in the Megaport Portal to make changes.
If you have the required permissions to edit VXCs, you can modify the details on the Megaport side including the connection name, VLAN ID, service level reference, and rate limit. Once submitted, those changes take effect in a few minutes.\
For more information, see [Configuring an MCR](/mcr/configuring-mcr).
**To delete a VXC**
* Click the trash icon next to the connection in the Megaport Portal.
For more information, see [Terminating a VXC](/connections/terminating-vxc).
## Redundancy
To establish full redundancy between your MCR and 3DS Outscale, we recommend deploying redundant VXCs between two different 3DS Outscale locations with two corresponding Ports at each Megaport-enabled data center.
### Redundant solution
### Fully redundant solution
### Setting up a redundant 3DS Outscale DirectLink
To set up a redundancy to access 3DS Outscale, create a DirectLink and then repeat the procedure to create a second DirectLink. Ensure that your VXCs are set up on separate DirectLink interconnection ports.
With two VIFs configured on two different DirectLink interconnections, you can then connect both VIFs to the same VGW.
Redundancy is not possible if the VIFs are set up on the same DirectLink interconnection.
## Updating the service bandwidth
You can scale the service speed up to the 3DS Outscale Connect speed rate at any time. To change the 3DS Outscale Connect speed, edit the VXC and change the speed.
## 3DS Outscale Frequently Asked Questions (FAQs)
### Are there any 3DS Outscale port fees?
3DS Outscale doesn't charge for ingress or egress data transfer.
### What services are available using 3DS Outscale?
3DS Outscale offers private cloud with computing power, storage solutions, network infrastructure, and virtual private cloud.
### What is the 3DS Outscale DirectLink solution designed for?
With 3DS Outscale DirectLink, you can link your company network to your private 3DS Outscale Virtual Private Cloud network without creating a VPN tunnel through the internet. This gives you a faster, more stable connection with guaranteed bandwidth.
### How do I establish redundancy between my MCR and 3DS Outscale?
We suggest establishing redundant VXCs between two different 3DS Outscale regions or availability zones within a region with two corresponding ports at each Megaport-enabled data center.
### Are my bandwidth speeds set?
The bandwidth is set in increments specified by you from 1 Mbps. Maximum bandwidth depends on the selected region and service configuration.
### Does 3DS Outscale support public or private ASNs?
3DS Outscale supports private ASNs. If you are using a private ASN, it must be between 64512 and 65535. The use of public ASNs is available upon request.
## Helpful references
* [3DS Outscale Documentation](https://docs.outscale.com/en/userguide/Home.html)
* [3DS Outscale DirectLink](https://en.outscale.com/networks/directlink/#:~:text=3DS%20OUTSCALE%20offers%20DirectLink%2C%20a,or%20third%2Dparty%20network%20provider.)
* [Installing and Configuring OSC CLI](https://docs.outscale.com/en/userguide/Installing-and-Configuring-OSC-CLI.html)
* [DirectLink API Documentation - VIF Creation](https://docs.outscale.com/directlink#directlink-api-virtual-interfaces)
* [Hosted Private Cloud Pricing](https://en.outscale.com/pricing/how-pricing-works/)
* [3DS Outscale Compatible Virtual Machine Pricing](https://en.outscale.com/pricing/aws-compatible-vm-pricing/)
# Creating MCR Connections to OVHcloud Connect
Source: https://docs.megaport.com/cloud/mcr/ovhcloud
This help topic describes how to create connections between a Megaport Cloud Router and OVHcloud Connect.
Megaport makes it easy to provision fast, secure, and private connections to OVHcloud Connect through our global software-defined network (SDN). Megaport is an OVHcloud partner providing direct private access to the OVHcloud infrastructure. You can quickly provision connectivity from hundreds of Megaport-enabled locations to OVHcloud regions and OVHcloud Connect Points-of-Presence (PoPs) across North America, Europe, and Asia Pacific.
You can create a Virtual Cross Connect (VXC) from an MCR to OVHcloud Connect from the Megaport Portal. You can also create additional VXCs to other Cloud Service Providers (CSPs) for multicloud access from the MCR. Click the appropriate CSP link in the [MCR Cloud Connectivity Overview](/cloud/mcr) navigation.
The benefits of direct connectivity to OVHcloud Connect through Megaport include:
* Secure, private connectivity throughout Megaport’s redundant network infrastructure. Your traffic will not transit the public internet.
* High performance and predictability of your network.
* Improved data and operational security.
* Flexible and scalable cloud networking options.
* Consistent connectivity while scaling bandwidth to OVHcloud Connect. This means no downtime when you need to change your VXC speed.
* Connect to multiple regions from a single interconnection point, which uses multi-region redundancy at a fraction of the cost.
## How it works
OVHcloud Connect consists of a physical network connection at several OVHcloud locations around the world. OVHcloud locations reside within facilities operated by co-located data centers where Megaport is enabled.
Physical fiber connections (NNIs) at each location between Megaport and OVHcloud are established to OVHcloud routers. These physical connections are maintained between OVHcloud and Megaport.
Connecting to OVHcloud follows these general steps through the Megaport Portal:
1. Order Megaport Cloud Routers (MCRs) in Megaport locations of your choice. Two MCRs are required for redundancy.
2. Order VXCs to OVHcloud in fixed increments of 200 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, or 5 Gbps.\
VXCs to OVHcloud are established as a Layer 3 service between OVHcloud and the MCR. One VXC from each MCR is required for redundancy.
## Availability
OVHcloud is available in these locations:
* Europe
* Frankfurt
* London
* Paris
You can connect to multiple regions from a single interconnection point (which lets you use multi-region redundancy at a fraction of the cost).
For more information, see [OVHcloud Connect](http://ovh.com/world/solutions/ovhcloud-connect/).
## Prerequisites
Before you begin, notify OVHcloud. If you are an existing OVHcloud customer, contact your OVHcloud Account Manager and establish an agreement for OVHcloud services. If you are a new customer, you can order from the [OVHcloud Connect website](http://ovh.com/world/solutions/ovhcloud-connect/).
OVHcloud will provide you with a service key that is unique for each cloud peering location interface: one for the primary and one for the secondary cloud peering location interface.
The key includes the provider (Megaport), VLAN ID, speed, and OVHcloud port location.
To use your OVHcloud service key, you will need to create an MCR or connect your service key to an existing MCR from your Megaport Portal account. An MCR enables data transfer between multicloud and hybrid cloud environments, network service providers, and cloud service providers. For more information, see [Creating an MCR](/mcr/creating-mcr).
## Setting up OVHcloud Connect
The easiest way to create a connection between Megaport and OVHcloud is with a service key. A service key includes the essential configuration details for your business and automates much of the configuration process. Once you receive your service key from OVH, you specify your Layer 3 connectivity information in the OVHcloud portal. You then create a VXC in the Megaport Portal to connect MCR to OVHcloud.
**To configure your Point of Presence in OVHcloud**
1. Log in to the OVHcloud website.\
If this is your first time, you will need to register for an account.
2. Order an OVHcloud Connect with Megaport as the partner.
3. Click Order Product.
4. Select Megaport as the partner.
5. Select the speed for the connection.
6. Select the OVHcloud Connect location.\
Within minutes of placing the order, you will receive an email notification that includes your Service Key identifier.
When you use the service key created by OVHcloud, you are responsible for any VXC charges.
7. Select My Orders from the Dashboard navigation pane to verify if your order is complete and ready for service.
Once the Service Key is active in your OVHcloud portal account, you will attach a vRack.
8. In the Dashboard view, select OVHcloud Connect.
9. Choose Network > OVHcloud Connect, and select the Service Description that you created when ordering the OVHcloud Connect service key.
10. Click Attach a vRack under vRack.
11. Select the vRack to attach from the drop-down list and click **Attach**.\
If required, you can click the link to order a new vRack.
Once the vRack is attached, you will provide the Layer 3 connection details.
12. Specify the following details in the Add a PoP Configuration dialog box:
* **Type** -- L3
* **Customer ASN** -- Megaport ASN 133937
* **OVHcloud ASN** -- Your customer desired ASN
* **Subnetwork in /30** -- The IP address subnet range to peer with MCR. For example, 172.16.0.0 /30. OVHcloud will use the first IP address from the subnet mask.
These details apply the required IP address with a subnet mask and ASN to establish your peering connection between OVHcloud and Megaport.
13. Click **Create**.
**To deploy a VXC from MCR to OVHcloud Connect**
1. In the Megaport Portal, go to the **Services** page.\
If you don't have a Megaport account, see [Setting Up a Megaport Account](/setting-up).
2. Select the MCR for the connection and click **+Connection**.
3. Click **Enter Service Key** and click **Next**.
4. Enter the service key provided by OVHcloud in the **Megaport Service Key ID** field.
Megaport validates the key. Data including VLAN ID, speed, and OVHcloud location are included in the key and populate automatically. For more information about using a service key, see [Setting up Service Keys](/marketplace/service-keys).
5. Click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Enter the name of the VXC using the label provided by OVH.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit for the VXC is capped at the maximum allowable based on the OVHcloud Connect service key speed.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next**.\
The MCR Connection detail page appears, where you set up the peering session between the MCR and OVHcloud.
8. Enter your private IP address to connect to OVHcloud.\
You will apply this IP /30 subnet within your OVHcloud Manager Portal for the vRack environment.
9. Click **Add BGP Connection**.
10. Specify the connection details:
* **Local IP** -- The IP address on this interface (the MCR) that communicates with the BGP peer (OVHcloud Connect). The menu is automatically populated based on the address you specified in the MCR Connection detail. Select the IP address assigned to the MCR from the drop-down list.
* **Peer IP** -- Specify the IP address for the BGP peer (OVHcloud Connect).
* **Peer ASN** -- Enter the private peer autonomous system number (ASN) that you specified in the OVHcloud Manager Portal to connect to the MCR. Private ASNs must be between 64512 and 65535.
* **BGP Password** (optional) -- Specify the BGP key. If you leave this blank, Megaport negotiates a key automatically for you with OVHcloud which will be displayed in the Megaport Portal. (The key is not displayed in the OVHcloud Control Panel.) The shared key length is from 1 to 32 characters.
* **Description** (optional) -- Enter a name for this connection. The minimum description length is from 1 to 100 characters.
* **BGP State** -- This option should be set to Enabled.
11. Click **Add** to view the configured BGP connections.
12. Click **Next**.
13. Click **Add VXC** to proceed through the ordering process.
14. Repeat these steps to provision your secondary OVHcloud interface on a second MCR.
The second MCR must be in a different location from the primary MCR.
15. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
16. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
17. Click **Order Now**.
Once the VXC connection is deployed to OVHcloud, a single VLAN is assigned from your Megaport Portal account, with Layer 3 networking routing established using BGP between your MCR and OVHcloud VM vRack environment. Connections are private peering types, and will use private IPv4 addresses.
## Redundancy
To establish full redundancy between your data center and OVH, we recommend deploying redundant VXCs between two different OVHCloud regions (or availability zones within a region) with two corresponding MCRs at each Megaport-enabled data center.
### Redundant solution
### Fully redundant solution
## Updating the service bandwidth
You can scale the service speed up to the OVHcloud Connect speed rate at any time. If you require additional capacity, you must place an order for a new connection speed on the [OVHcloud website](https://www.ovh.com/world/solutions/ovhcloud-connect/).
To change the OVHcloud Connect speed, you must delete the Cloud Connect and VXC connections, and then recreate them.
## OVHcloud Frequently Asked Questions (FAQs)
### Are there any OVHcloud port fees?
OVHcloud doesn’t charge for data transfer. Customers pay a flat, auto-renewable monthly rate.
### What services are available using OVHcloud?
OVHcloud offers Private Cloud based on VMware platform, Bare Metal servers, Public Cloud based on Openstack and services as Kubernetes Managed, and Databases as a Service.
### What if I’m not located within an OVHcloud Point of Presence (PoP)?
You don’t have to be located within the same facility as OVHcloud; you can establish a VXC to the closest OVHcloud location of your choice. Each VXC is carried across Megaport’s redundant network to OVHcloud.
### Does OVHCloud support public or private ASNs?
OVHcloud supports public and private ASNs. If you are using a public ASN, you must own it. Private ASNs must be between 64512 and 65535. AS\_PATH prepending does not work if you are using a private ASN for your public VIF. Your preference is requested at the time of order. This is a private connection, but customers can peer with their private or public ASN and an OVHcloud private ASN that they can choose.
## Using a service key
You can create a service key that allows you to share your service with another Megaport account holder.
For more information, see [Setting up Service Keys](/marketplace/service-keys/).
## Helpful references
* [OVHcloud Connect](https://www.ovh.com/world/solutions/ovhcloud-connect/)
* [Hybrid and Multi-Cloud Solutions](https://www.ovhcloud.com/en/enterprise/solutions/datacentre-extension-cloud/hybrid-multi-cloud/)
* [Hosted Private Cloud Prices](https://www.ovh.com/world/private-cloud/options/)
# Creating MCR Connections to Salesforce Express Connect
Source: https://docs.megaport.com/cloud/mcr/salesforce
This help topic describes how to create connections between a Megaport Cloud Router and Salesforce Express Connect.
Salesforce Express Connect lets you access Salesforce applications and services directly with a private, dedicated connection. When you create a Salesforce Express Connect through the Megaport Portal:
* Express Connect is delivered as a Layer 3 routed service.
* You access Salesforce services using public IPs and are required to
run BGP to receive Salesforce routes.
* Megaport allocates a /31 public IP range for each Salesforce
peering.
* You can advertise your own public IP address space to Salesforce.
(Salesforce will not accept [RFC 1918](https://tools.ietf.org/html/rfc1918) routes.)
Deployment considerations:
* **Provisioning** -- One Virtual Cross Connect (VXC) provisions two logical connections to Salesforce using a Megaport Cloud Router (MCR). Salesforce has redundant routers that provide guaranteed uptime for both service locations.
* **Timeframe** -- Salesforce can take up to 2 business days for approval once a VXC is deployed from the Portal.
* **Internet Backup** -- Although Megaport always recommends two Ports for redundancy, an Express Connect over Megaport can be used for the primary connection to Salesforce and if you use publicly routed IP space and the single Megaport fails, routing to Salesforce can revert to the public internet.
This image shows a common Express Connect deployment:
**To create a connection to Salesforce Express Connect**
1. Log in to the Megaport Portal, choose **Services**, and select the MCR you want to configure.\
If you haven't already created an MCR, see
[Creating an MCR](/mcr/creating-mcr).
2. Add a VXC connection.\
If this is the first connection for the MCR, click the Salesforce
tile. The tile is a shortcut to the configuration page.
Alternatively, click **+Connection**, click **Cloud**, then click **Salesforce**.
3. Select Salesforce as the provider.
4. Select your destination Port and click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Accepted values start at 1 Mbps and scale up to several Gbps, depending on location and service availability.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.
7. On the pop-up window called **MCR A-End Connection Details**, click **Next**.
8. Provide these connection details:
* **ASN** -- Enter a private or public ASN. By default, the MCR ASN is 133937.
* **BGP Password** -- Leave this blank, as Salesforce doesn't support a BGP password.
* **Prefixes** -- Enter prefixes to announce to Salesforce -- RIR
assigned IPv4 address ranges only. If you do not have public
IP ranges, you can source NAT to the /31s IP provided by
Megaport. If you are going to use the /31s IP provided by
Megaport, you can leave this field blank. Once configured, you cannot add new prefixes to the VXC.
[RFC 1918](https://tools.ietf.org/html/rfc1918) space is not permitted.
9. Click **Next**.
A summary page appears that includes the monthly cost.
10. Click **Back** to make changes or click **Add VXC**.
Once you have finished this configuration, you can configure additional VXCs or proceed with the order.
11. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
12. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
13. Click **Order Now**.
After submitting the order, Salesforce can take up to 2 business days to approve the connection request. The VXC status will be *Deployable* until Salesforce accepts the connection.
When Salesforce accepts the request, two logical and redundant connections are created from Salesforce.
You can view and edit the details of your connection in the Megaport Portal by selecting the VXC and selecting Details.
## Using a service key
You can create a service key that allows you to share your service with another Megaport account holder.
For more information, see [Setting up Service Keys](/marketplace/service-keys/).
## Helpful references
* [Salesforce Express Connect Product Page](https://www.salesforce.com/campaign/salesforce-express-connect/)
# Creating MCR Connections to SAP HANA Enterprise Cloud
Source: https://docs.megaport.com/cloud/mcr/sap
This help topic describes how to create connections between a Megaport Cloud Router and SAP HANA Enterprise Cloud.
Megaport makes it easy to provision fast, secure, and private connections between a Cloud Service Provider (CSP) and the SAP HANA Enterprise Cloud with a Megaport Cloud Router (MCR).
Through private connectivity that bypasses the public internet, enterprises benefit from:
* Higher network performance, consistency, and predictability
* Streamlined and accelerated workloads and data migration
* Improved data and operational security
With SAP Cloud Peering through Megaport, you can connect to the SAP HANA Enterprise Cloud.
With an interconnection, you can use Megaport to reach additional cloud
providers, including Amazon Web Services, Microsoft Azure, Google Cloud
Platform, and others.
## How the SAP Cloud Peering service works
SAP consists of a physical network connection at several SAP points
of presence (PoPs) around the world. These PoPs reside within facilities
operated by co-located data centers where Megaport is enabled.
Physical fiber connections (NNIs) at each location between Megaport and
SAP are established on SAP HEC WAN routers (a minimum of two). These
physical connections are maintained between SAP and Megaport.
Connecting from a Cloud Service Provider to the SAP Cloud Peering Service follows these general steps through the Megaport Portal:
1. Order Megaport Cloud Routers in locations of your choice.\
Two MCRs are required for resilience.
2. Order VXCs to SAP in increments of 100 Mbps, typically up to 2 Gbps. Speeds greater than 2 Gbps are available on request.\
VXCs to SAP Cloud Peering are established as a Layer 3 service between SAP and the MCR. One VXC from each MCR is required for resilience.
3. Provision a VXC from each MCR to your chosen Cloud Service Provider.\
Detailed instructions for each CSP are in [Cloud Connectivity > MCR](/cloud/mcr).
## Availability
SAP Cloud Peering is available in these locations:
* Asia Pacific
* Sydney, Australia Equinix SY3
* Europe
* Frankfurt, Germany Equinix FR5
* North America
* Ashburn, US Digital Realty ASH1
* Sterling, US Cyxtera DC 1/2/3
* Santa Clara, US vXchange
You can connect to multiple regions from a single interconnection point (which lets you use multi-region redundancy at a fraction of the cost).
For more information, see the [provisioning guide in the SAP Help Portal](https://help.sap.com/doc/36c625027bd245818ac46998669c639f/ALL/en-US/SAP_Cloud_Peering_Customer_Guide.pdf).
## Setting up the SAP cloud peering service
Setting up SAP cloud peering requires two stages: first, open a ticket
with SAP to set up your SAP cloud peering service and configuration, and
second, create a connection from Megaport to SAP.
**To set up SAP cloud peering with SAP**
1. Contact your SAP Account Manager or cloud advisory architect and
establish an HEC agreement that covers SAP Cloud Peering services.
2. Open an SPC ticket and provide the following configuration details.
| **Required Information** | **Details** |
| :- | :- |
| Customer | HEC customer name and CID |
| Provider | Megaport |
| Location | Sydney, Frankfurt, Sterling, Ashburn, or Santa Clara |
| Solution | HEC |
| Bandwidth | 100 Mbps up to 2 Gbps or above |
| Customer contact | Contact details |
| 2 x BGP peering networks | 10.11.12.0/30, 10.11.12.4/30, or similar |
| Customer side IP1 & SAP side IP1 | 10.11.12.1/30 & 10.11.12.2/30, or similar |
| Customer side IP2 & SAP side IP2 | 10.11.12.5/30 & 10.11.12.6/30, or similar |
| MD5 secret for BGP | \< md5-hash-key > |
| ASN of customer BGP side | For example, 65200 is HEC01 |
| Customer side peering ASN | Public or private ASN |
| SAP side peering ASN | Public or private ASN |
When configured, SAP provides a unique Megaport service key for both
cloud peering location interfaces: one key for the primary and one key for the
secondary.
**To set up SAP Cloud Peering with Megaport**
1. Log in to the Megaport Portal.\
If you don’t already have an MCR, create one following the procedures in [Creating an MCR](/mcr/creating-mcr). Two MCRs are required for resilience.
2. Add a VXC connection for the MCR.\
If this is the first connection for the port or MCR, click the SAP
tile. The tile is a shortcut to the configuration page.
Alternatively, click **+Connection**, click **Cloud**, then click **SAP**.
3. Enter the service key provided by SAP and click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. This number populates automatically based on the rate defined with the service key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.\
The MCR Connection Detail page appears, where you can set up the peering session between the MCR and the SAP HEC WAN router based on the configuration details in the SPC ticket, and add IPsec tunnels if you want them.\
For more information, see [Creating an MCR VXC](/mcr/mcr-vxc).
6. Enter your local IP address.
7. If the MCR has IPsec enabled, you can add IPsec tunnels.
Click **+ Add IPsec Tunnel Interface**.\
Add the IPsec tunnel details:
* **Description** -- Enter a description of the IPsec tunnel for your reference.
* **Source IP Address** -- Click the box and select the address from the drop-down list.\
This is a list of interface IP addresses defined on this VXC.
* **Destination IP Address** -- Add the destination IP address.\
The destination IP address of the tunnel must not be an IP address configured on the same MCR.
* **Pre-shared key** -- Add a key that is common to both the IKE2 (Internet Key Exchange version 2) initiator and responder. The length must be between 8 and 100 characters.
* **Local Identifier** (optional) -- Enter the identifier used for IKE authentication. This allows you to override the default source IP address with a non-IP address, which is required for some configurations. By default, the source IP address is used. Valid values include IPv4/IPv6 addresses, domain names, and email addresses (lowercase, 5-100 characters). For example, `megaport.com` or `user@example.com`.
* **Remote Identifier** (optional) -- Enter the identifier used for IKE authentication. This allows you to override the default destination IP address with a non-IP address, which is required for some configurations. By default, the destination IP address is used. Valid values include IPv4/IPv6 addresses, domain names, and email addresses (lowercase, 5-100 characters). For example, `megaport.com` or `user@example.com`.
* **Start Action** -- Select either active or passive. Passive indicates that the local MCR is an IPsec responder waiting for the remote to perform IKE2 initiation.
* **Phase 1 Lifetime** -- Enter a value between 300 and 604800 seconds. This is the lifetime of IKE2 session in seconds. The default value is 28800 seconds (8 hours). When it expires, rekeying will occur.
* **Phase 2 Lifetime** -- Enter a value between 300 and 86400 seconds. This is the lifetime in seconds of the IPsec Security Association (SA). The value must be less than the Phase 1 Lifetime. The default value is 3600 seconds (1 hour). When it expires, rekeying will occur.
8. Click **Add BGP Connection**.
9. Specify the connection details:
* **Local IP** -- Select the IP address assigned to the MCR from the drop-down list.
* **Peer IP** -- Select the second available IP address assigned by the customer.
* **Peer ASN** -- Enter the peer autonomous system number (ASN) assigned by SAP. For example, 65200 is HEC01.
* **BGP Password** (optional) -- Specify a shared key to authenticate the BGP peer. You will need to use this key when you configure your BGP peer group in the SAP Console. The shared key length is from 1 to 25 characters. The key can include any of these characters:\
a-z
A-Z
0-9
! @ # ? . \$ % ^ & \* + = -
Click the eye icon to see the password as you type. The view persists until you click the eye icon again to hide the password.
* **Description** (optional) -- Enter a description for the connection.
* **BGP State** -- Shuts down the connection without removing it. The initial setting will be taken from the setting on the A-End of the MCR. Enabling or shutting down the BGP state does not affect existing BGP sessions. The BGP state only affects new VXCs. This setting overrides the MCR state for an individual connection.
10. Click **Add VXC**.
11. Repeat these steps to provision your secondary SAP Cloud Peering
interface on a second MCR. The second MCR must be in a different location from the primary MCR.
12. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
13. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
14. Click **Order Now**.
## Resiliency to SAP
By default, SAP provides a primary and secondary interface. For maximum resiliency, we recommend provisioning two Megaport MCRs in separate data centers. VXCs from Megaport correspond to the two SAP WAN router connections.
## Updating the service bandwidth
You define your VXC speeds at the time of signing your agreement with SAP.
If you need to change the speed, work with your SAP Account Manager to
define your new speed and then update the VXC configuration in the
Megaport Portal with the new speed.
Speed changes require approval from SAP. SAP accepts or rejects incoming
speed change requests based on the contracted agreement. Speed changes
do not affect network traffic.
## Using a service key
You can create a service key that allows you to share your service with another Megaport account holder.
For more information, see [Setting up Service Keys](/marketplace/service-keys/).
## SAP Frequently Asked Questions (FAQs)
### Does SAP HANA Enterprise Cloud offer BYOIP?
Yes, SAP HANA Enterprise Cloud lets you bring your own IP address.
### What if I'm not located within an SAP cloud peering enabled facility?
You don't have to be located within the same facility as SAP. You can establish a VXC to the closest SAP location of your choice. Each VXC is carried across the Megaport redundant network to SAP.
### Are my bandwidth speeds set?
Yes, you set your speeds when you sign your agreement with SAP. Speeds are set to 100 Mbps, in increments of 100 Mbps up to 2 Gbps (and speeds greater than 2 Gbps are available on request).
### Does SAP support public or private ASNs?
SAP supports both private and public ASNs.
# Connecting to 11:11 Systems Cloud
Source: https://docs.megaport.com/cloud/megaport/1111systems/index
This help topic describes how to connect to 11:11 Systems (11:11 Systems) Cloud.
Megaport makes it easy to provision fast, secure, and private connections to 11:11 Systems Megaport-enabled Connected Hubs through our global software-defined network (SDN).
Connect from any Megaport location to 11:11 Systems cloud services platforms and
3rd-party cloud providers. 11:11 Systems Cloud services let you build the interconnectivity
you need for high performance Hybrid IT multicloud architectures.
The benefits of direct connectivity to the services you need:
* Secure, private connectivity throughout Megaport’s redundant network infrastructure. Your traffic will not transit the public internet.
* High performance and predictability of your network.
* Improved data and operational security.
* Flexible and scalable cloud networking options.
* Consistent connectivity while scaling bandwidth to and from 11:11 Systems. This means no downtime when you need to change your Virtual Cross Connect (VXC) speed.
* Connect to multiple regions from a single interconnection point, which uses multi-region redundancy at a fraction of the cost.
## How it works
11:11 Systems Cloud services consist of physical network connections at 11:11 Systems Megaport-enabled Connected Hubs in the US, Canada, and Europe that are connected to the Megaport Global Network.
Physical optical connections () at each location between Megaport and 11:11 Systems are established to 11:11 Systems infrastructure. These physical connections are maintained between 11:11 Systems and Megaport.
Ports and Virtual Cross Connects (VXCs) connect to the Megaport-enabled locations and establish interconnectivity to cloud services. You can choose from 1 or 10 Gbps dedicated ports and VXCs with a scalable rate limit, configurable up to the maximum port size. Shared ports are also available for customers with bandwidth requirements up to 500 Mbps. (100 Gbps ports are not currently available at 11:11 Systems Connected Hubs.)
11:11 Systems Cloud services offers these connectivity options:
* Use a Megaport account and the Megaport Marketplace to establish connectivity through Ports from Megaport-enabled data centers with VXCs to 11:11 Systems Cloud services at 11:11 Systems Connected Hubs.
* 11:11 Systems establishes Ports from 11:11 Systems Connected Hubs with VXCs to consume resources from 3rd-party cloud providers.
Once a VXC connection deploys to a cloud service, a single connection is assigned with routing established between your physical network device and the endpoint. You can connect to multiple regions from a single interconnection point, allowing you to use multi-region redundancy at a fraction of the cost.
## Services and ordering
Existing 11:11 Systems customers can contact their 11:11 Systems Account Manager and establish an agreement for 11:11 Systems Cloud services. New customers can contact 11:11 Systems through their website to discuss options.
For customers who want a managed service, 11:11 Systems offers a Managed Cloud service.
You contract directly with 11:11 Systems for Managed Cloud services.
With a contract in place, 11:11 Systems creates the required Ports and VXCs and fulfills change requests for the Ports and VXCs throughout the lifetime of the contract. Once 11:11 Systems has established the connections you need, 11:11 Systems will send you a monthly bill for the active Ports and the bandwidth usage for the VXCs.
11:11 Systems offers the following Managed Cloud services:
* 11:11 Systems establishes dedicated private 1 or 10 Gbps Ports from your Megaport-enabled location of choice and one or more VXCs into your destination of choice with your required rate limit.
* From shared Ports in a 11:11 Systems Megaport-enabled Connected Hub, 11:11 Systems AS establishes one or more VXCs, with a 500 Mbps maximum rate limit per VXC, to your destination of choice.
For existing Megaport customers who want to buy 11:11 Systems Cloud services directly from Megaport, 11:11 Systems offers the following:
* Buy or use existing Ports and set up VXCs for connectivity to 3rd-party cloud providers from one or more 11:11 Systems Megaport-enabled Connected Hub locations through the Megaport Portal.
* Buy or use existing Ports from Megaport-enabled locations and set up VXCs to establish connectivity into one or more 11:11 Systems Cloud services. 11:11 Systems provides you with a service key and instructions to set up the VXCs. You can find current 11:11 Systems Cloud service locations in the Megaport Marketplace.
## Setting up connectivity to a 11:11 Systems Cloud Service with Cloud
To create a connection from a Megaport Port to a 11:11 Systems Cloud service, you need a service key. A service key includes the essential configuration details for your business and automates much of the configuration process. 11:11 Systems generates the service key.
For Managed Cloud Service customers, 11:11 Systems uses the service key to set up the VXCs and create the connections.
If you prefer, you can create the connection to 11:11 Systems Cloud Service with the following procedure.
**To create a connection to 11:11 Systems Cloud Service in the Megaport Portal**
1. Contact 11:11 Systems to obtain a service key.
When you use the service key created by 11:11 Systems, you are responsible for any VXC charges.
2. In the Megaport Portal, go to the **Services** page.\
If you don’t have a Megaport account, see [Setting Up a Megaport Account](/setting-up).
3. Select the Port for the connection and click **+Connection**.
4. Click **Enter Service Key** and click **Next**.
5. Enter the service key provided by 11:11 Systems in the **Megaport Service Key ID** field.\
Megaport validates the key.\
Data including VLAN ID, speed, and 11:11 Systems location are included in the key and populate automatically. For more information about using a service key, see [Setting up Service Keys](/marketplace/service-keys).
6. Click **Next**.
7. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
Use this field for the SNT code.
* **Rate Limit** -- The speed of your connection in Mbps. Specify a speed for your connection in Mbps, up to the maximum allowable based on the maximum limit defined by the service key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection. 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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you do not specify a value, Megaport will assign one.
The B-End VLAN (11:11 Systems VLAN ID) for the provider-side termination will be automatically populated based on the service key. Alternatively, you can select **Untagged** to remove the VLAN tagging for this connection. The untagged option limits you to having only one VXC deployed on this port. You must use untagged VLANs if you are creating a MACsec connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
8. Click **Next**.\
A summary page appears that displays the monthly cost.
9. Click **Add VXC** to move this configuration to your cart.
10. Repeat these steps to provision any additional VXCs.
11. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
12. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
13. Click **Order Now**.
## Redundancy
To establish full redundancy between Megaport locations and 11:11 Systems, we recommend deploying redundant VXCs between two different 11:11 Systems locations with corresponding Ports at each Megaport-enabled data center.
### Redundant solution
### Fully redundant solution
## 11:11 Systems Frequently Asked Questions (FAQs)
### What fees will apply?
Customers pay a flat, auto-renewable monthly rate for the Port. The pricing for VXCs varies depending on the location and the bandwidth limit. You can change the bandwidth limit throughout the month, which will change the price.
Customers only pay for the Port, VXC, and bandwidth usage; 11:11 Systems doesn’t charge for data transfer.
### What services are available using 11:11 Systems Cloud?
11:11 Systems has several Megaport-enabled data centers known as Connected Hubs. You can connect to and from these hubs from other Megaport Locations through the Megaport SDN to create the interconnectivity you need to build high performance Hybrid IT, multicloud or hybrid cloud architectures. Go to the Megaport Marketplace for current 11:11 Systems Megaport-enabled locations and services.
### What if I’m not located within an 11:11 Systems Megaport-enabled Hub?
You don’t have to be located within the same facility as 11:11 Systems; you can establish a VXC from one Megaport-enabled location to the closest 11:11 Systems enabled Connected Hub of your choice. Each VXC is carried across Megaport’s redundant network to 11:11 Systems.
### Does 11:11 Systems support public or private ASNs?
This is a private connection, but customers can peer with their private or public ASN and a 11:11 Systems private ASN that they can choose.
# Connecting to Alibaba Express Connect
Source: https://docs.megaport.com/cloud/megaport/alibaba/index
This help topic describes how to create connections between a Port and Alibaba Express Connect.
The Alibaba private interconnection service is called Express Connect. Alibaba Express Connect enables customers to create private connections
between their remote network environments and their Virtual Private Cloud (VPC) deployments.
When connecting to Alibaba Cloud services through Express Connect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection and Layer 3 BGP is established directly between the customer and their private environment with Alibaba Cloud VPC.
## Benefits of Alibaba Express Connect through Megaport
The benefits of creating a Alibaba Express Connect through Megaport include:
* Enhanced security and higher network performance
* Scalable connectivity options
* API integration between Megaport and Alibaba which simplifies the provisioning of connections for a fast and seamless experience
* Connect to Alibaba Cloud on-ramp locations through any of the global [Megaport-enabled locations](https://www.megaport.com/megaport-enabled-locations/)
* Connect with the Alibaba Cloud Enterprise Network (CEN). For more information, see [What is Cloud Enterprise Network?](https://www.alibabacloud.com/help/doc-detail/59870.htm) in the Alibaba documentation.
## Creating a VXC to the Alibaba Cloud
Before you can create a connection to Alibaba Cloud, you need to have an Alibaba account (you can create one in the Alibaba Console). Your account number is required to create your Megaport VXC.
If you require a VXC to the Alibaba Cloud with a rate limit higher than 1 Gbps, contact your Alibaba and Megaport Account Managers to request a higher limit before proceeding. VXCs created with a higher rate limit without approval will not be deployed.
**To get your Alibaba account ID**
* Log in to the [Alibaba Cloud Console](https://account.alibabacloud.com/login/login.htm) and retrieve your account ID. When logged in, click your Avatar icon located in the top right corner and copy your Account ID.
**To create a VXC to your Alibaba Express Connect peer location**
1. In the Megaport Portal, find the Port to attach your VXC to and click **+Connection**.\
This example uses Alibaba Express Connect as the selected Port.\
If you haven't already created a Port, see [Creating a Port](/connections/creating-port).
2. Click the **Cloud** tile and click **Next**.
3. Select Alibaba Cloud as the provider.
4. Select the target location for your connection and click **Next**.\
You can use the Select Destination Port search field to narrow the selection.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Select one of Alibaba's supported speed options for the Shared Port connection.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged** to remove the VLAN tagging for this connection. The untagged option limits you to only one VXC deployed on this Port. You must use untagged VLANs if you are creating a MACsec connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.
7. Enter the Account ID copied from your Alibaba Console and click **Next**.
8. Add the VXC to your cart and configure more VXCs or proceed through the checkout process.\
Once you have completed and deployed the VXC in the Portal, return to the Alibaba Console and in the Express Connect section, find the new connection under Physical Connections. It will take a few minutes from the time you deploy the VXC for the connection to appear in the Alibaba Console. Make sure you select the Express Connect Region you selected in the Portal to find your connection under Physical Connections.
9. Click **Accept and Pay**.
10. Specify the duration of the Physical Connection.
11. Click **Buy Now**.
12. Confirm the payment details.
13. Once your payment has been accepted, return to the console.
14. Confirm that the Physical Connection Status has changed to *Enabled*.
# Connecting to Cisco Webex Edge Connect with Megaport
Source: https://docs.megaport.com/cloud/megaport/cisco/webex
This help topic describes how to connect a Port to Cisco Webex Edge Connect.
Megaport makes it easy to provision fast, secure, and private connections to Webex through our global software-defined network (SDN). As a Webex Edge Connect partner, Megaport provides customers with direct, private access to global Webex infrastructure via pre-provisioned on-ramps.
Webex Edge Connect peering is a private point-to-point network connection that bypasses the public internet and connects your network directly to Webex Meetings, and Webex Calling Multi-Tenant and Dedicated Instance data centers. Webex Edge Connect insulates meetings from the public internet, resulting in less congestion, , , and delay. No exposure to the internet means connections are more secure.
The benefits of direct connectivity to Webex through Megaport include:
* Private access that bypasses the public internet.
* High performance and predictability for your network.
* Improved data and operational security.
* Flexible and scalable cloud networking.
* Consistent connectivity while scaling bandwidth to Webex. This means no downtime when you need to increase or decrease your speed.
* Connect to multiple regions from a single interconnection point, which uses multi-region redundancy at a fraction of the cost.
## Availability
Webex Edge Connect is available in these locations with Megaport:
**Asia Pacific**
Singapore, Equinix SG1\
Sydney, Equinix SY1\
Melbourne, Equinix ME1\
Tokyo, Equinix TY2
**Europe**
Amsterdam, Equinix AM1\
London, Telehouse North\
Frankfurt, Equinix FR5
**North America**
Ashburn, Equinix DC 4\
Chicago, Equinix CH4\
Dallas, Equinix DA1\
San Jose, Equinix SV1\
New York City, Digital Realty NYC2
## Prerequisites
To create a connection to Cisco Webex, you need the following:
* **ASN** - Public and Private BGP autonomous system number (ASN).
* **IP address** -- An IP space that is public and provider-independent. This is not supplied by Megaport or Cisco, please discuss these specific details with Cisco.
Edge Connect does not accept private IP advertisements like RFC1918 addresses for the BGP peering IP addresses for the connection.
* **Cisco Webex Edge Connect account** -- To request a connection to Cisco Webex and obtain a service key, you must have an account for the Cisco Webex Edge Connect portal at [https://edgeconnect.webex.com](https://edgeconnect.webex.com).
* **Megaport account** -- If you haven’t already created one, see [Creating an Account](/setting-up/registering).
* **Port** -- Select the required Port speed. Port capacity depends on location and service availability. You can create, for example, a 10 Gbps Port onto the Megaport network, with Virtual Cross Connects (VXCs) that connect your data center and a Webex location. If you haven’t already created one, see [Creating a Port](/connections/creating-port).
## Creating a connection to Webex
To create a connection between Megaport and Webex, you must obtain a service key from Cisco Webex. A service key includes the essential configuration details and automates much of the configuration process. Prior to receiving a service key, Webex requires information from the customer to configure Layer 3 BGP peering in the appropriate metro.
After obtaining the service key from Cisco Webex, you can create a VXC from a Port to Webex.
**To request a connection to Webex**
1. Ensure you have a Megaport account and a Port.
2. Purchase Webex Edge Connect from Cisco.
3. Enter all sales, customer, partner, and technical information into the [Cisco Webex Edge Connect portal page](https://edgeconnect.webex.com).
4. Webex edge routers are configured based on the information provided, along with the appropriate backbone connectivity to the different data centers.
5. You will receive an email from [csg-peering@cisco.com](mailto:csg-peering@cisco.com) with a service key. You need to enter the service key in the Megaport Portal when creating a VXC to Webex.
6. Configure your edge router.\
IP connectivity is established between your router and Webex router.
This process can take up to 10 business days to complete, excluding holidays, starting from the date the provision request is submitted via the [Cisco Webex Edge Connect portal page](https://edgeconnect.webex.com).
**To create a VXC to Webex in the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page.
2. Select the Port for the connection and click **+Connection**.
3. Click **Enter Service Key** and click **Next**.
4. Enter the key provided by Webex.
Megaport validates the key. For more information about using a service key, see [Setting up Service Keys](/marketplace/service-keys).
5. Click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Accepted values start at 1 Mbps and scale in 1 Mbps increments. Maximum available speed depends on location and service availability. Note the sum of all hosted virtual VXCs to a service can exceed the Port capacity (1 or 10 Gpbs) but the total aggregate will never burst beyond the Port capacity. Higher speeds might be available depending on location and Port capabilities.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** -- The VLAN for this connection that you will receive through the Port.\
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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged**. This selection removes the VLAN tagging for this connection but also means that only one VXC can be deployed on this Port. You must use untagged VLANs if you are creating a MACsec connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next**.\
A summary page appears that includes the monthly cost.
8. Click **Add VXC** to move the configuration to your cart.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
## Redundancy
To establish full redundancy between your data center and Webex, we recommend deploying redundant VXCs between two different Webex regions (or availability zones within a region) and two corresponding Ports at each Megaport-enabled data center.
## Helpful references
* [Cisco Webex Edge Connect Product Overview](https://www.cisco.com/c/en/us/products/conferencing/webex-edge-connect/index.html)
* [Webex Edge Data Sheet](https://www.cisco.com/c/en/us/products/collateral/conferencing/webex-edge/data-sheet-c78-741264.html)
* [Preferred Architecture for Cisco Webex Edge Connect](https://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/EdgeConnect/PA_Edge_Connect_Design.pdf)
* [Webex Edge Connect Help Center](https://help.webex.com/en-us/article/n68tcpb/Webex-Edge-Connect)
# Connecting to Cloudflare with Megaport
Source: https://docs.megaport.com/cloud/megaport/cloudflare/index
This help topic describes how to connect to Cloudflare.
Megaport makes it easy to provision fast, secure, and private connections to Cloudflare through our global software-defined network (SDN). As part of the Cloudflare Network Interconnect (CNI) Partner program, Megaport provides customers with direct, private access to the Cloudflare infrastructure.
The benefits of direct connectivity to Cloudflare through Megaport include:
* Private access that bypasses the public internet.
* High performance and predictability for your network.
* Improved data and operational security.
* Flexible and scalable cloud networking.
* Consistent connectivity while scaling bandwidth to Cloudflare. This means no downtime when you need to increase or decrease your speed.
* Connect to multiple regions from a single interconnection point, which uses multi-region redundancy at a fraction of the cost.
## Availability
Cloudflare Network Interconnect is available in these locations with Megaport:
**Asia Pacific**\
Singapore, Equinix SG1\
Sydney, Equinix SY 1/2\
Tokyo, Equinix TY2
**Europe**\
Amsterdam, Equinix AM1\
Frankfurt, Equinix FR5\
London, Telehouse North
**North America**\
Ashburn, Equinix DC/6\
Chicago, Equinix CH1/2/4\
Los Angeles, Equinix LA1\
Miami, Equinix MI1\
New York City, Digital Realty NYC2\
San Jose, Equinix SV1/5/10\
Seattle, Equinix SE2\
Toronto, Equinix TY2
## Prerequisites
Before you begin, notify Cloudflare. If you are an existing Cloudflare customer, contact your Cloudflare Account Manager.
If you are a new business looking to use Cloudflare Network Interconnect (CNI) to connect securely and reliably with Megaport, you can [email Cloudflare directly](mailto:interconnection@cloudflare.com). In addition to performance benefits, Cloudflare services include Magic Transit, authenticated origin pulls for large content delivery network (CDN) customers, and Cloudflare for Teams.
If you are a new business that requires a public peering service, you can [request peering service](https://www.cloudflare.com/partners/peering-portal/). Examples include ISPs, service providers, large networks, and CDNs that exchange a significant amount of data.
After you notify Cloudflare, ensure you have a Megaport connection:
* **Port** -- You can create a 10 Gbps Port onto the Megaport network, with Virtual Cross Connects (VXCs) that connect your data center and a Cloudflare location. Higher-capacity Ports, for example, 100 Gbps or higher, are available depending on location and service availability. If you haven’t already created one, see [Creating a Port](/connections/creating-port).
* **MCR** -- An MCR enables data transfer between multicloud and hybrid cloud environments, network service providers, and cloud service providers. For more information, see [Creating an MCR](/mcr/creating-mcr).
Public ASNs are required.
## Creating a connection to Cloudflare
The easiest way to create a connection between Megaport and Cloudflare is with a service key. A service key includes the essential configuration details and automates much of the configuration process. After obtaining the service key from Cloudflare, you can create a VXC from the Port or MCR to Cloudflare.
**To request a connection to Cloudflare**
1. Contact Cloudflare to obtain a service key.
2. In the Megaport Portal, go to the **Services** page.
3. Select the Port or MCR for the connection and click **+Connection**.
4. Click **Enter Service Key** and click **Next**.
5. Enter the key provided by Cloudflare.
Megaport validates the key. For more information about using a service key, see [Setting up Service Keys](/marketplace/service-keys).
6. Click **Next**.
7. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Accepted values start at 1 Mbps and scale in 1 Mbps increments. Maximum available speed depends on location and service availability. Note the sum of all hosted virtual VXCs to a service can exceed the Port capacity (1 or 10 Gpbs) but the total aggregate will never burst beyond the Port capacity. Higher speeds might be available depending on location and Port capabilities.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** -- The VLAN for this connection that you will receive through the Port.\
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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged**. This selection removes the VLAN tagging for this connection but also means that only one VXC can be deployed on this Port. You must use untagged VLANs if you are creating a MACsec connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
8. Click **Next**.\
The summary page shows the monthly cost.
9. Click **Add VXC** to move the configuration to your cart.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
Once you deploy a VXC connection to Cloudflare, you need to configure the Layer 3 BGP connectivity between your network equipment and Cloudflare, including a Public ASN and Public IPs to peer with Cloudflare.
## Redundancy
To establish full redundancy between your data center and Cloudflare, we recommend deploying redundant VXCs between two different Cloudflare regions (or availability zones within a region) and two corresponding Ports at each Megaport-enabled data center.
## Cloudflare Frequently Asked Questions (FAQs)
### Does Cloudflare offer BYOIP?
Cloudflare is a public service, so you can use your own public IPs.
### Does Cloudflare support public or private ASNs?
Cloudflare supports public ASNs. If you are using a public ASN, you must own it. Cloudflare will verify ownership for Magic Transit before announcing network routes.
## Helpful references
* [Infopaper: Connecting to Cloudflare with Megaport](https://www.megaport.com/services/cloudflare-network-interconnect/)
* [Cloudflare Enterprise Services](https://www.cloudflare.com/enterprise/)
* [Cloudflare DDoS](https://www.cloudflare.com/ddos/)
* [Cloudflare CDN](https://www.cloudflare.com/cdn/)
* [Cloudflare Magic Transit](https://www.cloudflare.com/magic-transit/)
# Diversity in Google Connections
Source: https://docs.megaport.com/cloud/megaport/google/google-diversity
This help topic describes how to identify and create diverse connections in Google Cloud.
Diverse connections improve the robustness of your network by using different physical infrastructure to provide network services. Diverse connections build in redundancy and eliminate single points of failure.
Google Cloud and Megaport simplify the deployment of diverse connections by establishing multiple domains (1 and 2) within each metro. Each domain is physically separated on Megaport edge devices and connected to diverse Google devices. During Megaport scheduled maintenance, no more than one domain within a data center will experience downtime at any moment. Whenever possible, diverse services have maintenance periods scheduled for different days.
Each Google Cloud destination port indicates its domain using "zone1" or “zone2” in the Megaport Portal.
To create diverse connections, you need to create two connections: one connection for each Google Cloud destination port. This image shows the approach of using VXCs to diverse Google Cloud ports.
For end-to-end diversity, the connections must be on diverse ports at both ends. In other words, truly diverse VXCs can only exist between two pairs of diverse ports. This image shows a fully redundant solution with VXCs from different physical locations using diverse ports.
The preferred diversity method deploys connections in different Megaport locations. This offers the most redundancy and protection.
## Helpful references
* [How to Establish 99.9% Availability for Partner Interconnect | Google Cloud](https://cloud.google.com/network-connectivity/docs/interconnect/tutorials/partner-creating-999-availability)
* [How to Establish 99.99% Availability for Partner Interconnect | Google Cloud](https://cloud.google.com/network-connectivity/docs/interconnect/tutorials/partner-creating-9999-availability)
# Connecting to Google Cloud Services
Source: https://docs.megaport.com/cloud/megaport/google/index
This help topic describes the supported connection models between Megaport and Google Cloud Services.
Megaport supports these private and public options to access Google Cloud offerings.
* [Partner Interconnect](#partner-interconnect) -- to access the private address space
([RFC 1918](https://tools.ietf.org/html/rfc1918)) to access a Virtual Private Cloud (VPC)
* [Direct Peering](#direct-peering) -- for public access
## Partner Interconnect
Megaport makes it easy to provision fast, secure, and private connections between a customer's data center and Google Cloud Platform.
As part of the Google Cloud Interconnect (GCI) Partner program, Megaport provides users with dedicated access to Google Cloud Platform (GCP) and enables customers to create private connections between their remote network environments and their Virtual Private Cloud (VPC) deployments.
The benefits of creating GCI Partner Connections with Megaport include:
* Enhanced security and higher network performance
* Connectivity reach beyond Google's existing network locations
* Scalable connectivity for those who do not require the full
bandwidth of Google's Dedicated Interconnect
* Savings on egress traffic costs from the customer's VPC network to
their on-premises network
* API integration between Megaport and Google Cloud which simplifies
the provisioning of connections for a fast and seamless experience
When connecting to Google Cloud Platform (GCP) through Partner Interconnect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection and Layer 3 BGP is established directly between the customer and GCP. Through Partner Interconnect, a customer can access VMs (Virtual Machines) built within a VPC.
### Creating a VXC to the Google Cloud Platform
Before you begin, make sure you've performed these tasks:
* Created a Partner Interconnect attachment in Google Cloud Console or
gcloud CLI.
* Copied the pairing key that is provided as part of the attachment
creation.
**To deploy a VXC to Google Cloud Platform**
1. Log in to your Google Cloud
Console and create a pairing key.
2. From the main menu in the console, select Hybrid Connectivity > Interconnect.
3. Click **Get Started**.
4. Select Partner Interconnect and click **Continue**.
5. Click **I already have a service provider**.
6. Configure your attachment.
Provide the following details:
* **Redundancy** -- Review the options for redundancy and select. You can create redundant Attachments or single Attachment.
* **Network** -- Select VPC network you want your VPC to connect.
* **Region** -- Select region where your attachment will connect.
* **Cloud Router** -- A Cloud Router to associate with this attachment.
You can only choose a Cloud Router in the VPC network and region
that you selected with an ASN of 16550. If you don't have an
existing Cloud Router, create one with an ASN of 16550. For
redundancy, each VLAN attachment must be associated with a unique
Cloud Router. Google automatically adds an interface and a BGP
peer on the Cloud Router.
* **VLAN attachment name** -- Lowercase letters only.
* **Description** -- An optional field.
* **Maximum Transmission Unit (MTU)** -- Set the MTU to match the MTU of your VPC network. The default VPC network MTU is 1460 bytes.
7. Click **Create**.\
A pairing key appears.
8. Copy the pairing key and click **OK**.
9. In the Megaport Portal, create a VXC to your Google peering location:\
Click **+Connection** on the Port for your VXC.\
This example has Google GCI Partner as the selected Port.
10. Click the **Cloud** tile.
11. Select Google as the provider.
To check the latency and price of connecting to a particular Google location, click **View all Google Partner locations**. You can proceed to the Connection Details page without a pairing key and review the pricing of the selected port. To place an order for a Google connection, you need to provide a pairing key.
1. Copy and paste the pairing key from the Google Cloud console into the Google Partner Pairing Key field.\
The relevant Google targets appear based on the region of your GCI Partner connection.
2. Select your chosen target location for your first connection then click **Next**.
3. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Enter the same rate you selected for your Google port speed.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** -- The VLAN for this connection that you will receive through the Port.\
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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged**. This selection removes the VLAN tagging for this connection but also means that only one VXC can be deployed on this Port. You must use untagged VLANs if you are creating a MACsec connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
4. Add the VXC to your cart and configure further VXCs or proceed through the checkout process.
5. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
6. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
7. Click **Order Now**.
8. To deploy a second connection (recommended), repeat these steps and select *Add a redundant VLAN to an existing VLAN* in step 6. Adding a second connection ensures that you receive [redundancy and an SLA from Google](https://cloud.google.com/network-connectivity/docs/interconnect/concepts/partner-overview#redundancy).
After you have completed and deployed the VXC, go back to your attachment in the Google Cloud Console and accept the attachment. You will be provided your private IP address from Google to configure your BGP.
This completes your Layer 2 VXC deployment.
The Google ASN will always be 16550.
For additional details, see the Google documentation on [Google Partner Interconnects](https://cloud.google.com/interconnect/docs/how-to/partner/provisioning-overview).
## Direct Peering
Direct Peering allows Google Cloud Platform (GCP) customers to connect
to Google through carrier-grade connections that can reduce latency and increase availability versus best-effort internet connections.
Direct Peering with Google is achieved by exchanging BGP routes between Google and the customer network. Once Direct Peering is in place, customers can reach all Google's services including the full suite of GCP products.
Features and benefits:
* Reduced latency, increase availability
* Reduce data egress cost
* Secure connectivity
* Access to all Google Cloud services and Google apps for business
across one connection
When connecting to GCP Direct Peering with Megaport, the Virtual Cross Connect (VXC) forms a Layer 2 VXC between the customer's Port and Mega-IX or AMS-IX.
Direct Peering requirements:
* Publicly routable ASN
* Publicly routable address space (at least one /24 of IPv4 and/or one /48 of IPv6 space)
Not all customers meet Google's [Direct Peering requirements](https://peering.google.com/#/options/peering). Customers are not required to have 24/7 NOC, but must meet remaining requirements outlined by Google.
Megaport - Google IX Peering Locations:
* MegaIX: Ashburn, Dallas, Los Angeles, Seattle, Singapore, Sofia, Sydney
* AMS-IX: Chicago, New York, Bay Area
For more information, see [PeeringDB](https://www.peeringdb.com/asn/15169).
**To deploy a Google Direct peering VXC connection**
1. Create a VXC in the Megaport Portal to a MegaIX or AMS-IX Peering location.
2. Click **+Connection** for the Port you want to attach your VXC.
3. Select the Internet Exchange tile.
4. Select the MegaIX location where a peer will be set up with Google
and click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Accepted values are in 1 Mbps increments up to the Port rate size.
6. Click **Next**.
7. Provide the connection details for the service:
* **Preferred VLAN** -- The VLAN for this connection that you will
receive via the Port. This must be a unique VLAN ID on this Port and can range from 2 to 4093. Alternatively, you can select **Untagged**. This selection removes the VLAN tagging for this connection but also means that only one VXC can be deployed on this Port.
* **ASN** -- You must own a registered Publicly routable ASN.
* **MAC Address** -- The MAC address of your device used to peer.
* **Graph Visibility** -- Select Public or Private visibility.
If Public is selected, the usage graph will be visible on the
MegaIX. If Private is selected, the usage graph will not be visible.
8. Click **Next** and add the VXC then proceed through the checkout
process.
To complete the Google Direct Peering process, you need to
register
with Google.
# Connecting to IBM Cloud Direct Link
Source: https://docs.megaport.com/cloud/megaport/ibm/direct-link-2.0
This help topic describes how to create a connection from a Port between Megaport and IBM Cloud Direct Link.
IBM Direct Link lets you create private connections between your remote network environments and their IBM Cloud deployments.
When connecting to IBM through a Direct Link with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection. Layer 3 BGP connectivity is established directly between the customer and IBM Cloud.
This topic describes how to connect to IBM Direct Link from a Port. For more information about connecting from an MCR, see [Creating MCR Connections to IBM Cloud Direct Link](/cloud/mcr/ibm-2.0).
If you edit an older VXC to IBM Cloud Direct Link in the Megaport Portal, a prompt appears stating that Megaport has updated API integrations, and advises you to cancel and reorder the VXC. In this situation, we recommend that you cancel and then reorder the VXC using the latest API integration.
## Benefits of IBM Direct Link through Megaport
The benefits of creating an IBM Direct Link through Megaport include:
* Reduced latency, increased availability
* Reduced data egress cost
* Secure connectivity
## Creating a connection to IBM Direct Link
To set up IBM Direct Link with Megaport, you need to create a VXC from your Port in the Megaport Portal to the IBM Direct Link cloud location.
Design considerations when setting up your Direct Link to IBM Cloud:
* **Redundancy** -- Megaport supports redundant connections. In each of the Direct Link peering locations, Megaport has established two diverse Direct Links with IBM Cloud. In the Megaport Portal, the Ports are noted as Port 1 and Port 2. A redundant configuration requires two or more VXCs.
* **Local and Global Routing Options** -- The Local Routing option provides
access to data centers with the same three-letter prefix as the
Point of Presence (such as DAL, AMS, and MEL). The Global Routing
option is required as an add-on to reach data centers outside of
those locations. For more information about local and global routing options,
see the [IBM cloud documentation](https://cloud.ibm.com/docs/direct-link).
* **Port speed** -- Port speed options for IBM Direct Link Connect are 50 Mbps, 100
Mbps, 200 Mbps, 500 Mbps, 1 Gbps, 2 Gbps, or 5 Gbps. For pricing
details from IBM, see
[Pricing for IBM Cloud Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-pricing-for-ibm-cloud-dl).
* Megaport-enabled Direct Link locations:
* North America: Ashburn, Chicago, Dallas, San Jose, Toronto
* Europe: Amsterdam, Frankfurt, London, Paris
* Australia: Melbourne, Sydney
* Asia: Osaka, Tokyo
**To create a VXC to the IBM Direct Link Connect**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.\
If you haven't already created a Port, see [Creating a Port](/connections/creating-port).
2. Add an IBM Cloud connection for the Port.\
If this is the first connection for the Port, click the IBM Cloud tile. The tile is a shortcut to the configuration page. Alternatively, click **+Connection**, click **Cloud**, then click **IBM Cloud**.
3. Select the IBM Direct Link location where the peer will be set up with IBM Cloud and click **Next**.\
This destination should match the peer location selected in the IBM Cloud.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The speed tiers available are dependent on the selected location, and match the speeds available in IBM. Select the port speed from the drop-down list to match the selected speed in the IBM Cloud portal for the Direct Link service.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged** to remove the VLAN tagging for this connection. The untagged option limits you to only one VXC deployed on this Port. You must use untagged VLANs if you are creating a MACsec connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.\
The Cloud Details page appears.
6. Specify these IBM cloud details:
* **IBM Account ID** -- Your IBM account ID. You can get your account ID from the IBM account setting in the IBM Cloud portal.\
This is used to link the Megaport Portal and IBM Cloud portal. Confirmation for this new connection will be sent to the specified account ID in the IBM Cloud portal.
* **Customer ASN** -- Your network's autonomous system number (ASN). This can be a public or private ASN and the supported ranges are 1 - 65401, 65434 - 4201064999, and 4201066000 - 4294967294 (default is 64999).\
Excluded ranges are 65201 - 65234, and excluded values are 13884, 36351, 64512, 64513, 65100, 65500, 65516, 65519, 65521, and 65531.
* **Customer IP Address** (optional) -- The IP address space (in CIDR format) you will use on your network for peering. For private connections, this field is optional and if left blank, Megaport assigns a private /30 address. For public connections, this field is required and needs public IPs (/30) allocated by you for BGP connectivity. You must own the public IPs.
* **Provider IP Address** (optional) -- The IP address space in CIDR format assigned in the IBM network for peering. If left blank, Megaport automatically assigns a private /30 address.
7. Click **Next**.\
A summary page appears that includes a drop-down of the IBM cloud details and the monthly cost.
8. Click **Back** to make changes or click **Add VXC**.\
Once you have finished this configuration, you can configure additional VXCs or proceed through the ordering process.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
The IBM Portal Connection prompt displays. This is a reminder that you need to approve or reject the request in the IBM Cloud portal, and provides a link to the IBM Cloud portal.
Once the VXC is created and ordered in the Megaport Portal, the change is available immediately in the IBM Cloud portal. After you verify and approve the inbound IBM VXC in the IBM Cloud portal, the IBM Direct Link Connect status changes to Provisioned and the Megaport VXC is active.
* When editing a VXC in the Megaport Portal, a prompt listing the changes appears first, then the IBM Portal Connection prompt. If editing an older VXC to IBM Cloud Direct Link, a prompt appears stating that Megaport has updated API integrations, and advises you to cancel and reorder the VXC. In this situation, we recommend that you cancel and then reorder the VXC using the latest API integration.
* When terminating a VXC in the Megaport Portal, confirm the termination in the prompt that appears. The IBM Portal Connection prompt appears to remind you to cancel the service in the IBM Cloud portal also. The VXC is terminated on the Megaport side, but you must do the same in the IBM Cloud portal to fully terminate the service.
## Helpful references
* [Models for diversity and redundancy in Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-models-for-diversity-and-redundancy-in-direct-link#:~:text=IBM%20Cloud%C2%AE%20Direct%20Link,gateway%20protocol%20\(BGP\)%20schemas)
# Connecting to Latitude.sh with Megaport
Source: https://docs.megaport.com/cloud/megaport/latitude-sh/index
This help topic describes how to create a connection to Latitude.sh from a Megaport Port.
Latitude.sh is a Megaport-owned bare metal and cloud infrastructure provider. You can create a connection to Latitude.sh through the Megaport global software-defined network (SDN), bypassing the public internet for lower latency and more consistent network performance.
BGP is required for all Latitude.sh connections. To create a connection, specify an ASN, BGP password, and the prefixes to advertise. The connection becomes live after Latitude.sh approves the request.
## Prerequisites
## Creating a connection to Latitude.sh
To set up a connection to Latitude.sh with Megaport, you need to create a VXC from your Port in the Megaport Portal to the Latitude.sh location where you have provisioned your Latitude.sh services.
**To create a connection to Latitude.sh**
1. In the Megaport Portal, go to the **Services** page.
2. Select the Port you want to use.\
If you haven't created a Port, see [Creating a Port](/connections/creating-port).
3. Click **+Connection**, click **Cloud**, then click **Compute via Latitude.sh**.
4. Select the target location for your connection then click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc/).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection. The VLAN ID must be unique on this port and can range from 2 to 4093. If you don't specify a value, Megaport assigns one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.\
A summary page appears that includes the monthly cost.
7. Click **Back** to make changes, or click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
The connection becomes live after Latitude.sh approves the request.
After ordering, the connection status shows *Deployable* until it is provisioned. When Latitude.sh approves the connection and provisioning is complete, the status updates to *Configured*.
## Helpful references
* [Connecting to Latitude.sh](/portal-admin/connect-latitude)
* [Creating a Port](/connections/creating-port)
* [Creating MCR Connections to Latitude.sh](/cloud/mcr/latitude-sh)
* Latitude.sh docs
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Connecting to Oracle Cloud Infrastructure FastConnect
Source: https://docs.megaport.com/cloud/megaport/oracle/index
This help topic describes how to create a connection between Megaport and Oracle Cloud Infrastructure FastConnect.
The Oracle Cloud Infrastructure (OCI) private connection model is called FastConnect. FastConnect provides private connectivity and self-service provisioning including full API-level integration.
When connecting to the Oracle Cloud Infrastructure (OCI) through FastConnect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection. Layer 3 BGP connectivity is established directly between you and Oracle.
A common FastConnect deployment might look like this:
Oracle offers an SLA on its FastConnect connectivity but the SLA requires two FastConnect VXCs for redundancy.
You can connect to OCI through FastConnect with Megaport using the OCI console without having to switch between the Oracle and Megaport Portals. For more information, see [A simple guide: OCI and Megaport are now integrated](https://blogs.oracle.com/cloud-infrastructure/post/simple-guide-oci-megaport-now-integrated).
There are two stages involved with establishing a FastConnect connection.
* Create the FastConnect in the Oracle console with Megaport as the provider.
* Create the VXC in the Megaport Portal to connect to your FastConnect location.
## Creating the FastConnect in the Oracle console
**To create the FastConnect in the Oracle console**
1. Log in to the Oracle console and select the region from the upper-right corner.
2. Create a Compartment or select an existing Compartment to deploy these new resources.
3. Select Networking and create your Virtual Cloud Network (VCN), Dynamic Routing Gateway, and the
FastConnect.
When you create the FastConnect in the Oracle Console, you will be
provided with the OCID.
1. Copy this OCID and then log in to the Megaport Portal.
If you plan to use a private virtual circuit (private peering), you need a Dynamic Routing Gateway (DRG). Use the Oracle Cloud Infrastructure Console to set up a DRG, attach it to your VCN, and update routing in your VCN to include a route rule to send traffic to the DRG. It's easy to forget to update the route table but without the route rule, no traffic will flow.
## Creating the Megaport connection to Oracle FastConnect
**To create the Megaport connection to Oracle FastConnect**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.\
If you haven't already created a Port, see
[Creating a Port](/connections/creating-port).
2. Add a VXC connection for the Port.\
If this is the first connection for the Port, click the Oracle Cloud tile.
The tile is a shortcut to the configuration page. Alternatively, click **+Connection**, click **Cloud**, then click **Oracle Cloud**.
3. Enter your Oracle Cloud ID (OCID) in the Oracle Virtual Circuit ID field.\
The Portal verifies the OCID and displays the available port locations based on the FastConnect region. For example, if your FastConnect service is deployed in Ashburn, you only see the Ashburn FastConnect targets.
4. Select a target location for your first connection and click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Enter the same rate or up to the rate you specified in the Oracle console.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify a VLAN ID for this connection.\
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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged** to remove the VLAN tagging for this connection. The untagged option limits you to only one VXC deployed on this Port. You must use untagged VLANs if you are creating a MACsec connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.\
A summary page appears that includes the monthly cost. Click **Back** to
make changes or click **Add VXC** to move this configuration to your
cart. Once you have finished this configuration, you can configure
additional VXCs or proceed through the checkout process.
7. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
8. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
9. Click **Order Now**.
To deploy a second FastConnect (and this is recommended), create a
second FastConnect on the Oracle Console, copy the new OCID into the
Megaport Portal, and repeat these steps.
Oracle regions are independent of other regions. Each FastConnect connects to one region; connecting to multiple regions requires multiple FastConnects.
## Helpful references
* [Oracle Cloud Infrastructure Documentation: FastConnect](https://docs.cloud.oracle.com/en-us/iaas/Content/Network/Concepts/fastconnect.htm)
* [FastConnect Redundancy Best Practices](https://docs.oracle.com/en-us/iaas/Content/Network/Concepts/fastconnectresiliency.htm)
* [Oracle VCNs and Subnets](https://docs.cloud.oracle.com/en-us/iaas/Content/Network/Tasks/managingVCNs.htm)
* [FastConnect FAQ](https://www.oracle.com/cloud/networking/fastconnect-faq.html)
# Connecting to 3DS Outscale DirectLink
Source: https://docs.megaport.com/cloud/megaport/outscale/index
This help topic describes how to connect to 3DS Outscale DirectLink.
Megaport makes it easy to provision fast, secure, and private connections to 3DS Outscale Connect through our global software-defined network (SDN). Megaport is a 3DS Outscale partner providing direct private access to the 3DS Outscale infrastructure. You can quickly provision connectivity from hundreds of Megaport-enabled locations to 3DS Outscale Connect regions and 3DS Outscale Connect Points-of-Presence (PoPs) across North America, Europe, and Asia Pacific.
The benefits of direct connectivity to 3DS Outscale Connect through Megaport include:
* Secure, private connectivity throughout Megaport's redundant network infrastructure. Your traffic will not transit the public internet.
* High performance and predictability of your network.
* Improved data and operational security.
* Flexible and scalable cloud networking options.
* Consistent connectivity while scaling bandwidth to 3DS Outscale Connect. This means no downtime when you need to change your Virtual Cross Connect (VXC) speed.
* Connect to multiple regions from a single interconnection point, which uses multi-region redundancy at a fraction of the cost.
## How it works
3DS Outscale Connect consists of a physical network connection at several 3DS Outscale locations. 3DS Outscale locations reside within facilities operated by co-located data centers where Megaport is enabled.
Physical fiber connections (NNIs) at each location between Megaport and 3DS Outscale are established to 3DS Outscale routers. These physical connections are maintained between 3DS Outscale and Megaport.
Connecting to 3DS Outscale follows these general steps through the Megaport Portal:
1. Order Ports in Megaport locations of your choice. Two Ports are required for redundancy.
2. Order VXCs to 3DS Outscale. Bandwidth is available from 1 Mbps to several Gbps in 1 Mbps increments. Maximum bandwidth depends on the selected region and available Port capacity. VXCs to 3DS Outscale are established as a Layer 2 service between 3DS Outscale and the Port. One VXC from each Port is required for resilience.
3. After you deploy VXCs in the Megaport Portal, establish Layer 3 BGP peering between your routing equipment and 3DS Outscale.
DirectLink can connect private 3DS Outscale cloud services. Each VXC (DirectLink) lets you manage the bandwidth and as long as the total bandwidth of the VXCs does not exceed the size of the Port, utilization of each VXC (to the VPC) will not affect the other VPCs.
Key features:
* Connections can share bandwidth, which is managed and monitored to ensure defined network performance.
* If you connect to 3DS Outscale from a Megaport Cloud Router (MCR), the DirectLink provides access to the routing information for automatic configuration of your MCR.
* You can change the service speed without affecting the service.
* 3DS Outscale port charges are included with your Megaport order. Billing details and Megaport rates are shown as you configure the connection.
## Availability
3DS Outscale Connect is available in this location:
* Europe
* Paris (eu-west-2)
You can have only one VIF per Virtual Gateway (VGW)/DirectLink connection.
For more information about 3DS Outscale locations, see [3DS Outscale Connect](https://docs.outscale.com/en/userguide/Regions-Endpoints-and-Availability-Zones-Reference.html).
## Prerequisites
Before you create a private connection to 3DS Outscale, make sure you have:
* Your [3DS Outscale account number](https://docs.outscale.com/en/userguide/Account.html).
* Requested that 3DS Outscale remove your DirectLink quota limit.
* [OSC CLI](https://docs.outscale.com/en/userguide/Installing-and-Configuring-OSC-CLI.html) installed. OSC CLI is required to be able to confirm the DirectLink connection requests.
* A 3DS Outscale [virtual private gateway](https://docs.outscale.com/en/userguide/Managing-Your-Virtual-Private-Gateways.html) associated with your VPCs.
* The ASN for the 3DS Outscale gateway: 50624
* A Megaport Port. If you don't currently have a Port, create one following the procedure in [Creating a Port](/connections/creating-port).
## Creating a 3DS Outscale DirectLink connection
A DirectLink can connect to private 3DS Outscale cloud services. Before you deploy a 3DS Outscale DirectLink, ensure that you meet all the prerequisites above.
**To create a DirectLink connection**
1. Log in to the Megaport Portal and go to the **Services** page.\
If you don't have a Megaport account, see [Setting Up a Megaport Account](/setting-up).
2. Select the Port for the connection.
3. Add a 3DS Outscale connection for the Port.\
If this is the first connection for the Port, click the 3DS Outscale tile. The tile is a shortcut to the configuration page. Alternatively, click **+Connection**, click **Cloud**, then click **3DS Outscale**.
4. In the Select Destination Port list, select the 3DS Outscale region and the interconnection point for your connection, then click **Next**.\
You can use the Select Destination Port search field to narrow the selection.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
Match this to the VXC name on the next screen for easy mapping.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Accepted values range from 1 Mbps and can scale to several Gbps, in 1 Mbps increments. The maximum available speed depends on the selected region and service configuration. The sum of all hosted virtual VXCs to a service can exceed the Port capacity (for example, 10 Gbps, 100 Gbps, or higher) but the total aggregate will never burst beyond the Port capacity.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection. This must be a unique VLAN ID on this Port and can range from 2 to 4095. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged** to remove the VLAN tagging for this connection. The untagged option limits you to only one VXC deployed on this Port. The VLAN for the 3DS Outscale side termination will be automatically allocated and will not affect your Megaport details. You must use untagged VLANs if you are creating a MACsec connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.
7. Specify the cloud details:
* **Outscale Connection Name** (optional) -- The name of your virtual interface (VIF) that will appear in the 3DS Outscale console (Cockpit/OSC CLI). For easy mapping, use the same name for this field as you did for the VXC name on the previous page.
* **Outscale Account ID** -- The ID of the account you want to connect. You can find this value in the management section of your 3DS Outscale console (Cockpit/OSC CLI).
* **Customer ASN** -- Your network’s autonomous system number (ASN). This must be a private ASN and the supported private ASN range is 64512 - 65534. Accepts a string with leading "AS" or "ASN".
* **BGP Auth Key** (optional) -- Specify the BGP key using alphanumeric characters only. If you leave this blank, Megaport negotiates a key automatically for you with 3DS Outscale which is displayed in the Megaport Portal. The key is also displayed in the OSC CLI API call, but not in the 3DS Outscale Cockpit console.
The BGP Auth Key is generated during the ordering process when this field is left blank. It will not be displayed on the Summary page when ordering. To see the key, view the Connection Settings after the service has been deployed and is live.
* **Customer IP Address** -- The IP Address space (in CIDR format) you will use on your network for peering. For private connections, this field is optional and if left blank, Megaport assigns a private /30 address.
* **Outscale IP Address** (optional) -- The IP address space in CIDR format assigned in the 3DS Outscale VPC network for peering. If left blank, Megaport automatically assigns a private /30 address.
8. Click **Next**.\
A summary page appears that includes the monthly cost. Click **Back** to make changes or click **Add VXC** to move this configuration to your cart. Once you have finished this configuration, you can configure additional VXCs or proceed through the checkout process.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Megaport will deploy the connection. The deployment can take several minutes.
## Accepting the virtual interface connection
Once you have deployed the VXC, you will accept the virtual interface in 3DS Outscale using the OSC CLI (API calls).
Currently, you cannot accept virtual interface connection requests in 3DS Outscale Cockpit v1. This is only possible through the API.
For more information about the next procedure, see the [3DS Outscale documentation](https://docs.outscale.com/en/userguide/Accepting-a-Hosted-Private-Virtual-Interface.html).
**To review and accept the virtual interface connection**
1. Go to the OSC CLI.
2. Enter this command to show the DirectLink request:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
%osc-cli directlink DescribeVirtualInterfaces --profile "default"
{
"virtualInterfaces": [
{
"virtualInterfaceState": "confirming",
"authKey": "QnfhEsgJ1MDPqiRiRbVz",
"asn": 65000,
"vlan": 3206,
"bgpPeers": null,
"customerAddress": "169.254.6.22/30",
"ownerAccount": "XXXXXXXXXXXX",
"connectionId": "dxcon-a7c2eb08",
"addressFamily": null,
"virtualGatewayId": null,
"virtualInterfaceId": "dxvif-b2e8dcda",
"amazonSideAsn": null,
"routeFilterPrefixes": null,
"location": "PAR4",
"directConnectGatewayId": null,
"customerRouterConfig": null,
"amazonAddress": "169.254.6.21/30",
"virtualInterfaceType": "private",
"virtualInterfaceName": "DirectLink VXC eu-west-2"
}
],
"requestid": "5ad8af40-c0af-4deb-85db-7a8ae5481d18"
}
```
You can also click the DirectLink name to view the virtual interface in Cockpit:
Next, you will ensure that you have a Virtual Private Gateway (VGW) to connect your VIF to.
3. In Cockpit, choose VPC menu > Virtual Private Gateways.
If no VGW is available, see the [3DS Outscale documentation](https://docs.outscale.com/en/userguide/Creating-a-Virtual-Private-Gateway.html) to learn how to create one in Cockpit or the OSC CLI.
4. To accept the VIF creation request, take note of the `virtualInterfaceId` from step 2 and the `virtualGatewayID` from step 3 and enter this command:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
% osc-cli directlink ConfirmPrivateVirtualInterface --profile "default" \
--virtualGatewayId "vgw-bc6932d6" \
--virtualInterfaceId "dxvif-b2e8dcda"
{
"virtualInterfaceState": "pending",
"requestid": "9b66a7e8-a02a-45ba-9a21-c01058273190"
}
```
Next, you will verify that the status is now *available* for the VIF.
5. Click the DirectLink name in the Virtual Interfaces screen.
6. Verify the VIF status in the Details screen.
## Redundancy
To establish full redundancy between your data center and 3DS Outscale, we recommend deploying redundant VXCs between two different 3DS Outscale locations with two corresponding Ports at each Megaport-enabled data center.
### Redundant solution
### Fully redundant solution
## Updating the service bandwidth
You can scale the service speed up to the 3DS Outscale Connect speed rate at any time. To change the 3DS Outscale Connect speed, edit the VXC and change the speed.
## 3DS Outscale Frequently Asked Questions (FAQs)
### Are there any 3DS Outscale port fees?
3DS Outscale doesn't charge for ingress or egress data transfer.
### What services are available using 3DS Outscale?
3DS Outscale offers private cloud with computing power, storage solutions, network infrastructure, and virtual private cloud.
### What is the 3DS Outscale DirectLink solution designed for?
With 3DS Outscale DirectLink, you can link your company network to your private 3DS Outscale Virtual Private Cloud network without creating a VPN tunnel through the internet. This gives you a faster, more stable connection with guaranteed bandwidth.
### What if I'm not located within a 3DS Outscale-enabled facility?
You do not have to be located within the same facility as 3DS Outscale. Just connect to Megaport anywhere globally and establish a VXC to the closest 3DS Outscale location of your choice. Each VXC is carried across Megaport's redundant network to 3DS Outscale.
### How do I establish redundancy between my data center and 3DS Outscale?
We recommend establishing redundant VXCs between two different 3DS Outscale regions or availability zones within a region with two corresponding ports at each Megaport-enabled data center.
### Are my bandwidth speeds set?
You can define the bandwidth in 1 Mbps increments, and it can scale to several Gbps. Higher speeds might be available depending on the location and Port capabilities.
### Does 3DS Outscale support public or private ASNs?
3DS Outscale supports private ASNs. If you are using a private ASN, it must be between 64512 and 65535. The use of public ASNs is available upon request.
## Helpful references
* [3DS Outscale Documentation](https://docs.outscale.com/en/userguide/Home.html)
* [3DS Outscale DirectLink](https://en.outscale.com/networks/directlink/#:~:text=3DS%20OUTSCALE%20offers%20DirectLink%2C%20a,or%20third%2Dparty%20network%20provider.)
* [Installing and Configuring OSC CLI](https://docs.outscale.com/en/userguide/Installing-and-Configuring-OSC-CLI.html)
* [DirectLink API Documentation - VIF Creation](https://docs.outscale.com/directlink#directlink-api-virtual-interfaces)
* [Hosted Private Cloud Pricing](https://en.outscale.com/pricing/how-pricing-works/)
* [3DS Outscale Compatible Virtual Machine Pricing](https://en.outscale.com/pricing/)
# OVHcloud Connect Direct
Source: https://docs.megaport.com/cloud/megaport/ovhcloud/direct
This help topic describes how to create a direct connection to OVHcloud Connect.
An OVHcloud Connect Direct connection is at Layer 2. The connection is transparent to the Ethernet protocol and simplifies the way you connect your data center’s campus network to your OVHcloud vRack private network. The virtual local area networks (VLANs) are the same in your data center and within the OVHcloud data centers.
The configuration requires a physical cross connect between a Port on the Megaport network and a 1 Gbps or 10 Gbps OVHcloud Connect Direct port, and a Virtual Cross Connect (VXC) between the Port connected to the Connect Direct port and a second Megaport Port.
**To create an OVHcloud Connect Direct connection**
1. Log in to the [OVHcloud website](https://www.ovh.com/world/solutions/ovhcloud-connect/) using your OVHcloud credentials and order each connection.\
Once your order has been processed, your billing contact will receive a summary email including the configuration details needed for the OVHcloud support team to set up your OVHcloud Connect Direct solution.
2. Download the Letter of Authorization (LOA) from OVHcloud.
3. Provision a Megaport Port in the same data center as the OVHcloud Connect Direct port.
4. Contact your Megaport Account Manager to set up a physical cross connect from the OVHcloud Connect Direct port to the Port on the Megaport network.
5. Provide the OVHcloud LOA to Megaport.
6. Configure a private VXC to connect the Port attached to the OVHcloud Connect Direct port to a second Port in a different data center.
For OVHcloud Connect port installation specifications, see [OVHcloud Connect Service Provisioning](https://docs.ovh.com/gb/en/ovhcloud-connect/occdedicated-delivery/).
## Helpful references
* [OVHcloud Connect Layer 2 Design](https://docs.ovh.com/gb/en/ovhcloud-connect/layer2/#connection-mode-details)
* [OVHcloud Connect Layer 3 Design](https://docs.ovh.com/gb/en/ovhcloud-connect/layer3/)
* [OVHcloud Connect Service Provisioning](https://docs.ovh.com/gb/en/ovhcloud-connect/occdedicated-delivery/)
* [FAQ | OVH Guides](https://docs.ovh.com/gb/en/ovhcloud-connect/occdedicated-faq/)
# Connecting to OVHcloud Connect
Source: https://docs.megaport.com/cloud/megaport/ovhcloud/index
This help topic describes how to connect to OVHcloud Connect.
Megaport makes it easy to provision fast, secure, and private connections to OVHcloud Connect through our global software-defined network (SDN). Megaport is an OVHcloud partner providing direct private access to the OVHcloud infrastructure. You can quickly provision connectivity from hundreds of Megaport-enabled locations to OVHcloud Connect regions and OVHcloud Connect Points-of-Presence (PoPs) across North America, Europe, and Asia Pacific.
The benefits of direct connectivity to OVHcloud Connect through Megaport include:
* Secure, private connectivity throughout Megaport’s redundant network infrastructure. Your traffic will not transit the public internet.
* High performance and predictability of your network.
* Improved data and operational security.
* Flexible and scalable cloud networking options.
* Consistent connectivity while scaling bandwidth to OVHcloud Connect. This means no downtime when you need to change your Virtual Cross Connect (VXC) speed.
* Connect to multiple regions from a single interconnection point, which uses multi-region redundancy at a fraction of the cost.
## How it works
OVHcloud Connect consists of a physical network connection at several OVHcloud locations. OVHcloud locations reside within facilities operated by co-located data centers where Megaport is enabled.
Physical fiber connections (NNIs) at each location between Megaport and OVHcloud are established to OVHcloud routers. These physical connections are maintained between OVHcloud and Megaport.
Connecting to OVHcloud follows these general steps through the Megaport Portal:
1. Order Ports in Megaport locations of your choice.\
Two Ports are required for redundancy.
2. Order VXCs to OVHcloud. Bandwidth is available in increments starting at 200 Mbps. Available speed options might vary by location and Port capabilities.\
VXCs to OVHcloud are established as a Layer 2 service between OVHcloud and the Port. One VXC from each Port is required for resilience.
3. After you deploy VXCs in the Megaport Portal, establish Layer 3 BGP peering between your routing equipment and OVHcloud.
## Availability
OVHcloud Connect is available in these locations:
* Europe
* Frankfurt
* London
* Paris
You can connect to multiple regions from a single interconnection point (which lets you use multi-region redundancy at a fraction of the cost).
For more information about OVHcloud locations, see [OVHCloud Connect](http://ovh.com/world/solutions/ovhcloud-connect/).
## Prerequisites
Before you begin, notify OVHcloud. If you are an existing OVHcloud customer, contact your OVHcloud Account Manager and establish an agreement for OVHcloud services. If you are a new customer, you can order from the OVHcloud Connect website. OVHcloud will provide you with a service key that is unique for each cloud peering location interface: one for the primary and one for the secondary cloud peering location interface. The key includes the OVHcloud VLAN ID, speed, and OVHcloud location.
After you notify OVHcloud, ensure you have a Port on the Megaport network. The Port is your interface to the Megaport network, and you will need to deploy a Port wherever you want to direct traffic. For more information, see [Creating a Port](/connections/creating-port).
## Setting up OVHcloud Connect
The easiest way to create a connection between Megaport and OVHcloud is with a service key. A service key includes the essential configuration details for your business and automates much of the configuration process. After obtaining the service key from OVHcloud, you can create a VXC from the Port to OVHcloud Connect.
**To request a connection to OVHcloud in the Megaport Portal**
1. Contact OVHcloud to obtain a service key.
When you use the service key created by OVHcloud, you are responsible for any VXC charges.
2. In the Megaport Portal, go to the **Services** page.\
If you don’t have a Megaport account, see [Setting Up a Megaport Account](/setting-up).
3. Select the Port for the connection and click **+Connection**.
4. Click **Enter Service Key** and click **Next**.
5. Enter the service key provided by OVHcloud in the **Megaport Service Key ID** field.
Megaport validates the key. Data including VLAN ID, speed, and OVHcloud location are included in the key and populate automatically. For more information about using a service key, see [Setting up Service Keys](/marketplace/service-keys).
6. Click **Next**.
7. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Enter a name for the VXC using the label provided by OVH.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit for the VXC is capped at the maximum allowable based on the OVHcloud Connect service key speed.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** -- The VLAN for this connection that you will receive through the Port.\
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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged**. This selection removes the VLAN tagging for this connection but also means that only one VXC can be deployed on this Port.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
8. Click **Next**.\
A summary page appears that includes the monthly cost.
9. Click **Add VXC** to move this configuration to your cart.
10. Repeat these steps to provision your secondary OVHcloud interface.
11. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
12. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
13. Click **Order Now**.
Once the VXC connection is deployed to OVHcloud, a single VLAN is assigned from your Megaport Portal account, with Layer 3 networking routing established using BGP between your physical network device and OVHcloud. Connections are private peering types, and will use private IPv4 addresses.
## Redundancy
To establish full redundancy between your data center and OVH, we recommend deploying redundant VXCs between two different OVHcloud locations with two corresponding Ports at each Megaport-enabled data center.
### Redundant solution
### Fully redundant solution
## Updating the service bandwidth
You can scale the service speed up to the OVHcloud Connect speed rate at any time. If you require additional capacity, you must place an order for a new connection speed on the website.
To change the OVHcloud Connect speed, you must delete the Cloud Connect and VXC connections, and then recreate them.
## OVHcloud Frequently Asked Questions (FAQs)
### Are there any OVHcloud port fees?
OVHcloud Connect doesn’t charge for data transfer. Customers pay a flat, auto-renewable monthly rate.
### What services are available using OVHcloud?
OVHcloud offers Private Cloud based on VMware platform, Bare Metal servers, Public Cloud based on Openstack and services as Kubernetes Managed, and Databases as a Service.
### What if I’m not located within an OVHcloud Point of Presence (PoP)?
You don’t have to be located within the same facility as OVHcloud; you can establish a VXC to the closest OVHcloud Connect location of your choice. Each VXC is carried across Megaport’s redundant network to OVHcloud.
### Does OVHCloud Connect support public or private ASNs?
OVHcloud Connect supports public and private autonomous system numbers (ASNs). If you are using a public ASN, you must own it. If you are using a private ASN, it must range from 64512 to 65535. AS path prepending does not work if you are using a private ASN for your public VIF. When you place your order, you can specify your preference for private or public ASNs. The OVHcloud connection is private, but customers can peer with their private or public ASN and an OVHcloud private ASN of their choosing.
## Helpful references
* [OVHcloud Connect](https://www.ovh.com/world/solutions/ovhcloud-connect/)
* [Hybrid and Multi-Cloud Solutions](https://www.ovhcloud.com/en/enterprise/solutions/datacentre-extension-cloud/hybrid-multi-cloud/)
* [Hosted Private Cloud Prices](https://www.ovh.com/world/private-cloud/options/)
# Connecting to Salesforce Express Connect
Source: https://docs.megaport.com/cloud/megaport/salesforce/index
This help topic describes how to create a connection between Megaport and Salesforce Express Connect.
Salesforce Express Connect lets you access Salesforce applications and
services directly with a private, dedicated connection. When you create
a Salesforce Express Connect through the Megaport Portal:
* Express Connect is delivered as a Layer 3 routed service.
* You access Salesforce services using public IPs and are required to
run BGP to receive Salesforce routes.
* Megaport allocates a /31 public IP range for each Salesforce
peering.
Express Connect offers two IP addressing options:
* You can source NAT your LAN traffic to use the /31 public IP space
provided by Megaport.\
\--*or*--
* You can advertise your own public IP address space to Salesforce.
(Salesforce will not accept RFC1918 routes.)
Deployment considerations:
* **Provisioning** -- One Virtual Cross Connect (VXC) provisions two
logical connections to Salesforce using a Megaport Cloud Router
(MCR). Salesforce has redundant routers which provide guaranteed
uptime for both service locations.
* **Timeframe** -- Salesforce can take up to 2 business days for
approval once a VXC is deployed from the Portal.
* **IP Addresses and ASN** -- Customers can use their own publicly
registered IP space or Megaport will allocate a public /31 for the
end user to peer directly with Salesforce. RFC 1918 private space is
not allowed. Private and public ASNs are accepted.
* **Internet Backup** -- Although we always recommend two
Ports for redundancy, an Express Connect over Megaport can be
used for the primary connection to Salesforce and if you use
publicly routed IP space and the single Port fails,
routing to Salesforce can revert to the public Internet.
This image shows a common Express Connect deployment:
**To create a connection to Salesforce Express Connect**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.\
If you haven't already created a Port, see
[Creating a Port](/connections/creating-port).
2. Add a VXC connection for the Port.\
If this is the first connection for the Port, click the Salesforce
tile. The tile is a shortcut to the configuration page.
Alternatively, click **+Connection**, click **Cloud**, then click **Salesforce**.
3. Select Salesforce as the provider.
4. Select your destination Port and click **Next**.\
You can use the Select Destination Port search field to narrow the selection. You can also filter by diversity zone.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. You can select any value starting from 1 Mbps, with maximum speeds depending on location and service availability.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify a VLAN ID for this connection.\
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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Alternatively, you can select **Untagged** to remove the VLAN tagging for
this connection. The untagged option limits you to only one VXC
deployed on this Port.
You must use untagged VLANs if you are creating a MACsec connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.
7. Specify the connection details for the Salesforce service:
* **ASN** -- Enter a private or public ASN.
* **BGP Password** (optional) -- Specify the BGP Auth Key.
* **Prefixes** -- Enter prefixes to announce to Salesforce -- RIR
assigned IPv4 address ranges only. If you do not have public
IP ranges, you can source NAT to the /31s IP provided by
Megaport. If you are going to use the /31s IP provided by
Megaport, you can leave this field blank.\
Note: RFC 1918 space is not permitted.\
Once configured, you cannot add new prefixes to the VXC.
8. Click **Next**.\
A summary page appears that includes the monthly cost. Click **Back** to
make changes or click **Add VXC** to move this configuration to your
cart. Once you have finished this configuration, you can configure
additional VXCs or proceed through the checkout process.
After you complete the checkout process, Salesforce can take up to 2
business days to approve the connection request. The VXC status will be
*Deployable* until Salesforce accepts the connection.
When Salesforce accepts the request, two logical and redundant
connections are created from Salesforce.
You can view and edit the details of your SEC connection by clicking the
VXC and selecting Details.
9. Configure one BGP peering connection using the /31 IP addresses
assigned by Megaport (outlined in red in the image below).\
It is important to configure the IP address that has been assigned
to you for the local interface as it has been automatically
whitelisted on the SEC side. You will still be able to configure
your own public prefixes for advertising across this link using the
Megaport specific peering IP address.
## Helpful references
* [Salesforce Express Connect Product Page](https://www.salesforce.com/campaign/salesforce-express-connect/)
# Connecting to SAP HANA Enterprise Cloud
Source: https://docs.megaport.com/cloud/megaport/sap/index
This help topic describes how to create a connection between Megaport and SAP HANA Enterprise Cloud.
Megaport makes it easy to provision fast, secure, and private
connections between your data center and the SAP HANA Enterprise Cloud
with SAP Cloud Peering.
Through private connectivity that bypasses the public internet, enterprises benefit from:
* Higher network performance, consistency, and predictability
* Streamlined and accelerated workloads and data migration
* Improved data and operational security
With SAP Cloud Peering through Megaport, you can connect to the SAP HANA Enterprise Cloud.
With an interconnection, you can use Megaport to reach additional cloud service providers, including Amazon Web Services, Microsoft Azure, Google Cloud Platform, and others.
## How SAP Cloud Peering Service works
SAP consists of a physical network connection at several SAP Points-of-Presence (PoPs) around the world. These PoPs reside within facilities operated by co-located data centers where Megaport is enabled.
Physical fiber connections (NNIs) at each location between Megaport and
SAP are established on SAP HEC WAN routers (a minimum of two). These
physical connections are maintained between SAP and Megaport.
You can purchase 10 Gbps Ports onto the Megaport network. Higher-capacity Ports, for example, 100 Gbps or higher, are available depending on location and service availability. Megaport recommends two Ports for resilience.
Through the Megaport Portal, you can order Virtual Cross Connects (VXCs) to SAP in increments of 100 Mbps up to 2 Gbps (and speeds greater than 2 Gbps are available on request).
VXCs to SAP Cloud Peering are established as a Layer 2 VLAN through Megaport, with Layer 3 between the customer device and SAP.
## Availability
SAP Cloud Peering is available in these locations:
* Asia Pacific
* Sydney, Australia Equinix SY3
* Europe
* Frankfurt, Germany Equinix FR5
* North America
* Ashburn, US Digital Realty ASH1
* Sterling, US Cyxtera DC 1/2/3
* Santa Clara, US vXchnge
You can connect to multiple regions from a single interconnection point (which lets you use multi-region redundancy at a fraction of the cost).
For more information, see the [provisioning guide in the SAP Help Portal](https://help.sap.com/doc/36c625027bd245818ac46998669c639f/ALL/en-US/SAP_Cloud_Peering_Customer_Guide.pdf).
## Setting up SAP Cloud Peering Service
Setting up SAP Cloud Peering requires two stages: first, open a ticket
with SAP to set up your SAP cloud peering service and configuration, and
second, create a connection from Megaport to SAP.
**To set up SAP Cloud Peering with SAP**
1. Contact your SAP Account Manager or cloud advisory architect and
establish a HEC agreement that covers SAP Cloud Peering services.
2. Open a SPC ticket and provide the following configuration details.
| **Required Information** | **Details** |
| :- | :- |
| Customer | HEC customer name and CID |
| Provider | Megaport |
| Location | Sydney, Frankfurt, Sterling, Ashburn, or Santa Clara |
| Solution | HEC |
| Bandwidth | 100 Mbps up to 2 Gbps, or higher |
| Customer Contact | Contact Details |
| 2 x BGP peering networks | 10.11.12.0/30, 10.11.12.4/30, or similar |
| Customer side IP1 & SAP side IP1 | 10.11.12.1/30 & 10.11.12.2/30, or similar |
| Customer side IP2 & SAP side IP2 | 10.11.12.5/30 & 10.11.12.6/30, or similar |
| MD5 secret for BGP | \< md5-hash-key > |
| ASN of customer BGP side | For example, 65200 is HEC01 |
| Customer side peering ASN | Public or private ASN |
| SAP side peering ASN | Public or private ASN |
When configured, SAP provides a unique Megaport service key for each
cloud peering location interface: one for the primary and one for the
secondary cloud peering location interface. When you use the service key created by SAP, you pay for the VXC charges.
**To set up SAP Cloud Peering with Megaport**
1. Log in to the Megaport Portal.
2. If you are not already on the Megaport network, create a 1
Gbps or 10 Gbps Port, or create an MCR.
3. Add a VXC connection for the Port or MCR.\
If this is the first connection for the Port or MCR, click the SAP
tile. The tile is a shortcut to the configuration page.
Alternatively, click **+Connection**, click **Cloud**, then click **SAP**.
4. Enter the service key provided by SAP and click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Name the VXC with the label provided by SAP (for example CID-1234567890).
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. This populates automatically based on the rate defined with the service key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** -- This populates automatically based on the service key.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.\
A summary page appears that includes the monthly cost. Click **Add VXC** to move this configuration to your cart.
7. Repeat these steps to provision your secondary SAP Cloud Peering interface.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
## Resiliency to SAP
By default, SAP provides a primary and secondary interface. For maximum
resiliency, we recommend provisioning two Ports or MCRs in
separate data centers. VXCs from Megaport correspond to the two SAP WAN
router connections.
## Updating the Service
You define your speeds at the time of signing your agreement with SAP.
If you need to change the speed, work with your SAP Account Manager to
define your new speed and then update the VXC configuration in the
Megaport Portal with the new speed.
Speed changes require approval from SAP. SAP accepts or rejects incoming
speed change requests based on the contracted agreement. Speed changes
do not affect network traffic.
## SAP Frequently Asked Questions (FAQs)
### Does SAP HANA Enterprise Cloud offer BYOIP?
Yes, SAP HANA Enterprise Cloud lets you bring your own IP address.
### What if I'm not located within an SAP cloud peering enabled facility?
You don't have to be located within the same facility as SAP. You can establish a VXC to the closest SAP location of your choice. Each VXC is carried across the Megaport redundant network to SAP.
### Are my bandwidth speeds set?
Yes, you set your speeds when you sign your agreement with SAP. Speeds are set to 100 Mbps, in increments of 100 Mbps up to 2 Gbps (and speeds greater than 2 Gbps are available on request).
### Does SAP support public or private ASNs?
SAP supports both private and public ASNs.
### Can I use SAP Cloud Peering to connect to SAP HEC running on other cloud platforms?
No, SAP Cloud Peering is only for SAP Direct solutions. When SAP HEC is running on other cloud platforms, use their private connectivity option through Megaport. For example, for SAP HEC on AWS use Direct Connect; for Azure, use ExpressRoute; and for GCP, use Partner Interconnect.
# Integrating Megaport with SAP on AWS
Source: https://docs.megaport.com/cloud/megaport/sap/sap-aws
This help topic describes how to integrate Megaport and SAP on AWS.
You can use Megaport to create an AWS Direct Connect Layer 2 connection
between your on-premises or colocation-based infrastructure and your SAP
environment on AWS. You can also use Direct Connect to connect to a
cloud-only instance of SAP on AWS.
Before you begin, ensure that you have created a Megaport connection, or Port. After you create the Port, you can connect a Virtual Cross Connect (VXC) from the Port to the virtual gateway associated with the AWS VPC infrastructure. A VXC is a point-to-point Ethernet connection
between an A-End (your Port) and a B-End (in this case, your SAP on AWS instance).
If you aren't a Megaport customer, you can create a 10 Gbps, 100 Gbps, or higher Port in one of our global [data centers/Points of Presence](https://www.megaport.com/megaport-enabled-locations/). If your company isn't located in one of our PoPs, you can procure a last mile circuit to one of the sites to connect to Megaport. [Contact Megaport](https://www.megaport.com/contact/) for more information.
If you require a Port in a different location to physically separate this solution from other existing traffic traversing your Ports, we recommend that you [create a new one](/connections/creating-port) before proceeding.
**To integrate Megaport with SAP on AWS**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.
If you haven't already created a Port, see [Creating a Port](/connections/creating-port).
2. Add an AWS connection for the Port.
If this is the first connection for the Port, click the AWS tile. The tile is a shortcut to the configuration page. Alternatively, click **+Connection**, click **Cloud**, then click **AWS**.
3. For AWS Connection Type, click **Hosted VIF** or **Hosted Connection** and click **Next**.
For this example, you will click **Hosted VIF**.
Next, create a new VXC.
4. In the Select Destination Port list, select the AWS region and the interconnection point for your connection and click **Next**.\
You can use the Select Destination Port search field to narrow the selection. You can also filter by diversity zone.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
Match this to the VXC name on the next screen for easy mapping.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Accepted values start at 1 Mbps and scale in 1 Mbps increments. Maximum available speed depends on location and service availability. Note the sum of all hosted virtual VXCs to a service can exceed the Port capacity (1 or 10 Gpbs) but the total aggregate will never burst beyond the Port capacity.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection.\
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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.
7. Specify the cloud details.
* **Type** -- This refers to your destination within the AWS cloud infrastructure, either Public or Private resources. For this example, choose Private.
* **AWS Connection Name** -- This is a text field and will be the name of your virtual interface that appears in the AWS console. For easy mapping, use the same name for this field as you did for the VXC name on the previous screen.
* **AWS Account ID** -- This is the ID of the account you want to connect. You can find this value in the Account Details section of your AWS console.
* **Customer ASN** -- Your network's autonomous system number (ASN). For Private Direct Connects, this must be a private ASN and the supported private ASN range is 64512 - 65535.
* **BGP Auth Key** (optional) -- Specify the BGP key. If you leave this blank, Megaport negotiates a key automatically for you with AWS which will be displayed in the Megaport Portal. The key is not displayed in the AWS console.
The BGP Auth Key is generated during the ordering process when this field is left blank. It will not be displayed on the Summary page when ordering. To see the key, view the Connection Settings after the service has been deployed and is live.
* **Customer IP Address** -- The IP Address space (in CIDR format) you will use on your network for peering. For private connections, this field is optional and if left blank, Megaport assigns a private /30 address.
* **Amazon IP Address** -- The IP address space in CIDR format assigned in the AWS VPC network for peering. For private connections, this field is optional and if left blank, Megaport automatically assigns a private /30 address. For public connections, this field is required and needs public IPs (/30) allocated by you for BGP connectivity. You must own the public IPs.
8. Click **Next**.
9. Click **Add VXC**.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
13. Connect the new VXC to the SAP on AWS instance.
In approximately 2 minutes, log in to your AWS account. The VIF will appear in your Direct Connect under Virtual Interfaces. Accept the VIF and attach it to either a Virtual Gateway (VGW) or a Direct Connect Gateway (DGW), depending on your particular solution's design.
## Redundancy
To achieve redundancy for the connectivity portion of this solution, you can establish additional VXCs to the AWS environment. For additional physical redundancy, you can implement the VXCs on separate Ports.
AWS Hosted Virtual Interfaces (Hosted VIF) do not support diversity zones. To ensure connection diversity for Hosted VIFs, create VXCs to two destination ports in different data centers, instead of two ports in separate diversity zones.
## Background information
### Planning for deployment of SAP on AWS
SAP on AWS can be operated as a hybrid model with on-premises (global) and cloud resources working in tandem or entirely as a cloud-based solution.
This image shows a hybrid solution showing the QAS, DEV, and SAP test, training and Sandbox environment in the AWS cloud. As shown here, the VPC can connect to a wide array of AWS resources. The on-premises infrastructure is connected to the AWS cloud via a Direct Connect Layer 2 connection, enabled through Megaport.
## Helpful references
For more information about how to migrate, implement, configure, and operate SAP solutions on AWS:
* [SAP on AWS Technical Documentation](https://aws.amazon.com/sap/docs/)
* [Get Started with SAP on AWS](https://aws.amazon.com/sap/get-started/)
* [SAP on AWS Implementation and Operations Guide](https://d1.awsstatic.com/enterprise-marketing/SAP/SAP_on_AWS_Implementation_Guide.pdf)
* [SAP on AWS High-Availability Guide](https://d0.awsstatic.com/enterprise-marketing/SAP/sap-on-aws-high-availability-guide.pdf)
# Integrating Megaport with SAP on Azure
Source: https://docs.megaport.com/cloud/megaport/sap/sap-azure
This help topic describes how to integrate Megaport and SAP on Azure.
You can use Megaport to implement an ExpressRoute Layer 2 connection
between your on-premises or colocation-based infrastructure and your SAP
on Azure instance. You can also use ExpressRoute to connect to a
cloud-only instance of SAP on Azure.
Before you begin, ensure that you have created a physical connection, or Port. After you create a Port, you will connect a Virtual Cross Connect (VXC) from the Port to the virtual gateway associated with the Azure VNet infrastructure. A VXC is a point-to-point Ethernet connection between an A-End (your Port) and a B-End (in this case, your SAP on Azure instance).
If you aren't a Megaport customer, you can create a 10 Gbps, 100 Gbps, or higher Port in one of our global [data centers/Points of Presence](https://www.megaport.com/megaport-enabled-locations/). If your company isn't located in one of our PoPs, you can procure a last
mile circuit to one of the sites to connect to Megaport. [Contact Megaport](https://www.megaport.com/contact/) for more information.
If you require a Port in a different location to physically separate this solution from other existing traffic traversing your Ports, we recommend that you [create a new one](/connections/creating-port) before proceeding.
This high-level image shows Megaport connectivity into an SAP Netweaver on Azure solution:
You can achieve redundancy for the connectivity portion of this solution
by deploying additional VXCs to the Azure environment. This image shows
how you can achieve additional physical redundancy if the VXCs are
implemented on separate Ports:
## Prerequisites
Before you begin, you must have the following:
* **A Port** -- If you haven't already created a Port, see [Creating a Port](/connections/creating-port). You will deploy a connection from the Port to the SAP on Azure instance using a VXC.
* **An ExpressRoute Service Key** -- Create a service key from your Azure portal by following the steps in the [Azure documentation](https://learn.microsoft.com/en-us/azure/expressroute/expressroute-howto-circuit-portal-resource-manager#create). Ensure that you choose Megaport as the Provider in the Create ExpressRoute Circuit window (Step 2 in the Azure documentation).
To check the latency and price of connecting to a particular Azure Partner location, start the procedure to [add a connection to Microsoft Azure](#azure-vxc) but instead of providing a **Microsoft Azure Service Key**, click **View all Azure Partner locations**. You can proceed to the Connection Details page without a service key and review the pricing of the selected port. To place an order for a Microsoft Azure connection, you need to provide a service key.
**To integrate Megaport with SAP on Azure**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.
2. Add an Azure connection for the Port.
If this is the first connection for the Port, click the Microsoft Azure tile. The tile is a shortcut to the configuration page. Alternatively, click **+Connection**, click **Cloud**, then click **Microsoft Azure**.
3. Add the ExpressRoute service key into the **Microsoft Azure Service Key** field.
The Portal verifies the key then displays Primary and Secondary Azure on-ramps based on the ExpressRoute region. For more information about adding a redundant connection, see [Redundancy](#redundancy).
4. Choose the Primary option and click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. This value will be auto-populated with information from the Service Key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** -- Specify an unused VLAN ID for this connection. This is the S-Tag, or outer tag, associated with the Port that transparently carries the inner C-Tags for ExpressRoute. This VLAN ID must be a unique ID on this Port and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
Megaport delivers ExpressRoute services to Microsoft ports using Q-in-Q. For network devices that do not support Q-in-Q, you can select **Untagged** for the A-End VLAN. Untagging removes the VLAN tag for the outer connection (S-Tag), and delivers the three inner tags (C-Tags) natively as 802.1Q VLANs. Be aware that using an untagged VLAN limits that VXC to one Port. Because you cannot deploy any other VXCs on the Port, such as a secondary ExpressRoute VXC, we don't recommend this workaround as a long-term solution.
You must use untagged VLANs if you are creating a MACsec connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.
7. Review the details and click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
You have now created a Layer 2 connection into your Azure infrastructure.
11. Connect the new VXC to the SAP on Azure instance.
Log in to your Microsoft Azure portal. Specify the AS number, VLAN ID, and Primary and Secondary IP subnets for your Primary and Secondary BGP connections into your Azure infrastructure.
Microsoft Azure requires that you use BGP to connect between your on-premises environment and your Azure infrastructure.
For more information about setting up Microsoft Peering and Private Peering from your Azure console, see [Create and modify peering for an ExpressRoute circuit](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-routing-portal-resource-manager).
## Redundancy
A second VXC connection into your Azure infrastructure is required for the setup to qualify for Microsoft Azure’s [availability SLA](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services). When you paste your Microsoft Azure service key into the appropriate field, choose the **Secondary** on-ramp location (the **Primary** on-ramp location will be grayed out and unavailable).
At this point, you will have created the second Layer 2 connection from your Megaport to your Azure infrastructure and your work in the Megaport Portal is complete.
## Background information
### Planning for deployment of SAP on Azure
You can run SAP applications on Azure Virtual Machines (VMs) and bare metal instances as is the case with SAP Hana on Azure (large instance). SAP applications on VMs offer fast deployment of compute and storage as opposed to the relatively long process of procuring and installing equipment for premise-based installations. This can be on-premises, connected to a cloud solution, or run entirely as a cloud solution. Dividing the same SAP system between an on-premises and cloud infrastructure is not supported.
### SAP on Azure Virtual Machines
SAP services such as NetWeaver, Business One, and HANA can run on Azure VMs, storage, and network. To use these services efficiently, it’s important to understand the sizes and capacities of the VMs in terms of vCPU, memory, and associated network and storage bandwidth. You will need adequate resources to ensure the performance of the SAP applications you are using.
The VMs are based on Hyper-V Virtual Hard Drives (VHD) that can run various operating systems as guest OSs. You can find details on [Linux](https://docs.microsoft.com/en-us/azure/virtual-machines/linux/sizes)
and [Windows](https://docs.microsoft.com/en-us/azure/virtual-machines/windows/sizes) VM sizes on the Microsoft website.
There are two storage types associated with Azure VMs: non-persistent (volatile) and persistent. Microsoft Azure offers Standard and Premium Storage tiers; the Premium Storage tier delivers better I/O latency, better throughput, and less variability in I/O latency. For more information about Premium Storage, see [Azure Premium Storage, now generally available](https://azure.microsoft.com/en-us/blog/azure-premium-storage-now-generally-available-2/).
### SAP HANA (large instance)
SAP HANA (large instance) is a special solution for large enterprise customers that allows for the implementation of SAP HANA on bare metal servers that are dedicated to you. This solution removes any potential performance issues that might be associated with a shared multi-tenant environment. You have options ranging from 36 Intel CPU cores with 768 GB of memory to 480 Intel CPU cores with 24 TB of memory. Note that the bare metal servers are only designated to run the SAP HANA, while the workload middle layer will still operate on VMs.
The isolation of customer resources for the networking, storage, and servers are met through tenants. The bare metal solution of SAP on Azure is Tailored Datacenter Integration (TDI) certified.
## Helpful references
* [SAP Solutions on Azure](https://azure.microsoft.com/en-us/solutions/sap/azure-solutions/) -- How to migrate, implement, configure, and operate SAP solutions on Azure
* [SAP on Azure: Planning and Implementation Guide](https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/planning-guide) -- Additional planning and implementation guides for SAP NetWeaver on Azure VMs
* [SAP Business One on Azure Virtual Machines](https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/business-one-azure) -- How to migrate, implement, configure, and operate SAP solutions on Azure
* [What is SAP HANA on Azure (Large Instances)?](https://docs.microsoft.com/en-us/azure/virtual-machines/workloads/sap/hana-overview-architecture?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json) -- More information on the large instance solution
# Integrating Megaport with SAP on Google Cloud
Source: https://docs.megaport.com/cloud/megaport/sap/sap-google
This help topic describes how to integrate Megaport and SAP on Google Cloud.
You can create a network connection from your physical Port to your SAP environment on Google with Virtual Cross Connects (VXCs) and Google Partner Interconnect. You can also use Partner Interconnect to connect to a cloud-only instance of SAP on Google.
If you already have a physical Port, you can add a new VXC to your SAP on Google instance through the Megaport Portal. We recommend that you [create a new Port](/connections/creating-port) if you meet either of the following criteria:
* You want to physically separate this solution from your other existing traffic traversing your Ports.
* You require the new Port to be in a different location from the existing Port.
If you aren't a Megaport customer, you can create a 10 Gbps, 100 Gbps, or higher Port in one of our global [data centers/Points of Presence](https://www.megaport.com/megaport-enabled-locations/). If your company isn't located in one of our PoPs, you can procure a last mile circuit to one of the sites to connect to Megaport. [Contact Megaport](https://www.megaport.com/contact/) for more information.
## SAP on Google Cloud
SAP on Google Cloud can be deployed in any existing [Google region](https://cloud.google.com/compute/docs/regions-zones/). This high-level diagram shows an SAP Business One solution on Google Cloud with the incorporation of Megaport Partner Interconnect Layer 2 services.
You can achieve redundancy for the connectivity portion of this solution by establishing additional VXCs to the Google environment. You can achieve additional physical redundancy if the VXCs are implemented on separate Ports. In addition, you can establish an internet VPN for redundancy.
### Before you begin
When planning SAP deployments on Google Cloud, you will need to consider:
* Supported database options
* Supported operating systems
* Certified VM types for the particular SAP service plan
Hardware sizing documentation and tools such as [Quick Sizer](https://www.sap.com/about/benchmark/sizing.greenfield-sizing.html?pdf-asset=74b7bcf5-e07c-0010-82c7-eda71af511fa\&page=1#greenfield-sizing) can help you determine the required hardware to support your implementation of SAP on Google.
### Connecting Megaport to SAP on Google Cloud
To integrate Megaport with SAP on Google Cloud, you will perform the following tasks:
1. Create pairing keys in the Google Cloud console.
2. Deploy a VXC in the Megaport Portal to the Google Cloud Platform.
3. Activate the VLAN attachment in Google Cloud console.
4. Configure the BGP in the Google Cloud console.
**To create pairing keys**
1. Log on to your [Google Cloud Console](https://console.cloud.google.com/).
2. From the main menu, choose Hybrid Connectivity > Interconnect.
3. Click **Get Started**.
4. Select Partner Interconnect and click **Continue**.
5. Click **I already have a service provider**.
6. Configure your attachment.\
Provide the following details:
* **Redundancy** -- You can create redundant attachments or a single attachment:
* Create a redundant pair of VLAN attachments (default option) -- If you set up two VLAN attachments into your Google Cloud infrastructure, you will qualify for Google’s 99.9% SLA.
* Create a single VLAN -- Set up a non-redundant single BGP session (this attachment does not qualify for the Google SLA).
* Add a redundant VLAN to an existing VLAN -- If you previously created a single VLAN, you can make it redundant by selecting this option.
* **VPC Network** -- Select the VPC network you want your VPC to connect to.
* **Region** -- Select the region where your attachment will connect.
* **Cloud Router** -- A Cloud Router to associate with this attachment. You can only choose a Cloud Router in the VPC network and region that you selected with an ASN of 16550. If you don’t have an existing Cloud Router, create one with an ASN of 16550. For redundancy, each VLAN attachment must be associated with a unique Cloud Router. Google automatically adds an interface and a BGP peer on the Cloud Router.
* **VLAN attachment name** -- Specify a name for the first VLAN. Lowercase letters only.
* **Description** -- An optional field.
7. Click **Create**.\
A pairing key appears.
8. Copy the two pairing keys and click **OK**.
The next task is to create a VXC to your Google peering location from the Megaport Portal.
**To deploy a VXC to the Google Cloud Platform**
1. In the Megaport Portal, click **+Connection** on the Port for your VXC.\
If you haven’t already created a Port, see [Creating a Port](/connections/creating-port).
2. Add a Google Cloud connection for the Port.\
If this is the first connection for the Port, click the Google Cloud tile. The tile is a shortcut to the configuration page. Alternatively, click **+Connection**, click **Cloud**, then click **Google**.
3. Copy and paste the pairing key from the Google Cloud console into the Google Partner Pairing Key field.
After verifying the key, a Valid Service Key notification appears and the relevant Google targets appear based on the region of your Partner connection.
4. Select your chosen target location for your first connection then click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your VXC connection in Mbps. The speed cannot be changed once deployed. The drop-down list shows predefined rate limits available for your Port.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for your on-premises router configuration.\
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.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.\
A summary page appears that includes the monthly cost.
7. Click **Back** to make changes or click **Add VXC** to move this configuration to your cart.
8. Configure an additional VXC for redundancy using the second Google pairing key.
9. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
10. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
11. Click **Order Now**.
Megaport will deploy the VXC connection, which can take several minutes.
The Layer 2 VXC deployment is complete. The next task is to return to your Google Cloud Console to complete the BGP configuration for the VXCs/VLANs.
**To activate the BGP configuration in Google Cloud**
1. Log on to your [Google Cloud Console](https://console.cloud.google.com/).
2. From the main menu, choose Hybrid Connectivity > Interconnect.
3. Click **Activate** next to the new attachment.
4. In the Activate your Partner VLAN attachment window, click **Accept**.
5. Click **Configure BGP** to complete the process.
6. Repeat these steps to activate and configure the BGP session on your second VLAN attachment.
The BGP configuration is complete.
## Background Information
### What is SAP on Google Cloud?
SAP on Google is an Infrastructure as a Service (IaaS) that allows customers to have an SAP service on the Google Cloud platform. Using SAP on Google allows for backup and disaster recovery, global system monitoring, simple to use configuration and automation tools, identity management, and a range of security tools.
Key terms and acronyms:
* **Partner Interconnect** -- Google’s Layer 2 service that allows for private connectivity from a Partner Interconnect partner like Megaport into the Google Cloud platform.
* **Virtual Cross Connect (VXC)** -- Virtual Cross Connect is the Megaport product name for a Layer 2 VLAN.
### What are the benefits of using SAP on Google Cloud?
* A wide range of application solutions to find the appropriate product for your enterprise. For example, you can deploy on-demand instances with a pay-as-you-go model, or deploy purpose-built HANA large instances. For a list of SAP-certified products available to run on Google Cloud, see this Google help topic: [Certifications for SAP applications on GCP](https://cloud.google.com/solutions/sap/docs/certifications-sap-apps).
* The ability to trial SAP solutions, perform proof of concepts, migrate to the cloud, and create a disaster recovery solution for your business.
* Bring-your-own license models along with images and templates for migrating from on-premises to cloud help to simplify the consumption of SAP services on the Google platform.
### Google resources
To learn more about SAP on Google Cloud, explore these resources:
* [Planning guides for SAP NetWeaver, SAP HANA, SAP ASE, SAP MaxDB, and SAP Business One](https://cloud.google.com/solutions/sap/docs/)
* [Reference architectures](https://cloud.google.com/solutions/sap/docs/architectures/business-suite-architectures)
* [Deployment guides for SAP Business Suite on SAP ASE or IBM Db2 on GCP](https://cloud.google.com/solutions/sap/docs/architectures/sap-business-suite-on-ase-or-db2)
* [Reference architectures for SAP S/4HANA on Google Cloud Platform](https://cloud.google.com/solutions/sap/docs/architectures/sap-s4hana-on-gcp)
* [Guides for SAP Netweaver on Google Cloud Platform](https://cloud.google.com/solutions/sap/docs/architectures/sap-s4hana-on-gcp)
Bring-your-own-license models are available for customers who are currently using SAP services. Existing licenses can be used for production and non-production use cases.
# Integrating Megaport with Arista VeloCloud on AWS
Source: https://docs.megaport.com/cloud/megaport/vmware/vmware-aws
This help topic describes how to integrate Megaport and Arista VeloCloud on AWS.
Arista VeloCloud on AWS is an out-of-the-box service that lets you spin up a Arista VeloCloud SDDC within the AWS cloud. This functionality is available across Megaport’s global software-defined network (SDN).
Arista VeloCloud on AWS provides many benefits including the ability to take a slow and low-risk approach to cloud adoption. You can augment existing on-premises infrastructure with cloud resources for growth. This solution curbs the need for new capital expenditures on equipment while providing the ability to grow and/or reduce workloads in the cloud. It also allows you to take full advantage of your existing equipment and infrastructure while it’s still in a productive and usable state if you were contemplating an eventual full migration to the cloud.
AWS has segmented portions of their physical data center spaces to accommodate the Arista VeloCloud infrastructure. Arista VeloCloud software is implemented directly on AWS bare metal. Support and management functions, such as patching and upgrades to the software, are performed by Arista VeloCloud while management of the physical devices is handled by AWS. You are in control of your VMs and you have delegated access to vSphere.
To see how to configure Arista VeloCloud on AWS, see [ARISTA VeloCloud on AWS Overview](https://www.arista.com/en/admin-guide-vc-6-4/sd-wan-6-4-configuring-amazon-web-services).
## Understanding the architecture
AWS has simplified the connectivity model using AWS Direct Connect to reach Arista VeloCloud.
Using Megaport as your Network-as-a-Service provider, you can seamlessly deploy Virtual Interfaces (VIF) to AWS Direct Connect for Arista VeloCloud consumption, from their on-premises Data Center infrastructure.
The images below highlight the components associated with a customer’s on-premises environment connecting to a Port to reach VMware Cloud on AWS along with the available AWS Cloud services.
You will not have root or SSH access to vSphere. Also, you cannot install 3rd-party VIBs or plugins. Check with your Arista VeloCloud representative if these are required for your solution.
When networking functions are provided by the NSX-T, management traffic, cold migration and hot migration (using vMotion) traffic, and compute gateway traffic can all be transported across Direct Connect. This is an upgrade from the previous version of NSX that did not support all traffic types. Note that NSX-T is not a requirement in the on-premises infrastructure for this solution to work. An NSX standalone client can be downloaded into the on-premises environment for operational use.
When deploying vMotion between a VMkernel source and destination, a minimum bandwidth of 250 Mbps is required with a maximum round trip latency of 150 milliseconds. For more information, see [vSphere vMotion Networking Requirements](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/vcenter-and-host-management/migrating-virtual-machines-host-management/migration-with-vmotion-host-management/host-configuration-for-vmotion-host-management/vmotion-networking-requirements-host-management.html).
Infrastructure details are subject to AWS announcement changes for compute, storage, hypervisor, and technology features. Check with your VeloCloud account team for releases and updates.
## Setting up
Refer to the ARISTA VeloCloud documentation for initial set up. For more information, see [VeloCloud SD-WAN 6.4 Operator Guide](https://www.arista.com/en/operator-guide-vc-6-4/sd-wan-6-4-about-velocloud-sd-wan-operator-guide).
Once logged in, you need to create a new SDDC with information such as the AWS account, management network IPs (once you submit the IP blocks, they cannot be changed/updated), number of hosts (minimum of four required for original setup to a maximum of 32 per cluster and you can have 10 clusters per SDDC), and the AWS region for the solution along with the availability zones.
The VeloCloud account will be linked to the AWS account. Preconfigured [Cloudformation templates](https://github.com/vmware-samples/vmware-cloud-on-aws-integration-examples/blob/master/CloudFormation/README.md) for configuration can help in the initial setup of the solution. The initial environment takes up to two hours to spin up and provision while subsequent additions, deletions, and changes to hosts can happen in a matter of minutes. For more information about the initial setup process, see the [ARISTA VeloCloud on AWS Getting Started](https://www.arista.com/en/admin-guide-vc-6-4/sd-wan-6-4-configuring-amazon-web-services) and a [walk-through video](https://www.youtube.com/watch?v=JI_BUvgfXRg).
## Using Megaport with this solution
You can implement a Direct Connect Layer 2 connection to link your on-premises or co-location based infrastructure and your Arista VeloCloud on an AWS instance using Megaport.
If you are already a Megaport customer with a physical Port established, you simply add a new VXC through your Megaport account to the ARISTA VeloCloud on AWS instance that you created in the initial setup process. You use the same AWS account ID that you used in the setup process. You can establish a new Port if you want to physically separate this solution from your existing traffic traversing your Ports or simply require this Port in a different location.
If you are not a current Megaport customer, you can establish a 10 Gbps, 100 Gbps, or higher connection into one of our [Points of Presence (PoPs)](https://www.megaport.com/megaport-enabled-locations/) around the globe.
If you are not currently in one of these Point of Presence (PoP) locations, you can procure the last mile circuit to one of the PoPs to achieve connectivity to Megaport. [Contact Megaport](https://www.megaport.com/contact/) if you require help with or information on procuring a last mile circuit to one of our PoP locations.
With a Port, you can set up a VXC to a private VIF in the Arista VeloCloud SDDC instance in AWS. The VXC utilizes private IP space and will terminate directly to your AWS VPC and only the VPC CIDR blocks are advertised back to your on-premises infrastructure. Additionally, the private VIF will terminate on a virtual gateway (VGW) in the VPC which is transparent to users.
Customers can create a private Hosted VIF from their account and enter the Arista VeloCloud on AWS account number for the VIF. This account number can be obtained from the Arista VeloCloud on AWS console, under the Direct Connect > VMC AWS Account.
For more information, see [Arista VeloCloud SD-WAN and VMware Cloud on AWS Deployment Guide](https://www.arista.com/en/deployment-guide-vc-vmware/sd-wan-arista-velocloud-sd-wan-and-vmware-cloud-on-aws-deployment-guide).
You can advertise your on-premises networks to the SDDC as well. This allows a simplified full connectivity option while taking advantage of the 10 Gbps, 100 Gbps, or higher bandwidth connections from Direct Connect.
You can see the routes advertised from the Arista VeloCloud SDDC to your on-premises from the Advertised BGP Routes section on the console, and the routes received from their on-premises on the Learned BGP Routes section. The maximum number of logical network routes that can be advertised from the Arista VeloCloud SDDC to on-premises is 16 (Arista VeloCloud can increase this limit).
You can achieve redundancy for the connectivity portion of for this solution by establishing additional VXCs to to the AWS environment. You can achieve additional physical redundancy by implementing the VXCs on separate Ports.
You can also establish an internet VPN for redundancy purposes.
## Arista VeloCloud availability
Arista VeloCloud on AWS is currently available in US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Asia Pacific (Sydney), Asia Pacific (Tokyo), Europe (Frankfurt), Europe (Ireland), Europe (London), and AWS GovCloud (US). Additional regions are pending. Check the [AWS website](https://aws.amazon.com/vmware/) for the latest information.
## Helpful references
For more information, see these additional useful links:
* [ARISTA VeloCloud on AWS](https://www.arista.com/en/admin-guide-vc-6-4/sd-wan-6-4-configuring-amazon-web-services)
* [AWS for VMware](https://aws.amazon.com/vmware/)
# Integrating Megaport with Azure VMware Solution (AVS)
Source: https://docs.megaport.com/cloud/megaport/vmware/vmware-azure
This help topic describes how to integrate Megaport and Azure VMware Solution (AVS).
You can use Megaport to create an Azure ExpressRoute Layer 2 connection between your on-premises or colocation-based infrastructure and your VMware environment on Azure. You can also use ExpressRoute to connect to a cloud-only instance of Azure VMware Solution.
Before you begin, ensure that you have created a Megaport connection, or Port. After you create the Port, you can connect a Virtual Cross Connect (VXC) from the Port to the virtual gateway associated with the Azure VNET infrastructure. A VXC is a point-to-point Ethernet connection between an A-End (your Port) and a B-End (in this case, your VMware Cloud on Azure instance).
If you aren’t a Megaport customer, you can create a 10 Gbps, 100 Gbps, or higher Port in one of our global [data centers/Points of Presence](https://www.megaport.com/megaport-enabled-locations/). If your company is not located in one of our PoPs, you can procure a last mile circuit to one of the sites to connect to Megaport. [Contact Megaport](https://www.megaport.com/contact/) for more information.
If you require a Port in a different location to physically separate this solution from other existing traffic traversing your Ports, we recommend that you [create a new one](/connections/creating-port) before proceeding.
## How is VMware implemented in Azure?
Azure integrates VMware implementation into its platform using CloudSimple, a third-party vendor that provides VMware-as-a-Service in public clouds. CloudSimple is fully managed, validated, and supported by VMware and allows you to quickly implement a VMware solution using familiar tools and services including vSphere, vCenter, vSAN, and NSX.
## Setting up VMware within Azure
**To set up VMware within Azure**
1. Log in to your Azure account and search for VMware or CloudSimple.
2. Choose VMware Solution by CloudSimple – Service from the search results.
3. On the Create page, specify the project details:
* **Subscription** -- Select the subscription where you want to create the service.
* **Resource group** -- Select an existing Resource group or create a new one.
* **Name** and **Location** -- Enter a name for the service and the location/region to implement it.
* **Gateway CIDR (/28)** -- Enter a /28 IP subnet for the gateway. This IP block should be unique and not overlap with any other IP block associated with the CloudSimple environment.
4. Click **Review + create**.
5. Click **Create** to create the service.
After you have set up VMware in Azure, you can perform any of the following optional procedures:
* [Create Nodes](https://docs.microsoft.com/en-us/azure/vmware-cloudsimple/quickstart-create-cloudsimple-service) in the environment for pay-as-you-go capacity.
* [Implement a Private Cloud](https://docs.microsoft.com/en-us/azure/vmware-cloudsimple/quickstart-create-private-cloud) using CloudSimple to create an isolated VMware stack within Azure that will support ESXi hosts, vCenter, vSAN and NSX.
* [Use CloudSimple to create virtual machines](https://docs.microsoft.com/en-us/azure/vmware-cloudsimple/quickstart-create-vmware-virtual-machine) in Azure.
## Creating an authorization on the ExpressRoute circuit
To use ExpressRoute for connectivity between your on-premises infrastructure and VMware on Azure, you must create an authorization on the ExpressRoute circuit. You will then provide this authorization to CloudSimple.
**To create an authorization on the ExpressRoute circuit**
1. Log in to the Azure console and search for ExpressRoute.
2. Create a new ExpressRoute circuit or choose an existing circuit to authorize.
For more information about creating a new ExpressRoute service key in the Azure console, see the [Microsoft documentation](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-circuit-portal-resource-manager).
To check the latency and price of connecting to a particular Azure Partner location, start the procedure to [add a connection to Microsoft Azure](#azure-vxc) but instead of providing a **Microsoft Azure Service Key**, click **View all Azure Partner locations**. You can proceed to the Connection Details page without a service key and review the pricing of the selected port. To place an order for a Microsoft Azure connection, you need to provide a service key.
3. Once you have selected the circuit to authorize, select Authorizations from the navigation bar, enter a name for the authorization, and click **Save**.
4. Click **Refresh**.
5. Copy the Resource ID and the Authorization key and paste them into a text file.
6. Create a Support ticket in the Azure console. Search for Support and then select **+ New support request**.
7. Complete the Support ticket details as follows:
* **Issue type** -- Technical
* **Subscription** -- Where you want to deploy the CloudSimple service
* **Service** -- VMware Solution by CloudSimple
* **Problem type** -- Service Request
* **Problem subtype** -- Create ExpressRoute connection to on-premises
* Additional details to provide:
* Authorization key and resource ID that you previously copied into a text file
* A /29 IP network for the transit network
* Whether you are sending default routes over ExpressRoute
* Whether the Private Cloud traffic should use the default routes
## Integrating Megaport with VMware Cloud on Azure
Once you have completed the ExpressRoute authorization process, you can use the Megaport Portal to create the VXC to the VMware Cloud on Azure environment.
**To integrate Megaport with VMware Cloud on Azure**
1. In the Megaport Portal, go to the **Services** page and select the Port you want to use.
2. Add an Azure connection for the Port.\
If this is the first connection for the Port, click the Microsoft Azure tile. The tile is a shortcut to the configuration page. Alternatively, click **+Connection**, click **Cloud**, then click **Microsoft Azure**.
3. Add the ExpressRoute service key into the **Microsoft Azure Service Key** field.\
For more information about creating a service key, see the [Microsoft documentation](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-circuit-portal-resource-manager).\
After the Portal verifies the key (in approximately 5 seconds), you will be presented with Primary and Secondary on-ramp options into the Azure infrastructure.
4. Choose the **Primary** option and click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. This populates automatically based on the rate defined with the service key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** -- Specify an unused VLAN ID for this connection. This is the S-Tag, or outer tag, associated with the Port that transparently carries the inner C-Tags for ExpressRoute. This VLAN ID must be a unique ID on this Port and can range from 2 to 4090. 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.
Megaport delivers ExpressRoute services to Microsoft ports using Q-in-Q. For network devices that do not support Q-in-Q, you can select **Untagged** for the A-End VLAN. Untagging removes the VLAN tag for the outer connection (S-Tag), and delivers the three inner tags (C-Tags) natively as 802.1Q VLANs. Be aware that using an untagged VLAN limits that VXC to one Port. Because you cannot deploy any other VXCs on the Port, such as a secondary ExpressRoute VXC, we don’t recommend this workaround as a long-term solution.
You must use untagged VLANs if you are creating a MACsec connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.
7. Click **Add VXC** on the Summary page.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
You have created a single Layer 2 connection into your Azure infrastructure.
### Redundancy
You can achieve redundancy for the connectivity portion of this overall solution by establishing additional VXCs to the Azure environment. If the VXCs are implemented on separate Ports, you can achieve additional physical redundancy.
Creating a second VXC connection into your Azure infrastructure (along with the associated BGP session) will qualify the setup for Microsoft Azure’s SLA. When you paste your Microsoft Azure Service Key into the appropriate field, choose the Secondary on-ramp location (the Primary on-ramp location will be grayed out and unavailable). Follow the above process from step 5 to to complete the second VXC.
At this point, you will have created the second Layer 2 connection from your Port to your Azure infrastructure and your work in the Megaport Portal is complete.
To complete the connectivity process, log in to the Azure portal and enter the AS number, VLAN ID, and Primary and Secondary IP subnet for the Primary and Secondary BGP connections into your Azure infrastructure.
Microsoft Azure requires that you use BGP to connect your on-premises environment with your Azure infrastructure. For more information about setting up Microsoft peering and private peering from your Azure console, see the [Microsoft documentation](https://docs.microsoft.com/en-us/azure/expressroute/expressroute-howto-routing-portal-resource-manager).
## Background information
### What does the architecture look like?
Azure has simplified the connectivity model using Azure ExpressRoute to reach VMware Cloud by CloudSimple. Using Megaport as your Network-as-a-Service provider, you can seamlessly deploy ExpressRoute for VMware consumption from your on-premises Data Center infrastructure. This image shows the components associated with an on-premises environment connecting to a Port to reach VMware Cloud on Azure.
### What are the benefits for an enterprise using VMware Cloud?
VMware Cloud provides a multitude of benefits, including the ability to take a slow and low-risk approach to cloud adoption. You can augment an existing on-premises infrastructure with cloud resources for growth purposes. This augmentation reduces the need for new capital expenditures on equipment and allows increased or decreased workloads in the cloud. If you are contemplating an eventual full migration to the cloud, you can take full advantage of existing equipment and infrastructure while it’s still in a productive and usable state.
This solution can also be incorporated into an overall disaster recovery plan by using the cloud as a primary deployment with the on-premises infrastructure used as a backup. You can reverse Primary and Backup deployment locations to align with your business requirements. For additional information on benefits of VMware Cloud, see [VMware Solution on Azure by CloudSimple – features, benefits, and use case scenarios](https://docs.microsoft.com/en-us/azure/vmware-cloudsimple/cloudsimple-vmware-solutions-overview).
### Where is VMware on Azure available?
Existing Azure VMware Regions by CloudSimple can be found in this [FAQ](https://docs.microsoft.com/en-us/azure/vmware-cloudsimple/cloudsimple-faq).
# Connecting to Wasabi with Megaport
Source: https://docs.megaport.com/cloud/megaport/wasabi/index
This help topic describes how to connect to Wasabi.
Megaport makes it easy to provision fast, secure, and private connections between your data center, cloud, and Wasabi. We provide dedicated connectivity to Wasabi through our global software-defined network (SDN) from hundreds of locations worldwide.
Through private connectivity that bypasses the public internet, enterprises benefit from:
* Higher network performance, consistency, and predictability
* Streamlined and accelerated workloads and data migration
* Improved data and operational security
Megaport provides a powerful solution for enterprises to interconnect their IT environments to Wasabi across a mixture of on-premises branch locations, co-location, private and public cloud.
Enterprises have the control and ability to enable multiple VXCs to Wasabi from a single location, providing the scalability and agility required in response to evolving business needs.
## How it works
Wasabi consists of a physical network connection at several Wasabi DCs (PoPs) around the world. These PoPs reside within facilities operated by co-located data centers where Megaport is enabled.
Physical fiber connections (NNIs) between Megaport and Wasabi are established at each location. These physical connections are maintained between Wasabi and Megaport.
You can purchase access services onto the Megaport network either via Ports (DC to Cloud), MCR (Cloud to Cloud), or MVE (Branch to Cloud). Through your Megaport account, VXCs can be ordered in increments of 1 Mbps speeds up to the maximum capacity available for your location.
## Availability
**Wasabi enabled Regions**\
Customers can interconnect to Wasabi via Megaport across US, EMEA, and Asia Pacific regardless of the enabled region.
**US**\
Dallas, Ashburn, Portland
**EMEA**\
Amsterdam, Frankfurt, London, Milan
**Asia Pacific**\
Sydney
## Creating a Wasabi Direct Connect connection
To create a connection from a Megaport Port to a Wasabi Cloud service, you need a service key. Wasabi generates the service key on request.
### How to order
1. Existing Wasabi customers must contact their Wasabi Account Manager or pre-sales architect to establish a connection.
New customers can contact Wasabi through their website to discuss options.
2. Wasabi will provide a unique service key. This key will be unique to your business and will include Wasabi's VLAN ID, speed, and cloud peering location.
3. Create a connection to Wasabi Direct Connect in the Megaport Portal using the service key. Data including VLAN ID, speed, and Wasabi peering location will populate automatically from the data supplied by the service key.
4. Start uploading data to Wasabi.
### Creating a connection to Wasabi Direct Connect in the Megaport Portal
After you get your unique service key from Wasabi, create your connection to Wasabi Direct Connect in the Megaport Portal. The instructions below will help you to create the connection.
**To create a connection to Wasabi Direct Connect**
1. Make sure you have your Wasabi service key.
When you use the service key created by Wasabi, you are responsible for any VXC charges.
2. In the Megaport Portal, go to the **Services** page.
3. Select the Port you want to use.
If you haven’t already created a Port, see [Creating a Port](/connections/creating-port).
4. Add a Wasabi connection for the Port.
If this is the first connection for the Port, click the Wasabi Technologies tile. The tile is a shortcut to the configuration page.
Alternatively, click **+Connection**, click **Cloud**, then click **Wasabi Technologies**.
5. Enter the service key provided by Wasabi in the **Megaport Service Key ID** field.\
Megaport validates the key. For more information about using a service key, see [Setting up Service Keys](/marketplace/service-keys).
6. Click **Next**.
7. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Specify a speed for your connection in Mbps, up to the maximum allowable based on the maximum limit defined by the service key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** (optional) – Specify an unused VLAN ID for this connection.\
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, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don’t specify a value, Megaport will assign one.
Alternatively, you can select **Untagged** to remove the VLAN tagging for this connection. The untagged option limits you to only one VXC deployed on this Port. You must use untagged VLANs if you are creating a MACsec connection.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
8. Click **Next**.\
The summary page appears that includes the monthly cost.
1. Click **Back** to make changes or click **Add VXC**.\
Once you have finished this configuration, you can configure additional VXCs or proceed through the ordering process.
2. Repeat these steps to provision any additional VXCs.
3. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
4. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
5. Click **Order Now**.
## Wasabi Frequently Asked Questions (FAQs)
### Does Wasabi offer BYOIP?
Wasabi does support BGP advertising with both public IP addressing and RFC1918 addresses.
### What if I’m not located within a Wasabi location?
You don’t have to be located within the same facility as Wasabi, you can establish a VXC to the closest Wasabi location of your choice. You can interconnect to Wasabi regardless of your A-End location on the Megaport network.
### How do I establish redundancy between my data center and Wasabi?
We suggest establishing separate VXCs between two different Wasabi locations with two corresponding Ports at each Megaport-enabled data center.
### Are my bandwidth speeds set?
Bandwidth speeds of 10 Mbps up to several Gbps are supported.
### Does Wasabi support public and private ASNs?
Yes.
## Helpful references
* [Wasabi Direct Connect (WDX) data sheet](https://cdn.brandfolder.io/BFD8NB05/at/2n4wp7r8pp4zmmxvh4p7mmp7/WDX_Data_Sheet-4-20-21.pdf)
* [Wasabi Technologies Direct Connect](https://wasabi.com/direct-connect/)
# Creating MVE Connections to Any Endpoint with Aruba EdgeConnect SD-WAN
Source: https://docs.megaport.com/cloud/mve/aruba/generic/index
This help topic describes how to create a VXC from an MVE to Cloud Partners and integrate the connection with Aruba EdgeConnect SD-WAN.
This topic describes the general steps to configure and deploy a Megaport VXC connection in the Megaport Portal and integrate it with an MVE in Aruba EdgeConnect SD-WAN. The VXC can connect to a Cloud Service Provider, a Port, or an MCR.
#### Step 1 -- Create an MVE
* Create an MVE in the Megaport Portal.\
For more information, see [Creating an MVE](/mve/aruba/creating).
The MVE needs to be in the active state.
#### Step 2 -- Create a VXC from the MVE
1. In the Megaport Portal, select the MVE created in Step 1.
2. Create a VXC to another MVE, a Port, or Cloud Service Provider.\
For more information, see [Creating a VXC](/connections/overview#create_vxc).
Ensure both ends of the connection are active and have BGP configured.
3. In the connection details, note the A-End VLAN.
#### Step 3 -- Collect these values for the connection
* MVE IP address
* MVE VLAN (A-End)
* MVE ASN
* Cloud/B-End IP address
* B-End ASN
* MD5 Password
#### Step 4 -- Create an interface in Aruba Orchestrator
1. Log in to Aruba Orchestrator.
2. Go to Configuration > Networking | Deployment.
3. Locate the appliance by the hostname and click the Edit (pencil) icon.
4. If you do not have a wan0 LAN side interface: Click **+Add** next to LAN Interfaces and in the Interface drop-down menu, choose wan0.
If you already have a wan0 LAN interface, click **+IP** to add a new configuration.
5. In the **VLAN** field, enter the A-End VLAN for the connection.
6. (Optional) Select a preconfigured Label or select None.
7. In the **IP/Mask** field, enter the IP address and mask for the MVE side of the connection.
8. For the Next Hop, enter the IP address for the B-End side of the connection.
9. Specify in and out bandwidth values.
The bandwidth must be equal to or less than the MVE bandwidth limit.
This image shows sample configuration values.
10. Click Apply.
11. If prompted, reboot the appliance.
A reboot is required only when adding the first LAN interface, as the system switches the appliance from server mode to router mode.
Once the device is reachable from Orchestrator, you can configure a BGP session.
1. In Orchestrator, go to Configuration > Networking | Routing | BGP.
2. Click the Edit (pencil) icon for the appliance.
3. Move the slider to **Enable BGP**.
4. Provide the local AS number.
This is the MVE ASN.
5. In the **Router ID** field, enter the loopback 0 IP specified during the initial acceptance of the appliance or another system IP, as required by your network.
You can use any IP address on the appliance, such as the interface IP on the MVE side of the VXC or the transit IP address.
6. In the BGP Peers section, click **Add** and provide the following information:
* **Peer IP** -- The IP address of the B-End of the connection (cloud provider, port, or other MVE).
* **Local Interface** -- Choose the newly created LAN interface (the interface is in the format *wan0+VLAN*).
* **Peer ASN** -- The AS value for the B-End of the connection.
* **Peer Type** -- Choose Branch.
* **Enable MD5 Password** -- If required, select this and then enter and confirm your MD5 password.
7. Click **Add**.
8. Click **Apply**.
It takes several seconds for the configuration to be pushed to the appliance.
#### Step 5 -- Validating your connection
You can review appliance status, including the connection state, from the Monitoring tab in Orchestrator.
When successful, the Peer State is *Established*:
You can review connection details, including the connection state, from the Aruba (Silver Peak) CLI with these commands:
* `show interface wan0.` -- Displays configuration details and current status for the appliances.
* `show bgp neighbors` or `show bgp summary` -- Displays configuration details and current status for the BGP neighbors.
**To start a CLI session from Orchestrator**
1. In Orchestrator, use the mouse to hover over the appliance and click the Appliance Menu icon to the right of the appliance name.
2. Choose CLI Session from the menu.
3. Enter **enable** mode to use the recommended CLI commands to display configuration details.
# Creating a Google Cloud Services Connection for an MVE with Aruba EdgeConnect SD-WAN
Source: https://docs.megaport.com/cloud/mve/aruba/google/index
This help topic describes how to provision connections between MVE and Google Cloud Services and integrate the connection with Aruba EdgeConnect SD-WAN.
You can create a network connection from an MVE with Aruba EdgeConnect SD-WAN to Google Cloud through Partner Interconnect.
When connecting to Google Cloud Platform (GCP) through Partner Interconnect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection and Layer 3 BGP is established directly between the customer and GCP.
Before you begin, create an MVE in Aruba Orchestrator. For more information, see [Creating an MVE](/mve/aruba/creating). The MVE needs to be in the active state.
There are three parts to adding a Google Cloud connection to your MVE and Aruba Orchestrator.
1. Create a Partner Interconnect attachment in Google Cloud Console or gcloud CLI. Copy the pairing key that is provided as part of the attachment creation. For additional details, see the Google documentation on
[Google Partner Interconnects](https://cloud.google.com/interconnect/docs/how-to/partner/provisioning-overview).
2. In the Megaport Portal, create a VXC from your MVE to connect to your Google Cloud attachment.
3. In Aruba Orchestrator, create a new interface and add the details of the Google Cloud connection.
These instructions step through the second and third parts.
MVE for Aruba EdgeConnect SD-WAN requires configuration steps in both Aruba Orchestrator and the Megaport Portal for all cloud connections.
## Adding the Google Cloud connection in the Megaport Portal
To set up the Google Cloud Platform connection, you need to create the connection in the Megaport Portal.
**To create a connection to GCP from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select Google as the service provider.
To check the latency and price of connecting to a particular Google location, click **View all Google Partner locations**. You can proceed to the Connection Details page without a pairing key and review the pricing of the selected port. To place an order for a Google connection, you need to provide a pairing key.
4. Copy and paste the pairing key from the Google Cloud console into the Google Partner Pairing Key field.\
After verifying the key, a Valid Service Key notification appears and the relevant Google targets appear based on the region of your GCI Partner connection.
5. Select the target location for your connection then click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The speed cannot be changed once deployed. Enter the same rate you selected for your Google port speed.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/aruba/creating-mve-manual#creating-mve).
* **Preferred A-End VLAN** -- The VLAN for this connection that you will receive through the MVE. This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
11. Once you have deployed the VXC, go back to your attachment in the Google Cloud Console and accept it.\
You will be provided your private IP address from Google to configure BGP.\
Ensure that you pre-activate the attachment or mark the attachment as active after configuring the VXC. Otherwise, you cannot set up BGP with your SD-WAN instance.
The Google ASN will always be 16550.
## Adding Google Cloud connection details to Aruba Orchestrator
After you create the connection from your MVE to Google Cloud and set up the connection in the Google console, you need to configure it in Aruba Orchestrator. This involves revising Orchestrator templates to add a LAN interface and configure BGP settings, ASNs, and VLANs.
**To add a LAN interface in Aruba Orchestrator**
1. Collect the connection details from the Google console.\
Display the details of the connection you created in Google Cloud for this connection. Note the values for the **Peer ASN**, **Cloud Router BGP IP**, and **BGP Peer IP**.
2. Collect the connection details from the Megaport Portal.\
To display the details, click the gear icon for the Google connection from your MVE and click the **Details** view. Note the value for the **A-End VLAN**.
Next, you will add a subinterface to your Aruba EC-V.
3. Log in to Aruba Orchestrator.
4. Choose Configuration > Networking | Deployment.
5. Locate the appliance by the hostname and click the Edit (pencil) icon.
6. Add a new LAN side interface: Click **+Add** next to LAN Interfaces.
If this is the first LAN side service connection, click **+Add**. If you already have a LAN interface, click **+IP** under the Interface drop-down list to add a new configuration.
Here is a screen with sample values.
7. In the Interface drop-down menu, choose wan0.
8. In the **VLAN** field, enter the A-End VLAN value for this Google connection in the Megaport Portal.\
Click the Details icon for the connection in the Megaport Portal to find this value.
9. (Optional) Select a preconfigured Label or select None.
10. In the **IP/Mask** field, enter the A-End interface IP Address and subnet mask for this Google connection.
These values are available in the VLAN attachment details in the Google Cloud console. The IP address appears in the **BGP Peer IP** field.
11. For the Next Hop, enter the Google-side **Cloud Router BGP IP** address from the VLAN attachment details in the Google Cloud console.
12. Specify in and out bandwidth values.\
The bandwidth must be equal to or less than the MVE bandwidth limit: Small ≤ 500 Mbps, Medium ≤ 1 Gbps, or Large ≤ 5 Gbps.
13. Click **Apply**.
14. If prompted, reboot the appliance.\
A reboot is required only when adding the first LAN interface, as the system switches the appliance from server mode to router mode.
Once the device is reachable from Orchestrator, you can configure a BGP session.
**To configure a BGP session** (optional)
1. In Orchestrator, go to Configuration > Networking | BGP.
2. Click the Edit (pencil) icon for the appliance.
3. Move the slider to **Enable BGP**.
4. Provide the autonomous system number (ASN).\
This is the Customer ASN (your local MVE), collected in Step 1.
5. In the **Router ID** field, enter a system IP as required by your network design.\
You can use any IP address on the MVE, such as the loopback 0 IP specified during the initial acceptance of the appliance, the interface IP on the MVE side of the VXC, or the transit IP address.
6. In the BGP Peers section, click **Add** and provide the following information:
* **Peer IP** -- This is the local Google Cloud IP address. This value is available in the VLAN attachment details in the Google Cloud console. The IP address appears in the **Cloud Router BGP IP** field.
* **Local Interface** -- Choose the newly created LAN interface (the interface is in the format *wan0+VLAN*).
* **Peer ASN** -- This is the Google Cloud ASN of 16550. This is a fixed value, and appears in the VLAN attachment details on the Google console.
* **Peer Type** -- Choose Branch.
* **Enable Password** -- If required, select this and then enter and confirm your MD5 password. This is the BGP Auth Key in the Megaport Portal.
7. Click **Add**.
8. Click **Apply**.\
It takes several seconds for the configuration to be pushed to the appliance. Click the refresh icon to update the data from the appliance.
When successful, the Peer State is *Established*:
## Validating your Google Cloud connection
You can review connection details, including the connection state, from the CLI with these commands:
* `show interface wan0.` -- Displays configuration details and current status for the appliances.
* `show bgp neighbors` or `show bgp summary` -- Displays configuration details and current status for the BGP neighbors.
**To start a CLI session from Orchestrator**
1. In Orchestrator, use the mouse to hover over the appliance and click the Appliance Menu icon to the right of the appliance name.
2. Choose CLI Session from the menu.
3. Enter **enable** mode to use the recommended CLI commands to display configuration details.
# Creating MVE Connections to Latitude.sh with Aruba EdgeConnect SD-WAN
Source: https://docs.megaport.com/cloud/mve/aruba/latitude-sh/index
This help topic describes how to create a connection from an Aruba EdgeConnect SD-WAN MVE to Latitude.sh.
This topic describes how to create a VXC from MVE to Latitude.sh bare metal cloud using the Megaport Portal, and how to configure BGP in to bring the connection up.
BGP is required for all Latitude.sh connections. To create a connection, specify an ASN, BGP password, and the prefixes to advertise. The connection becomes live after Latitude.sh approves the request.
## Prerequisites
The MVE must be in the active state before you create a connection.
## Adding the Latitude.sh connection in the Megaport Portal
To set up a connection to Latitude.sh with Megaport, you need to create a VXC from your MVE in the Megaport Portal to the Latitude.sh location where you have provisioned your Latitude.sh services.
**To create a connection to Latitude.sh from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection**, click **Cloud**, then click **Compute via Latitude.sh**.
3. Select the target location for your connection then click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc/).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you don't specify a value, Megaport assigns one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.\
A summary page appears that includes the monthly cost.
6. Click **Back** to make changes, or click **Add VXC**.
7. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
8. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
9. Click **Order Now**.
The connection becomes live after Latitude.sh approves the request.
After ordering, the connection status shows *Deployable* until it is provisioned. When Latitude.sh approves the connection and provisioning is complete, the status updates to *Configured*.
## Adding the Latitude.sh connection to Aruba Orchestrator
To add the connection to Aruba Orchestrator, you will need the following information:
* MVE IP address
* MVE VLAN (A-End)
* MVE ASN
* Cloud/B-End IP address
* B-End ASN
* MD5 Password
After you create the connection from your MVE to Latitude.sh, you need to configure a LAN interface and a BGP session for it in Aruba Orchestrator.
For more information about configuring the interface, see [HPE Networking Orchestrator Docs: Interfaces Tab](https://arubanetworking.hpe.com/techdocs/sdwan/docs/orch/configuration/network/interfaces/).
For more information about configuring BGP, see [HPE Networking Orchestrator Docs: BGP Tab](https://arubanetworking.hpe.com/techdocs/sdwan/docs/orch/configuration/network/bgp/).
## Validating your Latitude.sh connection
You can review appliance status, including the connection state, from the Monitoring tab in Orchestrator. When successful, the Peer State is *Established*:
You can also review connection and BGP session details from the Aruba (Silver Peak) CLI. For more information, see [HPE Networking Orchestrator Docs: BGP Tab](https://arubanetworking.hpe.com/techdocs/sdwan/docs/orch/configuration/network/bgp/).
## Helpful references
* [Connecting to Latitude.sh](/portal-admin/connect-latitude)
* [Creating an MVE Integrated with Aruba Overview](/mve/aruba/creating)
* Latitude.sh docs
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Creating MVE Connections to Any Endpoint with Aviatrix Secure Edge
Source: https://docs.megaport.com/cloud/mve/aviatrix/generic/index
This help topic describes how to create a VXC from an MVE to Cloud Partners and integrate the connection with Aviatrix Secure Edge.
This topic describes the general steps to configure and deploy a Megaport VXC connection in the Megaport Portal and integrate it with an MVE in Aviatrix Secure Edge. The VXC can connect to a Cloud Service Provider, a Port, or an MCR.
#### Step 1 -- Create an MVE
* Create an MVE in the Megaport Portal.\
For more information, see [Creating an MVE Integrated with Aviatrix](/mve/aviatrix/creating-mve-aviatrix).
The MVE needs to be in the *active* state.
#### Step 2 -- Create a VXC from the MVE
1. In the Megaport Portal, select the MVE created in Step 1.
2. Create a VXC to another MVE, a Port, or Cloud Service Provider.\
For more information, see [Creating a VXC](/connections/overview#create_vxc).
Ensure both ends of the connection are active and have BGP configured.
3. In the connection details, note the A-End VLAN.
#### Step 3 -- Collect these values for the connection
* MVE IP address
* MVE VLAN (A-End)
* MVE ASN
* Cloud/B-End IP address
* B-End ASN
* MD5 Password
#### Step 4 -- Configure the connection in Aviatrix CoPilot
After you create the connection from your MVE to the required endpoint, you need to configure it in Aviatrix CoPilot. This involves configuring an interface and BGP.
For more information, see the [Aviatrix Documentation](https://docs.aviatrix.com/documentation/latest/building-your-network/edge-spoke-workflow-megaport.html).
#### Step 5 -- Validating your connection
* Use CoPilot's diagnostic tools to review connection details and perform a ping test to check IP connectivity.
* Verify that BGP is established using BGP diagnostics and relevant BGP CLI commands.
# Creating a Google Cloud Services Connection for an MVE with Aviatrix Secure Edge
Source: https://docs.megaport.com/cloud/mve/aviatrix/google/index
This help topic describes how to provision connections between MVE and Google Cloud Services and integrate the connection with Aviatrix Secure Edge.
You can create a network connection from an MVE with Aviatrix Secure Edge to Google Cloud through Partner Interconnect.
When connecting to Google Cloud Platform (GCP) through Partner Interconnect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection and Layer 3 BGP is established directly between the customer and GCP.
Before you begin, create an MVE. For more information, see [Creating an MVE Integrated with Aviatrix](/mve/aviatrix/creating-mve-aviatrix). The MVE needs to be in the *active* state.
There are three parts to adding a Google Cloud connection to your MVE and Aviatrix CoPilot.
1. Create a Partner Interconnect attachment in Google Cloud Console or gcloud CLI. Copy the pairing key that is provided as part of the attachment creation. For more information, see the Google documentation on
[Google Partner Interconnects](https://cloud.google.com/interconnect/docs/how-to/partner/provisioning-overview).
2. In the Megaport Portal, create a VXC from your MVE to connect to your Google Cloud attachment.
3. In Aviatrix CoPilot, configure an interface and Border Gateway Protocol (BGP).
MVE for Aviatrix Secure Edge requires configuration steps in both Aviatrix CoPilot and the Megaport Portal for all cloud connections.
## Adding the Google Cloud connection in the Megaport Portal
To set up the Google Cloud Platform connection, you need to create the connection in the Megaport Portal.
**To create a connection to GCP from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select Google as the service provider.
To check the latency and price of connecting to a particular Google location, click **View all Google Partner locations**. You can proceed to the Connection Details page without a pairing key and review the pricing of the selected port. To place an order for a Google connection, you need to provide a pairing key.
4. Copy and paste the pairing key from the Google Cloud console into the Google Partner Pairing Key field.\
The relevant Google targets appear based on the region of your GCI Partner connection.
5. Select the target location for your connection then click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The speed cannot be changed once deployed. Enter the same rate you selected for your Google port speed.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/aviatrix/creating-mve-aviatrix#creating-mve).
* **Preferred A-End VLAN** -- The VLAN for this connection that you will receive through the MVE. This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
11. Once you have deployed the VXC, go back to your attachment in the Google Cloud Console and accept it.\
You will be provided your private IP address from Google to configure BGP.\
Ensure that you pre-activate the attachment or mark the attachment as active after configuring the VXC. Otherwise, you cannot set up BGP with your product.
The Google ASN will always be 16550.
## Adding the Google Cloud connection to Aviatrix
After you create the connection from your MVE to Google Cloud and set up the connection in the Google console, you need to configure it in Aviatrix. This involves configuring BGP settings, ASNs, and VLANs.
**To add the Google Cloud connection in Aviatrix**
1. **Google Connection Details**
Collect the connection details from the Google console for the connection you created.
Note the values for the **Peer ASN**, **Cloud Router BGP IP**, and **BGP Peer ID**.
2. **Megaport Connection Details**
Collect the A-End vNIC details associated with the Google connection from the Megaport Portal. To display the details, click the gear icon for the Google connection from your MVE then click the **Details** view.
Note the **A-End vNIC** value associated with the Google connection. Aviatrix orders vNICs in the same order they are created in the Megaport Portal. For example:
* 0: eth0
* 1: eth1
* 2: eth2
Collect the vNIC number associated with the connection, as this number will be used to associate the Aviatrix interface with the same number. For example, vNIC **0** in the Megaport Portal corresponds to **eth0** in Aviatrix.
Ensure all vNICs remain untagged as the Aviatrix MVE does not support VLAN tagging.
3. **Aviatrix CoPilot Configuration**
Log in to Aviatrix and configure Aviatrix CoPilot with the details you have copied.
For more information, see the [Aviatrix Documentation](https://docs.aviatrix.com/documentation/latest/building-your-network/edge-spoke-workflow-megaport.html).
**Validation**
* Use CoPilot's diagnostic tools to review connection details and perform a ping test to check IP connectivity to Google.
* Verify that BGP is established using BGP diagnostics and relevant BGP CLI commands.
# Creating MVE Connections to Latitude.sh with Aviatrix
Source: https://docs.megaport.com/cloud/mve/aviatrix/latitude-sh/index
This help topic describes how to create a connection from an Aviatrix MVE to Latitude.sh.
This topic describes how to create a VXC from MVE to Latitude.sh bare metal cloud using the Megaport Portal, and how to configure BGP in to bring the connection up.
BGP is required for all Latitude.sh connections. To create a connection, specify an ASN, BGP password, and the prefixes to advertise. The connection becomes live after Latitude.sh approves the request.
## Prerequisites
The MVE must be in the active state before you create a connection.
## Adding the Latitude.sh connection in the Megaport Portal
To set up a connection to Latitude.sh with Megaport, you need to create a VXC from your MVE in the Megaport Portal to the Latitude.sh location where you have provisioned your Latitude.sh services.
**To create a connection to Latitude.sh from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection**, click **Cloud**, then click **Compute via Latitude.sh**.
3. Select the target location for your connection then click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc/).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you don't specify a value, Megaport assigns one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.\
A summary page appears that includes the monthly cost.
6. Click **Back** to make changes, or click **Add VXC**.
7. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
8. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
9. Click **Order Now**.
The connection becomes live after Latitude.sh approves the request.
After ordering, the connection status shows *Deployable* until it is provisioned. When Latitude.sh approves the connection and provisioning is complete, the status updates to *Configured*.
## Adding the Latitude.sh connection to Aviatrix
To add the connection to Aviatrix, you will need the following information:
* MVE IP address
* MVE VLAN (A-End)
* MVE ASN
* Cloud/B-End IP address
* B-End ASN
* MD5 Password
After you create the connection from your MVE to Latitude.sh, you need to configure it in Aviatrix CoPilot. This involves configuring an interface and BGP.
For more information, see the [Aviatrix Documentation: Deploy an Edge Spoke Gateway on Megaport Virtual Edge](https://docs.aviatrix.com/docs/enterprise/9.0/guides/connectivity/edge/edge-spoke-workflow-megaport#deploy-an-edge-spoke-gateway-on-megaport-virtual-edge).
## Validating your Latitude.sh connection
* Use CoPilot's diagnostic tools to review connection details and perform a ping test to check IP connectivity.
* Verify that BGP is established using BGP diagnostics and relevant BGP CLI commands.
## Helpful references
* [Connecting to Latitude.sh](/portal-admin/connect-latitude)
* [Creating an MVE Integrated with Aviatrix](/mve/aviatrix/creating-mve-aviatrix)
* Latitude.sh docs
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Creating MVE Connections to Any Endpoint with Cisco SD-WAN
Source: https://docs.megaport.com/cloud/mve/cisco/generic/index
This help topic describes how to create a VXC from a Cisco SD-WAN MVE to Cloud Partners.
This topic describes the general steps to configure and deploy a Megaport VXC connection in the Megaport Portal and integrate it with an MVE (the interconnect gateway) in Cisco SD-WAN. The VXC can connect to a Cloud Service Provider, a Port, or an MCR.
Although you can create MVE-to-MVE and AWS connections from the MVE in the Portal, Megaport strongly recommends creating these connections in vManage for seamless integration with your Cisco SD-WAN environment.
#### Step 1 -- Create an MVE
* Create an MVE (Cisco interconnect gateway) in vManage.\
For more information, see [Creating an MVE](/mve/cisco/creating/creating-mve).
The MVE needs to be in the active state.
#### Step 2 -- Create a VXC from the MVE
1. In the Megaport Portal, select the MVE created in Step 1.
2. Create a VXC to a Port, MCR, or Cloud Service Provider.\
For more information, see [Creating a VXC](/connections/overview#create_vxc).
3. In the connection details, note the A-End VLAN.
#### Step 3 -- Copy the default device template
1. In Cisco vManage, go to Configuration > Templates and select the **Device** tab.
2. Make a copy of Default\_MEGAPORT\_ICGW\_C8000V\_Template\_V01.\
Click the ellipsis (**...**) at the end of the row and select Copy from the drop-down list.
3. Provide a name for the copied template and click **Copy**.\
This name can contain only uppercase and lowercase letters, the digits 0 through 9, hyphens, and underscores. It cannot contain spaces or any other characters.
#### Step 4 -- Create a VPN feature template
1. On the Templates page, select the **Feature** tab and click **+Add Template**.
2. In Select Devices, select the C8000v.
3. Under Select Template > VPN, click **Cisco VPN**.
4. Enter a template name and description.
5. In the Basic Configuration section, enter the VPN (VRF) ID for the VXC.\
The VPN ID can be any number 1 -- 511 or 513 -- 65530.
VPN 0 is reserved for Transport VPN and VPN 512 is reserved for Managed VPN. The number is normally identical to the VPN ID assigned for corporate networks to communicate between the corporate network and cloud service.
6. Click **Save**.
#### Step 5 -- Create a BGP feature template
1. On the Templates page, select the **Feature** tab and click **+Add Template**.
2. In Select Devices, select the C8000v.
3. In Select Template > OTHER TEMPLATES click **Cisco BGP**.
4. Enter a template name and description.
5. In the Neighbor section, click **+New Neighbor**.
6. Next to the **Address** field, select Device Specific from the drop-down list.
7. Next to the **Remote AS** field, select Device Specific from the drop-down list.
8. Click **Add** and click **Save**.
#### Step 6 -- Create a CLI add-on feature template
1. On the Templates page, select the **Feature** tab and click **+Add Template**.
2. In Select Devices, select the C8000v.
3. In Select Template > OTHER TEMPLATES click **Cli Add-On Template**.
4. Enter a template name and description.
5. Copy the following configuration into the **CLI CONFIGURATION** field.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
interface GigabitEthernet1.{{interface-tag}}
encapsulation dot1Q {{dot1Q-tag}}
vrf forwarding {{vrf-number}}
ip address {{ip-address-subinterface}}
ip mtu 1500
!
```
6. Click **Save**.
#### Step 7 -- Apply the feature templates to the device template
1. Go to Configuration > Templates and select the **Device** tab.
2. Select the MVE template that was copied from the default in Step 1.
3. Click the ellipses (**...**) in the last column and choose Edit.
4. In the Transport & Management VPN section, from the Cisco VPN 512 drop-down list, select Factory\_Default\_Cisco\_VPN\_512\_Template.
5. In Service VPN, click **+Add VPN**.
6. Select the VPN template created in Step 4, click the arrow to move it to the Selected VPN Templates pane, and click **Next**.\
The select sub-templates step appears.
7. In Additional Cisco VPN Templates, click **Cisco BGP**.
8. From the Cisco BGP drop-down list, select the BGP template created in Step 5 and click **Add**.
9. In Additional Templates, from the CLI Add-On Template drop-down list, select the CLI template created in Step 6.
10. Click **Update**.
#### Step 8 -- Apply the device template to MVE
1. Go to Configuration > Templates and select the **Device** tab.
2. Select the MVE template that was copied from the default in Step 1.
3. Click the ellipses (**...**) in the last column and choose **Attach Devices**.
4. Select the live MVE that was created before starting Step 1, move it to the right pane, and click **Attach**.\
Next, enter device-specific information.
5. Click the ellipses (**...**) in the last column and click **Edit Device Template**.
6. Enter values in these fields:
* **interface-tag** -- This value is the same as dot-1Q-tag.
* **dot-1Q-tag** -- This value is the same as interface-tag. You can find this value in the VXC connection details on the Megaport Portal: click the VXC name, click Details, and use the A-End VLAN value.
* **vrf-number** -- Specify the VRF number (VPN ID) for the interface.
* **ip-address-subinterface** -- Specify the IP address and mask of the interface.
* **AS Number** -- Specify the AS number of the MVE.
* **Address** -- Specify the remote BGP peer IP address.
* **Remote AS** - Enter the ASN for the remote BGP peer.
7. Click **Update**.
8. Click **Next**.\
vManage displays the Config Preview and Config Diff. Use these features to ensure the correct configuration will be applied.
9. Select the MVE on the left.
10. Click **Configure Devices**.\
vManage pushes the configuration to the MVE. When complete, the status indicates success.
#### Step 9 -- Verify the connection
1. In vManage, go to Tools > SSH Terminal.
2. Select the MVE in the device group.\
An SSH terminal opens.
3. Enter your login details.
4. Enter the following command to ping the other end of the Megaport VXC from the MVE.
`ping vrf `
5. Enter the following command to confirm the BGP session is up:
`show ip bgp vpnv4 vrf summary`
# Creating a Google Cloud Services Connection for an MVE with Cisco SD-WAN
Source: https://docs.megaport.com/cloud/mve/cisco/google/index
This help topic describes how to provision connections between Cisco SD-WAN MVEs and Google Cloud Services.
You can create a network connection from an MVE (a Cisco interconnect gateway) to Google Cloud through Partner Interconnect.
When connecting to Google Cloud Platform (GCP) through Partner Interconnect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection and Layer 3 BGP is established directly between the customer and GCP.
Before you begin, create an MVE (Cisco interconnect gateway) in vManage. For more information, see [Creating an MVE](/mve/cisco/creating/creating-mve). The MVE needs to be in the active state.
There are three parts to adding a Google Cloud connection to your MVE and vManage.
1. Create a Partner Interconnect attachment in Google Cloud Console or gcloud CLI. Copy the pairing key that is provided as part of the attachment creation.\
For more information, see the Google documentation on
[Google Partner Interconnects](https://cloud.google.com/interconnect/docs/how-to/partner/provisioning-overview).
2. In the Megaport Portal, create a VXC from your MVE to connect to your Google Cloud attachment.
3. In vManage, create a custom MVE device template and add the details of the Google Cloud connection.
These instructions step through the second and third parts.
The initial release of MVE requires configuration steps in both Cisco vManage and the Megaport Portal for Google cloud connections (as described in this topic). Subsequent updates by Cisco let you configure Google connections completely in vManage. When possible, we recommend creating Google connections in vManage for seamless integration with your Cisco SD-WAN environment. Cisco provides instructions for the vManage steps: [Create Interconnects to Google Cloud](https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/cloudonramp/ios-xe-17/cloud-onramp-book-xe/m-cloud-onramp-sdci.html#d27774e5530a1635).
## Adding the Google Cloud connection in the Megaport Portal
To set up the GCP connection, you need to create the connection in the Megaport Portal.
**To create a connection to GCP from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select Google as the provider.
To check the latency and price of connecting to a particular Google location, click **View all Google Partner locations**. You can proceed to the Connection Details page without a pairing key and review the pricing of the selected port. To place an order for a Google connection, you need to provide a pairing key.
4. Copy and paste the pairing key from the Google Cloud console into the Google Partner Pairing Key field.\
The relevant Google targets appear based on the region of your GCI Partner connection.
5. Select the target location for your connection then click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Enter the same rate you selected for your Google port speed.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/cisco/creating-mve-autonomous#creating-mve).
* **Preferred A-End VLAN** -- The VLAN for this connection that you will receive through the MVE. This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
11. Once you have deployed the VXC, go back to your attachment in the Google Cloud Console and accept the attachment. You will be provided your private IP address from Google to configure BGP.\
Ensure that you pre-activate the attachment or mark the attachment as active after configuring the VXC. Otherwise, you cannot set up BGP with your SD-WAN instance.
The Google ASN will always be 16550.
## Adding the Google Cloud connection to vManage
Follow the steps in each of these sections to create, edit, and attach the vManage templates for an MVE with the connection details.
To set up the connection in vManage, you need a dedicated device template and you need to provide feature templates to specify configuration details. You need to create a Service VPN template, a Cisco BGP template, as well as a CLI add-on template.
### Step 1 - Copy the default device template
You need a dedicated template for the MVE so you can edit the template with the connection details for the VXC. You need a dedicated template because if other devices are attached to the template, the change affects each attached device.
**To create a copy of the device template**
1. In vManage, go to Configure > Templates and select the **Device** tab.
2. Find the Default\_MEGAPORT\_ICGW\_C8000V\_Template\_V01 template and copy it.\
Click the ellipsis (**...**) at the end of the row and choose Copy from the drop-down menu.
3. Enter a name for the template and a description and click **Copy**.\
This name can contain only uppercase and lowercase letters, the digits 0 through 9, hyphens, and underscores. It cannot contain spaces or any other characters.
### Step 2 - Create a Cisco VPN feature template
You need to create a VPN template so you can specify the VPN ID of the GCP connection. The VPN ID is the same as the corporate network.
**To create a VPN feature template**
1. In vManage, go to Configure > Templates and select the **Feature** tab.
2. Find a template for the C8000v device model and a type of Cisco VPN and copy it.\
Click the ellipsis (**...**) at the end of the row and choose Copy from the drop-down menu.
Instead of copying the template, you can also add a new Cisco VPN template for a C8000v device and populate it with the same values.
3. Enter a name for the template and a description and click **Copy**.
4. Edit the template and add the VPN ID in the Basic Configuration.\
Click the ellipsis (**...**) and choose Edit.\
The VPN ID can be any number 1 -- 511 or 513 -- 65530.
VPN 0 is reserved for Transport VPN and VPN 512 is reserved for Managed VPN. The number is normally identical to the VPN ID assigned for corporate networks to communicate between the corporate network and cloud service.
5. Click **Update**.
### Step 3 - Create a BGP feature template
You also need a BGP template for the connection peering details.
**To create a Cisco BGP feature template**
1. In the Feature tab of vManage Templates, find a template for the C8000v device model and a type of Cisco BGP and copy it.
Instead of copying the template, you can also add a new Cisco BGP template for a C8000v device and populate it with the same values.
2. Enter a name for the template and a description and click **Copy**.
3. Edit the template (click the ellipsis **...** for the new template and choose Edit) and enter the AS Number for the MVE in the Basic Configuration section.
4. In the Neighbor section, click **+New Neighbor** and specify these values for the cloud side of the connection:
* **Address** -- Specify the peer IP address of the cloud side. Enter the IP address and subnet mask in dotted quad format and not CIDR notation. For example, specify `169.254.x.y 255.255.255.248` instead of `a.b.c.d/29`.
* **Description** -- Enter a meaningful description of the template.
* **Remote AS** -- Enter the AS Number of the cloud side: the AS number of GCP is 16550.
5. Click **Update**.
### Step 4 - Create a CLI Add-On feature template
You also need an add-on CLI template.
**To create a CLI Add-On feature template**
1. Find a template for the C8000v device model and a type of CLI Template and copy it.
2. Enter a name for the template and a description and click **Copy**.
3. Edit the template (click the ellipsis **...** for the new template and choose Edit) and copy the following lines into the CLI Configuration section.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
interface GigabitEthernet1. {{interface-tag}}
encapsulation dot1Q {{dot1Q-tag}}
vrf forwarding {{vrf-number}}
ip address {{ip-address-subinterface}}
ip mtu 1500
!
```
4. Click **Update**.
### Step 5 - Update your device template
Next, we need to add the feature templates to the copy of the default device template and then define the values for the added features.
**To add the feature templates to the device template**
1. In the Device tab of vManage Templates, find the copy of the device template that you created in Step 1 and click the ellipsis (**...**) and choose Edit.
2. In the Service VPN tab, click **+Add VPN**.
3. In the Available VPN Templates, highlight the template created in Step 2, click the arrow to move it to the Selected VPN Templates, and click **Next**.\
The select sub-templates step appears.
4. From the Additional Cisco VPN Templates, click **Cisco BGP**.
5. From the Cisco BGP menu, choose the BGP template you created in Step 3 and click **Add**.
6. In the Additional Templates tab, select the CLI Add-On template you created in Step 4 and click **Update**.\
A screen appears that lists the updated device template. You need to edit this template to add values for the new fields and associate an MVE.
7. Click the ellipsis (**...**) and choose Edit.\
The device settings appear with new fields defined in the feature templates.
8. Enter values for these new fields:
* **vrf-number** -- Specify the VRF number (VPN ID) for the interface.
* **ip-address-subinterface** -- Specify the IP address of the interface. This is the IP address assigned by GCP. You can confirm the IP address from the GCP console.
* **Interface-tag** -- This value is the same as dot-1q-tag. You can find this value in the VXC connection details on the Megaport Portal: click the VXC name, choose Details, and use the A-End VLAN value.
* **dot-1q-tag** -- This value is the same as interface-tag. You can find this value in the VXC connection details on the Megaport Portal: click the VXC name, choose Details, and use the A-End VLAN value.
* **Description(gcp\_bgp\_neighbor\_description)** -- Enter a meaningful description of the template for the BGP peer.
* **Address(gcp\_bgp\_neighbor\_address)** -- Specify the peer IP address of GCP cloud router. You can find the IP address in the GCP console.
* **AS Number** -- Specify the AS number of the MVE.
9. Click **Update**.\
vManage displays a preview of the configuration.
Click Config Diff to review the changes. (Changes are highlighted in green.)
10. Select the MVE in the device list.
11. Review the changes and click **Configure Devices**.\
vManage loads the template. When complete, the status indicates success.
The VLAN attachment and the BGP session will appear on the GCP console.
# Creating MVE Connections to Latitude.sh with Cisco SD-WAN
Source: https://docs.megaport.com/cloud/mve/cisco/latitude-sh/index
This help topic describes how to create a connection from a Cisco SD-WAN MVE to Latitude.sh.
This topic describes how to create a VXC from MVE to Latitude.sh bare metal cloud using the Megaport Portal, and how to configure BGP in to bring the connection up.
BGP is required for all Latitude.sh connections. To create a connection, specify an ASN, BGP password, and the prefixes to advertise. The connection becomes live after Latitude.sh approves the request.
## Prerequisites
The MVE must be in the active state before you create a connection.
## Adding the Latitude.sh connection in the Megaport Portal
To set up a connection to Latitude.sh with Megaport, you need to create a VXC from your MVE in the Megaport Portal to the Latitude.sh location where you have provisioned your Latitude.sh services.
**To create a connection to Latitude.sh from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection**, click **Cloud**, then click **Compute via Latitude.sh**.
3. Select the target location for your connection then click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc/).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you don't specify a value, Megaport assigns one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.\
A summary page appears that includes the monthly cost.
6. Click **Back** to make changes, or click **Add VXC**.
7. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
8. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
9. Click **Order Now**.
The connection becomes live after Latitude.sh approves the request.
After ordering, the connection status shows *Deployable* until it is provisioned. When Latitude.sh approves the connection and provisioning is complete, the status updates to *Configured*.
## Adding the Latitude.sh connection to vManage
To set up the connection in vManage, you need a dedicated device template and feature templates for the device-specific configuration details: a Service VPN template, a Cisco BGP template, and a CLI add-on template.
For more information about creating and applying device and feature templates, see [Cisco: Create a Device Template from Feature Templates](https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/system-interface/vedge/systems-interfaces-book/configure-devices.html).
For more information about configuring the BGP feature template, see [Cisco: Configure BGP](https://www.cisco.com/c/en/us/td/docs/routers/sdwan/26x-later/routing/routing-configuration-guide/border-gateway-protocol/configure-bgp.html).
## Validating your Latitude.sh connection
You can verify the connection by opening an SSH session to the MVE from Tools > SSH Terminal in vManage. Confirm that the VXC interface can reach the remote end and that the BGP session is established.
For more information, see [Cisco: Configure BGP](https://www.cisco.com/c/en/us/td/docs/routers/sdwan/26x-later/routing/routing-configuration-guide/border-gateway-protocol/configure-bgp.html).
## Helpful references
* [Connecting to Latitude.sh](/portal-admin/connect-latitude)
* [Creating an MVE Integrated with Cisco Overview](/mve/cisco/creating/overview)
* Latitude.sh docs
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Creating MVE Connections to Any Endpoint with Fortinet SD-WAN
Source: https://docs.megaport.com/cloud/mve/fortinet/generic/index
This help topic describes how to create a VXC from an MVE to Cloud Partners and integrate the connection with Fortinet SD-WAN.
This topic describes the general steps to configure and deploy a Megaport VXC connection in the Megaport Portal and integrate it with an MVE in Fortinet SD-WAN. The VXC can connect to a Cloud Service Provider, a Port, or an MCR.
#### Step 1 -- Create an MVE
* Create an MVE in the Megaport Portal.\
For more information, see [Creating an MVE](/mve/fortinet/creating-mve).
The MVE needs to be in the active state.
#### Step 2 -- Create a VXC from the MVE
1. In the Megaport Portal, select the MVE created in Step 1.
2. Create a VXC to another MVE, a Port, or Cloud Service Provider.\
For more information, see [Creating a VXC](/connections/overview#create_vxc).
Ensure both ends of the connection are active and have BGP configured.
3. In the connection details, note the A-End VLAN.
#### Step 3 -- Collect these values for the connection
* MVE IP address
* MVE VLAN (A-End)
* MVE ASN
* Cloud/B-End IP address
* B-End ASN
* MD5 Password
#### Step 4 -- Create an interface in FortiManager
1. Log in to the FortiManager.
You can also log in on your MVE instance: https\://\
2. From your managed device, go to the **System** menu and choose **Interface**.
The page displays **port1** as your physical interface.
3. Click **+Create New > Interface** and provide this information:
* **Interface Name** -- Specify a meaningful name for the interface.
* **Alias Name** (optional) -- Enter an alternate name.
* **Type** -- Choose VLAN.
* **Interface** -- Choose the parent interface: `port1`.
* **VLAN ID** -- Specify the A-End VLAN for the connection.
* **Role** -- Choose Undefined.
* **Addressing Mode** -- Select Manual.
* **IP/Netmask** -- The IP address/netmask for the MVE.
* **Administrative Access** - Specify how you want to access this interface, such as HTTPS, PING, and SSH.
* **DHCP Server** - Click **OFF**.
4. Click **OK**.\
The new VLAN interface appears with your `port1` physical interface.
You can run an `execute ping` command from FortiOS to verify the connection.
#### Step 5 -- Configure BGP
At this point, we have created the interface and next we need to create the BGP session.
1. In FortiManager, go to **Router > BGP**.
2. Provide this information:
* **Local AS** -- Provide the ASN for the MVE connection.
* **Router ID** -- Enter the B-End IP address (cloud provider, port, or other MVE).
3. In Neighbors, click **+Create New**.
4. For the neighbor **IP**, add the B-End IP address (cloud provider, Port, or other MVE).
5. For **Remote ASN**, enter the ASN of the B-End.
6. Click **OK**.
7. Click **Apply**.\
The neighbor is configured but we need to add the BGP Auth information. The web interface does not let you define this and you need to use the command line to add the BGP details.
8. SSH to the MVE instance using your private key file.\
For example\
`ssh -i ~/.ssh/megaport-mve-instance-1-2048 admin@162.43.143.XX`
9. Use these commands to add a password for the BGP neighbor.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
config router bgp
config neighbor
edit ""
set password
next
end
```
#### Step 6 -- Validating your connection
You can review connection details, including the connection state, from the CLI with these commands:
* `get system interface` -- Displays configuration details and current status for the device interfaces.
* `get router info bgp neighbor ` -- Displays configuration details and current status for the BGP neighbors.
# Creating a Google Cloud Services Connection for an MVE with Fortinet SD-WAN
Source: https://docs.megaport.com/cloud/mve/fortinet/google/index
This help topic describes how to provision connections between MVE and Google Cloud Services and integrate the connection with Fortinet SD-WAN.
You can create a network connection from an MVE (a FortiGate) to Google Cloud through Partner Interconnect.
When connecting to Google Cloud Platform (GCP) through Partner Interconnect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection and Layer 3 BGP is established directly between the customer and GCP.
Before you begin, create an MVE (FortiGate) in FortiManager. For more information, see [Creating an MVE](/mve/fortinet/creating-mve). The MVE needs to be in the active state.
There are three parts to adding a Google Cloud connection to your MVE and FortiManager.
1. Create a Partner Interconnect attachment in Google Cloud Console or gcloud CLI. Copy the pairing key that is provided as part of the attachment creation.
For additional details, see the Google documentation on
[Google Partner Interconnects](https://cloud.google.com/interconnect/docs/how-to/partner/provisioning-overview).
2. In the Megaport Portal, create a VXC from your MVE to connect to your Google Cloud attachment.
3. In FortiManager, create a new interface and add the details of the Google Cloud connection.
These instructions step through the second and third parts.
MVE for Fortinet SD-WAN requires configuration steps in both FortiManager and the Megaport Portal for all cloud connections.
## Adding the Google Cloud connection in the Megaport Portal
To set up the GCP connection, you need to create the connection in the Megaport Portal.
**To create a connection to GCP from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select Google as the provider.
To check the latency and price of connecting to a particular Google location, click **View all Google Partner locations**. You can proceed to the Connection Details page without a pairing key and review the pricing of the selected port. To place an order for a Google connection, you need to provide a pairing key.
4. Copy and paste the pairing key from the Google Cloud console into the Google Partner Pairing Key field.\
The relevant Google targets appear based on the region of your GCI Partner connection.
5. Select the target location for your connection then click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Enter the same rate you selected for your Google port speed.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/fortinet/creating-mve#creating-mve).
* **Preferred A-End VLAN** -- The VLAN for this connection that you will receive through the MVE. This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
11. Once you have deployed the VXC, go back to your attachment in the Google Cloud Console and accept the attachment.\
You will be provided your private IP address from Google to configure BGP.\
Ensure that you pre-activate the attachment or mark the attachment as active after configuring the VXC. Otherwise, you cannot set up BGP with your SD-WAN instance.
The Google ASN will always be 16550.
## Adding the Google Cloud connection to FortiManager
After you create the connection from your MVE to Google Cloud and set up the connection in the Google console, you need to configure it in FortiManager. This involves configuring BGP settings, ASNs, and VLANs.
**To add the Google Cloud connection in FortiManager**
1. Collect the connection details from the Google console.\
Display the details of the connection you created in Google Cloud for this connection. Note the values for the **Peer ASN**, **Cloud Router BGP IP**, and **BGP Peer ID**.
2. Collect the connection details from the Megaport Portal.\
Click the gear icon for the Google connection from your MVE and click the Details view.
Note the value for the **A-End VLAN**.
3. Log in to the FortiManager.
You can also log in on your MVE instance: https\://\
4. From your managed device, go to the **System** menu and choose **Interface**.
The page displays **port1** as your physical interface.
5. Click **+Create New > Interface** and provide this information:
* **Interface Name** -- Specify a meaningful name for the interface.
* **Alias Name** (optional) -- Enter an alternate name.
* **Type** -- Choose VLAN.
* **Interface** -- Choose the parent interface: `port1`.
* **VLAN ID** -- Specify the A-End VLAN listed for this Google Connection in the Megaport Portal.
* **Role** -- Choose Undefined.
* **Addressing Mode** -- Select Manual.
* **IP/Netmask** -- These values are available in the VLAN attachment details in the Google Cloud console. The IP address appears in the **BGP Peer IP** field.
* **Administrative Access** - Specify how you want to access this interface, such as HTTPS, PING, and SSH.
* **DHCP Server** - Click **OFF**.
6. Click **OK**.\
The new VLAN interface appears with your `port1` physical interface.
You can run an `execute ping` command from FortiOS to verify the connection.
You need to push the configuration to the MVE, which happens when you have AutoUpdate configured. If you cannot successfully ping the connection, go to Manage Devices in FortiManager, select the MVE, and choose **Refresh Device** from the More menu. If prompted, select AutoUpdate for the **Config Status**.
At this point, we have created the interface and next we need to create the BGP session.
1. In FortiManager, go to **Router > BGP**.
2. Provide this information:
* **Local AS** -- Provide the ASN for the MVE connection. Specify the **Peer ASN** that you defined in the BGP configuration for the VLAN attachment in the Google Cloud console.
* **Router ID** -- Specify the **Cloud Router BGP IP** from the VLAN attachment details in the Google Cloud console.
3. In Neighbors, click **+Create New**.
4. For the neighbor **IP**, add the **Cloud Router BGP IP** from the VLAN attachment details in the Google Cloud console.
5. For **Remote ASN**, enter the Google Cloud ASN of 16550.\
This is a fixed value, and appears in the connection details on the Google console.
6. Click **OK**.
7. Click **Apply**.
Google Cloud requires BGP multihop support. You can configure multihop support from the Fortinet CLI with these commands:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
config router bgp
config neighbor
edit ""
set ebgp-enforce-multihop enable
next
end
```
## Validating your Google Cloud connection
You can review connection details, including the connection state, from the Fortinet CLI with these commands:
* `get system interface` -- Displays configuration details and current status for the device interfaces.
* `get router info bgp neighbor ` -- Displays configuration details and current status for the BGP neighbors.
# Creating MVE Connections to Latitude.sh with Fortinet FortiGate
Source: https://docs.megaport.com/cloud/mve/fortinet/latitude-sh/index
This help topic describes how to create a connection from a Fortinet FortiGate MVE to Latitude.sh.
This topic describes how to create a VXC from MVE to Latitude.sh bare metal cloud using the Megaport Portal, and how to configure BGP in to bring the connection up.
BGP is required for all Latitude.sh connections. To create a connection, specify an ASN, BGP password, and the prefixes to advertise. The connection becomes live after Latitude.sh approves the request.
## Prerequisites
The MVE must be in the active state before you create a connection.
## Adding the Latitude.sh connection in the Megaport Portal
To set up a connection to Latitude.sh with Megaport, you need to create a VXC from your MVE in the Megaport Portal to the Latitude.sh location where you have provisioned your Latitude.sh services.
**To create a connection to Latitude.sh from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection**, click **Cloud**, then click **Compute via Latitude.sh**.
3. Select the target location for your connection then click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc/).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you don't specify a value, Megaport assigns one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.\
A summary page appears that includes the monthly cost.
6. Click **Back** to make changes, or click **Add VXC**.
7. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
8. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
9. Click **Order Now**.
The connection becomes live after Latitude.sh approves the request.
After ordering, the connection status shows *Deployable* until it is provisioned. When Latitude.sh approves the connection and provisioning is complete, the status updates to *Configured*.
## Adding the Latitude.sh connection to FortiManager
To add the connection to FortiManager, you will need the following information:
* MVE IP address
* MVE VLAN (A-End)
* MVE ASN
* Cloud/B-End IP address
* B-End ASN
* MD5 Password
After you create the connection from your MVE to Latitude.sh, you need to configure a VLAN interface and a BGP session for it in FortiManager. The BGP MD5 password must be set using the FortiOS CLI, since the FortiManager web interface does not support it.
For more information about configuring the interface, see [Fortinet: Configuring Network Interfaces](https://docs.fortinet.com/document/fortimanager/latest/administration-guide/578841/configuring-network-interfaces).
For more information about configuring BGP, see [Fortinet: Configure BGP Neighbor](https://docs.fortinet.com/document/fortimanager/latest/administration-guide/726126/bgp-neighbors).
## Validating your Latitude.sh connection
You can review connection details, including the connection and BGP session state, from the FortiOS CLI.
For more information, see [Fortinet: Configure BGP Neighbor](https://docs.fortinet.com/document/fortimanager/latest/administration-guide/726126/bgp-neighbors).
## Helpful references
* [Connecting to Latitude.sh](/portal-admin/connect-latitude)
* [Creating an MVE Integrated with Fortinet](/mve/fortinet/creating-mve)
* Latitude.sh docs
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Creating MVE Connections to Any Endpoint with Palo Alto VM-Series
Source: https://docs.megaport.com/cloud/mve/palo-alto/generic/index
This help topic describes how to create a VXC from an MVE to Cloud Partners and integrate the connection with Palo Alto VM-Series.
This topic describes the general steps to configure and deploy a Megaport VXC connection in the Megaport Portal and integrate it with an MVE in Palo Alto VM-Series. The VXC can connect to a Cloud Service Provider, a Port, or an MCR.
#### Step 1 -- Create an MVE
* Create an MVE in the Megaport Portal.\
For more information, see [Creating an MVE](/mve/palo-alto/creating-mve).
The MVE needs to be in the active state.
#### Step 2 -- Create a VXC from the MVE
1. In the Megaport Portal, select the MVE created in Step 1.
2. Create a VXC to another MVE, a Port, or Cloud Service Provider.\
For more information, see [Creating a VXC](/connections/overview#create_vxc).
Ensure both ends of the connection are active and have BGP configured.
3. In the connection details, note the A-End VLAN.
#### Step 3 -- Collect these values for the connection
* MVE IP address
* MVE VLAN (A-End)
* MVE ASN
* Cloud/B-End IP address
* B-End ASN
* MD5 Password
#### Step 4 -- Create an interface in VM-Series
1. Log in to VM-Series.
2. Choose Network > Interfaces.
3. Click **Add Subinterface**.
4. Provide these details:
* **Interface Name** -- Specify a meaningful name for the interface.
* **Comment** -- Enter an alternate name.
* **Tag** -- Specify the A-End inner VLAN value for the connection.
* **Virtual Router** -- Select a virtual router to the interface, as required by your network.
* **Type** -- Choose VLAN.
5. Select the **IPv4** tab.
6. Select **Static** as the Type.
7. Click **+Add** to add a new IP address.
8. Enter the IPv4 address and netmask for the MVE.
9. Click **OK**.
10. Click **Commit** in the top right corner.
11. Review the changes and click **Commit**.
The new VLAN interface appears with your physical interface.
Next, you will create a security zone so the interface can route traffic.
**To create a security zone**
1. Select the `ethernet1/1.1010` subinterface.
2. Select New Zone from the Security Zone drop-down list.
3. Specify a name for the security zone.
4. Click **+Add** under Interfaces and add `ethernet1/1.1010` to the security zone.
5. Specify any additional details as required for your network security.
6. Select New Zone Protection Profile from the Zone Protection Profile drop-down list.
7. Specify any details as required for your network security. This example uses all the defaults.
8. Click **OK**.
9. Click **OK** in the Layer3 Subinterface screen.
10. Click **Commit** in the top right corner.
11. Review the changes and click **Commit**.
#### Step 5 -- Configure BGP
**To create the BGP session**
1. In VM-Series, choose Network > Virtual Routers.
2. Select the virtual router.
3. In the left pane, select BGP.
4. Provide the following BGP details:
* **Enable** -- Select this check box to start the BGP session after committing these changes.
* **Router ID** -- Enter the B-End IP address (cloud provider, port, or other MVE).
* **AS Number** -- Provide the ASN for the MVE connection.
5. Click **+Add** under Auth Profiles.
6. Specify a Profile Name.
7. Enter and confirm the auth password.
8. Click **OK**.
9. Select the **Peer Group** tab.
10. Click **+Add** to add a peer group.
11. Specify a name for the peer group.
12. Specify eBGP as the session type.
13. Specify any additional details as required for your network.
14. Click **+Add** to add a new peer.
15. Specify the details for the peer:
* **Name** -- Specify a name for the peer.
* **Peer AS** -- Specify the B-End autonomous system number (ASN).
* **Local Address** -- Select the proper subinterface and IP address from the drop-down list.
* **Peer Address** -- Enter the B-End IPv4 address.
16. Select the **Connection Options** tab.
17. Select the previously created Auth Profile.
18. Click **OK** in the Peer Group - Peer screen.
19. Click **OK** in the BGP - Peer Group/Peer screen.
20. Click **OK** in the Virtual Router screen.
21. Click **Commit** in the top right corner.
22. Review the changes and click **Commit**.
#### Step 6 -- Validating your connection
**To check the connection status**
1. Choose Network > Virtual Routers.
2. Locate your virtual router (default).
3. Click **More Runtime Stats** in the Runtime Stats column on the right.
4. Select the **BGP** tab, and then select the **Peer** tab.
5. Verify that the peer status is *Established*.
# Creating a Google Cloud Services Connection for an MVE with Palo Alto VM-Series
Source: https://docs.megaport.com/cloud/mve/palo-alto/google/index
This help topic describes how to provision connections between MVE and Google Cloud Services and integrate the connection with Palo Alto VM-Series.
You can create a network connection from an MVE (a Palo Alto VM-Series) to Google Cloud through Partner Interconnect.
When connecting to Google Cloud Platform (GCP) through Partner Interconnect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection and Layer 3 BGP is established directly between the customer and GCP.
Before you begin, create an MVE (VM-Series firewall). For more information, see [Creating an MVE](/mve/palo-alto/creating-mve). The MVE needs to be in the active state.
There are three parts to adding a Google Cloud connection to your MVE and VM-Series.
1. Create a Partner Interconnect attachment in Google Cloud Console or gcloud CLI. Copy the pairing key that is provided as part of the attachment creation.
For additional details, see the Google documentation on [Google Partner Interconnects](https://cloud.google.com/interconnect/docs/how-to/partner/provisioning-overview).
2. In the Megaport Portal, create a VXC from your MVE to connect to your Google Cloud attachment.
3. In VM-Series, create a new interface and add the details of the Google Cloud connection.
These instructions step through the second and third parts.
MVE for Palo Alto VM-Series requires configuration steps in both VM-Series and the Megaport Portal for all cloud connections.
## Adding the Google Cloud connection in the Megaport Portal
To set up the GCP connection, you need to create the connection in the Megaport Portal.
**To create a connection to GCP from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select Google as the provider.
To check the latency and price of connecting to a particular Google location, click **View all Google Partner locations**. You can proceed to the Connection Details page without a pairing key and review the pricing of the selected port. To place an order for a Google connection, you need to provide a pairing key.
4. Copy and paste the pairing key from the Google Cloud console into the Google Partner Pairing Key field.\
The relevant Google targets appear based on the region of your GCI Partner connection.
5. Select the target location for your connection then click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Enter the same rate you selected for your Google port speed.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/palo-alto/creating-mve#creating-mve).
* **Preferred A-End VLAN** -- The VLAN for this connection that you will receive through the MVE. This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
11. Once you have deployed the VXC, go back to your attachment in the Google Cloud Console and accept the attachment.\
You will be provided your private IP address from Google to configure BGP.\
Ensure that you pre-activate the attachment or mark the attachment as active after configuring the VXC. Otherwise, you cannot set up BGP with your SD-WAN instance.
The Google ASN will always be 16550.
## Adding the Google Cloud connection to VM-Series
After you create the connection from your MVE to Google Cloud and set up the connection in the Google console, you need to configure it in VM-Series. This involves configuring BGP settings, ASNs, and VLANs.
**To add the Google Cloud connection in VM-Series**
1. Collect the connection details from the Google console.\
Display the details of the connection you created in Google Cloud for this connection. Note the values for the **Peer ASN**, **Cloud Router BGP IP**, and **BGP Peer ID**.
2. Collect the connection details from the Megaport Portal.\
Click the gear icon for the Google connection from your MVE and click the Details view. Note the value for the **A-End VLAN**.
3. Log in to the VM-Series.
4. Choose Network > Interfaces.
5. Select the A-End MVE (`ethernet1/1`).
6. Click **Add Subinterface**.
7. Provide these details:
* **Interface Name** -- Enter a name for the subinterface. In the adjacent field, enter a number to identify the subinterface.
* **Comment** -- Enter an alternate name.
* **Tag** -- Specify the A-End VLAN associated with this Google Connection in the Megaport Portal.
* **Virtual Router** -- Select a virtual router to the interface, as required by your network.
8. Select the **IPv4** tab.
9. Select **Static** as the Type.
10. Click **+Add** to add a new IP address.
11. Enter the IPv4 address and netmask.\
These values are available in the VLAN attachment details in the Google Cloud console. The IP address appears in the **BGP Peer IP** field.
12. Click **OK**.
13. Click **Commit** in the top right corner.
14. Review the changes and click **Commit**.
The new VLAN interface appears with your `ethernet1/1` physical interface.
Next, you will create a security zone so the interface can route traffic.
**To create a security zone**
1. Select the `ethernet1/1.1010` subinterface.
2. Select New Zone from the Security Zone drop-down list.
3. Specify a name for the security zone.
4. Click **+Add** under Interfaces and add `ethernet1/1.1010` to the security zone.
5. Specify any additional details as required for your network security.
6. Select New Zone Protection Profile from the Zone Protection Profile drop-down list.
7. Specify any details as required for your network security. This example uses all the defaults.
8. Click **OK**.
9. Click **OK** in the Layer3 Subinterface screen.
10. Click **Commit** in the top right corner.
11. Review the changes and click **Commit**.
At this point, you have created the interface. Next, you will create the BGP session.
**To create the BGP session**
1. In VM-Series, choose Network > Virtual Routers.
2. Select the virtual router.
3. In the left pane, select BGP.
4. Provide the following BGP details:
* **Enable** -- Select this check box to start the BGP session after committing these changes.
* **Router ID** -- Specify the **Cloud Router BGP IP** from the VLAN attachment details in the Google Cloud console.
* **AS Number** -- Provide the ASN for the MVE connection. Specify the **Peer ASN** that you defined in the BGP configuration for the VLAN attachment in the Google Cloud console.
5. Click **+Add** under Auth Profiles.
6. Specify a Profile Name.
7. Enter and confirm the auth password.
8. Click **OK**.
9. Select the **Peer Group** tab.
10. Click **+Add** to add a peer group.
11. Specify a name for the peer group. For example, AWS-xxxx.
12. Specify eBGP as the session type.
13. Specify any additional details as required for your network.
14. Click **+Add** to add a new peer.
15. Specify the details for the peer:
* **Name** -- Specify a name for the peer.
* **Peer AS** -- Specify the Google-side autonomous system number (ASN) of 16550. This is a fixed value, and appears in the connection details on the Google console.
* **Local Address** -- Select the proper subinterface and IP address from the drop-down list.
* **Peer Address** -- Enter the **Cloud Router BGP IP** from the VLAN attachment details in the Google Cloud console.
Google Cloud requires BGP multihop support. You can configure multihop support from VM-Series, in the Connection Options tab of the BGP peer:
## Validating your Google Cloud connection
**To check the status of the BGP peer**
1. Choose Network > Virtual Routers.
2. Locate your virtual router (default).
3. Click **More Runtime Stats** in the Runtime Stats column on the right.
4. Select the **BGP** tab, and then select the **Peer** tab.
5. Verify that the peer status is *Established*.
# Creating MVE Connections to Latitude.sh with Palo Alto Networks
Source: https://docs.megaport.com/cloud/mve/palo-alto/latitude-sh/index
This help topic describes how to create a connection from a Palo Alto Networks MVE to Latitude.sh.
This topic describes how to create a VXC from MVE to Latitude.sh bare metal cloud using the Megaport Portal, and how to configure BGP in to bring the connection up.
BGP is required for all Latitude.sh connections. To create a connection, specify an ASN, BGP password, and the prefixes to advertise. The connection becomes live after Latitude.sh approves the request.
## Prerequisites
The MVE must be in the active state before you create a connection.
## Adding the Latitude.sh connection in the Megaport Portal
To set up a connection to Latitude.sh with Megaport, you need to create a VXC from your MVE in the Megaport Portal to the Latitude.sh location where you have provisioned your Latitude.sh services.
**To create a connection to Latitude.sh from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection**, click **Cloud**, then click **Compute via Latitude.sh**.
3. Select the target location for your connection then click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc/).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you don't specify a value, Megaport assigns one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.\
A summary page appears that includes the monthly cost.
6. Click **Back** to make changes, or click **Add VXC**.
7. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
8. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
9. Click **Order Now**.
The connection becomes live after Latitude.sh approves the request.
After ordering, the connection status shows *Deployable* until it is provisioned. When Latitude.sh approves the connection and provisioning is complete, the status updates to *Configured*.
## Adding the Latitude.sh connection to VM-Series
To add the connection to VM-Series, you will need the following information:
* MVE IP address
* MVE VLAN (A-End)
* MVE ASN
* Cloud/B-End IP address
* B-End ASN
* MD5 Password
After you create the connection from your MVE to Latitude.sh, you need to configure a Layer 3 subinterface, a security zone, and a BGP session for it in VM-Series.
For more information about configuring the interface, see [Palo Alto Networks: Configure Layer 3 Interfaces](https://docs.paloaltonetworks.com/ngfw/networking/configure-interfaces/layer-3-interfaces/configure-layer-3-interfaces).
For more information about configuring BGP, see [Palo Alto Networks: Configure BGP](https://docs.paloaltonetworks.com/ngfw/networking/bgp/configure-bgp).
## Validating your Latitude.sh connection
You can review the BGP peer status in VM-Series under Network > Virtual Routers > Runtime Stats. Verify that the peer status is *Established*.
For more information, see [Palo Alto Networks: Configure BGP](https://docs.paloaltonetworks.com/ngfw/networking/bgp/configure-bgp).
## Helpful references
* [Connecting to Latitude.sh](/portal-admin/connect-latitude)
* [Creating a VM-Series MVE](/mve/palo-alto/creating-mve)
* Latitude.sh docs
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Creating an Azure Connection for an MVE with Versa Secure SD-WAN
Source: https://docs.megaport.com/cloud/mve/versa/azure/index
This help topic describes how to create a VXC from an MVE to Microsoft Azure ExpressRoute and integrate the connection with Versa Secure SD-WAN.
You can create a network connection from an MVE (a Versa Controller) to Azure ExpressRoute with Virtual Cross Connects (VXCs). You can create either a private connection or a public (Microsoft) connection.
Before you begin, create an MVE in Versa Director. For more information, see [Creating an MVE Integrated with Versa](/mve/versa/creating-mve).
There are three parts to adding an ExpressRoute connection to your MVE and Versa SD-WAN.
1. Set up your ExpressRoute plan and deploy the ExpressRoute circuit in the Azure console. When deployed, you get a service key. For additional details, see the Microsoft [ExpressRoute documentation](https://docs.microsoft.com/en-us/azure/expressroute/).
To check the latency and price of connecting to a particular Azure Partner location, start the procedure to [add a connection to Microsoft Azure](#azure-vxc) but instead of providing a **Microsoft Azure Service Key**, click **View all Azure Partner locations**. You can proceed to the Connection Details page without a service key and review the pricing of the selected port. To place an order for a Microsoft Azure connection, you need to provide a service key.
2. In the Megaport Portal, create a connection (VXC) from your MVE to your ExpressRoute location.
3. In Versa Director, create a new interface and add the details of the ExpressRoute connection.
The instructions in this topic describe the second and third parts.
MVE for Versa SD-WAN requires configuration steps in both Versa Director and the Megaport Portal for all cloud connections.
## Adding the ExpressRoute connection in the Megaport Portal
To set up the ExpressRoute connection, you need to create the connection in the Megaport Portal.
**To create a connection to ExpressRoute from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE you want to use.
2. Click **+Connection** on the MVE.
3. Click the **Cloud** tile.
4. Select Microsoft Azure as the provider.
5. Add the ExpressRoute service key into the **Microsoft Azure Service Key** field.\
The Portal verifies the key then displays the available port locations based on the ExpressRoute region. For example, if your ExpressRoute service is deployed in the Australia East region in
Sydney, you can select the Sydney locations.
6. Select the connection point for your first connection.\
To deploy a second connection (and this is recommended), you can create a second VXC - enter the same service key and select the other connection location.
Some helpful links appear on the configuration screen to resources including the Azure Resource Manager console and some tutorial videos.
7. Click **Next**.
8. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The rate limit for the VXC will be capped at the maximum allowable based on the ExpressRoute service key.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/versa/creating-mve#creating-mve).
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection (for ExpressRoute this is the S-Tag). This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
* **Configure Single Azure Peering VLAN** -- By default, this option is enabled for MVE and we strongly recommend keeping it enabled with Versa SD-WAN.\
This option provides a single tag VLAN solution. You configure peering in Azure with the MVE VLAN (A-End) and the peer VLAN set in Azure (B-End). Note, you can have only one peering type (Private or Microsoft) per VXC with this option.
If you do not enable this option, the VXC appears active but it does not recognize traffic.
* **Azure Peering VLAN** -- This value needs to match the A-End VLAN for single tag VLAN peering. A different Azure peering VLAN can also be set, if required.
9. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
When the VXC configuration completes, the VXC icon is green.
In the Azure Resource Management console, the provider status will be `Provisioned`.
When provisioned, you need to configure peerings. You can configure private and Microsoft peering. Click the peer to configure and provide these details:
* **Peer ASN** -- Enter the ASN for the MVE.
* **IPv4 Subnets** -- From each of these subnets, MVE uses the first usable IP address and Microsoft uses the second usable IP for its router.
* **VLAN ID** -- Enter the A-End VLAN from the MVE. (Note, the VLAN ID in the Azure console can be different from the A-End VLAN.)
* **Shared Key** (optional) -- Enter an password for BGP.
## Adding the ExpressRoute connection to Versa Director
After you create the connection from your MVE to Azure and set up the connection in the Azure console, you need to configure it in Versa Director. This involves creating an interface and configuring BGP settings, ASNs, VLANs, and MD5 values.
**To add the Azure Cloud connection in Versa Director**
1. Collect the connection details from the Azure console.\
Display the details of the connection you created in Azure for this connection. Note the values for the **Peer ASN**, **Shared Key**, **VLAN ID**, and **IPv4 Primary Subnet**.
2. Collect the connection details from the Megaport Portal.\
Click the gear icon for the Azure connection from your MVE and click the Details view.
Note the value for the **A-End VLAN**.
3. Log in to Versa Director.
4. Select the **Workflows** tab in the top menu bar.
5. Select Template > Templates in the left menu bar.
6. Select the template associated with this device.
7. Select the **Interfaces** tab.
8. Under WAN Interfaces, click (Add) to add a subinterface.
9. In the **VLAN ID** field, enter the VLAN value from the Megaport Portal.\
Specify the A-End VLAN for the connection - click the details icon for the connection in the Portal to find this value.
10. In the Network Name column, choose **+ Create WAN Network** from the menu.\
Or select a previously created network, if appropriate.
11. For a new network, enter a name and optionally, a description.
12. Click **OK**.
13. In the IPv4 column, choose **Static** from the menu.
14. Select the **Routing** tab.
15. In the BGP section, select the network created earlier.
16. Enter in the following values for your connection:
* **Local AS** -- The AS value for the A-End of the connection.
* **Neighbor IP** -- The IP address of the Azure side of the connection. These values are available in the Azure console. The IP addresses and CIDR appear in the **IPv4 Primary Subnet** field; MVE uses the first usable IP address and Azure uses the second usable IP for its router. For this field, enter the MVE (first usable) IP address.
* **Peer AS** -- Enter the Azure-side ASN of 12076. This is a fixed value, and appears in the connection details on the Azure console.
* Optionally, enable BFD.
17. Click (Add).
18. Click **Recreate** at the bottom of the page.\
A screen appears that highlights the differences in the configuration.
19. Click **Deploy**.
20. Select the **Configuration** tab in the top menu bar.
21. Select Templates > Device Templates in the horizontal menu bar.
22. Click the template you want to modify.
23. In the side navigation, select Virtual Routers.
24. Click the link for the subinterface network.
25. In the side navigation, select BGP.
26. Click the Instance ID for your network.
27. Click (Parameterize) to use variables for the Router ID and the Password fields.\
You can also parameterize Local AS and Peer AS fields - otherwise it will use the static values provided in earlier steps.
Static Address is parameterized by default.
28. Click **OK** two times to return to the main window.
At this point, we have created the interface and next we need to configure the device and create the BGP session.
1. In Director, select the **Workflows** tab in the top menu bar.
2. Select Devices > Devices in the left navigation.
3. Click the device to modify.
4. Select the **Bind Data** tab.
5. Enter the values for IPv4 Static Address, BGP Password, BGP Router ID, and Hop Address.\
Other values, such as the Local and Peer AS are auto-populated from our earlier settings.
* **Static Address** -- Enter the Customer IP address (your local IP address, including the mask value).
* **Password** -- Add the BGP Auth information if you defined this in the Azure console. (This was optional.)
* **BGP Router ID** -- Enter the Customer IP address (your local IP address, including the mask value) from the MVE details.
* **Hop Address** - The IP address for the Azure side of the connection. Enter the second usable IP address from the **IPv4 Primary Subnet** from the Azure console.
6. Click **Deploy**.
7. In the upper right of the screen under your username, click **Commit Template**.
8. Select your **Organization** and **Template**.\
In the lower part of the screen, the Template State will be OUT-OF-SYNC.
9. Click the eye icon in the Differences column.\
A page appears that highlights the differences in the configuration.
10. If you are satisfied with the configuration, click **Commit to Device**.
## Validating your Azure connection
You can review device status, including the connection state, from the Monitor tab in Director.
1. Select the **Monitor** tab in the top menu bar.
2. Select Devices in the horizontal menu bar.
3. Click the device to review status and activity.
# Creating MVE Connections to Any Endpoint with Versa Secure SD-WAN
Source: https://docs.megaport.com/cloud/mve/versa/generic/index
This help topic describes how to create a VXC from an MVE to Cloud Partners and integrate the connection with Versa Secure SD-WAN.
This topic describes the general steps to configure and deploy a Megaport VXC connection in the Megaport Portal and integrate it with an MVE in Versa Secure SD-WAN. The VXC can connect to a Cloud Service Provider, a Port, or an MCR.
#### Step 1: Create an MVE
* Create an MVE in the Megaport Portal.\
For more information, see [Creating an MVE](/mve/versa/creating-mve).
The MVE needs to be in the active state.
#### Step 2: Create a VXC from the MVE
1. In the Megaport Portal, select the MVE created in Step 1.
2. Create a VXC to another MVE, a Port, or Cloud Service Provider.\
For more information, see [Creating a VXC](/connections/overview#create_vxc).
Ensure both ends of the connection are active and have BGP configured.
3. In the connection details, note the A-End VLAN.
#### Step 3: Collect these values for the connection
* MVE IP address
* MVE VLAN (A-End)
* MVE ASN
* Cloud/B-End IP address
* B-End ASN
* MD5 Password
#### Step 4: Create an interface in Versa Director
1. Log in to Versa Director.
2. Select the **Workflows** tab in the top menu bar.
3. Select Template > Templates in the left menu bar.
4. Select the template associated with this device.
5. Select the **Interfaces** tab.
6. Under WAN Interfaces, click (Add) to add a subinterface.
7. In the **VLAN ID** field, enter the VLAN value from the Megaport Portal.\
Specify the A-End VLAN for the connection - click the details icon for the connection in the Portal to find this value.
8. In the Network Name column, choose **+ Create WAN Network** from the menu.\
Or select a previously created network, if appropriate.
9. For a new network, enter a name and optionally, a description.
10. Click **OK**.
11. In the IPv4 column, choose **Static** from the menu.
12. Select the **Routing** tab.
13. In the BGP section, select the network created earlier.
14. Enter in the following values for your connection:
* **Local AS** -- The AS value for the A-End of the connection.
* **Neighbor IP** -- The IP address of the B-End of the connection (cloud provider, port, or other MVE).
* **Peer AS** -- The AS value for the B-End of the connection.
* Optionally, enable BFD.
15. Click (Add).
16. Click **Recreate** at the bottom of the page.\
A screen appears that highlights the differences in the configuration.
17. Click **Deploy**.
18. Select the **Configuration** tab in the top menu bar.
19. Select Templates > Device Templates in the horizontal menu bar.
20. Click the template you want to modify.
21. In the side navigation, select Interfaces.
22. Click the vni-0/0 interface.
23. Click the VLAN value of the new subinterface.
24. In the Static Address section, click (Parameterize) to use a variable for the static IP address value. (This is enabled by default.)\
When parameterized, the icon is green. Click it if you need to change it. The parameterized field ensures each device associated with the template has a unique variable for the IP address.
25. Click **OK** two times to update the VNI.
26. In the side navigation, select Virtual Routers.
27. Click the Transport-VR link for your network.
28. In the side navigation, select BGP.
29. Click the Instance ID for your network.
30. Click (Parameterize) to use variables for the Router ID and the Password fields.
31. Click **OK** two times to return to the main window.
#### Step 5: Configure the device
1. Select the **Workflows** tab in the top menu bar.
2. Select Devices > Devices in the left navigation.
3. Click the device to modify.
4. Select the **Bind Data** tab.
5. Enter the values for Static Address, BGP Password, and BGP Router ID.\
Other values, such as the Local and Peer AS are auto-populated from our earlier settings.
6. Click **Deploy**.
7. In the upper right of the screen under your username, click **Commit Template**.
8. Select your **Organization** and **Template**.\
In the lower part of the screen, the Template State will be OUT-OF-SYNC.
9. Click the eye icon in the Differences column.\
A page appears that highlights the differences in the configuration.
10. If you are satisfied with the configuration, click **Commit to Device**.
#### Step 6: Validating your connection
You can review device status, including the connection state, from the Monitor tab in Director.
1. Select the **Monitor** tab in the top menu bar.
2. Select Devices in the horizontal menu bar.
3. Click the device to review status and activity.
# Creating a Google Cloud Services Connection for an MVE with Versa Secure SD-WAN
Source: https://docs.megaport.com/cloud/mve/versa/google/index
This help topic describes how to provision connections between MVE and Google Cloud Services and integrate the connection with Versa Secure SD-WAN.
You can create a network connection from an MVE with Versa Secure SD-WAN to Google Cloud through Partner Interconnect.
When connecting to Google Cloud Platform (GCP) through Partner Interconnect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection and Layer 3 BGP is established directly between the customer and GCP.
Before you begin, create an MVE in Versa Director. For more information, see [Creating an MVE](/mve/versa/creating-mve). The MVE needs to be in the active state.
There are three parts to adding a Google Cloud connection to your MVE and Versa Director.
1. Create a Partner Interconnect attachment in Google Cloud Console or gcloud CLI. Copy the pairing key that is provided as part of the attachment creation. For additional details, see the Google documentation on
[Google Partner Interconnects](https://cloud.google.com/interconnect/docs/how-to/partner/provisioning-overview).
2. In the Megaport Portal, create a VXC from your MVE to connect to your Google Cloud attachment.
3. In Versa Director, create a new interface and add the details of the Google Cloud connection.
These instructions step through the second and third parts.
MVE for Versa Secure SD-WAN requires configuration steps in both Versa Director and the Megaport Portal for all cloud connections.
## Adding the Google Cloud connection in the Megaport Portal
To set up the Google Cloud Platform connection, you need to create the connection in the Megaport Portal.
**To create a connection to GCP from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select Google as the provider.
To check the latency and price of connecting to a particular Google location, click **View all Google Partner locations**. You can proceed to the Connection Details page without a pairing key and review the pricing of the selected port. To place an order for a Google connection, you need to provide a pairing key.
4. Copy and paste the pairing key from the Google Cloud console into the Google Partner Pairing Key field.\
The relevant Google targets appear based on the region of your GCI Partner connection.
5. Select the target location for your connection then click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Enter the same rate you selected for your Google port speed.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/versa/creating-mve#creating-mve).
* **Preferred A-End VLAN** -- The VLAN for this connection that you will receive through the MVE. This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
11. Once you have deployed the VXC, go back to your attachment in the Google Cloud Console and accept the attachment.\
You will be provided your private IP address from Google to configure BGP.\
Ensure that you pre-activate the attachment or mark the attachment as active after configuring the VXC. Otherwise, you cannot set up BGP with your SD-WAN instance.
The Google ASN will always be 16550.
## Adding the Google Cloud connection to Versa Director
After you create the connection from your MVE to Google Cloud and set up the connection in the Google console, you need to configure it in Versa Director. This involves configuring BGP settings, ASNs, and VLANs.
**To add the Google Cloud connection in Versa Director**
1. Collect the connection details from the Google console.\
Display the details of the connection you created in Google Cloud for this connection. Note the values for the **Peer ASN**, **Cloud Router BGP IP**, and **BGP Peer IP**.
2. Collect the connection details from the Megaport Portal.\
Click the gear icon for the Google connection from your MVE and click the Details view.
Note the value for the **A-End VLAN**.\
Next, you will add a subinterface to your Versa MVE instance.
3. Log in to Versa Director.
4. Select the **Workflows** tab in the top menu bar.
5. Select Template > Templates in the left menu bar.
6. Select the template you want to edit, then select the **Interfaces** tab.
7. Under WAN Interfaces, click (Add) to add a subinterface.
8. Provide the following information:
* **VLAN ID** -- Enter the A-End VLAN value for this Google connection in the Megaport Portal. Click the Details icon for the connection in the Portal to find this value.
* **Network Name** -- Choose **+Create WAN Network** from the drop-down to open the Create WAN Network window. Specify a meaningful name for the network, click **OK**, and then select the WAN network you created. (Or, if appropriate for your environment, select an existing network name.)
* **IPv4** -- Choose **Static** from the drop-down to assign a static IP address to this subinterface.
We have finished creating the interface. Next we need to create the BGP session.
9. Select the **Routing** tab to add the BGP configuration information.
10. In the BGP section, choose the network created earlier.
11. Enter the following values for your connection:
* **Local AS** -- This is the **Peer ASN** value from the VLAN attachment details in the Google Cloud console.
* **Neighbor IP** -- This is the local Google Cloud IP address. This value is available in the VLAN attachment details in the Google Cloud console. The IP address appears in the **Cloud Router BGP IP** field.
* **Peer AS** -- This is the Google Cloud ASN of 16550. This is a fixed value, and appears in the connection details on the Google console.
* Optionally, enable BFD (as appropriate for your network).
12. Click (Add).
13. Click **Recreate**.\
A screen appears that shows the differences in the configuration. The auto-merged version is recommended, and selected by default.
14. Click **Deploy**.
At this point, we have updated the template assigned to the device group. Next, we will parameterize variables to generate routing information dynamically.
**To parameterize the configuration variables**
1. Select the **Configuration** tab in the top menu bar.
2. Select Templates > Device Templates in the horizontal menu bar.
3. Click the template you want to modify.\
By default, the Interfaces column appears.
4. In the side navigation, select Virtual Routers, and click the link for the subinterface network to open the Edit window.
5. In the side navigation, select BGP, then click the Instance ID for your network.
6. In the Edit BGP Instance window, click (Parameterize) next to each of the following fields: **Router ID**, **Local AS**, **Peer AS**, and **Password**.
7. Click **OK** two times to update.
Next we need to configure the device and create the BGP session.
**To update parameterized variables for a device**
1. Select the **Workflows** tab in the top menu bar.
2. Select Devices > Devices in the horizontal menu bar.
3. Click the device to modify.
4. Select the **Bind Data** tab.\
All parameterized values are displayed here.
5. Enter the following values for the variables:
* **Local AS number** -- The Customer ASN in the Megaport Portal.
* **MD5 password** -- The BGP Auth Key in the Megaport Portal.
* **BGP Peer AS** -- 16550, the Google Cloud ASN.
* **BGP Router ID** -- The Customer IP address (your local IP address) from the MVE details.
* **Next Hop Address** -- The Cloud Router BGP IP from the VLAN attachment details in the Google Cloud console.
* **Interfaces with Mask** -- The static IP address of the interface on the Megaport side of the connection, including the mask value.
6. Click **Deploy** to create the new configuration for the device.
When the new configuration for the device has completed successfully, a green checkmark appears at the bottom of the Director window.
7. In the upper right of the screen under your username, click **Commit Template** to push the changes to the device.
8. Specify the following values:
* **Organization** -- Select your organization from the drop-down.
* **Select Template** -- Select your template to display its associated devices in the table.
* **Differences** -- Click the eye icon in the Differences column to view the configuration to be applied to the device.
9. If you are satisfied with the configuration, click **Commit to Device**.\
A green checkmark appears at the bottom right of the screen when the push is successful. The Template State and Appliance State are now IN\_SYNC with the device.
10. Close the window.
## Validating your Google Cloud connection
You can review device status, including the connection state, from the Monitor tab in Director.
1. Select the **Monitor** tab in the top menu bar.
2. Select Devices in the horizontal menu bar.
3. Click the device to view status and activity.
In the Summary screen you can review your subinterface in the Interface column, and the Operational and Admin Status.
4. Return to Google Cloud Platform and refresh to see the new virtual interface.
# Creating MVE Connections to Latitude.sh with Versa SD-WAN
Source: https://docs.megaport.com/cloud/mve/versa/latitude-sh/index
This help topic describes how to create a connection from a Versa SD-WAN MVE to Latitude.sh.
This topic describes how to create a VXC from MVE to Latitude.sh bare metal cloud using the Megaport Portal, and how to configure BGP in to bring the connection up.
BGP is required for all Latitude.sh connections. To create a connection, specify an ASN, BGP password, and the prefixes to advertise. The connection becomes live after Latitude.sh approves the request.
## Prerequisites
The MVE must be in the active state before you create a connection.
## Adding the Latitude.sh connection in the Megaport Portal
To set up a connection to Latitude.sh with Megaport, you need to create a VXC from your MVE in the Megaport Portal to the Latitude.sh location where you have provisioned your Latitude.sh services.
**To create a connection to Latitude.sh from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection**, click **Cloud**, then click **Compute via Latitude.sh**.
3. Select the target location for your connection then click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc/).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you don't specify a value, Megaport assigns one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.\
A summary page appears that includes the monthly cost.
6. Click **Back** to make changes, or click **Add VXC**.
7. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
8. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
9. Click **Order Now**.
The connection becomes live after Latitude.sh approves the request.
After ordering, the connection status shows *Deployable* until it is provisioned. When Latitude.sh approves the connection and provisioning is complete, the status updates to *Configured*.
## Adding the Latitude.sh connection to Versa Director
To add the connection to Versa Director, you will need the following information:
* MVE IP address
* MVE VLAN (A-End)
* MVE ASN
* Cloud/B-End IP address
* B-End ASN
* MD5 Password
After you create the connection from your MVE to Latitude.sh, you need to configure a WAN subinterface and a BGP session for it in the device's template, then bind the device-specific values and commit the template to the device.
For more information about configuring the interface, see [Versa: Configure Interfaces](https://docs.versa-networks.com/Secure_SD-WAN/01_Configuration_from_Director/Common_Configuration/Configure_Interfaces).
For more information about configuring BGP, see [Versa: Configure BGP](https://docs.versa-networks.com/Secure_SD-WAN/01_Configuration_from_Director/Common_Configuration/Configure_BGP).
## Validating your Latitude.sh connection
You can review device status, including the connection state, from the Monitor tab in Director.
For more information, see [Versa: Configure BGP](https://docs.versa-networks.com/Secure_SD-WAN/01_Configuration_from_Director/Common_Configuration/Configure_BGP).
## Helpful references
* [Connecting to Latitude.sh](/portal-admin/connect-latitude)
* [Creating an MVE Integrated with Versa](/mve/versa/creating-mve)
* Latitude.sh docs
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Creating MVE Connections to Any Endpoint with Arista VeloCloud SD-WAN
Source: https://docs.megaport.com/cloud/mve/vmware/generic/index
This help topic describes the general steps to create a VXC from an MVE to a Cloud Service Provider, a Port, or an MCR and integrate the connection with Arista VeloCloud SD-WAN.
This topic describes the general steps to configure and deploy a Megaport VXC connection in the Megaport Portal and integrate it with an MVE in Arista VeloCloud SD-WAN. The VXC can connect to a Cloud Service Provider, a Port, or an MCR.
#### Step 1 -- Create an MVE
* Create an MVE in the Megaport Portal.\
For more information, see [Creating an MVE](/mve/vmware/creating-mve).
The MVE needs to be in the active state.
#### Step 2 -- Create a VXC from the MVE
1. In the Megaport Portal, select the MVE created in Step 1.
2. Create a VXC to another MVE, a Port, or Cloud Service Provider.\
For more information, see [Creating a VXC](/connections/overview#create_vxc).
Ensure both ends of the connection are active and have BGP configured.
3. In the connection details, note the A-End VLAN.
#### Step 3 -- Collect these values for the connection.
* MVE IP address
* MVE VLAN (A-End)
* MVE ASN
* Cloud/B-End IP address
* B-End ASN
* MD5 Password
#### Step 4 -- Create a subinterface in Orchestrator.
1. In Orchestrator, go to Configure > Edges, click the MVE.
2. Select the **Device** tab and scroll down to Interface Settings.
3. Click **+Add Subinterface**.
4. From the **Select Interface** menu, choose GE3 and for the **Subinterface ID** enter the A-End VLAN ID configured for the connection in the Megaport Portal.
5. Change the **Addressing Type** to Static and provide the **IP Address** (MVE), **CIDR value** (MVE), and **Gateway** (Cloud/B-End IP address).
6. Ensure **Enable VLAN Tagging** is enabled.
7. Click \*\*Update GE3:\*\**vlan-id*.
8. In the upper-right corner of the Configure > Edges window, click **Save Changes** and then confirm.
9. Go to Configure > Edges and click the MVE device.
10. Select the **Device** tab and in the Configure Segments section, click **Enable Edge Override** for BGP Settings.
11. Click the toggle button to turn on BGP and click **Edit**.\
The BGP Editor appears.
12. For **Local ASN**, add the ASN for the MVE side of the connection.
13. For the **Neighbor IP**, add the IP address of the B-End of the connection.
14. Add the B-End ASN to the **ASN** field for the neighbor.
15. View all Additional Options and enable **MD5 Auth** and enter your **MD5 Password** (**BGP Auth Key**).
16. Click **OK** and then click **Save Changes**.
#### Step 5 -- Validating your connection
Under Test & Troubleshoot > Remote Diagnostics, select the MVE and click **Run** for **Troubleshoot BGP - Show BGP Summary** to verify the BGP session and ensure the remote router is up.
You can also check connectivity and BGP status from the CLI of the edge device. For more information, see [Reviewing your VMware MVE connection settings](/cloud/mve/vmware/generic/mve-vxc-details).
# Reviewing MVE Connection Settings in Arista VeloCloud SD-WAN
Source: https://docs.megaport.com/cloud/mve/vmware/generic/mve-vxc-details
This help topic describes how to review your MVE connection settings integrated with Arista VeloCloud SD-WAN through the console and the CLI.
You can review your MVE connection settings through Orchestrator and the CLI.
In Orchestrator, under Test & Troubleshoot > Remote Diagnostics, select the MVE and click **Run** for **Troubleshoot BGP - Show BGP Summary** to verify the BGP session and ensure the remote router is up.
You can also check connectivity and BGP status from the CLI of the edge device.
1. SSH to your MVE using the SSH keypair you provided during MVE creation.
`ssh -i megaport-mve-instance-1-2048 root@162.43.144.9`
2. Check the interface configuration.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
edge:megaport-demo-1:~# ip addr list | grep eth2.1000
22: eth2.1000@eth2: mtu 1500 qdisc noqueue state UP group default qlen 1000
inet 169.254.11.18/30 brd 169.254.11.19 scope global eth2.1000
```
Interface numbering on the CLI differs from the Orchestrator console. In the CLI, interface numbering begins at 0 so the corresponding CLI interface for GE3 is `eth2`. The number following `eth2` is the subinterface ID (the A-End VLAN ID).
3. Ping the remote end.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
edge:megaport-demo-1:~# ping 169.254.11.17
PING 169.254.11.17 (169.254.11.17) 56(84) bytes of data.
64 bytes from 169.254.11.17: icmp_req=1 ttl=63 time=29.5 ms
64 bytes from 169.254.11.17: icmp_req=2 ttl=63 time=28.7 ms
64 bytes from 169.254.11.17: icmp_req=3 ttl=63 time=32.6 ms
64 bytes from 169.254.11.17: icmp_req=4 ttl=63 time=34.2 ms
64 bytes from 169.254.11.17: icmp_req=5 ttl=63 time=28.6 ms
64 bytes from 169.254.11.17: icmp_req=6 ttl=63 time=28.6 ms
^C
--- 169.254.11.17 ping statistics ---
7 packets transmitted, 6 received, 14% packet loss, time 6008ms
rtt min/avg/max/mdev = 28.629/30.413/34.279/2.232 ms
```
4. Check the BGP status.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
edge:megaport-demo-1:~# debug.py --bgp_view_summary
show ip bgp summary
===================
BGP view name 0
BGP router identifier 192.168.1.1, local AS number 65135
RIB entries 1, using 112 bytes of memory
Peers 1, using 4568 bytes of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
169.254.11.17 4 64512 2762 2694 0 0 0 22:25:07 1
Total number of neighbors 1
```
# Creating a Google Cloud Services Connection for an MVE with Arista VeloCloud SD-WAN
Source: https://docs.megaport.com/cloud/mve/vmware/google/index
This help topic describes how to provision connections between an MVE and Google Cloud Services and integrate the connection with Arista VeloCloud SD-WAN.
You can create a network connection from an MVE (Edge) to Google Cloud through Partner Interconnect.
When connecting to Google Cloud Platform (GCP) through Partner Interconnect with Megaport, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection and Layer 3 BGP is established directly between the customer and GCP.
Before you begin, create an MVE (Edge) in Orchestrator. For more information, see [Creating an MVE](/mve/vmware/creating-mve). The MVE needs to be in the active state.
There are three parts to adding a Google Cloud connection to your MVE and Orchestrator.
1. Create a Partner Interconnect attachment in Google Cloud Console or
gcloud CLI. Copy the pairing key that is provided as part of the attachment
creation. For additional details, see the Google documentation on
[Google Partner Interconnects](https://cloud.google.com/interconnect/docs/how-to/partner/provisioning-overview).
2. In the Megaport Portal, create a VXC from your MVE to connect to your Google Cloud attachment.
3. In Orchestrator, create a new interface and add the details of the Google Cloud connection.
These instructions step through the second and third parts.
MVE for Arista VeloCloud SD-WAN requires configuration steps in both Orchestrator and the Megaport Portal for all cloud connections.
## Adding the Google Cloud connection in the Megaport Portal
To set up the GCP connection, you need to create the connection in the Megaport Portal.
**To create a connection to GCP from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection** then click **Cloud**.
3. Select Google as the provider.
To check the latency and price of connecting to a particular Google location, click **View all Google Partner locations**. You can proceed to the Connection Details page without a pairing key and review the pricing of the selected port. To place an order for a Google connection, you need to provide a pairing key.
4. Copy and paste the pairing key from the Google Cloud console into the Google Partner Pairing Key field.\
The relevant Google targets appear based on the region of your GCI Partner connection.
5. Select the target location for your connection then click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. Enter the same rate you selected for your Google port speed.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list. For more information about vNICs, see [Creating an MVE in the Megaport Portal](/mve/vmware/creating-mve#creating-mve).
* **Preferred A-End VLAN** -- The VLAN for this connection that you will receive through the MVE. This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don't specify a value, Megaport will assign one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Next** to proceed to the connection detail summary, then click **Add VXC**.
8. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click **Order Now**.
11. Once you have deployed the VXC, go back to your attachment in the Google Cloud Console and activate the attachment and configure BGP.\
You will be provided your private IP address from Google to configure BGP. The BGP configuration requires your ASN for the MVE.
The Google ASN will always be 16550.
## Adding Google Cloud connection details to Orchestrator
After you create the connection from your MVE to Google Cloud and set up the connection in the Google console, you need to configure it in Orchestrator. This involves configuring BGP settings, ASNs, and VLANs.
**To add the Google Cloud connection in Orchestrator**
1. Collect the connection details from the Google console.\
Display the details of the connection you created in Google Cloud for this connection. Note the values for the **Peer ASN**, **Cloud Router BGP IP**, and **BGP Peer ID**.
2. Collect the connection details from the Megaport Portal.\
Click the gear icon for the Google connection from your MVE and click the Details view.
Note the value for the **A-End VLAN**.
3. In Orchestrator, go to Configure > Edges and click the MVE device.
4. Select the **Device** tab and scroll down to the Interface Settings.
5. Click **+Add Subinterface**.
The Select Interface dialog box appears.
6. From the **Select Interface** menu, choose GE3 and for the **Subinterface ID** enter the A-End VLAN ID configured on the MVE in the Megaport Portal.
The subinterface settings appear.
7. Change the **Addressing Type** to Static and provide the **IP Address**, **CIDR value**, and **Gateway**.\
These values are available in the VLAN attachment details in the Google Cloud console. The IP address appears in the **BGP Peer ID** field; the Gateway appears in the **Cloud Router BGP IP** field.
8. Ensure **Enable VLAN Tagging** is enabled.\
The field is automatically populated with the VLAN ID you specified for the subinterface ID.
9. Click **Update GE3:** *vlan-id*.
10. In the upper-right corner of the Configure > Edges window, click **Save Changes** and then confirm.\
This configures the interface, VLAN tags, and IP addresses, which you can test with ping commands through the CLI. (BGP is not yet configured.)
Adding the subinterface momentarily disrupts the connection.
**To configure BGP for the Google Cloud connection in Orchestrator**
1. In Orchestrator, go to Configure > Edges and click the MVE device.
2. Select the **Device** tab and in the Configure Segments section click **Enable Edge Override** for BGP Settings.\
This override lets us define BGP values specific for this device beyond the profile definition.
3. Click the toggle button to turn on BGP and click **Edit**.\
The BGP Editor appears.
4. For **Local ASN**, add the **Peer ASN** that you defined in the BGP configuration for the VLAN attachment in the Google Cloud console.
5. For the **Neighbor IP**, add the **Cloud Router BGP IP** from the VLAN attachment details in the Google Cloud console.
6. Add the Google Cloud ASN of 16550 to the **ASN** field for the neighbor.\
This is a fixed value from Google Cloud.
7. Click **OK** and then click **Save Changes**.
## Validating your connection
Under Test & Troubleshoot > Remote Diagnostics, select the MVE and click **Run** for **Troubleshoot BGP - Show BGP Summary** to verify the BGP session and ensure the Google Cloud Router is up.
You can also check connectivity and BGP status from the CLI of the edge device. For more information, see [Reviewing your Arista VeloCloud MVE connection settings](/cloud/mve/vmware/generic/mve-vxc-details).
# Creating MVE Connections to Latitude.sh with Arista VeloCloud SD-WAN
Source: https://docs.megaport.com/cloud/mve/vmware/latitude-sh/index
This help topic describes how to create a connection from an Arista VeloCloud SD-WAN MVE to Latitude.sh.
This topic describes how to create a VXC from MVE to Latitude.sh bare metal cloud using the Megaport Portal, and how to configure BGP in to bring the connection up.
BGP is required for all Latitude.sh connections. To create a connection, specify an ASN, BGP password, and the prefixes to advertise. The connection becomes live after Latitude.sh approves the request.
## Prerequisites
The MVE must be in the active state before you create a connection.
## Adding the Latitude.sh connection in the Megaport Portal
To set up a connection to Latitude.sh with Megaport, you need to create a VXC from your MVE in the Megaport Portal to the Latitude.sh location where you have provisioned your Latitude.sh services.
**To create a connection to Latitude.sh from the Megaport Portal**
1. In the Megaport Portal, go to the **Services** page and select the MVE for the connection.
2. Click **+Connection**, click **Cloud**, then click **Compute via Latitude.sh**.
3. Select the target location for your connection then click **Next**.
4. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc/).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active.
* **A-End vNIC** -- Select an A-End vNIC from the drop-down list.
* **Preferred A-End VLAN** (optional) -- Specify an unused VLAN ID for this connection. The VLAN ID must be unique on this MVE and can range from 2 to 4093. If you don't specify a value, Megaport assigns one.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click **Next**.\
A summary page appears that includes the monthly cost.
6. Click **Back** to make changes, or click **Add VXC**.
7. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
8. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
9. Click **Order Now**.
The connection becomes live after Latitude.sh approves the request.
After ordering, the connection status shows *Deployable* until it is provisioned. When Latitude.sh approves the connection and provisioning is complete, the status updates to *Configured*.
## Adding the Latitude.sh connection to Orchestrator
To add the connection to Orchestrator, you will need the following information:
* MVE IP address
* MVE VLAN (A-End)
* MVE ASN
* Cloud/B-End IP address
* B-End ASN
* MD5 Password
After you create the connection from your MVE to Latitude.sh, you need to configure a subinterface and a BGP session for it in Orchestrator.
For more information about configuring the interface, see [VeloCloud SD-WAN 6.4 - Administration Guide: Manage Edges](https://www.arista.com/en/admin-guide-vc-6-4/sd-wan-6-4-manage-edges).
For more information about configuring BGP, see [VeloCloud SD-WAN 6.4 - Administration Guide: Configuring BGP](https://www.arista.com/en/admin-guide-vc-6-4/sd-wan-6-4-configuring-dynamic-routing-with-ospf-or-bgp#configure_bgp).
## Validating your Latitude.sh connection
Under Test & Troubleshoot > Remote Diagnostics, select the MVE and click **Run** for **Troubleshoot BGP - Show BGP Summary** to verify the BGP session and ensure the connection to Latitude.sh is up.
You can also check connectivity and BGP status from the CLI of the edge device. For more information, see [Reviewing your Arista VeloCloud MVE connection settings](/cloud/mve/vmware/generic/mve-vxc-details).
## Helpful references
* [Connecting to Latitude.sh](/portal-admin/connect-latitude)
* [Creating an MVE Integrated with Arista VeloCloud SD-WAN](/mve/vmware/creating-mve)
* Latitude.sh docs
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Creating NAT Gateway Connections to Latitude.sh
Source: https://docs.megaport.com/cloud/nat/latitude-sh
This help topic describes how to create a connection between a Megaport NAT Gateway and Latitude.sh.
BGP is required for all Latitude.sh connections. To create a connection, specify an ASN, BGP password, and the prefixes to advertise. The connection becomes live after Latitude.sh approves the request.
## Prerequisites
## Creating a connection to Latitude.sh
To set up a connection to Latitude.sh with Megaport, you need to create a VXC from your NAT Gateway in the Megaport Portal to the Latitude.sh location where you have provisioned your Latitude.sh services.
**To create a connection to Latitude.sh**
1. In the Megaport Portal, go to the **Services** page.
2. Select the NAT Gateway you want to use.\
If you haven't created a NAT Gateway, see [Creating a NAT Gateway](/nat/creating-nat-gateway).
3. Click **+Connection**, click **Cloud**, then click **Compute via Latitude.sh**.
4. Select the target location for your connection then click **Next**.
5. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc/).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
6. Click **Next**.
7. Review the NAT Gateway A-End connection details.\
For more information, see [Configuring a NAT Gateway VXC](/nat/configuring-nat-vxc/).
8. Click **Next**.\
A summary page appears that includes the monthly cost.
9. Click **Back** to make changes, or click **Add VXC**.
10. Click **Review Order** to proceed through the checkout process, or click **Save** to save the configured services before placing the order.
11. Review the Important Information section and confirm agreement with the Service Agreements.
If you do not have a promotion code, skip to the **Order Now** step. If you do have a promotion code, enter it into the **Enter discount code** field then click **Apply**. Alternatively, if a code already appears in the **Discounts** field, verify it is correct and click **Apply**.
The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code.
If you entered an incorrect promotion code, you can remove it by clicking **Remove**.
In addition to entering a promotion code manually, there are two other ways to apply promotion codes.
* **Auto-apply** -- Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
* **Manual list** -- Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
12. Click **Order Now**.
The connection becomes live after Latitude.sh approves the request.
After ordering, the connection status shows *Deployable* until it is provisioned. When Latitude.sh approves the connection and provisioning is complete, the status updates to *Configured*.
## Helpful references
* [Connecting to Latitude.sh](/portal-admin/connect-latitude)
* [Creating a NAT Gateway](/nat/creating-nat-gateway)
* Latitude.sh docs
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Enabling Cloud-Native VPN/Encryption Options Over Dedicated Cloud Connectivity Paths
Source: https://docs.megaport.com/encryption/cloud-native-vpn-encryption
This help topic describes encryption options for dedicated cloud connectivity paths with Megaport.
When implementing a dedicated connection into the public cloud through ExpressRoute to Microsoft Azure or Direct Connect to Amazon Web Services, the security of the transport path is part of a security risk assessment to minimize the risk of any potential man-in-the-middle attack.
Azure and AWS have published details on how to use VPN services through their respective dedicated cloud connectivity options:
* [Configure a site-to-site VPN over Microsoft Peering](https://docs.microsoft.com/en-us/azure/expressroute/site-to-site-vpn-over-microsoft-peering)
* [Establish a VPN Using AWS Direct Connect](https://aws.amazon.com/premiumsupport/knowledge-center/create-vpn-direct-connect/)
This topic describes several scenarios using dedicated cloud connectivity, including:
* **Scenario 1:** IPsec VPN -- Azure ER Microsoft Peering or AWS DX Public VIF
* **Scenario 2:** IPsec VPN via Megaport Cloud Router (MCR) -- Azure ER Microsoft Peering or AWS DX Public VIF
* **Scenario 3:** IPsec VPN -- Azure ER Private Peering or AWS DX Private VIF with in Azure or AWS
* **Scenario 4:** IPsec VPN -- Multicloud with Network Virtual Appliance (NVA) in Azure and AWS
IPsec VPN -- Azure ER Microsoft Peering or AWS DX Public VIF
**Prerequisites**
* Owned public IP addresses that can be assigned to use Microsoft Peering and Public VIF. **Note:** If public IP addresses are not owned, use MCR (Scenario 2).
* Owned network appliance capable of IPsec.
**Megaport Technology Required**
| Technology | Required | How many? |
| - | - | - |
| Port | Yes | 1 or (2 in a Link Aggregation/LAG) |
| Megaport Cloud Router (MCR) | No | |
| Virtual Cross Connect (VXC) | Yes | 1 to each CSP (Azure or AWS) |
**Considerations**
* Azure and AWS use industry standard protocol IPsec AES128 or AES256 for encryption: using other protocols for security or performance is not easily customizable.
* Azure and AWS IPsec VPN can be configured with Active-Active HA configuration.
* The maximum throughput available to AWS Virtual Private Gateway is 1.25 Gbps. The maximum throughput of Azure VPNs depends on the VPN Gateway SKU.
IPsec VPN via Megaport Cloud Router (MCR) -- Azure ER Microsoft Peering or AWS DX Public VIF
This solution is suitable for organizations that do not own public IP addresses.
**Prerequisites**
* Customer-owned network appliance capable of IPsec.
**Megaport Technology Required**
| Technology | Required | How many? |
| - | - | - |
| Port | Yes | 1 (2 in a Link Aggregation/LAG) |
| Megaport Cloud Router (MCR) | Yes | 1 |
| Virtual Cross Connect (VXC) | Yes | 1 to each CSP (Azure or AWS) and 1 Private VXC |
**Considerations**
* Azure and AWS use industry standard protocol IPsec AES128 or AES256 for encryption: using other protocols for security or performance is not easily customizable.
* Azure and AWS IPsec VPN can be configured with Active-Active HA configuration.
* The maximum throughput available to AWS Virtual Private Gateway is 1.25 Gbps. The maximum throughput of Azure VPNs depends on the VPN Gateway SKU.
IPsec (or other) VPN - Private Peering or Private VIF with [Network Virtual Appliance (NVA)](https://azure.microsoft.com/en-au/solutions/network-appliances/) in Azure or AWS.
**Prerequisites**
* Customer-owned IPsec-capable network appliances on-premises and in the cloud.
**Megaport Technology Required**
| Technology | Required | How many? |
| - | - | - |
| Port | Yes | 1 (2 in a Link Aggregation/LAG) |
| Megaport Cloud Router (MCR) | No | |
| Virtual Cross Connect (VXC) | Yes | 1 to each CSP (Azure or AWS) |
**Considerations**
* Organizations have the flexibility of the encryption method for better security or better performance.
* Additional cost to the VMs running the NVA.
* Organizations will need to consider how to design and deliver HA for this scenario.
* The maximum throughput can exceed 1.25 Gbps up to the maximum Port size (1 Gbps or 10 Gbps) with the right compute power available on the NVA.
IPsec (or other) VPN - Multicloud with [Network Virtual Appliance (NVA)](https://azure.microsoft.com/en-au/solutions/network-appliances/) in Azure and AWS.
This solution is suitable for organizations with on-premises infrastructure that is not geographically close to the CSPs.
**Prerequisites**
* Customer owns IPsec-capable network appliances on-premises and in the cloud.
**Megaport Technology Required**
| Technology | Required | How many? |
| - | - | - |
| Port | Yes | 1 (2 in a Link Aggregation/LAG) |
| Megaport Cloud Router (MCR) | Yes | 1 |
| Virtual Cross Connect (VXC) | Yes | 1 to each CSP (Azure and AWS) and 1 Private VXC |
**Considerations**
* Provides a flexible encryption method for better security or better performance.
* Additional cost to the VMs running the NVA.
* Need to consider how to design and deliver HA for this scenario.
* The maximum throughput can exceed 1.25 Gbps with the required compute power available on the NVA.
## Helpful references
* **Readme file:** [AWS - Azure Private IP VPN with Megaport](https://github.com/Mark-Austen/mcr-aws-azure-private-ip-vpn)
# High-Speed Cross-Cloud Encryption Overview
Source: https://docs.megaport.com/encryption/high-speed-cross-cloud-encryption
This help topic describes what Megaport High-Speed Cross-Cloud Encryption is and provides detailed information on how to order it.
High-Speed Cross-Cloud Encryption delivers secure, high-performance connectivity for enterprises and organizations that require uncompromised speed and protection across multicloud networks.
Enabling Media Access Control security () for High-Speed Cross-Cloud Encryption ensures that your data remains private and secure while traveling at speeds up to 100 Gbps, and even higher in the future, between critical locations.
Designed for mission-critical workloads, this service combines line-rate encryption with the reliability and scalability needed to support modern cloud, data centers, and enterprise applications without compromising performance.
The primary benefit is that data is secured without sacrificing network speed. You can configure High-Speed Cross-Cloud Encryption by enabling hardware-based encryption of MACsec. It provides (Data Link Layer) encryption to authenticate Ethernet frames across a direct link. For more information, see [Using MACsec with Megaport](/encryption/macsec).
## About line-rate encryption
Line-rate encryption is a form of data encryption that operates at the maximum physical speed of the communication link, often referred to as wire speed or full line rate.
This means that the encryption and decryption process is performed without introducing any noticeable delay or reducing the overall data throughput of the link.
In high-speed networks, achieving line-rate encryption is critical because traditional software-based encryption methods often cannot process data fast enough and might create bottlenecks.
## Enabling High-Speed Cross-Cloud Encryption
The following steps outline how to configure and enable High-Speed Cross-Cloud Encryption via Megaport’s services.
1. **Order CSP ports** -- Order dedicated Cloud Service Provider () ports and obtain Letters of Authorization () from CSPs.
2. **Order Megaport Ports** -- Order Ports in the Megaport Portal and upload the CSP LOAs for Cross Connect completion with Megaport's assistance. For more information, see [Uploading a Letter of Authorization (LOA)](/connections/cross-connect#uploading-a-letter-of-authorization-loa).
3. **Configure MACsec** -- After the Cross Connects to the dedicated CSP ports are completed, provision the encrypted link and enable MACsec on all endpoints. For more information about establishing a MACsec connection between CSPs using Megaport services, see [Creating a cloud-to-cloud encrypted connection](/encryption/macsec#creating-a-cloud-to-cloud-encrypted-connection).
4. **Activate the encrypted paths** -- Activate encrypted connections between endpoints at line rate, up to 100 Gbps across the Megaport network.
## Helpful references
* [Ordering a Cross Connect](/connections/cross-connect)
* [Uploading a Letter of Authorization (LOA)](/connections/cross-connect#uploading-a-letter-of-authorization-loa)
* [Using Encryption in Transit with Megaport Services](/encryption)
* [Using MACsec with Megaport](/encryption/macsec)
# Using Encryption in Transit with Megaport Services
Source: https://docs.megaport.com/encryption/index
This help topic describes how to use encryption with Megaport services
**Encryption in transit** refers to protecting data while it moves from one place to another.
There are many options available for encrypting data as it moves over a network. The most common are , , and host-level encryption. Each of these approaches has its advantages and disadvantages, and each operates at a different level of the network stack.
Using the [OSI Model](https://en.wikipedia.org/wiki/OSI_model), MACsec operates at , IPsec operates at , and host level, including TLS and SSH, typically operates at Layers 4-7 within the clients and servers rather than at the network level.
Megaport works with customers using various combinations of all of these protocols, along with many others.
For more information about using MACsec with your Megaport services, see [Using MACsec with Megaport](/encryption/macsec).
For more information about using IPsec with your Megaport services, see [Using IPsec with Megaport](/encryption/ipsec).
## Helpful references
* [Comparing Encryption in Transit Options](https://www.megaport.com/blog/comparing-encryption-in-transit-options/)
* [Enabling Cloud-Native VPN/Encryption Options Over Dedicated Cloud Connectivity Paths](/encryption/cloud-native-vpn-encryption)
* [Using IPsec with Megaport](/encryption/ipsec)
* [Using MACsec with Megaport](/encryption/macsec)
# Using IPsec with Megaport
Source: https://docs.megaport.com/encryption/ipsec
This help topic describes how to use IPsec encryption with Megaport services.
If you need to encrypt traffic between endpoints in an IP network, is the most common solution. IPsec encrypted traffic can be transparently carried over any Megaport VXC.
## Creating an encrypted IPsec link using Megaport
You can create an IPsec encrypted customer-to-customer, customer-to-cloud, or cloud-to-cloud connection. See your cloud or equipment vendor's documentation for more information about creating IPsec connections.
On Megaport Cloud Routers (MCR), you can enable IPsec in the Megaport Portal during creation, or edit the MCR to enable IPsec after it has gone live. For more information, see [Using IPsec with MCR](/mcr/ipsec-mcr).
## Supported ciphers
The MCR will offer the following ciphers to IPsec peers. At this time, the options are not configurable.
**Encryption**
* AES128-GCM-128
* AES256-GCM-128
**Integrity**
* HMAC SHA-1
* HMAC SHA-256
* HMAC SHA-384
* HMAC SHA-512
**Key Exchange (Diffie-Hellman group)**
* MODP
* Diffie-Hellman Group 2 (1024-bit)
* Diffie-Hellman Group 14 (2048-bit)
* ECP
* Diffie-Hellman Group 19 (256-bit random)
* Diffie-Hellman Group 20 (384-bit random)
* Diffie-Hellman Group 21 (521-bit random)
## IP MTU settings
IPsec packets include overhead due to encryption and encapsulation. We recommend that you configure your carefully to suit your network. The maximum value depends on the negotiated ciphers.
If you do not configure the IP MTU setting, the MCR will use the following default values:
* 96 bytes less than the parent interface IP MTU for IPv4
* 116 bytes less than the parent interface IP MTU for IPv6
These values allow for ciphers that have the largest overhead.
## Creating a customer-to-customer link using Megaport and IPsec
You can use an IPsec connection between two of your own devices using Megaport services.
**Prerequisites**
Before creating an IPsec encrypted link from customer-to-customer, you need:
* An IPsec capable router at each of your locations.
* Megaport Ports in locations where you can connect physically from your IPsec capable routers to the Port for each end of your connection.
**To create a customer-to-customer encrypted connection**
1. From each IPsec capable router, create a physical link to a Megaport Port.
2. Use a VXC to connect your Ports.
3. Create an IPsec connection over the interfaces connected to Megaport.
## Creating a customer-to-cloud link using Megaport and IPsec
**Prerequisites**
Before creating an IPsec encrypted link from customer-to-cloud, you need:
* An IPsec capable router.
* A Megaport Port in a location where you can connect physically from your IPsec capable router to the Port.
* A connection to your CSP.
**To create a customer-to-cloud encrypted connection**
This example shows an IPsec connection from a customer to AWS Direct Connect.
1. From your IPsec capable router, create a physical link to a Megaport Port.
2. Use VXC to connect the Port to the CSP, AWS Direct Connect in this case.
3. Create an IPsec tunnel between your device and the CSP's VPN services.
The connection will be IPsec encrypted from the IPsec capable router through to the AWS Transit Gateway.
## Creating a cloud-to-cloud link using Megaport and IPsec
**Prerequisites**
Before creating an IPsec encrypted link from cloud to cloud, you need:
* A Megaport Cloud Router (MCR) with IPsec enabled.
* Connections to your CSPs VXCs
**To create a cloud-to-cloud encrypted connection**
This example describes an IPsec connection from AWS Direct Connect to Azure ExpressRoute.
1. Create a VXC to connect your Direct Connect connection to the MCR.
2. Use a VXC to connect the MCR to the ExpressRoute connection.
3. Create an IPsec tunnel between the AWS and Azure VPN services.\
For more information, see [Using IPsec with MCR](/mcr/ipsec-mcr).
The connection will be IPsec encrypted from the AWS Transit Gateway to the Azure Virtual Network Gateway.
## Creating a cloud-to-cloud link using Megaport and IPsec tunnels
**Prerequisites**
Before creating a cloud to cloud link with IPsec tunnels, you need:
* A Megaport Cloud Router (MCR) with IPsec enabled.
* Connections established through VXCs to your Cloud Service Providers.
**To create a cloud-to-cloud encrypted connection**
This example describes an IPsec connection from AWS Direct Connect to Azure ExpressRoute.
1. Create a VXC to connect your Direct Connect connection to the MCR.
2. Create a VXC to connect the MCR to the ExpressRoute connection.
3. Create an IPsec tunnel on the VXC between the MCR and the Direct Connect connection.
For more information, see [Using IPsec with MCR](/mcr/ipsec-mcr).
4. Create an IPsec tunnel on the VXC between the MCR and the ExpressRoute connection.
For more information, see [Using IPsec with MCR](/mcr/ipsec-mcr).
The connection will be IPsec-encrypted from the AWS Transit Gateway to the Azure Virtual Network Gateway.
## Helpful references
* [Comparing Encryption in Transit Options](https://www.megaport.com/blog/comparing-encryption-in-transit-options/)
* [Creating a Port](/connections/creating-port)
* [Creating a VXC](/connections/overview#create_vxc)
* [Creating an MCR](/mcr/creating-mcr)
* [IPsec Overhead Calculator](https://ipsec-overhead-calculator.netsec.us/)
* [Using Encryption in Transit with Megaport Services](/encryption)
* [Using IPsec with MCR](/mcr/ipsec-mcr)
* [What is IPsec?](https://www.megaport.com/blog/what-is-ipsec/)
# Using MACsec with Megaport
Source: https://docs.megaport.com/encryption/macsec
This help topic describes how to use MACsec encryption with Megaport services
encrypts traffic at the Ethernet layer between devices connected by a layer 2 path, and is often implemented in hardware. The use of dedicated hardware means that MACsec can maintain wire-speed performance while providing strong security. This makes it suitable for environments that require high throughput, such as data centers and high-performance computing networks.
## Using tagged or untagged VXCs
MACsec-encrypted traffic can be carried transparently over untagged VXCs, or over tagged VXCs when the VLAN is not encrypted.\
Some equipment does not support unencrypted VLANs. Check whether the equipment you use supports unencrypted VLANs, also known as clear tag mode, before using MACsec-encrypted traffic over tagged VXCs.
Most Cloud Service Providers (CSP) support MACsec from 10 Gbps or above (10 Gbps or 100 Gbps). Check with your Cloud Service Provider. Megaport supports both 10 Gbps and 100 Gbps options.
## Creating a customer-to-customer encrypted connection
You can use a MACsec connection between two of your own devices using Megaport services.
**Prerequisites**
To create a MACsec-encrypted link between two of your own devices, you need:
* MACsec capable customer equipment, for example, a switch or router, at each end.
* Two Megaport Ports.
* One in a location where you can create a physical cross connect to your first MACsec capable device.
* One in a location where you can create a physical cross connect to your second MACsec capable device.
**To create a customer-to-customer encrypted connection**
1. From your first MACsec capable device, create a physical link to the first Port.
2. From your second MACsec capable device, create a physical link to the second Port
3. Create an untagged VXC to connect your first Port to your second Port. For more information, see [Using tagged or untagged VXCs](#tagged-or-untagged-vxc).
4. Configure MACsec on your devices, on the interfaces connected to Megaport.
The connection will be MACsec-encrypted between your devices.
## Creating a customer-to-cloud encrypted connection
You can use a MACsec connection between your device and a CSP using Megaport services.
**Prerequisites**
To create a MACsec-encrypted link from customer to cloud, you need:
* MACsec capable customer equipment, for example, a switch or router.
* Two Megaport Ports.
* One in a location where you can create a physical cross connect to your MACsec capable router.
* One in a location where you can create a physical cross connect to the cloud onramp.
* A dedicated connection service from your cloud provider. For example, AWS Dedicated Direct Connect, or ExpressRoute Direct.
**To create a customer-to-cloud encrypted connection**
1. From your MACsec capable device, create a physical cross connect to the first Megaport Port.
2. Create a physical link from the second Port to the CSP onramp, which is ExpressRoute in this case. You will need to contact your Megaport account team for this step.
3. Create an untagged VXC to connect your first Port to your second Port. For more information, see [Using tagged or untagged VXCs](#tagged-or-untagged-vxc).
4. Configure MACsec on the CSP service and on your device.
The connection will be MACsec-encrypted from the MACsec capable router through to the ExpressRoute Direct Circuit.
## Creating a cloud-to-cloud encrypted connection
You can use a MACsec connection between cloud providers using Megaport services.
**Prerequisites**
Before creating a MACsec-encrypted link from cloud to cloud, you need:
* Dedicated connection services from your cloud providers. For example, AWS Direct Connect or ExpressRoute Direct.
* Two Megaport Ports.
* One in a location where you can create a physical cross connect to your first cloud connection.
* One in a location where you can create a physical cross connect to your second cloud connection.
**To create a cloud-to-cloud encrypted connection**
This example describes a MACsec connection from AWS Direct Connect to Azure ExpressRoute.
1. Create a physical connection from your dedicated AWS Direct Connect to your first Megaport Port. You will need to contact your Megaport account team for this step.
2. Create a physical connection from your second Megaport Port to your Azure ExpressRoute Direct. You will need to contact your Megaport account team for this step.
3. Create a tagged or untagged VXC to connect your Ports.\
For more information, see [Using tagged or untagged VXCs](#tagged-or-untagged-vxc).
The MACsec-encrypted connection will persist from the dedicated Direct Connect through to the ExpressRoute Direct Circuit.
## Helpful references
* [Comparing Encryption in Transit Options](https://www.megaport.com/blog/comparing-encryption-in-transit-options/)
* [Creating a Port](/connections/creating-port)
* [Creating a VXC](/connections/overview#create_vxc)
* [Technical Specifications](/tech-specs)
* [Using Encryption in Transit with Megaport Services](/encryption)
# Customer Security Responsibilities
Source: https://docs.megaport.com/troubleshooting/security-responsibilities
This help topic describes the security responsibilities that Megaport customers have when using Megaport services.
Security is a shared responsibility between Megaport and Customers. Customers should note that, while the Services are inherently isolated, they are deployed over shared network infrastructure.
Customers are recommended to evaluate and employ additional controls appropriate to the design and use of Services including but not limited to:
* **Data Center** -- Evaluate the data center operators (DCO) where equipment is located to ensure the DCO meets Customer security and compliance obligations.
* **Service Implementation** -- Port / Service diversity, resiliency, configuration and logging, use of API and terraform.
* **Internet Exchange** -- Use of assigned IX IP addressing and [prevent illegal traffic types](/ix/ix-requirements#illegal).
* **Compliant Prefix Advertisement** -- Preventing RFC-1918 compliant address space (that is, Private Address space) prefix advertisement to external peers.
* **BGP Configuration** -- Ensuring prefixes are accurate, registered, owned by the customer (or an authorized downstream network), have signed Route Origin Authorization objects registered with the appropriate RIR, and restricted to those intended.
* **Data Transmission** -- Connection to trusted destinations and content of data transmitted.
* Protocols and addressing -- Method by which data is transmitted
* Encryption -- Transport and/or Application-layer
* Traffic filtering -- Technology employed to explicitly permit or deny source, destination, protocol, or payload.
* **SD-WAN Service** -- Configuration and security; image administration and security.
* **Portal Identity and Access Management** -- User, role, and permission assignment.
* Identity-Provider (IdP) security
* User token, password, and/or key secrecy
* User multi-factor authentication configuration.
# Megaport Account Admin & Billing Overview
Source: https://docs.megaport.com/account-billing/index
This help topic introduces account administration, pricing, and billing for the Megaport Portal.
This topic introduces account administration, pricing, and billing for the Megaport Portal.
You can manage your Megaport Portal account, users, pricing, and billing from these sections:
* **[Portal Admin](/portal-admin/overview)** -- Administer your user and company details, including security settings, webhooks, activity logs, and Letters of Authorization, from the Settings menu in the Megaport Portal.
* **[Pricing](/finance/creating-estimates)** -- Quote and plan the cost of Megaport services, and manage contract terms and Early Termination Fees.
* **[Billing](/finance/overview)** -- Manage your billing and accounts receivable process, including invoices, payment methods, and billing markets.
To get started, select a topic from the side navigation.
# Payment Webhook Events
Source: https://docs.megaport.com/api/webhooks/events/payment
This help topic describes the payment webhook events.
This topic describes the payment events sent by Megaport's webhooks.
## payment.card.registered
`payment.card.registered` is sent when a payment card is registered.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `auto_pay` (boolean)
* `billing_market` (string)
* `last_four_digits` (string)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "payment.card.registered",
"data": {
"auto_pay": true,
"billing_market": "US",
"last_four_digits": "1234"
}
}
```
## payment.card.registration.failed
`payment.card.registration.failed` is sent when a payment card registration failed.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `billing_market` (string)
* `failure_reason` (string)
* `last_four_digits` (string)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "payment.card.registration.failed",
"data": {
"billing_market": "US",
"failure_reason": "Do Not Honor",
"last_four_digits": "1234"
}
}
```
## payment.card.removed
`payment.card.removed` is sent when a payment card is removed.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `billing_market` (string)
* `last_four_digits` (string)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "payment.card.removed",
"data": {
"billing_market": "US",
"last_four_digits": "1234"
}
}
```
## payment.card.updated
`payment.card.updated` is sent when a payment card is updated.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `auto_pay` (boolean)
* `billing_market` (string)
* `last_four_digits` (string)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "payment.card.updated",
"data": {
"auto_pay": true,
"billing_market": "US",
"last_four_digits": "1234"
}
}
```
## payment.failed
`payment.failed` is sent when a payment failed.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `amount` (number, double)
* `billing_market` (string)
* `currency` (string)
* `failure_reason` (string)
* `payment_date` (string, date-time)
* `payment_method` (string)
* `reference` (string)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "payment.failed",
"data": {
"amount": 1000,
"billing_market": "US",
"currency": "AUD",
"failure_reason": "Stripe blocked this charge as too risky.",
"payment_date": "2026-05-12T03:00:00Z",
"payment_method": "Credit Card",
"reference": "007_asdf"
}
}
```
## payment.succeeded
`payment.succeeded` is sent when a payment was successful.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `amount` (number, double)
* `billing_market` (string)
* `currency` (string)
* `payment_date` (string, date-time)
* `payment_method` (string)
* `reference` (string)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "payment.succeeded",
"data": {
"amount": 1000,
"billing_market": "US",
"currency": "AUD",
"payment_date": "2026-05-12T03:00:00Z",
"payment_method": "Credit Card",
"reference": "ch_12345abcdefg"
}
}
```
# Security Webhook Events
Source: https://docs.megaport.com/api/webhooks/events/security
This help topic describes the security webhook events.
This topic describes the security events sent by Megaport's webhooks.
## security.login.failed
`security.login.failed` is sent when a failed login attempt occurred.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `account_locked` (boolean)
* `attempts` (integer, int32)
* `email` (string, email)
* `person_uid` (string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "security.login.failed",
"data": {
"account_locked": false,
"attempts": 3,
"email": "jane.doe@example.com",
"person_uid": "c1135358-29fa-4b0f-9742-ba4bc4c22e1a"
}
}
```
## security.password.reset\_requested
`security.password.reset_requested` is sent when a password reset was requested.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `email` (string, email)
* `person_uid` (string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "security.password.reset_requested",
"data": {
"email": "jane.doe@example.com",
"person_uid": "c1135358-29fa-4b0f-9742-ba4bc4c22e1a"
}
}
```
# Service Webhook Events
Source: https://docs.megaport.com/api/webhooks/events/service
This help topic describes the service webhook events.
This topic describes the service events sent by Megaport's webhooks.
## service.availability.updated
`service.availability.updated` is sent when service availability changes.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `service_type` (string)
* `service_uid` (string, UUID)
* `status` (string, "down" | "up")
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "service.availability.updated",
"data": {
"service_type": "vxc",
"service_uid": "34ee661a-18f0-4c30-8a73-e2d7e0ab641d",
"status": "up"
}
}
```
## service.bgp.availability.updated
`service.bgp.availability.updated` is sent when BGP availability changes.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `mcr_service_uid` (string, UUID)
* `peer_asn` (integer, int64)
* `peer_ip_address` (string)
* `status` (string, "down" | "up")
* `vxc_service_uid` (string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "service.bgp.availability.updated",
"data": {
"mcr_service_uid": "34ee661a-18f0-4c30-8a73-e2d7e0ab641d",
"peer_asn": 12076,
"peer_ip_address": "172.16.35.22",
"status": "down",
"vxc_service_uid": "e513ab3e-8b0c-4d88-bef0-1f7358897d6e"
}
}
```
## service.configured
`service.configured` is sent when a service is configured.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `service_type` (string)
* `service_uid` (string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "service.configured",
"data": {
"service_type": "megaport",
"service_uid": "34ee661a-18f0-4c30-8a73-e2d7e0ab641d"
}
}
```
## service.terminated
`service.terminated` is sent when a service is terminated.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `service_type` (string)
* `service_uid` (string, UUID)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "service.terminated",
"data": {
"service_type": "megaport",
"service_uid": "34ee661a-18f0-4c30-8a73-e2d7e0ab641d"
}
}
```
# User Webhook Events
Source: https://docs.megaport.com/api/webhooks/events/user
This help topic describes the user webhook events.
This topic describes the user events sent by Megaport's webhooks.
## user.registered
`user.registered` is sent when a user is registered.
The payload of this event has the following structure:
* `company_uid` (string, UUID)
* `metadata` (object)
* `environment` (string)
* `schema_version` (string)
* `timestamp` (string, date-time)
* `type` (string)
* `data` (object)
* `email` (string, email)
* `first_name` (string)
* `last_name` (string)
* `person_uid` (string, UUID)
* `position` (string)
For example:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"company_uid": "681ef39b-436b-40dd-a914-26391db2689c",
"metadata": {
"environment": "production"
},
"schema_version": "1",
"timestamp": "2026-04-23T10:29:12Z",
"type": "user.registered",
"data": {
"email": "jane.doe@example.com",
"first_name": "Jane",
"last_name": "Doe",
"person_uid": "c1135358-29fa-4b0f-9742-ba4bc4c22e1a",
"position": "Network Engineer"
}
}
```
# Megaport CLI Overview
Source: https://docs.megaport.com/cli/index
This help topic describes the Megaport CLI features.
This topic introduces Megaport services and the Megaport command-line interface (CLI), which is currently in beta. It is intended for users getting started with the Megaport CLI.
## What is Megaport?
Megaport is a global Network as a Service (NaaS) provider that makes it easy to connect your network to cloud services such as AWS, Microsoft Azure, and Google Cloud without needing complex physical infrastructure.
It uses a software-defined network (SDN) to let you create scalable, secure, and on-demand virtual connections called Virtual Cross Connects (VXCs), between data centers, cloud providers, and enterprise networks. If you are new to Megaport, see [Introducing Megaport](/overview/).
## What is a CLI?
A CLI is a text-based interface used to interact with a computer's operating system or software by typing specific commands into a terminal or console.
Unlike a graphical user interface (GUI), which relies on icons, menus, and mouse clicks, a CLI processes lines of text to execute tasks, manage files, and run scripts.
It is favored by developers and system administrators for its speed, precision, and ability to automate complex workflows through scripting. While it requires an understanding of specific command syntax, it offers direct control over a system's underlying architecture that visual interfaces often lack.
## What is the Megaport CLI?
The Megaport CLI gives you direct, programmable access to the Megaport software-defined networking platform from your terminal. Whether you are provisioning a single Port or automating a multicloud network across three continents, you can do it from the command line.
Detailed guidance on installation, authentication, first commands, core concepts, tutorials, live demos, and reference material is available at [Master the Megaport CLI](https://tutorials.megaport.com/cli/).
## What are the key benefits of Megaport CLI?
The Megaport CLI enhances speed and efficiency by replacing multi-step web wizards with single-command executions, allowing you to manage network resources in seconds without navigating the Portal.
Built with an automation-first approach, the Megaport CLI integrates into Continuous Integration (CI) and Continuous Deployment (CD) pipelines and Infrastructure as Code (IaC) workflows.
The Megaport CLI is suitable for network engineers, cloud and platform engineers, DevOps and site reliability engineers, solution architects, and other technical roles.
## What can you do with the Megaport CLI?
The Megaport CLI provides access to Megaport services and account configuration.
For example:
* **Provision and manage infrastructure** -- Create and manage Ports, VXCs, MCRs, MVEs, Internet Exchange connections, NAT Gateways and other services.
* **Connect to any CSP** -- Enable multicloud connections such as AWS Direct Connect, Azure ExpressRoute, Google Cloud Interconnect, and so on.
* **Troubleshoot MCR routing** -- Use the MCR Looking Glass commands to view IP and BGP routes, check the routes advertised to or received from a BGP neighbor, and run ping and traceroute tests from an MCR.
In addition, the Megaport CLI offers several features that are not available in the Portal:
* **Explore the network** -- Browse more than 1,100 locations across 30 countries and list CSPs and their port configurations.
* **Automate operations** -- Use script-friendly input and output for managing CI and CD pipelines. The CLI supports three input modes: interactive prompts, CLI flags, and JSON input through `--json` (inline) or `--json-file` (file-based). You can format the output as a table, JSON, CSV, or XML, or use a custom Go template.
* **Provision from a configuration file** -- Define multiple Ports, MCRs, MVEs, and VXCs in a single YAML or JSON file, then provision them all with the `apply` command. The CLI creates the resources in dependency order. You can also validate the file before provisioning and choose to have the CLI delete the created resources automatically if provisioning fails.
* **Run it anywhere** -- Run the CLI natively on all major operating systems, in Docker containers, or in a web browser through WebAssembly. The browser version does not support the `apply` command or file-based input such as `--json-file`.
## Helpful references
* [Automation & Scripting](https://tutorials.megaport.com/cli/tutorials/automation)
* [Connections Overview](/connections/overview)
* [Creating a Port](/connections/creating-port)
* [Internet Exchange Overview](/ix)
* [Master the Megaport CLI](https://tutorials.megaport.com/cli/)
* [MCR Overview](/mcr)
* [Megaport API Documentation](https://dev.megaport.com/)
* [Megaport Internet Overview](/megaport-internet)
* [Megaport NAT Gateway Overview](/nat)
* [MVE Overview](/mve)
* [Service Provisioning Methods](/provisioning-methods)
* [Viewing Traffic Routing through MCR Looking Glass](/mcr/mcr-looking-glass)
# VXC, Megaport Internet, and IX Billing
Source: https://docs.megaport.com/finance/billing-details
This help topic describes how to view billing details for a VXC, Megaport Internet connection, or IX.
This topic describes billing details for VXCs, Megaport Internet connections, and Internet Exchange (IX) connections.
Billing starts as soon as the service is in live status. Each month, for metro VXCs you are billed a flat fee based on your connection speed and contract term. Non-metro VXCs are billed based on usage. VXC speed can be changed at any time and this will affect the billing amount. The service is charged on a postpaid basis.\
For example, if you place your order on January 15, your first invoice will be issued on February 1, and the charge will cover the period from January 15 to January 31.
Summary of service type and billing:
* **Metro VXC** -- Flat rate
* **Local IX** -- \$0
* **Non-metro (Zone and Interzone) VXC** -- Usage based billing
* **Remote IX** -- Usage based billing
* **Megaport Internet** -- Usage based billing
If any contract term changes occurred within the month, billing will reflect a sum of the charges. Megaport incorporates a cap of 28 days per month to calculate the percentage allocation of the rate charged.
## Viewing billing details
The Billing page shows billing details for the selected connection. You can view upcoming estimated bills and any changes in the configured speed over a given month for a .
If your account is managed through a Megaport partner, the partner manages the billing. Contact your partner for your billing details.
**To view billing details for a **
1. Log in to the Megaport Portal and choose **Services**.
2. Click the gear icon next to the connection.
3. On the Connection Details page, click **Billing**.
The Billing graph shows the configured speed over the current billing month and the Estimated Next Bill. The Estimated Next Bill for the current month is updated with each change to the service.
The shaded area of the graph shows the configured speeds for the portion of the month that has already passed. The dotted line shows the expected speed for the rest of the billing month, assuming that no changes are made.
To view details for a previous month, click the Billing Month and select a month.
## Billing Details table
The Billing Details table shows the configured speed for the connection, as well as any changes made to the speed during the selected month. Each speed change creates a new entry in the table.
Each entry includes these billing details:
* **Speed (Mbps)** -- The configured speed for the connection.
* **Start/End** -- The date range that the connection was configured at this speed. Time is displayed as UTC+10 (Brisbane time).
* **Duration** -- The length of time that the connection is expected to be configured at the current speed. When viewing the current month, the duration for the last configured speed is extended to the end of the 28-day billing cycle, and the price is calculated based on that duration.
* **Price** -- The cost of the connection in the market-enabled currency. The price is based on the amount of time that the connection was configured at that speed.
Optionally, click **Download CSV** to download the billing data shown in the comma-separated values (CSV) format. You can use the CSV file to import the data into spreadsheets and databases. You can open the CSV file in any text editor.
## Cancellation
You can cancel a VXC, Megaport Internet connection, or IX connection at any time. Canceling a service on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. You can waive the ETF yourself by ordering an eligible replacement service.
For more information, see:
* [Terminating a VXC](/connections/terminating-vxc)
* [Terminating a Megaport Internet Connection](/megaport-internet/terminating-connection)
* [Terminating an IX](/ix/terminating-an-ix)
* [Managing Early Termination Fees (ETF Management)](/finance/etf-management)
## Helpful references
* [Billing Overview](/finance/overview)
* [Enabling Billing Markets](/finance/enabling-market)
* [IP Address Billing](/finance/ip-address-billing)
* [IX Pricing and Contract Terms](/finance/ix-pricing)
* [MCR Billing](/finance/mcr-billing)
* [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing)
* [MVE Billing](/finance/mve-billing)
* [NAT Gateway Billing](/finance/nat-gateway-billing)
* [Port Billing](/finance/port-billing)
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Quoting Service Cost
Source: https://docs.megaport.com/finance/creating-estimates
This help topic describes how to create a quote for the cost of Megaport services.
This topic describes how to quickly create a quote to estimate the cost of deploying Megaport services, before actually ordering the services.
Entering details of the services into the Quoting Tool helps you plan the overall cost of Megaport services within a specified time period. This provides a clear idea of the design, services needed, and cost breakdown for planning.
You can use the Megaport Quoting Tool to:
* Create solution quotes
* Save a quote
* View all saved quotes
* Edit saved quotes
* Download saved quotes
* Track quote status
* Print quotes for review
* Compare pricing for different terms and currencies side by side.
## Creating a quote
Use your Megaport Portal credentials to log in to the [Quoting Tool](https://pricing.megaport.com/).
Your login takes you to the Quoting Tool Saved Quotes page. Use the Saved Quotes page to view a list of your company's quotes and create, duplicate, save, and print and send quotes for review.
The Saved Quotes page displays all your saved quotes. The list includes quotes where the created date is less than six months old. Quotes are deleted after six months.
By default, the page is sorted by the date the quote was created, in descending order. The most recent quote is listed first.
**To create a quote**
1. On the Saved Quotes page, click **Create New Quote**.
2. Select whether this is for an **Existing Customer** or a **Potential Customer**.
* **Existing Customer** -- Select this option if the quote is for a customer that already has an account with Megaport. Select the company name from the **Target Company** drop-down list.
* **Potential Customer** -- Select this option if the quote is for a potential customer that does not have an account with Megaport. Enter the potential customer's company name in the **Company Name** field.
The Quote Builder page appears. This page shows the Quote Builder details area, which contains the quote name, quote ID, company name, user who created the quote, created date, and quote status. The **Created By** field automatically populates with the email address of the logged-in user.
3. Enter a name for the quote in the **Quote Name** field.\
The company name cannot be changed.
4. Select a service to add to the quote: Port, MCR, MVE, NAT Gateway, IP Address, or Latitude.sh products.
5. Click **Choose Location** and select the service location.
6. Enter the required fields, such as name, rate limit, currency, term, diversity zone, Cross Connect, and subnet size if available. Requirements vary by service.
7. If you want to exclude the cost of this service from the quote, select **Exclude (service type)** from quote.\
You might do this, for example, if you need the service configured to replicate a network design without including the cost in the quote.
8. Add the service.
9. Click **+Connection** to add a connection to the service. For connections, select a destination type. The procedure varies slightly depending on the destination type.
* **Cloud** -- Select a provider, destination, and a diversity zone if available.
* **Private** -- Select a destination.
* **Marketplace** -- Select a Marketplace provider and destination.
* **Internet Exchange** -- Select a location and a term. The default term is 12 months.
* **Compute** -- Select a Latitude.sh destination.
* **Megaport Internet** -- Select a location.
* **Megaport Object Storage** -- Select a storage destination.
10. Enter the connection name, minimum term, and rate limit, where applicable. Exclude the service cost from the quote if required.
11) Click **Save Connection** to add the connection.
12) Continue adding the required services to the quote.
13) Click **Save** on the right when done.\
The Quote ID field is automatically populated with a system-generated UID and the quote status is set to *Saved*.
14) Click **Close** to view the Saved Quotes page.
### Summary
The summary shows the total monthly cost of all services in the quote, including any add-ons. The summary is updated when you change the term or currency.
## Importing existing services
You can import existing live or configured services from your account into a quote. This allows you to add services that are already deployed without recreating them manually.
**To import existing services**
1. In the Quote Builder, click the import existing services icon.
2. In the **Add Existing Services** dialog, select the services and connections you want to add to the quote. Use the search field to filter by name or service UID.
When you select a connection, its associated A-end service is automatically selected.
3. To keep a service in the quote design but leave it out of pricing calculations, select **Exclude From Quote** for that service.
4. Click **Add Selected** to add the services to your quote.
The imported services and connections appear in your quote with their current configuration details. Each imported row is marked with an import icon and a chip showing a shortened service ID, consisting of # followed by the first part of the service UID. The same indicator appears in the editor header when you open an imported service or connection. Click the chip to copy the full service UID to your clipboard.
### Editing imported services
Imported services and connections represent existing deployments, so some fields are restricted when you edit them in a quote. These restrictions apply only to imported rows and do not affect new services that you add to the quote.
The restrictions take these forms:
* Some fields are read-only and cannot be changed. For all service types, this includes the name, location or connection destination, and currency. The speed or rate limit is also read-only for Port, MCR, MVE, and NAT Gateway services. For MVE services, the vendor, version, and size are read-only. For NAT Gateway services, the session count is read-only.
* For all service types, you can keep the term the same or extend it, but you cannot shorten it. For VXC and IX connections, whether you can change the rate limit depends on the term:
* **On a fixed term** -- you can keep the rate limit the same or increase it, but you cannot reduce it; a lower value cannot be saved.
* **On a month-to-month term** -- you can also reduce the rate limit down to the default minimum rate limit for the connection.
* You cannot remove existing add-ons and features, but you can add to them. For example, you cannot remove a Cross Connect from a Port or IPsec from an MCR, reduce the number of IPsec tunnels, or reduce the number of ports in a link aggregation group (LAG).
### Renewing imported services
When you edit an imported service or connection so that its price changes, for example by extending the term or increasing the rate limit, the Quoting Tool treats the line as a renewal and compares the current contracted price with the new price.
A **Renewal** tag appears next to the service or connection in the Quote Builder and in the editor header.
In the editor, a renewal price summary shows the current price, introduced by **was** with the previous price struck through, alongside the new **Renewal price** and the change in price as both an amount and a percentage. When you change the term, the new term appears in the label, for example **Renewal price (36 MO)**.
The Quote Summary shows the same comparison for each renewal line: the current price struck through, the new price, and the change as an amount and a percentage.
When a freshly imported service can be renewed on its current term at a different price, a **Renew With Same Term** button appears in the editor footer. Click it to renew the service on its current term without changing any other field.
## Sorting quotes
You can sort the Saved Quotes list by date, quote ID, quote name, and user who created the quote.
**To sort by column heading**
* Click the up/down triangles next to a column heading.\
The table columns reload, if necessary.
* Click the heading again to reverse the order.\
The triangle color reflects the current bidirectional sort order.
**To delete a quote**
1. On the Saved Quotes page, click the down arrow next to the quote.
2. Choose **Delete**.
3. Click **Yes** to confirm.
You can only delete quotes with a *Saved* status.
## Editing a quote
It's easy to change or duplicate a saved quote. For example, you can add a new service, add a Virtual Cross Connect (VXC) to a previously created service, or create a quote based on an existing quote.
Quotes that have been registered cannot be edited. They can be viewed and duplicated to create a new quote, which can then be edited.
**To edit a quote**
1. On the Saved Quotes page, click **Edit** next to the quote.
2. Make the required changes.\
For example, change the term of a service or add a new connection.\
The changes to the quote are reflected in the pricing.
3. Click **Save**.
4. To return to the Saved Quotes page, click **Close**.
**To create a quote based on an existing quote**
1. On the Saved Quotes page, click the down arrow next to the quote.
2. Choose **Duplicate**.\
A prompt is displayed confirming the quote was successfully duplicated. The new quote is added to the Saved Quotes page, with *(Duplicate)* added to the quote name.
3. Click **Edit** to make changes to the new quote.
4. Enter a unique descriptive name in the **Quote Name** field to identify the quote.
5. Make any changes unique to this quote. For example, add a new service or connection, or change an existing service or connection.\
Duplicating a quote doesn't copy the Submitted Date, or the Created By and Created Date values. These fields are unique for each quote. The Created By and Created Date values automatically populate with the current logged-in user and date.
6. Click **Save**.
## Comparing pricing for different terms and currencies
The Advanced View lists every service and its add-ons in a single table, showing the monthly rate for every available term, currency, and pricing level you have chosen to display.
From the Advanced View, you can add or remove terms and currencies to change the pricing display. This enables you to compare pricing for different terms and currencies side by side, for each service in the quote.
**To compare pricing for different terms and currencies**
1. Click **Analyze & Export** in the Quote Builder to open the Advanced View.
2. Use **Display Terms** to select the terms for which you want to display pricing. You can select one or more terms, and the table updates to show the monthly rate for each service for every selected term.
3. Use **Display Currency** to select the currencies for which you want to display pricing. You can select one or more currencies, and the table updates to show the monthly rate for each service for every selected currency.
The selected terms and currencies carry over into the downloaded CSV or PDF file. The Advanced View also includes a **Download CSV** button and a **Download PDF** button.
## Add-on pricing
When you add an optional add-on (IPsec, Cross Connect, or DDoS Protection) to a service or connection, the Quoting Tool displays an **Includes** indicator with the add-on name on that item, both in the Network Design list and in the Advanced View. A service or connection can display more than one indicator when it has multiple add-ons.
The quote pricing also reflects add-on charges:
* Each service's summary price and the quote subtotal includes the monthly add-on charges, and they recalculate when you change the term.
* In the Advanced View, each add-on appears as a separate line item beneath its service, showing the monthly charge for every available term. When partner pricing is shown, the add-on line items repeat beneath the partner row.
* A term with no add-on charge displays **N/A** instead of a zero amount.
## Downloading a quote
You can download a quote in two formats: PDF and CSV. The PDF version is ideal because it includes the quote details on a Megaport letterhead and a legal disclaimer that the quote is non-binding. Once the quote is downloaded, you can share it for review.
**To download a quote**
1. On the Saved Quotes page, click **Edit** next to the quote.
2. Click **Analyze & Export**.
3. Choose **Download CSV** or **Download PDF**.
* **Download CSV** -- Downloads the quote in the comma-separated values (CSV) format. You can use the CSV file to import the data into spreadsheets and databases. You can open the CSV file in any text editor.
* **Download PDF** -- Shows a preview of the formatted data. Before you print or save the file, you can optionally include these sections:
* **About Section** -- Include or edit the introductory paragraph that describes Megaport.
* **Tax Registration Number** -- Enter a tax registration number to include on the PDF.
* **Company Address** -- Enter a company address to include on the PDF.
Click **Print PDF** to open the Print dialog box. You can then either save to PDF or print. When you are finished, click the browser back button to return to the previous page.
When you download a quote as a CSV or PDF, the file reflects the terms, currencies, and pricing level (retail, partner, or both) you have chosen to display, along with diversity zone information for each service.
## Logging out
Click **Logout** to safely log out of the Megaport application.
If you have the Megaport Portal or Quoting Tool open in multiple tabs in the same browser, logging out in one tab automatically logs you out of all other open tabs of that application. The other tabs update immediately without requiring a refresh and display a message with a link to log in again.
This behavior applies only to tabs in the same browser and is application-specific. Logging out of the Megaport Portal does not log you out of the Quoting Tool, and vice versa.
## Helpful references
* [Billing Overview](/finance/overview)
* [IX Pricing and Contract Terms](/finance/ix-pricing)
* [MCR Diversity](/mcr/mcr-mve-diversity)
* [MCR Pricing and Contract Terms](/finance/mcr-pricing)
* [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing)
* [Megaport Object Storage Pricing and Contract Terms](/finance/storage-pricing)
* [MVE Diversity](/mve/mcr-mve-diversity)
* [MVE Pricing and Contract Terms](/finance/mve-pricing)
* [NAT Gateway Pricing and Contract Terms](/finance/nat-gateway-pricing)
* [Port Diversity](/connections/port-diversity)
* [Port Pricing and Contract Terms](/finance/port-pricing)
* [Quoting Service Cost as a Megaport Partner](/partners/services/creating-estimates)
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Credit Card Payments
Source: https://docs.megaport.com/finance/credit-card-payments
This help topic provides information about credit card payments.
If you are not able to make payments by wire or , or do not have a local bank in your enabled market, you can pay by credit card. To use a credit card for automatic payments, you need to register a card in the Megaport Portal. You can also register a card to automatically populate payment details for one-off payments.
Payment details do not appear if your account is managed by a partner. Contact your partner to arrange billing and payment.
**To register a credit card with Megaport**
1. Visit the Megaport Portal and log in.
2. Choose Billing > Billing Markets.
3. In an enabled market, click the Make Payment icon.
4. In the Payments tab, click **Register Card**.
5. Enter the Card Number, Expiry, and CVC.
6. Specify whether you want to enable automatic payments for this credit card.
7. Click **Register Card**.
If you select Automatic Payments, no further action is required. Payments will be processed on the 20th of each month for the outstanding balance on your account.
If you do not select Automatic Payments, you need to submit payments before your invoice due date. Follow the procedures in [Making a one-off credit card payment](#making-a-one-off-credit-card-payment).
## Markets enabled for credit card payments
The following billing markets and currencies accept credit card payments:
| **Billing Market** | **Local Currency Accepted** | **USD Accepted?** | **Other Currencies Accepted** |
| - | :-: | :-: | :-: |
| Australia | AUD | **✓** | NZD |
| Belgium | EUR | **✓** | |
| Bulgaria | EUR | **✓** | |
| Canada | CAD | **✓** | |
| Finland | EUR | **✓** | |
| France | EUR | **✓** | |
| Germany | EUR | **✓** | |
| Hong Kong | HKD | **✓** | |
| Ireland | EUR | **✓** | |
| Italy | EUR | **✓** | |
| Japan | JPY | | |
| Netherlands | EUR | **✓** | |
| New Zealand | NZD | **✓** | AUD |
| Portugal | EUR | **✓** | |
| Singapore | SGD | **✓** | |
| Spain | EUR | **✓** | |
| Sweden | SEK | | |
| Switzerland | CHF | **✓** | |
| UK | GBP | **✓** | EUR |
| USA | USD | | |
## Credit card processing fees
Credit card processing fees are added to the payment amount and reflected on your next invoice. Megaport passes these fees directly from our service provider, Stripe.
Megaport does not take or hold any PCI DSS information.
You can get additional information on credit card transaction fees from Stripe for these markets:
* [Australia](https://stripe.com/au/pricing)
* [Belgium](https://stripe.com/en-gb-be/pricing)
* [Bulgaria](https://stripe.com/en-gb-bg/pricing)
* [Canada](https://stripe.com/en-gb-ca/pricing)
* [Denmark](https://stripe.com/en-gb-dk/pricing)
* [Germany](https://stripe.com/en-gb-de/pricing)
* [Finland](https://stripe.com/en-gb-fi/pricing)
* [France](https://stripe.com/en-gb-fr/pricing)
* [Hong Kong](https://stripe.com/en-gb-hk/pricing)
* [Ireland](https://stripe.com/ie/pricing)
* [Italy](https://stripe.com/it/pricing)
* [Japan](https://stripe.com/en-gb-jp/pricing)
* [Netherlands](https://stripe.com/en-gb-nl/pricing)
* [Norway](https://stripe.com/en-gb-no/pricing)
* [New Zealand](https://stripe.com/nz/pricing)
* [Portugal](https://stripe.com/pt/pricing)
* [Singapore](https://stripe.com/en-gb-sg/pricing)
* [Spain](https://stripe.com/en-gb-es/pricing)
* [Switzerland](https://stripe.com/en-gb-ch/pricing)
* [Sweden](https://stripe.com/en-gb-se/pricing)
* [United Kingdom (UK)](https://stripe.com/gb/pricing)
* [USA](https://stripe.com/en-gb-us/pricing)
## Making a one-off credit card payment
If you have the appropriate permissions, you can use a credit card to make a one-off payment of an invoice at any point in the billing cycle.
**To make a one-off payment**
1. Visit the Megaport Portal and log in.
2. Choose Billing > Billing Markets.
3. Click the Make Payment icon.
4. Click **Make One-off Payment**.
5. Add the payment information.\
If you have registered a credit card, the payment information automatically appears.
6. For the Payment Description, enter the payment amount and invoice number.
7. Click **Make One-off Payment**.
# Customer Field Services
Source: https://docs.megaport.com/finance/customer-field-services
This help topic describes the customer field service troubleshooting process and associated fees.
This topic describes the customer field service process and how Megaport calculates fees associated with field services.
## Megaport field service process
From time to time, Megaport receives requests for a field service technician's onsite attendance in the data center.
### Why are field service technicians necessary?
As part of the troubleshooting process, both Megaport and customers rely on either the data center or third-party technicians to validate that the physical connections are working as expected.
Megaport (at the B-End) opens a ticket and arranges a field service technician to work with a Megaport Technical Support Engineer (TSE) and investigate the root cause of the issue. This includes validating the correct operation of the:
* Physical connections within the Megaport rack.
* .
* Structured cabling up to the demarcation point.
Customers (at the A-End) arrange a field service technician to validate the physical connections within their rack and the cross-connect running to the Megaport demarcation point.
### Physical connections
The two most common scenarios for physical connectivity between the customer rack (A-End) and the Megaport demarcation point (B-End) are:
* Scenario 1: Connection into Megaport rack via a meet-me room
Data center technicians run the customer cross connect to the Megaport demarcation as defined in the Megaport .
The Megaport demarcation point is generally hosted within a or interconnect. The customer cross connect is run to the Port within this demarcation as defined in the Megaport LOA.
* Scenario 2: Connection into Megaport rack without a meet-me room
When there is no meet-me room available at the data center and a customer orders a cross connect, the data center runs a patch lead directly from the customer rack to the Megaport patch panel.
### When are field service fees passed on to a customer?
Megaport may pass field service fees on to a customer after proving:
* The service is operating within specification up to the Megaport demarcation point, according to the Megaport LOA.
* The fault is beyond the Megaport demarcation and resides within the customer network. A field service technician is dispatched to the data center to investigate.
\--or--
* A field service technician is dispatched to assist in a customer project: for example, moving Ports.
Troubleshooting or assistance by a field service technician is a pay-per-use service.
### How will I be informed of customer field service fees?
Before dispatching a field technician to the data center, Megaport provides you with this information:
* A confirmation that additional service fees might be passed on to you.
* Complete details of the issue investigation to date.
* A link to the Megaport Rate Card detailing the field service billing fees.
* A request for acknowledgement of the service fees and authorization to proceed.
After you acknowledge the service fees and authorize Megaport to proceed, a technician is dispatched to the data center.
When the field service technician completes the work, Megaport finalizes and closes the customer ticket to resolve the issue. Field service fees are added to your invoice for the next billing cycle. A summary of the work performed appears under the Field Services Description.
### How are customer field service fees calculated?
* Services provided by field service technicians are billed hourly with a minimum one-hour charge.
* Fees are incurred at a flat rate according to the rate card.
* The fees are billed in the currency of the customer's billing market according to the rate card:
| Area/Region | Business Hours | After Hours/Expedited |
| - | - | - |
| Asia Pacific | \$250 (AUD) | \$350 (AUD) |
| Europe | €180 (EUR) | €280 (EUR) |
| North America | \$250 (USD) | \$350 (USD) |
### How can I prevent customer field service fees?
* Review the [Troubleshooting Overview](/troubleshooting/overview) and perform the necessary checks from your side to validate your network.
* Confirm with any other providers that your network connects to that there are no maintenance works, outages, or any other activities that could be affecting your service.
* If you have recently provisioned a service, confirm with the data center that they have completed all physical checks after connection, such as rolling the fiber to confirm polarity.
# Downloading Invoices
Source: https://docs.megaport.com/finance/download-invoice
This help topic describes how to download invoices in the Megaport Portal.
Megaport invoices for services every month. You can download individual invoices in PDF or CSV format using either of these methods:
* **Billing > Invoices** -- A centralized view of all invoices across all your billing markets. You can filter by Invoice ID, market, payment status, or date range.
* **Billing > Billing Markets** -- A per-market view. Use this to browse invoices for a specific billing market.
- If your account is managed through a Megaport partner, the partner manages the billing and the Portal does not display billing markets or invoices. Contact your partner for billing details.
- Invoice downloads are not available for the Brazil and India billing markets:
* For the Brazil billing market, Accounts Receivable (AR) sends invoices, statements, and other standard communications to the billing contact email address registered in your account. For invoice inquiries about your Brazil billing account, contact [Megaport Accounts Receivable](mailto:ar.global@megaport.com).
* For the India billing market, invoices, statements, and other standard communications are sent by our invoicing agent. For inquiries, contact [Megaport Accounts Receivable](mailto:ar.global@megaport.com).
**To download an invoice from the Invoices page**
1. Visit the Megaport Portal and log in.
2. Choose Billing > Invoices.
The Invoices page displays these columns:
| **Column** | **Description** |
| - | - |
| Invoice ID | Unique identifier for the invoice. |
| Date | Date the invoice was generated. |
| Due Date | Date the payment is due. |
| Market | The billing market the invoice belongs to. |
| Amount | Total amount charged. |
| Open Balance | Remaining unpaid amount. |
| Status | Payment status: Pending, Paid, or Overdue. |
| Download | Options to download the invoice as PDF or CSV. |
3. (Optional) Use the filter bar to narrow the list. You can filter by Invoice ID, billing market, payment status, or date range. To clear all filters, click **Clear filters**.
4. In the invoice row, click **PDF** or **CSV**:
* **PDF** – Opens a new browser tab with a PDF version of the invoice.
* **CSV** – Downloads the invoice in comma-separated values (CSV) format. You can import the file into spreadsheets or databases, or open it in any text editor.
**To download an invoice from Billing Markets**
1. Visit the Megaport Portal and log in.
2. Choose Billing > Billing Markets.
3. Click the View Invoices icon.\
Invoices for that billing market are displayed. Each invoice is available to download as a CSV or PDF file.
4. By default, the page shows invoices from the last 12 months. To narrow the list, select a date range.
5. Click the CSV or PDF icon to download the invoice.
* **CSV** – Downloads the invoice in comma-separated values (CSV) format. You can import the file into spreadsheets or databases, or open it in any text editor.
* **PDF** – Opens a new browser tab with a PDF version of the invoice.
For more information about your invoice, see [Understanding Your Megaport Invoice](/finance/invoices).
# Enabling Billing Markets
Source: https://docs.megaport.com/finance/enabling-market
This help topic describes how to enable billing markets for an account in the Megaport Portal.
Before you can order services in a region, you need to enable a billing market.\
We recommend that you enable multiple markets to cover your business needs. Each billing market will receive its own standalone invoice for that billing entity.
**To enable a billing market**
1. Visit the Megaport Portal and log in.
2. Choose Billing > Billing Markets.\
The Billing Markets page displays a table of all available billing markets, showing the country, status, currency, billing contact, billing email, and PO number for each market.
3. (Optional) Use the **Search by country** field to find a specific market, or use the **All**, **Enabled**, and **Disabled** tabs to filter the list.
4. Click **Enable** next to the billing market you want to enable.
Before choosing a currency for your billing market, see [Credit Card Payments](/finance/credit-card-payments#markets-enabled-for-credit-card-payments) to view the markets and currencies where credit card payments are currently accepted.
5. Complete all fields for the chosen billing market.
* **Billing Currency** -- The billing currency for this market.\
Note that once you have chosen a currency for the billing market, it cannot be changed. For more information, see the Accepted Currencies table below.
* **Company Legal Name** -- The legal registered company name that appears in your profile.
* **Billing Contact Details** -- The name, phone, email address, physical address, and country for the billing contact. Use commas to separate multiple email addresses. For the Billing Address, enter the business location where the key decision makers who procure and provision Megaport services are based. The Billing Contact will be emailed an invoice on a monthly basis.
When you specify a billing contact email address, Megaport sends an invitation to that address. The recipient can accept or decline the invitation directly from the email without logging in to the Portal. After the invitation is accepted, invoices are sent to the billing contact email address. If the invitation is declined, Megaport is notified.
For tax calculation, Megaport uses the country specified in the Billing Address linked to the billing market. When you enable a market in the UK, Australia, Singapore, Switzerland, or France, you might be required to provide additional information needed to calculate an accurate tax rate. For example:
* **United Kingdom** -- Answer whether you have registered for the value-added tax (VAT). Registered users must provide their VAT registration number. If yes, confirm whether you have personnel in the UK who use Megaport services.
* **Australia or Singapore** -- Answer whether the legal entity or branch that uses Megaport services is registered for the goods and services tax (GST). Registered users must provide their GST registration number.
* **Switzerland** -- Answer whether you have registered for the value-added tax (VAT). Registered users must provide their VAT registration number. A Swiss VAT ID starts with the prefix CHE, followed by nine numbers, and ends with a suffix representing the language region in which the business is registered: MWST (German), TVA (French), or IVA (Italian).
* **France** -- You must provide a valid French VAT ID. A French VAT ID starts with the prefix FR, followed by 11 characters. You must also provide your SIRET number. A SIRET is 14 digits: your 9-digit SIREN followed by a 5-digit establishment code. The SIREN (the first 9 digits of your SIRET) must match the SIREN portion of your VAT ID.
* **Company Registration No.** -- The tax or VAT registration number as required per region.
The Company Registration Number is optional for the France and Mexico markets, but is mandatory for all other markets.
* **EU Markets (Opting EECC waiver)** -- When you enable a billing market in Austria, Belgium, Bulgaria, Denmark, Finland, France, Germany, Ireland, Italy, Luxembourg, Netherlands, Poland, Spain, or Sweden, you might see an option to opt in to an EECC (European Electronic Communications Code) waiver.
This option appears only if your company is established in an EU Member State. For example, a France-based company enabling Austria will see the waiver option, but a US-based company enabling Austria will not.
The EECC waiver applies only if your organization is a micro enterprise, small enterprise, or not-for-profit organization.
If you select **Yes** to opt in, you will see a declaration stating that you qualify as a micro or small enterprise or a not-for-profit organization under the laws of your country. By opting in, you waive the rights granted to such organizations under the national rules implementing the European Electronic Communications Code (EECC). This waiver covers, as applicable under local law:
* The right to receive pre-contractual information and a Contract Summary in the prescribed form.
* The right to access monitoring tools for Internet Access Services billed on the basis of time or volume.
* Restrictions on the maximum mandatory contractual commitment period.
Select the **I expressly agree to this waiver** check box to confirm.
If you select **No**, the EECC waiver will not apply and you will keep all rights under the EECC regulations.
* **Mexico Market Only** - These fields are mandatory Mexico TAX Registration details for the CFDI (Electronic billing schema defined by the Mexican federal tax code).
* **Company Type** – The legal tax ID type of the taxpayer (company (Legal entity), individual (Legal person), or foreign company). A company or individual is the taxpayer registered with the Mexico Federal Taxpayer Registry. A foreign company is a business or individual not registered with the Mexican TAX Administration Service (SAT).
* **Tax Regime** – The Fiscal Regime code registered with the Mexican TAX Administration Service (SAT).
* **Tax Purpose** – Relates to the use of the electronic tax invoice (CFDI) that will be issued to the taxpayer receiving the invoice. Use this field to record the economic activity on the electronic invoice that will be reported to the Mexican TAX Administration Service (SAT).
* **RFC Number** – The Federal Taxpayer Registry number as issued by the Mexican Tax Administration Service (SAT). An RFC number is assigned to each taxpayer (Legal entity or person) that carries out economic activity in Mexico.
* **USA Market Only** - Federal USF Traffic Certification – As required by the Federal Communications Commission (FCC), confirmation is needed here on the nature of the traffic where you purchase Megaport data transmission products between two points in the same state.
For further context, the Federal Universal Service Fund (USF) is a charge levied by the FCC on interstate telecommunications services and this certification is needed to ensure we apply Federal USF charges appropriately on your invoices.\
Complete the **Federal USF Interstate Traffic Certification** check box according to the following rules:
* Select the check box to certify that more than 10% of traffic is interstate in nature in relation to all data transmission products purchased from Megaport - and therefore subject to Federal USF charges.
* Leave the check box clear to certify that 10% or less of traffic is interstate in nature in relation to all data transmission products purchased from Megaport - and **NOT** subject to Federal USF charges.
You acknowledge that Megaport’s determination of jurisdiction of the services and assessment of Federal USF will be based upon the information provided by you in this certification. If Megaport determines that the jurisdiction has been established based upon false, inaccurate or erroneous information, Megaport may bill you for Federal USF that was not previously charged and you will pay these charges.
* **Invoice Purchase Order Number** -- An optional PO number for tracking. This number is optional and appears on all invoices related to its market.
See the [Customer Onboarding](/finance/finance-forms) topic for finance forms that could be required for your business.
6. Select the check box to accept the terms of the Global Services Agreement.
7. Click **Save**.\
After adding a company profile, you can view markets associated with it by choosing User Menu > Admin Settings > Company Profile, then clicking **View Company Markets**.
## Accepted currencies
Accepted currencies vary for each billing market. In most markets, the US dollar (USD) is available as the secondary currency. For example, the Singapore billing market offers the option of billing in both Singapore dollars (SGD) and USD.
Once you have chosen a currency, it cannot be changed.
| **Billing Market** | **Local Currency Accepted** | **USD Accepted?** | **Other Currencies Accepted** |
| - | :-: | :-: | :-: |
| Australia | AUD | **✓** | NZD |
| Belgium | EUR | **✓** | |
| Brazil | BRL | | |
| Bulgaria | EUR | **✓** | |
| Canada | CAD | **✓** | |
| Denmark | EUR | **✓** | |
| Finland | EUR | **✓** | |
| France | EUR | **✓** | |
| Germany | EUR | **✓** | |
| Hong Kong | HKD | **✓** | SGD |
| Ireland | EUR | **✓** | |
| Italy | EUR | **✓** | |
| Japan | JPY | **✓** | |
| Luxembourg | EUR | **✓** | |
| Mexico | USD | **✓** | |
| Netherlands | EUR | **✓** | |
| New Zealand | NZD | **✓** | AUD |
| Norway | EUR | **✓** | |
| Portugal | EUR | **✓** | |
| Singapore | SGD | **✓** | |
| Spain | EUR | **✓** | |
| Sweden | SEK | **✓** | EUR |
| Switzerland | CHF | **✓** | EUR |
| UK | GBP | **✓** | EUR |
| USA | USD | **✓** | |
## Helpful references
* [Billing Overview](/finance/overview)
* [MCR Billing](/finance/mcr-billing)
* [MVE Billing](/finance/mve-billing)
* [NAT Gateway Billing](/finance/nat-gateway-billing)
* [Port Billing](/finance/port-billing)
* [VXC, Megaport Internet, and IX Billing ](/finance/billing-details)
# Managing Early Termination Fees
Source: https://docs.megaport.com/finance/etf-management
This help topic describes how to waive outstanding early termination fees (ETFs) in the Megaport Portal by matching terminated services with eligible replacement services.
This topic describes how to waive early termination fees (ETFs) in the Megaport Portal by matching terminated services with eligible replacement services.
When you terminate a service before the end of its contract term, Megaport calculates an ETF and adds it as a pending charge on your account. Under the [Megaport Global Services Agreement](https://www.megaport.com/legal/global-services-agreement/) (GSA), Megaport allows you to waive the ETF when you order a replacement service on a contract term, with a monthly rate equal to or greater than that of the terminated service, within 30 days before or after the termination. This serves as your formal notification to Megaport of an ETF waiver request under the [Global Services Agreement](https://www.megaport.com/legal/global-services-agreement/).
If you don't waive the ETF within 30 days of service termination, Megaport applies it to your invoice.
## Prerequisites
You must be a Company Admin, Technical Admin, or Finance user to access and use ETF Management. For more information, see [Managing User Roles](/portal-admin/user-management/roles).
Managed accounts can't access ETF Management. Contact your partner to handle ETF waivers on your behalf. For more information, see [Partner-Managed Accounts](/partner/managed).
## Eligible replacement services
A replacement service is eligible to offset an ETF if it meets all of these conditions:
* It is an Eligible Service with a monthly recurring charge and term equal to or greater than the service being terminated.
* It is active within 30 days of termination.
## Understanding the coverage check
The **Coverage check** compares the services you select from both lists:
* **Terminated Services** -- The sum of the monthly rates for all terminated services you have selected.
* **Eligible Replacements** -- The sum of the monthly rates for all replacement services you have selected. This must meet or exceed the Terminated Services total.
If the replacement total is less than the terminated total, the difference is shown as **Short by** in red, and **Next** is disabled. If the replacement total is equal to or greater than the terminated total, the surplus is shown in green. The **Coverage check** also confirms whether the contract term of the selected replacement services covers the remaining term of the selected terminated services. **Next** stays disabled until both requirements are met.
Add or remove services from either list until both the monthly rate and term requirements are met.
By default, amounts are shown in each service's original currency. Use the **Show In** drop-down list at the top of the page to display all amounts in a single currency for easier comparison. Converted amounts are approximate and rounded to the nearest whole currency unit. Your selected currency is retained for the review step.
Changing the display currency doesn't affect the **Coverage check**, which always compares amounts using a consistent currency.
## Waiving an ETF
You can waive one or more outstanding ETFs in a single request by pairing each terminated service with one or more eligible replacement services.
**To waive an ETF using a replacement service**
1. In the Megaport Portal, go to Billing > ETF Management.
2. In the **Terminated Services** list, select the check box next to each service with an ETF you want to waive.
3. In the **Eligible Replacements** list, select the check box next to each replacement service you want to use to cover the selected ETFs.
Services that can't be combined with your current selection are grayed out. Watch the **Coverage check** indicators at the top of the page to confirm your selected replacements cover the combined monthly rate and remaining term of your selected terminated services.
4. Click **Next**.
**Next** is enabled only after the combined replacement monthly rate meets or exceeds the combined ETF monthly rate, and the replacement terms cover the remaining terms of the terminated services.
5. Review the ETFs to be waived and the replacement services you selected, including the total ETF amount and total replacement monthly rate.
6. Select the **I confirm that I have reviewed and agree to the above requirements** check box.
7. Click **Submit**.
If the request succeeds, a confirmation is displayed showing the number of ETFs waived and the total amount. The waived services disappear from the **Terminated Services** list, and the replacement services you used disappear from the **Eligible Replacements** list.
If the request fails, an error is displayed along with a summary of the ETFs and replacement services you attempted to waive, so you have a record to reference.
8. Click **Done**.
## Helpful references
* [Billing Overview](/finance/overview)
* [Managing Contract Terms in Bulk](/finance/term-management)
* [Managing User Roles](/portal-admin/user-management/roles)
* [Megaport Global Services Agreement](https://www.megaport.com/legal/global-services-agreement/)
* [MVE Overview](/mve)
* [Partner-Managed Accounts](/partner/managed)
* [Terminating a MCR](/mcr/terminating-mcr)
* [Terminating a Megaport NAT Gateway](/nat/terminating-nat-gateway)
* [Terminating a Port](/connections/terminating-port)
* [Terminating a VXC](/connections/terminating-vxc)
# Customer Onboarding
Source: https://docs.megaport.com/finance/finance-forms
This help topic has helpful links to finance forms.
This topic lists finance forms that could be required for your business.
If you are looking for additional information, contact [Megaport Accounts Receivable](mailto:ar.global@megaport.com).
## Onboarding letters
* [Australia](https://media.megaport.com/docs/pdf/finance/onboarding/AU-onboarding-letter.pdf)
* [Austria](https://media.megaport.com/docs/pdf/finance/onboarding/AUST-onboarding-letter.pdf)
* [Belgium](https://media.megaport.com/docs/pdf/finance/onboarding/belg-onboarding-letter.pdf)
* [Brazil](https://media.megaport.com/docs/pdf/finance/onboarding/BRA-onboarding-letter.pdf)
* [Bulgaria](https://media.megaport.com/docs/pdf/finance/onboarding/BULG-onboarding-letter.pdf)
* [Canada](https://media.megaport.com/docs/pdf/finance/onboarding/CAN-onboarding-letter.pdf)
* [Denmark](https://media.megaport.com/docs/pdf/finance/onboarding/den-onboarding-letter.pdf)
* [Finland](https://media.megaport.com/docs/pdf/finance/onboarding/FIN-onboarding-letter.pdf)
* [France](https://media.megaport.com/docs/pdf/finance/onboarding/FR-onboarding-letter.pdf)
* [Germany](https://media.megaport.com/docs/pdf/finance/onboarding/GER-onboarding-letter.pdf)
* [Hong Kong](https://media.megaport.com/docs/pdf/finance/onboarding/HK-onboarding-letter.pdf)
* [Ireland](https://media.megaport.com/docs/pdf/finance/onboarding/IR-onboarding-letter.pdf)
* [Italy](https://media.megaport.com/docs/pdf/finance/onboarding/it-onboarding-letter.pdf)
* [Japan](https://media.megaport.com/docs/pdf/finance/onboarding/JP-onboarding-letter.pdf)
* [Luxembourg](https://media.megaport.com/docs/pdf/finance/onboarding/LUX-onboarding-letter.pdf)
* [Mexico](https://media.megaport.com/docs/pdf/finance/onboarding/mex-onboarding-letter.pdf)
* [Netherlands](https://media.megaport.com/docs/pdf/finance/onboarding/NE-onboarding-letter.pdf)
* [New Zealand](https://media.megaport.com/docs/pdf/finance/onboarding/NZ-onboarding-letter.pdf)
* [Norway](https://media.megaport.com/docs/pdf/finance/onboarding/nor-onboarding-letter.pdf)
* [Poland](https://media.megaport.com/docs/pdf/finance/onboarding/pl-onboarding-letter.pdf)
* [Portugal](https://media.megaport.com/docs/pdf/finance/onboarding/pt-onboarding-letter.pdf)
* [Singapore](https://media.megaport.com/docs/pdf/finance/onboarding/SING-onboarding-letter.pdf)
* [Spain](https://media.megaport.com/docs/pdf/finance/onboarding/sp-onboarding-letter.pdf)
* [Sweden](https://media.megaport.com/docs/pdf/finance/onboarding/swe-onboarding-letter.pdf)
* [Switzerland](https://media.megaport.com/docs/pdf/finance/onboarding/sw-onboarding-letter.pdf)
* [UK](https://media.megaport.com/docs/pdf/finance/onboarding/UK-onboarding-letter.pdf)
* [United States](https://media.megaport.com/docs/pdf/finance/onboarding/US-onboarding-letter.pdf)
## W-8
The W-8 form (Certificate of Status of Beneficial Owner for United States Tax Withholding and Reporting Entities) is used to confirm that a vendor is a foreign person and must be provided even if the vendor is not claiming a tax treaty reduction or exemption from withholding.
Megaport is required to provide this form when billing a US entity (local Megaport entity billing a foreign US entity; for example, when Megaport Singapore bills a US customer). These forms are required to be signed and updated annually.
* [Australia](https://media.megaport.com/docs/pdf/finance/W8/Australia.pdf)
* [Brazil](https://media.megaport.com/docs/pdf/finance/W8/Brazil.pdf)
* [Bulgaria](https://media.megaport.com/docs/pdf/finance/W8/Bulgaria.pdf)
* [Canada](https://media.megaport.com/docs/pdf/finance/W8/Canada.pdf)
* [Finland](https://media.megaport.com/docs/pdf/finance/W8/Finland.pdf)
* [France](https://media.megaport.com/docs/pdf/finance/W8/France.pdf)
* [Germany](https://media.megaport.com/docs/pdf/finance/W8/Germany.pdf)
* [Hong Kong](https://media.megaport.com/docs/pdf/finance/W8/Hong-Kong.pdf)
* [Ireland](https://media.megaport.com/docs/pdf/finance/W8/Ireland.pdf)
* [Japan](https://media.megaport.com/docs/pdf/finance/W8/Japan.pdf)
* [Luxembourg](https://media.megaport.com/docs/pdf/finance/W8/Luxembourg.pdf)
* [Mexico](https://media.megaport.com/docs/pdf/finance/W8/Mexico.pdf)
* [Netherlands](https://media.megaport.com/docs/pdf/finance/W8/Netherlands.pdf)
* [New Zealand](https://media.megaport.com/docs/pdf/finance/W8/New-Zealand.pdf)
* [Singapore](https://media.megaport.com/docs/pdf/finance/W8/Singapore.pdf)
* [Sweden](https://media.megaport.com/docs/pdf/finance/W8/Sweden.pdf)
* [Switzerland](https://media.megaport.com/docs/pdf/finance/W8/Switzerland.pdf)
* [UK](https://media.megaport.com/docs/pdf/finance/W8/UK.pdf)
## W-9
US businesses use IRS form W-9 (Request for Taxpayer Identification Number and Certification) to obtain information from vendors that they hire as independent contractors. Businesses use the name, address, and Social Security number (or tax identification number) that contractors provide on the W-9 form to complete the information return. Neither the sender nor the recipient should send a copy to the IRS.
* [USA](https://media.megaport.com/docs/pdf/finance/W9/W-9-May-USA-2026.pdf)
## Certificate of Residence (COR)
A COR is a letter certifying that you are a tax resident in Singapore for the purpose of claiming benefits under the Avoidance of Double Tax Agreements (DTAs).
* [India](https://media.megaport.com/docs/pdf/finance/CoR/cor-singapore-india-2026.pdf)
* [Indonesia](https://media.megaport.com/docs/pdf/finance/CoR/cor-singapore-indonesia-2026.pdf)
* [Indonesian DGT](https://media.megaport.com/docs/pdf/finance/CoR/cor-singapore-2026.pdf)
* [Sri Lanka](https://media.megaport.com/docs/pdf/finance/CoR/cor-singapore-sri-lanka-2026.pdf)
# Assigning a Finance User Role
Source: https://docs.megaport.com/finance/finance-user
This help topic describes how to create a finance user role.
You can provide Portal access to those who make financial decisions for the registered company by creating specific user roles: *Finance* or *Financial Contact*. These roles determine the user's permissions to manage the account.
Only Company Admins can create or edit user roles.
A *Finance* user can:
* Place and approve orders
* View and delete services
* Create, view, and modify service keys
* View financial data
* Make payments
* Create, edit, and delete credit card records
The *Financial Contact* role is similar to a *Finance* role, but does not have permissions to place or approve orders, delete services, or administer service keys.
A *Financial Contact* user can:
* View and design services
* View the Megaport Marketplace profile
* View financial data
* Make payments
* Create, edit, and delete credit card records
**To create a financial user role**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Manage Users.
The Manage Users page appears. On this page, you can view existing users, add a new user, edit existing user permissions and contact information, and reset Multi-Factor Authentication per user.
3. Click **New User** to create a new Finance user role.
4. Provide the following information:
* **Contact details** -- The first name, last name, email address, and phone number of the financial contact.
* **Role** -- The financial role for the new user. Permissions vary by role.
5. Click **Save**.
For more information about user roles and permissions, see [Managing User Roles](/portal-admin/user-management/roles).
# Understanding Your Megaport Invoice
Source: https://docs.megaport.com/finance/invoices
This help topic describes the details in your Megaport invoice.
Megaport invoices for services every month. The invoice contains a summary of the services you ordered, general information about the invoice, the amount due, how to make a payment, and how to contact Megaport. These invoices are sent monthly to the Billing Contact email address registered in your account.
For more information about viewing current and previous invoices, see [Downloading Invoices](/finance/download-invoice).
Invoices for services in the Brazil and India billing markets are not available in the Portal. Megaport Accounts Receivable sends invoices to the registered billing contact email address for services in the Brazil billing market. For services in India, invoices are sent by our invoicing agent. Contact [Megaport Accounts Receivable](mailto:ar.global@megaport.com) with any questions.
## Invoice details
Megaport provides invoices in PDF and CSV file formats. The invoice includes billing activity details for that month. Here is a sample invoice in PDF format:
Your invoice header includes these terms:
* **Invoice Number** -- The number assigned to your invoice.
* **Invoice Date** -- The date the invoice was created.
* **Payment Terms** -- The number of days that credit is allowed from the invoice date, as agreed between Megaport and your company. For more information about Port terms and pricing, see [Port Pricing & Contract Terms](/finance/port-pricing).
* **Due Date** -- The date when full payment is due for the invoice.
* **Purchase Order** -- The purchase order you specified when you created the Megaport service. For the PO number to appear on the invoice, you must specify it in the **Edit Market** tab before the end of the billing period. For more information about how to update your Invoice Purchase Order Number, see [Updating Your Billing Information](/finance/payment-info).
* **Total** -- Total including all taxes and surcharges.
The body of the invoice includes these terms:
* **Description** -- The unique ID and name assigned to the service by Megaport and the service type. The Service ID is a unique 8-character alphanumeric reference associated with each service. For example, `hd72g38f`. The ID also appears next to the service name on the Services page.
* **Date** -- The time period associated with the billed services.
* **Your Reference** -- The Service Level Reference number. This is a unique identifying number for your Megaport service that is used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. The Service Level Reference number appears for each service under the Product section of the invoice.\
This number appears in the invoice only if you specified it when you ordered the service. For example, when ordering a VXC, you can specify this number as part of the connection details in the **Service Level Reference** field. For more information, see [Creating a Private VXC](/connections/private-vxc).
* **Amount** -- The sum of the billed service amount for time period within the date range.
You can view upcoming estimated bills for a specific service on the Billing page in the Portal. For more information, see [VXC and IX Billing](/finance/billing-details).
Every month, invoices are sent to the Billing Contact email address you provided in the Megaport Portal in the Billing Markets > Edit Market tab. Invoices are usually sent on the first business day of the month. Statements can be downloaded from the Megaport Portal. For more information, see [Downloading Invoices](/finance/download-invoice).
Megaport's auto-pay system processes payments on the 20th of each month for all invoices listed on your account statement. If you have any questions relating to Megaport's auto-pay system, contact Megaport Accounts Receivable.
Ensure that you keep the Billing Contact email address current so you receive invoices and other communication in a timely manner.
## Taxes - domestic customers
Taxes are broken down by region, depending on where you ordered the Megaport service and the location of your registered business address.
Here is an example of the tax breakdown on a USA invoice where a USA-based customer ordered services in several states:
The Federal Universal Service Fund (FUSF) rate in the USA is [established by the Federal Communications Commission (FCC)](https://www.fcc.gov/general/contribution-factor-quarterly-filings-universal-service-fund-usf-management-support) and is updated on a quarterly basis. State sales tax rates in the US can also change occasionally, however less frequently than the FUSF.
The Carrier Cost Recovery is a surcharge to recover Property Tax and Franchise taxes that the company incurs.
If you qualify for any tax exemptions on any of your Megaport services, contact [Megaport Accounts Receivable](mailto:ar.global@megaport.com?) for instructions on how to upload your supporting documentation to our Exemption Certificate Management System.
In European countries, the standard Value-Added Tax (VAT) is generally applied on services to domestic customers. Here is a sample VAT breakdown for a UK domestic customer:
In the rest of the world, a local tax is applied for domestic customers. In this example, an Australian invoice includes a standard Goods and Services Tax (GST):
## Taxes - non-domestic customers
In Europe, services for non-domestic customers within the European Union (EU) can be 0% rated for VAT purposes when the customer provides a valid EU VAT registration number. In this situation, the customer must account for VAT on a reverse charge basis.
*Export customers* are generally defined as those located outside the country from which Megaport provides and bills services. In the case of an EU billing entity, they are also located outside the EU. In all cases, an export customer does not have a permanent establishment for tax purposes or tax registration in the country of billing.
Export invoices are generally not subject to tax, such as VAT (Europe) or GST (AU, NZ, SGP).
Megaport Japan customers should note that the criteria for export transactions are more technical in Japan and depend on the nature of the services rather than where the customer is based.
## Questions?
For billing or invoice questions, contact Megaport Accounts Receivable.
# IP Address Billing
Source: https://docs.megaport.com/finance/ip-address-billing
This help topic describes IP Address block billing details.
Megaport charges a recurring monthly flat fee based on the subnet size of the IP Address block. Some IPv6 block sizes are available at no monthly charge and are labeled **Free** when you order.
Billing starts as soon as the block is in live status. Each month, you are billed a flat fee for the block. IP Address is charged on a postpaid basis. For example, if you place your order on January 15, your first invoice will be issued on February 1, and the charge will cover the period from January 15 to January 31.
For more information, see [IP Address Pricing and Contract Terms](/finance/ip-address-pricing).
## Cancellation
Canceling an IP Address block on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees](/finance/etf-management).
## Helpful references
* [Billing Overview](/finance/overview)
* [Enabling Billing Markets](/finance/enabling-market)
* [IP Address Pricing and Contract Terms](/finance/ip-address-pricing)
* [MCR Billing](/finance/mcr-billing)
* [MVE Billing](/finance/mve-billing)
* [NAT Gateway Billing](/finance/nat-gateway-billing)
* [Port Billing](/finance/port-billing)
* [VXC, Megaport Internet, and IX Billing](/finance/billing-details)
# IP Address Pricing and Contract Terms
Source: https://docs.megaport.com/finance/ip-address-pricing
This help topic describes IP Address block pricing and contract term details.
When you order an IP Address block, the Megaport Portal displays the monthly cost (before tax) based on the subnet size and metro you select, before you confirm the order.
## Contract terms
IP Address blocks are ordered on a fixed 12-month minimum contract term. Unlike other Megaport services, there is no pay-as-you-go (No Minimum Term) option. You cannot change the metro, IP version, or subnet size after ordering.
By default, the block automatically renews for another 12-month term when the contract ends. You can turn off automatic renewal during ordering, or at any time afterward from the **Billing** tab, so the block moves to month-to-month billing instead of renewing.
If you select a 12-month term when ordering a new IP Address block, you cannot later renew it for a longer term, such as 24 or 36 months.
For more information, see [Creating an IP Address Block](/ip-address/creating-ip-address).
## How does billing work?
Megaport charges a recurring monthly flat fee based on the subnet size of the IP Address block. Some IPv6 block sizes have no monthly charge and are labeled **Free** when you order. You cannot change the metro, IP version, or subnet size of an existing block. To use a different configuration, you must order a new block. For more information about available sizes, see [IP Address block sizes](/ip-address#ip-address-block-sizes).
## Cancellation
Canceling an IP Address block on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. You can waive the ETF yourself by ordering an eligible replacement service. For more information, see [Managing Early Termination Fees](/finance/etf-management).
## Helpful references
* [Billing Overview](/finance/overview)
* [Creating an IP Address Block](/ip-address/creating-ip-address)
* [IP Address Billing](/finance/ip-address-billing)
* [IP Address block sizes](/ip-address#ip-address-block-sizes)
* [IP Address Overview](/ip-address)
* [Linking and Unlinking Megaport Internet Connections](/ip-address/linking-vxc)
* [Managing Early Termination Fees](/finance/etf-management)
* [Terminating an IP Address Block](/ip-address/terminating-ip-address)
# IX Pricing and Contract Terms
Source: https://docs.megaport.com/finance/ix-pricing
This help topic describes IX pricing structure and contract term details.
The key factors that determine IX pricing are the distance between your Port and the IX location, the rate limit that you configure, and the term that you choose.
## Pricing structure
IX pricing is based on distance:
* **Local IX** -- An IX connection within the same metro area as your Port incurs no additional charge for the connection itself. You only pay for the Port.
* **Remote IX** -- An IX connection in a different metro area than your Port incurs charges at VXC rates. These rates are calculated based on the distance between locations, rate limit, and the term of the IX connection.\
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing).
## Contract terms
When you create an IX, the Megaport Portal displays the monthly cost before tax on a Summary page before you confirm the order. The price is determined by the distance between your Port and the IX location, the rate limit that you configure, and the term that you choose. Local IXs remain at \$0 and are eligible for term commitments.
When you deploy an IX, cost accrual begins immediately. In the Megaport Portal, you can make the following changes to pay-as-you-go or long-term contracts:
### New IXs
Select No Minimum Term to pay-as-you-go, or select a 12, 24, 36, 48, or 60-month term, billed monthly. The default term is 12 months. If you don’t renew the contract at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.\
For more information, see [Joining an IX](/ix/joining-an-ix).
Longer contract terms have these benefits:
* Fixed base rate cost
* Discounts based on the term duration. Longer terms result in a lower monthly rate.
* Reduced peering costs
You can change the rate limit while the IX is on a term. The IX rate limit can be increased or decreased, provided it is not reduced below the original committed term speed. For more information, see [Changing the Speed of a Termed IX](/ix/ix-termed-rate-change).
### Existing IXs
In the Megaport Portal, you can make the following changes to a month-to-month or long-term contract:
* Add a 12, 24, 36, 48, or 60-month term to a month-to-month IX on No Minimum Term.
* Extend a term on an existing contracted IX.
* Increase or decrease the rate limit.
* Renew a term in the last month of a contracted IX, before the term expires.
After making a term change, the Portal begins a new term on the next billing date.
* **Existing IXs on a minimum term** -- You can renew a 12, 24, 36, 48, or 60-month term, or extend to a longer term. You can extend a minimum term at any time.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information about changing a term, see [Joining an IX](/ix/joining-an-ix).
* **Existing IXs on No Minimum Term** -- You can add a 12, 24, 36, 48, or 60-month term to an IX on No Minimum Term.
* **Expired IX terms** -- Renew a term contract after it has expired. After an IX term expires, the monthly rate reverts to the standard rates.
- Not all contract terms can be changed in the Portal. If an option is not available, it will be grayed out. Contact your Megaport Account Manager for more information.
- To provide adequate time for you to extend or renew the IX, Megaport will notify you via email one month ahead of term expiration.
### Changing a contract term
Use these instructions to help you change your contract term.
To change the IX speed, you can increase or decrease the rate limit during a term without needing to re-term. For more information, see [Changing the Speed of a Termed IX](/ix/ix-termed-rate-change).
**To change a contract term**
1. In the Megaport Portal, go to the **Services** page and locate the IX you want to change.
2. Click the IX Details icon.
3. Review the contract term details for the IX.\
The **Contract Terms** field shows the current term details for the IX.
4. Click **Change Contract Term** and select the new term for the IX.
* **Choose IX Contract Term** -- Select 12, 24, 36, 48, or 60 months. IXs that are under a contract term or on No Minimum Term start their new contract term immediately.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
When you re-term an IX, you can optionally increase the rate limit.
5. Select the **I agree to the terms and conditions** check box to indicate you have read and agreed to the Global Services Agreement.
6. Click **Start New Contract Term**.\
Alternatively, click **Cancel** to maintain the current term conditions for the IX.\
IXs on No Minimum Term will continue to be billed on a pay-as-you-go basis.\
If a termed IX expires, it will roll over to No Minimum Term. The term discount will no longer be applied and the rate limit will be editable.
The Portal accepts the new term at the current standard rate and will apply any applicable term discounts at the new term start date. The new Term details are shown on the IX Connection Configuration page.
For more information, see [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
### Changing the speed of a termed IX
You can increase and decrease the speed of a termed IX. For more information, see [Changing the Speed of a Termed IX](/ix/ix-termed-rate-change).
## Pricing estimates
You can obtain a remote IX price estimate as follows:
* [Megaport Quoting Tool](https://pricing.megaport.com/) -- Quickly create a quote to estimate the cost of deploying IXs, before ordering the services. Entering details into the Quoting Tool helps you plan the overall cost of Megaport services. This provides a clear idea of the design, services needed, and cost breakdown for planning.\
For more information, see [Quoting Service Cost](/finance/creating-estimates).
* Megaport Portal -- Test different IX configurations in the staging environment without any obligation. Create an IX to see how remote IXs are priced. Create an IX to get an immediate estimate in your currency before you deploy.
By default, partner-managed accounts do not display pricing details. Discuss pricing directly with your partner.
## Cancellation
You can cancel an IX at any time. Canceling an IX on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. For more information, see [Terminating an IX](/ix/terminating-an-ix).
## Helpful references
* [Billing Overview](/finance/overview)
* [Changing the Speed of a Termed IX](/ix/ix-termed-rate-change)
* [Joining an IX](/ix/joining-an-ix)
* [Managing Minimum Term Renewal](/portal-admin/auto-renew)
* [MCR Pricing and Contract Terms](/finance/mcr-pricing)
* [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing)
* [MVE Pricing and Contract Terms](/finance/mve-pricing)
* [Port Pricing and Contract Terms](/finance/port-pricing)
* [Quoting Service Cost](/finance/creating-estimates)
* [Terminating an IX](/ix/terminating-an-ix)
* [VXC, Megaport Internet, and IX Billing](/finance/billing-details)
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# MCR Billing
Source: https://docs.megaport.com/finance/mcr-billing
This help topic describes Megaport Cloud Router (MCR) billing details.
Megaport charges a recurring monthly flat fee based on the MCR provisioned services consumed hourly in the course of the previous month.
The billing starts as soon as the MCR is in live status. Each month, you are billed a flat fee for each MCR.
MCR is charged on a postpaid basis. For example, if you place your order on January 15, your first invoice will be issued on February 1, and the charge will cover the period from January 15 to January 31.
If any contract term changes occurred within the month, billing will reflect a sum of the charges. Megaport incorporates a cap of 28 days per month to calculate the percentage allocation of the rate charged.
For more information, see [MCR Pricing and Contract Terms](/finance/mcr-pricing).
## Cancellation
You can cancel an MCR at any time. Canceling an MCR on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. For more information, see [Terminating an MCR](/mcr/terminating-mcr/).
## Helpful references
* [Billing Overview](/finance/overview)
* [Enabling Billing Markets](/finance/enabling-market)
* [MVE Billing](/finance/mve-billing)
* [NAT Gateway Billing](/finance/nat-gateway-billing)
* [Port Billing](/finance/port-billing)
* [VXC, Megaport Internet, and IX Billing ](/finance/billing-details)
# MCR Pricing and Contract Terms
Source: https://docs.megaport.com/finance/mcr-pricing
This help topic describes Megaport Cloud Router (MCR) pricing and contract term details.
When you create a Megaport Cloud Router (MCR), the Megaport Portal displays the monthly cost (before tax) in the order summary, which updates as you make selections. The price is determined by the MCR location and the MCR rate limit.
When you deploy an MCR, cost accrual begins immediately. In the Megaport Portal, you can make the following changes to pay-as-you-go or long-term contracts that are on standard pricing:
* **New MCR** -- In the **Contract Term** field, select No Minimum Term to pay-as-you-go, or select a 12, 24, 36, 48, or 60-month minimum term, billed monthly. The default term is 12 months. The term starts when you place the order. For more information about creating an MCR, see [Creating an MCR](/mcr/creating-mcr).
Longer contract terms have these benefits:
* Fixed monthly cost.
* Discounts based on the term duration. For example, a 24-month term has a 5% discount and a 36-month term has a 10% discount.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Existing MCR on a minimum term** -- Renew a 12, 24, 36, 48, or 60-month minimum term, extend to a longer term, or shorten the term. You can extend a minimum term at any time; however, you can only shorten it during the last calendar month of the term.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information about changing a term, see [Changing a contract term](#changing).
* **Existing contract term** -- Upgrade a contract term at any time.
* **Expired MCR term** -- Renew a term contract after it has expired.
To provide adequate time to extend or renew the MCR contract, Megaport will notify you via email 1 month ahead of the term expiration and 1 week before a price change.
## Changing a contract term
In the Portal, you can make the following changes:
* Add a term to an MCR.
* Extend the term on an existing MCR contract.
* Renew a term in the final 30 days of an MCR contract, before the term expires.
After changing an existing term, the new term begins immediately.
Not all contract terms can be changed in the Portal (the option will be grayed out). Contact your Megaport Account Manager for more information.
**To add, extend, or renew a contract term**
1. In the Megaport Portal, go to the **Services** page and locate the MCR you want to change.
2. Click the MCR Details icon.
3. Review the contract term details for this MCR.\
The End Date and Term length are shown.
4. Click **Change Contract Term** and select the new term for the MCR.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
MCRs that are under a contract term or on pay-as-you-go billing start their new contract term immediately.
5. Select the **I agree to the terms and conditions** check box to indicate you have read and agreed to the Global Services Agreement.
6. Click **Start New Contract Term**.\
Click **Cancel** to maintain the MCR's current term conditions. If an MCR on a contract term expires, it rolls over to pay-as-you-go billing (at standard pricing, without term discounts).
The Portal accepts the new term at the current standard rate and applies any applicable term discounts at the new term start date. The new term and end date appear on the MCR Details page.
For more information, see [MCR Billing](/finance/mcr-billing).
## MCR pricing
Megaport charges a recurring monthly flat fee based on the MCR provisioned services consumed hourly in the course of the previous month.
The MCR service is priced by speed, and the speed is fixed for the life of the service. When you order an MCR, you select a speed from one of these bandwidth tiers:
* 1 Gbps
* 2.5 Gbps
* 5 Gbps
* 10 Gbps
* 25 Gbps
* 50 Gbps
* 100 Gbps
After you select an MCR speed, you cannot change it in the future.
For more information, see [MCR Billing](/finance/mcr-billing).
## Cancellation
You can cancel an MCR at any time. Canceling an MCR on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. For more information, see [Terminating an MCR](/mcr/terminating-mcr/).
## Helpful references
* [Billing Overview](/finance/overview)
* [IX Pricing and Contract Terms](/finance/ix-pricing)
* [Managing Minimum Term Renewal](/portal-admin/auto-renew)
* [MCR Billing](/finance/mcr-billing)
* [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing)
* [MVE Pricing and Contract Terms](/finance/mve-pricing)
* [Port Pricing and Contract Terms](/finance/port-pricing)
* [Quoting Service Cost](/finance/creating-estimates)
* [Terminating an MCR](/mcr/terminating-mcr)
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Megaport Internet Pricing and Contract Terms
Source: https://docs.megaport.com/finance/megaport-internet-pricing
This help topic describes the Megaport Internet pricing structure.
The key factors that determine Megaport Internet pricing are the term for the connection, the rate limit that you configure, and the market in which the connection exists.
For more information about Megaport Internet, see [Megaport Internet Overview](/megaport-internet).
## Contract terms
When you create a Megaport Internet connection, the Megaport Portal displays the monthly cost before tax on a Summary page before you confirm the order. The price is determined by the market, the rate limit that you configure, and the term that you choose.
When you deploy a Megaport Internet connection, cost accrual begins immediately. In the Megaport Portal, you can make the following changes to pay-as-you-go or long-term contracts that are on standard pricing:
### New Megaport Internet connections
Select No Minimum Term to pay-as-you-go, or select a 12, 24, 36, 48, or 60-month term, billed monthly. The default term is 12 months. If you don’t renew the contract at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.\
For more information, see [Megaport Internet Overview](/megaport-internet).
Longer contract terms have these benefits:
* Fixed base rate cost
* Discounts based on the term duration. Longer terms result in a lower monthly rate.
Rate limit changes are not allowed while the connection is on a term.
### Existing Megaport Internet connections
In the Megaport Portal, you can make the following changes to a month-to-month or long-term contract:
* Add a 12, 24, 36, 48, or 60-month term to a month-to-month Megaport Internet connection on No Minimum Term.
* Extend a term on an existing contracted Megaport Internet connection.
* Renew a term in the last month of a contracted Megaport Internet connection, before the term expires.
After making a term change, the Portal begins a new term on the next billing date.
* **Existing Megaport Internet connections on a minimum term** -- You can renew a 12, 24, 36, 48, or 60-month term, or extend to a longer term. You can extend a minimum term at any time.
If you prefer not to renew, no action is required. At the end of the term, the contract will automatically roll over to pay-as-you-go billing at the current rack rate (standard pricing, without term discounts). For more information about changing a term, see [Changing a contract term](#changing).
* **Existing month-to-month Megaport Internet connection** -- Upgrade a connection on No Minimum Term to a 12, 24, 36, 48, or 60-month contract term at any time.
* **Expired Megaport Internet connection terms** -- Renew a term contract after it has expired. After a Megaport Internet connection term expires, the monthly rate reverts to the standard rates.
- Not all contract terms can be changed in the Portal. If an option is not available, it will be grayed out. Contact your Megaport Account Manager for more information.
- To provide adequate time to extend or renew the Megaport Internet connection, Megaport will notify you via email two months and one month ahead of term expiration.
### Changing a contract term
Use these instructions to help you change your contract term.
**To change a contract term**
1. In the Megaport Portal, go to the **Services** page, and locate the Megaport Internet connection you want to change.
2. Click the VXC Details icon.
3. Review the contract term details for the Megaport Internet connection.\
The **Contract Terms** field shows the current term details.
4. Click **Change Contract Term** and select the new term for the Megaport Internet connection.
Select 12 Months, 24 Months, 36, 48, or 60 Months. Megaport Internet connections that are under a contract term or on No Minimum Term start their new contract term immediately.
When you re-term a Megaport Internet connection, you can optionally increase the rate limit.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
5. Read the Important Information and see the Global Services Agreement if necessary. Select I agree to the terms and conditions.
6. Click **Start New Contract Term**.\
Alternatively, click **Cancel** to maintain the current term conditions for the Megaport Internet connection. Connections on No Minimum Term will continue to be billed on a pay-as-you-go basis.\
If a termed Megaport Internet connection expires, it will roll over to No Minimum Term. The term discount will no longer be applied and the rate limit will be editable.
The Portal accepts the new term at the current standard rate and will apply any applicable term discounts at the new term start date. The new Term details are shown on the Megaport Internet Connection Configuration page.
For more information, see [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
## Pricing estimates
You can obtain a Megaport Internet connection price estimate as follows:
* [Megaport Quoting Tool](https://pricing.megaport.com/) -- Quickly create a quote to estimate the cost of deploying Megaport Internet connections, before ordering the services. Entering details into the Quoting Tool helps you plan the overall cost of Megaport services. This provides a clear idea of the design, services needed, and cost breakdown for planning. For more information, see [Quoting Service Cost](/finance/creating-estimates).
Megaport Internet is not available for all services in all countries. For the latest on Megaport Internet availability, see [Megaport Internet Overview](/megaport-internet).
* Megaport Portal -- Test different Megaport Internet configurations in the staging environment without any obligation. Create a Megaport Internet to see how metros, zones, and data centers are priced. Create a Megaport Internet connection to get an immediate estimate in your currency before you deploy.
By default, partner-managed accounts do not display pricing details. Discuss pricing directly with your partner.
## How does billing work?
Metro Megaport Internet connections are billed a recurring monthly flat fee based on these bandwidth tiers:
* 1 Mbps to 1 Gbps
* 1001 Mbps to 10 Gbps
* 10001 Mbps to 50 Gbps
* 50001 Mbps to 100 Gbps
Zone Megaport Internet connections are priced using two components:
1. A recurring fixed fee.
2. Bandwidth-based rate (priced per Mbps per month).\
This rate is based on the time a Megaport Internet connection is active at a defined speed and rate limit.
For more information, see [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
## Cancellation
You can cancel a Megaport Internet connection at any time. Canceling a Megaport Internet connection on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. For more information, see [Terminating a Megaport Internet Connection](/megaport-internet/terminating-connection).
## Helpful references
* [Billing Overview](/finance/overview)
* [IX Pricing and Contract Terms](/finance/ix-pricing)
* [Managing Minimum Term Renewal](/portal-admin/auto-renew)
* [MCR Pricing and Contract Terms](/finance/mcr-pricing)
* [MVE Pricing and Contract Terms](/finance/mve-pricing)
* [Port Pricing and Contract Terms](/finance/port-pricing)
* [Quoting Service Cost](/finance/creating-estimates)
* [Terminating a Megaport Internet Connection](/megaport-internet/terminating-connection)
* [VXC, Megaport Internet, and IX Billing](/finance/billing-details)
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# MVE Billing
Source: https://docs.megaport.com/finance/mve-billing
This help topic describes Megaport Virtual Edge (MVE) billing details.
For MVE, the billing starts as soon as the MVE is in live status. Each month, you are billed a flat fee for each MVE. MVE is charged on a postpaid basis, so if you order the MVE 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.
You can view MVE invoices in the Megaport Portal, even if your MVE was created in the Cisco SD-WAN vManage console. For more information, see [Downloading an Invoice](/finance/download-invoice).
For more information, see [MVE Pricing and Contract Terms](/finance/mve-pricing).
## Cancellation
You can cancel an MVE at any time. Canceling an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.\
For more information, see the relevant topic for your provider:
* [6WIND](/mve/6wind/terminating-mve/)
* [Anapaya](/mve/anapaya/terminating-mve/)
* [Aruba](/mve/aruba/terminating-mve/)
* [Aviatrix](/mve/aviatrix/terminating-mve/)
* [Check Point](/mve/checkpoint/terminating-mve/)
* [Cisco](/mve/cisco/terminating-mve/)
* [Deciso OPNsense](/mve/deciso/terminating-mve/)
* [F5](/mve/f5/terminating-mve/)
* [Fortinet](/mve/fortinet/terminating-mve/)
* [Juniper](/mve/juniper/terminating-mve/)
* [Netskope One SD-WAN](/mve/netskope/terminating-mve/)
* [Palo Alto Networks (VM-Series)](/mve/palo-alto/terminating-mve/)
* [Palo Alto Networks (Prisma SD-WAN)](/mve/palo-alto/terminating-mve-prisma/)
* [Peplink](/mve/peplink/terminating-mve/)
* [Versa](/mve/versa/terminating-mve/)
* [VMware](/mve/vmware/terminating-mve/)
## Helpful references
* [Billing Overview](/finance/overview)
* [Enabling Billing Markets](/finance/enabling-market)
* [MCR Billing](/finance/mcr-billing)
* [NAT Gateway Billing](/finance/nat-gateway-billing)
* [Port Billing](/finance/port-billing)
* [VXC, Megaport Internet, and IX Billing ](/finance/billing-details)
# MVE Pricing and Contract Terms
Source: https://docs.megaport.com/finance/mve-pricing
This help topic describes Megaport Virtual Edge (MVE) billing details.
Megaport charges a recurring monthly flat fee based on the MVE provisioned services consumed hourly in the course of the previous month.
The MVE service is priced by the instance size you select when ordering an MVE. These fixed monthly prices include the MVE, public IP address, and Megaport Internet connectivity. Megaport Internet costs might differ by market. VXCs between MVEs or other resources are billed separately. For more information, see the *Planning Your Deployment* topic for your provider:
* [6WIND](/mve/6wind/plan-deployment)
* [Anapaya](/mve/anapaya/plan-deployment)
* [Aruba](/mve/aruba/plan-deployment)
* [Aviatrix](/mve/aviatrix/plan-deployment)
* [Check Point CloudGuard](/mve/checkpoint/plan-deployment)
* [Cisco](/mve/cisco/plan-deployment)
* [Deciso OPNsense](/mve/deciso/plan-deployment)
* [F5](/mve/f5/plan-deployment)
* [Fortinet](/mve/fortinet/plan-deployment)
* [Juniper](/mve/juniper/plan-deployment)
* [Netskope One SD-WAN](/mve/netskope/plan-deployment)
* [Palo Alto (VM-Series)](/mve/palo-alto/plan-deployment)
* [Palo Alto (Prisma SD-WAN)](/mve/palo-alto/plan-deployment-prisma)
* [Peplink](/mve/peplink/plan-deployment)
* [Versa](/mve/versa/plan-deployment)
* [VMware](/mve/vmware/plan-deployment)
When you deploy an MVE, cost accrual begins immediately. In the Megaport Portal, you can make the following changes to pay-as-you-go or long-term contracts that are on standard pricing:
* **New MVE** -- Select No Minimum Term to pay-as-you-go, or select a 12, 24, 36, 48, or 60-month minimum term, billed monthly. The default term is 12 months. The term starts when you place the order. Longer contract terms have these benefits:
* Fixed monthly cost.
* Discounts based on the term duration. For example, a 24-month term has a 5% discount and a 36-month term has a 10% discount.
See the [MVE Overview](/mve) for SD-WAN vendor-specific details on creating an MVE.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Existing MVE on a minimum term** -- Renew a 12, 24, 36, 48, or 60-month minimum term, extend to a longer term, or shorten the term. You can extend a minimum term at any time; however, you can only shorten it during the last calendar month of the term.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information about changing a term, see [Changing a contract term](#changing).
* **Existing contract term** -- Upgrade a contract term at any time.
* **Expired MVE term** -- Renew a term contract after it has expired.
To provide adequate time to extend or renew the MVE contract, Megaport will notify you via email 1 month ahead of the term expiration and 1 week before a price change.
## Changing a contract term
In the Portal, you can make the following changes:
* Add a term to an MVE.
* Extend the term on an existing MVE contract.
* Renew a term in the final 30 days of an MVE contract, before the term expires.
After changing an existing term, the new term begins immediately.
Not all contract terms can be changed in the Portal (the option will be grayed out). Contact your Megaport Account Manager for more information.
**To add, extend, or renew a contract term**
1. In the Megaport Portal, go to the **Services** page and locate the MVE you want to change.
2. Click the MVE Details icon.
3. Review the contract term details for this MVE.
The End Date and Term length are shown.
4. Click **Change Contract Term** and select the new term for the MVE.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
MVEs that are under a contract term or on pay-as-you-go billing start their new contract term immediately.
5. Select the **I agree to the terms and conditions** check box to indicate you have read and agreed to the Global Services Agreement.
6. Click **Start New Contract Term**.\
Click **Cancel** to maintain the MVE's current term conditions. If an MVE on a contract term expires, it rolls over to pay-as-you-go billing (at standard pricing, without term discounts).
The Portal accepts the new term at the current standard rate and applies any applicable term discounts at the new term start date. The new term and end date appear on the MVE Details page.
For more information, see [MVE Billing](/finance/mve-billing).
## Cancellation
You can cancel an MVE at any time. Canceling an MVE on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.\
For more information, see the relevant topic for your provider:
* [6WIND](/mve/6wind/terminating-mve/)
* [Anapaya](/mve/anapaya/terminating-mve/)
* [Aruba](/mve/aruba/terminating-mve/)
* [Aviatrix](/mve/aviatrix/terminating-mve/)
* [Check Point](/mve/checkpoint/terminating-mve/)
* [Cisco](/mve/cisco/terminating-mve/)
* [Deciso OPNsense](/mve/deciso/terminating-mve/)
* [F5](/mve/f5/terminating-mve/)
* [Fortinet](/mve/fortinet/terminating-mve/)
* [Juniper](/mve/juniper/terminating-mve/)
* [Netskope One SD-WAN](/mve/netskope/terminating-mve/)
* [Palo Alto Networks (VM-Series)](/mve/palo-alto/terminating-mve/)
* [Palo Alto Networks (Prisma SD-WAN)](/mve/palo-alto/terminating-mve-prisma/)
* [Peplink](/mve/peplink/terminating-mve/)
* [Versa](/mve/versa/terminating-mve/)
* [VMware](/mve/vmware/terminating-mve/)
## Helpful references
* [Billing Overview](/finance/overview)
* [IX Pricing and Contract Terms](/finance/ix-pricing)
* [Managing Minimum Term Renewal](/portal-admin/auto-renew)
* [MCR Pricing and Contract Terms](/finance/mcr-pricing)
* [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing)
* [MVE Billing](/finance/mve-billing)
* [Quoting Service Cost](/finance/creating-estimates)
* [Port Pricing and Contract Terms](/finance/port-pricing)
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# NAT Gateway Billing
Source: https://docs.megaport.com/finance/nat-gateway-billing
This help topic describes Megaport NAT Gateway (NAT) billing details.
Megaport charges a recurring monthly flat fee based on provisioned Megaport NAT Gateway (NAT Gateway) services consumed during the previous month.
The billing starts as soon as the NAT Gateway is in live status. Each month, you are billed a flat fee for each NAT Gateway.
The NAT Gateway is charged on a postpaid basis. For example, if you place your order on January 15, your first invoice will be issued on February 1, and the charge will cover the period from January 15 to January 31.
If any contract term changes occurred within the month, billing will reflect a sum of the charges. Megaport incorporates a cap of 28 days per month to calculate the percentage allocation of the rate charged.
For more information, see [NAT Gateway Pricing and Contract Terms](/finance/nat-gateway-pricing).
## Cancellation
You can cancel a NAT Gateway at any time. Canceling a NAT Gateway on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. For more information, see [Terminating a NAT Gateway](/nat/terminating-nat-gateway/).
## Helpful references
* [Billing Overview](/finance/overview)
* [Enabling Billing Markets](/finance/enabling-market)
* [MCR Billing](/finance/mcr-billing)
* [MVE Billing](/finance/mve-billing)
* [Port Billing](/finance/port-billing)
* [VXC, Megaport Internet, and IX Billing](/finance/billing-details)
# NAT Gateway Pricing and Contract Terms
Source: https://docs.megaport.com/finance/nat-gateway-pricing
This help topic describes Megaport NAT Gateway (NAT Gateway) pricing and contract term details.
When you create a Megaport NAT Gateway (NAT Gateway), the Megaport Portal displays the monthly cost (before tax) on a Summary page before you confirm the order. The price is based on the selected maximum concurrent sessions and the rate limit.
When you deploy a NAT Gateway, cost accrual begins immediately. In the Megaport Portal, you can make the following changes to pay-as-you-go or long-term contracts that are on standard pricing:
* **New NAT Gateway** -- Select No Minimum Term to pay-as-you-go, or select a 12, 24, 36, 48, or 60-month minimum term, billed monthly. The default term is 12 months. The term starts when you place the order. For more information about creating a NAT Gateway, see [Creating a NAT Gateway](/nat/creating-nat-gateway).
Longer contract terms have these benefits:
* Fixed monthly cost.
* Discounts based on the term duration. For example, a 24-month term has a 5% discount and a 36-month term has a 10% discount.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Existing NAT Gateway on a minimum term** -- Renew a 12, 24, 36, 48, or 60-month minimum term, extend to a longer term, or shorten the term. You can extend a minimum term at any time; however, you can only shorten it during the last calendar month of the term.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information about changing a term, see [Changing a contract term](#changing).
* **Existing contract term** -- Upgrade a contract term at any time.
* **Expired NAT Gateway term** -- Renew a term contract after it has expired.
To provide adequate time to extend or renew the NAT Gateway contract, Megaport will notify you via email 1 month ahead of the term expiration and 1 week before a price change.
## Changing a contract term
In the Portal, you can make the following changes:
* Add a term to a NAT Gateway.
* Extend the term on an existing NAT Gateway contract.
* Renew a term in the final 30 days of a NAT Gateway contract, before the term expires.
After changing an existing term, the new term begins immediately.
Not all contract terms can be changed in the Portal (the option will be grayed out). Contact your Megaport Account Manager for more information.
**To add, extend, or renew a contract term**
1. In the Megaport Portal, go to the **Services** page and locate the NAT Gateway you want to change.
2. Click the NAT Gateway Details icon.
3. Review the contract term details for this NAT Gateway.\
The End Date and Term length are shown.
4. Click **Change Contract Term** and select the new term for the NAT Gateway.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
NAT Gateways that are under a contract term or on pay-as-you-go billing start their new contract term immediately.
5. Select the **I agree to the terms and conditions** check box to indicate you have read and agreed to the Global Services Agreement.
6. Click **Start New Contract Term**.\
Click **Cancel** to maintain the NAT Gateway's current term conditions. If a NAT Gateway on a contract term expires, it rolls over to pay-as-you-go billing (at standard pricing, without term discounts).
The Portal accepts the new term at the current standard rate and applies any applicable term discounts at the new term start date. The new term and end date appear on the NAT Gateway Details page.
For more information, see [NAT Gateway Billing](/finance/nat-gateway-billing).
## NAT Gateway pricing
Megaport charges a recurring monthly flat fee based on the NAT Gateway provisioned services consumed hourly in the course of the previous month.
The NAT Gateway service is priced by the rate limit and the maximum concurrent sessions, and both limits are fixed for the life of the service. When you order a NAT Gateway, you select the maximum concurrent sessions, then the rate limit:
| Session Count | Rate Limits in Gbps |
| :-: | :-: |
| 250,000 | 1, 2.5, 5, and 10 |
| 500,000 | 10 and 25 |
| 1,000,000 | 10, 25, and 50 |
| 2,500,000 | 10, 25, 50, and 100 |
| 5,000,000 | 10, 25, 50, and 100 |
| 10,000,000 | 10, 25, 50, and 100 |
After you select the NAT Gateway maximum concurrent sessions and rate limit, you cannot change it.
For more information, see [NAT Gateway Billing](/finance/nat-gateway-billing).
## Cancellation
You can cancel a NAT Gateway at any time. Canceling a NAT Gateway on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. For more information, see [Terminating a NAT Gateway](/nat/terminating-nat-gateway/).
## Helpful references
* [IX Pricing and Contract Terms](/finance/ix-pricing)
* [Managing Minimum Term Renewal](/portal-admin/auto-renew)
* [MCR Pricing and Contract Terms](/finance/mcr-pricing)
* [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing)
* [Megaport NAT Gateway Overview](/nat)
* [MVE Pricing and Contract Terms](/finance/mve-pricing)
* [Port Pricing and Contract Terms](/finance/port-pricing)
* [Quoting Service Cost](/finance/creating-estimates)
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Billing Overview
Source: https://docs.megaport.com/finance/overview
This help topic describes how to work with Megaport accounts receivable and billing.
This section outlines essential information to assist with the billing and Accounts Receivable process. Here are some essentials:
* **Global Service Agreement** -- See the [Megaport Global Services Agreement](https://www.megaport.com/legal/global-services-agreement/) for the official description of terms and conditions.
* **Your billing contact** -- Invoices, statements, and other communications from Accounts Receivable is sent to the Billing Contact email address registered in your account. Ensure that this contact is current. See [Updating Your Billing Information](/finance/payment-info) for instructions on how to update your billing contact.
* **Payments** -- Payments must be received on or before the invoice due date using one of the electronic payment methods outlined on your invoice.
Payments can be processed electronically either to the bank account listed on your invoice or by credit card in the Portal. For credit card payment details, see [Credit Card Payments](/finance/credit-card-payments).
* **Contact Megaport** -- Send remittance and account queries to [Megaport Accounts Receivable](mailto:ar.global@megaport.com).
Click a link in the side navigation to explore more billing topics.
## Helpful references
* [Enabling Billing Markets](/finance/enabling-market)
* [IP Address Billing](/finance/ip-address-billing)
* [Managing Contract Terms in Bulk](/finance/term-management)
* [Managing Early Termination Fees](/finance/etf-management)
* [MCR Billing](/finance/mcr-billing)
* [MVE Billing](/finance/mve-billing)
* [NAT Gateway Billing](/finance/nat-gateway-billing)
* [Port Billing](/finance/port-billing)
* [VXC, Megaport Internet, and IX Billing ](/finance/billing-details)
# Updating Your Billing Information
Source: https://docs.megaport.com/finance/payment-info
This help topic describes how to update your billing details in the Megaport Portal.
You can update billing information, such as the Billing Contact email address or Purchase Order (PO) number.
1. Visit the Megaport Portal and log in.
2. Choose Billing > Billing Markets.
3. Locate the market to update and click **Edit Market**.
Alternatively, for quick updates, you can edit the Billing Contact, Billing Email, or PO number directly from the **Billing Markets** page using the edit (pencil) icon.
4. Update any of the billing information for the selected market.
* For the Purchase Order Number to appear on an invoice, you must update it before the end of the billing period.
* To change your billing market **Company Legal Name** and **Company Registration No** details, contact your Account Manager or Customer Success Manager.
5. Click **Save**.
# Port Billing
Source: https://docs.megaport.com/finance/port-billing
This help topic describes Megaport Port billing details.
When a new Port is created on a contract term, charges are applied on a *postpaid* basis from the day the Port goes *Live*, or 14 days after the order date, whichever comes first, until the end of that calendar month. From the 1st day of the following calendar month, charges change to a *prepaid* basis.
For example, if a Port is ordered on March 15 and goes *Live* on March 26, the first invoice (issued April 1) will cover two periods:
* March 26–31: Prorated *postpaid* charge for the remainder of the month that the Port went *Live*.
* April 1–30: Full month *prepaid* charge for the following calendar month.
The second invoice (issued May 1) will cover May 1–31 as a full month *prepaid* charge.
Any changes to an existing term will apply from the start of the next billing month.
In the Portal, if you have chosen a billing currency other than the home currency for a market (such as USD in Australian market), the price will be recalculated based on the current exchange rates in the Portal.
For more information, see [Port Pricing & Contract Terms](/finance/port-pricing).
## Cancellation
You can cancel a Port at any time. Canceling a Port on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. For more information, see [Terminating a Port](/connections/terminating-port/).
## Helpful references
* [Billing Overview](/finance/overview)
* [Enabling Billing Markets](/finance/enabling-market)
* [MCR Billing](/finance/mcr-billing)
* [MVE Billing](/finance/mve-billing)
* [NAT Gateway Billing](/finance/nat-gateway-billing)
* [VXC, Megaport Internet, and IX Billing ](/finance/billing-details)
# Port Pricing and Contract Terms
Source: https://docs.megaport.com/finance/port-pricing
This help topic describes Port contract term details.
When you create a Port, the Megaport Portal displays the monthly cost (before tax) on a Summary page before you confirm the order. The price is determined by the Port location, the Port speed, the term, and whether a Cross Connect is included.
## Changing a contract term
The Port billing also begins on the same date the Port goes *Live*, or 14 days after the order date, whichever comes first.
In the Megaport Portal, you can make the following changes to month-to-month or long-term contracts that are on standard pricing:
* **New Ports** -- Choose a 1, 12, 24, 36, 48, or 60-month minimum term, billed monthly. The default term is 12 months. If you don't add a 12, 24, 36, 48, or 60-month term when creating a new Port, you will be billed with the month-to-month rate. For more information, see [Creating a Port](/connections/creating-port).
Longer contract terms offer lower monthly costs and discounts based on the term duration.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Existing Ports on a minimum term** -- Renew a 12, 24, 36, 48, or 60-month term, extend to a longer term, or shorten the term. You can extend a minimum term at any time; however, you can only shorten it during the last calendar month of the term.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
* **Existing month-to-month Ports** -- Upgrade a Port from month-to-month to a 12, 24, 36, 48, or 60-month contract term, at any time.
* **Expired Port terms** -- Renew a term contract after it has expired. From the first day of the next calendar month, it will be charged at the term discount.
You might not be able to change the terms for some of the services. If the option is grayed out, contact your Megaport Account Manager for more information.
After making a term change, the Portal begins a new term on the next billing date.
To provide adequate time for you to extend or renew the Port, Megaport will notify you via email one month and one week before the expiration of the term. For LAGs, each Port in the LAG is treated individually. Megaport will send a separate renewal email for each Port.
**Contract terms for Link Aggregation Groups (LAGs)**
When ordering a Port in a LAG, secondary Ports are initially set to match the primary Port's contract term. After ordering, contract terms for the primary and secondary Ports can be extended independently.
This can result in mismatched terms, for example, one primary Port might be on a 12-month term, while one secondary Port might be on a 24-month term and another secondary Port on a 36-month term.
Additional Ports can be added to a LAG with any contract term, including month-to-month.
To ensure accurate billing and term management, confirm the new term information in the Portal. For more information about LAGs, see [Creating a Link Aggregation Group](/connections/lag).
**To change a contract term**
1. In the Megaport Portal, go to the **Services** page, and locate the Port you want to change.
2. Click the Port Details icon.
3. Review the contract term details for this Port.
The End Date and Term length are shown. Optionally, click **Download LOA** to view the Port details.
4. Click **Change Contract Term** and select the new term for the Port.
* **Choose Port Contract Term** -- Select 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
5. Select the **I agree to the terms and conditions** check box to indicate you have read and agreed to the Global Services Agreement.
6. Click **Start New Contract Term**.\
Click **Cancel** to maintain the Port's current term conditions. The Port will remain as a month-to-month Port. If a termed Port expires, it will roll over to month-to-month and the discount will no longer be applied.
The Portal accepts the new term at the current standard rate and will apply any applicable term discounts at the new term start date. The new term and end date are shown on the Port Details page.
For more information, see [Port Billing](/finance/port-billing).
## Cancellation
You can cancel a Port at any time. Canceling a Port on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. For more information, see [Terminating a Port](/connections/terminating-port/).
## Helpful references
* [Billing Overview](/finance/overview)
* [IX Pricing and Contract Terms](/finance/ix-pricing)
* [Managing Minimum Term Renewal](/portal-admin/auto-renew)
* [MCR Pricing and Contract Terms](/finance/mcr-pricing)
* [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing)
* [MVE Pricing and Contract Terms](/finance/mve-pricing)
* [Port Billing](/finance/port-billing)
* [Quoting Service Cost](/finance/creating-estimates)
* [Terminating a Port](/connections/terminating-port)
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Megaport Object Storage Billing
Source: https://docs.megaport.com/finance/storage-billing
This help topic describes Megaport Object Storage billing details.
Megaport Object Storage billing has two components:
* The **Megaport Object Storage VXC** (the network connection to the storage) is billed by Megaport and appears on your **Megaport invoice**.
* **Storage consumption** (the amount of storage you use each month) is billed by Latitude.sh and appears on your **Latitude.sh invoice**.
For more information about contract terms and pricing, see [Megaport Object Storage Pricing and Contract Terms](/finance/storage-pricing).
## Megaport Object Storage VXC billing
VXC billing starts as soon as the Megaport Object Storage connection is live. Megaport bills the VXC monthly on a postpaid basis.
You can view Megaport invoices in the Megaport Portal. For more information, see [Downloading an Invoice](/finance/download-invoice).
## Storage consumption billing
Latitude.sh bills you for your storage consumption. For more information, see Latitude.sh Billing and Latitude.sh Invoices.
## Viewing Megaport Object Storage connection billing details
The Billing page shows billing details for the selected connection. You can view upcoming estimated bills and any changes in the configured speed over a given month for a .
If your account is managed through a Megaport partner, the partner manages the billing. Contact your partner for your billing details.
**To view billing details for a **
1. Log in to the Megaport Portal and choose **Services**.
2. Click the gear icon next to the connection.
3. On the Connection Details page, click **Billing**.
The Billing graph shows the configured speed over the current billing month and the Estimated Next Bill. The Estimated Next Bill for the current month is updated with each change to the service.
The shaded area of the graph shows the configured speeds for the portion of the month that has already passed. The dotted line shows the expected speed for the rest of the billing month, assuming that no changes are made.
To view details for a previous month, click the Billing Month and select a month.
## Billing Details table
The Billing Details table shows the configured speed for the connection, as well as any changes made to the speed during the selected month. Each speed change creates a new entry in the table.
Each entry includes these billing details:
* **Speed (Mbps)** -- The configured speed for the connection.
* **Start/End** -- The date range that the connection was configured at this speed. Time is displayed as UTC+10 (Brisbane time).
* **Duration** -- The length of time that the connection is expected to be configured at the current speed. When viewing the current month, the duration for the last configured speed is extended to the end of the 28-day billing cycle, and the price is calculated based on that duration.
* **Price** -- The cost of the connection in the market-enabled currency. The price is based on the amount of time that the connection was configured at that speed.
Optionally, click **Download CSV** to download the billing data shown in the comma-separated values (CSV) format. You can use the CSV file to import the data into spreadsheets and databases. You can open the CSV file in any text editor.
## Cancellation
Terminating the Megaport Object Storage connection in the Megaport Portal only stops Megaport Object Storage VXC billing.\
For more information, see [Terminating a Megaport Object Storage Connection](/storage/object/terminating-connection).
Terminating a Megaport Object Storage connection on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information about Megaport Object Storage contract terms, see [Megaport Object Storage Pricing and Contract Terms](/finance/storage-pricing).
To stop storage consumption billing, delete your storage allocation in the Latitude.sh Portal.\
For more information about Latitude.sh billing, see Latitude.sh Billing.
## Helpful references
* [Billing Overview](/finance/overview)
* [Downloading an Invoice](/finance/download-invoice)
* Latitude.sh Invoices
* [MCR Billing](/finance/mcr-billing)
* [Megaport Object Storage Pricing and Contract Terms](/finance/storage-pricing)
* [MVE Billing](/finance/mve-billing)
* [NAT Gateway Billing](/finance/nat-gateway-billing)
* [Port Billing](/finance/port-billing)
* [VXC, Megaport Internet, and IX Billing](/finance/billing-details)
# Megaport Object Storage Pricing and Contract Terms
Source: https://docs.megaport.com/finance/storage-pricing
This help topic describes Megaport Object Storage pricing and contract terms.
Megaport Object Storage pricing has two components billed separately:
* **Megaport Object Storage VXC** -- The Megaport network connection from your service to the storage endpoint, billed by Megaport.
* **Storage consumption** -- The amount of storage you use, billed by Latitude.sh.
For more information about how billing works for each component, see [Megaport Object Storage Billing](/finance/storage-billing).
For more information about Megaport Object Storage, see [Megaport Object Storage Overview](/storage/object).
## Contract terms
When you create a Megaport Object Storage connection, the Megaport Portal displays the monthly cost before tax on a Summary page before you confirm the order. The price is determined by the market, the rate limit, and the term you select.
When you deploy a Megaport Object Storage connection, cost accrual begins immediately.
### New Megaport Object Storage connections
Select No Minimum Term to pay-as-you-go, or select a 12, 24, 36, 48, or 60-month term, billed monthly. The default term is 12 months. If you don't renew the contract at the end of the term, the contract automatically rolls over to a month-to-month contract for the following billing period at the same price, without term discounts.
Longer contract terms have these benefits:
* Fixed base rate cost.
* Discounts based on the term duration. Longer terms result in a lower monthly rate.
Rate limit changes are not allowed while the connection is on a term.
### Existing Megaport Object Storage connections
In the Megaport Portal, you can make the following changes to a month-to-month or long-term contract:
* Add a 12, 24, 36, 48, or 60-month term to a connection on No Minimum Term.
* Extend a term on an existing contracted connection.
* Renew a term in the last month of a contracted connection, before the term expires.
After making a term change, the Portal begins a new term on the next billing date.
* **Connections on a minimum term** -- You can renew or extend to a longer term at any time. If you prefer not to renew, no action is required. At the end of the term, the contract automatically rolls over to pay-as-you-go billing at standard rates.
* **Month-to-month connections** -- Upgrade to a 12, 24, 36, 48, or 60-month contract at any time.
* **Expired terms** -- Renew a term after it has expired. After a term expires, the monthly rate reverts to standard rates.
- Not all contract term changes are available in the Portal. If an option is grayed out, contact your Megaport Account Manager.
- To provide adequate time to extend or renew the connection, Megaport will notify you by email two months and one month ahead of term expiration.
### Changing a contract term
Use these instructions to help you change your contract term.
To change the VXC speed, you can increase or decrease the rate limit during a term without needing to re-term. For more information, see [Changing the Speed of a Termed VXC](/connections/vxc-termed-rate-change/).
**To change a contract term**
1. In the Megaport Portal, go to the **Services** page and locate the VXC you want to change.
2. Click the VXC Details icon.
3. Review the contract term details for the VXC.\
The **Contract Terms** field shows the current term details for the VXC.
4. Click **Change Contract Term** and select the new term for the VXC.
* **Choose VXC Contract Term** -- Select 12, 24, 36, 48, or 60 months. VXCs that are under a contract term or on No Minimum Term start their new contract term immediately.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
When you re-term a VXC, you can optionally increase the rate limit.
5. Select the **I agree to the terms and conditions** check box to indicate you have read and agreed to the Global Services Agreement.
6. Click **Start New Contract Term**.\
Alternatively, click **Cancel** to maintain the current term conditions for the VXC.\
VXCs on No Minimum Term will continue to be billed on a pay-as-you-go basis.\
If a termed VXC expires, it will roll over to No Minimum Term. The term discount will no longer be applied and the rate limit will be editable.
The Portal accepts the new term at the current standard rate and will apply any applicable term discounts at the new term start date. The new Term details are shown on the VXC Connection Configuration page.
## Pricing estimates
You can obtain a Megaport Object Storage connection price estimate as follows:
* Megaport Quoting Tool -- Quickly create a quote to estimate the cost of deploying Megaport Object Storage connections, before ordering the services. Entering details into the Quoting Tool helps you plan the overall cost of Megaport services. This provides a clear idea of the design, services needed, and cost breakdown for planning. For more information, see [Quoting Service Cost](/finance/creating-estimates).
* Megaport Portal -- Test different configurations in the [staging environment](/troubleshooting/staging) without any obligation. Create a Megaport Object Storage connection to see how metros, zones, and data centers are priced. Create a Megaport Object Storage connection to get an immediate estimate in your currency before you deploy.
Storage consumption is not included in Megaport price estimates. For information about storage consumption pricing, see [Latitude.sh Storage & Data Pricing](https://www.latitude.sh/pricing/storage/).
## Cancellation
Terminating a Megaport Object Storage connection on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term.
For more information, see [Terminating a Megaport Object Storage Connection](/storage/object/terminating-connection).
Terminating the Megaport Object Storage connection does not delete your storage allocation or data. To cancel storage consumption billing, delete your storage allocation in the Latitude.sh Portal.
## Helpful references
* [Billing Overview](/finance/overview)
* [Managing Minimum Term Renewal](/portal-admin/auto-renew)
* [Megaport Object Storage Billing](/finance/storage-billing)
* [Quoting Service Cost](/finance/creating-estimates)
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Managing Contract Terms in Bulk
Source: https://docs.megaport.com/finance/term-management
This help topic describes how to update contract terms for one or more services in the Megaport Portal.
This topic describes how to manage the contract terms for multiple services in bulk.
You can re-term multiple services approaching term expiry or lock in longer-term discounts across a group of services.
## Eligible services
You can re-term any service or connection type except the following:
* **Locked services** -- Services that have been locked by you or a Company Admin.
* **Admin-locked services** -- Services locked by Megaport support.
* **Non-live services** -- Services that are not yet fully provisioned.
These services appear grayed out in the Term Management list and cannot be selected.
## Filtering the services list
You can filter the list of services on the Term Management page using these filters:
* **Filter services** -- Filter by service name.
* **Service Type** -- Filter by Megaport products, such as VXCs and MCRs.
* **Auto-Renew** -- Filter by automatic term renewal status (on or off).
* **Contract Term** -- Filter by the current contract term length of services: month-to-month, 12, 24, 36, 48, or 60 months.
* **Expiring in** -- Filter for services with terms expiring within 30, 60, or 90 days.
## Updating contract terms
You can update the contract terms of one or more services.
The Portal offers only the contract terms that are available for every selected service. You can apply a term equal to or longer than a service's current term, but you cannot shorten it. If a selected service already has a longer term, the Portal grays out any shorter terms for the whole selection.
**To update contract terms for multiple services**
1. In the Megaport Portal, go to Billing > Term Management.
2. (Optional) Use the filters to narrow the list of services.
3. Select the check box next to each service you want to re-term.
Ineligible services appear in the list but their check boxes are grayed out. Mouse over a grayed-out check box to see why the service cannot be re-termed.
4. Click **Next**.
5. Select the new contract term.
The Portal offers only the contract terms available for every selected service. You can apply a term equal to or longer than a service's current term, but you cannot shorten it. If a selected service already has a longer term, the Portal grays out any shorter terms for the whole selection. Mouse over a grayed-out term to see why. Review each service's new monthly rate.
To remove a service from the list, click the **Trash** icon at the end of the row.
6. (Optional) To automatically renew all selected services at the same discounted price and term length at the end of the contract term, enable the automatic renewal option. This overrides the current [Minimum Term Renewal](/portal-admin/auto-renew) setting on each selected service. If you don't enable this option, services continue on a month-to-month basis at the end of the term.
7. Click **Next**.
8. Review the pricing summary for each service.
9. Review the terms and conditions, then select the **I agree to the terms and conditions** check box.
10. Click **Start New Contract Term**.
The Portal processes each service independently. The results page shows the outcome for each service:
* **Updated** -- The term change was applied.
* **Failed** -- The term change was not applied. A reason is shown next to the service name.
* **Pending Approval** -- (Managed accounts only) The request is waiting for your partner to approve it. The new term takes effect after the partner approves.
11. Click **Done** to return to the Services page.
## Auto-renewing services
When re-terming multiple services on the Term Management page, the Automatic Renewal option is applied to all selected services. If enabled, each service automatically renews for the same term at the end of the new contract term.
You can change the automatic renewal setting for individual services at any time on the configuration page for the service. For more information, see [Managing Minimum Term Renewal](/portal-admin/auto-renew).
## Helpful references
* [Billing Overview](/finance/overview)
* [IX Pricing and Contract Terms](/finance/ix-pricing)
* [Locking Megaport Services](/portal-admin/locking)
* [Managing Early Termination Fees](/finance/etf-management)
* [Managing Minimum Term Renewal](/portal-admin/auto-renew)
* [MCR Pricing and Contract Terms](/finance/mcr-pricing)
* [MVE Pricing and Contract Terms](/finance/mve-pricing)
* [NAT Gateway Pricing and Contract Terms](/finance/nat-gateway-pricing)
* [Port Pricing and Contract Terms](/finance/port-pricing)
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# VXC Pricing and Contract Terms
Source: https://docs.megaport.com/finance/vxc-pricing
This help topic describes the Megaport Virtual Cross Connect (VXC) pricing structure.
The key factors that determine VXC pricing are the distance between the locations (the A-End and B-End), the rate limit that you configure, and the term that you choose.
There are three rate types based on distance:
* **Metro** -- A defined metropolitan area, usually a city or group of cities. A VXC connects two locations within the same city, such as:
* Two Ports located in San Francisco
* A Port and a Cloud Service Provider (CSP), both located in London
* **Zone** -- A group of metro areas, typically multiple states or provinces. A VXC connects any two metros within the same zone, such as:
* Seattle and San Francisco (in the US West zone)
* **Interzone** -- Different cities in different zones. For example, an interzone VXC connects:
* A Port in US West and a Port in US East
* A Port in NE Asia and a CSP in AU North
## Pricing zones and metros
| **Pricing Zone** | **Indicative Metro** |
| - | - |
| US West | Seattle, Reno, Los Angeles, Portland, Las Vegas, Phoenix, San Diego, Sacramento, Salt Lake City, Bay Area |
| US East | Ashburn, New York, Atlanta, Norwalk, Culpeper, Stamford, Miami, Boston, Philadelphia, Wise, Tampa, Pittsburgh, Orlando, Charlotte, Raleigh |
| US Central | Memphis, Grand Rapids, Detroit, Chicago, Dallas, Houston, Cincinnati, Austin, San Antonio, Denver, Kansas City, Columbus, St. Louis, Minneapolis, Nashville, Omaha |
| CA East | Toronto, Montreal, Quebec City, Ottawa |
| CA West | Calgary, Vancouver |
| Mexico | Mexico City, Querétaro |
| Brazil | São Paulo |
| EU North | Brussels, Copenhagen, Rogaland, Luxembourg, Marseille, Amsterdam, Stockholm, Frankfurt, Berlin, Munich, Hamburg, Dusseldorf, Nuremberg, Helsinki, Oslo, Vienna, Geneva, Zurich, Warsaw, Paris, Madrid, Milan |
| EU West | Manchester, Edinburgh, London, Dublin, Birmingham |
| EU East | Sofia |
| Dubai | Dubai |
| AU Central | Adelaide |
| AU East | Wollongong, Sydney, Canberra |
| AU North | Brisbane |
| AU South | Melbourne |
| AU West | Perth |
| NZ | Auckland, Wellington, Hamilton |
| SE Asia | Singapore |
| East Asia | Hong Kong |
| NE Asia | Tokyo, Osaka |
This image shows the available zones in Megaport's global network:
For the most current location information, see the [Megaport Locations page](https://www.megaport.com/megaport-enabled-locations/).
## Contract terms
When you create a VXC, the Portal displays the monthly cost before tax on a Summary page before you confirm the order. The price is determined by the distance between the A-End and B-End locations, the rate limit that you configure, and the term that you choose.
When you deploy a VXC, cost accrual begins immediately. In the Megaport Portal, you can make the following changes to pay-as-you-go or long-term contracts that are on standard pricing:
### New VXCs
Select No Minimum Term to pay-as-you-go, or select a 12, 24, 36, 48, or 60-month term, billed monthly. The default term is 12 months. If you don’t renew the contract at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.\
For more information, see [Creating a VXC](/connections/overview#create_vxc).
Longer contract terms have these benefits:
* Fixed base rate cost
* Discounts based on the term duration. Longer terms result in a lower monthly rate.
You can change the rate limit while the VXC is on a term. For more information, see [Changing the Speed of a Termed VXC](/connections/vxc-termed-rate-change).
### Existing VXCs
In the Megaport Portal, you can make the following changes to a month-to-month or long-term contract:
* Add a 12, 24, 36, 48, or 60-month term to a month-to-month VXC on No Minimum Term.
* Extend a term on an existing contracted VXC.
* Increase or decrease the rate limit.
* Renew a term in the last month of a contracted VXC, before the term expires.
After making a term change, the Portal begins a new term on the next billing date.
* **Existing VXCs on a minimum term** -- You can renew a 12, 24, 36, 48, or 60-month term, or extend to a longer term. You can extend a minimum term at any time.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [Changing a contract term](#changing).
* **Existing month-to-month VXC** -- Upgrade a VXC on No Minimum Term to a 12, 24, 36, 48, or 60-month contract term, at any time.
* **Expired VXC terms** -- Renew a term contract after it has expired. After a VXC term expires, the monthly rate reverts to the standard rates.
- Not all contract terms can be changed in the Portal. If an option is not available, it will be grayed out. Contact your Megaport Account Manager for more information.
- To provide adequate time for you to extend or renew the VXC, Megaport will notify you via email one month ahead of term expiration. For Link Aggregation Groups (LAGs), each VXC in the LAG is treated individually. Megaport will send a separate renewal email for each Port.
- Each VXC in a Link Aggregation Group (LAG) is treated individually and is subject to the same contract term and billing agreements as an individual Port. For more information about LAGs, see [Creating a Link Aggregation Group](/connections/lag).
### Changing a contract term
Use these instructions to help you change your contract term.
To change the VXC speed, you can increase or decrease the rate limit during a term without needing to re-term. For more information, see [Changing the Speed of a Termed VXC](/connections/vxc-termed-rate-change/).
**To change a contract term**
1. In the Megaport Portal, go to the **Services** page and locate the VXC you want to change.
2. Click the VXC Details icon.
3. Review the contract term details for the VXC.\
The **Contract Terms** field shows the current term details for the VXC.
4. Click **Change Contract Term** and select the new term for the VXC.
* **Choose VXC Contract Term** -- Select 12, 24, 36, 48, or 60 months. VXCs that are under a contract term or on No Minimum Term start their new contract term immediately.
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
When you re-term a VXC, you can optionally increase the rate limit.
5. Select the **I agree to the terms and conditions** check box to indicate you have read and agreed to the Global Services Agreement.
6. Click **Start New Contract Term**.\
Alternatively, click **Cancel** to maintain the current term conditions for the VXC.\
VXCs on No Minimum Term will continue to be billed on a pay-as-you-go basis.\
If a termed VXC expires, it will roll over to No Minimum Term. The term discount will no longer be applied and the rate limit will be editable.
The Portal accepts the new term at the current standard rate and will apply any applicable term discounts at the new term start date. The new Term details are shown on the VXC Connection Configuration page.
For more information, see [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
### Changing the speed of a termed VXC
You can increase and decrease the speed of a termed VXC. For more information, see [Changing the Speed of a Termed VXC](/connections/vxc-termed-rate-change).
## Pricing estimates
You can obtain a VXC price estimate as follows:
* [Megaport Quoting Tool](https://pricing.megaport.com/) -- Quickly create a quote to estimate the cost of deploying VXCs, before ordering the services. Entering details into the Quoting Tool helps you plan the overall cost of Megaport services. This provides a clear idea of the design, services needed, and cost breakdown for planning.\
For more information, see [Quoting Service Cost](/finance/creating-estimates).
* Megaport Portal -- Test different VXC configurations in the staging environment without any obligation. Create a VXC to see how metros, zones, interzones, and data centers are priced. Create a VXC to get an immediate estimate in your currency before you deploy.
By default, partner-managed accounts do not display pricing details. Discuss pricing directly with your partner.
## How does billing work?
Metro VXCs are billed a recurring monthly flat fee based on these bandwidth tiers:
* 1 Mbps to 1 Gbps
* 1001 Mbps to 10 Gbps
* 10001 Mbps to 50 Gbps
* 50001 Mbps to 100 Gbps
Zone and interzone VXCs are priced using two components:
1. A recurring fixed fee.
2. Bandwidth-based rate (priced per Mbps per month).\
This rate is based on the time a VXC is active at a defined speed and rate limit.
Megaport applies surcharges to cloud on-ramp VXCs with a B-End connecting to Alibaba, Amazon Web Services (AWS), AWS Hosted Connections (AWSHC), Azure, Google, Oracle, SFDC, Outscale, IBM, and GCI for these VXC types:
* VXCs connecting two ends within the same metro area
* VXCs connecting two ends in different metro areas
Megaport applies a surcharge based on the selected rate limit for any VXCs with a B-End connecting to France-IX.
For more information, see [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
## Cancellation
You can cancel a VXC at any time. Canceling a VXC on a contract term will result in an early termination fee (ETF) equivalent to 100% of the remainder of the term. For more information, see [Terminating a VXC](/connections/terminating-vxc).
## Helpful references
* [Billing Overview](/finance/overview)
* [Changing the Speed of a Termed VXC](/connections/vxc-termed-rate-change)
* [IX Pricing and Contract Terms](/finance/ix-pricing)
* [Managing Minimum Term Renewal](/portal-admin/auto-renew)
* [MCR Pricing and Contract Terms](/finance/mcr-pricing)
* [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing)
* [MVE Pricing and Contract Terms](/finance/mve-pricing)
* [Port Pricing and Contract Terms](/finance/port-pricing)
* [Quoting Service Cost](/finance/creating-estimates)
* [Terminating a VXC](/connections/terminating-vxc)
* [VXC, Megaport Internet, and IX Billing](/finance/billing-details)
# Getting Started with the Megaport MCP Server
Source: https://docs.megaport.com/mcp-server/getting-started
This help topic describes the prerequisites for using Megaport MCP Server and the process of setting up.
This topic describes the prerequisites and required setup steps to get started using the Megaport MCP Server.
## Prerequisites
This section describes the basic setup steps and provides the necessary links to start using the Megaport MCP Server. Before using the Megaport MCP Server, you need to:
1. **Understand Megaport's services** -- Understand the process of creating services and the features of each service.
* [Port](/connections/creating-port)
* [Virtual Cross Connect (VXC)](/connections/overview)
* [Megaport Cloud Router (MCR)](/mcr)
* [Megaport Virtual Edge (MVE)](/mve)
* [Megaport NAT Gateway (NAT Gateway)](/nat)
* [Megaport Internet](/megaport-internet)
* [Internet Exchange](/ix)
2. **Understand Megaport Portal environments** -- Megaport provides two Portal environments, the production environment and the staging environment. You can test any action in the staging environment. All actions mirror the production system, but services will not be deployed and you will not be billed for any activity. For more information, see [Testing Configurations in the Staging Environment](/troubleshooting/staging).
3. **Create a Megaport account** -- If you have not already created one, see [Creating an Account](/setting-up/registering).
4. **Add and modify users** -- Any user role can access the Megaport MCP Server. For more information, see [Adding and Modifying Users](/portal-admin/user-management).
5. Install your AI command line interface (CLI) tool – such as Claude Code, Codex, Gemini CLI, and so on. For more information, see each AI tool provider’s website.
## Available environments to use the Megaport MCP Server
You can access the Megaport MCP Server at the following URLs.
* **Staging**: [https://mcp-staging.megaport.com/mcp](https://mcp-staging.megaport.com/mcp)
* **Production**: [https://mcp.megaport.com/mcp](https://mcp.megaport.com/mcp)
User authentication is managed via OAuth 2.1, allowing you to log in securely using your Megaport Portal credentials. Most MCP clients handle this authentication flow automatically, ensuring a seamless setup. For more information about OAuth 2.1, see [OAuth 2.1](https://oauth.net/2.1/).
## Setting up the Megaport MCP Server
Configuration and authentication methods for MCP servers vary by AI assistant. The following guides provide step-by-step integration examples for some common platforms.
### Claude Code
1. Run the following command.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
claude mcp add --transport http -s user megaport https://mcp.megaport.com/mcp
```
2. Authenticate your access.
3. Start Claude Code (`claude`).
4. Type `/mcp` to open the MCP server list.
5. Select the **megaport** server.
6. Choose **Authenticate**.\
This opens your browser.
7. Log in with your Megaport Portal credentials.
8. After successfully logging in, return to Claude Code.\
The server should show as connected.
Authentication tokens are cached, so you only need to do this once, or when your token expires.
### Copilot CLI
1. Run the following command.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
copilot mcp add --transport http megaport https://mcp.megaport.com/mcp
```
2. Start Copilot CLI (`copilot`).\
It should automatically open a login authentication browser window.
3. Enter your Megaport Portal credentials in the browser.
4. After successfully logging in, return to Copilot CLI.\
The server should show as connected.
### Codex
1. Run the following command.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
codex mcp add megaport --url https://mcp.megaport.com/mcp
```
2. Run the following command.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
codex mcp login megaport
```
This should automatically open a login authentication browser window.
3. Log in with your Megaport Portal credentials.
4. Enter your Megaport Portal credentials in the browser.
5. After successfully logging in, return to Codex.\
The server should show as connected.
## Helpful references
* [Get Started with Codex](https://chatgpt.com/codex/get-started/)
* [Get Started with Gemini CLI](https://geminicli.com/docs/get-started/)
* [Get Started with GitHub Copilot CLI](https://developer.microsoft.com/blog/get-started-with-github-copilot-cli-a-free-hands-on-course)
* [Quickstart (Claude Code)](https://code.claude.com/docs/en/quickstart)
* [Service Provisioning Methods](/provisioning-methods)
# Megaport MCP Server Overview
Source: https://docs.megaport.com/mcp-server/index
This help topic describes an overview of Megaport, MCP, and the Megaport MCP Server.
This topic provides an introduction to Megaport services, Model Context Protocol (MCP), and the Megaport MCP Server, aimed at users looking to get started using the Megaport MCP Server.
## What is Megaport?
Megaport is a global Network as a Service (NaaS) provider that makes it easy to connect your network to cloud services such as AWS, Microsoft Azure, and Google Cloud without needing complex physical infrastructure.
It uses a software-defined network (SDN) to let you create scalable, secure, and on-demand virtual connections called Virtual Cross Connects (VXCs), between data centers, cloud providers, and enterprise networks. If you are new to Megaport, see [Introducing Megaport](/overview/).
## What is MCP?
Model Context Protocol (MCP) is a universal, open-source standard designed to bridge the gap between AI models and external data or software.
Just as USB-C provides a standardized interface for connecting a wide range of devices, MCP offers a unified way for AI platforms (such as ChatGPT and Claude) to connect with databases, local files, and specialized workflows.
By streamlining these connections, MCP enables AI agents to retrieve live information and execute complex tasks across different systems without the need for custom, fragmented coding.
## How does an MCP Server work?
MCP servers don’t perform any 'thinking' themselves, nor do they contain AI. Instead, they act as a bridge, much like a USB port, that allows Large Language Models (LLMs) to execute API calls to external systems, such as the Megaport API. The server simply fetches the data and returns it in a format the AI can easily interpret.
LLM-based AIs are non-deterministic, meaning you will not receive the same response twice. It is also important to note that outputs vary depending on the provider, such as Claude, Codex, or Gemini, and the specific model version used, such as Claude 3.5 Sonnet, GPT-4o, or Gemini 1.5 Pro.
Due to this nature of LLM-based AIs, when using the Megaport MCP Server for network diagnostics, we recommend that you thoroughly review each response before applying changes to your live services. Test all configurations in the staging environment. For more information about the staging environment, see [Testing Configurations in the Staging Environment](/troubleshooting/staging).
## What is Megaport MCP Server?
Megaport offers a comprehensive suite of public API endpoints designed to automate the provisioning, management, and monitoring of network infrastructure. Customers can leverage these capabilities to order and manage Megaport services through the [Megaport Portal](/portal-admin/services-page), [Terraform](/terraform), and direct [API](/api) integrations.
To streamline the customer experience, Megaport introduces the Megaport MCP Server (currently read-only beta version), a specialized middleware layer that transforms public APIs into a standardized, authenticated, and searchable interface.
By exposing Megaport APIs through the MCP, the server enables AI coding assistants, such as Claude Code, Copilot CLI, Gemini CLI, Codex and others to query and manage Megaport infrastructure directly within the development environment.
## Megaport MCP Server (Open Beta) capabilities
The Megaport MCP Server acts as a standardized middleware that exposes Megaport API functions to any MCP-compatible client. By simplifying the interface between your network and AI-driven tools, you can:
* **Interact via LLMs** -- Use your preferred AI assistant, such as ChatGPT, Claude, or Gemini, to ask about service status in natural language, diagnose latency, or compare utilization. Here are some example questions:
* Show me all ports with utilization > 60%
* Diagnose latency on a specific VXC using Looking Glass.
* Compare last month’s utilization for all MCRs.
* **Autonomous agents** -- You can integrate the Megaport MCP Server with observability tools to automate diagnostics and validate connectivity in real-time.
* **Enhance developer workflows** -- You can connect the Megaport MCP Server directly to Integrated Development Environments (IDEs) such as VS Code and JetBrains, or to Slack bots and browser plugins, to allow engineers to manage bandwidth and check status without leaving their primary workspace.
## Helpful references
* [Introducing Megaport](/overview)
* [Megaport API Overview](/api)
* [Megaport Terraform Provider Overview](/terraform)
* [Service Provisioning Methods](/provisioning-methods)
* [Understanding MCP servers](https://modelcontextprotocol.io/docs/learn/server-concepts#understanding-mcp-servers)
* [What is the Model Context Protocol (MCP)?](https://modelcontextprotocol.io/docs/getting-started/intro)
# Using the Megaport MCP Server
Source: https://docs.megaport.com/mcp-server/using-mcp-server
This help topic describes how to use the Megaport MCP Server.
This topic describes how to interact with the Megaport MCP Server, including practical query examples and their corresponding responses.
## Sample questions and responses
The Megaport MCP Server is currently in read-only beta. You can securely use natural language to query your Megaport services across various categories.
For example:
* Locations
* Information on clouds and partners
* Your service connections
* Your service pricing and billing information
* Service discovery and health status of your services
* Network diagnostics
* Monitoring telemetry and performance
The AI assistant automatically selects the most relevant tools based on the context of your query. Below are several sample questions and responses from the Megaport MCP Server.
❯ `List locations where I can order 100 Gbps ports in Tokyo.`
Sample response:
❯ `List all live NAT Gateways in my Portal.`
Sample response:
❯ `Show me BGP peer status on attached VXCs to the NAT Gateway, Service ID 69c7303e in Ashburn.`
Sample response:
❯ `Show traffic and performance metrics for the MCR service ID 2266520d.`
❯ `Why is the MCR service ID 2266520d traffic idle?`
Sample response:
❯ `Diagnose why this VXC (806d8fbc-5782-4a46-8cbc-01688be998f5) status is
down?`
Sample response:
## Helpful references
* [Megaport API Documentation](https://dev.megaport.com/)
* [Monitoring MCR](/monitoring/mcr-monitoring)
* [Monitoring MVE](/monitoring/mve-monitoring)
* [Monitoring NAT Gateway](/monitoring/nat-gateway-monitoring)
* [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring)
* [Monitoring Services for Status](/monitoring/service-status)
# Monitoring Service Activity in the Megaport Portal
Source: https://docs.megaport.com/monitoring/index
This help topic describes how to view Port, VXC, Megaport Internet, MCR, MVE, and IX service logs and usage reports in the Megaport Portal.
You can view service logs and usage reports for Ports, Virtual Cross Connect (VXCs), Megaport Internet connections, MCRs, MVEs, IXs, and NAT Gateways in the Megaport Portal. These logs and reports help you monitor service health, analyze performance, and troubleshoot issues.
If you want to access monitoring data programmatically, you can use the Megaport API. For more information, see the API documentation at [dev.megaport.com](https://dev.megaport.com), [Monitoring Service Status with the API](/api/monitoring), and [Setting up OpenMetrics for Service Monitoring](/api/monitoring/api-openmetrics).
## Viewing service logs
The Service Logs page displays the activity and status of your Megaport services. For example, you can view the operational status of a Port or determine whether a BGP session is down on an MCR, VXC, or IX connection.
Metrics become available as soon as a service is live in the Megaport Portal. For Ports, the Billing graph begins reporting metrics when the Port goes live or 14 days after it is configured, whichever occurs first. For more information about Port billing and contracts, see [Port Pricing and Contract Terms](/finance/port-pricing).
For service-specific information see:
* [Monitoring Ports, VXCs, Megaport Internet](/monitoring/port-vxc-monitoring#service-logs)
* [Monitoring MCRs](/monitoring/mcr-monitoring#service-logs)
* [Monitoring MVEs](/monitoring/mve-monitoring#service-logs)
* [Monitoring NAT Gateway](/monitoring/nat-gateway-monitoring#service-logs)
## Viewing usage details
The Service Graph displays historical usage for Port, MCR, MVE, VXC, Megaport Internet, and IX connections. You can filter the graphs by date range.
You can access a Service Graph from these locations:
* From the **Services** page, click the gear icon, then select **Telemetry**.\
You will see Service Graphs for the selected service only. For more information, see:
* [Monitoring Port, VXC, Megaport Internet connections](/monitoring/port-vxc-monitoring#usage-details)
* [Monitoring MCRs](/monitoring/mcr-monitoring#usage-details)
* [Monitoring MVEs](/monitoring/mve-monitoring#usage-details)
* [Monitoring NAT Gateway](/monitoring/nat-gateway-monitoring#usage)
* From **Monitoring & Diagnostics** > **Service Telemetry**.\
This page shows usage for multiple services. You can filter the information for a specified date range and select a metric to display. For more information, see [Monitoring Services using the Service Telemetry Page](/monitoring/service-telemetry).
* For IX connections, choose **Tools** > **IX Telemetry**. For more information, see [IX Telemetry](/ix/ix-telemetry).
The Service Graph is updated every 5 minutes.
## Helpful references
* [IX Telemetry](/ix/ix-telemetry)
* [Monitoring Maintenance and Outage Events](/portal-admin/monitoring-events)
* [Monitoring MCRs](/monitoring/mcr-monitoring)
* [Monitoring MVEs](/monitoring/mve-monitoring)
* [Monitoring NAT Gateway](/monitoring/nat-gateway-monitoring)
* [Monitoring Ports, VXCs, Megaport Internet](/monitoring/port-vxc-monitoring)
* [Monitoring Service Status with the API](/api/monitoring)
* [Monitoring Services using the Service Telemetry Page](/monitoring/service-telemetry)
* [Setting up OpenMetrics for Service Monitoring](/api/monitoring/api-openmetrics)
# Monitoring MCR
Source: https://docs.megaport.com/monitoring/mcr-monitoring
This help topic describes how to view MCR service logs and usage reports in the Megaport Portal.
This topic describes how to view service logs and usage reports for a Megaport Cloud Router (MCR) in the Megaport Portal. This information helps you troubleshoot issues and monitor the status, activity, and performance of your MCRs.
For visibility into the traffic routing on an MCR, see [Viewing Traffic Routing through MCR Looking Glass](/mcr/mcr-looking-glass).
Megaport offers a public API that you can use to access the services available through the Looking Glass. For more information, see [Megaport API Overview](/api).
## Viewing service logs
Viewing the service logs is a simple way to monitor the activity and performance of your MCRs. Megaport starts reporting metrics as soon as the MCR is live in the Megaport Portal.
You can also monitor the VXCs and BGP peering on MCR services, such as BGP session down, BGP authentication failure, and so on.
**To view service logs for an MCR**
1. Log in to the Megaport Portal and choose **Services**.
2. Click the gear icon next to the MCR.
3. On the MCR Details page, click **Logs**.\
The 100 most recent events are displayed, including the time zone of the log entries. The standard time zone formatting for MCR log messages is UTC.
4. To view VXC and BGP events, click the gear icon next to the VXC and click **Logs** on the Connection Details page.
A green check mark indicates that the service is running as expected, or shows a non-critical event such as a speed change. A yellow warning icon indicates that there is a potential issue with the service.
Company Admins see an additional **Activity Logs** tab next to Service Logs. The Activity Logs tab displays user activity for the MCR, such as configuration changes and other administrative actions. For more information about activity logs, see [Viewing Activity Logs](/portal-admin/activity-logs).
For more information about investigating MCR issues, see [Troubleshooting MCR When Down or Unavailable](/troubleshooting/mcr/down) and [Troubleshooting MCR When a BGP Session is Down](/troubleshooting/mcr/bgp).
## Viewing usage details
The Service Graph provides helpful information such as inbound/outbound traffic and packet rates. The graph is useful for comparing monthly usage on a MCR. You can export the MCR usage data in comma-separated values (CSV) format for analysis in spreadsheets and databases.
You can access a Service Graph from these locations:
* From the **Services** page, click the gear icon, then select **Telemetry**.\
You will see Service Graphs for the selected service only.
* From **Monitoring & Diagnostics** > **Service Telemetry**.\
This page shows usage for multiple services. You can filter the information for a specified date range and select a metric to display. For more information, see [Monitoring Services using the Service Telemetry Page](/monitoring/service-telemetry).
The Service Graph is updated every 5 minutes.
**To view usage details for an MCR on the Services page**
1. Log in to the Megaport Portal and choose **Services**.
2. Click the gear icon next to the MCR.
3. On the MCR Details page, click **Telemetry**.\
The Service Graph page appears, showing all available metric graphs.
The controls above the graphs apply to all graphs at once. When you change a control, every graph updates together.
4. In the **Date Range** field, enter the range of dates for which to view usage details.\
Select from the following options:
* Last hour
* Last 12 hours
* Last 24 hours
* Last week
* Last month
* Last 3 months
* Last 6 months
* Last 12 months
* Custom - Enter a custom date range using the date picker.
The default time range is the last 24 hours.
5. In the **Resolution** control, select the resolution for the graph data: **5 min**, **Daily**, or **Monthly**.
The available resolutions depend on the selected date range:
* **5 min** is available only for ranges of 3 months or less.
* **Daily** is available for any range.
* **Monthly** is available only for ranges greater than 3 months.
Resolutions that the selected date range does not support are grayed out and unavailable, with a tooltip explaining why.
6. If you selected **Daily** or **Monthly** resolution, select one or more values in the **Aggregate** control to plot on the graph: **Average**, **Peak**, **95th percentile**, or **Minimum**. The **Aggregate** control is not shown for **5 min** resolution.
7. You can customize the graphs by selecting or clearing the **In pps**, **Out pps**, **In Mbps**, **Out Mbps**, and **Configured speed Mbps** check boxes to show or hide data.
Use the mouse to hover over a specific data point to see the values and exact timestamp.
| **Metric** | **Description** |
| - | - |
| Packets | In pps - Incoming packet rate to the MCR, measured in packets per second. Out pps - Outbound packet rate from the MCR, measured in packets per second. |
| Traffic | In Mbps - Number of inbound Megabits per second. Out Mbps - Number of outbound Megabits per second. Configured speed Mbps - Configured speed of the MCR, in Megabits per second. |
8. Click **Export CSV** to download the MCR usage data for all metrics in a single CSV file.\
You can use the CSV file to import the data into spreadsheets and databases. You can open the CSV file in any text editor. The exported data uses the selected resolution.
9. Click **UTC** or your local time zone to change the time zone.
For more information about usage information and service logs, see [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring). For billing information for MCR VXCs, see [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
## Helpful references
* [IX Telemetry](/ix/ix-telemetry)
* [Monitoring MVE](/monitoring/mve-monitoring)
* [Monitoring NAT Gateway](/monitoring/nat-gateway-monitoring)
* [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring)
* [Monitoring Service Activity in the Megaport Portal](/monitoring)
* [Monitoring Services for Status](/monitoring/service-status)
* [Monitoring Services using the Service Telemetry Page](/monitoring/service-telemetry)
* [Setting up MCR BGP notifications](/mcr/configuring-mcr#bgp-notification)
* [Viewing Activity Logs](/portal-admin/activity-logs)
# Monitoring MVE
Source: https://docs.megaport.com/monitoring/mve-monitoring
This help topic describes how to view MVE service logs and usage reports in the Megaport Portal.
This topic describes how to view service logs and usage reports for a Megaport Virtual Edge (MVE) in the Megaport Portal. This information helps you troubleshoot issues and monitor the status, activity, and performance of your MVEs.
Megaport offers a public API that you can use to access the services available available through the service logs and usage reports. For more information, see [Megaport API Overview](/api).
## Viewing service logs
Viewing the service logs is a simple way to monitor the activity and performance of your MVEs. Megaport starts reporting metrics as soon as the MVE is live in the Megaport Portal.
**To view service logs for an MVE**
1. Log in to the Megaport Portal and choose **Services**.
2. Click the gear icon next to the MVE.
3. On the MVE Details page, click **Logs**.\
The 100 most recent events are displayed, including the time zone of the log entries. The standard time zone formatting for MVE log messages is UTC.
A green check mark indicates that the service is running as expected, or shows a non-critical event such as a speed change. A yellow warning icon indicates that there is a potential issue with the service.
Company Admins see an additional **Activity Logs** tab next to Service Logs. The Activity Logs tab displays user activity for the MVE, such as configuration changes and other administrative actions. For more information about activity logs, see [Viewing Activity Logs](/portal-admin/activity-logs).
For more information about investigating MVE issues, see [Troubleshooting MVE When Down or Unavailable](/troubleshooting/mve/down) and [Troubleshooting MVE Connectivity](/troubleshooting/mve/internet).
## Viewing usage details
The Service Graph provides helpful information such as inbound/outbound traffic and packet rates. The graph is useful for comparing monthly usage on a MVE. You can export the MVE usage data in comma-separated values (CSV) format for analysis in spreadsheets and databases.
You can access a Service Graph from these locations:
* From the **Services** page, click the gear icon, then select **Telemetry**.\
You will see Service Graphs for the selected service only.
* From **Monitoring & Diagnostics** > **Service Telemetry**.\
This page shows usage for multiple services. You can filter the information for a specified date range and select a metric to display. For more information, see [Monitoring Services using the Service Telemetry Page](/monitoring/service-telemetry).
The Service Graph is updated every 5 minutes.
**To view usage details for an MVE on the Services page**
1. Log in to the Megaport Portal and choose **Services**.
2. Click the gear icon next to the MVE.
3. On the MVE Details page, click **Telemetry**.\
The Service Graph page appears, showing all available metric graphs.
The controls above the graphs apply to all graphs at once. When you change a control, every graph updates together.
4. In the **Date Range** field, enter the range of dates for which to view usage details.\
Select from the following options:
* Last hour
* Last 12 hours
* Last 24 hours
* Last week
* Last month
* Last 3 months
* Last 6 months
* Last 12 months
* Custom - Enter a custom date range using the date picker.
The default time range is the last 24 hours.
5. In the **Resolution** control, select the resolution for the graph data: **5 min**, **Daily**, or **Monthly**.
The available resolutions depend on the selected date range:
* **5 min** is available only for ranges of 3 months or less.
* **Daily** is available for any range.
* **Monthly** is available only for ranges greater than 3 months.
Resolutions that the selected date range does not support are grayed out and unavailable, with a tooltip explaining why.
6. If you selected **Daily** or **Monthly** resolution, select one or more values in the **Aggregate** control to plot on the graph: **Average**, **Peak**, **95th percentile**, or **Minimum**. The **Aggregate** control is not shown for **5 min** resolution.
7. You can customize the graphs by selecting or clearing the **In pps**, **Out pps**, **In Mbps**, and **Out Mbps** check boxes to show or hide data.
Use the mouse to hover over a specific data point to see the values and exact timestamp.
| **Metric** | **Description** |
| - | - |
| Packets | In pps - Incoming packet rate to the MVE, measured in packets per second. Out pps - Outbound packet rate from the MVE, measured in packets per second. |
| Traffic | In Mbps - Number of inbound Megabits per second. Out Mbps - Number of outbound Megabits per second. |
8. Click **Export CSV** to download the MVE usage data for all metrics in a single CSV file.\
You can use the CSV file to import the data into spreadsheets and databases. You can open the CSV file in any text editor. The exported data uses the selected resolution.
9. Click **UTC** or your local time zone to change the time zone.
For billing information for MVE VXCs, see [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
## Helpful references
* [IX Telemetry](/ix/ix-telemetry)
* [Monitoring MCR](/monitoring/mcr-monitoring)
* [Monitoring NAT Gateway](/monitoring/nat-gateway-monitoring)
* [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring)
* [Monitoring Service Activity in the Megaport Portal](/monitoring)
* [Monitoring Services for Status](/monitoring/service-status)
* [Monitoring Services using the Service Telemetry Page](/monitoring/service-telemetry)
* [Viewing Activity Logs](/portal-admin/activity-logs)
# Monitoring NAT Gateway
Source: https://docs.megaport.com/monitoring/nat-gateway-monitoring
This help topic describes how to view Megaport NAT Gateway service logs and usage reports in the Megaport Portal.
This topic describes how to view service logs and usage reports for a Megaport NAT Gateway (NAT Gateway) in the Megaport Portal. This information helps you troubleshoot issues and monitor the status, activity, and performance of your NAT Gateways.
Megaport offers a public API that you can use to access the services available available through the service logs and usage reports. For more information, see [Megaport API Overview](/api).
## Viewing service logs
Viewing the service logs is a simple way to monitor the activity and performance of your NAT Gateways. Megaport starts reporting metrics as soon as the NAT Gateway is live in the Megaport Portal.
You can also monitor the VXCs and BGP peering on NAT Gateway services, such as BGP session down, BGP authentication failure, and so on.
**To view service logs for a NAT Gateway**
1. Log in to the Megaport Portal and choose **Services**.
2. Click the gear icon next to the NAT Gateway.
3. On the NAT Gateway Details page, click **Logs**.\
The 100 most recent events are displayed, including the time zone of the log entries. The standard time zone formatting for NAT Gateway log messages is UTC.
4. To view VXC and BGP events, click the gear icon next to the VXC and click **Logs** on the Connection Details page.
A green check mark indicates that the service is running as expected, or shows a non-critical event such as a speed change. A yellow warning icon indicates that there is a potential issue with the service.
Company Admins see an additional **Activity Logs** tab next to Service Logs. The Activity Logs tab displays user activity for the NAT Gateway, such as configuration changes and other administrative actions. For more information about activity logs, see [Viewing Activity Logs](/portal-admin/activity-logs).
For more information about investigating NAT Gateway issues, see [Troubleshooting a NAT Gateway Routing Issue](/troubleshooting/nat/routing).
## Viewing usage details
The Service Graph provides helpful information such as inbound/outbound traffic and packet rates. The graph is useful for comparing monthly usage on a NAT Gateway. You can export the NAT Gateway usage data in comma-separated values (CSV) format for analysis in spreadsheets and databases.
You can access a Service Graph from these locations:
* From the **Services** page, click the gear icon, then select **Telemetry**.\
You will see Service Graphs for the selected service only.
* From **Monitoring & Diagnostics** > **Service Telemetry**.\
This page shows usage for multiple services. You can filter the information for a specified date range and select a metric to display. For more information, see [Monitoring Services using the Service Telemetry Page](/monitoring/service-telemetry).
The Service Graph is updated every 5 minutes.
**To view usage details for a NAT Gateway on the Services page**
1. Log in to the Megaport Portal and choose **Services**.
2. Click the gear icon next to the NAT Gateway.
3. On the NAT Gateway Details page, click **Telemetry**.\
The Service Graph page appears, showing all available metric graphs.
The controls above the graphs apply to all graphs at once. When you change a control, every graph updates together.
4. In the **Date Range** field, enter the range of dates for which to view usage details.\
Select from the following options:
* Last hour
* Last 12 hours
* Last 24 hours
* Last week
* Last month
* Last 3 months
* Last 6 months
* Last 12 months
* Custom - Enter a custom date range using the date picker.
The default time range is the last 24 hours.
5. In the **Resolution** control, select the resolution for the graph data: **5 min**, **Daily**, or **Monthly**.
The available resolutions depend on the selected date range:
* **5 min** is available only for ranges of 3 months or less.
* **Daily** is available for any range.
* **Monthly** is available only for ranges greater than 3 months.
Resolutions that the selected date range does not support are grayed out and unavailable, with a tooltip explaining why.
6. If you selected **Daily** or **Monthly** resolution, select one or more values in the **Aggregate** control to plot on the graph: **Average**, **Peak**, **95th percentile**, or **Minimum**. The **Aggregate** control is not shown for **5 min** resolution.
7. You can customize the graphs by selecting or clearing the **In pps**, **Out pps**, **In Mbps**, **Out Mbps**, and **Configured speed Mbps** check boxes to show or hide data.
Use the mouse to hover over a specific data point to see the values and exact timestamp.
| **Metric** | **Description** |
| - | - |
| Packets | In pps - Incoming packet rate to the NAT Gateway, measured in packets per second. Out pps - Outbound packet rate from the NAT Gateway, measured in packets per second. |
| Traffic | In Mbps - Number of inbound Megabits per second. Out Mbps - Number of outbound Megabits per second. Configured speed Mbps - Configured speed of the NAT Gateway, in Megabits per second. |
8. Click **Export CSV** to download the NAT Gateway usage data for all metrics in a single CSV file.\
You can use the CSV file to import the data into spreadsheets and databases. You can open the CSV file in any text editor. The exported data uses the selected resolution.
9. Click **UTC** or your local time zone to change the time zone.
For more information about usage information and service logs, see [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring). For billing information for NAT Gateway VXCs, see [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
## Helpful references
* [IX Telemetry](/ix/ix-telemetry)
* [Monitoring MCR](/monitoring/mcr-monitoring)
* [Monitoring MVE](/monitoring/mve-monitoring)
* [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring)
* [Monitoring Service Activity in the Megaport Portal](/monitoring)
* [Monitoring Services for Status](/monitoring/service-status)
* [Monitoring Services using the Service Telemetry Page](/monitoring/service-telemetry)
* [Viewing Activity Logs](/portal-admin/activity-logs)
# Monitoring Ports, VXCs, Megaport Internet, and IXs
Source: https://docs.megaport.com/monitoring/port-vxc-monitoring
This help topic describes how to view Port, VXC, Megaport Internet, and IX service logs and usage reports in the Megaport Portal.
This topic describes how to view service logs and usage reports for a Port, Virtual Cross Connect (VXC), Megaport Internet connection, and IX in the Megaport Portal. These detailed logs and reports help you monitor connections, evaluate performance, and troubleshoot issues with your Megaport services.
For information about monitoring maintenance and outage events that affect your services, including current, scheduled, and past events, see [Monitoring Maintenance and Outage Events](/portal-admin/monitoring-events).
Megaport offers a public API that you can use to access the services available through the service logs and usage reports. To view the API documentation, see [dev.megaport.com](https://dev.megaport.com). For information about API monitoring, see [Monitoring Service Status with the API](/api/monitoring) and [Setting up OpenMetrics for Service Monitoring](/api/monitoring/api-openmetrics).
## Viewing service logs
Viewing the Service Logs is a simple way to monitor the activity and performance of your Megaport services. For example, you can view the status of a Port or if a BGP session is down on a VXC.
Megaport starts reporting metrics as soon as the service is live in the Megaport Portal. A Port’s Billing graph starts reporting metrics either when it goes live, or 14 days after it is configured. For more information about billing and Port contracts, see [Port Pricing and Contract Terms](/finance/port-pricing).
**To view service logs for a Port**
1. Log in to the Megaport Portal and choose **Services**.
2. Click the gear icon next to the Port.
3. On the Port Details page, click **Logs**.\
The Service Logs page appears.
The 100 most recent events are displayed. A green check mark indicates that the service is running. A yellow warning icon indicates that there is a potential issue with the service.
Company Admins see an additional **Activity Logs** tab next to Service Logs. The Activity Logs tab displays user activity for the Port, such as configuration changes and other administrative actions. For more information about activity logs, see [Viewing Activity Logs](/portal-admin/activity-logs).
For more information about investigating issues, see [Troubleshooting](/troubleshooting/overview).
**To view service logs for a connection**
1. Log in to the Megaport Portal and choose **Services**.
2. Click the gear icon next to the VXC, Megaport Internet connection, or IX.
3. On the Connection Details page, click **Logs**.\
The Service Logs page appears. The most recent log events are listed first.
The 100 most recent events are displayed. A green check mark indicates that the service is running as expected, or shows a non-critical event such as a change in speed. A yellow warning icon indicates that there is an event that requires attention.
Company Admins see an additional **Activity Logs** tab next to Service Logs. The Activity Logs tab displays user activity for the connection, such as configuration changes and other administrative actions. For more information about activity logs, see [Viewing Activity Logs](/portal-admin/activity-logs).
For more information about investigating issues, see [Troubleshooting](/troubleshooting/overview).
## Viewing usage details
You can access a Service Graph to view usage details for a Port, VXC, or Megaport Internet connection. The Service Graph provides a visual representation of the service usage over time. You can view the graphs for a specific date range.
The Service Graph provides helpful information such as errors, optical signal levels, inbound/outbound packets, and inbound and outbound traffic. The graph is useful for comparing monthly usage on a Port or connection. You can export the service usage data in comma-separated values (CSV) format for analysis in spreadsheets and databases.
You can access a Service Graph from these locations:
* From the **Services** page, click the gear icon, then select **Telemetry**.\
You will see Service Graphs for the selected service only.
* From **Monitoring & Diagnostics** > **Service Telemetry**.\
This page shows usage for multiple services. You can filter the information for a specified date range and select a metric to display. For more information, see [Monitoring Services using the Service Telemetry Page](/monitoring/service-telemetry).
The Service Graph is updated every 5 minutes.
**To view usage details for a Port on the Services page**
1. Log in to the Megaport Portal and choose **Services**.
2. Click the gear icon next to the Port.
3. On the Port Details page, click **Telemetry**.\
The Service Graph page appears, showing all available metric graphs.
The controls above the graphs apply to all graphs at once. When you change a control, every graph updates together.
4. In the **Date Range** field, enter the range of dates for which to view usage details.\
Select from the following options:
* Last hour
* Last 12 hours
* Last 24 hours
* Last week
* Last month
* Last 3 months
* Last 6 months
* Last 12 months
* Custom - Enter a custom date range using the date picker.
The default time range is the last 24 hours.
5. In the **Resolution** control, select the resolution for the graph data: **5 min**, **Daily**, or **Monthly**.
The available resolutions depend on the selected date range:
* **5 min** is available only for ranges of 3 months or less.
* **Daily** is available for any range.
* **Monthly** is available only for ranges greater than 3 months.
Resolutions that the selected date range does not support are grayed out and unavailable, with a tooltip explaining why.
6. If you selected **Daily** or **Monthly** resolution, select one or more values in the **Aggregate** control to plot on the graph: **Average**, **Peak**, **95th percentile**, or **Minimum**. The **Aggregate** control is not shown for **5 min** resolution.
7. You can customize the graphs by selecting or clearing the **In errors/second**, **Out errors/second**, **Tx Power dBm**, **Rx Power dBm**, **In pps**, **Out pps**, **In Mbps**, **Out Mbps**, and **Configured speed Mbps** check boxes to show or hide data.
Use the mouse to hover over a specific data point to see the values and exact timestamp.
| **Metric** | **Description** |
| - | - |
| Errors | Errors/second - Rate of incoming and outgoing errors, measured in errors per second. |
| Optical | Optical signal levels for the Port, measured in decibel milliwatts. This metric is useful for measuring any signal loss over the connection. Tx Power dBm - Light level transmitted. Rx Power dBm - Light level received.
For a 100 Gbps Port, optical light levels are reported per lane. When an Optical graph is present, it displays a separate line for each lane, **Tx Lane 1** through **Tx Lane 4** and **Rx Lane 1** through **Rx Lane 4**, instead of a single Tx Power and Rx Power pair. For a Port with more than one interface, such as a Link Aggregation Group (LAG), the graph displays optical light levels for all of its interfaces. |
| Packets | In pps - Incoming packet rate to the Port, measured in packets per second Out pps - Outbound packet rate from the Port, measured in packets per second. |
| Traffic | In Mbps - Number of inbound Megabits per second. Out Mbps - Number of outbound Megabits per second. Configured speed Mbps - Configured speed of the Port, in Megabits per second. |
8. Click **Export CSV** to download the Port usage data for all metrics in a single CSV file.\
You can use the CSV file to import the data into spreadsheets and databases. You can open the CSV file in any text editor. The exported data uses the selected resolution.
9. Click **UTC** or your local time zone to change the time zone.
**To view usage details for a connection**
1. Log in to the Megaport Portal and choose **Services**.
2. Click the gear icon next to the VXC, Megaport Internet, or IX connection.
3. On the Connection Details page, click **Usage**.\
The Service Graph page appears, showing all available metric graphs.
The controls above the graphs apply to all graphs at once. When you change a control, every graph updates together.
4. In the **Date Range** field, enter the range of dates for which to view usage details.\
Select from the following options:
* Last hour
* Last 12 hours
* Last 24 hours
* Last week
* Last month
* Last 3 months
* Last 6 months
* Last 12 months
* Custom - Enter a custom date range using the date picker.
The default time range is the last 24 hours.
5. In the **Resolution** control, select the resolution for the graph data: **5 min**, **Daily**, or **Monthly**.
The available resolutions depend on the selected date range:
* **5 min** is available only for ranges of 3 months or less.
* **Daily** is available for any range.
* **Monthly** is available only for ranges greater than 3 months.
Resolutions that the selected date range does not support are grayed out and unavailable, with a tooltip explaining why.
6. If you selected **Daily** or **Monthly** resolution, select one or more values in the **Aggregate** control to plot on the graph: **Average**, **Peak**, **95th percentile**, or **Minimum**. The **Aggregate** control is not shown for **5 min** resolution.
7. You can customize the graphs by selecting or clearing the **In pps**, **Out pps**, **In Mbps**, **Out Mbps**, and **Configured speed Mbps** check boxes to show or hide data.
Use the mouse to hover over a specific data point to see the values and exact timestamp.
| **Metric** | **Description** |
| - | - |
| Packets | In pps - Incoming packet rate to the connection, measured in packets per second Out pps - Outbound packet rate from the connection, measured in packets per second. |
| Traffic | In Mbps - Number of inbound Megabits per second. Out Mbps - Number of outbound Megabits per second. Configured speed Mbps - Configured speed of the Port, in Megabits per second. |
8. Click **Export CSV** to download the connection usage data for all metrics in a single CSV file.\
You can use the CSV file to import the data into spreadsheets and databases. You can open the CSV file in any text editor. The exported data uses the selected resolution.
9. Click **UTC** or your local time zone to change the time zone.
10. For VXCs, select the A-End (the Port) or B-End (the destination) of the VXC from the **Source** drop-down list. The selection applies to all graphs.
On a VXC, you can view graphs from the A-End or B-End perspective. By default, the VXC graphs display the In and Out details from the perspective of the end you are viewing. In an Internet Exchange graph, you are simply connecting to that IX, so you can only view graphs for the A-End. Similar to IX, in a Megaport Internet graph you are connecting to the Transit router, so you can only view graphs for the A-End.
For information on how to view billing details for a connection, see [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
## Helpful references
* [IX Telemetry](/ix/ix-telemetry)
* [Monitoring MCR](/monitoring/mcr-monitoring)
* [Monitoring MVE](/monitoring/mve-monitoring)
* [Monitoring NAT Gateway](/monitoring/nat-gateway-monitoring)
* [Monitoring Service Activity in the Megaport Portal](/monitoring)
* [Monitoring Services for Status](/monitoring/service-status)
* [Monitoring Services using the Service Telemetry Page](/monitoring/service-telemetry)
* [Viewing Activity Logs](/portal-admin/activity-logs)
# Monitoring Services for Status
Source: https://docs.megaport.com/monitoring/service-status
This help topic describes the service statuses, how Megaport monitors services, and how often.
Megaport queries services every 5 minutes for status, and tracks alerts.
* **Regular status** -- The network hardware reports the current status of a service every 5 minutes. For any change in status, the monitoring system logs an event and you are sent an email notification. Megaport performs this status check for all services.
* **Event-based alerts** -- If the network hardware sends an alert based on an event, Megaport immediately logs the event for the service and you are sent an email notification. Megaport logs events for all services except VXCs.
Megaport might not report downtime in cases when the network hardware is down or unreachable, or for very brief interruptions to a VXC, such as a network flap. A VXC could go down and come back up in the time between two status checks.
Email notifications are sent once per hour, per user, per service. If a service status changes multiple times within an hour, you receive only one notification for that service during that period. For more information, see [Configuring Email Notifications](/portal-admin/email-notifications).
Service status can also be monitored using the Megaport API. For more information, see [Monitoring Service Status with the API](/api/monitoring).
## Service statuses
These are the available service statuses:
| Provisioning Status | Description | Port | MCR, MVE, or NAT Gateway | MegaIX, Megaport Internet, Megaport Marketplace, or other VXC connections |
| :- | :- | :- | :- | :- |
| NEW | Only for preordering Ports. This status indicates the service order has been accepted and is waiting on the infrastructure to be available. | This status applies to Port preorders only. The Port cannot accept any connections (such as a VXC) and is not billed. | N/A | N/A |
| DESIGN | The service has been added, but has not been ordered or deployed. | | | |
| DEPLOYABLE | The service order has been confirmed and is waiting for deployment. Services are typically in this state for 1-2 minutes. | | | |
| CONFIGURED | The deployment has completed and the service is configured on the network. | | | |
| LIVE | The meaning of this status depends on the product. | The service has been detected as live on the network. Light has been detected on the Port, meaning a Cross Connect has been attached and the Port activated. | The transition from CONFIGURED to LIVE is instantaneous. | The transition from CONFIGURED to LIVE is instantaneous. |
| CANCELLED, CANCELLED\_PARENT | Termination of the service has been requested. Services are typically in this state for 1-2 minutes. | You can terminate Ports directly and they remain in this state for up to 2 minutes. | You can terminate MCRs, MVEs, and NAT Gateways directly and they remain in this state for up to 2 minutes. | You can terminate VXCs directly or by terminating the attached Port, MCR, MVE, or NAT Gateway. |
| DECOMMISSIONED | The service has been decommissioned from the network. The service is billed only for the time that it was in use before it was decommissioned. Products on a term will incur early termination fees (ETF). | | | |
| FAILED | The service could not be deployed and is not in the deployment queue. | | | |
## MCR BGP notifications
You can receive email notifications whenever a session status changes on your MCR. These changes can include BGP going up, down, or flapping. If a session is flapping, only one email per hour will
be sent.
You can opt in or out of receiving these email notifications.
**MCR BGP notifications email specifications**
The MCR BGP notification system is designed to provide timely notifications for BGP up, down, or flapping events while minimizing alert noise.
The notification system implements rate limiting for rapidly changing status, as described below.
* The initial notification is sent immediately.
* Subsequent events within one hour are suppressed.
* The email body will indicate if the event has repeated during the suppression period.
**To receive BGP email notifications**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > User Settings > Notifications.
3. Click the Service Status notification group to view the BGP email notification types.
4. Select the notification group check box to subscribe to all notifications in that group, or subscribe to individual notification types. Any notification subscription changes are automatically saved.
## Helpful references
* [Monitoring MCR](/monitoring/mcr-monitoring)
* [Monitoring MVE](/monitoring/mve-monitoring)
* [Monitoring NAT Gateway](/monitoring/nat-gateway-monitoring)
* [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring)
* [Monitoring Service Activity in the Megaport Portal](/monitoring)
* [Monitoring Services using the Service Telemetry Page](/monitoring/service-telemetry)
* [Viewing Activity Logs](/portal-admin/activity-logs)
# Monitoring Services using the Service Telemetry Page
Source: https://docs.megaport.com/monitoring/service-telemetry
This help topic describes the service telemetry page, and how to use it.
This topic describes how to view service logs and usage reports for a Port, MCR, MVE, VXC, NAT Gateway, and IX in the Portal. These detailed reports help you monitor connections, evaluate performance, and troubleshoot issues with your Megaport services.
## Viewing Service Telemetry
The Service Telemetry page provides a multi-service landing page that displays the status of all your services in one place. You can filter the services by type, status, and location. You can also view the details of a specific service searching for it by name, location, or service ID.
To search for multiple services at once, separate your search terms with commas. For example, enter `Sydney, Melbourne, VXC`. A service appears if it matches any of the terms. Search terms are not case-sensitive and can match part of a service name, location, or service ID. Terms can contain spaces, so you can search for locations with multiple words.
**To view Service Telemetry**
1. Log in to the Megaport Portal and choose **Monitoring & Diagnostics** > **Service Telemetry**.\
The Service Telemetry page appears, showing graphs for Ports, MCRs, MVEs, VXCs, NAT Gateways, and IX connections.
2. In the **Date Range** field, enter the range of dates for which to view usage details. Select from the following options:
* Last hour
* Last 12 hours
* Last 24 hours
* Last week
* Last month
* Last 3 months
* Last 6 months
* Last 12 months
* Custom - Enter a custom date range using the date picker.
The default time range is the last 24 hours.
3. From the **Type** drop-down list, select the service type.
For a VXC connection, you can view graphs from the A-End or B-End perspective. By default, the VXC graph displays the in and out details from the perspective of the end you are viewing. Select the A-End (the Port) or B-End (the destination) of the VXC from the graph heading drop-down list.
4. In the **Metrics** drop-down list, select a metric for which to view usage details.\
The available metrics depend on the selected service type.
You can view a graph for one metric at a time.
The metrics available for selection vary by service type. For example, Port provide more metrics than VXCs, and Routes Imported, Routes Filtered, Broadcast/Multicast, and Unknown Unicast are available only for IX connections.
| **Metric** | **Description** |
| - | - |
| Traffic | In Mbps - Number of inbound Megabits per second. Out Mbps - Number of outbound Megabits per second. Configured Speed Mbps - Configured speed of the Port, in Megabits per second. |
| Packets | In pps - Incoming packet rate to the Port, measured in packets per second Out pps - Outbound packet rate from the Port, measured in packets per second. |
| Errors | Errors/second - Rate of incoming and outgoing errors, measured in errors per second. |
| Optical | Optical signal levels for the Port, measured in decibel milliwatts. This metric is useful for measuring any signal loss over the connection. Tx Power dBm - Light level transmitted. Rx Power dBm - Light level received.
For a 100 Gbps Port, optical light levels are reported per lane. When you select the **Optical** metric, the graph displays a separate line for each lane, **Tx Lane 1** through **Tx Lane 4** and **Rx Lane 1** through **Rx Lane 4**, instead of a single Tx Power and Rx Power pair. For a Port with more than one interface, such as a Link Aggregation Group (LAG), the graph displays optical light levels for all of its interfaces. |
| Subscribed Speed | Configured speed of the service, in Megabits per second. |
| Service Count | The number of active services connected to this service. |
| Routes Imported | A count of the BGP routes accepted from the IX peer, shown separately for each route server (primary and secondary, IPv4 and IPv6). |
| Routes Filtered | A count of the imported BGP routes dropped by Megaport route filters, shown separately for each route server (primary and secondary, IPv4 and IPv6). |
| Broadcast/Multicast Traffic | The volume of broadcast and multicast traffic emitted from the IX peer. A low level is expected. A high level can indicate a problem with the peer's configuration. For more information, see [IX Requirements](/ix/ix-requirements). |
| Broadcast/Multicast Packets | The rate of broadcast and multicast packets emitted from the IX peer. |
| Unknown Unicast Traffic | The volume of unknown unicast traffic emitted from the IX peer. Persistent unknown unicast traffic can indicate the peer is sending traffic to another peer on the IX that is no longer present. |
| Unknown Unicast Packets | The rate of unknown unicast packets emitted from the IX peer. |
5. In the **Resolution** field, select the level of detail for the graph: **5 min**, **Daily**, or **Monthly**.
* **5 min** resolution is available only for ranges of 3 months or less.
* **Daily** resolution is available for any range.
* **Monthly** resolution is available only for ranges greater than 3 months.
For Daily or Monthly resolution, select one or more of **Average**, **Peak**, **95th percentile**, and **Minimum** to plot those values on the graph. The **Aggregate** field is not shown for **5 min** resolution.
You can customize the graph by selecting or clearing the check boxes for **In Mbps**, **Out Mbps**, and **Configured Speed** to show or hide data.
Use the mouse to hover over a specific data point to see the values and exact timestamp.
* To export the telemetry data to CSV, select **Export CSV**. The exported data uses the resolution you selected.
* To view a graph in a larger size, click the **Expand graph** icon at the top right of the graph. The graph opens in a larger size for better readability. To return to the Service Telemetry page, click close.
## Helpful references
* [IX Telemetry](/ix/ix-telemetry)
* [Monitoring MCR](/monitoring/mcr-monitoring)
* [Monitoring MVE](/monitoring/mve-monitoring)
* [Monitoring NAT Gateway](/monitoring/nat-gateway-monitoring)
* [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring)
* [Monitoring Service Activity in the Megaport Portal](/monitoring)
* [Monitoring Services for Status](/monitoring/service-status)
* [Viewing Activity Logs](/portal-admin/activity-logs)
# Viewing Activity Logs
Source: https://docs.megaport.com/portal-admin/activity-logs
This help topic describes the Megaport Portal activity logs and how to view activity logs for your Megaport Portal account.
The Activity Log options on the Settings menu allow you to view activities that users have performed. The **User Activity** option shows activities only for the logged-in user, while the **Company Activity** option shows the activities of all users in the current company.
Users with any Portal role can view the **User Activity** option, however, only Company Admins can view the **Company Activity** option. For more information, see [Managing User Roles](/portal-admin/user-management/roles).
The Activity Logs record all activities that occur, and include the date and time of each event. Activity logs can provide an audit trail to prove any malicious activity via compromised accounts, show evidence of activities performed by API keys, and can be useful when troubleshooting a system issue.
Activity Log events are retained for 6 months.
## What information is logged
The system logs these activities:
* Logging in to the Portal (successful and failed)
* Logging in to the Portal with Single Sign-On
* Logging out of the Portal
* Enabling, resetting, and disabling Multi-Factor Authentication (MFA) for a user
* Configuring, deploying, and updating services (successful or failed)
* Approving, denying, or canceling a speed change
* Approving or denying connections
* Updating service terms
* Bulk management of service terms (successful or failed)
* Terminating services
* Registering payment cards, updating and removing cards, and making payments
* Setting up and updating service keys
* Updating user profiles
* Creating a company profile or Megaport Marketplace profile
* Setting up and updating billing markets
* Saving and managing configurations
* Updating user notification settings
* Managing users
* Locking and unlocking services
* Encountering issues with the ordering process
* Creating and updating a managed account
* Creating and updating Prefix Filter and Packet Filter lists
* Creating and updating resource tags
* Creating, updating, and deleting Megaport Marketplace forms
* Attaching, updating, and detaching forms on services
* Submitting and deleting form submissions
* API calls from external sources (such as customer integrations)
* Whether the activity is created by an API key user
* The client ID of the API key if the activity was created by an API key user
* The type of service for which the activity log is being created
* The UID of the service for which the activity log is being created
## What information is not logged
The Activity Log does not provide usage or billing information for a Megaport service, such as performance for a VXC or IX, or how much it costs. For more information about VXC billing, see [VXC Pricing and Contract Terms](/finance/vxc-pricing).
## What logs can users view
The following table shows the access and functionality available in the **User Activity** and **Company Activity** pages, based on user role.
| **User Role** | **Activity Log Functionality** |
| - | - |
| Non Admin (All role types except Company Admin) | **User Activity** Can view their own activities. Can filter activities by:
Activity name
Date
|
| Company Admin | **User Activity** Can view their own activities. Can filter activities by:
Activity name
Date
**Company Activity** Can view:
Activities of all users in the company
Activities of all API keys associated with the company. The User column displays the API key name.
Activities created by Megaport staff, for example, when performing support investigations
All system-generated activities
Can filter activities by:
Date
User type
User
Activity name
|
## Viewing activity logs
Depending on your role, you can perform the following actions to locate and view specific activity logs:
* **Sort** -- All users can sort activity logs by date/time.
* **Filter** -- All users can filter activity logs by date and activity name. Company Admins can also filter activity logs by user type or specific user.
* **Search** -- Company Admins can use a free text search on the Company Activity page to locate specific activity logs. The search matches all log details, including usernames, activity names, and full descriptions in the **More Details** option.
**To view the activity log table**
1. Visit the Megaport Portal and log in.
2. Choose:
* **User Menu > User Settings > User Activity** -- to view your own activities, or
* **User Menu > Admin Settings > Company Activity** -- to view company-wide activities.
The Activity Log page appears, showing activities by date, user type and username (Company Activity only), and activity name.
3. Click **More Details** to view additional information about an activity, including an expanded description to further explain the action that triggered the log entry.
**To sort activities**
You can sort activity logs by date and time, in either ascending or descending order.
* In the Activity Log page, click the small up/down triangle next to the **Date** column heading.
The activity log table reloads.
* Click the up/down triangle again to reverse the sort order.\
The up or down triangle next to the **Date** column heading indicates the current bidirectional sort order.
**To filter activities**
You can filter all activity logs by date and activity name. You can also filter Company Activity logs by user type and user.
1. In the Activity Log page, click the filter icon next to the column heading on which you want to filter.\
You can filter on activity date, user type, user, and activity name.
2. Filter the activity log table:
* **To filter by date** -- Select a single date or select two dates to filter between the date range.
* **To filter by user type** -- Select a user type from the list.
* **To filter by user** -- Search for and select a username.
* **To filter by activity name** -- Search for and select an activity name.
3. Click **Apply**.\
The filter is added to the top of the activity log table. You can save one filter per column at a time. Any saved filters are not retained if you leave the activity page and then return to the page.
**To search for activities**
Company Admins can use a free text search on the Company Activity page to locate specific activity logs. The search matches all log details, including usernames, activity names, and full descriptions in the **More Details** option. Any partial or complete matches are included in the search results.
1. Choose User Menu > Admin Settings > Company Activity.
2. In the Company Activity page, enter the search text in the **Search** field on the right. For example, enter **IDP** to search for any SSO sign up or login activities.\
Activity logs matching your search update in real-time as you type.
3. Use the sort, filter, and pagination controls to refine the search results and locate specific activity log entries.
## Viewing activity logs for a specific service
Company Admins can view activity logs for a specific service directly from the service details page. The Logs tab includes Service Logs and Activity Logs. The **Activity Logs** tab displays user activity related to the service, including configuration changes and updates. For more information, see [Viewing service logs](/monitoring/port-vxc-monitoring#service-logs).
## Helpful references
* [Managing User Roles](/portal-admin/user-management/roles)
* [Monitoring MCR](/monitoring/mcr-monitoring)
* [Monitoring MVE](/monitoring/mve-monitoring)
* [Monitoring NAT Gateway](/monitoring/nat-gateway-monitoring)
* [Monitoring Ports, VXCs, Megaport Internet, and IXs](/monitoring/port-vxc-monitoring)
* [Monitoring Services for Status](/monitoring/service-status)
# Managing Minimum Term Renewal
Source: https://docs.megaport.com/portal-admin/auto-renew
This help topic describes how Company Admins can modify the default Minimum Term Renewal setting for new services.
This topic describes how a Company Admin can modify the default Minimum Term Renewal setting for new services.
## What is Minimum Term Renewal?
The Minimum Term Renewal feature ensures that a service contract automatically renews for the same duration and discounted price at the end of its term.
By default, Minimum Term Renewal is enabled, that is, new services with a minimum term of 12, 24, 36, 48, or 60 months are set to renew automatically for the same duration and discounted price.
As a Company Admin, you can change the default Minimum Term Renewal setting at any time. Changing the default setting only affects new service orders and does not affect existing services. Users can override the default setting for each service by selecting or clearing the default setting any time.
The image shows the default enabled state for the Minimum Term Renewal setting for a new service.
* **If Minimum Term Renewal is enabled for the service:**
* No action is required. The service automatically renews for the same term length at the same discounted price.
* If a customer changes the VXC speed, the service is repriced based on the current market rate.
* For a VXC, the term discount is a fixed monthly amount calculated based on the percentage discount associated with the selected term length and committed speed. This discount remains fixed throughout the contract term, regardless of any speed changes.
* To opt out of automatic renewal, disable Minimum Term Renewal in the Megaport Portal before the contract expiry date. The service will then continue on a month-to-month basis at the same market rate.
* The early termination fee (ETF) for canceling a contract early remains 100% of the remaining term cost.
* **If Minimum Term Renewal is disabled for the service:**
* To continue the service under a minimum term contract, log in to the Megaport Portal before the contract expires and renew the service for 12, 24, 36, 48, or 60 months at the same discounted market rate.
* If no action is taken, the service continues on a month-to-month basis at the same market rate for Ports or the pay-as-you-go rate for virtual services.
## Notification email
A notification email is sent one month before the contract end date, informing customers of their Minimum Term Renewal options. For Megaport Internet connections, an additional notification is sent two months before the contract end date.
* **Recipients** -- All customer contacts in the Megaport Portal, that is, all primary company email addresses receive the email.
* **Managed accounts** -- Term renewal emails are sent to all users of the partner company, but not to users of the managed company.
* **Can customers disable the renewal emails?** -- No, these are critical service notifications and cannot be disabled.
## Changing the default setting
As a Company Admin, you can change the default Minimum Term Renewal setting at any time. The change applies to new service orders only and does not affect existing services.
**To configure the default Minimum Term Renewal setting for new services**
1. Log in to the Megaport Portal as a Company Admin.
2. Choose User Menu > Admin Settings > Minimum Term Renewal.
3. Set the default state for Minimum Term Renewal:
* **When creating new services on term, the option to Auto Renew the Term will be Enabled by default** -- The Minimum Term Renewal feature will be set to enabled for new services, automatically renewing the contract for the same term and discounted price.
* **When creating new services on term, the option to Auto Renew the Term will be Disabled by default** -- The Minimum Term Renewal feature will be set to disabled for new services, meaning the contract will not renew automatically.
4. Click **Save**.
## Bulk contract term management
Use the Term Management page to update contract terms for multiple services at once or to apply the Automatic Renewal setting across a group of services.
For more information, see [Managing Contract Terms in Bulk](/finance/term-management).
# Configuring Email Notifications
Source: https://docs.megaport.com/portal-admin/email-notifications
This help topic describes how to review and configure Megaport email notifications.
Registered Megaport Portal customers and users can manage email notification subscriptions in the Megaport Portal. Email notifications are categorized into these groups:
* Financial
* Company
* Ordering
* Services
* Service Status
You can choose to receive email notifications or opt out for each notification type, with some exceptions by account type.
Here are the email notification settings by account type:
| **Account Type** | **Supported By** | **Default Notification Settings** | **Configurable?** | **Notes** | |
| :- | :- | :- | :-: | :- | - |
| Direct | Megaport | Enabled for all categories except Service Status. | **✓** | | |
| Partner | Partner | Enabled for all categories except Service Status. | **✓** | Notification settings are hidden.
Partner accounts cannot disable managed account notifications. | |
| Partner | Megaport | Enabled for all categories except Service Status for both partner and managed accounts. | **✓** | Partner accounts can receive partner-only notifications or partner and managed account notifications.
Partner notifications are sent to Megaport. | |
| Managed | Megaport | Disabled for all categories. | **✓** | Managed account users are given access to Services, Ordering, and Service Status notifications for their own managed account and services.
Partner, Financial, and Company notifications do not appear.
Port and service re-terming notifications that a managed user is not subscribed to are sent to the partner. | |
| Managed | Partner | Disabled for all categories. Notification settings are hidden. | *X* | | |
**To change email notification preferences**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > User Settings > Notifications.
3. Click a notification group to view all of the individual email notification types in that group.\
The list of events that trigger notifications in that group appear.
4. Select the notification group check box to subscribe to all notifications in that group, or subscribe to individual notification types.
Any notification subscription changes are automatically saved.
## Default email notifications
All users, including partners and managed account users, receive the following People and Security email notifications by default. These categories are not configurable.
| **Category** | **Event** |
| - | - |
| People | When an email is being validated. |
| | When a user registers with a company. |
| | When a user enables two-factor authentication. |
| | When a user requests the secret for two-factor authentication. |
| Security | When a person tries to log in but fails. |
| | When a person registers. |
| | When a user requests a password reset. |
## Helpful references
* [Adding and Modifying Users](/portal-admin/user-management)
* [Managing User Roles](/portal-admin/user-management/roles)
* [Monitoring Services for Status](/monitoring/service-status)
* [Monitoring Service Status with the API](/api/monitoring)
* [Network Maintenance Notifications](/support/maintenance)
* [Setting up MCR BGP notifications](/mcr/configuring-mcr#bgp-notification)
# Megaport Letter of Authorization
Source: https://docs.megaport.com/portal-admin/loa
This help topic describes the Megaport Letter of Authorization and how it is used.
Before you can establish the physical cross-connect from your data center to the new Megaport Port, you must present a Letter of Authorization (LOA) to your data center provider.
After you create a Port, an LOA is automatically generated and available for download in the Megaport Portal. Click **Download LOA** next to the new Port on the Services page.
The LOA is a PDF document that includes the patching details for the Megaport end and is required when placing a cross-connect with the data center. New Ports are not active until the data center operator establishes the physical cross-connect from your network device to the Port.
| Term | Description |
| - | - |
| Issue Date | The date when the service was ordered. |
| LOA Issue Date | The date when the LOA was issued. If the LOA Issue Date has passed and expired, download another copy from the Megaport Portal to automatically update the Issue Date to today's date. |
| Issued By | The Megaport entity that you placed the service order through. |
| Requested By | The Megaport-approved party that will connect to our demarcation point. |
| Service ID | The unique identifier for your Megaport service. |
| Customer Demarcation/ Z Side | The demarcation details required by the data center. Some LOAs do not provide specific Port numbers. This generally indicates that Megaport will be required to complete patching at our end to finalize the cross-connection. Port details can be supplied to you after the cross-connect is complete. If the data center advises that the LOA demarcation is incorrect, contact our [Support team](/support/contact) for assistance. |
# Locking Megaport Services
Source: https://docs.megaport.com/portal-admin/locking
This help topic describes how to lock Ports and other services to prevent modification and deletion.
If you are a *Company Admin* user, you can lock Ports, Megaport Cloud Routers (MCRs), Megaport Virtual Edges (MVEs), Internet Exchanges (IXs) and other Megaport services to prevent modification or deletion. For information about user roles such as *Company Admin*, see [Managing User Roles](/portal-admin/user-management/roles).
You can lock a service while it is still provisioning; the service does not need to be *Live*. For example, you can lock a configured Port that is awaiting its Cross Connect. Unlocking is available regardless of provisioning status.
Locking is not available for services that are in your cart, or that have been cancelled, decommissioned, or have failed. When locking is unavailable, the padlock icon is grayed out.
**To lock a Port service**
1. In the Megaport Portal, go to the **Services** page.
2. Click the padlock icon next to the service you want to lock.
**Example 1:** A Port (DRNYC1) has a VXC attached (Singapore SG2). The padlock icons on the Port and VXC indicate that the Port's provisioning status is *Live*, traffic is traversing across the VXC, and both services can be locked.
**Example 2:** The same Port and VXC are shown; however, even though the Port is unlocked, the VXC remains locked. When a single VXC is locked, it is not possible to delete the VXC, the Port, or any attached services (as indicated by the grayed out Delete Port icons). To delete the Port, a *Company Admin* must unlock the VXC first.
**To lock an Internet Exchange or Virtual Cross Connect service**
1. In the Megaport Portal, go to the **Services** page.
2. Click the padlock icon next to the Megaport service you would like to lock.
## User role permissions
If an Admin user below *Company Admin* (such as a *Technical Admin* or *Finance Admin* user) has permission to make changes, they still won't be able to delete or edit any locked Megaport service. Only a *Company Admin* can unlock the service. Other users receive the following warning if they attempt to make a change.
Users at access levels below *Company Admin* can perform the following tasks:
* **Add VXCs/IX services to locked Megaport services** -- Additional services will not be set to Locked status. By default, they will be set to Unlocked.
* **View details of locked Megaport services** -- If a service is locked, its status can be viewed on the Details page.
# Managing your Megaport Marketplace Profile
Source: https://docs.megaport.com/portal-admin/megaport-marketplace
This help topic describes how to manage your Megaport Marketplace profile.
The Megaport Marketplace option on the Settings menu allows you to create and manage your Megaport Marketplace profile.
Choose User Menu > Admin Settings > Megaport Marketplace to manage your Megaport Marketplace profile.
## Creating a Megaport Marketplace profile
If you do not have a Megaport Marketplace profile, click **Edit** to begin entering details.
For more information about creating a Megaport Marketplace profile, see [Creating a Megaport Marketplace Profile](/marketplace/profile).
## Updating a Megaport Marketplace profile
If you already have a Megaport Marketplace profile, click **Edit** to update your details.
For more information, see [Changing your profile](/marketplace/profile#changing-your-profile).
## Helpful references
* [Megaport Marketplace Overview](/marketplace/overview)
* [Creating a Megaport Marketplace Profile](/marketplace/profile)
* [Requesting a Connection to a Service Provider](/marketplace/connections)
* [Megaport Marketplace Frequently Asked Questions (FAQs)](/marketplace/marketplace-faqs)
# Monitoring Maintenance and Outage Events
Source: https://docs.megaport.com/portal-admin/monitoring-events
This help topic describes the Service Status page and its features.
The Service Status page allows you to monitor maintenance and outage events that affect your services, including current, scheduled, and past events. By staying informed about maintenance activities and service outages, you can plan effectively around scheduled maintenance and provide faster responses during unplanned outages.
Event notifications for service maintenance and outages are sent via email and displayed on the Service Status page. You can quickly access these events and drill down to see the affected services.
For partner and managed accounts, access to the Service Status page is available to both partners and managed accounts. If you, as a partner, want to monitor events for your managed accounts, switch from a partner account to a managed account and access the Service Status page.
Follow these steps to learn how to use the Service Status page.
**To monitor maintenance and outage events**
1. Access the Service Status page in one of these ways:
* In the left navigation, click **Service Status**.
* From the dashboard of the Megaport Portal, click **Service Status**.
* On the Services page, click (Extra Actions) > **Service Status**.
Alternatively, maintenance and outage events are displayed on the Services page for the duration of the ongoing event. Click **View** to access the event on the Service Status page.
2. On the Service Status page, select **Maintenance** or **Outages** to filter the events accordingly.
The maintenance and outage events data automatically refreshes every 5 minutes, but you can also click **Refresh** to get the latest updates immediately.
3. Filter events:
* Search for any text or find a specific event related to a product by entering the product ID.
* For maintenance, filter by:
* **Scheduled** -- Events that are planned but have not started yet.
* **Ongoing** -- Events that are in progress.
* **Completed** -- Events that were completed within the last 90 days.
* **Cancelled** -- Events that were canceled within the last 90 days.
* For outages, filter by:
* **Ongoing** -- Events that are in progress.
* **Resolved** -- Events that were resolved within the last 90 days.
4. Select the required time zone from the Timezone (UTC) drop-down list.
For example, to select the time zone for Chicago (UTC-5), type **Chicago** in the **Timezone** field then select **America/Chicago**.
* If you select a time zone on the **Maintenance** tab, it will apply only to the maintenance events. Similarly, if you select a time zone on the **Outages** tab, it will apply only to the outage events.
* If you sign out, the time zone resets to the default (UTC).
5. View maintenance events in a **List** or **Calendar** view.
The **Calendar** view allows you to see the start and end times of maintenance events visually, making it easier to track upcoming activities.
In the **Calendar** view, you can toggle between month, week or day views. Double-clicking on a day in the month or week view will narrow the focus to the corresponding day. From there, click the event to view the full details of the event similar to how it appears in the **List** view.
6. Sort events:
* **Status** -- Sort events based on their status, such as Scheduled, Ongoing, Completed, and Canceled for maintenance events, or Ongoing and Resolved for outages.
* **Start Date** -- Sort events by their start date in either ascending or descending order.
7. After you find the service event, you can view detailed information about the affected services.
To search for events related to a particular service, copy the service ID of an event to your clipboard by clicking on it. You can then paste it into the **Filter** field to search for that service. Make sure that relevant filters (Scheduled, Ongoing, Canceled, Completed) are enabled to see all results.
You can also click **Logs** to view the service logs for the selected service.
If no results are found that match your criteria, try adjusting the filter settings to broaden your search.
# Megaport Portal User and Admin Settings
Source: https://docs.megaport.com/portal-admin/overview
This help topic describes how to access the Megaport Portal User and Admin settings
The Megaport Portal provides two places to manage settings.
* The **User menu**, at the top right of the Portal header bar, for your personal account settings.
* The **Company** section, in the main navigation menu, for company-wide settings. This section is visible only if you are a Company Admin.
## Using the User menu
Click your avatar at the top right of the Portal header bar to open the User menu. From here, you can access:
* **Profile** -- Manage your personal profile details, email address, and password. For more information, see [Managing Your User Profile](/setting-up/manage-profile).
* **Notifications** -- Manage your email notification preferences. For more information, see [Configuring Email Notifications](/portal-admin/email-notifications).
* **Language** -- Set the language for the Megaport Portal. See [Setting the language](#setting-the-language).
* **Theme** -- Switch between light and dark mode. See [Changing the Portal theme](#changing-the-portal-theme).
* **Logout** -- Log out of the Megaport Portal. See [Logging out](#logging-out).
### Setting the language
Use the **Language** option to set the language for the Megaport Portal. Select your preferred language from the drop-down list.
To change the language of the Megaport documentation, go to [Megaport Documentation](https://docs.megaport.com/megaport) and select your preferred language from the drop-down menu.
### Changing the Portal theme
Use the **Theme** option in the User menu to switch between light and dark mode for the Megaport Portal. Click the sun icon for light mode or the moon icon for dark mode.
Your theme preference is saved in your current browser. If you log in to the Megaport Portal using a different browser or clear your browser data, you need to select your preferred theme again.
### Logging out
Click **Logout** to safely log out of the Megaport application.
If you have the Megaport Portal or Quoting Tool open in multiple tabs in the same browser, logging out in one tab automatically logs you out of all other open tabs of that application. The other tabs update immediately without requiring a refresh and display a message with a link to log in again.
This behavior applies only to tabs in the same browser and is application-specific. Logging out of the Megaport Portal does not log you out of the Quoting Tool, and vice versa.
## Using the Company section
The **Company** item is visible only in the main navigation menu if you are a Company Admin. The options you see depend on your Megaport account role.
Click **Company** in the main navigation menu to administer company-wide settings:
* **Company Profile** -- View and update your company details and registered information. For more information, see [Updating a Company Profile](/setting-up/company-profile).
* **Manage Users** -- Add and manage user account details and roles within your company. For more information, see [Managing User Roles](/portal-admin/user-management/roles).
* **Marketplace Profile** -- Configure your Megaport Marketplace presence and visibility settings. For more information, see [Managing Your Megaport Marketplace Profile](/portal-admin/megaport-marketplace).
* **Security Settings** -- Manage your Single Sign-On and Multi-Factor Authentication security settings. For more information, see [Managing Security Settings](/portal-admin/security-settings).
Other company administration tasks, such as billing, webhooks, and activity logs, are available from their own sections in the main navigation menu, such as **Billing**, **Integrations**, and **Monitoring & Diagnostics**.
## Helpful references
* [Assigning a Finance User Role](/finance/finance-user)
* [Configuring Email Notifications](/portal-admin/email-notifications)
* [Downloading Invoices](/finance/download-invoice)
* [Enabling Billing Markets](/finance/enabling-market)
* [Logging in to the Megaport Portal](/setting-up/logging-in)
* [Managing Security Settings](/portal-admin/security-settings)
* [Managing User Roles](/portal-admin/user-management/roles)
* [Managing Your Megaport Marketplace Profile](/portal-admin/megaport-marketplace)
* [Managing Your User Profile](/setting-up/manage-profile)
* [Multi-Factor Authentication](/setting-up/enforcing-mfa)
* [Setting up Single Sign-On](/setting-up/enforcing-sso)
* [Updating a Company Profile](/setting-up/company-profile)
* [Updating Your Billing Information](/finance/payment-info)
* [Using Webhooks in the Megaport Portal](/portal-admin/using-webhooks)
* [Viewing Activity Logs](/portal-admin/activity-logs)
# Managing Security Settings
Source: https://docs.megaport.com/portal-admin/security-settings
This help topic describes how to manage security settings for your Megaport Portal account.
The Security Settings option on the Settings menu allows you to set your Single Sign-On (SSO) and Multi-Factor Authentication (MFA) configuration details.
Choose User Menu > Admin Settings > Security Settings to access SSO and MFA settings.
## Managing Single Sign-On
Use the **Single Sign-On** tab to enable and manage SSO settings for your company.
For more information, see [Setting up Single Sign-On](/setting-up/enforcing-sso).
## Managing Multi-Factor Authentication
Use the **Multi-Factor Authentication** tab to administer MFA for your company.
For more information, see [Multi-Factor Authentication](/setting-up/enforcing-mfa).
# Adding and Modifying Users
Source: https://docs.megaport.com/portal-admin/user-management/index
This help topic describes how to manage users for your Megaport Portal account.
If you are a Company Admin for the Megaport Portal, you can create and edit Portal users, assign roles, activate/deactivate users, and reset Multi-Factor Authentication (MFA) per user. Creating a new user will send the user an email, inviting them to join your Megaport Portal account. For more information, see [Inviting Users to Your Account](/setting-up/inviting-users).
## Adding users
You can add new users who will be invited to your account. The maximum number of users you can add per account is 100.
**To create a new user**
1. Visit the Megaport Portal and log in.
2. Choose Company > Users.
3. Click **New User**.\
Complete all fields, including name, email, phone number, and role.
The user email address is required for registration. It becomes the username for logging in to the Megaport Portal and will receive notifications from the system. The role determines what actions the user can perform in the Megaport Portal and their access permissions. For more information about user roles, see [Managing User Roles](/portal-admin/user-management/roles).
* An email address cannot be used more than once and cannot be from a free email domain (such as Gmail, Yahoo, or Outlook).
* When SSO is enabled (an IdP connection has been created), and the email domain is associated with SSO, the user will be sent an email containing a link that must be clicked to confirm the user for the account. If the email domain is not associated with SSO, the standard invite email will be sent with a temporary password for logging in. Users from other domains can be added, however, a pop-up message will show during creation warning that the user won’t be able to log in unless they are a Company Admin. For more information, see [Setting up Single Sign-On](/setting-up/enforcing-sso).
4. Click **Save**.\
When you create a new user, the user is sent an email with instructions for logging in or confirming the user account. For more information, see [Inviting Users to Your Account](/setting-up/inviting-users).
## Modifying existing users
For existing users, you can edit the user profile, and activate and deactivate user access. This allows you to maintain accurate user details, ensure users are assigned to the appropriate roles, and suspend user access to the Megaport Portal.
* You cannot change the user's email address.
* When SSO is enforced and the user is in an *Inactive* state, if you are re-activating the user account and it is not associated with an SSO domain, the user will be blocked and unable to log in. Make sure that the user's email domain is associated with an SSO domain. As an exception, if the user is a Company Admin, they will be able to access their account even if they are not associated with an SSO domain. For more information, see [Setting up Single Sign-On](/setting-up/enforcing-sso).
**To modify an existing user**
1. From the Manage Users page, find the user to modify.\
You can use the filter at the top of the page to quickly find the user by name.
2. Click (Edit) for the required user.
3. Make the changes to the user account then click **Save**.
# Managing User Roles
Source: https://docs.megaport.com/portal-admin/user-management/roles
This help topic describes how to manage roles for the users of your Portal account.
You can assign user roles to control the actions and permissions of users. This table summarizes each user role and its supported functionality, indicated by a **✓**.
|
**Action** | **Company Admin** | **Technical Admin** | **Technical Contact** | **Finance** | **Financial Contact** | **Read Only** |
| - | :-: | :-: | :-: | :-: | :-: | :-: |
| Create services | **✓** | **✓** | | **✓** | | |
| Delete services | **✓** | **✓** | | | | |
| Design services | **✓** | **✓** | **✓** | **✓** | **✓** | **✓** |
| Update a service | **✓** | **✓** | **✓** | | | |
| Update the term on a service, including bulk updates | **✓** | **✓** | **✓** | | | |
| Approve a VXC in Megaport Marketplace | **✓** | **✓** | **✓** | | | |
| View services | **✓** | **✓** | **✓** | **✓** | **✓** | **✓** |
| Lock and unlock services | **✓** | | | | | |
| Access the MVE Console | **✓** | **✓** | **✓** | | | |
| Restart MVE | **✓** | **✓** | **✓** | | | |
| Create, view, and edit service keys | **✓** | **✓** | | **✓** | | |
| View usage | **✓** | **✓** | **✓** | **✓** | **✓** | **✓** |
| Enable and update billing markets | **✓** | | | **✓** | **✓** | |
| View markets | **✓** | | | **✓** | **✓** | |
| View and pay invoices | **✓** | | | **✓** | **✓** | |
| Waive early termination fees | **✓** | **✓** | | **✓** | | |
| Create, update, and delete credit cards | **✓** | | | **✓** | **✓** | |
| Create, view, and update users | **✓** | | | | | |
| Update user details | **✓** | **✓** | **✓** | **✓** | **✓** | **✓** |
| View Megaport Marketplace profile | **✓** | **✓** | **✓** | **✓** | **✓** | **✓** |
| Update Megaport Marketplace profile | **✓** | | | | | |
| Create and manage Megaport Marketplace forms | **✓** | | | | | |
| Subscribe to notifications | **✓** | **✓** | **✓** | **✓** | **✓** | **✓** |
| Create, update, and delete API keys | **✓** | | | | | |
| View User Activity logs | **✓** | **✓** | **✓** | **✓** | **✓** | **✓** |
| View Company Activity logs | **✓** | | | | | |
| Create, update, and delete webhooks | **✓** | **✓** | | | | |
Here are some details to consider when creating user roles:
* **Company Admin** -- Company Admins have access to all user privileges. We recommend limiting the number of Company Admins to only those who require full access, but defining at least two for redundancy.
* **Technical Admin** -- This role is for technical users who know how to create and approve orders.
* **Technical Contact** -- This role is for technical users who know how to design and modify services but don't have the authority to approve orders.
* **Finance** -- Finance users should have a financial responsibility within the organization while also understanding the consequences of their actions if they delete or approve services.\
*Note:* While creating services, direct customers can see the cost of the service before deploying. It is also possible to see the cost of deployed services by selecting a service in the Portal and viewing the Details tab.
* **Financial Contact** -- This user role is similar to the Finance role without the ability to place and approve orders, delete services, or administer service keys.
* **Read Only** -- Read Only is the most restrictive role. Note that a Read Only user can view service details which you might want to keep secure and private.
You can add user roles when you create a new user, or you can edit user information to change their role. For more information about adding a new user, see [Adding and Modifying Users](/portal-admin/user-management).
To edit users, you must be a Company Admin.
**To manage user roles and permissions**
1. Visit the Megaport Portal and log in.
2. Choose Company > Users.\
The Manage Users page appears. Using this page, you can add a new user, edit existing user privileges and contact information, and reset Multi-Factor Authentication (MFA) per user.
3. Click (Edit) to modify an existing user’s role or click **New User** to set up a new user and define their role.
4. Select the role for the user.
5. Click **Save**.
# Using Webhooks in the Megaport Portal
Source: https://docs.megaport.com/portal-admin/using-webhooks
This help topic describes how to use webhooks to receive real-time notifications when events occur in your Megaport account.
Webhooks are lightweight, event-driven HTTP callbacks that automatically push real-time data between applications, which allow you to receive real-time notifications when events occur in your Megaport account. You can integrate webhooks with your existing systems, such as monitoring tools, incident response platforms, or custom dashboards.\
To enable webhooks, you can create an endpoint URL to which Megaport pushes event data as it
happens.
You must have at least Company Admin or Technical Admin privileges to perform these actions. For more information, see [Managing User Roles](/portal-admin/user-management/roles).
## Creating a webhook endpoint
You can create up to 10 webhook endpoints for your company Megaport account. Each endpoint can be configured to receive notifications for specific event types, such as service provisioning, billing updates, or security alerts.
**To create a webhook endpoint**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin > Webhooks.
3. Click **+ Create Webhook** to create a new webhook endpoint.
4. In the **Create New Webhook** page, enter these details:
* **Name** -- A descriptive name for the webhook endpoint.
* **Destination URL** -- The endpoint URL where you want to receive event notifications. This should be a publicly accessible URL that can accept POST requests.\
The destination URL format must have the following details:
* It must use the HTTPS protocol.
* It must be publicly accessible and able to receive POST requests.
* It must be less than 2048 characters in length.
* **Event Subscriptions** -- Select the specific event types for which you want to receive notifications.
5. Click **Create Webhook** to save the webhook endpoint.
## Testing webhook endpoints
After creating a webhook endpoint, you can test it to ensure that it is correctly configured to receive event notifications.
**To test a webhook endpoint**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin > Webhooks.
3. In the Webhooks settings page, locate the webhook endpoint you want to test and click **Test** next to it.
4. On the Test Webhook page, click **Send Ping** to send a test notification to the webhook endpoint.\
The response will show on the page. A successful test will show a **Ping sent successfully** message. If the test fails, the response will include an error message indicating the reason for the failure.
## Managing webhook endpoints
You can manage your webhook endpoints from the Webhooks settings page. This includes editing the endpoint details, updating event subscriptions, and deleting endpoints that are no longer needed.
**To edit a webhook endpoint**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin > Webhooks.
3. In the Webhooks settings page, locate the webhook endpoint you want to edit and click **Edit** next to it.
4. In the Edit Webhook page, update the webhook name, destination URL, or event subscriptions as required.
5. Click **Save Changes**.
**To delete a webhook endpoint**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin > Webhooks.
3. You can delete a webhook endpoint from the Webhooks settings page by either:
* Clicking **Delete** next to the endpoint you want to remove, or
* Editing the endpoint and clicking **Delete** in the Edit Webhook page.
4. In either case, confirm the deletion by clicking **Delete** in the confirmation prompt.
This will permanently delete the webhook endpoint and stop all notifications from being sent to it.
**To disable a webhook endpoint**
You can disable a webhook endpoint without deleting it. This will stop all notifications from being sent to the endpoint until you re-enable it.
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin > Webhooks.
3. In the Webhooks settings page, locate the webhook endpoint you want to disable and click **Edit** next to it.
4. In the Edit Webhook page, click **Deactivate** to disable the webhook endpoint.
5. Confirm the action by clicking **Deactivate** in the confirmation prompt.
Events occurring while the endpoint is deactivated are not reported. When the endpoint is reactivated, only new events occurring after reactivation are reported.
**To re-enable a webhook endpoint**
You can re-enable a disabled webhook endpoint to resume receiving notifications.
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin > Webhooks.
3. In the Webhooks settings page, locate the disabled webhook endpoint you want to re-enable and click **Edit** next to it.
4. In the Edit Webhook page, click **Activate** to re-enable the webhook endpoint.
5. Confirm the action by clicking **Activate** in the confirmation prompt.
## Consuming webhook events
When an event occurs that matches the subscriptions of a webhook endpoint, Megaport sends a JSON POST request to the endpoint's destination URL.\
The request includes a JSON payload containing details about the event, such as the event type, timestamp, and relevant data.
For more information about the fields included in the data object for each event type, see the [Webhooks API Event Reference](/api/webhooks).
### JSON payload structure
The structure of the JSON payload will vary depending on the event type.
For more information about the fields included in the data object for each event type, see the [Webhooks API Event Reference](/api/webhooks).
### HTTP headers
Each webhook event delivery includes the following HTTP headers:
| Header | Description | Example |
| - | - | - |
| webhook-id | Unique identifier for this delivery (UUID) | d4f5a6b7-c8d9-4e0f-a1b2-c3d4e5f6a7b8 |
| webhook-timestamp | Unix timestamp in seconds when the delivery was sent | 1736942400 |
| Content-Type | Always application/json | application/json |
## Retrying failed deliveries
If a webhook delivery fails due, for example, to a network error or a non-2xx HTTP response, Megaport will automatically retry the delivery with an exponential backoff strategy. The retries will continue for up to 24 hours after the initial delivery attempt.\
After 7 total attempts (1 initial + 6 retries), the delivery is marked as failed and no further retries are attempted.
A delivery is considered successful when your endpoint responds with any 2xx status code (200-299).
**Retry Schedule**
| Attempt | Delay after failure |
| - | - |
| 1st retry | 30 seconds |
| 2nd retry | 5 minutes |
| 3rd retry | 30 minutes |
| 4th retry | 2 hours |
| 5th retry | 8 hours |
| 6th retry | 24 hours |
## Webhook best practices
**Respond quickly**
Return a 200 OK response within 5 seconds. We recommend acknowledging the webhook first and processing the payload in the background (asynchronously). If your endpoint fails to respond within the 5-second timeout, Megaport will mark the delivery as a failure and trigger a retry.
**Prevent duplicate events**
The webhook-id header uniquely identifies each delivery. Store processed webhook IDs and check for duplicates before processing. Network issues or retries can result in the same event being delivered more than once.
```python theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
def handle_webhook(request):
webhook_id = request.headers["webhook-id"]
if already_processed(webhook_id):
return 200 # acknowledge but skip processing
process_event(request.body)
mark_processed(webhook_id)
return 200
```
**Reject stale deliveries**
Use the webhook-timestamp header to block old messages. We recommend a 5-minute window to account for slight time differences between servers. This also protects your system from replay attacks, which occur when an attacker tries to resend an old intercepted message.
```python theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
import time
def validate_timestamp(request):
timestamp = int(request.headers["webhook-timestamp"])
now = int(time.time())
if abs(now - timestamp) > 300: # 5 minute tolerance
return 400 # reject stale delivery
```
**Ignore unknown fields**
Ensure your endpoint stays compatible with future payload updates. Megaport only adds new fields and never removes or changes existing ones.
**Use HTTPS only**
Your endpoint URL must use HTTPS. This ensures the payload is encrypted in transit. HTTP endpoints are rejected at registration time.
**Return appropriate status codes**
| Your response | Megaport behavior |
| - | - |
| 2xx | Delivery marked as successful |
| 3xx | Treated as failure, redirects are not followed |
| 4xx | Treated as failure, will retry |
| 5xx | Treated as failure, will retry |
**Keep your endpoint available**
Ensure your endpoint can handle your expected event volume and remains online consistently. If your endpoint is down or consistently returns errors, you might miss critical notifications about your Megaport account.\
If your endpoint is consistently unreachable, deliveries will exhaust all retry attempts and be marked as failed. Monitor your endpoint's availability and check the Megaport portal for delivery failures.
## Helpful references
* [Billing Events](/api/webhooks/events/billing)
* [Maintenance Events](/api/webhooks/events/maintenance)
* [Order Events](/api/webhooks/events/order)
* [Outage Events](/api/webhooks/events/outage)
* [Payment Events](/api/webhooks/events/payment)
* [Security Events](/api/webhooks/events/security)
* [Service Events](/api/webhooks/events/service)
* [User Events](/api/webhooks/events/user)
# Updating a Company Profile
Source: https://docs.megaport.com/setting-up/company-profile
This help topic describes how to update your company profile in the Megaport Portal.
Your company profile includes your account name and unique account identifier.
Entering an account name is mandatory when signing up for a Megaport account. However, you can change the account name defined for your company profile.
The account name is the name the public sees, not the legal name of your company.
**To update a company profile**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Company Profile.
3. Edit your account name.
4. Click **Save**.
# Managing Your User Profile
Source: https://docs.megaport.com/setting-up/manage-profile
This help topic describes how to manage your user profile details and to set your Multi-factor authentication (MFA) security preference.
From the User Profile page, you can update user profile details, email preferences, change your password, view account activity, and reset Multi-Factor Authentication (MFA) for your account.
## Updating your user profile details
This section includes these tasks:
* To manage your user profile details
* To change your email address
* To change your password
You cannot change your email address or password in this page if you have logged in to the Megaport Portal using Single Sign-On (SSO) or Google credentials. The **Change Email** and **Change Password** buttons are not available.
**To manage your user profile details**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > User Settings > Profile.\
The User Profile page appears.
3. To update your name and phone number, make the changes and click **Save**.
4. To update your email preferences, click **Email Preferences**, specify whether or not you want to receive Megaport newsletters and promotional material, then click **Save**.
The role associated with the logged-in user is also displayed in the User Profile page, where the user is assigned one of the standard roles. For more information, see [Managing User Roles](/portal-admin/user-management/roles).
**To change your email address**
1. Choose User Menu > User Settings > Profile.
2. Click **Change Email**.\
The Change Email screen appears.
3. In the **New Email** field, enter your new email address.
4. Click **Get Verification Code**.\
An email will be sent to your new email address with the verification code. The verification code is valid for 24 hours. An email will also be sent to the old email address advising of the email change request.\
Keep this screen open until you have entered the verification code.
5. In the **Verification Code** field, enter the verification code that you received in the email to your new email address.
6. Click **Save**.\
Your email address is now updated. You need to log in again after changing your email address to continue working in the Megaport Portal.
* The original email address will not change until a valid New Email and Verification Code combination has been entered.
* If the new email address that is entered is already registered with Megaport against another account, it will not be accepted.
* The new email address cannot be from a free email domain (such as Gmail, Yahoo, or Outlook). If a free email domain is used, the change will not be accepted.
**To change your password**
1. Choose User Menu > User Settings > Profile.
2. Click **Change Password**.\
The Change Password screen appears.
3. Specify the password details:
* **Old Password** -- Enter your current password.
* **New Password** -- Enter your new password.
* **Retype New Password** -- Enter your new password again to confirm.
The Megaport Portal password policy includes minimum password complexity rules. Your new password must contain:
* At least 8 characters
* Uppercase characters (A-Z)
* Lowercase characters (a-z)
* Numbers (0-9)
* At least one special character: ^ \$ \* . \[ ] ( ) ? " ! @ # % & / \ , > \< ' : ; | \_ \~ \` = + -
The password policy uses a password strength estimator to prevent common, easily guessed passwords, such as Passw0rd. If you have met all complexity requirements and your password is still being rejected, the likely cause is that the password is too common or easy to guess.
4. Click **Save**.\
For more information, see [Resetting Your Password](/setting-up/change-password).
## Securing your account with MFA
MFA is an authentication method and security system that ensures all of your business accounts require more than one verification factor before they can be accessed. For example, a username and password, and a code from an authentication app. MFA is a core component of a strong identity and access management (IAM) policy, and provides an extra level of security for your Megaport Portal account. We recommend that you use the Google Authenticator app when securing your accounts with MFA.
Each user should install a login verification app (such as Google Authenticator) on their digital device (phone, tablet, computer, and so on). When users log in, they check the login verification app for the token or code that they need to enter as the additional factor.
MFA is enforced globally. It is enabled by default and you cannot disable it.
You can reset MFA to enroll a new device, if required.
For more information about logging in with MFA, see [Logging in to the Megaport Portal](/setting-up/logging-in).
### Resetting MFA
You can reset MFA to enroll a new mobile device. This is required if you have lost access to your previous device, or if you want to change the device that you use for MFA.
* You will remain logged in to the Megaport Portal when resetting MFA.
* Resetting MFA does not disable MFA for your account.
* A Company Admin can also reset MFA for your account.
* Megaport Support is unable to reset or regenerate QR codes for customers. A Company Admin must perform this task in the Megaport Portal.
**To reset MFA**
1. Choose User Menu > User Settings > Profile.
2. Click **Reset MFA**.
If MFA is not set up for your account, the **Reset MFA** button is grayed out and unavailable.
3. Scan the QR code with the authenticator app.
4. Enter the one time token generated by the authenticator app.\
Using Google Authenticator, this is a series of six numbers.
5. Click **Reset Multi-factor Authentication**.\
A message appears stating that MFA has been reset successfully. After MFA has been reset, you need to supply a valid token from the authenticator app on the new device every time you log in to the Megaport Portal, in addition to your email and password. Tokens from the authenticator app on the previous device will no longer work.
# Creating and Managing Services using the Megaport Terraform Provider
Source: https://docs.megaport.com/terraform/deploying-terraform-configuration-file
This help topic describes steps to execute a terraform configuration file.
This topic describes the steps to create and manage Megaport services using the Megaport Terraform Provider.
Having learnt the basic knowledge for preparing Terraform configuration files, you are now ready to use the Megaport Terraform Provider to create and manage your Megaport services.
To prevent accidental modification or deletion of production services, we recommend that you test Terraform files in the staging environment first before applying them to the production environment.
## Preparing to deploy services with Terraform
To apply changes in the staging environment, confirm that your `provider.tf` file contains the following configuration.
```terraform theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
environment = "staging"
```
We recommend that you run the `terraform plan` command before applying changes, to review your execution plan.
The `terraform plan` command creates an execution plan, which lets you preview the actions that Terraform will make to your infrastructure.
This plan details exactly what Terraform will do to reach the state defined in your configuration files. You can preview which resources will be created, changed, or destroyed. This allows you to review the proposed changes before they are applied, preventing unexpected or unwanted modifications to your infrastructure.
The image below shows an example output running the `terraform plan` command. In this example, the Terraform configuration file will create a new month-to-month 1 Gpbs Port, named *Megaport Port A-End* at NextDC B2.
For more information, see [terraform plan command (HashiCorp)](https://developer.hashicorp.com/terraform/cli/commands/plan).
## Creating test services
After you are satisfied with the changes in the Terraform plan, you can create services in the staging environment using the following command in your terminal.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
terraform apply
```
This command creates new services based on the definition in the Terraform configuration file. See the following example output.
Type `yes` to confirm.
After you type `yes`, the Terraform configuration file creates services and an *Apply complete!* message appears.
After the apply process is complete, view the [staging Portal](https://portal-staging.megaport.com/) to confirm that the service(s) have been created as designed in the Terraform configuration file.
## Changing test services
To modify your services (for example, service name, VXC speed), update the Terraform configuration file ( `main.tf` ) you initially used. After making the required changes, apply them using the following command. For testing, ensure that you first apply these changes in the staging environment.
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
terraform apply
```
## Removing test services
After testing, clean up the staging environment by removing the services you created for the test using the following command:
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
terraform destroy
```
Make sure you are removing services in the staging environment, not in the production environment. See the example output below.
Type `yes` to confirm.
After you type `yes`, services defined in the Terraform configuration file will be removed, and a *Destroy complete!* message appears.
After the destroy process is complete, view the [staging Portal](https://portal-staging.megaport.com/) to confirm that the services are removed.
You need to refresh the staging Portal to check that the test services have been removed.
## Creating services in production
After you complete testing in the staging environment and are satisfied with the outcome, you can run the ` terraform apply` command in the production environment by specifying the production environment in the `provider.tf` file.
```terraform theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
environment = "production"
```
You need to create an API key in the production environment before running `terraform apply`. For more information, see [API key](/terraform/megaport-terraform-configuration#API-key).
After running the `terraform apply` command, refresh the Production Portal to check that the services have been created.
## Helpful references
* [Megaport Terraform Provider GitHub repository](https://github.com/megaport/terraform-provider-megaport)
* [Megaport Terraform Provider Registry documentation](https://registry.terraform.io/providers/megaport/megaport/latest/docs)
* [terraform apply command (HashiCorp)](https://developer.hashicorp.com/terraform/cli/commands/apply)
* [Terraform CLI Overview (HashiCorp)](https://developer.hashicorp.com/terraform/cli/commands)
* [terraform destroy command (HashiCorp)](https://developer.hashicorp.com/terraform/cli/commands/destroy)
* [terraform plan command (HashiCorp)](https://developer.hashicorp.com/terraform/cli/commands/plan)
# Getting Started with the Megaport Terraform Provider
Source: https://docs.megaport.com/terraform/getting-started
This help topic describes prerequisites for using Megaport Terraform Provider.
This topic describes the prerequisites and required setup steps to get started using the Megaport Terraform Provider.
## Prerequisites
This section describes the basic setup steps and provides the necessary links to start using the Megaport Terraform Provider. Before using the Megaport Terraform Provider, you need to:
1. **Understand Megaport's services** -- Understand the process of creating services and the features of each service.
* [Port](/connections/creating-port)
* [Virtual Cross Connect (VXC)](/connections/overview)
* [Megaport Cloud Router (MCR)](/mcr)
* [Megaport Virtual Edge (MVE) ](/mve)
* [Megaport NAT Gateway (NAT Gateway)](/nat)
* [Megaport Internet](/megaport-internet)
* [Internet Exchange](/ix)
2. **Understand Megaport Portal environments** -- Megaport provides two Portal environments, the production environment and the staging environment. You can test any action in the staging environment. All actions mirror the production system, but services will not be deployed and you will not be billed for any activity. For more information, see [Testing Configurations in the Staging Environment](/troubleshooting/staging).
We highly recommend that you test Terraform configuration files in the staging environment before applying them to production to prevent errors.
Automated configuration creates and deletes services instantly. Testing the configuration file in the staging environment helps you avoid accidentally changing or deleting live production services. Note that some live services in the production environment start incurring charges immediately after creation.
3. **Create a Megaport account** -- If you have not already created one, see [Creating an Account](/setting-up/registering).
4. **Add and modify users** -- To run Terraform configuration files, you must be a Company Admin. For more information, see [Adding and Modifying Users](/portal-admin/user-management).
5. **Create an API key** -- You need to create an API key before you can use the Megaport Terraform Provider. The API key consists of the `access_key` and `secret_key` values.
The API key values can be defined in the Terraform file in various ways, including as a variable, an environment variable, directly in the code (not recommended), and so on.
API keys are valid only in the environment in which they were created. If you need an API key to access a different environment, log in to the Megaport Portal in that environment and create the API key there. For more information, see [Creating an API Key](/api/api-key).
6. **Install the HashiCorp Terraform platform** -- Install the Terraform CLI and verify the installation. For detailed instructions, see the [Install Terraform (HashiCorp) documentation](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli).
7. **Have access to GitHub** -- You can obtain sample configuration files, report bugs, and learn about new Megaport Terraform Provider feature releases in the [Megaport Terraform Provider GitHub repository](https://github.com/megaport/terraform-provider-megaport).
8. **Install your preferred code editor** -- A code editor is required to create Terraform configuration files. For example, [Visual Studio Code](https://code.visualstudio.com/).
## Next steps
After you have completed all of the prerequisites above, you can create a Terraform configuration file. For more information, see [Creating a Megaport Terraform Provider Configuration File](/terraform/megaport-terraform-configuration).
## Helpful references
* [Initialize Terraform configuration (HashiCorp)](https://developer.hashicorp.com/terraform/tutorials/cli/init)
* [Install Terraform (HashiCorp)](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli)
* [Megaport Terraform Provider GitHub repository](https://github.com/megaport/terraform-provider-megaport)
* [Megaport Terraform Provider Registry documentation](https://registry.terraform.io/providers/megaport/megaport/latest/docs)
* [Visual Studio Code (example code editor)](https://code.visualstudio.com/)
# Importing Existing Production Services
Source: https://docs.megaport.com/terraform/importing-existing-services
This help topic describes steps to import existing production services into a target Terraform configuration file.
You might already have live services in your production environment. To transition to fully automated service management using the Megaport Terraform Provider, the corresponding Terraform configuration file must include resource definitions for all existing services, such as product name, speed, location, and so on.
To achieve this, you will need to import these services into the Terraform configuration file.
## Importing production services
To import existing production services, follow these steps. We recommend testing the process in the staging environment first.
**To import production services**
1. Create definitions matching the production service(s) in the target directory where related Terraform configuration files exist.
For example, if you want to import an MCR then you need to add the following Terraform configuration file into the target directory.
```terraform theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
resource "megaport_mcr" "example" {
product_name =
product_speed =
location_id =
contract_term_months =
diversity_zone =
}
```
2. You can find the product\_UID in the Portal. Click the service to view the URL.
The alphanumeric information at the end of the URL is the product\_UID.
3. Run the following command:
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
terraform import ""
```
Example:
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
terraform import megaport_mcr.example "example-uid-a123456-7000-3333-xyz"
```
After the import is complete, you will see a message similar to the following:
Confirm that the target service is imported into Terraform as intended by reviewing the `terraform.tfstate` file.
## Helpful references
* [Megaport Terraform Provider GitHub Best Practice for Imports](https://github.com/megaport/terraform-provider-megaport?tab=readme-ov-file#best-practice-for-imports)
* [Megaport Terraform Provider GitHub Importing Existing Resources](https://github.com/megaport/terraform-provider-megaport?tab=readme-ov-file#importing-existing-resources)
* [Megaport Terraform Provider Registry documentation (import IX)](https://registry.terraform.io/providers/megaport/megaport/latest/docs/resources/ix#import)
* [Megaport Terraform Provider Registry documentation (import Lag Port)](https://registry.terraform.io/providers/megaport/megaport/latest/docs/resources/lag_port#import)
* [Megaport Terraform Provider Registry documentation (import MCR)](https://registry.terraform.io/providers/megaport/megaport/latest/docs/resources/mcr#import)
* [Megaport Terraform Provider Registry documentation (import MVE)](https://registry.terraform.io/providers/megaport/megaport/latest/docs/resources/mve#import)
* [Megaport Terraform Provider Registry documentation (import NAT Gateway)](https://registry.terraform.io/providers/megaport/megaport/latest/docs/resources/nat_gateway#import)
* [Megaport Terraform Provider Registry documentation (import optional VXC information)](https://registry.terraform.io/providers/megaport/megaport/latest/docs/resources/vxc#optional)
* [Megaport Terraform Provider Registry documentation (import VXC)](https://registry.terraform.io/providers/megaport/megaport/latest/docs/resources/vxc#import)
# Megaport Terraform Provider Overview
Source: https://docs.megaport.com/terraform/index
This help topic describes an overview of Megaport, Terraform, and the Megaport Terraform Provider.
This topic provides introductory information about Megaport services, Terraform, and the Megaport Terraform Provider, aimed at new users seeking to get started using the Megaport Terraform Provider.
## What is Megaport?
Megaport is a global Network as a Service (NaaS) provider that makes it easy to connect your network to cloud services such as AWS, Microsoft Azure, and Google Cloud without needing complex physical infrastructure.
It uses a software-defined network (SDN) to let you create scalable, secure, and on-demand virtual connections called Virtual Cross Connects (VXCs), between data centers, cloud providers, and enterprise networks. If you are new to Megaport, see [Introducing Megaport](/overview/).
For users who want to work with , Megaport offers Terraform support so you can automate the setup and management of your network connections, just like you do with your cloud resources. This helps you build flexible, agile, and multicloud-ready networks with ease.
## What is Terraform?
Terraform is an Infrastructure as Code (IaC) tool developed by [HashiCorp](https://developer.hashicorp.com/terraform). It allows you to define infrastructure such as servers, networks, and databases in code, rather than configuring it manually through web interfaces.
With Terraform, you write simple, human-readable configuration files that can be version-controlled, shared, and reused. This approach makes infrastructure management more consistent, scalable, and efficient.
Terraform automates the creation, update, and removal of infrastructure resources, helping DevOps teams streamline and standardize their workflows.
## Key features of Terraform
* **Declarative** – You describe the final configuration of your infrastructure, and Terraform figures out how to achieve it, instead of providing step-by-step instructions to provision it manually.
* **Cloud-agnostic** – Terraform works with various cloud providers such as AWS, Azure, Google Cloud, and on-premises infrastructure. This allows for multicloud deployments.
* **Automation** – Terraform automates the provisioning and management of infrastructure, reducing manual errors and saving time.
* **State management** – Terraform keeps track of your infrastructure's state, enabling it to understand and manage changes effectively.
* **Modules** – Terraform provides reusable configurations that simplify the creation of complex infrastructure setups.
## What is the Megaport Terraform Provider?
The Megaport Terraform Provider lets you create, manage, and update Megaport services through the [Megaport API](/api) using [Terraform](https://developer.hashicorp.com/terraform) tools.
The Megaport Terraform Provider allows you to create and manage Megaport services, including Ports, Virtual Cross Connect (VXCs), Megaport Cloud Router (MCR), Megaport Virtual Edge (MVE), and partner VXCs. It makes it easy to create multicloud and hybrid environments on the Megaport software-defined network (SDN).
The benefits of using the Megaport Terraform Provider include:
* You can manage Megaport’s network resources in a consistent, repeatable, and automated manner.
* Creation of multicloud hybrid environments in an automated manner.
* Version-controlled, shared, and reused infrastructure management, making deployment more consistent and efficient.
* Reduced manual configuration and potential manual errors.
The Megaport Terraform Provider is intended to be used with the Megaport API. It constitutes part of the official paid product and is eligible for support through customer channels. For more information, see [Contacting Support](/support/contact).
Usage of the Megaport Terraform Provider constitutes your acceptance of the terms in the [Megaport Acceptable Use Policy](https://www.megaport.com/legal/acceptable-use-policy/) and [Global Services Agreement](https://www.megaport.com/legal/global-services-agreement/).
## Megaport Terraform Provider Release Notes
Megaport actively tests against the two latest major versions of Terraform to ensure compatibility and reliability.
You can find the latest version of the Megaport Terraform Provider in the [Megaport Terraform Provider Releases page](https://github.com/megaport/terraform-provider-megaport/releases). This page also includes release notes for each version.
We highly recommend that you keep your Terraform configuration file updated with the latest provider version to take advantage of improvements, new features, and important fixes.
## Service provisioning methods
Megaport offers three primary methods for provisioning and managing services: the Portal, API, and Terraform. The optimal choice depends on the customer's need for automation, the complexity of the deployment, and the user's role.
We recommend reviewing the [Service Provisioning Methods](/provisioning-methods) topic for information about suitable users and scenarios for each option to ensure you choose the method that best meets your requirements.
## Helpful references
* [Initialize Terraform configuration (HashiCorp)](https://developer.hashicorp.com/terraform/tutorials/cli/init)
* [Install Terraform (HashiCorp)](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli)
* [Megaport Live: Tech Drop-in: APAC 2024/09/27 - Megaport Overview & Terraform Overview](https://youtu.be/P9PwvT4T-eg?si=0GWT1owIWb83u3m3)
* [Megaport Terraform Provider GitHub repository](https://github.com/megaport/terraform-provider-megaport)
* [Megaport Terraform Provider Registry documentation](https://registry.terraform.io/providers/megaport/megaport/latest/docs)
* [Megaport Terraform Provider Releases page](https://github.com/megaport/terraform-provider-megaport/releases)
* [Release Notes](/whatsnew)
* [Visual Studio Code (a code editor)](https://code.visualstudio.com/)
# Megaport Terraform Provider Learning Materials and Resources
Source: https://docs.megaport.com/terraform/learning-materials-and-resources
You can find useful learning materials and resources to learn how to use the Megaport Terraform Provider.
This topic includes a variety of learning materials and resources to help you get started with and effectively use the Megaport Terraform Provider. We're continuing to add more new content — stay tuned!
## Webinars
The following is a list of webinars delivered by Megaport Solution Architects and Engineering Team staff.
Megaport + Infrastructure as Code (IaC): Automating Global Networks at DevOps Speed
**APAC and EMEA (July 2025)**
* [Presentation file](https://media.megaport.com/docs/pdf/terraform/2025-july-megaport-terraform-provider.pdf)
**NAM (Dec 2025)**
* [Presentation file](https://media.megaport.com/docs/pdf/terraform/2025-dec-megaport-terraform-provider-nam.pdf)
## Tutorial contents
We have developed an introductory tutorial for customers interested in testing the Megaport Terraform Provider alongside the Terraform MCP Server in the staging environment.
* [Tutorial: Megaport Terraform Provider](https://tutorials.megaport.com/terraform/?_gl=1*m4bjly*_gcl_au*MTQ2Mzg0MTczNC4xNzc2NjQ4ODQ5LjEyNjI5NTAwOS4xNzc2NjYwNTMzLjE3NzY2NjA1OTg.*_ga*MTA0MjU4MzU0MC4xNzYxMDEzMDIx*_ga_ETEP887XGG*czE3ODA0NDYwNjMkbzQ1OSRnMSR0MTc4MDQ0NjczOCRqNDckbDAkaDEwMDg2MTg4MTg.)
* [Tutorial: Building an Agentic Network with Megaport and Terraform](https://github.com/megaport/terraform-provider-megaport/blob/main/terraform-mcp-server.md)
The Megaport Terraform Provider is built on HashiCorp Terraform. HashiCorp is actively developing and progressively releasing the Terraform MCP Server implementation, which is currently in open beta. Megaport is closely monitoring HashiCorp's MCP Server deployment.
## Helpful references
* [Getting Started with the Megaport Terraform Provider](/terraform/getting-started)
* [Megaport Terraform Provider Overview](/terraform)
* [Troubleshooting the Megaport Terraform Provider](/troubleshooting/megaport-terraform-provider)
# Using Terraform MCP Server (open beta) for Megaport Terraform Provider
Source: https://docs.megaport.com/terraform/mcp-server
This topic introduces the current status of the Megaport Terraform Provider in relation to Terraform Model Context Protocol (MCP) Server.
This topic introduces the current status of the Terraform Model Context Protocol (MCP) Server (open beta) in relation to the Megaport Terraform Provider.
Linking AI applications with Infrastructure-as-Code (IaC) opens new frontiers for network automation via AI agents. This integration enables AI applications to move beyond simple text generation, allowing them to actively evaluate and execute network configurations using Megaport's infrastructure.
## What is MCP?
The Model Context Protocol (MCP) is an open-source standard that acts as a universal translator between AI models and external tools or data sources.
Instead of building custom integrations for every AI application (such as Claude, ChatGPT, or Copilot), MCP allows a server to expose specific capabilities, such as reading files or executing API calls, to any compatible AI host, enabling complex tasks beyond simple text generation.
This allows AI applications to interact directly with technical environments, such as executing infrastructure changes via Terraform or retrieving live network analytics.
## How does that relate to Terraform?
In the context of infrastructure management, an MCP server for Terraform allows AI applications to understand and interact with existing Terraform configurations and providers.
The Megaport Terraform Provider is a tool that communicates directly with the Megaport API to provision network resources, and MCP Server is a translator that helps AI applications to understand how to use the Megaport Terraform Provider correctly.
The Megaport Terraform Provider is built on HashiCorp Terraform. HashiCorp is actively developing and progressively releasing the Terraform MCP Server implementation, which is currently in open beta. Megaport is closely monitoring HashiCorp's MCP Server deployment.
## Tutorial contents
We have developed an introductory tutorial for customers interested in testing the Megaport Terraform Provider alongside the Terraform MCP Server in the staging environment.
It is available in the Megaport Terraform Provider GitHub repository. For more information, see [Tutorial: Building an Agentic Network with Megaport and Terraform](https://github.com/megaport/terraform-provider-megaport/blob/main/terraform-mcp-server.md).
## Helpful references
* [Terraform (HashiCorp)](https://developer.hashicorp.com/terraform)
* [Terraform MCP server overview](https://developer.hashicorp.com/terraform/mcp-server)
* [What is the Model Context Protocol (MCP)?](https://modelcontextprotocol.io/docs/getting-started/intro)
# Creating a Megaport Terraform Provider Configuration File
Source: https://docs.megaport.com/terraform/megaport-terraform-configuration
This help topic describes steps to prepare a terraform configuration.
This topic provides step-by-step instructions for preparing a Megaport Terraform Provider configuration file, based on common and effective methods identified by Megaport Solution Architects through customer engagements.
Before you start, perform the prerequisites described in [Getting Started with the Megaport Terraform Provider](/terraform/getting-started).
## Creating a configuration file
When you are ready with your network design, you can create executable Terraform configuration files to deploy the design using these steps.
**To create a configuration file**
1. Design your network with Megaport services.
Sample Megaport Terraform Provider configuration files are available in the [Megaport Terraform Provider GitHub repository](https://github.com/megaport/terraform-provider-megaport).
Megaport also provides explanations about [common multicloud connectivity scenarios](/deployment/multicloud). Sample Megaport Terraform Provider configuration files of common multicloud connectivity scenarios can be found in the [Megaport Terraform Provider GitHub examples page](https://github.com/megaport/terraform-provider-megaport/tree/main/examples/multicloud-scenarios).
2. Identify the Megaport enabled location ID.
Data center location names and site codes can sometimes change in the API. For reliable and stable Megaport Terraform Provider configurations, use the location ID instead of names or codes. For the most up-to-date list of Megaport data center locations, see [Megaport Location IDs](/enabled-locations/location-ids).
Location IDs are also available through the [GET /v3/locations Megaport API](https://dev.megaport.com/#7c8e0706-e138-4d9a-bc4f-0419d97604cf).
3. Define the Megaport Terraform Provider environment.
There are a few ways to manage Terraform directories and configuration files (.tf files). You need to establish the most effective way to manage your Terraform resources to meet your needs.
The following example shows how you could keep Terraform configuration files in an organized manner.
* Create a directory to keep a set of Terraform configuration files to manage a certain set of Megaport services, such as Port, MCR, VXC.
* Create a `provider.tf` file which declares the Megaport Terraform Provider environment.
You can define settings of other providers, such as AWS, Azure, and GCP in the `provider.tf` file. For more information, see [Build Infrastructure (HashiCorp)](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/aws-build).
* Keep the`provider.tf` file in the same directory that other Terraform configuration files are stored. The following example shows the `provider.tf` file containing the Megaport Terraform Provider related configurations:
```terraform theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
terraform {
required_providers {
megaport = {
source = "megaport/megaport"
version = ">= 1.4.1"
}
}
}
provider "megaport" {
environment = "staging"
access_key = "access_key"
secret_key = "secret_Key"
accept_purchase_terms = true
}
```
There are some important fields and information you need to define to configure the Megaport Terraform Provider configuration file.
* **Version** -- Megaport tests against the two latest major versions of Terraform. You can find the latest version of the Megaport Terraform Provider in the [Megaport Terraform Provider Registry documentation](https://registry.terraform.io/providers/megaport/megaport/latest/docs). We highly recommend that you keep the `provider.tf` file updated with the latest version number.
* **Environment** -- This defines the environment in which you will be deploying services using Terraform. For example, if this is set to `staging`, then the services will be created in the [https://portal-staging.megaport.com/](https://portal-staging.megaport.com/) environment. When you have finished testing in the staging environment and want to start deploying services in the production environment, set this value to `production`. For more information, see [Environments](/api#environments).
* **API key** -- You need to create an API key before you can use the Megaport Terraform Provider. The API key consists of the `access_key` and `secret_key` values.
API keys are valid only in the environment in which they were created. If you need an API key to access a different environment, log in to the Megaport Portal in that environment and create the API key there. For more information, see [Creating an API Key](/api/api-key).
* **Accept purchase terms** -- To order Megaport services using Terraform, you must accept the purchase terms. This will allow a billable event to occur in the production environment, that is, create and deploy Megaport services in the production environment that will incur costs.
4. Create the `main.tf` file, which declares your infrastructure. Then copy the sample configuration that implements a network design closest to yours and modify it as required in the `main.tf` file.
You can find sample configurations in the [Megaport Terraform Provider GitHub repository](https://github.com/megaport/terraform-provider-megaport).
The following example shows a Megaport Terraform Provider configuration to order a single Port.
```terraform theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
data "megaport_location" "location_1" {
name = "NextDC B1"
}
resource "megaport_port" "port" {
product_name = "Megaport Port Example"
port_speed = 10000
location_id = 5
contract_term_months = 1
marketplace_visibility = false
}
```
When you deploy Terraform, `provider.tf` is executed first. Then `main.tf` will be executed automatically along with any other Terraform configuration files saved in the same directory.
5. If this is your first time using Terraform, run the `terraform init` command in your directory to prepare the working directory containing Terraform configuration files.
This command performs several setup tasks such as downloading the Megaport Terraform Provider and other backend plugins to prepare your working directory for use with Terraform.
To run this command, the directory must first have Terraform configuration files. It is safe to run this command multiple times to bring the working directory up to date with changes in the configuration.
The image below shows an example of the output of the `terraform init` command.
For more information, see [terraform init command (HashiCorp)](https://developer.hashicorp.com/terraform/cli/commands/init).
## Next steps
After you have prepared the Terraform configuration files, you can deploy them in the staging environment for initial testing before applying them to the production environment.
For more information, see [Creating and Managing Services using the Megaport Terraform Provider](/terraform/deploying-terraform-configuration-file).
## Helpful references
* [Build infrastructure (HashiCorp)](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/aws-build)
* [Megaport Live: Tech Drop-in: APAC 2024/09/27 - Megaport Overview & Terraform Overview](https://youtu.be/P9PwvT4T-eg?si=0GWT1owIWb83u3m3)
* [Megaport Terraform Provider GitHub multicloud scenarios examples](https://github.com/megaport/terraform-provider-megaport/tree/main/examples/multicloud-scenarios)
* [Megaport Terraform Provider GitHub repository](https://github.com/megaport/terraform-provider-megaport)
* [Megaport Terraform Provider Registry documentation](https://registry.terraform.io/providers/megaport/megaport/latest/docs)
* [Provider Requirements (HashiCorp)](https://developer.hashicorp.com/terraform/language/providers/requirements)
* [terraform init command (HashiCorp)](https://developer.hashicorp.com/terraform/cli/commands/init)
# Megaport Terraform Provider Frequently Asked Questions (FAQs)
Source: https://docs.megaport.com/terraform/megaport-terraform-provider-faq
This help topic provides answers to common questions about using Megaport Terraform Provider.
This topic covers frequently asked questions about using the Megaport Terraform Provider. For more information, see [Megaport Terraform Provider Overview](/terraform).
### How do I find DC location information?
The easiest way to find a location is with the location name in the Portal.
However, data center location information, such as name or site code, is subject to change in the API. For reliable and stable Terraform configurations, we strongly recommend using the location ID instead of names or codes. For the most up-to-date list of Megaport data center locations, see [Megaport Location IDs](/enabled-locations/location-ids).
Location IDs are also available through the [GET /v3/locations Megaport API](https://dev.megaport.com/#7c8e0706-e138-4d9a-bc4f-0419d97604cf).
For more information, see step 2 in [Creating a Megaport Terraform Provider Configuration File](/terraform/megaport-terraform-configuration).
### How do I avoid deleting live services in the production environment while deploying a Terraform configuration file?
Lock your live services via the Portal before deploying a Terraform configuration file. For more information, see [Locking Megaport Services](/portal-admin/locking).
### How do I add new VXCs to a Port?
If a service such as a Port already exists in the production environment but isn't in your Terraform configuration file, you will need to import it. For more information, see [Importing Existing Production Services](/terraform/importing-existing-services).
Afterwards, add a new configuration line in the Terraform file to create a new VXC under that Port.
### How do I change the name of a service?
Update the `product_name` field in the Terraform configuration file.
Example: Change `product_name` = “Name of Product” to `product_name` = “Updated Name of Product”, then run the `terraform apply` command.
### Does the Megaport Terraform Provider support managing IX services?
Yes, it does.
### How do I apply a service key while ordering a VXC?
First, set up a service key in the Portal. For more information, see [Setting Up Service Keys](/marketplace/service-keys).
Once the service key is created, you can apply it in your `.tf` configuration when ordering a VXC.
In the [Megaport GitHub repository](https://github.com/megaport/terraform-provider-megaport/blob/main/examples/resources/megaport_vxc/resource.tf), there’s an example in `resource.tf` showing exactly how to do this.
Look for the block that starts like this:
`resource "megaport_vxc" "service_key_vxc" {`
* Replace `"YOUR-SERVICE-KEY-HERE"` with the value from the Portal.
* The `b_end` block is where you specify the service key for the remote end.
* You can still define other parameters (for example, `rate_limit`, VLAN) as required.
* The provider docs on GitHub include multiple VXC examples, including MCR and cloud connectivity scenarios.
### How do I find the current version of Terraform on my computer?
Run the `terraform version` command to check the version of Terraform you have installed.
This will output the version information for Terraform.
If the output is similar to the example below, visit [Upgrading Guides (HashiCorp)](https://developer.hashicorp.com/terraform/language/upgrade-guides) to update your system.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
terraform version Your version of Terraform is out of date!
The latest version is x.y.z.
You can update by downloading from
https://www.terraform.io/downloads.html
```
### How do I find the current version of the Megaport Terraform Provider?
Megaport actively tests against the two latest major versions of Terraform to ensure compatibility and reliability.
You can find the latest version of the Megaport Terraform Provider in the [Megaport Terraform Provider Releases page](https://github.com/megaport/terraform-provider-megaport/releases). This page also includes release notes for each version.
We highly recommend that you keep your Terraform configuration file updated with the latest provider version to take advantage of improvements, new features, and important fixes.
### Where do I update the Megaport Terraform Provider version number?
You update the version field in the `provider.tf` file.
See `version = ">= 1.4.1"` in the following example. This is an example of a version coding that instructs Terraform to use a version of the provider that is 1.4.1 or newer.
```terraform theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
terraform {
required_providers {
megaport = {
source = "megaport/megaport"
version = ">= 1.4.1"
}
}
}
```
### Do you support OpenTofu?
Yes, the Megaport Terraform Provider has been tested and is compatible with OpenTofu starting from version v1.3.7.
OpenTofu is an open-source, community-driven fork of Terraform that maintains compatibility with the same providers and HashiCorp Configuration Language (HCL) syntax.
While we test for compatibility with new Megaport Terraform Provider releases, we recommend checking the [Megaport Terraform Provider GitHub Releases page](https://github.com/megaport/terraform-provider-megaport/releases) for the latest information.
For usage details, see the Megaport Provider on the [OpenTofu Registry](https://search.opentofu.org/provider/megaport/megaport/latest) and refer to the [Megaport Terraform Provider GitHub Readme](https://github.com/megaport/terraform-provider-megaport/blob/main/README.md) file.
### Where are the most current examples?
Examples for Ports, VXCs, MCRs, and MVEs are available in the [examples directory](https://github.com/megaport/terraform-provider-megaport/blob/main/examples) of the provider. Additional guidance can be found in the Guides section of the [Megaport Terraform Provider Registry](https://registry.terraform.io/providers/megaport/megaport/latest/docs/guides), which provides context and instructions to complement the examples.
### How does terming work with the provider?
There should be no issues with putting a service on a contract term using Terraform.
### Why is there a requested\_product\_uid field?
This is because when selecting a partner Port, we don't allow the user to pick the specific Port, and the API will pick one dynamically for capacity reasons. This means that this field can be different to what the user requested, which would cause an error in the provider.
## Helpful references
* [Getting Started with the Megaport Terraform Provider](/terraform/getting-started)
* [Megaport Terraform Provider Overview](/terraform)
* [Troubleshooting the Megaport Terraform Provider](/troubleshooting/megaport-terraform-provider)
# Terraform State Management with Megaport Resources
Source: https://docs.megaport.com/terraform/terraform-state-management
This help topic describes Terraform state management and recommended practices for using it.
This topic describes the Terraform state file and recommended practices for using it to map your configuration files to the Megaport services deployed on your network.
## What is Terraform state?
Terraform stores information about resources you have created in a state file, called `terraform.tfstate`.
This file is automatically created after running the `terraform apply` command. It provides a snapshot of your infrastructure managed by Terraform at a specific point in time. It is created in the same directory where Terraform is deployed. We recommend monitoring `terraform.tfstate` regularly.
The main purposes of the Terraform state file are:
* **Mapping real-world resources** -- The state file keeps track of the real-world infrastructure resources that Terraform has created and is managing. It logs information about their configurations, IDs, and dependencies.
* **Source of truth** -- The state file is the source of truth about your current infrastructure. When you run the `terraform apply` command, it compares your configuration files with the state file to determine what changes need to be made.
* **Tracking metadata** -- The state file stores metadata that Terraform uses internally, such as the Terraform version used to create the state and resource dependencies.
For more information about the Terraform state file, see [State (HashiCorp)](https://developer.hashicorp.com/terraform/language/state).
## Understanding Terraform state for Megaport resources
Terraform state is a crucial component that maps your configuration files to the Megaport resources deployed on your network. When you run the `terraform apply` command, Terraform creates a state file, `terraform.tfstate`, that tracks all resources it manages, their configurations, and interdependencies.
**What does the Megaport Terraform Provider state file contain?**
For Megaport resources, the state file tracks information such as:
* Resource IDs and UIDs
* Port configurations
* VXC settings
* MCR router configurations
* Partner connections
* Location information
**Key state management concepts**
* **Importing existing resources** -- If you already have Megaport services configured through the Portal, use the `terraform import` command to bring them under Terraform management:
Example 1: Import an existing Port
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
terraform import megaport_port.my_port "example-uid-41d4-a716-446655440000"
```
Example 2: Import an existing VXC
```shell theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
terraform import megaport_vxc.my_vxc "example-uid-426f-9247-bb680e5fe0c8"
```
For more information, see [Importing Existing Production Services](/terraform/importing-existing-services).
* **Preventing accidental deletions** -- To safeguard critical infrastructure, use Terraform's `prevent_destroy` lifecycle feature. This option prevents the accidental deletion of existing resources when applying configuration updates. For more information, including some examples, see [Megaport Terraform Provider GitHub repository, Lifecycle Prevent Destroy Example](https://github.com/megaport/terraform-provider-megaport/tree/main/examples/prevent_destroy#lifecycle-prevent-destroy-example).
* **State file storage for team environments** -- By default, Terraform stores state information locally.
For Terraform state file storage in team environments, using a remote storage space is recommended for collaboration, version control, and security.
* Use remote state storage (Terraform Cloud, S3, and so on).
* Enable state locking to prevent concurrent modifications.
* Consider encrypting state files as they contain sensitive information.
* **State file maintenance** -- Occasionally, you might need to use some commands, for example:
* `terraform state list` to see all managed resources.
* `terraform state show` to examine a specific resource.
* `terraform state rm` to remove a resource from state without destroying it.
* **Handling state drift** -- Terraform's state file keeps track of all the infrastructure it manages. Manually changing these resources outside of Terraform can cause the state file to become inaccurate, a situation known as *drift*.
If Terraform's record of your infrastructure doesn't match reality, it will try to fix the discrepancies, potentially leading to the unintended deletion or recreation of your resources. For more information, see [Manage resource drift (HashiCorp)](https://developer.hashicorp.com/terraform/tutorials/state/resource-drift).
If changes are made to Megaport resources outside of Terraform:
* Use the `terraform refresh` command to update the state with the current resource configurations.
* Consider running the `terraform plan` command regularly to detect unauthorized changes.
## Recommended practices
We recommend you follow these practices for optimal results with Terraform:
* **Back up your state file regularly** -- Losing it is irreversible.
* **Version control your configuration files** -- However, never save state files containing sensitive data such as credentials. For more information, see [Sensitive Data in State (HashiCorp)](https://developer.hashicorp.com/terraform/language/state/sensitive-data).
* **Modularize complex configurations** -- This approach improves resource management by promoting a more organized and reusable structure.
* **Lock Megaport services in the Portal** -- Terraform state is the source of truth for resource management. To prevent conflicting changes to production services in the Portal and Terraform, locking production services is recommended. For more information, see [Locking Megaport Services](/portal-admin/locking).
For more information, see [Learn Terraform recommended practices (HashiCorp)](https://developer.hashicorp.com/terraform/cloud-docs/recommended-practices).
## Helpful references
* [Learn Terraform recommended practices (HashiCorp)](https://developer.hashicorp.com/terraform/cloud-docs/recommended-practices)
* [Manage resource drift (HashiCorp)](https://developer.hashicorp.com/terraform/tutorials/state/resource-drift)
* [Manage resource lifecycle (HashiCorp)](https://developer.hashicorp.com/terraform/tutorials/state/resource-lifecycle)
* [Megaport Terraform Provider GitHub repository, Lifecycle Prevent Destroy Example](https://github.com/megaport/terraform-provider-megaport/tree/main/examples/prevent_destroy#lifecycle-prevent-destroy-example)
* [Sensitive Data in State (HashiCorp)](https://developer.hashicorp.com/terraform/language/state/sensitive-data)
* [State (HashiCorp)](https://developer.hashicorp.com/terraform/language/state)
* [Target resources (HashiCorp)](https://developer.hashicorp.com/terraform/tutorials/state/resource-targeting)
* [terraform plan command (HashiCorp)](https://developer.hashicorp.com/terraform/cli/commands/plan)
# Troubleshooting Port Activation
Source: https://docs.megaport.com/troubleshooting/activation
This help topic describes troubleshooting steps to solve issues with Port activation.
At times your Port might not come up after the data center has completed your cross connect to the Megaport . The most common reason for this is swapped fiber polarity, but there are additional checks that you can perform to confirm.
You can verify Port status from the Megaport Portal. On the [Services page](/portal-admin/services-page) in the Portal, find the Port and mouse over its icon. A message displays the status of the service. The color of the icon also indicates the service status.
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Provide the to the data center** | After you create a Port, an LOA is automatically generated and available for download on the Megaport Portal. This PDF document includes the patching details for the Megaport end and is required when placing a cross connect with the data center. New Ports are not active until the data center operator establishes the physical cross connect from your network device to the Port. |
| **Verify the Tx and Rx optical levels on the device** | Check the transmitted (Tx) and received (Rx) light levels. When no signal is received from the far-end (Megaport) device, it could indicate that the polarity has been reversed. If no light is received from the Megaport end, verify the fiber polarity (next). |
| **Verify physical connections with the data center** | **For new services**
On one end of the connection, swap the Tx and Rx cables of the cross connect. After swapping, verify the Tx and Rx optical readings on the device.
models should align with the Interface Speed and Interface details in Megaport [Technical Specifications](/tech-specs). Reseat or swap the SFP device if needed.
Ensure that the cross connect is not faulty.
Place a loopback on the Megaport demarcation point where the cross connect terminates, facing the Megaport rack.
When contacting Megaport, provide the cable ID and the completion notice from the data center. **Note:** If the Port appears in the Megaport Portal, it usually indicates that the Megaport-side connectivity is functioning correctly.
When contacting Megaport, provide the cable ID and the completion notice from the data center.
**For existing services**
Ensure that adequate light is being transmitted outside of the demarcation point on your end.
Reseat or swap the SFP if needed.
Have the cross connect cleaned and checked for damages.
When contacting Megaport, provide the data center ticket number.
|
| **Verify auto-negotiation on the network interface** | Auto-negotiation is the ability of a network interface to automatically coordinate its own connection parameters (speed and duplex) with another network interface. Auto-negotiation is usually the preferred setting for configuring management ports. However, if the negotiation fails, mismatched network interface settings can severely affect network performance.
Verify that the correct transceiver type is in use.
Ensure that the negotiation settings align with Megaport. Megaport has `Negotiation Auto` set by default.
If the device does not support auto-negotiation, contact Megaport Support.
**Tips**
Negotiation issues usually occur when connectivity is up, optical light is detected in both directions, but the Port status is down on either end. This issue is common on a 1 Gbps Port.
The transceiver speed should match on both ends. For example, if you create a 1 Gbps Port in the Megaport Portal, you must also set the device to 1 Gbps.
|
## Next steps
If the troubleshooting actions do not resolve your issue, contact support. Before requesting assistance, collect the following information.
* **Troubleshooting results** -- Provide all troubleshooting steps taken in detail. For example, if loops were placed, note their location and which direction they faced.
* **Service ID** -- The Megaport Service ID is a unique 8-digit alphanumeric code located next to each service in the Services page of the Megaport Portal.
* **Data center cross connect completion notice** -- Customers receive a completion notice from the data center once the cross connect is installed. The notice includes the data center cross connect order number, which Megaport requires to provide to the data center technician.
* **Data center cross connect order number (data center ticket number)** -- Provide any existing ticket reference numbers that you have opened directly with the data center.
* **Data center ticket reference and cable ID** -- Megaport requires specific information to identify the cross connect in question and any troubleshooting that was performed in case Megaport needs to open a ticket with the data center. Before contacting Megaport:
* Collect the cross connect order reference number, troubleshooting ticket number, and cable ID
* Confirm if the connectivity is correct from the device to the Megaport demarcation point
* Confirm whether a carrier is used for this connection
The cable ID is assigned by the data center to each cross connect and is usually located on a tag or small card that attaches to the cross connect cable. The data center will also provide the ID upon the completion of a cross connect to the ordering party.
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
# API Deprecation Notices and Frequently Asked Questions (FAQs)
Source: https://docs.megaport.com/troubleshooting/api-v2-faq
This help topic describes API deprecation notices and some common questions about the API version changes.
This topic includes API deprecation notices and some common questions about the API version changes.
We recommend that you keep up to date with these changes and plan any API integration updates accordingly.
For more information about the APIs mentioned in this topic, see the API reference at
[https://dev.megaport.com](https://dev.megaport.com).
## August 2026 - Transition to API Key Authentication
We are retiring the legacy username/password endpoint (POST `/v3/login`). Programmatic access now requires an API key paired with a short-lived access token.
If you already use API keys, no action is required.
If you integrate with this endpoint, you must update your integrations to use API keys before 25 September 2026. The deprecated v3 endpoint will be decommissioned on that date and will no longer be available. Follow these steps to migrate:
1. A Company Admin must generate an API key in the Megaport Portal under Integrations > API Key Generator to obtain a `client_id` and `client_secret`.
We strongly recommend creating keys from a dedicated machine-to-machine Admin account to avoid interruptions if individual user accounts are deactivated.
2. Update your integration to exchange these credentials for a token by calling `https://auth-m2m.megaport.com/oauth2/token` using grant\_type=client\_credentials.
3. Pass the token as a Bearer token in the Authorization header on subsequent API requests. Tokens are valid for up to 24 hours (configured upon API key creation), so ensure your integration automatically requests a new token upon expiration.
For more information, see [Creating an API Key](/api/api-key). If you require further support, contact your Megaport Account Manager or see [Contacting Support](/support/contact).
## July 2026 - New v4 Activity Logging APIs
We have made important updates to our activity logging APIs. New v4 activity logging endpoints are now available and replace the previous v3 endpoints. The v4 endpoints provide the same functionality using updated endpoint paths and pagination parameters that are consistent with the rest of the Megaport API.
If you integrate with these endpoints, you must update your integrations to use the v4 endpoints before 8 January 2027. The deprecated v3 endpoints will be decommissioned on that date and will no longer be available.
The key changes are listed in the table below.
| **Function** | **Old API** | **New API** |
| :- | :- | :- |
| GET User Activity | GET /v3/activity | GET /v4/activity |
| GET Company Activity | GET /v3/companyActivity | GET /v4/company\_activity |
| GET User Activity Names | GET /v3/activityNames | GET /v4/activity\_names |
| GET Company Activity Names | GET /v3/companyActivityNames | GET /v4/company\_activity\_names |
| GET Company Activity Users | GET /v3/companyActivity/users | GET /v4/company\_activity/users |
### What has changed in the paginated endpoints?
The paginated list endpoints (`/v4/activity` and `/v4/company_activity`) adopt Megaport's standard paginated response format. When you migrate from v3, note these changes:
* Pagination parameters are now snake\_case -- Use `page_number` and `page_size` instead of `pageNumber` and `pageSize`.
* Pagination metadata is now returned in the response body instead of in the `Pagination-*` response headers, such as `Pagination-Total-Count`.
* The activity timestamp is now returned as an ISO-8601 `createdAt` value instead of the epoch-millisecond `createDate`.
* Filter parameters are now snake\_case. The old v3 names will be rejected:
* `/v4/activity` -- activityName > activity\_name
* `/v4/company_activity` -- activityName > activity\_name, userUid > user\_uid, userType > user\_type, targetEntityUid > target\_entity\_uid
* `/v4/company_activity_names` -- targetEntityUid > target\_entity\_uid
(q, from, to are unchanged)
* The sort field was renamed from `createDate` to `createdAt`. Use `sort=createdAt,desc`. An unknown sort field now returns 400 instead of being ignored, so `sort=createDate` needs updating.
* Response shape -- Activity items now sit under data.items (with data.pageNumber, data.pageSize, data.totalItems, data.totalPages), rather than data being the array directly. Anything reading data as a list should switch to data.items.
The non-paginated lookup endpoints (`/v4/activity_names`, `/v4/company_activity_names`, and `/v4/company_activity/users`) change only the path to snake\_case. The response body is unchanged.
## February 2026 - New v3 Password APIs
We’ve made some important updates to our password APIs, which might affect you. The v2 password endpoints `/v2/password/change` and `/v2/password/reset` have been deprecated and replaced with new v3 endpoints. The v3 endpoints accept parameters in a JSON request body instead of form-encoded query parameters.
To ensure your system continues to function without interruption, all users who integrate with these password endpoints are required to migrate to the v3 endpoints.
| **Function** | **Old API** | **New API** |
| :- | :- | :- |
| Change Password | POST /v2/password/change | POST /v3/password/change |
| Reset Password | POST /v2/password/reset | POST /v3/password/reset |
For more information about the password APIs, see [https://dev.megaport.com](https://dev.megaport.com).
## September 2025 - New v4 Pricing APIs
We’ve made some important updates to our pricing APIs, which might affect you. A new version, v4, is now available and replaces the previous v2 and v3 pricing APIs. This version is required to fetch pricing for all services, including Ports, MCRs, MVEs, VXCs, Megaport Internet connections, IXs, and add-on products such as Cross Connects.
To ensure your system continues to function without interruption, all users who integrate with these APIs are required to migrate to the latest versions. Please begin transitioning your API calls to v4, as all future pricing requests for new and existing services and add-on charges will only be supported on this version. The Megaport Terraform Provider is not affected by these updates.
The key changes are listed in the table below. The deprecated v2 and v3 APIs will be fully decommissioned on 15 March 2026.
For more information about the pricing APIs, see [https://dev.megaport.com](https://dev.megaport.com/#ef22a22f-9161-4f66-b30e-3c810f0237a4).
| **Function** | **Old API** | **New API** |
| :- | :- | :- |
| GET Port Price | GET /v2/pricebook/megaport | POST /v4/pricebook/product |
| GET VXC Price (v3) | GET /v3/pricebook/vxc | POST /v4/pricebook/product |
| GET Megaport Internet Price (v3) | GET /v3/pricebook/vxc | POST /v4/pricebook/product |
| GET MCR Price | GET /v2/pricebook/mcr2 | POST /v4/pricebook/product |
| GET MVE Price - No Megaport Internet (v3) | GET /v3/pricebook/mve | POST /v4/pricebook/product |
| GET IX Price | GET /v2/pricebook/ix | POST /v4/pricebook/product |
| GET IP Address Price (New) | N/A | POST /v4/pricebook/product |
| GET Cross Connect Price (New) | N/A | POST /v4/pricebook/addon |
| GET IPsec Price (New) | N/A | POST /v4/pricebook/addon |
| GET Contract Term Details | GET /v2/product/portTerms/\{productUid} | POST /v4/pricebook/product/terms |
## May 2025 - API version changes
We’ve made some important updates to our API which might affect you. As a result of the updates, all users who currently integrate with these endpoints are required to migrate to the latest versions.
The key changes are listed in the table below. The deprecated APIs will be fully decommissioned on 31 July 2025.
**Moving from v2 to v3:**
* v3 API is now available and required for:
* GET location for all services
* POST login with username and password
* Notification settings APIs
* GET activity logs
* Invoice APIs (Note also that `companyId` has been updated to `companyUid` and `supplierId` has been added to the URL)
**Moving from v3 to v4:**
* GET MVE Image Details
| **Function** | **Old API** | **New API** |
| :- | :- | :- |
| GET Locations Returns a list of data centers where you can order a Port, MCR, or MVE. | GET /v2/locations | GET /v3/locations |
| POST Log in With Username and Password | POST /v2/login | POST /v3/login |
| GET List Notification Settings | GET /v2/notificationPreferences | GET /v3/notificationPreferences |
| PUT Change Notification Settings | PUT /v2/notificationPreferences | PUT /v3/notificationPreferences |
| GET User Activity | GET /v2/activity | GET /v3/activity These endpoints are all now available:
/v3/activity
/v3/companyActivity
/v3/activityNames
/v3/companyActivityNames
/v3/companyActivity/users
|
| GET Invoices Returns a list of all the invoices for the company and billing market combination, for the specified date range. | /v2/company/\$/invoice/ supplierId/\{supplierId}?fromDate=\$ \&toDate=\$ | /v3/company/\$/invoice/ supplierId/\{supplierId}?fromDate=\$ \&toDate=\$ |
| GET Single Invoice Returns the specified invoice in JSON format. | /v2/company/\$/invoice/ \$ | /v3/company/\{companyUId}/supplier/ \{supplierId}/invoice/\{invoiceId} |
| GET Single Invoice PDF | /v2/company/\$/invoice/ \$/pdf | /v3/company/\{companyUid}/supplier/ \{supplierId}/invoice/\{invoiceId}/pdf |
| GET Single Invoice CSV | /v2/company/\$/invoice/ \$/csv | /v3/company/\{companyUid}/supplier/ \{supplierId}/invoice/\{invoiceId}/csv |
| GET MVE Image Details | GET /v3/product/mve/images | GET /v4/product/mve/images |
## February 2024 - New Invoice APIs
Our invoice APIs are changing.
To ensure you keep receiving the most accurate, up-to-date and complete invoice data, including credit notes and tax information, you are required to migrate to the new invoice API endpoints.
For more information about the invoice APIs, see [https://dev.megaport.com](https://dev.megaport.com/#3ef5f20b-b6b1-49f3-9e8a-3580b3272349).
### Which invoice APIs are affected?
These API endpoints have been deprecated and replaced with new API endpoints.
| **Function** | **Old API** | **New API** |
| :- | :- | :- |
| GET Invoices | GET /v2/invoice Returns a list of invoices for the company associated with the user account. | GET /v2/company/\$/invoice/supplierId/\{supplierId}?fromDate=\$\&toDate=\$? Returns a list of invoices for the company ID and billing market ID combination, for the specified date range. |
| GET Single Invoice | GET v2/invoice/\{invoiceId} Returns the invoice for the specified `invoiceId`. | GET /v2/company/\$/invoice/\$ Returns the invoice for the specified `companyId` and `invoiceId` in JSON format. |
| GET Single Invoice PDF | GET /v2/invoice/\{invoiceId}/pdf Returns a PDF version of the invoice for the specified `invoiceId`. | GET /v2/company/\$/invoice/\$/pdf Returns a PDF version of the invoice for the specified `companyId` and `invoiceId`. |
| GET Single Invoice CSV | GET /v2/invoice/\{invoiceId}/csv Returns a CSV version of the invoice for the specified `invoiceId`. | GET /v2/company/\$/invoice/\$/csv Returns a CSV version of the invoice for the specified `companyId` and `invoiceId`. |
### Where do I find the supplier and company information?
All of the new invoice APIs require you to send company and supplier information as part of the API call. You can find these values from the following Megaport APIs:
* `supplierId` is the "firstPartyId" returned in the GET Billing Markets `/v2/market` API for the relevant supplier.
* `companyUid` is returned in the GET Product List `/v2/products` API or the GET API Keys `/v2/auth/apikeys` API.
* `companyId` is returned in the GET Company Details `/v2/company/companyUid` API.
### When do I need to start using the new invoice APIs?
As soon as possible. The new invoice APIs are currently available in Production, any future enhancements related to invoices will be applied to the new APIs only.
### When will the legacy invoice APIs be decommissioned?
The legacy invoice APIs have been deprecated and are no longer supported.
### Who can I talk to for more information?
Please reach out to your Account Manager or Megaport Support. For more information, see [Contacting Support](/support/contact).
## April 2023 - v2 MVE APIs
In April 2023, we launched a new version of Megaport Virtual Edge (MVE). Previously, MVE had been offered as a bundle with preset compute, virtual circuits, and Megaport Internet specifications. With this latest version, we’ve unbundled Megaport Internet to separate compute from Virtual Cross Connects (VXCs) and Megaport Internet connections. By unbundling compute and transit functions, you can now get a new level of configurability and flexibility by further customizing your network to suit your needs.
MVE is now also available in multiple sizes and has double the RAM of our previous version for better performance. The compute sizes are now 2/8, 4/16, 8/32, and higher-capacity options, where the first number is the CPU and the second number is the GB of available RAM.
To enable this new feature, a v3 API has been created to get prices, validate, order, edit, and delete MVE and Megaport Internet connections as separate products. Existing API integrators who want to change the speed of their Megaport Internet connection will have to integrate with the new v3 API.
As a result, users who integrate with the Validate and Buy APIs for other service types, including Ports, MCRs, VXCs and IXs, in addition to MVEs and Megaport Internet connections, will also be required to migrate to the latest v3 version. No changes for these service types, other than the version, are applied to the url, request body or response body.
To maintain backward compatibility for our existing API integrators, API users will be able to keep using the current v2 Megaport API calls to order bundled MVEs until 30 September 2024, at which time the legacy v2 API will be deprecated. When ordering an MVE with v2 APIs, a Megaport Internet connection with the default speed associated to the selected MVE size will be created automatically.
All integrators are encouraged to migrate and start using the v3 APIs when ordering MVEs and Megaport Internet connections to make the most out of the additional flexibility.
Our Customer Portal has already switched to v3 for:
**Fetch prices of MVEs and VXCs:**
* GET /v3/pricebook/mve?locationId=\&vendor=\&size=
* GET /v3/pricebook/vxc?bLocationId=\&aLocationId=
**Validate and Buy of all service types:**
* POST /v3/networkdesign/validate
* POST /v3/networkdesign/buy
**Update VXCs (only):**
* PUT /v3/product/vxc/
**Delete all service types:**
* POST /v3/product//action/
### When do I need to start using MVE API v3?
As soon as possible and no later than September 2024. The MVE v3 APIs are currently available in Production, any future enhancements related to MVE and Megaport Internet connections will be applied to the v3 APIs only.
### When will the MVE v2 APIs be deprecated?
MVE v2 APIs will be deprecated on 30 September 2024.
### Which v2 APIs are affected?
This table lists the v2 APIs that are affected by these changes:
| **Function** | **Old API** | **New API** |
| :- | :- | :- |
| Get MVE Price | \*\*GET /v2/\*\*pricebook/mve Returns price of MVE + Megaport Internet connection. | \*\*GET /v3/\*\*pricebook/mve Returns price of MVE compute only. |
| Get VXC Price | \*\*GET /v2/\*\*pricebook/vxc Does not return Megaport Internet price. | \*\*GET /v3/\*\*pricebook/vxc With connectType=transit, returns price of Megaport Internet connection. |
| Validate orders for all product types: Port, MCR, MVE, VXC, IX | \*\*POST /v2/\*\*networkdesign/validate For MVEs, validates order of MVE + Megaport Internet connection together. | \*\*POST /v3/\*\*networkdesign/validate For MVEs, validates order of MVE only. **Note:** Available sizes are: `"SMALL" "MEDIUM" "LARGE" "X_LARGE_12"`. |
| Buy services for all product types: Port, MCR, MVE, VXC, IX | \*\*POST /v2/\*\*networkdesign/buy For MVEs, buys MVE + Megaport Internet connection together. | \*\*POST /v3/\*\*networkdesign/buy For MVEs, buys the MVE only. Can buy Megaport Internet connections alone. |
| Update VXC Details | \*\*PUT /v2/\*\*product/vxc/\{productUid} Cannot update Megaport Internet connections. | \*\*PUT /v3/\*\*product/vxc/\{productUid} Can update Megaport Internet connections. |
| Delete services for all product types: Port, MCR, MVE, VXC, IX | \*\*POST /v2/\*\*product/\{productUid}/ action/\{action} | \*\*POST /v3/\*\*product/\{productUid}/ action/\{action} |
### What if I haven’t migrated in time?
Your MVE integration will stop working and you won’t be able to order new or update existing MVEs. For more information, please contact your Account Manager.
### Who can I talk to for more information?
Please reach out to your Account Manager or Megaport Support. For more information, see [Contacting Support](/support/contact).
# Troubleshooting the API
Source: https://docs.megaport.com/troubleshooting/api/index
This help topic describes troubleshooting steps to identify and solve problems when using the Megaport API.
If you encounter problems with the API or with the Megaport Terraform solution, step through these troubleshooting actions.
For API tutorials and a step-by-step guide, see [Megaport API Overview](/api). For a full reference, including working examples, see [https://dev.megaport.com/](https://dev.megaport.com/).
To try out the API, we recommend the Postman client with the imported Megaport Collection; information on downloading and using Postman is in the documentation.
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Ensure API access token is valid** | Megaport API calls require an access token that you can generate after creating an API key. An access token is required for authenticating API users, and allows temporary access to only the parts of the Megaport Portal that are required. Access tokens expire after a maximum of 24 hours, after which you need to generate a new access token. For more information, see [Creating an API Key](/api/api-key). |
| **Ensure API environment (URL) is correct** | Ensure that the URLs you are using are for the intended environment.
PRODUCTION - `https://api.megaport.com` The fully functional, live system. You are responsible for any services and associated costs ordered in this system.
STAGING - `https://api-staging.megaport.com` Lets you test commands without impact to your production environment. The staging environment is overwritten every 24 hours with the latest production values.
|
| **Ensure API parameters are correct** | The Megaport API uses standard HTTP response codes. Generally speaking, a 400 - Bad Request error is typically caused by missing or incorrect parameters. If you are receiving this error, double check your parameters. |
| **Ensure your API syntax is correct** | The correct syntax is essential when interacting with the Megaport API. The Megaport API is based on REST, has predictable URLs, and accepts form-encoded request bodies.
You can see examples of the correct calls on [https://dev.megaport.com](https://dev.megaport.com/). Select your preferred language from the drop-down menu on this page, and you can see examples of how to do anything within the API environment. |
| **API Limits** | **General Rate Limit** There is a rate limit of 500 requests in a rolling 5 minute period per IP address.
**Service Updates** You can only make one service update every 5 minutes, and there is a maximum of 100 updates per month per service.
**Note:** Currently, these are not hard limits, but Megaport monitors and reviews when limits are breached. If limit breaches occur, access could be blocked. |
## Common API error messages
### Login error
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"message": "Bad session token - try logging in again."
```
Common causes:
* incorrect username, email, or password
* missing or incorrect token
### Syntax error
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
HTTP Status 400 – Bad Request
```
The error commonly occurs when a required syntax is missing or incorrect.
### Incorrect API URL
An example of the error related to an incorrect URL is:
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
"message": "Service abcd1234 has wrong product type VXC"
```
For this scenario, the customer used this URL:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
URL = "https://api-staging.megaport.com/v2/product/megaport/abcd1234-1234-1234-1234-abcdef123456/telemetry?from=1614283800000&to=1614284400000&type=BITS"
```
but the correct URL is:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
URL = "https://api-staging.megaport.com/v2/product/vxc/abcd1234-1234-1234-1234-abcdef123456/telemetry?type=A_BITS&from=1614283800000&to=1614284400000"
```
### Incorrect parameters
As an example, a customer reported no data output when requesting VXC telemetry for this time range:
* From: GMT: Tuesday, August 3, 2021 1:52:23 PM
* To: GMT: Tuesday, August 3, 2021, 1:57:23 PM
Syntax
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
https://api-staging.megaport.com/v2/product/vxc/abcd1234-1234-0000000000telemetry?type=A_BITS&from=1627998743&to=1627999043
```
Output
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{"serviceUid":"abcd1234-1234-0000000000","type":"A_BITS","timeFrame":{"from":1627998743,"to":"1627999043},"data":[]}
```
From the [Get VXC Telemetry docs](https://dev.megaport.com/#28c05fb0-582b-4498-8e29-d2144111c8de) the From and To parameters must be set in milliseconds for each epoch value (so each value needed extra zeros at the end):
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
https://api-staging.megaport.com/v2/product/vxc/abcd1234-1234-0000000000telemetry?type=A_BITS&from=1627998743000&to=1627999043000
```
## Megaport required data
If the troubleshooting actions do not resolve your issue, contact Megaport Support.
With an API issue, Megaport will investigate and troubleshoot the issue at the back end.
To assist the investigation, provide the results of the tests you performed and any other relevant information, such as:
* Email/account used
* Date, time, and time zone of action and when the error occurred
* API configuration
* API URL
* Body data
* Endpoint parameters and syntax
* Error type and a screenshot of the error
## Helpful references
* [Solutions to Common API Issues With Megaport](https://www.megaport.com/blog/solutions-to-common-api-issues-with-megaport/)
# Using a /31 IP Address Space for Cloud Service Provider Peering
Source: https://docs.megaport.com/troubleshooting/cloud/csp-address-space
This help topic describes how to use a 31-bit subnet mask for a BGP peering session.
Can I use a 31-bit subnet mask address to establish a BGP peering session with a Cloud Service Provider?
The answer depends on two factors:
* If your on-premises device is capable of supporting a configuration with a 31-bit subnet mask.
* If the Cloud Service Provider is capable of supporting a configuration with a 31-bit subnet mask.
## On-premises device support
The most common network device operating system supports the use of a 31-bit subnet mask, with some older versions displaying a warning, such as:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
% Warning: use /31 mask on non point-to-point interface cautiously
```
## Cloud Service Provider support
The majority of Cloud Service Providers support the use of a 31-bit subnet mask, including AWS, Oracle, Alibaba, and IBM. Here are details provided by each CSP:
* **Oracle Cloud Infrastructure FastConnect**
Quick reference: “For a private virtual circuit, you can specify a /30 or /31 network of your choice, and those IP addresses are assigned to the virtual circuit during the provisioning process. The IP addresses are used for BGP peer establishment. For a public virtual circuit, Oracle Cloud Infrastructure chooses the BGP IP addresses.”
Resource: [https://www.oracle.com/cloud/networking/fastconnect-faq.html](https://www.oracle.com/cloud/networking/fastconnect-faq.html)
* **IBM Direct Link**
Quick reference: “Our staff at IBM Cloud assigns a /31 or /30 for each connection and configures an interface IP address on the IBM Cloud cross-connect router (XCR) infrastructure.”
Resource: [https://cloud.ibm.com/docs/direct-link?topic=direct-link-configure-ibm-cloud-direct-link](https://cloud.ibm.com/docs/direct-link?topic=direct-link-configure-ibm-cloud-direct-link)
* **AWS Direct Connect**
Quick reference: “For a private IPv4 VIF, Amazon will provide you a /31 CIDR.
Note: you can use a /31 public CIDR for a Public IPv4 VIF.”
Resource: [https://www.amazonaws.cn/en/directconnect/faqs/](https://www.amazonaws.cn/en/directconnect/faqs/)
* **Alibaba Cloud Express Connect**
You can use a /30 or /31 represented by the subnet mask.
Resource: [Connecting to Alibaba Express Connect](/cloud/megaport/alibaba).
* **Microsoft Azure ExpressRoute**
No support (or plans) for 31-bit subnet masks.
* **Google Partner Interconnect**
Does not currently support the use of 31-bit subnet masks. The mask is fixed and assigned from a 169.254.0.0/16 pool.
* **Megaport Cloud Router**
Supports the use of 31-bit subnet masks on VXCs connected to customer devices, as well as on CSP-facing VXCs where the CSP supports this mask length.
## Background
In December 2000, the Internet Engineering Task Force (IETF) released [RFC 3021](https://tools.ietf.org/html/rfc3021) for using 31-bit prefixes on IPv4 point-to-point links. The RFC investigates changes to the standards to preserve IP address space and reducing the amount of IP addresses assigned to point-to-point links by allowing the use of 31-bit subnet masks.
At that time, the current practice used a 30-bit subnet mask, which required four addresses per point-to-point link: one network address, two hosts addresses, and one broadcast address.
In a point-to-point link, where there can be only two possible identifying hosts and where any packet which is transmitted by one end of the link is always received by the other, using a mask defining four addresses could be seen as a waste in certain situations. This is why the RFC 3021 was developed. Using a 31-bit subnet mask, there are only two possible addresses: a network address and a broadcast address, but in a point-to-point link, these two must be interpreted as host addresses.
And currently, when a company creates a connection to a Cloud Service Provider, the standard practice uses a 30-bit subnet mask to set up BGP peering with the provider. So, with the IP shortage still a current issue, and with many organizations not having enough IP address space, organizations want to use a 31-bit subnet mask address for establishing a BGP peering session with a Cloud Service Provider.
# Insufficient Capacity to Increase Bandwidth for ExpressRoute Circuit
Source: https://docs.megaport.com/troubleshooting/cloud/expressroute-capacity
This help topic helps troubleshoot bandwidth capacity issues with ExpressRoute connections.
## Issue
The customer cannot increase the bandwidth for their ExpressRoute circuit and receives an insufficient capacity error message in the Azure portal.
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
Message
The upgrade from 1000 to 2000 on ExpressRoute circuit:
xxxxxxx did not succeed due to insufficient capacity with Megaport.
No changes have been made to this circuit at this time.
Please work with your service provider to create a new circuit
when capacity becomes available.
```
## Solution
This is a Microsoft Azure issue: Azure has determined that the port for the VXC is full and cannot support the request to increase capacity. (Megaport cannot control the capacity for an Azure interconnect.)
The only option is to create a new VXC at the required speed and Azure will position it on another interconnect that has sufficient capacity.
# Providing Debug Information for Faster Support
Source: https://docs.megaport.com/troubleshooting/debug
This help topic describes the Debug Information page.
The Debug Information page shows detailed information related to your Megaport Portal session. This data is useful for Megaport Support when troubleshooting, and can assist in reproducing the issue.
**To view the Debug Information page**
1. Log in to the Megaport Portal and click the Debug Information icon located in the status bar at the bottom of the screen.
The Debug Information page appears.
2. Click **Copy to Clipboard** and then paste the contents into your email or chat session with Support.
# Troubleshooting a Failure with an Order
Source: https://docs.megaport.com/troubleshooting/errors/automation-fails
This help topic describes what to do if automation fails to provision a service.
If the provisioning status of a service indicates failed, the service could not be deployed through the Megaport automation process and it is not in the deployment queue.
You can verify service status from the Megaport Portal. On the [Services page](/portal-admin/services-page) in the Portal, find the MVE and mouse over its icon. A message displays the status of the service. The color of the icon also indicates the service status.
Additionally, you can verify the provisioning status through the API. Use this endpoint:
```http theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
GET {baseUrl}/v2/product/{productUid}
```
The response includes the status of the service in the `provisioningStatus` field.
## Troubleshooting actions
If you are experiencing an automation failure when trying to provision your service, contact support. The Megaport Network Automation team will investigate and resolve the issue.
If you experience an automation failure, we highly recommend not to deploy additional services, as this can result in more automation failures.
## Next steps
Before contacting support for assistance, collect the following information.
* **Error messages** -- Provide any error messages when provisioning your service.
* **What service were you trying to provision?** -- Provide a breakdown of the service and the steps performed before the automation failure.
* **Is there anything unique to the service you are provisioning?** -- If there is any additional relevant information important to the provisioning of your service that will assist Megaport in troubleshooting the failure, provide as much detail as possible.
# Capacity Error While Provisioning Services
Source: https://docs.megaport.com/troubleshooting/errors/capacity-error
This help topic helps troubleshoot errors that might appear while provisioning a service.
When configuring a service in the Megaport Portal, Megaport API, or Megaport Terraform Provider, an error or API response alerts you that there are no free Ports available at the specified location.
## Troubleshooting action
This error appears if the specified location is already at capacity. To resolve this error, choose another location.
# Troubleshooting IX With a BGP Session Routing Issue
Source: https://docs.megaport.com/troubleshooting/ix/bgp-routing
This help topic describes the troubleshooting steps and actions to take when a BGP session has a routing issue.
When a session on Internet Exchange (IX) is experiencing a routing issue, step through these troubleshooting actions.
Megaport operates a public, web-accessible MegaIX Looking Glass for peers and network operators to investigate the current routing state. You can query the primary and redundant route servers for live BGP data here: [MegaIX Looking Glass](https://lg.megaport.com).
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Verify the BGP configuration** | Check the ASN, BGP IP address, and subnet mask. |
| **Verify access to TCP port 179** | BGP neighbors establish a TCP session using TCP port 179.
Make sure that a BGP neighbor is not blocking ingress or egress from TCP port 179 and other relevant ephemeral ports. You can view the port number using Wireshark, the **debug ip packet detail** command, or **netstat** in Windows.
Make sure that all firewalls and ACLs permit TCP port 179 in both directions.
|
| **Check the BGP neighbor state** | When BGP is configured with a neighbor IP address (route servers, bilateral peers, or both), it goes through several stages before it reaches the Established state. The BGP Neighbor States are Idle, Connect, Active, OpenSent, OpenConfirm, and Established. |
| **Check the BGP message type** | BGP packets use these message types:
**OPEN** -- Sets up and establishes BGP adjacency.
**UPDATE** -- Advertises, updates, or withdraws routes.
**KEEPALIVE** -- Ensures that the BGP neighbor is still alive.
**NOTIFICATION** -- Indicates an error condition to a BGP neighbor.
|
| **Verify the authentication** |
Look through the logs for `Invalid MD5 digest`.
Verify that the correct BGP MD5 password is in use for the and of the VXC.
|
| **Run connectivity tests** |
Run a **** test between the A-End and the B-End PE routers that are connected to route servers to test multilateral peering.
Run a **ping** test between the A-End PE router and the B-End PE router that is connected to bilateral peer to test the bilateral peering.
Ask the customer run a **ping** test from their BGP router to the BGP neighbor IP addresses to test end-to-end connectivity.
Confirm the ARP table entry of the BGP peer.
|
| **Find error conditions in BGP logs** | The BGP protocol sends a notification message when it detects an error with the BGP session such as an expiring hold timer, a change to neighbor capabilities, or a request to reset a BGP session. When an error is detected, the BGP session is closed.
For example, enter **show log %BGP-xxxxx**.
For more information, see [Internet Exchange Overview](/ix). |
## Next steps
If the troubleshooting actions do not resolve your issue, contact support. Before contacting support for assistance, collect the following information:
* All troubleshooting steps taken, in detail. For example, if you place loopbacks, note their location and direction.
* Note the date, time, and time zone in which the issue started.
* Is the BGP session down?
* Is the BGP session flapping? For example, does the peering establish, then drop, re-establish and then drop? Try to pinpoint where the problem might be in the network using **ping**.
* Is there a BGP routing issue?
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
### Collect essential troubleshooting data
**BGP configuration information**
* Interface settings, including number
* BGP IP address and subnet mask
* BGP ASN
* BGP network addresses to be advertised
* BGP neighbor IP address and subnet mask
* BGP neighbor ASN
* BGP neighbor network addresses to be received
* BGP authentication between BGP peers
* BGP route filtering and manipulation (if applicable)
**BGP command output and packet capture information**
* Examine the BGP neighbor table and BGP state using the **show IP BGP summary** command
* Examine the BGP neighbor details using the **show IP BGP neighbors** command
* Logs that show BGP-related messages (output from the **show log %BGP-xxxxx** command)
* BGP routing table entries that have BGP routing issues (output from the **show IP BGP** command)
* BGP advertised routes (output from the **show IP BGP neighbors \ advertised-routes** command)
* BGP received routes (output from the **show IP BGP neighbors \ routes** command)
* Routing table (output from the **show IP route \** command) at both ends
* **** logs between source and destination host
* **Packet capture** logs, if possible (file size can be up to 10 M)
# Troubleshooting IX BGP Session Down
Source: https://docs.megaport.com/troubleshooting/ix/bgp-session
This help topic describes how to identify and solve issues with IX BGP sessions.
If your Internet Exchange (IX) is down, there is likely an issue with your Border Gateway Protocol (BGP) session. Step through these troubleshooting steps to confirm whether your BGP session is the root cause of the IX issues.
Megaport operates a public, web-accessible MegaIX Looking Glass for peers and network operators to investigate the current routing state. You can query both the primary and redundant route servers for live BGP data here: [MegaIX Looking Glass](https://lg.megaport.com).
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Check interface or errors and packet drops on the device** | Interface statistics and logs can help identify which end of the cross connect is causing the fault, and the potential solution. For example, an increasing number of incoming errors on a network interface generally rules out that specific and indicates a potential issue with other components of the IX.
**Important to note**:
**Interface type, SFP type and cable type**
1 Gbps 1000BASE-LX \[10km; duplex on ]
10 Gbps 10GBASE-LR \[10km; duplex on SMOF]
100 Gbps 100GBASE-LR4 \[10km; duplex on SMOF]
**MTU (Maximum Ethernet Frame Size)**
9100 bytes for VXCs between customer Ports.
MCR and MVE support the standard MTU of 1500 bytes.
IX and many CSP ports do not support jumbo frames, but all support the standard MTU of 1500 bytes.
****
Protocol: LACP
Interface: 10GBASE-LR (10 Gbps) or 100GBASE-LR4 (100 Gbps). 1 Gbps Ports are not supported.
The maximum number of interfaces in a single LAG: 8
Multi-Chassis Link Aggregation (MC-LAG) across multiple devices is not supported.
**Preferred A-End VLAN (VXC/IX)**
**Untag (enabled)** -- This will limit the A-End Port to a single service. Only one VXC/IX per Port, equivalent to an access port on your device side.
**Untag (disabled)** -- Specify 802.1q VLAN number on the A-End Port. Each VXC is delivered as a separate VLAN on the Port. This must be a unique VLAN ID on the Port and can range from 2 to 4093. If you specify a VLAN ID already in use, the system displays the following available VLAN number. The system will randomly assign a VLAN number, equivalent to a trunk port with allowed VLANs on your device side, by leaving the VLAN ID blank.
**802.1Q Tunneling () IEEE 802.1ad (Azure VXC)**
To access Microsoft Azure ExpressRoute, Q-in-Q (IEEE 802.1ad) is required. Depending on which method is chosen, your device configurations can vary, either Q-in-Q, Q-in-Q breakout, untagged VXC or MCR.
|
| **Verify interface, SFP, cable and cabling are correct** |
Verify that auto-negotiation (speed auto and duplex auto) is used on gigabit interfaces.
Verify that the cross connect cable is connected to the correct port at both ends.
Verify that SFP optic power levels (Tx and Rx) show good light at both ends.
|
| **Verify configurations** |
Verify that the MTU size is correct.
Verify that the LACP configuration is correct if LAG is used. MC-LAG is not supported.
Verify that your devices are configured as per “Preferred A-End VLAN” on the Megaport Portal.
If a VLAN is used, confirm if the correct VLAN number is configured on your device side.
If Azure VXC is used, verify that your devices are configured using one of the Q-in-Q methods.
|
| **Verify configurations** |
Verify that the interface IP address and subnet address are configured correctly.
Verify that routing protocol configurations (EIGRP/OSPF/BGP) are configured correctly.
Run a **ping** test between Layer 3 network devices (for example, Edge routers, BGP peers).
Run a **ping** test between the source host and destination host (end-to-end connectivity test).
If the **ping** test fails, check the table and routing table at both ends.
If the **ping** test fails and there is no issue on the routing table at both ends, then take **** logs from both ends.
|
| **Verify the optic power levels on the device** | Optic light readings from the terminal help to understand whether the readings are within the threshold range. Check the device and port graphs for errors and view the [Megaport optic graphs history](https://graph.megaport.com/index.pl?page=devices). The graphs update every five minutes, so if flapping is rare, the graphs might not capture a drop in optical light. Ensure the optic reading is within specifications. |
| **Perform a ping test to route servers within the IX network and/or bilateral peers** | A **ping** test transmits data packets to a specific IP address and either confirms or denies there is connectivity between IP-networked devices. A confirmation includes the latency (the response time) of the connection.
|
| **Verify Layer 2 connectivity (ARP) to route servers and/or bilateral peers** | Layer 2 controls the flow of data between nodes on WAN or LAN segments, and is also responsible for detecting and possibly correcting Layer 1 errors. Layer 2 connectivity issues can affect the functionality of your VXCs, which connect to your MCR. When connecting to a [Cloud Service Provider (CSP)](/cloud/megaport), ensure that the VLAN configuration details are correct. Use particular caution when connecting to Azure, as you will be using Q-in-Q.
Layer 2 connectivity issues can also affect your IX services. MAC addresses are used to authenticate your devices when using IX services with Megaport. Depending on your network design, if you are peering with Megaport or other organizations, ensure that you have specified the correct MAC address in the Megaport Portal.
Perform these checks before submitting a support request:
Check the status of your IX service with the [Looking Glass tool](https://lg.megaport.com/Alice). You can access information for both the primary and redundant route servers for live BGP data. Layer 2 issues can be more challenging to diagnose than physical Layer 1 issues. Providing Megaport with Layer 2 connectivity details will help isolate the issue.
If you are not peering directly with Megaport, confirm any configuration changes with the company you are peering with.
Run a **ping** test to verify whether you are connected to Layer 2.
Check the ARP tables and confirm that the MAC address is visible in the Megaport Portal.
Confirm that the configuration matches Megaport [Technical Specifications](/tech-specs).
For additional guidance, reach out to your Account Manager and request a meeting with a Megaport Solution Architect.
|
| **Verify the BGP configuration** |
Interface settings, including VLAN number
BGP IP address and subnet mask
BGP number
BGP network addresses to be advertised
BGP neighbor IP address and subnet mask
BGP neighbor AS number
BGP neighbor network addresses to be received
BGP authentication between BGP peers
BGP route filtering and manipulation, if applicable
|
| **Check for BGP error messages** | The BGP protocol sends a notification message when it detects an error with the BGP session such as an expiring hold timer, a change to neighbor capabilities, or a request to reset a BGP session. When an error is detected, the BGP session is closed.
For example, enter **show log %BGP-xxxxx**.
For more information, see [Internet Exchange Overview](/ix). |
## Next steps
If the troubleshooting actions do not resolve your issue, contact support. Before requesting assistance, collect the following information:
**Troubleshooting results**
* Provide all the troubleshooting steps you have taken in detail. For example, if loops were placed, note their location and which direction they faced.
**Excerpts of network device configurations**
* Interface configurations
* Static routes and routing protocol configurations (EIGRP/OSPF/BGP)
* Firewall rules and ACL configurations for the data flow that has the issue
**BGP command output and packet capture information**
* Routing table (**show IP route \**) at both ends.
* Routing protocol status and the tables at both ends, for example, the BGP neighbor table that shows BGP state (**show ip bgp summary**) and BGP neighbor details (**show ip bgp neighbors \**).
* BGP routing table entries that have BGP routing issues (output from the command **show IP BGP**).
* BGP advertised routes (**show IP BGP neighbors \ advertised-routes**).
* BGP received routes (output from the **show IP BGP neighbors \ routes** command- Routing table (**show IP route \**)).
* **Traceroute** logs between the source and destination host.
* **Packet capture** logs, if possible (file size can be up to 10 M).
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
# Troubleshooting IX Connectivity
Source: https://docs.megaport.com/troubleshooting/ix/connectivity
This help topic describes how to identify and solve issues with IX connectivity.
A loss of connectivity to the IX (Internet Exchange) can be caused by several issues, including a Down status, flapping, , spikes on the network, or a Layer 2 loop.
If an IX is experiencing connectivity issues, step through these troubleshooting actions to identify the possible cause.
Megaport operates a public, web accessible MegaIX Looking Glass for peers and network operators to investigate the current routing state. You can query both the primary and redundant route servers for live BGP data here: [MegaIX Looking Glass](https://lg.megaport.com).
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Check interface or errors and packet drops on the device** | Interface statistics and logs can help identify which end of the cross connect is causing the fault, and the potential solution. For example, an increasing number of incoming errors on a network interface generally rules out that specific transceiver and indicates a potential issue with other components of the IX. |
| **Verify the optic power levels on the device** | Optic light readings from the terminal help to understand whether the readings are within the threshold range. Check the device and port graphs for errors and view the optic graphs for the history. |
| **Perform a test to route servers and/or bilateral peers** | A **ping** test confirmation includes the latency (the response time) of the connection. Provide the output of **ping** tests from the customer IX service IP to the following destinations:
Route servers in the IX network
Bilateral peers
|
| **Verify Layer 2 connectivity to route servers and/or bilateral peers** | controls the flow of data between nodes on WAN or LAN segments, and is also responsible for detecting and possibly correcting errors. Layer 2 connectivity issues can affect the functionality of your VXCs. When connecting to a [Cloud Service Provider (CSP)](/cloud/megaport), ensure that the VLAN configuration details are correct. Use particular caution when connecting to Azure, as you will be using .
Layer 2 connectivity issues can also affect your IX services. MAC addresses are used to authenticate your devices when using IX services with Megaport. Depending on your network design, if you are with Megaport or other organizations, ensure that you have specified the correct MAC address in the Megaport Portal.
Perform these checks before submitting a support request:
Check the status of your IX service with the [MegaIX Looking Glass](https://lg.megaport.com/Alice). You can access information for both the primary and redundant route servers for live BGP data. Layer 2 issues can be more challenging to diagnose than physical Layer 1 issues. Providing Megaport with Layer 2 connectivity details will help isolate the issue.
If you are not peering directly with Megaport, confirm any configuration changes with the company you are peering with.
Run a **ping** test to verify whether you are connected to Layer 2.
Check the ARP tables and confirm that the MAC address is visible in the Megaport Portal.
Confirm that the configuration matches Megaport [Technical Specifications](/tech-specs).
For additional guidance, reach out to your Account Manager and request a meeting with a Megaport Solution Architect.
|
## Next steps
If the troubleshooting actions do not resolve your issue, contact support. Before requesting assistance, collect the following information.
* **Troubleshooting results** -- Provide all the troubleshooting steps you have taken in detail. For example, if loops were placed, note their location and which direction they faced.
* **Ping test results** -- Provide the output of each **ping** test from the customer IX service IP address to the following destinations:
* Route servers in the IX network
* Bilateral peers
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
# Creating Private Megaport Connections for Juniper MX and EX Devices
Source: https://docs.megaport.com/troubleshooting/juniper/index
This help topic describes how to create a private connection between a Juniper MX device and a Juniper EX device on the Megaport network.
This topic describes how to create a private point-to-point connection between a Juniper MX device and a Juniper EX device on the Megaport network.
## Topology
## Prerequisites
Before proceeding, ensure you have the following:
* A Port established in two locations with a *Live* status, connected with fully deployed Virtual Cross Connects (VXCs).
If you haven't already created a Port, see
[Creating a Port](/connections/creating-port).
* Layer 2 or Layer 3 switches on each end terminating the physical connections.
* 802.1q trunking enabled on the two links connecting into Megaport.
## Deploying a private VXC
This section describes the configuration process on the Megaport side, using the Megaport Portal.
**To deploy a private VXC**
1. In the Megaport Portal, go to the **Services** page and select the originating A-End Port.
2. Click **+Connection**.
3. Click **Private VXC**.
4. Select the target Port (the B-End).
5. Click **Next**.
6. Specify the connection details:
* **Connection Name** -- The name of your VXC to be shown in the Megaport Portal. Specify a name for the VXC that is easily identifiable. You can change the name later, if you like.
* **Service Level Reference** (optional) -- Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
* **Rate Limit** -- The speed of your connection in Mbps. The maximum speed is displayed. The maximum speed available is limited to the smallest of the originating or destination port.
* **VXC State** -- Select **Enabled** or **Shut Down** to define the initial state of the connection. For more information, see [Shutting Down a VXC for Failover Testing](/connections/shut-down-vxc).
If you select **Shut Down**, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
* **Preferred A-End VLAN** -- Specify the 802.1q VLAN tag for this connection that you will receive via the A-End VLAN.
* **Preferred B-End VLAN** -- Specify the 802.1q VLAN tag for this connection that you will receive via the B-End VLAN.
The VLAN tags on each end do not have to be the same. This example uses VLAN 3000 on each end of the transport connection between Dallas and Seattle.
* **Minimum Term** -- Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. *12 Months* is selected by default. Take note of the information on the screen to avoid early termination fees (ETF).
Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don't renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts.
For more information, see [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
* **Resource Tags** -- You can use resource tags to add your own reference metadata to a Megaport service.\
To add a tag:
1. Click **Add Tags**.
2. Click **Add New Tag**.
3. Enter details into the fields:
* **Key** -- String, maximum length 128 characters. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- String, maximum length 256 characters. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
4. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
7. Click **Add VXC** to save the VXC.
8. Click **Review Order** and proceed through the ordering process.
When the VXC is deployed, you can view it in the Portal Services page.
Now that the Megaport side of the configuration is complete, you need to configure the Juniper devices on each end of the circuit.
## Configuring the Juniper devices on each end of the circuit
The example uses a supported maximum transmission unit (MTU) of 9100 on the trunk port. MTU is optional. See the results of different MTU settings in [Testing the MTU Settings](#testmtu).
**To configure the Juniper devices**
1. Configure the Juniper MX80 router located in Dallas like this:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
set bridge-domains VL-3000-DAL-SEA vlan-id 3000
set interfaces xe-1/1/0 description "MP1-10G L2 Port"
set interfaces xe-1/1/0 vlan-tagging
set interfaces xe-1/1/0 mtu 9100
set interfaces xe-1/1/0 unit 3000 description MP-DAL-SEA
set interfaces xe-1/1/0 unit 3000 vlan-id 3000
set interfaces xe-1/1/0 unit 3000 family inet address 10.10.1.1/30
```
2. Configure the Juniper EX4600 device located in Seattle like this:
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
set vlans VL-3000-DAL-SEA vlan-id 3000
set interfaces xe-0/0/46 description "Megaport SEA-10G"
set interfaces xe-0/0/46 vlan-tagging
set interfaces xe-0/0/46 mtu 9100
set interfaces xe-0/0/46 unit 3000 description MP-DAL-SEA
set interfaces xe-0/0/46 unit 3000 vlan-id 3000
set interfaces xe-0/0/46 unit 3000 family inet address 10.10.1.2/30
```
## Testing the MTU settings - Dallas to Seattle
This section shows how different MTU settings work on the configuration from Dallas to Seattle.
### Using 9100 MTU
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
maverick@BB1-EQ# run ping 10.10.1.2 size 9100 do-not-fragment
PING 10.10.1.2 (10.10.1.2): 9100 data bytes
ping: sendto: Message too long
ping: sendto: Message too long
ping: sendto: Message too long
ping: sendto: Message too long
^C
--- 10.10.1.2 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
```
### Using 9055 MTU
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
maverick@BB1-EQ# run ping 10.10.1.2 size 9055 do-not-fragment
PING 10.10.1.2 (10.10.1.2): 9055 data bytes
ping: sendto: Message too long
ping: sendto: Message too long
ping: sendto: Message too long
ping: sendto: Message too long
^C
--- 10.10.1.2 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
```
### Using 9054 MTU: Success
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
maverick@BB1-EQ# run ping 10.10.1.2 size 9054 do-not-fragment
PING 10.10.1.2 (10.10.1.2): 9054 data bytes
9062 bytes from 10.10.1.2: icmp_seq=0 ttl=64 time=60.443 ms
9062 bytes from 10.10.1.2: icmp_seq=1 ttl=64 time=62.667 ms
9062 bytes from 10.10.1.2: icmp_seq=2 ttl=64 time=57.640 ms
9062 bytes from 10.10.1.2: icmp_seq=3 ttl=64 time=65.529 ms
9062 bytes from 10.10.1.2: icmp_seq=4 ttl=64 time=67.623 ms
^C
--- 10.10.1.2 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 57.640/64.212/71.371/4.553 ms
```
## Testing the MTU settings - Seattle to Dallas
This section shows how different MTU settings work on the configuration from Seattle to Dallas.
### Using 9100 MTU
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
maverick@BB1-EQ# run ping 10.10.1.2 size 9100 do-not-fragment
PING 10.10.1.2 (10.10.1.2): 9100 data bytes
ping: sendto: Message too long
ping: sendto: Message too long
ping: sendto: Message too long
ping: sendto: Message too long
^C
--- 10.10.1.2 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
```
### Using 9055 MTU
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
maverick@BB1-EQ# run ping 10.10.1.2 size 9055 do-not-fragment
PING 10.10.1.2 (10.10.1.2): 9055 data bytes
ping: sendto: Message too long
ping: sendto: Message too long
^C
--- 10.10.1.2 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
```
### Using 9054 MTU: Success
```text theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
maverick@BB1-EQ# run ping 10.10.1.2 size 9054 do-not-fragment
PING 10.10.1.2 (10.10.1.2): 9054 data bytes
9062 bytes from 10.10.1.2: icmp_seq=0 ttl=64 time=60.443 ms
9062 bytes from 10.10.1.2: icmp_seq=1 ttl=64 time=62.667 ms
9062 bytes from 10.10.1.2: icmp_seq=2 ttl=64 time=57.640 ms
9062 bytes from 10.10.1.2: icmp_seq=3 ttl=64 time=65.529 ms
9062 bytes from 10.10.1.2: icmp_seq=4 ttl=64 time=67.623 ms
^C
--- 10.10.1.2 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 57.640/64.212/71.371/4.553 ms
```
# Troubleshooting MCR When a BGP Session is Down
Source: https://docs.megaport.com/troubleshooting/mcr/bgp
This help topic describes the troubleshooting steps and actions to take when a BGP session is down on MCR.
When a BGP session on Megaport Cloud Router (MCR) is down, step through these troubleshooting actions.
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Verify the configuration** | Check the , BGP IP address, and subnet mask:
Select the MCR.
Select the VXC and select the MCR or .
Under BGP Connections, verify that the correct local ASN is in use for the A-End of the VXC.
Verify that the correct peer IP address is in use.
|
| **Verify access to TCP port 179** | establish a TCP session using TCP port 179.
Make sure that a BGP neighbor is not blocking ingress or egress from TCP port 179 and other relevant ephemeral ports. You can view the port number using Wireshark, **debug ip packet detail** command, **netstat** in Windows.
Make sure that all firewalls and permit TCP port 179 in both directions.
|
| **Verify the route filtering** | The MCR Looking Glass displays the routes received or sent after applying route filtering. For more information, see [Viewing Traffic Routing Through MCR Looking Glass](/mcr/mcr-looking-glass).
Choose Tools > MCR/NAT Gateway Looking Glass.
Select an MCR from the MCR drop-down list.
Next to the VXC, click **Neighbour Routes**.
After Show, select the Advertised or Received tabs to narrow the list.
|
| **Check the BGP neighbor state** | When BGP is configured with a neighbor IP address, it goes through several stages before it reaches the Established state. The BGP Neighbor States are Idle, Connect, Active, OpenSent, OpenConfirm, and Established. |
| **Check the BGP message type** | BGP packets use these message types:
**OPEN** -- Sets up and establishes BGP adjacency.
**UPDATE** -- Advertises, updates, or withdraws routes.
**KEEPALIVE** -- Ensures that the BGP neighbor is still alive.
**NOTIFICATION** -- Indicates an error condition to a BGP neighbor.
|
| **Verify the authentication** |
Look through the logs for `Invalid MD5 digest`.
Verify that the correct BGP MD5 password is in use for the A-End and B-End of the VXC.
|
| **Run connectivity tests** |
Run a **ping** test between BGP peers.
Confirm the table entry of the BGP peer.
|
| **Find error conditions in BGP logs** | The BGP protocol sends a notification message when it detects an error with the BGP session such as: an expiring hold timer, a change to neighbor capabilities, or a request to reset a BGP session. When an error is detected, the BGP session is closed.
For example, enter **show log %BGP-xxxxx** |
## Next steps
If the troubleshooting actions do not resolve your issue, contact support. Before contacting support for assistance, collect the following information.
* Note the date, time, and time zone in which the issue started.
* Is the BGP session down?
* Is the BGP session flapping? For example, does the peering establish, then drop, re-establish, and then drop? Try to pinpoint where the problem might be in the network using **ping**.
* Is there a BGP routing issue?
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
### Collect essential troubleshooting data
**BGP configuration information**
* Interface settings, including VLAN number
* BGP IP address and subnet mask
* BGP ASN
* BGP network addresses to be advertised
* BGP neighbor IP address and subnet mask
* BGP neighbor ASN
* BGP neighbor network addresses to be received
* BGP authentication between BGP peers
* BGP route filtering and manipulation, if any
**BGP command output and packet capture information**
* Examine the BGP neighbor table and BGP state using the **show IP BGP summary** command
* Examine the BGP neighbor details using the **show IP BGP neighbors** command
* Logs that show BGP-related messages (output from the **show log %BGP-xxxxx** command)
* BGP routing table entries that have BGP routing issues (output from the **show IP BGP** command)
* BGP advertised routes (output from the **show IP BGP neighbors \ advertised-routes** command)
* BGP received routes (output from the **show IP BGP neighbors \ routes** command)
* Routing table (output from the **show IP route \** command)
* **Traceroute** logs between source and destination host
* **Packet capture** logs, if possible (file size can be up to 10 M)
# Troubleshooting MCR When Down or Unavailable
Source: https://docs.megaport.com/troubleshooting/mcr/down
This help topic describes troubleshooting steps to identify and solve problems when MCR is down.
If your Megaport Cloud Router (MCR) is down, the root cause could be the status of your attached Ports or VXCs, the BGP configuration, or the interface settings. Step through these troubleshooting actions to isolate the issue.
You can verify MCR status from the Megaport Portal. On the [Services page](/portal-admin/services-page) in the Portal, find the MCR and mouse over its icon. A message displays the status of the service. The color of the icon also indicates the service status.
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Perform a ping test to the MCR** | Although the MCR cannot initiate **** tests internally, you can verify connectivity by running ping tests to the MCR from devices connected at . For example, if one of the MCR interfaces is set with IP address 172.16.100.2 with subnet mask 30, run the **ping** test from the connected device with IP address 172.16.100.1.
A successful **ping** test confirms basic connectivity and shows the latency (response time). |
| **Verify Layer 2 connectivity (ARP)** | Confirm that the IP address of the MCR is mapped correctly to the MAC address in the table. For example, enter **show ip arp**. Layer 2 controls the flow of data between nodes on WAN or LAN segments, and is also responsible for detecting and possibly correcting errors. connectivity issues can affect the functionality of your VXCs, which connect to your MCR. When connecting to a [Cloud Service Provider (CSP)](/cloud/megaport), ensure that the VLAN configuration details are correct. Use particular caution when connecting to Azure, as you will be using . For additional guidance, contact your Account Manager and request a meeting with a Megaport Solution Architect. |
| **Verify ACL/FW rules on your devices** | During some troubleshooting sessions where the circuit is up but you cannot **ping** between Layer 3 endpoints, there might be a firewall or in between.
On many devices, it is possible to set an interface to filter or ignore ICMP requests on many devices, leading to a failed **ping**, while other traffic might pass without problems. It is essential to know the **ping source**, its destination, the path, and any intermediate devices it traverses. Megaport requires customers to provide a network diagram and the **** result before investigation and troubleshooting. Inaccurate information might lead to wrong troubleshooting results and inappropriate solutions.
Perform these checks before opening a ticket with Megaport support:
Ensure the source device is sending the **ping** packets by examining the egress interface/subinterface.
Ensure the destination device is receiving the **ping** packets by reading the ingress interface/subinterface.
Perform a **traceroute** and find the hop where the traceroute starts to time out. Examine the configuration on the hop.
|
## Next steps
If the troubleshooting actions do not resolve your issue, contact support. Before contacting support for assistance, provide details of all troubleshooting steps. For example, if loops were placed, note where they were located and their direction.
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
# Troubleshooting MCR With Other Issues
Source: https://docs.megaport.com/troubleshooting/mcr/other
This help topic describes troubleshooting steps to identify and solve problems when MCR has issues not covered in previous troubleshooting topics.
If your MCR is experiencing issues other than those covered in previous troubleshooting topics, step through these troubleshooting actions.
You can verify MCR status from the Megaport Portal. On the [Services page](/portal-admin/services-page) in the Portal, find the MCR and mouse over its icon. A message displays the status of the service. The color of the icon also indicates the service status.
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Check Network Address Translation (NAT) filters** | Review your filters to ensure that they are preventing incoming traffic from interfering with your internet and network. Ensure that NAT filtering is active on your routers. For more information, see [How MCR Performs NAT](/mcr/mcr-nat). |
| **Check route filters** | Ensure your route filters are working as expected. Route filtering provides selective control over which networks are discoverable between Border Gateway Protocol (BGP) neighbor routers. Route filtering is configured to influence the routing path and manage redundancy while improving security. For more information, see [MCR Route Filtering](/mcr/route-filtering). |
| **Verify MCR settings from the Megaport Portal** | Verify your MCR settings from the Megaport Portal. For more information, see the How to Check MCR Settings video above. |
## Next steps
If the troubleshooting actions do not resolve your issue, contact support. Before contacting support for assistance, collect the details of all troubleshooting steps. For example, if loopbacks were placed, note where they were located and their direction.
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
# Troubleshooting an MCR Routing Issue
Source: https://docs.megaport.com/troubleshooting/mcr/routing
This help topic describes the troubleshooting steps and actions to take when a MCR is experiencing a routing issue.
When Megaport Cloud Router (MCR) is experiencing a routing issue, step through these troubleshooting actions.
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Perform a test between the source and destination** | A **ping** test transmits data packets to a specific IP address and either confirms or denies connectivity between IP-networked devices. In the case of confirmation, a **ping** test shows the latency (the response time) of the connection. Provide the IP address and the subnet mask of services on the Megaport end used for the **ping** test. |
| **Perform a test between the source and destination** | **Traceroute** testing can help to determine if a destination is reachable. **Traceroute** sends a sequence of packets between two points and shows you the route the packets take. **Traceroute** also measures the transit delays of packets across an IP network. From the host that is originating traffic (A-End), start the **traceroute** to the destination host. Then run the **traceroute** from the destination host (B-End) to the origin host. Commands and flags might differ by device.
**Analyze the results**
Look for asymmetric routing. If the traffic is not taking the same path, there might be asymmetric routing somewhere in the network.
Are there any places in the **traceroute** where the response time has increased markedly? If so, are those delays within your network?
Are there any firewalls or access list rules prohibiting traffic from reaching its destination?
|
| **Verify routing configurations and routing tables** |
Confirm both Layer 2 and Layer 3 configurations.
Review metrics, route filters, firewalls, and traffic shaping.
Verify the routing table (Layer 3) and confirm whether the prefix in question is reachable and on the expected routing path to Megaport.
Confirm that the gateway (the device facing the MCR) is advertising the required prefix if a route filter is in place.
Confirm the MCR routing table: [Viewing Traffic Routing Through MCR Looking Glass](/mcr/mcr-looking-glass).
|
## Ping and traceroute
Megaport provides standard network diagnostic tools, such as ping and traceroute, directly from an MCR.
You can run diagnostic requests via the Megaport Portal or the Megaport API. After the tests are complete, the real-time results are retrieved and displayed in the Portal.
* Diagnostic requests (ping or traceroute) are initiated against a specified MCR.
* The destination must be a valid IPv4 or IPv6 address.
* The source must be a valid IPv4 or IPv6 address that is configured on the MCR interface.
* You cannot cancel a running diagnostic request. The request must complete or naturally time out, then return the result before the next request will run.
**To run a ping test**
Ping is available only on MCR with at least one active VXC connection.
1. Log in to the Megaport Portal and choose **Services**.
2. Click the Service Diagnostics icon or the Looking Glass icon.
3. Click the **Ping** tab.
4. Type the destination IP into the **Destination IP** field, then click **Run Ping**.\
Latency results are returned.
**To run a traceroute test**
Traceroute is available only on MCR with at least one active VXC connection.
1. Log in to the Megaport Portal and choose **Services**.
2. Click the Service Diagnostics icon or the Looking Glass icon.
3. Click the **Traceroute** tab.
4. Type the destination IP into the **Destination IP** field, then click **Run Traceroute**.\
Packet routing and transit delay results are returned.
### Ping and traceroute specifications
Ping and traceroute tests from an MCR are subject to certain limits and specifications. For more information, see [Megaport Cloud Router (MCR)](/limits-quotas#mcr).
## Next steps
If the troubleshooting actions do not resolve your issue, contact support. Before contacting support for assistance, collect the following information.
* **Troubleshooting results** -- Provide all troubleshooting steps taken in detail.
* **General details** -- The date, time, and time zone in which the issue started.
* **Loopback details** -- If you placed loopbacks, note their location and direction.
* **Interface and BGP configurations on the customer device/Cloud Service Provider side**
* Provide the interface settings, including the VLAN number.
* Provide any static routes and routing protocol configurations (EIGRP/OSPF/BGP).
* Provide the BGP ASN.
* Provide all firewall rules and ACL configurations for the data flow experiencing the issue.
* **Source and destination IP addresses**
* Provide the **IP packet** field containing the IP address of the originating device.
* Provide the **IP packet** field containing the IP address of the destination device.
* **High-level network diagram** -- Understanding how your network design is implemented and the connection into the Megaport network helps identify additional focus areas within the troubleshooting process. Provide a network diagram that includes all devices in the path; note each device’s involved IP addresses and VLANs.
* **Ping test results** -- Provide the output of each **ping** test performed on the service. Provide output tests for all services related to different products (Port, VXC, MCR).
* **Traceroute test results** -- Provide **traceroute** results indicating which side of the connection initiated the test and which side was the destination. We recommend using the A-End and B-End information from your VXC.
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
# Troubleshooting the Megaport Terraform Provider
Source: https://docs.megaport.com/troubleshooting/megaport-terraform-provider/index
This help topic describes troubleshooting steps to identify and solve problems when using the Megaport Terraform Provider.
If you encounter problems with the Megaport Terraform Provider, step through these troubleshooting actions.
For information about troubleshooting API issues, see [Troubleshooting the API](/troubleshooting/api).
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Ensure you are using the latest version of Terraform and the Megaport Terraform Provider** | Make sure you are using a supported version of Terraform and the latest version of the Megaport Terraform Provider, as indicated in the [Megaport Terraform Provider Registry](https://registry.terraform.io/providers/megaport/megaport/latest/). Megaport tests against the two latest major versions of Terraform.
To check both, run the command:
`terraform version`
which should output the version information like this:
You can update Terraform by downloading from [Upgrading Guides (HashiCorp)](https://developer.hashicorp.com/terraform/language/upgrade-guides).
The version of the Megaport Terraform Provider is what you declare when you create the provider in the Terraform file. For more information, see [Creating a Megaport Terraform Provider Configuration File](/terraform/megaport-terraform-configuration). |
| **Resolve Azure VXC deletion error** | Deleting an Azure VXC leads to the error:
`Error: Error deleting resource ****: has an attached peering connection that must be removed in Azure first:`
To resolve this issue, the ExpressRoute peering should be managed using the Azure Terraform provider instead and it will then be torn down before the VXC. For more information, see [the Azure provider documentation](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/express_route_circuit_peering). |
| **Resolve VXC being deleted issue when associated service is deleted** | The provider does not handle the situation when a Port is recreated, which then deletes the Port and its associated VXCs.
For example, if you had a Terraform file with a Port with a speed of 1000:
and wanted to update the port\_2 speed to 10000, it will trigger the Port to be recreated, which will first delete the Port and its associated VXCs. The provider does not currently handle this and will return an error like this:
` Error: Error Updating VXC` `Could not update VXC with ID a7b44cda-28bc-4d64-b05b-8703114a8fcd: PUT https://api-staging.megaport.com/v3/product/vxc/a7b44cda-28bc-4d64-b05b-8703114a8fcd: 400 (trace_id "89b4016d9f9d0b7545987092d0b17493") Product [a7b44cda-28bc-4d64-b05b-8703114a8fcd] Not Found`
To resolve this, you can specify a lifecycle modifier to the Port resource like below, which will first create the new Port, perform the update on the VXC, then delete the old Port.
`lifecycle \{` `create_before_destroy = true` `}` |
| **Report the provider error message** | If you see the following error message, it indicates a problem with the provider. [Contact support](/support/contact) or [create a GitHub issue](https://github.com/megaport/terraform-provider-megaport/issues) and include details of the process that caused it, to have this error recorded and investigated.
`"This is a bug in the provider, which should be reported in the provider's own issue tracker."` |
# Troubleshooting Megaport Internet Connectivity
Source: https://docs.megaport.com/troubleshooting/mic/megaport-internet
This help topic describes troubleshooting steps to identify and solve problems when a Megaport Internet connection does not have connectivity.
A Megaport Internet connection is required for MVE provisioning, and can also be created for Ports and MCRs. If your Megaport Internet connection cannot access the internet, step through these specific and general troubleshooting actions.
For more information, see [Megaport Internet Routing Guide](/megaport-internet/routing).
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **BGP-enabled Megaport Internet - Review the advertised routes checklist** | Confirm the following:
BGP ASN (public or private) has been provided.
Route objects have been created in the appropriate RIR or RADb for all advertised networks.
For private ASNs or statically routed networks, AS49915 is used as the origin.
Networks can be checked using tools such as [BGP Tools](https://bgp.tools) by searching for the IP network and verifying that the **Validation** tab shows IRR database entries matching the provided ASN.
A Letter of Authorization (LOA) has been provided for public IPs, confirming the IP range and ASN match the LOA.
Upstream filters have been accounted for, with the understanding that they might take up to 48 hours to propagate after service configuration.
|
| **BGP-enabled Megaport Internet - Check maximum prefixes have not been reached** | If the prefix limit is exceeded, the BGP peer will shut down and not re-enable for 45 minutes. To check the maximum prefixes are not reached:
Review the internet VXC logs to confirm whether the maximum number of prefixes has been reached.
Review and update the BGP export filters to reduce the number of prefixes.
|
| **Verify MVE/SD-WAN configurations** | Where the Megaport Internet connection is being used with an MVE, confirm this information:
Ensure SD-WAN login credentials are accurate.
Ensure the MVE has has the correct license and template/workflow.
Verify the instance size and software version.
Verify the MVE interface status, including configuration values for IP addresses and subnets, VLAN, bandwidth, and ASNs.
For gateway and interconnect connectivity, check sessions, bandwidth, BGP status, and BGP neighbor status.
For more information about Megaport SD-WAN providers, see [MVE Overview](/mve). |
| **Verify MVE Public IP Address, Gateway IP Address in Megaport Internet connection details** | Each MVE is assigned a public IP address by a Megaport configured DHCP server. To check the assigned IP address:
In the Megaport Portal, go to the **Services** page and locate your target MVE.
Click the gear icon next to the Megaport Internet connection and the public IP address assigned to the MVE appears.
|
| **Ping tests from MVE** | Run **** tests from MVE to the following destinations:
MVE default gateway IP address
SD-WAN management server/controller
Public IP (for example, ns1.google.com, 8.8.8.8)
A **ping** test transmits data packets to a specific IP address and either confirms or denies connectivity between IP-networked devices. In the case of confirmation, a **ping** test shows the latency (the response time) of the connection.
If you need to contact Support about this issue, provide the results from the **ping** tests. |
| **General troubleshooting tips** | For any service that has a Megaport Internet connection, perform these troubleshooting steps:
Try pinging the /31 address from anywhere to see if you receive a response.
Check the Transit router and make sure it's online.
|
## Next steps
If the troubleshooting actions do not resolve your issue, contact support.
Before contacting support for assistance, collect the following information.
* Provide details of all troubleshooting steps.\
For example, if you set up loops, note where they were located and their direction. If you ran **ping** tests, provide the output.
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
# Troubleshooting MVE When Down or Unavailable
Source: https://docs.megaport.com/troubleshooting/mve/down
This help topic describes troubleshooting steps to identify and solve problems when an MVE is down.
If your MVE is down or unavailable, step through these troubleshooting actions.
You can verify MVE status from the Megaport Portal. On the [Services page](/portal-admin/services-page) in the Portal, find the MVE and mouse over its icon. A message displays the status of the service. The color of the icon also indicates the service status.
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Ping test to MVE** | Run **** tests from MVE to the following destinations:
MVE default gateway IP address
SD-WAN management server/controller
Public IP (for example, ns1.google.com, 8.8.8.8)
A **ping** test transmits data packets to a specific IP address and either confirms or denies connectivity between IP-networked devices. In the case of confirmation, a **ping** test shows the latency (the response time) of the connection. |
| **Verify MVE remote access configurations** |
Check if MVE status is reachable/up in the SD-WAN management controller
Check if MVE status is up in the Megaport Portal
Check if SSH works
Check configurations for different vendors for further troubleshooting
|
| **Verify a [Cisco configuration](/mve/cisco/creating/creating-mve)** | **Check if Megaport API call communication is allowed** The Cisco vManage console uses Megaport API calls to synchronize and authenticate the MVE. If you use a vManage console that does not allow this API call, for example, an on-premises vManage, you might need to open ports on the customer firewall protecting the on-premises vManage. For more information, see [Firewall Ports for Cisco SD-WAN Deployments.](https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/sdwan-xe-gs-book/cisco-sd-wan-overlay-network-bringup.html#c_Firewall_Ports_for_Viptela_Deployments_8690.xml)
**Ensure internet access is granted (vManage)** For an edge device to come online, it needs internet access through the Transport & Management VPN.
To check the configuration details in vManage:
Go to Configuration > Templates and click Feature.
Find the template you’ve applied (created as a Cisco VPN Interface Ethernet type).
Click the ellipsis (...) on the far right and choose either View or Edit to review the details.
|
| **Verify a [Fortinet configuration](/mve/fortinet/creating-mve)** | **Ensure SSH access is granted** Try to connect using SSH to the Fortinet MVE instance using the private key generated when ordering and the public IP address assigned by Megaport. The default username is `admin`.
For example: `ssh -i ~/.ssh/mp1-mve-sa-sandbox admin@162.43.xx.x`
Note the key pasted in the Megaport Portal is the public key and the key used for SSH is the private one. If you cannot connect with SSH to the MVE while the VM is up, you might need to delete and re-generate the MVE.
**Ensure HTTPS access is allowed** Self-hosted web access to the FortiGate is delivered through a secure HTTPS session. The MVE blocks all access to the public IP addresses assigned to the device until you SSH into it and grant HTTPS access.
You can verify if access is allowed with the following command: `show system interface` |
| **Verify a [Versa configuration](/mve/versa/creating-mve)** | Verify the remote access configuration in Versa Director:
Select the **Configuration** tab in the top menu bar.
Select Templates > Device Templates in the horizontal menu bar.
Find your device template and click View.
In the details, you can review the configuration, including if SSH is enabled. |
| **Verify a [VMware configuration](/mve/vmware/creating-mve)** | Verify the device configuration is correct in Orchestrator:
Go to Configure > Profiles and select the applied configuration profile.
Select the **Device** tab.
Ensure Cloud VPN is enabled.
Ensure only the device type for **Virtual Edge** is selected.
In Interface Settings, ensure GE1 and GE2 are disabled.
Select the **Firewall** tab.
Ensure Support Access and Local Web UI Access from specific IP addresses are allowed. (This will also help with potential troubleshooting.) |
| **Verify ACL/FW rules on customer devices** | During some troubleshooting sessions where the circuit is up but you cannot ping between endpoints, there might be a firewall or ACL in between.
It is essential to know the source of the ping and its destination and the path, and any intermediate devices it traverses. Megaport will require a network diagram and the traceroute result before investigation and troubleshooting. Inaccurate information might lead to wrong troubleshooting results and inappropriate solutions.
Perform these checks before submitting a support request:
Ensure the source device is sending the ping packets by examining the egress interface/subinterface
Ensure the destination device is receiving the ping packets by reading the ingress interface/subinterface
Perform a traceroute and find the hop where the traceroute starts to time out. Examine the configuration on the hop.
On many devices, it is possible to set an interface to filter or ignore ICMP requests, leading to a failed ping, while other traffic might pass without problems. |
## Next steps
If the troubleshooting actions do not resolve your issue, contact support.
Before contacting support for assistance, collect the following information.
* Provide details of all troubleshooting steps.\
For example, if loops were placed, note where they were located and their direction.
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
# Troubleshooting MVE Connectivity
Source: https://docs.megaport.com/troubleshooting/mve/internet
This help topic describes troubleshooting steps to identify and solve problems when an MVE does not have connectivity.
If your MVE cannot access the internet, step through these troubleshooting actions.
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Verify MVE/SD-WAN configurations** | Confirm this information:
Ensure SD-WAN login credentials are accurate.
Ensure the MVE has has the correct license and template/workflow.
Verify the instance size and software version.
Verify the MVE interface status, including configuration values for IP addresses and subnets, VLAN, bandwidth, and ASNs.
For gateway and interconnect connectivity, check sessions, bandwidth, BGP status, and BGP neighbor status.
For more information about Megaport SD-WAN providers, see [MVE Overview](/mve). |
| **Verify MVE Public IP Address, Gateway IP Address in Megaport Internet connection details** | Each MVE is assigned a public IP address by a Megaport configured DHCP server. To check the assigned IP address:
From the Megaport Portal, go to the **Services** page and locate your target MVE.
Click the gear icon next to the Megaport Internet connection and the public IP address assigned to the MVE appears.
|
| **Ping tests from MVE** | Run **** tests from MVE to the following destinations:
MVE default gateway IP address
SD-WAN management server/controller
Public IP (for example, ns1.google.com, 8.8.8.8)
A **ping** test transmits data packets to a specific IP address and either confirms or denies connectivity between IP-networked devices. In the case of confirmation, a **ping** test shows the latency (the response time) of the connection.
If you need to contact Support about this issue, provide the results from the **ping** tests. |
## Next steps
If the troubleshooting actions do not resolve your issue, contact support.
Before contacting support for assistance, collect the following information.
* Provide details of all troubleshooting steps.\
For example, if you set up loops, note where they were located and their direction. If you ran **ping** tests, provide the output.
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
# Troubleshooting MVE Connectivity to SD-WAN Management
Source: https://docs.megaport.com/troubleshooting/mve/sd-wan-manager
This help topic describes troubleshooting steps to identify and solve problems when an MVE has trouble connecting to SD-WAN management components.
Step through these troubleshooting actions to review, investigate, and confirm the SD-WAN configuration and components.
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Verify MVE/SD-WAN configurations** | Confirm this information:
Ensure SD-WAN login credentials are accurate.
Ensure the MVE has has the correct license and template/workflow.
Verify the instance size and software version.
Verify the MVE interface status, including configuration values for IP addresses and subnets, VLAN, bandwidth, and ASNs.
For gateway and interconnect connectivity, check sessions, bandwidth, BGP status, and BGP neighbor status.
For more information about Megaport SD-WAN providers, see [MVE Overview](/mve). |
| **Verify MVE public IP address and gateway IP address in connection details** | Each MVE is assigned a public IP address by a Megaport configured DHCP server. To check the assigned IP address:
From the Megaport Portal, go to the **Services** page and locate your target MVE.
Click the gear icon next to the Megaport Internet connection and locate the public IP address assigned to the MVE.
|
| **Ping tests from MVE** | Run **** tests from MVE to the following destinations:
MVE default gateway IP address
SD-WAN management server/controller
Public IP (for example, ns1.google.com, 8.8.8.8)
A **ping** test transmits data packets to a specific IP address and either confirms or denies connectivity between IP-networked devices. In the case of confirmation, a **ping** test shows the latency (the response time) of the connection.
If you need to contact Support about this issue, provide the results from the **ping** tests. |
## Next steps
If the troubleshooting actions do not resolve your issue, contact support.
Before contacting support for assistance, collect the following information.
* Provide details of all troubleshooting steps.\
For example, if you set up loops, note where they were located and their direction. If you ran **ping** tests, provide the output.
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
# Troubleshooting a NAT Gateway Routing Issue
Source: https://docs.megaport.com/troubleshooting/nat/routing
This help topic describes the troubleshooting steps and actions to take when a NAT Gateway is experiencing a routing issue.
When Megaport NAT Gateway (NAT Gateway) is experiencing a routing issue, step through these troubleshooting actions.
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Perform a test between the source and destination** | A **ping** test transmits data packets to a specific IP address and either confirms or denies connectivity between IP-networked devices. In the case of confirmation, a **ping** test shows the latency (the response time) of the connection. Provide the IP address and the subnet mask of services on the Megaport end used for the **ping** test. |
| **Perform a test between the source and destination** | **Traceroute** testing can help to determine if a destination is reachable. **Traceroute** sends a sequence of packets between two points and shows you the route the packets take. **Traceroute** also measures the transit delays of packets across an IP network. From the host that is originating traffic (A-End), start the **traceroute** to the destination host. Then run the **traceroute** from the destination host (B-End) to the origin host. Commands and flags might differ by device.
**Analyze the results**
Look for asymmetric routing. If the traffic is not taking the same path, there might be asymmetric routing somewhere in the network.
Are there any places in the **traceroute** where the response time has increased markedly? If so, are those delays within your network?
Are there any firewalls or access list rules prohibiting traffic from reaching its destination?
|
| **Verify routing configurations and routing tables** |
Confirm both Layer 2 and Layer 3 configurations.
Review metrics, route filters, firewalls, and traffic shaping.
Verify the routing table (Layer 3) and confirm whether the prefix in question is reachable and on the expected routing path to Megaport.
Confirm that the gateway (the device facing the NAT Gateway) is advertising the required prefix if a route filter is in place.
Confirm the NAT Gateway routing table.
|
## Ping and traceroute
Megaport provides standard network diagnostic tools, such as ping and traceroute, directly from a NAT Gateway.
You can run diagnostic requests via the Megaport Portal or the Megaport API. After the tests are complete, the real-time results are retrieved and displayed in the Portal.
* Diagnostic requests (ping or traceroute) are initiated against a specified NAT Gateway.
* The destination must be a valid IPv4 or IPv6 address.
* The source must be a valid IPv4 or IPv6 address that is configured on the NAT Gateway interface.
* You cannot cancel a running diagnostic request. The request must complete or naturally time out, then return the result before the next request will run.
**To run a ping test**
Ping is available only on NAT Gateway with at least one active VXC connection.
1. Log in to the Megaport Portal and choose **Services**.
2. Click the Service Diagnostics icon or the Looking Glass icon.
3. Click the **Ping** tab.
4. Type the destination IP into the **Destination IP** field, then click **Run Ping**.\
Latency results are returned.
**To run a traceroute test**
Traceroute is available only on NAT Gateway with at least one active VXC connection.
1. Log in to the Megaport Portal and choose **Services**.
2. Click the Service Diagnostics icon or the Looking Glass icon.
3. Click the **Traceroute** tab.
4. Type the destination IP into the **Destination IP** field, then click **Run Traceroute**.\
Packet routing and transit delay results are returned.
### Ping and traceroute specifications
Ping and traceroute tests from a NAT Gateway are subject to certain limits and specifications. For more information, see [Megaport NAT Gateway (NAT Gateway)](/limits-quotas#nat-gateway).
## Next steps
If the troubleshooting actions do not resolve your issue, contact support. Before contacting support for assistance, collect the following information.
* **Troubleshooting results** -- Provide all troubleshooting steps taken in detail.
* **General details** -- The date, time, and time zone in which the issue started.
* **Loopback details** -- If you placed loopbacks, note their location and direction.
* **Interface and BGP configurations on the customer device/Cloud Service Provider side**
* Provide the interface settings, including the VLAN number.
* Provide any static routes and routing protocol configurations (EIGRP/OSPF/BGP).
* Provide the BGP ASN.
* Provide all firewall rules and ACL configurations for the data flow experiencing the issue.
* **Source and destination IP addresses**
* Provide the **IP packet** field containing the IP address of the originating device.
* Provide the **IP packet** field containing the IP address of the destination device.
* **High-level network diagram** -- Understanding how your network design is implemented and the connection into the Megaport network helps identify additional focus areas within the troubleshooting process. Provide a network diagram that includes all devices in the path; note each device’s involved IP addresses and VLANs.
* **Ping test results** -- Provide the output of each **ping** test performed on the service. Provide output tests for all services related to different products (Port, VXC, NAT Gateway).
* **Traceroute test results** -- Provide **traceroute** results indicating which side of the connection initiated the test and which side was the destination. We recommend using the A-End and B-End information from your VXC.
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
# Troubleshooting Next Steps
Source: https://docs.megaport.com/troubleshooting/next-steps
This help topic describes the information you need to provide support if you cannot resolve an issue through the published troubleshooting information.
If you are unable to resolve your issue through any of the troubleshooting topics, contact Megaport Support. Before contacting support for assistance, collect the following information.
## Megaport required data
* **Company Name** -- Provide the Company Name associated with the service. If you are working on behalf of another company, make sure you have been set up as a user on their Megaport account to receive support.
For user details, see [Adding and Modifying Users](/portal-admin/user-management).
* **Service ID** (if applicable) -- The Service ID is a unique alphanumeric reference associated with each service. The Service ID appears next to the service name on the Services page.
* **Details of inquiry, question, or requirement** -- Provide a detailed summary of how Megaport can assist. If relevant, provide any screenshots or links to documentation.
## Helpful references
* [Customer Field Services](/finance/customer-field-services)
* [Providing Debug Information for Faster Support](/troubleshooting/debug)
* [Contacting Support](/support/contact)
# Troubleshooting Overview
Source: https://docs.megaport.com/troubleshooting/overview
This help topic introduces the troubleshooting section.
This section helps you investigate errors and unexpected behaviors with your Megaport services. Each topic includes troubleshooting suggestions as well as next steps.
| **Feature** | **Topics** |
| :- | :- |
| **Activation** |
[Activating Ports](/troubleshooting/activation)
[Errors When Ordering](/troubleshooting/errors/automation-fails)
[Providing Debug Information for Faster Support](/troubleshooting/debug)
|
## Quick Tip Videos
## Megaport Support Videos
## Helpful Tools
* [ping](https://en.wikipedia.org/wiki/Ping_\(networking_utility\))
* [traceroute](https://www.fortinet.com/resources/cyberglossary/traceroutes)
* [packet capture](https://www.thousandeyes.com/learning/glossary/packet-capture)
# Troubleshooting Down or Flapping Ports
Source: https://docs.megaport.com/troubleshooting/port/down
This help topic describes how to troubleshoot down or flapping Ports.
If a is down (not passing traffic) or rapidly alternating between an up/down state (flapping), run through these troubleshooting steps to help identify the root cause of the service disruption.
You can verify Port status from the Megaport Portal. On the [Services page](/portal-admin/services-page) in the Portal, find the Port and mouse over its icon. A message displays the status of the service. The color of the icon also indicates the service status.
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Check for errors, packet drops, and device logs** | Interface statistics and device logs can help identify which end of the cross connect is causing the fault, and the potential solution. For example, an increasing number of incoming errors on a network interface generally rules out that specific SFP (small form pluggable) and indicates a potential issue with other components of the cross connect. |
| **Verify physical connections with the data center** | Open a ticket with the data center to perform the following tests:
Check the cross connect for damages or cleaning, if needed.
SFP models should align with the Interface Speed and Interface details in Megaport [Technical Specifications](/tech-specs).
Ensure that the data center is transmitting adequate light outside of the demarcation point at its end of the connection. The data center should check the light at the demarcation point with a light reading meter.
|
| **Verify carrier circuit status (if any)** | Some cross connects are set through one or multiple carrier network devices before reaching the Megaport network. Verify that the device interfaces in the cross connect path are free of errors, and that send and receive optical levels are operating correctly. |
## Next steps
If the troubleshooting actions do not resolve your issue, contact support. Before requesting assistance, collect the following information.
* **Troubleshooting results** -- Provide all troubleshooting steps taken in detail. For example, if loops were placed, note their location and which direction they faced.
* **Data center ticket reference** -- Megaport requires the data center ticket number to ensure that a ticket has been opened, and works as a reference if we open a ticket. Providing the ticket to the data center helps expedite troubleshooting and provides information on work that has already been done.
* **Port status, Tx (transmitted) and Rx (received) optical levels, and device logs** -- Port status, optic light readings, and device logs are helpful in determining the potential cause of a down or flapping Port.
* **SFP model and specifications** -- SFP models should align with Megaport [Technical Specifications](/tech-specs).
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
# Troubleshooting Port and VXC Latency
Source: https://docs.megaport.com/troubleshooting/port/latency
This help topic describes how to identify and solve issues with Port and VXC latency.
Latency is the time it takes for data to be transferred between its original source and its destination, measured in milliseconds. Latency generally can be attributed to changes to the path network traffic traversed and stabilizes quite quickly. To understand the expected latency for the circuits your traffic traverses, see the Megaport [Network Latency page](https://www.megaport.com/network-latency/).
You can verify Port and VXC status from the Megaport Portal. On the [Services page](/portal-admin/services-page) in the Portal, find the Port or VXC and mouse over its icon. A message displays the status of the service. The color of the icon also indicates the service status.
## Troubleshooting actions
If you notice ongoing increased latency or frequent latency spikes with your Ports or VXCs, step through these troubleshooting actions before contacting Megaport Support.
| **Action** | **Steps** |
| :- | :- |
| **Check for errors and packet drops on the device** | Interface statistics and logs can help identify which end of the cross connect is causing the fault, and the potential solution. For example, an increasing number of incoming errors on a network interface generally rules out that specific and indicates a potential issue with other components of the cross connect. |
| **Verify the Tx and Rx optical levels on the device** | Verify both the transmitted (Tx) and received (Rx) light levels. When no signal is received from the far-end (Megaport) device, it could indicate that the polarity is wrong and reversed. If no light is received from the far-end connection, verify the fiber polarity. |
| **Verify physical connections with the data center (reseat and replace SFP, clean and replace cables, loopback test)** | Open a ticket with the data center to perform the following tests:
Check the cross connect for damages or cleaning, if needed.
Ensure that the data center is transmitting adequate light outside of the demarcation point at its end of the connection. The data center should check the light at the demarcation point with a light reading meter.
SFP models should align with the interface speed and interface details in Megaport [Technical Specifications](/tech-specs).
|
| **Verify carrier circuit status (if any)** | Some cross connects are set through one or multiple carrier network devices before reaching the Megaport network. Verify that the device interfaces in the cross connect path are free of errors and optic light readings are operating correctly. |
| **Validate equipment performance** | While troubleshooting, Megaport does not have visibility or access outside the Megaport network. To verify that the cause of an issue is within the Megaport network, Megaport Support requires customers to validate the performance of their equipment. This includes ensuring that the hardware specifications and limitations are compatible with Megaport [Technical Specifications](/tech-specs), and monitoring the network traffic and the workload on the hardware to avoid congestion or degraded performance. To ensure that hardware and your network is operating as expected, we recommend that you validate the performance of the following:
**Hardware**
Optic (SFP type, speed, and wavelength) and fiber type
Port capacity
Switch, router, and firewall models
Firmware version
**Network**
Traffic flow
Port utilization
CPU utilization
Configuration
Overall network design
If you identify any anomalies, capture the logs, graph details, or any relevant error messages. |
| **Compare latencies** | Compare your latency to Megaport's published latency. For more information, see the How to Check the Network Latency video above. |
| **Perform or other test to locate symptom** | **Traceroute** testing can help to determine if a destination is reachable. **Traceroute** sends a sequence of packets between two points and shows you the route the packets take. **Traceroute** also measures the transit delays of packets across an IP network.
**Perform end-to-end traceroute testing**
From the host that is originating traffic (A-End), start the **traceroute** to the destination host (B-End). Then run the traceroute from the destination host to the origin host. Commands and flags might differ by device.
**Analyze the results**
Look for potential asymmetric routing. If the **traceroute** results are not taking the same path, a **traceroute** will help pinpoint asymmetric routing somewhere in the network.
Are there any places in the **traceroute** where the response time has significantly increased? If so, are those delays within your network? Are there any firewalls or access list rules prohibiting traffic from reaching the destination?
|
## Next steps
If the troubleshooting actions do not resolve your issue, contact support. Before requesting assistance, collect the following information.
* **Troubleshooting results** -- Provide all the troubleshooting steps you have taken in detail. For example, if loops were placed, note their location and which direction they faced.
* **Source IP address and destination IP address** -- The source IP address IP packet field contains the IP address of the originating data host. The destination IP address IP packet field contains the IP address of the host to which it is addressed.
* **High-level network diagram** -- Understanding how your network design is implemented and the connection into the Megaport network helps identify additional focus areas within the troubleshooting process. Provide a network diagram that includes all devices in the path; note the involved IP addresses and VLANs for each device.
* **Ping test results** -- Provide the output of each **ping** test performed on the service. Provide all output tests if you have multiple services related to different products (for example, a Port or VXC).
* **Traceroute results** -- Provide **traceroute** results, indicating which side of the connection initiated the test and which side was the destination. We recommend that you use the A-End and B-End information from your VXC.
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
# Troubleshooting Packet Loss on Ports and VXCs
Source: https://docs.megaport.com/troubleshooting/port/packet-loss
This help topic describes troubleshooting steps to solve issues with packet loss on Ports and VXCs.
When accessing any network, small units of data called packets are sent and received. When one or more of these packets fail to reach their intended destination, can manifest in the form of network disruption, slow service, or even total loss of network connectivity.
If you notice packet loss on a or , step through these troubleshooting actions to isolate the root cause.
You can verify Port or VXC status from the Megaport Portal. On the [Services page](/portal-admin/services-page) in the Portal, find the service and mouse over its icon. A message displays the status of the service. The color of the icon also indicates the service status.
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Check interface or errors and packet drops on the device** | Interface statistics and logs can help identify which end of the cross connect is causing the fault, and the potential solution. For example, an increasing number of incoming errors on a network interface generally rules out that specific and indicates a potential issue with other components of the cross connect. |
| **Verify the Tx and Rx optical levels on the device** | Check the transmitted (Tx) and received (Rx) light levels. This health check enables you to validate physical connectivity. Considerations:
If no Rx light is received, the service is down.
If you observe degradation of Tx and Rx light levels, the service might be interrupted. Megaport recommends that you check your physical connections.
If you are not transmitting or receiving light to/from Megaport, it might be caused by one of the following:
**Fiber polarity issue** -- Verify by rolling the fibers at your end.
**Connectivity issues within your environment or cross connect** -- Verify by performing physical loopback testing within your environment.
**Connectivity issues within the Megaport environment** -- Verify by performing physical loopback testing from your environment toward Megaport.
|
| **Verify physical connections with the data center (reseat and replace SFP, clean and replace cables, loopback test)** | Open a ticket with the data center to perform the following tests:
Check the cross connect for damages or cleaning, if needed.
Ensure that the data center is transmitting adequate light outside of the demarcation point at its end of the connection. The data center should check the light at the demarcation point with a light reading meter.
|
| **Verify carrier circuit status (if any)** | Some cross connects are set through one or multiple carrier network devices before reaching the Megaport network. Verify that the device interfaces in the cross connect path are free of errors and optic light readings are operating correctly. |
| **Validate equipment performance** | While troubleshooting, Megaport does not have visibility or access outside the Megaport network. To verify that the cause of an issue is within the Megaport network, Megaport Support requires customers to validate the performance of their equipment. This includes ensuring that the hardware specifications and limitations are compatible with Megaport [Technical Specifications](/tech-specs), and monitoring the network traffic and the workload on the hardware to avoid congestion or degraded performance. To ensure that hardware and your network is operating as expected, we recommend that you validate the performance of the following:
**Hardware**
Optic (SFP type, speed, and wavelength) and fiber type
Port capacity
Switch, router, and firewall models
Firmware version
**Network**
Traffic flow
Port utilization
CPU utilization
Configuration
Overall network design
If you identify any anomalies, capture the logs, graph details, or any relevant error messages. |
| **Perform (or other test) to locate the symptom** | **Traceroute** is a network diagnostic tool that tracks in real-time the pathway taken by a packet on an IP network from source to destination, reporting the IP addresses of all the routers along the path. **Traceroute** also records the time taken for each hop the packet makes during its route to the destination.
**Perform end-to-end traceroute testing**
From the host that is originating traffic (A-End), start the **traceroute** to the destination host (B-End). Then run the **traceroute** from the destination host to the origin host. Commands and flags might differ by device.
**Analyze the results**
Look for potential asymmetric routing. If the **traceroute** results are not taking the same path, a **traceroute** will help pinpoint asymmetric routing somewhere in the network.
Are there any places in the **traceroute** where the response time has significantly increased? If so, are those delays within your network? Are there any firewalls or access list rules prohibiting traffic from reaching the destination?
|
## Next steps
If the troubleshooting actions do not resolve your issue, contact support. Before requesting assistance, collect the following information.
* **Troubleshooting results** -- Provide all the troubleshooting steps you have taken in detail. For example, if loops were placed, note their location and which direction they faced.
* **Source IP address and destination IP address** -- The source IP address is the IP address of the host that sent the packet. The destination IP address is the IP address of the host that should receive the packet.
* **High-level network diagram** -- Understanding how your network design is implemented and the connection into the Megaport network helps identify additional focus areas within the troubleshooting process. Provide a network diagram that includes all devices in the path; note each device’s involved IP addresses and VLANs.
* **Ping test results** -- Provide the output of each **ping** test performed on the service. Provide all output tests if you have multiple services related to different products (for example, a Port or VXC).
* **Traceroute results** -- Provide **traceroute** results, indicating which side of the connection initiated the test and which side was the destination. We recommend that you use the A-End and B-End information from your VXC.
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
# Troubleshooting Throughput and Performance
Source: https://docs.megaport.com/troubleshooting/port/speed
This help topic describes how to identify and solve issues with throughput and speed.
This topic explains how to troubleshoot and isolate the cause of discrepancies between your subscribed bandwidth and actual transfer rates, and inconsistent network performance.
Megaport does not have visibility or access outside the Megaport network. To determine that the cause of an issue resides within the Megaport network, Megaport Support requires you first to validate the performance of your equipment.
## Before starting technical troubleshooting
Before troubleshooting, ensure your service is not affected by scheduled maintenance or a known outage from either your Cloud Service Provider (CSP) or Megaport.
* **For CSP updates** -- Check your email notifications or visit the provider’s official status page.
* **For Megaport updates** -- View real-time service status directly in the Megaport Portal. For more information, see [Monitoring Maintenance and Outage Events](/portal-admin/monitoring-events).
Additionally, review monitoring data in your Megaport Portal. The following items are key fields to monitor.
* **Service Logs** -- Check the Logs tab in the Portal for up/down events and provisioning history. For more information, see [Viewing service logs](/monitoring/port-vxc-monitoring#service-logs).
* **Usage Graphs** -- Review the Usage tab to analyze traffic patterns, optical levels, and errors. For more information, see [Viewing usage details](/monitoring/port-vxc-monitoring#usage-details).
## Troubleshooting Ports and Cross Connects
For issues related to your Port, please review the items below before contacting Megaport Support.
| **Category** | **Troubleshooting Step** | **Actions** | **Description and Analysis** |
| - | - | - | - |
| **Physical layer** | Interface error review | Check interface or CRC errors and packet drops on the device. | Interface statistics and logs can help identify which end of the Cross Connect is causing the fault, and the potential solution.
For example, an increasing number of incoming errors on a network interface generally rules out that specific SFP and indicates a potential issue with other components of the Cross Connect. |
| **Hardware** | compatibility | Check your SFP.
Confirm your Port capacity.
Check your switch, router, and firewall models.
Check the firmware version. | Confirm your optic SFP type, speed, wavelength, and fiber type.
Ensure SFPs match Megaport specs (For example, 1000BASE-LX for 1 Gbps or 10GBASE-LR for 10 Gbps).
For more information, see [Technical Specifications](/tech-specs). |
| **Optical level** | Optical level check | Verify Tx/Rx light levels on your device.
Check the transmitted (Tx) and received (Rx) light levels. | This health check allows you to validate physical connectivity.
If no Rx light is received, the service is down.
If you observe degradation of Tx and Rx light levels, the service might be interrupted. We recommend you check your physical connections.
If you are not transmitting (Tx) or receiving (Rx) light to/from Megaport, it might be caused by one of the following:
• Fiber polarity issue – Verify by rolling the fibers at your end.
• Connectivity issues within your environment or Cross Connect – Verify by performing physical loopback testing within your environment.
• Connectivity issues within the Megaport environment – Verify by performing physical loopback testing from your environment toward Megaport. |
| **Hardware** | Network | Check your network for the following:
• Port utilization • CPU utilization • Configuration • Overall network design | If you identify any anomalies, capture the logs, graph details, or any relevant error messages. |
| **Hardware** | Carrier circuit | Verify carrier circuit status (if any). | Some Cross Connects are set through one or multiple carrier network devices before reaching the Megaport network.
Verify that the device interfaces in the Cross Connect path are free of errors and optic light readings are operating correctly. |
| **Environment** | Data center verification | Open a ticket with the data center. | If errors persist, seek the data center’s assistance to verify the following:
• Check the Cross Connect for damage or cleaning, if needed.
• Ensure that the data center is transmitting adequate light outside of the demarcation point at its end of the connection. The data center should check the light at the demarcation point with a light reading meter.
• You might request to reset and replace SFP, clean and replace cables, loopback test. |
| **Configuration requirements of your device** | Auto-negotiation | Check your router configuration. | Depending on the Megaport device specified in your LOA, auto-negotiation might be required.
This is particularly important for some 1 Gbps services, where auto-negotiation must be enabled on your router.
Check the bottom of the Customer Demarcation/Z Side section in your LOA. If auto-negotiation is set to On, you must enable it on your router.
Use the `negotiate auto` command on your interface. |
| **Your Port setting** | LACP settings | Check your Port setting in the Portal. | Enable LACP if the Port is part of a LAG. Otherwise, ensure it is disabled. For more information, see [Creating a Link Aggregation Group](/connections/lag). |
## Troubleshooting VXCs
For issues related to your VXC, please review the items below before contacting Megaport Support.
| **Test Method** | **Procedures and Actions** | **Description and Analysis** |
| - | - | - |
| **Traceroute (or other test) to locate the symptom** | Traceroute testing can help to determine if a destination is reachable.
**Traceroute:** • Sends a sequence of UDP packets between two points and shows you the route the packets take.
• Measures the transit delays of packets across an IP network.
**Perform end-to-end traceroute testing:** • From the host that is originating traffic (A-End), start the traceroute to the destination host (B-End).
• Then run the traceroute from the destination host to the origin host. Commands and flags might differ by device. | **Analyze the results:**
• Look for points in the traceroute where response times increase significantly. If identified, determine if these delays are occurring within your own network.
• Verify whether any firewalls or Access Control Lists (ACLs) are prohibiting traffic from reaching the destination. |
| **iPerf (Throughput tests)** | iPerf is a cross-platform tool used to create standardized performance measurements and tune your network.
iPerf has both client and server functionality and can create data streams to measure the throughput between two ends, in one or both directions.
**Recommended testing procedure** We recommend a 30-minute bidirectional testing window: test first with the A-End as the client and the B-End as the server, then reverse the roles with the B-End as the client and the A-End as the server. Allow approximately 10–15 minutes between each test. This test must be run using UDP. Here is an example of the command to run on the A-End or B-End:
iperf3 -c \ -b1000m -t 900 -u
**Note:** UDP streams must be used to measure throughput between the two ends of the connection without the overhead of TCP negotiation, congestion avoidance, and windowing. | **Analyze the results:**
• Look for potential asymmetric routing. A traceroute will help to pinpoint whether the traceroute results are taking different paths, which might indicate asymmetric routing somewhere in the network.
• Are there any places in the traceroute where the response time has increased significantly? If so, are those delays within your network?
**After testing, provide your interface statistics and take a screenshot of:**
• Traffic graphs (if possible)
• Ingress/egress points in your network nearest to Megaport
• Traffic graphs for B-End ingress/egress (if possible).
Specify which device(s), Port(s), and VLANs on the network diagram to which the graphs relate. |
## Next steps
If these troubleshooting steps do not resolve the issue, contact the Megaport Support. Provide the information in the table below in a .txt file when submitting your request, along with the following four mandatory pieces of information.
* **Service ID** -- The unique eight-character alphanumeric code (this is the most critical information for the Megaport Support team). For more information, see [Service Details](/portal-admin/services-page#servicedetails).
* **Source/destination details** -- Service information for each test performed.
* **iPerf parameters** -- The specific settings used for each test.
* **Timestamp** -- The exact time and timezone when the tests were conducted.
| **Category** | **Details** |
| - | - |
| **Troubleshooting results** | Provide all the troubleshooting steps you have taken in detail. For example, if loops were placed, note their location and which direction they faced. |
| **Source IP address and destination IP address** | The source IP address is the IP address of the host that sent the packet. The destination IP address is the IP address of the host that should receive the packet. |
| **High-level network diagram** | Understanding how your network design is implemented and the connection to the Megaport network helps identify additional focus areas within the troubleshooting process.
Provide a network diagram that includes all devices in the path. Note each device’s involved IP addresses and VLANs. |
| **Ping test results** | Provide the output of each ping test performed on the service. Provide all output tests if you have multiple services related to different products (for example, a Port or VXC). |
| **Traceroute results** | Provide traceroute results, indicating which side of the connection initiated the test and which side was the destination. We recommend that you use the A-End and B-End information from your VXC. |
| **iPerf (throughput) test results** | Provide all data based on the steps above and any relevant information related to the questions below:
**Are you using traffic shaping on your network?** If you are shaping, policing, or filtering traffic before it reaches Megaport, it can cause us to see only the shaped ingress traffic in the Megaport network. Customers and resellers must ensure that the equipment used outside of Megaport’s network can support the required speeds.
**Have you contacted the B-End of the connection to ensure that there aren’t any problems on that side of the path?** Provide the case number, if applicable. After traffic is sent out from Megaport’s network interface to the provider interface, we no longer control that flow.
**Are there any other providers involved, such as telco carriers? If a carrier is involved in the network, has a case been opened with them to investigate potential routing issues?** Provide the case number, if applicable. It is important to verify whether you are using a telco carrier to route traffic flow to/from your network to Megaport, as we can only troubleshoot flow through our devices. For example, we cannot account for any loss or other issue before it reaches our network.
**If this is an Azure connection, are you using the Q-in-Q option in the Megaport Portal as described in Configuring Q-in-Q?** Azure connectivity with Q-in-Q can be complex and must be configured correctly to ensure traffic is properly delivered to Megaport and onward to Azure. For more information, see [Configuring Q-in-Q](/connections/q-in-q). |
| **Packet capture logs (optional)** | Packet capture (PCAP) logs help collect network traffic, monitor bandwidth, detect malware, and support incident response. If relevant to the issue, providing PCAP logs can help give a clearer understanding of your network traffic and behavior. |
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
## Helpful references
* [Contacting Support](/support/contact)
* [Megaport Limits and Quotas](/limits-quotas)
* [Technical Specifications](/tech-specs)
* [Troubleshooting Port Activation](/troubleshooting/activation)
* [Understanding the Services Page](/portal-admin/services-page)
# Troubleshooting VXC Connectivity
Source: https://docs.megaport.com/troubleshooting/port/vxc-connection
This help topic describes how to identify and solve issues with VXC connectivity.
If you are experiencing connectivity issues, we recommend that you start by troubleshooting your to isolate the issue. While the VXC will often display different symptoms, the root cause might be attributed to another area of the network.
You can verify VXC status from the Megaport Portal. On the [Services page](/portal-admin/services-page) in the Portal, find the VXC and mouse over its icon. A message displays the status. The color of the icon also indicates the service status.
## Troubleshooting actions
| **Action** | **Steps** |
| :- | :- |
| **Check for errors, packet drops, and device logs** | Interface statistics and logs can help identify which end of the cross connect is causing the fault, and the potential solution. For example, an increasing number of incoming errors on a network interface generally rules out that specific and indicates a potential issue with other components of the cross connect. |
| **Verify the Tx and Rx optical levels on the device** | Check the transmitted (Tx) and received (Rx) light levels. This health check enables you to validate physical connectivity. Some considerations:
If no Rx light is received, the service is down.
If you observe degradation of Tx and Rx light levels, the service might be interrupted. Megaport recommends that you check your physical connections.
If you are not transmitting or receiving light to/from Megaport, it might be caused by one of the following:
**Fiber polarity issue** -- Verify by rolling the fibers at your end.
**Connectivity issues within your environment or cross connect** -- Verify by performing physical loopback testing within your environment.
**Connectivity issues within the Megaport environment** -- Verify by performing physical loopback testing from your environment toward Megaport.
|
| **Verify physical connections with the data center** | Open a ticket with the data center to perform the following tests:
Check the cross connect for damages or cleaning, if needed.
Ensure that the data center is transmitting adequate light outside of the demarcation point at its end of the connection. The data center should check the light at the demarcation point with a light reading meter.
SFP models should align with the Interface Speed and Interface details in the Megaport [ Technical Specifications](/tech-specs).
|
| **Verify carrier circuit status (if any)** | Some cross connects are set through one or multiple carrier network devices before reaching the Megaport network. Verify that the device interfaces in the cross connect path are free of errors and optic light readings are operating correctly. |
| **Validate equipment performance** | While troubleshooting, Megaport does not have visibility or access outside the Megaport network. To verify that the cause of an issue is within the Megaport network, Megaport Support requires customers to validate the performance of their equipment. This includes:
Ensuring that the hardware specifications and limitations are compatible with Megaport [Technical Specifications](/tech-specs).
Monitoring the network traffic and the workload on the hardware to avoid congestion or degraded performance.
In addition, it is recommended that you validate the below performance to ensure it is operating as expected. If any anomalies are identified, capture the logs, graph details or any relevant error messages.
**Hardware**
Optic (SFP type, speed, and wavelength) and fiber type
Port capacity
Switch, router, and firewall models
Firmware version
**Network**
Traffic flow
Port utilization
CPU utilization
Configuration
Overall network design
If you identify any anomalies, capture the logs, graph details, and any relevant error messages. |
| **Compare latencies** | Compare your latency to Megaport's published latency. For more information, see the How to Check the Network Latency video above. |
| **Perform or other test to locate the symptom** | **Traceroute** is a network diagnostic tool that tracks in real-time the pathway taken by a packet on an IP network from source to destination, reporting the IP addresses of all the routers along the path. **Traceroute** also records the time taken for each hop the packet makes during its route to the destination.
**Perform end-to-end traceroute testing**
From the host that is originating traffic (A-End), start the **traceroute** to the destination host (B-End). Then run the **traceroute** from the destination host to the origin host. Commands and flags might differ by device.
**Analyze the results**
Look for potential asymmetric routing. If the **traceroute** results are not taking the same path, a **traceroute** will help pinpoint asymmetric routing somewhere in the network.
Are there any places in the **traceroute** where the response time has significantly increased? If so, are those delays within your network? Are there any firewalls or access list rules prohibiting traffic from reaching the destination?
|
| **Perform throughput tests** | iPerf is a cross-platform tool used to create standardized performance measurements and tune your network. iPerf has both client and server functionality and can create data streams to measure the throughput between two ends, in one or both directions.
**Perform testing** Megaport recommends performing a 15 minute test on each side (the A-End client and B-End server, then the B-End client and A-End server) for a total of 30 minutes of testing and approximately 10 to 15 minutes between each test. This test must be run using . Here is an example of the command to run on the A-End or B-End:
`iperf3 -c -b1000m -t 900 -u`
**Note:** UDP streams must be used to measure throughput between the two ends of the connection without the overhead of TCP negotiation, congestion avoidance, and windowing.
**Analyze the results**
Look for potential asymmetric routing. A traceroute will help to pinpoint whether the traceroute results are taking different paths, which might indicate asymmetric routing somewhere in the network.
Are there any places in the traceroute where the response time has increased significantly? If so, are those delays within your network?
After testing, provide your interface statistics and take a screenshot of:
Traffic graphs (if possible)
Ingress/egress points in your network nearest to Megaport
Traffic graphs for B-End ingress/egress (if possible)
Specify which device(s), port(s), and VLANs on the network diagram to which the graphs relate.
|
## Next steps
If the troubleshooting actions do not resolve your issue, contact support. Before requesting assistance, collect the following information:
* **Troubleshooting results** -- Provide all the troubleshooting steps you have taken in detail. For example, if loops were placed, note their location and which direction they faced.
* **Port status and Tx/Rx optical levels on the device** -- Use the Megaport Portal to review your Port status. For more information, see the How to Check the Port Status video above.
* **Data center ticket reference** (optional) -- Once the cross connect is installed the data center will send a completion notice. The notice will include the data center cross connect order number, which Megaport requires to provide to the data center technician. Also provide any existing ticket reference numbers that you have opened directly with the data center.
* **Source IP address and destination IP address** -- The source IP address is the IP address of the host that sent the packet. The destination IP address is the IP address of the host that should receive the packet.
* **High-level network diagram** -- Understanding how your network design is implemented and the connection into the Megaport network helps identify additional focus areas within the troubleshooting process. Provide a network diagram that includes all devices in the path; note each device’s involved IP addresses and VLANs.
* **Ping test results** -- Provide the output of each **ping** test performed on the service. Provide all output tests if you have multiple services related to different products (for example, a Port, VXC, or MCR).
* **Traceroute results** -- Provide traceroute results, indicating which side of the connection initiated the test and which side was the destination. We recommend that you use the A-End and B-End information from your VXC.
* **iPerf (throughput) test results** -- Provide all data based on the steps above and any relevant information related to the questions below:
* **Are you using traffic shaping on your network?**\
If you are shaping, policing, or filtering traffic before it reaches Megaport, it can cause us to see only the shaped ingress traffic in the Megaport network. Customers and resellers must ensure that the equipment used outside of Megaport’s network can support the desired speeds.
* **Have you contacted the B-End of the connection to ensure that there aren't any problems on that side of the path?**\
Provide the case number if applicable. Once traffic is sent out from Megaport’s network interface to the provider interface, we no longer control that flow.
* **Are there any other providers involved, such as telco carriers? If a carrier is involved in the network, has a case been opened with them to investigate potential routing issues?**\
Provide the case number if applicable. It is important to verify whether you are using a telco carrier to route traffic flow to/from your network to Megaport, as we can only troubleshoot flow through our devices. For example, we cannot account for any loss or other issue before it reaches our network.
* **If this is an Azure connection, are you using the Q-in-Q option in the Megaport Portal as described in [Configuring Q-in-Q](/connections/q-in-q)?**\
Azure with Q-in-Q can be tricky, and must be configured correctly to send the traffic properly to Megaport and then on to Azure.
* **Packet capture logs** (optional) -- Packet capture (or PCAP) logs help collect network traffic, monitor bandwidth, detect malware, and assist in incident response. If relevant to the issue, provide packet capture logs for a greater understanding of your network.
* **MVE/SD-WAN configurations (if applicable)** -- Confirm the following:
* Login credentials are accurate
* The correct license and template/workflow are attached
* The instance size and software versions
* The MVE interface status, such as configured IP addresses and VLAN
* For gateway and interconnect connectivity, check sessions, bandwidth, and status
* Verify the MVE IP address in the Megaport Portal
* Verify the configured bandwidth, VLAN, IP address and subnet masks, and ASNs
* Validate connectivity details such as the interface status and BGP neighbor status
For more information, see [MVE Overview](/mve).
For more information about when a field service technician is needed onsite at the data center, see [Customer Field Services](/finance/customer-field-services).
# Megaport Portal Authentication Frequently Asked Questions (FAQs)
Source: https://docs.megaport.com/troubleshooting/signup-login-faq
This help topic describes some common questions about the authentication changes for the Megaport Portal.
This topic describes some of the commonly asked questions and answers relating to authentication for the Megaport Portal.
## Portal users
### Do I need to use Multi-Factor Authentication (MFA) to log in to the Megaport Portal?
Yes, MFA is mandatory for all users to log in to the Megaport Portal. If you are having trouble logging in with MFA, see [Logging in to the Megaport Portal](/setting-up/logging-in).
### What if I enter an incorrect password or token several times?
After five failed login attempts, your account will be locked. To have your account reactivated, contact your Company Admin.
For more information about account lockout, see [Account lockout](/setting-up/logging-in#account-lockout).
### My username has stopped working and I get a ‘Bad session token error’
Either your username or your password is incorrect. Your username is the primary email address associated with your company's Megaport account.\
If required, your password can be reset at the Megaport Portal login page [https://portal.megaport.com/login](https://portal.megaport.com/login).
### What is a trace ID on a login error?
When a login attempt fails, through the Megaport Portal login page, a social or SSO redirect, or an API token request, the response might include a trace ID. The trace ID uniquely identifies the failed authentication request and can be provided to Megaport Support to help troubleshoot the issue. Trace IDs are specific to authentication failures.
Not every authentication failure displays a trace ID. Simpler failures, such as an incorrect password, do not generate one. If a login error does not include a trace ID, provide Megaport Support with the error message, how you attempted to log in, the approximate time of the error, and your time zone.
**What to do if you encounter a login error**
Some login errors display an error message and a trace ID.
1. Copy the trace ID shown in the error message.
2. Provide it to Megaport Support along with a brief description of what you were trying to do.
Megaport Support can use the trace ID to quickly locate the relevant log entries and investigate the failed request.
**Notes for API and integration users**
A trace ID consists of 32 hexadecimal characters, for example, `4b8ad8c6904e562a6c236c5798e57a23`. Copy and provide the complete value to Megaport Support.
If you are building a client that uses the authentication endpoints, check failed requests for the `trace-id` response header and failed redirects for the `trace_id` query parameter. Include the trace ID in your error handling so users can provide it when contacting Megaport Support.
The trace ID does not change the failure reason returned. It provides an additional reference that Megaport Support can use to identify the failed request.
### What if I don’t know the primary email address associated with my Megaport account?
Megaport cannot provide email addresses over the phone due to privacy policies. We suggest you contact your Megaport Company Admin who can find this information in the Manage Users section of the Portal.
### What are the password complexity rules?
The Megaport Portal password policy enforces minimum password complexity rules. Your password must contain:
* At least 8 characters
* Uppercase characters (A-Z)
* Lowercase characters (a-z)
* Numbers (0-9)
* At least one special character: ^ \$ \* . \[ ] ( ) ? " ! @ # % & / \ , > \< ' : ; | \_ \~ \` = + -
The password policy uses a password strength estimator to prevent common, easily guessed passwords, such as Passw0rd. If you have met all complexity requirements and your password is still being rejected, the likely cause is that the password is too common or easy to guess.
Megaport's authentication platform will enforce and validate the password complexity on login. If your password does not meet these minimum password complexity rules, you will be directed to the Reset Password page, where you can set your new password and log in to the Megaport Portal.
### Can Megaport see my password? How do you know if I meet the complexity requirements?
Megaport doesn’t store passwords in clear text and they are hashed. Validation will occur on entering a new password to ensure it meets the complexity rules.
### How do I change my password?
If you are unable to log in, click **Forgot Password** on the login page to receive an email to update your password. If you have access to the Megaport Portal, you can change your password by choosing User Menu > User Settings > Profile, and clicking **Change Password**. You will be asked to enter your old password, new password, and re-enter the new password.
### Who can change email addresses in the Megaport Portal?
Only the user has the ability to change their email address by choosing User Menu > User Settings > Profile, and clicking **Change Email**. Company Admins and Megaport cannot change another user's email address.
### What is the support reference shown when my login fails?
Some login errors display a support reference on the Megaport Portal error page. If a support reference is shown, copy it and include it in your support request to help us investigate the issue more quickly. For more information, see [Contacting Support](/support/contact/).
## API users
### How will mandatory MFA affect API users?
You will need to use API keys to access Megaport APIs. API keys are the recommended authentication method for API users.
If you are currently using a user account with a username and password to access Megaport APIs, we recommend that you switch to using API keys as soon as possible.\
For more information about creating API keys, see [Creating an API Key](/api/api-key).
### Can I use API keys?
Yes, Megaport provides the ability to create API keys from the Portal. A Company Admin can create API keys with either Company Admin or Read Only permissions.
### How do I create API keys?
Information about creating API keys can be found here: [Creating an API Key](/api/api-key).
# Single Sign-On (SSO) Features and Instructions for Use
Source: https://docs.megaport.com/troubleshooting/sso-terms-conditions
This help topic describes terms and conditions of using Single Sign-On (SSO) in the Megaport Portal.
If Customer enables the Single Sign-On authentication feature ("SSO"), and Customer’s Administrator enforces SSO, then the users of the Megaport Portal must comply with the following.
* **Single Sign-On:** By setting up SSO you are allowing Megaport Portal users on your account to authenticate to the Megaport Portal (Portal) through a third-party identity provider (IdP) instead of a Megaport held username and password. If SSO is enforced by a Company Admin, all Portal users will be required to log in using their third-party IdP credentials. If a Company Admin switches off SSO or Megaport no longer provides SSO, then the Portal users will be required to set up a Megaport password to log in. In the event that the Third Party IdP is not configured correctly, or not responding, a Company Admin can use a username and password to access the Portal via the login help screen.
* **Compatibility:** Megaport currently supports SSO using SAML 2.0 standards. Megaport reserves the right to change or update the available authentication standards used giving the standard notice periods applicable to your GSA/GRA.
* **Third-Party Identity Providers (IdP):** SSO allows customers to connect and use Third-Party IdP products, services, or software to log in to the Portal. Customers are limited to integration with one IdP per Portal account. To enable SSO, users may be required to sign up or log in to the services of the IdP on its respective website or application.
* **Multi Factor Authentication (MFA):** MFA is mandatory on the Portal. A user will be required to enter an additional token to gain access to the Portal.
* **Confidentiality:** Users are responsible for maintaining the confidentiality of passwords and user accounts, including the setting up of SSO and the configuration of IdP. SSO may not suit all accounts and you should evaluate the suitability of SSO for your purposes. Megaport will not be liable if a customer sets up SSO and an unauthorised person gets access to your Megaport account as a result of, or in connection with the integration with the IdP.
* **Privacy:** The Third-Party IdP may process personal information about users. Megaport does not receive any new personal information from the IdP, nor do we share any personal information with the IdP. Users should review the IdP’s website for their Privacy Policy and any terms and conditions on using their service.
* **Availability:** The availability of SSO may depend on the availability of these Third-Party IdP services and their features and functionality. Megaport does not control Third-Party IdP service features and functionality, and they may change without any notice to us. If any Third- Party Service stops providing access to some or all features or functionality, we may stop providing access to the Portal. If your IdP is not responding you should contact your company IT administrator or IdP provider to troubleshoot the fault. Megaport will not be liable to you for any refunds or any damage or loss arising from or in connection with any such change or outage of the Third-Party IdP.
# Testing Configurations in the Staging Environment
Source: https://docs.megaport.com/troubleshooting/staging
This help topic describes the staging environment for testing.
You can test any action in the staging environment. All actions mirror the production system, but services will not be deployed and you will not be billed for any activity.
The Portal staging environment is available here: [https://portal-staging.megaport.com](https://portal-staging.megaport.com)
The API staging environment is available here: `https://api-staging.megaport.com`
You use your production credentials to log in to the staging environment and order or edit services. New user accounts take 24 hours before they are available for use in staging.
The staging data is overwritten every 24 hours and synchronized with the production environment.
This means your staging portal account reflects both your production data and the staging services created that day, but any services or user accounts created in the staging environment will be overwritten by the sync and disappear the following day.
# X-Auth Token Deprecation Frequently Asked Questions (FAQs)
Source: https://docs.megaport.com/troubleshooting/xauth-token-faq
This help topic describes some common questions about the X-Auth token authentication changes for the Megaport Portal.
In November 2022, Megaport released API keys to facilitate generation of authentication tokens for machine to machine communication to the Megaport API, removing the reliance on non-expiring X-Auth tokens. This has improved our security posture giving customer company admins and IT infosec managers additional control over access to Megaport's API.
The benefits of API keys are a controlled authentication process, no need to embed usernames and passwords when accessing the API, and the ability to create a company admin or read only API key.
Megaport will be phasing out the use of X-Auth tokens starting July 2023. Those accounts that have authenticated using X-Auth tokens with existing API integrations will be whitelisted so X-Auth tokens continue to function until 30 September 2023.
All accounts that have not previously accessed the API using X-Auth tokens must use API keys. On 1 October 2023, any existing X-Auth tokens will no longer be able to access the Megaport API. From this date, all customers must use API Keys to authenticate against the Megaport API.
This topic describes some of the changes and commonly asked questions relating to the X-Auth token authentication changes.
## Why is Megaport making a change to the API authentication?
We’re remediating security risks identified in the most recent penetration test conducted by third-party auditor.
## How do I know if I’m using X-Auth tokens?
Megaport will notify company admins and technical contacts of accounts we have logged using X-Auth tokens.
## When do I need to stop using X-Auth?
If you have authenticated using an X-Auth token previously then it will continue to work until 30 September 2023. If you have never used X-Auth tokens, you must use API keys from now on.
## Where can I find more information on API keys?
Information about creating API keys can be found here: [Creating an API Key](/api/api-key).
## When will API keys be mandatory?
From 1 October 2023 all API authentication must use API keys.
## What if I haven’t updated my API integrations to use API keys by 1 October?
The Megaport API will block access from X-Auth tokens.
## When can I move to API keys?
Immediately. Each company can create up to 5 API keys.
## How many API keys can I have on my Megaport account?
Each account has an allocation of 5 API keys. If you require more please contact your Account Manager or Megaport Support. For more information, see [Contacting Support](/support/contact).
## What permission do API keys have?
API keys can be read only or company admin (full read/write access to all supported functionality).
# Megaport Configuration Assistance
Source: https://docs.megaport.com/advanced-services/configuration-assistance
This help topic describes the Megaport Configuration Assistance service.
Megaport Configuration Assistance is a task-based, hands-on implementation service that provides expert execution of approved network designs. Delivered by Megaport engineers, this professional service helps organizations deploy and migrate Megaport services more efficiently by transferring implementation tasks from internal teams to Megaport.
By leveraging validated best practices, Configuration Assistance helps accelerate deployments while ensuring Megaport services are configured correctly the first time.
Configuration Assistance is available for direct and partner accounts only. It is not available for managed accounts.
## What's included?
Megaport Configuration Assistance has these inclusions.
* **Megaport core services** -- Provisioning and configuration of Megaport infrastructure services, including physical Ports, Megaport Cloud Routers (MCRs), Megaport Virtual Edges (MVE) instances, Virtual Cross Connects (VXCs), Megaport NAT Gateways, and Megaport Internet connections.
* **Cloud connectivity** -- Layer 2 and Layer 3 routing configuration into major Cloud Service Providers (CSPs), such as AWS Direct Connect, Azure ExpressRoute, and Google Cloud Interconnect.
* **Scheduled network events** -- Technical execution during a designated maintenance window to perform requested deployments, upgrades, or configuration tasks.
## Requesting Configuration Assistance
Megaport Configuration Assistance can be requested using these options in the Portal.
### Option 1: During the service ordering process
Use this method to request Configuration Assistance from the Megaport Advanced Services team while ordering your Megaport services.
**To request Configuration Assistance while ordering**
1. After configuring your new Megaport services, click **Review Order** to proceed to the Checkout screen.
2. In the **Would you like to engage our Advanced Services team to implement your solution?** field, choose Yes.\
This opens a text window where you can describe your configuration needs.
3. In the text field, enter a description of your specific deployment and configuration requirements. To help ensure an efficient review, include:
* A summary of the Megaport services requiring configuration.
* Requirements for the new services being deployed, or updates and changes needed for existing services.
* Destination cloud connectivity details, such as AWS, Azure, and Google Cloud.
* The intended end-state or required outcome of the configuration activity.
Submitting a Configuration Assistance request automatically creates a ticket that is sent to a Megaport Technical Account Manager (TAM) for review. You do not need to wait for a response before completing your transaction and can proceed with your service order immediately. A TAM will contact you shortly afterwards to review your requirements and discuss next steps.
4. Click **Order Now**.
### Option 2: Via Help & Support
Use this method to request Configuration Assistance from the Megaport Advanced Services team as a standalone request, separate from the service ordering process.
**To request Configuration Assistance as a standalone request**
1. Log in to the Megaport Portal.
2. Choose the **Help & Support** icon.
3. Click **Advanced Services**.
4. In the text field, enter a description of your specific deployment and configuration requirements. To help ensure an efficient review, include:
* A summary of the Megaport services requiring configuration.
* Requirements for the new services being deployed, or updates and changes needed for existing services.
* Destination cloud connectivity details, such as AWS, Azure, and Google Cloud.
* The intended end-state or required outcome of the configuration activity.
5. Click **Submit Request**.
Submitting a Configuration Assistance request automatically creates a ticket that is sent to a Megaport Technical Account Manager (TAM) for review. A TAM will contact you shortly afterwards to review your requirements and discuss next steps.
## Engagement process
After you submit a Configuration Assistance request, the engagement follows a structured delivery process.
1. **Consultation** -- A TAM conducts a technical workshop with your team to validate your proposed design and architecture, establish implementation requirements, and finalize deployment parameters.\
After both parties agree on the proposed requirements, the assigned TAM will provide a Manual Service Order (MSO) form for your review and acceptance of pricing, terms, and conditions.
2. **Planning and coordination** -- After the MSO is executed, all technical documentation is finalized, including step-by-step runbooks and Methods of Procedure (MOPs). Megaport then coordinates directly with your team to schedule the specific maintenance window for the deployment.
3. **Implementation** -- Megaport engineers execute the required deployment and configuration activities within the scheduled change window.
4. **Handover** -- Megaport verifies that the deployment aligns with your technical specifications and returns operational control of the network environment to your team, accompanied by a formal Notice of Completion.
## Helpful references
* [Megaport Advanced Services Overview](/advanced-services)
* [Megaport Premium Support](/advanced-services/premium-support)
* [Megaport Project Services](/advanced-services/project-services)
# Megaport Advanced Services Overview
Source: https://docs.megaport.com/advanced-services/index
This help topic describes the Megaport Advanced Services.
Megaport Advanced Services extends beyond standard support by providing access to specialized engineering expertise through paid professional services engagements.
Whether you require implementation assistance, support for a complex network transformation, or ongoing operational management, Megaport delivers tailored services to help accelerate outcomes and reduce operational complexity.
This table outlines the three Megaport Advanced Services tiers. Customers can choose the level of support that best fits their business requirements.
| **Name** | **Service Overview** | **Engagement Model** |
| - | - | - |
| Configuration Assistance | Task-based professional services providing hands-on configuration and implementation support for Megaport core service deployments, migrations, and cutovers.
This offering delivers fixed-outcome execution based on customer-provided, pre-defined designs. | Delivered as a fixed scope, coordinated engagement. |
| Project Services | Provides comprehensive support for large or complex digital transformation initiatives. This includes infrastructure auditing, custom network design, implementation, and dedicated project management.
The service covers a wide range of technologies across Megaport services, integrated vendor solutions, and customer hybrid-cloud infrastructure. | A long-term, project-based engagement that utilizes dedicated technical resources for the duration of the initiative. |
| Premium Support | An enterprise-grade operational service designed for organizations that require ongoing technical advocacy, proactive network monitoring, regular health reviews, cost optimization, and accelerated escalation paths. | An ongoing operational support framework delivered through a subscription service model.
This offering includes an assigned Technical Account Manager (TAM) who serves as a dedicated extension of the customer's team. |
To learn more about how Megaport Advanced Services can help you optimize your network lifecycle, contact your Megaport Account Manager or Solutions Architect.
## Helpful references
* [Accelerate your journey with Megaport Advanced Services](https://www.megaport.com/services/advanced-services/)
* [Connections Overview](/connections/overview)
* [Creating a Port](/connections/creating-port)
* [Internet Exchange Overview](/ix)
* [Introducing Megaport](/overview)
* [MCR Overview](/mcr)
* [Megaport Configuration Assistance](/advanced-services/configuration-assistance)
* [Megaport Internet Overview](/megaport-internet)
* [Megaport NAT Gateway Overview](/nat)
* [Megaport Premium Support](/advanced-services/premium-support)
* [Megaport Project Services](/advanced-services/project-services)
* [MVE Overview ](/mve)
# Megaport Premium Support
Source: https://docs.megaport.com/advanced-services/premium-support
This help topic describes the Megaport Premium Support.
Megaport Premium Support is a high-touch operational service designed for organizations that require proactive management of their Megaport environment.
Intended for enterprises operating large hybrid-cloud deployments or business-critical network services, Premium Support extends beyond standard support by providing ongoing technical advocacy, operational guidance, and strategic oversight.
Each customer is paired with a dedicated Megaport Technical Account Manager (TAM) who serves as a trusted advisor and extension of the operations team. Rather than focusing solely on reactive issue resolution, the TAM helps drive architectural alignment, improve operational efficiency, optimize costs, and support future growth.
By maintaining a detailed understanding of your network architecture, business priorities, and technology roadmap, your TAM helps ensure you maximize the performance, reliability, and value of your Megaport investment.
## What's included?
Premium Support provides proactive operational management, technical advocacy, and prioritized escalation pathways through the following service offerings.
* **Incident management** -- A single point of escalation through your TAM to streamline communications during infrastructure outages and coordinate with internal engineering resources, ensuring rapid root-cause analysis and resolution.
* **Priority support request** -- Priority handling of support requests, with accelerated Service Level Agreement (SLA) response targets and enhanced escalation paths.
* **Proactive operational reviews** -- Ongoing infrastructure health reviews and capacity assessments covering Port utilization, Virtual Cross Connect (VXC) capacity, and Megaport Cloud Router (MCR) and Megaport Virtual Edge (MVE) performance.
* **Cost optimization** -- Ongoing assessment of your network services to identify underutilized or over-provisioned resources and align infrastructure spend with actual usage requirements.
* **Capacity planning** -- Expert technical guidance to help scale network capacity ahead of anticipated traffic growth, seasonal demand, or major deployment initiatives.
* **Configuration Assistance** -- Access to Megaport's task-based implementation service for planned network maintenance, service deployments, migrations, and infrastructure updates.
## Requesting Premium Support
Contact your Megaport Account Manager to discuss upgrading your operational environment to Premium Support. Below is a step-by-step overview that describes the onboarding and subscription workflow.
* **Initial consultation** -- Contact your Megaport Account Manager or Solutions Architect to discuss your operational support requirements. A Megaport TAM will be introduced to your team to review the Premium Support offering, assess your current network environment, and identify your operational, technical, and business priorities.
* **Subscription activation** -- Your Megaport Account Manager will coordinate the required commercial and service activation processes to enroll your organization in Premium Support. The service is delivered through a monthly subscription model aligned with your ongoing operational requirements.
* **Operational onboarding** -- Once Premium Support is activated, your Megaport TAM conducts an operational kickoff workshop to establish communication channels, define escalation procedures, and agree on the cadence for ongoing operational reviews. During onboarding, the TAM develops a detailed understanding of your network architecture, business priorities, and support requirements to establish an initial roadmap for optimization, health reviews, and ongoing technical advocacy.
## Helpful references
* [Megaport Advanced Services Overview](/advanced-services)
* [Megaport Configuration Assistance](/advanced-services/configuration-assistance)
* [Megaport Project Services](/advanced-services/project-services)
# Megaport Project Services
Source: https://docs.megaport.com/advanced-services/project-services
This help topic describes the Megaport Project Services.
Megaport Project Services provides end-to-end consulting, project management, and implementation services for complex, large-scale, or long-term infrastructure initiatives. The Megaport Advanced Services team manages the engagement from start to finish, while delivery is carried out by Megaport's certified partner ecosystem, bringing specialized expertise across networking, cloud, security, and related technologies.
## What's included?
Project Services provides the technical expertise and project management capabilities required for large-scale infrastructure transformations. These engagements help organizations plan, implement, and transition from legacy environments to modern cloud and network architectures.
Megaport Project Services has these inclusions:
* **Auditing and design** -- Comprehensive assessment of your existing network environment, including asset discovery, architecture analysis, and the development of High-Level Designs (HLDs) and Low-Level Designs (LLDs).
* **Strategic planning** -- Development of implementation plans, resource allocation strategies, phased delivery schedules, risk mitigation measures, and migration procedures designed to minimize operational disruption.
* **Full-stack expertise** -- Access to specialized engineering expertise across Megaport services, Cloud Service Provider (CSP) networks, physical and virtual infrastructure, and supporting third-party technologies.
* **End-to-end management** -- Dedicated project management and stakeholder coordination to oversee project execution, manage dependencies, and help ensure delivery against agreed timelines and budgets.
## Megaport Project Services delivery framework
To help ensure project success, Megaport provides delivery oversight throughout the engagement, coordinating both the commercial and technical aspects of the project between your organization and our certified partner network.
This Megaport-led model operates through three core pillars:
* **Curated partner matching** -- Megaport maintains a network of certified integration partners with expertise across a range of technologies and services. Based on your project requirements, Megaport identifies and engages the partner best suited to deliver the required technical outcomes.
* **Joint architecture scoping** -- Megaport Technical Account Managers (TAMs) act as technical advisors throughout the discovery phase. Megaport facilitates collaborative scoping workshops with your organization and our partners to translate business and technical requirements into a clearly defined and actionable statement of work.
* **Program governance** -- Throughout the project lifecycle, a TAM provides ongoing technical oversight and coordination between your organization and the partner delivery team. Megaport works with key stakeholders to manage project milestones, address evolving requirements, and help ensure successful project delivery.
## Requesting Project Services
Megaport Project Services can be requested using these options in the Portal.
### Option 1: During the service ordering process
Use this method to request Project Services from the Megaport Advanced Services team while ordering your Megaport services.
**To request Project Services while ordering**
1. After configuring your new Megaport services, click **Review Order** to proceed to the Checkout screen.
2. In the **Would you like to engage our Advanced Services team to implement your solution?** field, choose Yes.\
This opens a text window where you can describe your project needs.
3. In the text field, enter a description of your specific project requirements. To help ensure an efficient review, include:
* A high-level summary of the broader project or program of works you require assistance with.
* The specific types of expertise needed for your project. For example, network and security auditing, strategic design, architectural planning, deployment implementation, or dedicated project management.
* A breakdown of the Megaport services and non-Megaport infrastructure involved across your physical, virtual, and cloud ecosystems.
* The business objective and technical outcome required for a successful project completion.
Submitting a Project Services request automatically creates a ticket that is sent to a Megaport Technical Account Manager (TAM) for review. You do not need to wait for a response before completing your transaction and can proceed with your service order immediately. A TAM will contact you shortly afterwards to review your requirements and discuss next steps.
4. Click **Order Now**.
### Option 2: Via Help & Support
Use this method to request Project Services from the Megaport Advanced Services team as a standalone request, separate from the service ordering process.
**To request Project Services as a standalone request**
1. Log in to the Megaport Portal.
2. Choose the **Help & Support** icon.
3. Click **Advanced Services**.
4. In the text field, enter a description of your specific deployment and project requirements. To help ensure an efficient review, include:
* A high-level summary of the broader project or program of works you require assistance with.
* The specific types of expertise needed for your project. For example, network and security auditing, strategic design, architectural planning, deployment implementation, or dedicated project management.
* A breakdown of the Megaport services and non-Megaport infrastructure involved across your physical, virtual, and cloud ecosystems.
* The business objective and technical outcome required for a successful project completion.
5. Click **Submit Request**.
Submitting a Project Services request automatically creates a ticket that is sent to a Megaport Technical Account Manager (TAM) for review. A TAM will contact you shortly afterwards to review your requirements and discuss next steps.
## Engagement process
After you submit a Project Services request, the engagement follows a structured delivery process.
1. **Consultation and discovery** -- A Megaport TAM will lead a discovery workshop with your team to discuss your project objectives, validate technical requirements, understand timelines and scheduling, and gather the information needed to define the project scope.
2. **Partner matching and scoping** -- Using Megaport's Curated Partner Matching process, Megaport identifies and introduces the certified integration partner best suited to your project requirements. Your Megaport TAM then leads collaborative scoping sessions with your team and the partner to define the project scope, delivery phases, resource requirements, key milestones, and statement of work.
3. **Review and contracting** -- Once the technical scope has been validated, your Megaport TAM provides a Statement of Work (SOW) for your review. The SOW outlines the agreed scope of work, deliverables, pricing, and applicable terms and conditions.
4. **Project mobilization** -- Upon execution of the SOW, the engagement formally begins. Your Megaport TAM schedules the project kickoff meeting, brings together key stakeholders from your organization and the partner delivery team, and initiates project activities under Megaport's governance framework.
## Helpful references
* [Megaport Advanced Services Overview](/advanced-services)
* [Megaport Configuration Assistance](/advanced-services/configuration-assistance)
* [Megaport Premium Support](/advanced-services/premium-support)
# Glossary
Source: https://docs.megaport.com/glossary/index
This help topic defines terminology related to the Megaport network and services.
This help topic defines terminology related to the Megaport network and services.
#### 802.1Q
#### A-End
#### ACH
#### ACL
#### AMS-IX
The Amsterdam Internet Exchange (AMS-IX) is an internet exchange point based in Amsterdam, in the Netherlands. AMS-IX is a non-profit, neutral, and independent peering point. AMS-IX operates a series of Internet Peering Exchanges (IXs) globally and partners with Megaport in several cities. IXs can exchange data traffic between networks more directly and efficiently, reducing bandwidth usage on network uplink connections.
#### API
Application program interface (API) is a set of routines, protocols, and tools for building software applications. An API specifies how software components should interact and APIs are used when programming graphical user interface (GUI) components. The Megaport API allows customers and partners to integrate directly into our platform for automation and service creation (see [dev.megaport.com](https://dev.megaport.com)).
#### ARP
#### ASN
#### Amazon Web Services (AWS)
Amazon Web Services (AWS) is a secure cloud services platform, offering compute power, database storage, content delivery and other functionality to help businesses scale and grow.
#### AWS Direct Connect
AWS (Amazon Web Services) Direct Connect is a network service that allows customers to establish a dedicated network connection between one of Amazon’s Direct Connect locations and the customer’s data center or colocation environment. Megaport is an AWS Direct Connect partner.
#### Azure
Azure is a Microsoft service. It is an open, flexible, enterprise-grade cloud computing platform accessed via Microsoft’s ExpressRoute service.
#### B-End
#### BFD
#### BGP
#### BGP neighbor
#### Classless Inter-domain Routing (CIDR) notation
#### Cloud Access Security Broker (CASB)
#### CDN
A content delivery network (CDN) is a system of distributed servers (network) that deliver webpages and other web content to a user based on the geographic locations of the user, the origin of the webpage and a content delivery server. Examples: Akamai, Cloudflare.
#### cloud computing
A general term for the delivery of hosted services over the internet.
#### colo
Abbreviation for co-location. The renting of space for housing computer equipment, usually in buildings specially designed to support a high density of computers and network connections, often called data centers, but also known as tele-houses or carrier hotel facilities.
#### CRC
#### Cloud Service Provider (CSP)
#### Cross Connect
#### data center (DC)
A physical facility with a large group of networked computer servers typically used by organizations for remote storage, processing, or distribution of large amounts of data. Key components of a data center include routers, switches, firewalls, storage systems, and servers.
#### dark fiber (DF)
#### demarc
#### DHCP
#### direct customer
Any direct Megaport customer that is not a member of the Megaport Partner Program.
#### DNS
The Domain Name System (DNS) is a hierarchical decentralized naming system for computers, services, or any resource connected to the internet or a private network. It associates various information with domain names assigned to each of the participating entities.
#### dot1q
See *802.1Q*: IEEE 802.1Q is the networking standard that supports virtual LANs (VLANs) on an Ethernet network. The standard defines a system of VLAN tagging for Ethernet frames and the accompanying procedures to be used by bridges and switches in handling such frames.
#### Direct Connect (DX)
AWS Direct Connect (DX) is a service solution that provides a dedicated and private network connection from your on-premises (branch office, data center, or co-location environment) to an Amazon Web Services (AWS) region, bypassing the internet service provider.
#### elastic interconnection
A term that defines a connection that provides businesses the flexibility to vary connectivity service requirements based on demand. Megaport customers can provision an elastic interconnection for as short as a day or as long as they need, with speeds ranging from 1 Mbps to several Gbps.
#### Ethernet Local Management Interface (E-LMI)
#### egress
Egress refers to the flow of data moving out of a private network into the public internet or another external network. This process is integral to network operations, especially in cloud environments where controlled data movement is important for security and efficiency.
#### endpoint
One end of an API communication channel that specifies the URI or URL of a server or service where you can access the resource. Includes any internet-enabled remote computing device that communicates with a TCP/IP network.
#### ExpressRoute (ER)
An Azure cloud integration option used to extend on-premises networks into the Microsoft cloud over a dedicated private connection. Megaport is a Microsoft Azure ExpressRoute partner.
#### Ethernet Virtual Private Line (EVPL)
EVPL allows for service multiplexing at the UNI (unlike EPL). This capability allows more than one EVC to be supported at the UNI where the EPL does not allow this. Second, an EVPL need not provide as much transparency of Service Frames as with an EPL (Definition: MEF).
#### fully qualified domain name (FQDN)
The complete domain name for a specific computer, or host, on the internet. The FQDN consists of two parts; the hostname and the domain name.
#### fast reroute (FRR)
A MPLS and IP resiliency technology to provide fast traffic recovery upon link or router failures for mission critical services. Upon any single link or node failures it is possible to recover affected traffic in the order of tens of milliseconds.
#### Firewall as a Service (FWaaS)
#### Generic Attribute Registration Protocol (GARP)
#### Google Cloud Interconnect (GCI)
#### Google Cloud Platform (GCP)
Google Cloud Platform is a suite of cloud computing services offered by Google that provides a series of features including computing, data storage, data analytics, machine learning, and a set of management tools.
#### Generic Routing Encapsulation (GRE)
#### Global Services Agreement (GSA)
The Global Services Agreement (GSA), the Service Schedule(s), the Acceptable Use Policy and Customer’s
Order(s) set out the terms and conditions that apply to Customer’s access to and use of the Services
and forms an agreement between Megaport and the Customer. See also the SLA which is a component of the GSA. [Megaport standard terms](https://www.megaport.com/legal/global-services-agreement/).
#### hybrid cloud
A cloud computing environment that uses a mix of on-premises, private cloud, and third-party public cloud services with orchestration between the two cloud platforms.
#### Infrastructure as a Service (IaaS)
#### Infrastructure as Code (IaC)
#### Internet Engineering Task Force (IETF)
An organization that develops and promotes voluntary internet standards, in particular the standards that comprise the internet protocol suite (TCP/IP). IETF has no formal membership or membership requirements. All participants and managers are volunteers with their work usually funded by their employers or other sponsors.
#### indirect customer
Any Megaport customer that is managed by a member of the Megaport Partner Program. Indirect customers work with partners to set up accounts, order services, and obtain billing and support. Otherwise known as managed accounts.
#### ingress
Ingress refers to the flow of data into a private network from an external source, typically the public internet. In cloud computing, managing ingress effectively is key to maintaining network integrity and security.
#### IP Address
#### Internet Protocol Security (IPsec)
#### IP Flow Information Export (IPFIX)
#### IPv4
IPv4 addresses are 32-bit numbers that uniquely identify a network interface on a device. An IPv4 address is typically written in decimal digits, formatted as four 8-bit fields that are separated by periods. A 32-bit address contains two primary parts: the network prefix and the host number. All hosts within a single network share the same network address.
#### IPv6
IPv6 addresses are 128-bit alphanumeric values that uniquely identify a network interface on a device. An IPv6 address consists of eight groups of four hexadecimal digits separated by ‘.‘ and each Hex digit representing four bits so the total length of IPv6 is 128 bits.
#### IP MTU (Maximum Transmission Unit)
#### Information Technology Infrastructure Library (ITIL)
The Information Technology Infrastructure Library (ITIL) is a set of practices for IT activities such as IT Service Management (ITSM) and IT Asset Management (ITAM) that focus on aligning IT services with the needs of the business.
#### IX
An Internet Exchange (known as IX or IXP for a given Internet Exchange point) is a physical infrastructure through which internet service providers (ISPs) and content delivery networks (CDNs) exchange internet traffic between their networks (autonomous systems). MegaIX is the Megaport IX product, and AMS-IX is the partner IX product offered in some geographies via the Cloud tile in the Megaport Portal.
#### jitter
#### Layer 1 (L1)
#### Layer 2 (L2)
#### Layer 3 (L3)
#### Link Aggregation Control Protocol (LACP)
#### Link aggregation group (LAG)
#### Link OAM
#### Letter of Authorization (LOA)
#### LR (Long Range)
An optical interface standard for a small form-factor pluggable (SFP) that can deliver 10 Gbps over roughly 10km. Megaport's standard for delivery of 10 Gbps Ports. See *LX* for the 1 Gbps equivalent. Uses 1310nm wavelength.
#### label-switched path (LSP)
A path through an MPLS network, set up by a signaling protocol such as LDP, RSVP-TE, BGP or CR-LDP. The path is set up based on criteria in the forwarding equivalence class (FEC).
#### LX (Long Wavelength)
An optical interface standard for a small form-factor pluggable (SFP) that can deliver 1 Gbps over roughly 10km. Megaport's standard for delivery of 1 Gbps Ports. See *LR* for the 10 Gbps equivalent. Uses 1310nm wavelength.
#### Media Access Control address (MAC address)
A Media Access Control address (MAC address) is a unique, 12-character alphanumeric attribute that is used to identify individual electronic devices on a network. An example of a MAC address is 01:02:0f:04:58:20.
#### Media Access Control security (MACsec)
#### managed account
An account that receives Megaport services and support through a Megaport partner. The partner can customize the features in the Megaport Portal to limit visibility and features for a managed account.
#### Megaport Cloud Router (MCR)
#### MD5
#### Multi-Exit Discriminator (MED)
#### MegaIX
MegaIX is Megaport's Internet Exchange service. Using MegaIX, networks can participate in multilateral peering via Megaport's route servers – a single BGP session can bring the majority of local IX routes without the effort of negotiating with individual peers.
#### Megaport Internet
#### Megaport SDN
Megaport’s neutral, software-defined network based global network comprising of cloud service providers, network service providers, and data center operators, accessed via the Megaport Portal or API.
#### Microsoft Azure ExpressRoute
#### meet-me room (MMR)
#### Multi-Protocol Label Switching (MPLS)
#### Multiple Spanning Tree Protocol (MSTP)
#### Megaport Virtual Edge (MVE)
#### multicloud
#### Multiplier (BFD)
#### Network Address Translation (NAT)
#### Network Function Virtualization (NFV)
#### net neutrality
A standard where internet service is treated as an essential service, and the principle that Megaport enables access to all service providers without favoring or blocking others.
#### network-to-network interface (NNI)
#### Network Virtual Appliances (NVA)
#### Next Generation Fire Wall (NGFW)
#### On-ramp
An on-ramp is a direct, private connection to a service provider's available resources, for example, via a Megaport connection. To ensure fast and reliable connections, the service provider maps these resources to their regions or zones, sets rate limits, manages per-customer VLAN capacity, and so on.
#### Open Systems Interconnection (OSI)
#### overlay network
A virtual network of nodes and logical links that are built on top of an existing network. The overlay network augments the underlay and provides traffic orchestration and the ability to enable business and security policies through a management console. The management console also provides visibility into the network.
#### PaaS
#### partner account
An account that directly manages the Megaport services, support, and billing for other accounts. The partner can customize the features in the Megaport Portal to limit visibility and features for a managed account.
#### Partner Program
The [Megaport Partner Program](https://www.megaport.com/partners/). The Megaport Partner Program makes it easy to add NaaS offerings to your cloud or managed services portfolio.
#### Pause frames (802.3x)
#### peering
#### ping
#### PLR
#### Port-based network access control (PNAC)
#### Port
#### Port diversity
#### provider edge (PE) router
#### PTD
Packet transfer delay (one-way latency measure). Packet transfer delay is the time taken by the physical layer at the source to send packets over a link.
#### Q-in-Q
#### rDNS
#### Receive Interval (BFD)
#### Resource Tags
Resource Tags allow you to add your own reference metadata to a Megaport service.
Every time you create or edit a service, you have the opportunity to create, update, or remove resource tags.
#### risers
(Generally vertical) shafts through which cable baskets are routed. Otherwise known as *verticals*.
#### Resource Public Key Infrastructure (RPKI)
#### route server (RS)
A route server provides a mechanism for the establishment of BGP routing exchanges in an Internet Exchange (IX or IXP). It simplifies the process of maintaining many peering partners across a network and also contributes to the network visibility and manageability. Route servers are generally deployed in pairs to allow for maintenance windows and general redundancy to support IX stability. Some offer a Looking Glass (LG) functionality to view which peers maintain which routes and allow troubleshooting on network routing choices.
#### Rapid Spanning Tree Protocol (RSTP)
#### RTBH
#### RTT
Round-trip time (RTT) is the length of time taken by a data packet to be sent to a destination, including the time it takes for an acknowledgment of that packet to be received back at the origin time. Also known as *ping* time.
#### rack units (RU)
A unit of measurement mainly used to describe the height of rack-mounted computer equipment (especially servers and routers) and the racks into which they are fitted. One RU is 1.75 inches or 4.445 centimeters. For example, 42RU indicates a 1.87m height cabinet.
#### Software as a Service (SaaS)
#### Secure Access Service Edge (SASE)
#### software-defined network (SDN)
Software-defined networking (SDN) is a network architecture that separates the control plane (which decides where traffic is sent) from the data plane (which forwards traffic to its destination). This decoupling enables centralized, programmable control of the network through software applications. SDN is commonly used in cloud environments, data centers, and service provider networks to simplify management, reduce operational costs, and respond quickly to changing business needs.
#### software-defined wide area network (SD-WAN)
#### Security as a Service (SECaaS)
Security as a Service (SECaaS) is a cloud-based model in which security services are delivered over the internet. Instead of deploying and maintaining security tools on-premises, organizations subscribe to security solutions hosted and managed by third-party providers.
#### service key
A service key is a code that is given by one Megaport account holder to another to connect two separate businesses together. Customers who have separate Megaport accounts can connect their Ports, MCRs, MVEs, and NAT Gateways to each other across the Megaport network, enabling business-to-business VXCs.
#### small form pluggable (SFP)
#### service-level agreement (SLA)
Part of a standardized service contract where a service is formally defined. Particular aspects of the service scope, quality, and responsibilities are agreed between the service provider and the service user. Referred to as the GSA in Megaport terms (Global Services Agreement).
#### single-mode optical fiber (SMOF)
#### Secure Service Edge (SSE)
#### Spanning Tree Protocol (STP)
#### Secure Web Gateway (SWG)
#### Supernetting
#### Transmission Control Protocol/Internet Protocol (TCP/IP)
A set of rules/protocols governing communications among all devices on the internet. More specifically, TCP/IP dictates how information should be packaged (packetized), sent, and received, as well as how to traverse connected networks to reach its ultimate destination.
#### traceroute
#### transit
Commodity internet capacity. As distinct from IX routes (specific), transit capacity (a generally paid service) indicates the general default route for internet traffic when routes are otherwise unknown at a settlement free peering exchange.
#### Transmit Interval (BFD)
#### User Datagram Protocol (UDP)
#### underlay network
A physical infrastructure that provides traditional physical Layer 2 and Layer 3 connectivity between gateways, routes, switches, and so on in a network.
#### Virtual Carrier Grade Network Address Translation (vCGNAT)
Virtual Carrier Grade Network Address Translation (vCGNAT) is a software-based, virtualized version of Carrier Grade NAT. It allows Internet Service Providers (ISPs) and mobile carriers to share a single public IPv4 address among thousands of subscribers by running the translation as a Virtual Network Function (VNF) on standard cloud or data center servers, rather than on expensive, proprietary hardware.
#### virtual LAN (VLAN)
#### virtualized network functions (VNFs)
#### virtual private cloud (VPC)
A virtual private cloud (VPC) is a secure, isolated private cloud hosted within a public cloud. VPC customers can run code, store data, host websites, and do anything else they could do in a normal private cloud, but the private cloud is hosted remotely by a public cloud provider.
#### Virtual Private LAN Service (VPLS)
A way to provide Ethernet-based multipoint to multipoint communication over IP or MPLS networks. It allows geographically dispersed sites to share an Ethernet broadcast domain by connecting sites through pseudo-wires.
#### virtual private network (VPN)
#### Zero Trust Network Access (ztna)
#### Virtual Cross Connect (VXC)
#### XCON or XC
Abbreviation for Cross Connect. A connection scheme between cabling runs, subsystems, and equipment using patch cords or jumpers that attach to networking equipment.
# What Users Can View and Access
Source: https://docs.megaport.com/partners/access/index
This help topic describes the differences in feature accessibility and viewing privileges for partner and managed accounts.
This topic describes the differences in feature accessibility and viewing privileges for partner and managed accounts.
When a partner account updates a setting in one of its managed accounts, all other managed companies will inherit the updated value for the setting unless they have an existing override in place.
Partner accounts can always view managed account settings and will receive email notifications about any service changes made by a managed account, unless they opt out of the notifications. For more information, see [Configuring Email Notifications](/partners/account/notifications).
## Feature access and views by account type
This table describes the visibility and accessibility settings for partners and managed accounts, as configured by your Megaport Sales Team. To request changes to the managed account settings, contact your Megaport Sales Team.
| **Display Setting** | **Accessibility** | **Configurable for Partner-Supported Managed Accounts?** | **Configurable for Megaport-Supported Managed Accounts?** | **Result** |
| - | - | - | - | - |
| **Company Profile** | By default, the [company profile](/setting-up/company-profile) is visible to the partners but does not appear for managed accounts. | Yes | Yes | When enabled, both partner and managed account users can view the company profile. Managed account users cannot edit the company profile. |
| **Dashboard** | By default, the dashboard is visible to the partner account after login, but it does not appear for managed accounts. The [Services page](/partners/services/viewing-services) appears in place of the dashboard for managed accounts. | Yes | Yes | By default, the dashboard is turned on for partners. When enabled for managed accounts, both partner and managed account users can view the dashboard.
When the dashboard is enabled and the managed account user has configured services such as a Port, the Services page appears in place of the dashboard after login. If no services are configured, the dashboard appears. |
| **Megaport Marketplace Profile** | The [Megaport Marketplace profile](/marketplace/profile) is visible to partner accounts only. Managed accounts are not listed in the Megaport Marketplace. | No | No |
Partners can view the Marketplace Profile.
Managed accounts can view the Marketplace and create connections to Marketplace services, but they cannot make a new service visible on the Megaport network for inbound connection requests.
Managed accounts cannot view or edit the Marketplace profile information.
|
| **Pricing** | By default, pricing is visible to the partners but does not appear for the managed accounts. Any changes to Megaport services made by a managed account will not include pricing estimates or details. | Yes | Yes |
When enabled for managed accounts, both partner and managed account users can view the pricing details.
When pricing is enabled for managed accounts, retail prices are shown.
|
| **Billing Market** | The [billing market](/finance/enabling-market) is accessible to partners only. | No | No | Partner accounts can access and modify a billing market. A message informs a managed account user that the market cannot be added unless they are logged in to a partner account.
**Note**: A change to a billing market (by the partner account) affects all of the managed accounts as well, including Megaport promotional discounts. |
| **Chat Support** | By default, for partner-managed accounts, chat support is enabled for the partners and turned off for managed accounts. For Megaport-supported managed accounts, chat support is turned off for the partners and turned on for managed accounts. | Yes | Yes | When enabled for managed accounts, both partner and managed account users can use chat. |
| **Service Approval Queue** | By default, managed account users with the appropriate roles can order new services, change existing services, and terminate services. For information about who can manage services, see [Managing User Roles](/partners/account/profiles). | Yes | No | When enabled, managed users cannot order new services, change existing services, or terminate services without approval from the partner. |
| **Notifications** | Notifications are enabled for partners and Megaport-supported managed accounts. Notifications are turned off for partner-supported managed accounts. | No | Yes |
Partners receive notifications they subscribe to.
Partners can unsubscribe from managed account notifications.
Megaport-supported managed accounts receive notifications they subscribe to for their own managed accounts and services.
Both partner and managed accounts receive Security and People notifications.
Financial and company notifications never go to managed accounts.
When multiple partner and managed account services are impacted by a planned event, the partner receives one email listing services under each account name.
For more information, see [Configuring Email Notifications](/partners/account/notifications).
|
# Viewing Activity Logs
Source: https://docs.megaport.com/partners/account/activity-logs
This help topic describes the Megaport Portal activity logs and how to view activity logs for your Megaport Portal account.
The Activity Log options on the Settings menu allow you to view activities that users have performed. The **User Activity** option shows activities only for the logged-in user, while the **Company Activity** option shows the activities of all users in the current company.
Users with any Portal role can view the **User Activity** option, however, only Company Admins can view the **Company Activity** option. For more information, see [Managing User Roles](/partners/account/profiles).
The Activity Logs record all activities that occur, and include the date and time of each event. Activity logs can provide an audit trail to prove any malicious activity via compromised accounts, show evidence of activities performed by API keys, and can be useful when troubleshooting a system issue.
Activity Log events are retained for 6 months.
## What information is logged
The system logs these activities:
* Logging in to the Portal (successful and failed)
* Logging in to the Portal with Single Sign-On
* Logging out of the Portal
* Enabling, resetting, and disabling Multi-Factor Authentication (MFA) for a user
* Configuring, deploying, and updating services (successful or failed)
* Requesting approval for creating, changing, and terminating services
* Withdrawing requests for creating, changing, and terminating services
* Approval or rejection of requests to create, change, and terminate services
* Approving, denying, or canceling a speed change
* Approving or denying connections
* Updating Port terms
* Terminating services
* Registering payment cards, updating and removing cards, and making payments
* Setting up and updating service keys
* Creating, updating, and deleting webhook endpoints
* Updating user profiles
* Creating a company profile or Megaport Marketplace profile
* Setting up and updating custom branding
* Setting up and updating billing markets
* Saving and managing configurations
* Updating user notification settings
* Managing users
* Locking and unlocking services
* Encountering issues with the ordering process
* Creating and updating a managed account
* Creating and updating Prefix Filter and Packet Filter lists
* API calls from external sources (such as customer integrations)
* Whether the activity is created by an API key user
* The client ID of the API key if the activity was created by an API key user
* The type of service for which the activity log is being created
* The UID of the service for which the activity log is being created
## What information isn’t logged
The Activity Log does not provide usage or billing information for a Megaport service, such as performance for a VXC or IX, or how much it costs. For more information about VXC billing, see [VXC Pricing and Contract Terms](/finance/vxc-pricing).
## What logs can users view
The following table shows the access and functionality available in the **User Activity** and **Company Activity** pages, based on user role.
| **User Role** | **Activity Log Functionality** |
| - | - |
| Non Admin (All role types except Company Admin) | **User Activity** Can view their own activities. Can filter activities by:
Activity name
Date
|
| Company Admin | **User Activity** Can view their own activities. Can filter activities by:
Activity name
Date
**Company Activity** Can view:
Activities of all users in the company
Activities of all API keys associated with the company. The User column displays the API key name.
Activities created by Megaport staff, for example, when performing support investigations
All system-generated activities
Can filter activities by:
Date
User type
User
Activity name
|
## Viewing activity logs
Depending on your role, you can perform the following actions to locate and view specific activity logs:
* **Sort** -- All users can sort activity logs by date/time.
* **Filter** -- All users can filter activity logs by date and activity name. Company Admins can also filter activity logs by user type or specific user.
* **Search** -- Company Admins can use a free text search on the Company Activity page to locate specific activity logs. The search matches all log details, including user names, activity names, and full descriptions in the **More Details** option.
**To view the activity log table**
1. Log in to a partner account.
2. Choose:
* **User Menu > User Settings > User Activity** -- to view your own activities, or
* **User Menu > Admin Settings > Company Activity** -- to view company-wide activities.
The Activity Log page appears, showing activities by date, user type and user name (Company Activity only), and activity name.
3. Click **More Details** to view additional information about an activity, including an expanded description to further explain the action that triggered the log entry.
**To sort activities**
You can sort activity logs by date and time, in either ascending or descending order.
* In the Activity Log page, click the small up/down triangle next to the **Date** column heading.
The activity log table reloads.
* Click the up/down triangle again to reverse the sort order.\
The up or down triangle next to the **Date** column heading indicates the current bidirectional sort order.
**To filter activities**
You can filter all activity logs by date and activity name. You can also filter Company Activity logs by user type and user.
1. In the Activity Log page, click the filter icon next to the column heading on which you want to filter.\
You can filter on activity date, user type, user, and activity name.
2. Filter the activity log table:
* **To filter by date** -- Select a single date or select two dates to filter between the date range.
* **To filter by user type** – Select a user type from the list.
* **To filter by user** -- Search for and select a user name.
* **To filter by activity name** -- Search for and select an activity name.
3. Click **Apply**.\
The filter is added to the top of the activity log table. You can save one filter per column at a time. Any saved filters are not retained if you leave the activity page and then return to the page.
**To search for activities**
Company Admins can use a free text search on the Company Activity page to locate specific activity logs. The search matches all log details, including user names, activity names, and full descriptions in the **More Details** option. Any partial or complete matches are included in the search results.
1. Choose User Menu > Admin Settings > Company Activity.
2. In the Company Activity page, enter the search text in the **Search** field on the right. For example, enter **IDP** to search for any SSO sign up or login activities.\
Activity logs matching your search update in real-time as you type.
3. Use the sort, filter, and pagination controls to refine the search results and locate specific activity log entries.
## Helpful references
* [Managing User Roles](/partners/account/profiles)
# Managing Minimum Term Renewal
Source: https://docs.megaport.com/partners/account/auto-renew
This help topic describes how a partner account Company Admin can modify the default setting of automatic contract renewals for all of their managed accounts.
This topic describes how partner account Company Admins can modify the default automatic contract renewals setting for all of their managed accounts.
As a Company Admin, you can also override the global Minimum Term Renewal default setting at the individual managed account level.
## What is Minimum Term Renewal?
The Minimum Term Renewal feature ensures that a service contract automatically renews for the same duration and discounted price at the end of its term.
By default, Minimum Term Renewal is enabled, that is, new services with a minimum term of 12, 24, 36, 48, or 60 months are set to renew automatically for the same duration and discounted price.
As a Company Admin, you can change the default Minimum Term Renewal setting at any time. Changing the default setting only affects new service orders and does not affect existing services. Users can override the default setting for each service by selecting or clearing the default setting at any time.
The image below shows the default enabled state for the Minimum Term Renewal setting for a new service.
* **If Minimum Term Renewal is enabled for the service:**
* No action is required. The service automatically renews for the same term length at the same discounted price.
* If a customer changes the VXC speed, the service is repriced based on the current market rate.
* For a VXC, the term discount is a fixed monthly amount calculated based on the percentage discount associated with the selected term length and committed speed. This discount remains fixed throughout the contract term, regardless of any speed changes.
* To opt out of automatic renewal, disable Minimum Term Renewal in the Megaport Portal before the contract expiry date. The service will then continue on a month-to-month basis at the same market rate.
* The early termination fee (ETF) for canceling a contract early remains 100% of the remaining term cost.
* **If Minimum Term Renewal is disabled for the service:**
* To continue the service under a minimum term contract, log in to the Megaport Portal before the contract expires and renew the service for 12, 24, 36, 48, or 60 months at the same discounted market rate.
* If no action is taken, the service continues on a month-to-month basis at the same market rate for Ports or the pay-as-you-go rate for virtual services.
## Notification email
A notification email is sent one month before the contract end date, informing customers of their Minimum Term Renewal options.
* **Recipients** -- All customer contacts in the Megaport Portal, that is, all primary company email addresses receive the email.
* **Managed accounts** -- Term renewal emails are sent to all users of the partner company, but not to users of the managed company.
* **Can customers disable the renewal emails?** -- No, these are critical service notifications and cannot be disabled.
## Configuring the default Minimum Term Renewal setting for new services
The override only impacts the ordering of new services. Existing services are not affected.
**To override the global Minimum Term Renewal setting for a specific managed account**
1. Log in as a Company Admin.
2. Select **Partner Admin**.
3. From the Manage Accounts page, find the account to modify.\
You can use the filter at the top of the page to focus the list.
4. Click **Edit** next to the managed account.
The Account Overview for the managed account is displayed.
5. Select the **Feature Configuration** tab.
6. Set the default state for Minimum Term Renewal for the managed account:
* When turned on, Minimum Term Renewal will be enabled by default for new services ordered by users of that managed account. Contracts are automatically renewed for the same term and discounted price.
* When turned off, Minimum Term Renewal will be disabled by default for new services ordered by users of that managed account. The contract will not renew automatically at the end of its term, unless the user selects the option during the order process.
Changes are saved automatically and take effect immediately.
# Creating a Managed Account
Source: https://docs.megaport.com/partners/account/create-managed
This help topic describes how to add managed accounts under a partner account.
This topic describes how to add managed accounts under a partner account.
Partner account Company Admins can create managed accounts and onboard managed account users.
* All managed accounts must be created as new.
* You cannot convert an existing customer account to a managed account, and a managed account cannot be converted to a direct customer account.
**To create a managed account**
1. Log in as a Company Admin.
2. Click **Partner Admin** in the left navigation.
3. Click **Create Managed Account**.
4. Provide these details:
* **Account Name** -- Specify a unique name for the account that is easily identifiable, particularly if you plan on having more than one account.
The description length is from 1 to 128 characters. To keep the company name anonymous, enter an alias name. The alias name appears on the Company Profile page.
Managed account users supported by a partner can view the company profile and the company name or alias is visible to managed account users.
* **Account Reference** -- Enter the managed account reference.
The partner assigns a unique reference to each managed account. The reference length is from 1 to 128 characters. The reference is typically an identifier used in partner systems (for example, CRM or billing). The reference is shown on the invoices under *Your Reference*. The reference also identifies the account in email notifications.
* **Technical Support Phone Number** -- Enter the phone number of your internal support team.
Megaport validates the number against the billing market format of your Billing Contact phone number.
Megaport requires a technical support phone number and a technical support email address for Megaport-supported managed accounts, but they are optional for partner-supported managed accounts. For more information, see [Providing Support Contact Details](/partners/tech-support-details-partner).
* **Technical Support Email** -- Enter the email address of your internal support team.
Megaport validates the email format and address against the email address provided during account sign up.
5. Click **Create**.\
The Feature Configuration prompt is displayed.
This prompt allows you to turn the following features on or off for the managed account:
* **Minimum Term Renewal** -- Enable automatic renewal of service contracts at the same duration and price. For more information, see [Managing Minimum Term Renewal](/partners/account/auto-renew).
* **Service Approval Queue** -- Require partner approval before managed account users can order services, make changes to existing services, or terminate services. For more information, see [Service Approval Queue](/partners/services/service-approval-queue).
* **Show Pricing** -- Display retail pricing information to managed account users. For more information, see [What Account Users Can View and Access](/partners/access).
* **Cross Connect** -- Allow managed account users to order Cross Connects. This option is available only for Megaport supported managed accounts. For partner-supported managed accounts, the option is grayed out.
When you have configured these settings, close the prompt. Your selections are automatically saved.
You can create as many managed accounts as you like. The accounts appear in a list on the Managed Accounts page.
You can filter the list and sort the columns.
**To sort the list by column**
* Click the up/down triangles next to a column heading.\
The table columns reload, if necessary.
* Click the heading again to reverse the order.\
A small up or down triangle reflects the current bidirectional sort order.
6. Click **View Services** to switch into the managed account and see all configured account services, such as Ports.\
For more information, see [Viewing Services](/partners/services/viewing-services).
7. Click **Edit** to change account settings and technical support contact details.
If you refresh the browser window when logged in as a partner and viewing a managed account, the Portal logs you out and back in again. The browser window returns to the partner context instead of the managed account you were viewing before the refresh.
### Next steps
Now that you’ve created a managed account, the next steps are to add users and order services, such as Ports, Virtual Cross Connects (VXCs), Megaport Virtual Edges (MVEs), and so on.
* See [Adding and Modifying Managed Account Users](/partners/account/user-management) for information about adding and managing users.
* See [Creating and Ordering Services](/partners/services/creating) for information about new service orders for partner accounts or managed users.
# Adding Custom Branding
Source: https://docs.megaport.com/partners/account/custom-branding
This help topic describes how to set up custom branding on the Partner Portal.
As a partner, you can strengthen your presence on the Portal by adding your logo to the Portal banner. Your logo will appear in the top left of the Portal, next to the Megaport logo, for your account and your managed accounts. If you click your logo, you will be taken to your website. You can also add your logo to the emails that Megaport sends to your managed accounts.
For information about configuring custom branding using the API, see [Customizing your Branding with the API](/partners/api/branding-profile).
* Custom branding applies to your account and all managed accounts. You cannot enable it for individual managed accounts.
* Custom Portal and email branding both require a saved branding profile and can be enabled independently.
**To add custom branding**
1. Log in as a Company Admin.
2. Choose Partner Admin > Custom Branding.
3. Click **Set Up Custom Branding**.\
The Custom Branding Settings page appears.
4. Add your branding details:
* **Branding Display Name** -- Enter the name you want to display.
* **Navbar Logo Asset** -- Upload the logo you want to display in the Portal banner.\
This logo will appear in the top left of the Portal, next to the Megaport logo, for your account and your managed accounts. After you select a logo, you can resize it to fit the display area.\
Images can be up to 2 MB and in one of the following formats: PNG, JPEG, SVG, or WebP.
* **Brand Website URL** -- Enter the URL of your website. This URL opens when users click your logo in the Portal banner.
After you add your branding details, the **Navbar Preview** shows how your branding will appear in the Portal banner.
5. Click **Enable Custom Email Branding** if you also want to show your logo alongside the Megaport logo in the emails that Megaport sends to your managed accounts.
6. Click **Create Custom Branding** to save your custom branding settings.\
The *Custom branding saved successfully* message appears with these options:
* **Later** -- Return to the Custom Branding Settings page without enabling the branding. You can enable the branding later by clicking **Enable Custom Portal Branding** on the Custom Branding Settings page.
* **Enable Now** -- Enable the branding and make it visible in the Portal banner for your account and your managed accounts.
# Configuring Account Settings
Source: https://docs.megaport.com/partners/account/feature-configuration
This help topic describes how to configure features for managed accounts, including service approval, pricing visibility, and minimum term renewal settings.
This topic describes how to configure features for your managed accounts, including service approval requirements, pricing visibility, and minimum term renewal settings.
Partner account Company Admins can configure these features individually for each managed account to control service ordering workflows and information visibility.
## Feature configuration options
You can configure the following features for each managed account:
* **Minimum Term Renewal** -- Set the default behavior for automatic renewal of service contracts at the same duration and price. For more information, see [Managing Minimum Term Renewal](/partners/account/auto-renew).
* **Service Approval Queue** -- Require partner approval before managed account users can order new services, make changes to existing services, or terminate services. For more information, see [Service Approval Queue](/partners/services/service-approval-queue).
* **Show Pricing** -- Display retail pricing information to managed account users. When enabled, managed account users can view:
* monthly rates and term costs during service ordering.
* pricing details in service approval requests.
* cost estimates for service changes.
When disabled, all pricing information is hidden from managed account users, including the pricing section in order requests. For more information about pricing visibility, see [What Users Can View and Access](/partners/access).
* **Cross Connect** -- Control whether Megaport-supported managed account users can add a Megaport-provisioned Cross Connect when ordering a new Port. When set to **Allowed**, eligible users can request a Cross Connect while ordering a Port. When set to **Not Allowed**, they can still arrange a Cross Connect directly with the data center. You can configure this setting only for Megaport-supported managed accounts, and independently of the Service Approval Queue. For partner-supported managed accounts, the option is grayed out. For more information about Cross Connects, see [Ordering a Cross Connect](/connections/cross-connect).
## Navigating to feature configuration
### During managed account creation
When you are creating a new managed account, the Feature Configuration prompt appears after you click **Create**, allowing you to configure features during account creation.
For step-by-step instructions on creating a managed account, see [Creating a Managed Account](/partners/account/create-managed).
### For existing managed accounts
**To access feature configuration for an existing managed account**
1. Log in to the Megaport Portal as a Company Admin.
2. Click **Partner Admin** in the left navigation.
3. From the Managed Accounts page, find the account you want to configure.\
You can use the filter at the top of the page to focus the list, or sort by column.
4. Click **Edit** next to the managed account.\
The Account Overview for the managed account is displayed.
5. Select the **Feature Configuration** tab.\
The feature configuration settings for that managed account are displayed.
6. Activate or deactivate features as required.\
Changes are saved automatically and take effect immediately.
## Viewing feature settings across all managed accounts
The Partner Admin page displays a table view of all your managed accounts and the features enabled or disabled for each account, making it easy to review settings across accounts at a glance.
**To view feature settings for all managed accounts**
1. Log in as a Company Admin.
2. Click **Partner Admin** in the left navigation.
The table displays each managed account with columns showing whether each feature is enabled or disabled.
## Helpful references
* [Creating a Managed Account](/partners/account/create-managed)
* [Managing Minimum Term Renewal](/partners/account/auto-renew)
* [Service Approval Queue](/partners/services/service-approval-queue)
* [What Account Users Can View and Access](/partners/access)
# Switching Account Types
Source: https://docs.megaport.com/partners/account/moving
This help topic describes how to switch between a partner account and managed accounts using the company switcher.
This topic describes how to switch between a partner account and a managed account using the company switcher.
## Locating the company switcher
The company switcher appears in the top left of the Megaport Portal as part of the breadcrumb trail.
* If you belong to only one account, your company name appears as plain text and no drop-down list is shown.
* If you belong to more than one account, for example, a partner account with managed accounts, click your company name to open the switcher.
## Switching from a partner account to a managed account
The Megaport Partner Program offers two account models that enable partners to create account hierarchies for the Partner Program services: partner and managed.
**To switch from a partner account to a managed account**
1. While logged in to the partner account, click the company switcher.
2. Under Partner, select an account. If available, use the **Filter Accounts** field to find an account.\
Specify part of the account name or account ID to filter the list.
The Megaport Portal switches to the selected account immediately, with no confirmation step. The company switcher shows which managed account you are currently viewing.
* Every open Megaport Portal tab switches to the selected account. Tabs displaying pages specific to the previous account are redirected to the home page of the selected account.
* Switching between managed accounts does not require you to complete MFA again.
## Showing all managed accounts
You can always expand or collapse the list of managed accounts.
If a partner account has more than three managed accounts, only the first three appear when you open the company switcher, with a **Show all** button to reveal the rest. This keeps a large list of managed accounts from crowding out other partner accounts if you belong to more than one.
## Switching from a managed account to a partner account
You can switch back to the partner account from any managed account using the company switcher.
**To switch from a managed account to the partner account**
1. While in a managed account, click the company switcher.
2. Under Partner, select your partner account.
The Megaport Portal switches immediately and returns you to the page you were on, now in the partner account.
## Switching from a managed account to another managed account
There is no direct switch between managed accounts. Switch back to the partner account first, then select the other managed account.
**To switch from a managed account to another managed account**
1. While in a managed account, click the company switcher, then select your partner account.
2. Repeat the steps in [Switching from a partner account to a managed account](#partner-to-managed) to select another managed account.
## Helpful references
* [Creating a Managed Account](/partners/account/create-managed)
* [Megaport Portal Dashboard](/dashboard)
* [Partner-Managed Accounts](/partner/managed)
* [Partner Program Account Hierarchy](/partners/acct-hierarchy)
* [Understanding the Services Page](/partners/services-page)
# Configuring Email Notifications
Source: https://docs.megaport.com/partners/account/notifications
This help topic describes how to review and configure Megaport email notifications.
Registered Megaport Partners and users can manage email notification subscriptions in the Megaport Portal. Email notifications are categorized into these groups:
* Financial
* Company
* Ordering
* Services
* Service Status
You can choose to receive email notifications or opt out for each notification type, with some exceptions by account type.
Here are the email notification settings by account type:
| **Account Type** | **Supported By** | **Default Notification Settings** | **Configurable?** | **Notes** | |
| :- | :- | :- | :-: | :- | - |
| Direct | Megaport | Enabled for all categories except Service Status. | **✓** | | |
| Partner | Partner | Enabled for all categories except Service Status. | **✓** | Partner accounts cannot disable managed account notifications. | |
| Partner | Megaport | Enabled for all categories except Service Status for both partner and managed accounts. | **✓** | Partner accounts can receive partner-only notifications or partner and managed account notifications. Partner notifications are sent to Megaport. | |
| Managed | Megaport | Disabled for all categories. | **✓** |
Managed account users are given access to Services, Ordering, and Service Status notifications for their own managed account and services.
Partner, Financial, and Company notifications do not appear.
Port and service re-terming notifications that a managed user is not subscribed to are sent to the partner.
| |
| Managed | Partner | Disabled for all categories. Notification settings are hidden. | *X* | | |
Megaport sends maintenance event notifications directly to managed accounts supported by Megaport. For partner-supported managed accounts, your partner will communicate with you about any maintenance events that affect your account. Megaport sends security and people notifications directly to anyone impacted.
Megaport sends Service email notifications once per hour.
**To configure email notification preferences**
1. Log in to a partner account with Partner Admin privileges.
2. Choose User Menu > User Settings > Notifications.\
Megaport customizes the notification groups by account type.
* Direct accounts see all notification settings.
* Partner-supported managed accounts cannot access any notification settings.
* Megaport-supported managed accounts have access to their own Services, Ordering, and Service Status notification settings.
* Megaport-supported partners see partner notification options and can select Partner and Managed to also subscribe to their managed account notifications.
3. Click a notification group to view all of the individual email notification types in that group.\
The list of events that trigger notifications in that group appear.
4. Select the notification group check box to subscribe to all notifications in that group, or subscribe to individual notification types.\
Any notification subscription changes are automatically saved.
## Default email notifications
Partner and managed account users receive the following People and Security email notifications by default. These categories are not configurable.
| **Category** | **Event** |
| - | - |
| People | When an email is being validated. |
| | When a user registers with a company. |
| | When a user enables two-factor authentication. |
| | When a user requests the secret for two-factor authentication. |
| Security | When a person tries to log in but fails. |
| | When a person registers. |
| | When a user requests a password reset. |
## Helpful references
* [Adding and Modifying Managed Account Users](/partners/account/user-management)
* [Managing User Roles](/partners/account/profiles)
* [Network Maintenance Notifications](/partners/support/maintenance)
# Managing User Roles
Source: https://docs.megaport.com/partners/account/profiles
This help topic describes how to manage roles for the users of your managed accounts.
This topic describes user roles within managed accounts that allow different levels of access privilege.
When logged in to a partner account, you can assign user roles to control the actions and permissions of users in managed accounts. The actions and permissions change if the Service Approval Queue feature is active. These tables summarize each user role and its supported functionality, indicated by a **✓**.
For information about the Service Approval Queue feature, see [Service Approval Queue](/partners/services/service-approval-queue).
Only Company Admins can create managed accounts and onboard managed account users.
|
**Action** | **Company Admin** | **Technical Admin** | **Technical Contact** | **Finance** | **Financial Contact** | **Read Only** |
| - | :-: | :-: | :-: | :-: | :-: | :-: |
| Create managed account | **✓** | | | | | |
| Onboard managed account users | **✓** | | | | | |
| Design services | **✓** | **✓** | **✓** | **✓** | **✓** | **✓** |
| Submit new services for approval | **✓** | **✓** | | **✓** | | |
| Submit service changes for approval | **✓** | **✓** | | **✓** | | |
| Submit service terminations for approval | **✓** | **✓** | | **✓** | | |
| Withdraw a service approval request | **✓** | **✓** | | **✓** | | |
| View services | **✓** | **✓** | **✓** | **✓** | **✓** | **✓** |
| Lock and unlock services | **✓** | | | | | |
| Create, view, and edit service keys | **✓** | **✓** | | **✓** | | |
| View usage | **✓** | **✓** | **✓** | **✓** | **✓** | **✓** |
| Create, view, and update users | **✓** | | | | | |
| Update user details | **✓** | **✓** | **✓** | **✓** | **✓** | **✓** |
| View User Activity logs | **✓** | **✓** | **✓** | **✓** | **✓** | **✓** |
| View Company Activity logs | **✓** | | | | | |
Here are some details to consider when creating user roles:
* **Company Admin** – We recommend limiting the number of Company Admins to only those who require full access, but defining at least two Company Admins for redundancy.
* **Technical Admin** – This role is for technical users who know how to create and approve orders.
* **Technical Contact** – This role is for technical users who know how to design and modify services but don't have the authority to approve orders.
* **Finance** – Finance users should have a financial responsibility within the organization while also understanding the consequences of their actions if they terminate or approve services.
* **Financial Contact** – This user role is similar to the Finance role without the ability to place and approve orders, terminate services, or administer service keys.
* **Read Only** – Read Only is the most restrictive role. Note that a Read Only user can view service details which you may want to keep secure and private. A user with the read-only role can view service details which might contain information about the service that you want to keep secure and private.
You can add user roles when you create a new user, or you can edit user information to change their role. For more information about adding a new user, see [Adding and Modifying Managed Account Users](/partners/account/user-management).
Only Company Admins can edit user credentials.
**To manage user roles and permissions**
1. Log in as a Company Admin.
2. Choose User Menu > Admin Settings > Manage Users.
The Manage Users page appears. This page lists existing users and you can add a new user or edit existing user privileges and contact information.
3. Click (Edit) to modify an existing user’s role or click **New User** (at the bottom of the page) to set up a new user and define their role.
4. Select the role for the user.
5. Click **Save**.
# Adding and Modifying Managed Account Users
Source: https://docs.megaport.com/partners/account/user-management
This help topic describes how to manage users for a managed account.
Partner account Company Admins can create and edit managed account users, assign roles, and activate/deactivate users. The maximum number of users you can add per account is 100.
**To create a new user**
1. Log in as a Company Admin.
2. Choose User Menu > Admin Settings > Manage Users.
3. Click **New User**.
4. Complete all fields.
The user email address is required for registration.
The role determines what actions the user can perform in the Portal through their access permissions. For more information about user roles, see [Managing User Roles](/partners/account/profiles).
5. Click **Save**.\
When you create a new user, the Portal sends the user an email with instructions for creating a password and logging in.
If a managed account user does not receive the set password notification or it has expired, they can go to Portal login screen and select the Forgot Password option using the same email address to generate the reset password email.
For existing users, you can edit the user profile and also activate and deactivate access. This allows for both pre-provisioning, fast enablement, and suspension of user access to the Portal.
**To modify an existing user**
1. From the Manage Users page, find the user to modify.\
You can use the filter at the top of the page to focus the list.
2. Click (Edit) next to the user entry.
3. After making changes, click **Save**.
# Partner Program Account Hierarchy
Source: https://docs.megaport.com/partners/acct-hierarchy/index
This help topic describes the Partner Program account hierarchy.
This topic describes the relationships between partner and managed accounts in the Partner Portal.
## Account levels
The Partner Program offers two account types that enable partners to create an account hierarchy for the Partner Program services: partner and managed.
This image shows the account hierarchy, billing flow, and user role permissions for partner and managed accounts. For more information about the user roles, see [Managing User Roles](/partners/account/profiles).
# Adding and Modifying Partner Account Users
Source: https://docs.megaport.com/partners/add-partner-users/index
This help topic explains how to add users to a partner account.
Partner account Company Admins can create and edit users, assign roles, and activate/deactivate users. The maximum number of users you can add per account is 100.
**To create a new user**
1. Log in as a Company Admin.
2. Choose User Menu > Admin Settings > Manage Users.
3. Click **New User**.
4. Complete all fields.\
The user email address is required for registration and notifications. The role determines what actions the user can perform in the Portal and their access permissions. For more information about user roles, see [Managing User Roles](/partners/account/profiles).
5. Click **Save**.\
When you create a new user, the Portal sends them an email with instructions for creating a password and logging in.
If an account user does not receive the set password notification, they can go to Portal login screen and select the Forgot Password option using the same email address to generate the reset password email.
For existing users, you can edit the user profile and also activate and deactivate access. This allows for both pre-provisioning, fast enablement, and suspension of user access to the Portal.
**To modify an existing user**
1. From the Manage Users page, find the user to modify.\
You can use the filter at the top of the page to focus the list.
2. Click (Edit) next to the user entry.
3. After making changes, click **Save**.
To edit your own user name (the user name you are logged in as), choose User Menu > User Settings > Profile. In the User Profile page, you can also enable MFA for your account. For more information, see [Securing your account with MFA](/setting-up/manage-profile#securing-your-account-with-mfa).
# Customizing your Branding with the API
Source: https://docs.megaport.com/partners/api/branding-profile
This help topic describes how to configure custom branding for your partner company using the Branding Profile API.
Custom branding lets you display your company logo, name, and website in the Portal for your managed accounts.\
For more information about custom branding, see [Adding Custom Branding](/partners/account/custom-branding).
The branding profile API lets you create, retrieve, and update custom branding.
## Prerequisites
Before you begin, ensure that you have a valid access token. For more information, see [Creating an API Key](/api/api-key).
## Authorization requirements
The branding profile endpoints have the following authorization requirements:
| **Endpoint** | **Account Type** |
| - | - |
| GET (Retrieve) | Partner or Managed Account |
| POST (Create) | Partner only |
| PUT (Update) | Partner only |
When a managed account retrieves a branding profile, the API returns the parent partner's branding profile.
## Retrieving a branding profile
To retrieve a branding profile, send a `GET` request to `/v3/companies/{companyUid}/branding-profile`.
### Response
A successful request returns a `200 OK` response with the branding profile details:
| **Field** | **Type** | **Description** |
| - | - | - |
| `companyBrandingName` | string | The display name for branding. |
| `primaryLogoKey` | string | The storage key for the uploaded logo image. |
| `webUrl` | string | The company website URL. |
**Example response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Branding profile found",
"data": {
"companyBrandingName": "Partner Company",
"primaryLogoKey": "primary/a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"webUrl": "https://partner-company.com"
}
}
```
### Error responses
| **Code** | **Description** |
| - | - |
| `401 Unauthorized` | Authentication required. |
| `403 Forbidden` | The user's account type is not Partner or Managed Account. |
## Creating a branding profile
To create a branding profile, send a `POST` request to `/v3/companies/{companyUid}/branding-profile`.
### Request
| **Parameter** | **Type** | **Required** | **Description** |
| - | - | - | - |
| `companyBrandingName` | string | Yes | The display name for branding. Must be 1-80 characters and cannot be blank or whitespace-only. |
| `primaryLogoImage` | string | Yes | The logo image as a base64-encoded data URI. Format: `data:image/\{type};base64,\{encoded-data}`. Supported image types: PNG, JPEG, SVG, and WebP. Maximum size: 2 MB. |
| `webUrl` | string | Yes | The company website URL. Must be a valid URL including the protocol (`http://` or `https://`). |
**Example request body**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"companyBrandingName": "Partner Company",
"primaryLogoImage": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR42mNk+M9QDwADhgGAWjR9awAAAABJRU5ErkJggg==",
"webUrl": "https://partner-company.com"
}
```
### Response
A successful request returns a `201 Created` response with the branding profile details:
| **Field** | **Type** | **Description** |
| - | - | - |
| `companyBrandingName` | string | The display name for branding. |
| `primaryLogoKey` | string | The storage key for the uploaded logo image. |
| `webUrl` | string | The company website URL. |
**Example response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Branding profile created successfully",
"data": {
"companyBrandingName": "Partner Company",
"primaryLogoKey": "primary/a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"webUrl": "https://partner-company.com"
}
}
```
### Error responses
| **Code** | **Description** |
| - | - |
| `400 Bad Request` | Invalid request parameters. Common causes: blank or whitespace-only branding name, invalid logo format or encoding, logo exceeds 2 MB, or invalid URL format. |
| `401 Unauthorized` | Authentication required. |
| `403 Forbidden` | User must be a Company Admin in the partner account. |
## Updating a branding profile
To update a branding profile, send a `PUT` request to `/v3/companies/{companyUid}/branding-profile`.
### Request
| **Parameter** | **Type** | **Required** | **Description** |
| - | - | - | - |
| `companyBrandingName` | string | Yes | The display name for branding. Must be 1-80 characters and cannot be blank or whitespace-only. |
| `primaryLogoImage` | string | No | The logo image as a base64-encoded data URI. Format: `data:image/\{type};base64,\{encoded-data}`. Supported image types: PNG, JPEG, SVG, and WebP. Maximum size: 2 MB. Only include this to update the logo. |
| `webUrl` | string | Yes | The company website URL. Must be a valid URL including the protocol (`http://` or `https://`). |
**Example request body**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"companyBrandingName": "Updated Partner Company",
"webUrl": "https://updated-partner-company.com"
}
```
### Response
A successful request returns a `200 OK` response with the updated branding profile details:
| **Field** | **Type** | **Description** |
| - | - | - |
| `companyBrandingName` | string | The display name for branding. |
| `primaryLogoKey` | string | The storage key for the uploaded logo image. |
| `webUrl` | string | The company website URL. |
**Example response**
```json theme={"theme":{"light":"github-light-high-contrast","dark":"github-dark-high-contrast"}}
{
"message": "Branding profile updated successfully",
"data": {
"companyBrandingName": "Updated Partner Company",
"primaryLogoKey": "primary/a1b2c3d4-e5f6-7890-abcd-ef1234567890",
"webUrl": "https://updated-partner-company.com"
}
}
```
### Error responses
| **Code** | **Description** |
| - | - |
| `400 Bad Request` | Invalid request parameters. Common causes: blank or whitespace-only branding name, invalid logo format or encoding, logo exceeds 2 MB, or invalid URL format. |
| `401 Unauthorized` | Authentication required. |
| `403 Forbidden` | User must be a Company Admin in the partner account. |
# Megaport API Overview for Partners
Source: https://docs.megaport.com/partners/api/index
This help topic describes the Megaport public API for partners to access to Megaport services.
The Megaport API contains several endpoints to manage partner accounts. Partners can order, edit, terminate, and list services for a managed account.
As a partner, you can act on behalf of a managed account. The `X-Call-Context` header allows switching the request context from the partner company to a managed account. You specify the managed account's full company UID as the value of the header.
You can add the header to most of the standard API endpoints with a few exceptions, such as the notification preferences and pricing endpoints.
For more information about the partner API, and for a complete API reference, see
[https://dev.megaport.com](https://dev.megaport.com/#d374b249-6d87-47d9-96aa-731e1279b593).
For information on API calls needed to perform common tasks such as logging in, creating a Port, and creating a VXC from the Port to a cloud provider, see [Megaport API](/api).
## Branding profile
The branding profile API lets you manage custom branding for your partner company. For more information, see [Customizing your Branding with the API](/partners/api/branding-profile).
# Understanding Partner Pricing and Billing
Source: https://docs.megaport.com/partners/billing/index
This help topic describes the basic billing and invoicing information for partner accounts.
This topic describes the basic billing and invoicing information for partner accounts, including customer billing.
Megaport billing features let you review your invoiced costs and manage access to billing information.
* A billing market was set up for your company profile when you registered your account and created a company profile.
* The partner account receives a monthly invoice directly from Megaport for all of its managed accounts.
* All managed accounts are invoiced by the partner.
* Each managed account is identified with a unique account number, called a *managed account reference*.
* All managed account references are rolled up into a consolidated invoice for the partner account.
* Each partner is responsible for all charges incurred by themselves and all managed accounts.
## Discounts
* All services are billed at the Megaport list price in the Partner Portal.
* Discounts aligned to a partner commission are calculated at the time of billing.
## Terms
* Partners can sign up for a service for these term lengths: month-to-month, 12, 24, 36, 48, or 60 months when creating a new Port, Virtual Cross Connect (VXC), Megaport Internet connection, IX connection, Megaport Cloud Router (MCR), Megaport Virtual Edge (MVE), or Megaport NAT Gateway (NAT Gateway). Partners updating an existing month-to-month service can select a 12, 24, 36, 48, or 60-month term.
* For more information about contract terms, see these topics:
* [Port Pricing and Contract Terms](/finance/port-pricing)
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
* [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing)
* [IX Pricing and Contract Terms](/finance/ix-pricing)
* [MCR Pricing and Contract Terms](/finance/mcr-pricing)
* [MVE Pricing and Contract Terms](/finance/mve-pricing)
* [NAT Gateway Pricing and Contract Terms](/finance/nat-gateway-pricing)
## Taxes
* All charges to the partner account and managed account are invoiced with the partner account tax treatment and any exemptions for the billing market applied.
* Partners incur tax remitted by Megaport.
* Resellers incur managed account taxes remitted by the partner.
* Taxes are applied in the Partner Portal against the final billed amount.
* For more information about taxes, see [Understanding Your Megaport Partner Invoice](/partners/billing/understanding-invoices).
## Resource tags
Resource tags let you add custom reference metadata to a Megaport service.
Partners can use resource tags to store internal service references for billing, reconciliation, and operational tracking, all of which are reflected in the invoice. Resource tags created by partners are not visible or editable by managed accounts.
* **Partner-only visibility** – Resource tags created by a partner are not visible to managed accounts.
* **Managed account privacy** – Managed accounts cannot view or modify partner-created resource tags.
* **Partner service references** – Partners can use resource tags to store internal references for services, such as billing identifiers or reconciliation data, which will then appear on the invoice for easier tracking.
**To add a tag**
1. When creating or editing a service, go to the **Configure** tab.
2. Click **Add Tags**.
3. Click **Add New Tag**.
4. Enter details into the fields:
* **Key** -- string maximum length 128. Valid values are a-z 0-9 \_ : . / \ -
* **Value** -- string maximum length 256. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
5. Click **Save**.
If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
## Viewing billing
The Billing page shows billing details for the selected service. You can view upcoming estimated bills and any changes to the configuration over a given month.
**To view billing details for a service**
1. Log in to a partner account.
2. Go to the **Services** page.
3. Click the gear icon next to the Service.
4. On the Connections Details page, click **Billing**.
For descriptions of the billing graph and details, see [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
## Understanding billing by service type
### Port
To understand billing details for a Port, see [Port Billing](/finance/port-billing).
### VXC
To understand billing details for a Virtual Cross Connect (VXC), see [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
### Megaport Internet
To understand billing details for a Megaport Internet connection, see [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
### MCR
To understand billing details for a Megaport Cloud Router (MCR), see [MCR Billing](/finance/mcr-billing).
### MVE
To understand billing details for a Megaport Virtual Edge (MVE), see [MVE Billing](/finance/mve-billing).
### NAT Gateway
To understand billing details for a NAT Gateway, see [NAT Gateway](/finance/nat-gateway-billing).
### IX
To understand billing details for an IX, see [VXC, Megaport Internet, and IX Billing](/finance/billing-details).
# Viewing and Downloading Invoices
Source: https://docs.megaport.com/partners/billing/invoices
This help topic describes how to view and download Megaport invoices.
This topic describes how to view and download Megaport invoices.
## Viewing invoices by billing market
From the Company Billing Markets page, a user logged in to a partner account can see an estimate of the next invoice, download a statement, and view an invoice list, including amounts, due dates, open balances, and more. The invoices are sorted by the Managed Account References.
* If your account is managed through a Megaport partner, the partner manages the billing and the Portal does not display billing markets or invoices. Contact your partner for billing and invoicing inquiries.
* Invoice downloads are not available for the Brazil and India billing markets:
* For the Brazil billing market, Accounts Receivable (AR) sends invoices, statements, and other standard communications to the billing contact email address registered in your partner account. For invoice inquiries about your Brazil billing account, contact [Megaport Accounts Receivable](mailto:ar.global@megaport.com).
* For the India billing market, invoices, statements, and other standard communications are sent to partners by our invoicing agent. For inquiries, contact [Megaport Accounts Receivable](mailto:ar.global@megaport.com).
**To view a list of invoices**
1. Choose User Menu > Admin Settings > Billing Markets.
2. Click the View Invoices icon.\
The Invoices screen for the selected market is displayed.
3. By default, the invoices from the last 12 months appear. To narrow the invoices shown on the page, select a date range.
All invoices with an invoice date within that date range appear, irrespective of settlement status.
**To download an invoice**
* On the **Invoices** tab, click the CSV or PDF icon next to the invoice you would like to download.
* **CSV** -- Downloads the invoice in the comma-separated values (CSV) format. You can use the CSV file to import the data into spreadsheets and databases. You can open the CSV file in any text editor.
* **PDF** -- Opens a new browser tab with a PDF version of the invoice.
You can only view and download invoices originally generated by the Portal. Credit notes and manually corrected invoices are not visible and cannot be downloaded from the Portal.
# Understanding Your Megaport Partner Invoice
Source: https://docs.megaport.com/partners/billing/understanding-invoices
This help topic describes the details in your Megaport partner invoice.
This topic describes the terms and details in Megaport partner invoices.
Megaport invoices partner accounts for services every month. The invoice contains a summary of the services ordered from a partner account, services ordered by managed accounts, general information about the invoices, the amount due, how to make a payment, and how to contact Megaport. These invoices and statements are sent monthly to the Billing Contact email address registered in your partner account. For more information about viewing current and previous invoices, see [Viewing and Downloading Invoices](/partners/billing/invoices).
## Invoice details
Megaport provides invoices in PDF and CSV file formats. The invoice includes billing activity details for that month, including managed account activity. Here is a sample invoice in PDF format:
Your invoice header includes these terms:
* **Invoice Number** -- The number assigned to your invoice.
* **Invoice Date** -- The date the invoice was created.
* **Payment Terms** -- The number of days that credit is allowed from the invoice date, as agreed between Megaport and the partner.
* **Due Date** -- The date when full payment is due for the invoice.
* **Purchase Order** -- The purchase order specified when you created the Megaport service. For the PO number to appear on the invoice, you must specify it in the **Edit Market** tab for the billing market before the end of the billing period. For more information about updating your Invoice Purchase Order Number, see [Updating Your Billing Information](/finance/payment-info).
* **Total** -- Total including all taxes and surcharges.
The body of the invoice includes these terms:
* **Product** -- The service and service type description, which includes a brief description of the billing type. For example, recurring or postpaid.
The product field can display different information, and an invoice can include several product lines for a single service. If a product meets multiple discount criteria, each discount is listed on a separate line. For example, an invoice for a single Port can show a separate line for its current retail rate charge, and any discount, such as New Logo.
The relevant partner discount will apply. The discount types are:
* **Promo** -- Identifies a promotional code applied to a service.
* **New Logo** -- Identifies a discount during a partner's first year of the Partner Program membership.
* **Description** -- The Service ID assigned to the service by Megaport and the service type. The Service ID is a unique 8-character alphanumeric reference associated with each service. For example, `hd72g38f`. The ID also appears next to the service name on the Services page.
* **Date** -- The time period associated with the billed services.
* **Your Reference** -- The service level reference number and the unique account reference of the managed account consuming the service. The service level reference number is shown if you or the managed account specify one for the service. Partners provide an account reference when [creating a managed account](/partners/account/create-managed).
* **Amount** -- The sum of the billed service amount for time period within the date range. The invoice lists any discount applied to the service as a negative amount.
You can view upcoming estimated bills for a specific service on the Billing page in the Portal. For more information, see [VXC and IX Billing](/finance/billing-details).
Every month, invoices and statements are sent to the Billing Contact email address provided in the Megaport Portal in the **Billing Markets > Edit Market** tab. Invoices are usually sent on the first business day of the month, and statements around the 10th business day.
Megaport's auto-pay system processes payments on the 20th of each month for all invoices listed on your account statement issued at the beginning of the same month. If you have any questions relating to Megaport’s auto-pay system, contact [Megaport Accounts Receivable](mailto:ar.global@megaport.com?).
Ensure that you keep the Billing Contact email address current so you receive invoices, statements, and other communication in a timely manner.
### Invoice in CSV format
You can download an invoice in the comma-separated values (CSV) format to import the data into spreadsheets and databases. You can open the CSV file in any text editor. Here is a sample partial invoice in the CSV format:
## Taxes - domestic customers
Taxes are broken down by region, depending on where you ordered the Megaport service and the location of your registered business address.
Here is an example of the tax breakdown on a USA invoice where a USA-based customer ordered services in several states:
The Federal Universal Service Fund (FUSF) rate in the USA is [established by the Federal Communications Commission (FCC)](https://www.fcc.gov/general/contribution-factor-quarterly-filings-universal-service-fund-usf-management-support) and is updated on a quarterly basis. State sales tax rates in the US can also change occasionally, however less frequently than the FUSF.
VXCs are the only Megaport service that incur an FUSF charge.
If you believe you are eligible to claim a tax exemption on any of the fees on your invoice, contact [Megaport Accounts Receivable](mailto:ar.global@megaport.com?) for instructions on how to upload your supporting documentation to our Exemption Certificate Management System.
In European countries, the standard Value Added Tax (VAT) is generally applied on services to domestic customers. Here is a sample VAT breakdown for a UK domestic customer:
In the rest of the world, a local tax is applied for domestic customers. In this example, an Australian invoice includes a standard Goods and Services Tax (GST):
## Taxes - non-domestic customers
In Europe, services for non-domestic customers within the European Union (EU) can be 0% rated for VAT purposes when the customer provides a valid EU VAT registration number. In this situation, the customer must account for VAT on a reverse charge basis.
*Export customers* are generally defined as those located outside the country from which Megaport provides and bills services. In the case of an EU billing entity, they are also located outside the EU. In all cases, an export customer does not have a permanent establishment for tax purposes or tax registration in the country of billing.
Export invoices are generally not subject to tax, such as VAT (Europe) or GST (AU, NZ, SGP).
Megaport Japan customers should note that the criteria for export transactions are more technical in Japan and depend on the nature of the services rather than where the customer is based.
## Questions?
For billing or invoice questions, contact Megaport Accounts Receivable.
# Glossary
Source: https://docs.megaport.com/partners/glossary/index
This help topic defines terminology related to the Megaport network and services.
This topic defines terminology related to the Megaport network and services.
#### 802.1Q
IEEE 802.1Q is the networking standard that supports virtual LANs (VLANs) on an Ethernet network. The standard defines a system of VLAN tagging for Ethernet frames and the accompanying procedures to be used by bridges and switches in handling such frames. Also informally known as *dot1q*.
#### A-End
The start of the connection--the Port, MCR, or MVE.
Megaport connections need an A-End and a B-End. The connection starts with an A-End. Most often, the Port is the A-End. The B-End is the other end of the connection: it can be a Port, an Internet Exchange, a Marketplace connection, or a cloud service provider.
#### API
Application program interface (API) is a set of routines, protocols, and tools for building software applications. An API specifies how software components should interact and APIs are used when programming graphical user interface (GUI) components. The Megaport API allows customers and partners to integrate directly into our platform for automation and service creation (see [dev.megaport.com](https://dev.megaport.com)).
#### ASN
An autonomous system number (ASN) is a collection of connected Internet Protocol (IP) routing prefixes under the control of one or more network operators on behalf of a single administrative entity or domain. ASN refers to Autonomous System Number and is a unique numerical ID allocated to each AS for use in BGP routing.
#### Amazon Web Services (AWS)
Amazon Web Services (AWS) is a secure cloud services platform, offering compute power, database storage, content delivery and other functionality to help businesses scale and grow.
#### AWS Direct Connect
AWS (Amazon Web Services) Direct Connect is a network service that allows customers to establish a dedicated network connection between one of Amazon’s Direct Connect locations and the customer’s data center or colocation environment. Megaport is an AWS Direct Connect partner.
#### Azure
Azure is a Microsoft service. It is an open, flexible, enterprise-grade cloud computing platform accessed via Microsoft’s ExpressRoute service.
#### B-End
A Port or MCR establishes the A-End of the connection and the B-End is the other end. The B-End can be a Port for a private VXC, an Internet Exchange, a Marketplace connection, or a cloud service provider.
#### BGP
Border Gateway Protocol (BGP) is a standardized routing protocol designed to exchange route and reachability information among autonomous systems (AS) on the internet.
#### CDN
A content delivery network (CDN) is a system of distributed servers (network) that deliver webpages and other web content to a user based on the geographic locations of the user, the origin of the webpage and a content delivery server. Examples: Akamai, Cloudflare.
#### cloud computing
Cloud computing is a general term for the delivery of hosted services over the internet.
#### colo
Abbreviation for co-location. The renting of space for housing computer equipment, usually in buildings specially designed to support a high density of computers and network connections, often called data centers, but also known as tele-houses or carrier hotel facilities.
#### cloud service provider (CSP)
A cloud service provider is an organization that offers one or more components of cloud computing to businesses or individuals. Typical cloud services are Infrastructure as a Service (IaaS), Software as a Service (SaaS), or Platform as a Service (PaaS).
#### customer account
Any direct Megaport customer that is not a member of the Megaport Partner Program.
#### demarc
Demarcation point. Generally, a floor/rack/port assignment for an optical port. See *Letter of Authorization (LOA)* for further details.
#### data center (DC)
A data center is a large group of networked computer servers typically used by organizations for remote storage, processing, or distribution of large amounts of data.
#### dark fiber (DF)
Dark fiber (DF) is essentially optical fiber infrastructure that is not in use. It is considered as capacity that has been laid in addition to that required at the initial time of service provisioning for expansion, growth, or resale. It is no longer considered dark once signals are traversing it (lit).
#### direct customer
Any Megaport customer that is not a member of the Megaport Partner Program. Direct customers order services directly for themselves in the Megaport Portal.
#### DNS
The Domain Name System (DNS) is a hierarchical decentralized naming system for computers, services, or any resource connected to the internet or a private network. It associates various information with domain names assigned to each of the participating entities.
#### dot1q
See *802.1Q*: IEEE 802.1Q is the networking standard that supports virtual LANs (VLANs) on an Ethernet network. The standard defines a system of VLAN tagging for Ethernet frames and the accompanying procedures to be used by bridges and switches in handling such frames.
#### Direct Connect (DX)
The method for accessing Amazon Web Services (AWS) public/private peering.
#### elastic interconnection
Elastic connectivity is a term used to define a connection that provides businesses the flexibility to vary connectivity service requirements based on demand. Megaport customers can provision an elastic interconnection for as short as a day or as long as they need, with speeds ranging from 1 Mbps to 10 Gbps.
#### endpoint
An endpoint is one end of an API communication channel and specifies the URI or URL of a server or service where you can access the resource. Includes any internet-enabled remote computing device that communicates with a TCP/IP network.
#### ExpressRoute (ER)
Microsoft Azure ExpressRoute lets customers extend their on-premises networks into the Microsoft cloud over a dedicated private connection. Megaport is a Microsoft Azure ExpressRoute partner.
#### Ethernet Virtual Private Line (EVPL)
EVPL allows for service multiplexing at the UNI (unlike EPL). This capability allows more than one EVC to be supported at the UNI where the EPL does not allow this. Second, an EVPL need not provide as much transparency of Service Frames as with an EPL (Definition: MEF).
#### fully qualified domain name (FQDN)
The complete domain name for a specific host on the internet, including the hostname and domain name.
#### fast reroute (FRR)
A MPLS and IP resiliency technology to provide fast traffic recovery upon link or router failures for mission critical services. Upon any single link or node failures it is possible to recover impacted traffic in the order of tens of milliseconds.
#### Google Cloud Interconnect (GCI)
Previously Google Carrier Interconnect.
#### Google Cloud Platform (GCP)
Offered by Google, GCP is a provider of computing resources for developing, deploying, and operating applications on the web.
#### Global Services Agreement (GSA)
[Megaport standard terms](https://megaport.com/legal/global-services-agreement/). See also the SLA which is a component of the GSA.
#### hybrid cloud
A cloud computing environment which uses a mix of on-premises, private cloud and third-party, public cloud services with orchestration between the two platforms.
#### indirect customer
Any Megaport customer that is managed by a member of the Megaport Partner Program. Indirect customers work with partners to set up accounts, order services, and obtain billing and support.
#### Infrastructure as a Service (IaaS)
Online services that abstract the user from the details of infrastructure like physical computing resources, location, data partitioning, scaling, security, backup. According to the Internet Engineering Task Force (IETF), IaaS is the most basic cloud-service model for providers offering cloud computing infrastructure.
#### Internet Engineering Task Force (IETF)
An organization that develops and promotes voluntary internet standards, in particular the standards that comprise the Internet protocol suite (TCP/IP). IETF has no formal membership or membership requirements. All participants and managers are volunteers with their work usually funded by their employers or other sponsors.
#### Internet Protocol Security (IPsec)
A protocol suite for secure Internet Protocol (IP) communications that works by authenticating and encrypting each IP packet of a communication session.
#### Information Technology Infrastructure Library (ITIL)
A set of practices for IT Service Management (ITSM).
#### IX
An Internet Exchange (known as IX or IXP for a given Internet Exchange Point) is a physical infrastructure through which internet service providers (ISPs) and Content Delivery Networks (CDNs) exchange internet traffic between their networks (autonomous systems). MegaIX is the Megaport IX product, AMS-IX is the partner IX product offered in some geographies via cloud ‘Tile’.
#### jitter
A variation in packet transit delay (RTT/RTD/PTD, latency) caused by queuing, contention and serialization effects on a path through the network.
#### Layer 1 (L1)
Layer 1 of the OSI model conveys the bit stream (electrical impulse, light or radio signal) through the network at the electrical and mechanical level. It provides the hardware means of sending and receiving data on a carrier, including defining cables, cards, and physical aspects. A fiber optic cable/SFP terminations would be considered Layer 1, as well as the physical Port.
#### Layer 2 (L2)
Layer 2 of the OSI model is the data link layer. This provides node-to-node data transfer (a link between two directly connected nodes). Most Megaport Virtual Cross Connects (VXCs) operate at this layer. Layer 2 is divided into Media Access Control (MAC) layer (controls how devices in a network gain access to medium and permission to transmit), and Logical Link Control (LLC) layer (responsible for identifying network layer protocols and then encapsulating them and controls error checking and frame synchronization).
#### Layer 3 (L3)
Layer 3 of the OSI model is the network layer. It translates logical network address into physical machine address (IP addressing). Layer 3 routers analyze traffic based on address details and forward appropriately, requiring knowledge of the details generally exchanged in BGP sessions for routing table exchanges.
#### Letter of Authorization (LOA)
A document that customers need to present to their data center provider to establish the physical cross-connect from their data center services to their Port. The LOA is provided via the Megaport Portal when a customer provisions a new Port.
#### link aggregation group (LAG)
Describe various methods for using multiple parallel network connections to increase throughput beyond the limit that a single link (one connection) can achieve. In general for link aggregation, physical Ports must reside on a single switch/router.
#### LR
An optical interface standard for a small form-factor pluggable (SFP) that can deliver 10 Gbps over roughly 10km. Megaport's standard for delivery of 10 Gbps ports. See *LX* for the 1 Gbps equivalent. Uses 1310nm wavelength.
#### label-switched path (LSP)
A path through an MPLS network.
#### LX
An optical interface standard for a small form-factor pluggable (SFP) that can deliver 1 Gbps over roughly 10km. Our standard for delivery of 1 Gbps ports. See *LR* for the 10 Gbps equivalent. Uses 1310nm wavelength.
#### managed account
An account that receives Megaport services and support through a Megaport partner. The partner can customize the features in the Megaport Portal to limit visibility and features for a managed account.
#### managed service provider (MSP)
A managed service provider is a third-party company that provides network, application and system management services to enterprises with a pay-as-you-go pricing model.
#### MD5
Sometimes known as an MD5 hash or BGP key. The MD5 algorithm is a widely used cryptographic function producing a string of 32 hexadecimal digits. This is used as a password or key between routers exchanging BGP information.
#### Megaport SDN
Megaport’s neutral, software-defined network based global network comprising of cloud service providers, network service providers, and data center operators, accessed via the Megaport Portal or API.
#### meet-me room (MMR)
A place within a data center, colocation center or carrier hotel, where telecommunications companies can physically connect to one another and exchange data without incurring local loop fees. Services provided across connections in an MMR might be voice circuits, data circuits, or Internet Protocol.
#### Microsoft Azure ExpressRoute
Microsoft Azure ExpressRoute lets customers extend their on-premises networks into the Microsoft cloud over a dedicated private connection. Megaport is a Microsoft Azure ExpressRoute Partner.
#### Multi-Protocol Label Switching (MPLS)
A type of data-carrying technique for high-performance telecommunications networks that directs data from one network node to the next based on short path labels rather than long network addresses, avoiding complex lookups in a routing table.
#### multicast frame
An Ethernet frame containing a multicast MAC address that identifies a select group of destinations. A frame sent to a multicast address is forwarded to all destinations in the multicast group simultaneously.
#### multicloud
The use of multiple cloud computing services in a single heterogeneous architecture. For example, an enterprise may use multiple cloud providers for infrastructure (IaaS) and software (SaaS) services. One of Megaport core value propositions is enabling multi-cloud connectivity.
#### Network Address Translation (NAT)
Network Address Translation (NAT) is the process that translates the unregistered private IP addresses used for an organization's private inner network into a single registered public IP address before packets are sent to an external network. NAT allows private IP networks to use the internet and cloud.
#### Net neutrality
The principle that Megaport enables access to all service providers without favoring or blocking others.
#### network-to-network interface (NNI)
An interface between two networks. Technically used as distinct from UNI to define an interface between provider networks but sometimes used interchangeably between provider and customer network handoffs (Definition: MEF).
#### Open Systems Interconnection (OSI)
A model that characterizes and standardizes the communication functions of a telecommunication or computing system. Most Megaport products are Layer 2 (or L2) with some of the OSI constructs pushing into Layer 3 (L3) where IP addressing information is exchanged, known as an L2/L3 service.
#### PaaS
Platform as a Service vendors offer a development environment to application developers. The provider typically develops toolkit and standards for development and channels for distribution and payment. In the PaaS models, cloud providers deliver a computing platform, typically including operating system, programming-language execution environment, database, and web server without the need to manage any of the underlying operating system or host architecture.
#### partner account
A partner reseller associated with the Partner Program member.
#### Partner Portal
The Megaport Partner Program term for the Megaport Portal.
#### Partner Program
The [Megaport Partner Program](https://www.megaport.com/partners/). The Megaport Partner Program makes it easy to add NaaS offerings to your cloud or managed services portfolio.
#### Partner Program member
A partner who has signed a Global Reseller Agreement (GRA) with Megaport to become a reseller in the Partner Program.
#### peering
A process by which two internet networks connect and exchange traffic. This allows these two internet networks to directly exchange traffic between each other’s customers, without having to pay a third party to carry that traffic across the internet.
#### PLR
Packet loss rate/packet loss ratio.
#### Port
A Port is the high-speed ethernet interface that connects to the Megaport network. Bandwidth options between Ports range from 1 Mbps to 10 Gbps. 100 Gbps is available in some locations.
#### provider
A provider purchases products and services from Megaport at a discount and then
resells those products to their own customers. A provider may be a value-added reseller (VAR), managed service provider (MSP), systems integrator (SI), cloud service provider (CSP), network service provider (NSP), data center reseller, or any combination.
#### PTD
Packet transfer delay (one-way latency measure).
#### Q-in-Q
802.1Q tunneling (also known as Q-in-Q or 802.1ad) is a technique used by OSI Layer 2 providers for customers. 802.1ad provides for both an *inner* and an *outer* tag whereby the outer (sometimes called S-TAG for service provider) can be removed to expose the inner (C-TAG or customer) tags that segment the data.
#### risers
(Generally vertical) shafts through which cable baskets are routed. Also known as *verticals*.
#### route server (RS)
A route server provides a mechanism for the establishment of BGP routing exchanges in an Internet Exchange (IX or IXP). It simplifies the process of maintaining many peering partners across a network and also contributes to the network visibility and manageability. Route servers are generally deployed in pairs to allow for maintenance windows and general redundancy to support IX stability. Some offer a Looking Glass functionality used to view which peers maintain which routes and allow troubleshooting on network routing choices.
#### RTT
Round-trip time (RTT) is the length of time taken by a data packet to be sent to a destination, including the time it takes for an acknowledgment of that packet to be received back at the origin time. Also known as **ping** time.
#### rack unit (RU)
A unit of measurement mainly used to describe the height of rack-mounted computer equipment (especially servers and routers) and the racks into which they are fitted. One RU is 1.75 inches or 4.445 centimeters. For example, 42RU indicates a 1.87m height cabinet.
#### SaaS
In the Software as a Service (SaaS) model, users gain access to client application software. Cloud providers manage the infrastructure and platforms that run the applications. SaaS is sometimes referred to as on-demand software and is usually priced on a pay-per-use basis or using a subscription fee.
#### software-defined networking (SDN)
An approach to computer networking that allows network administrators to manage network services through abstraction of higher-level functionality. This results in Network as a Service and on-demand network resources.
#### systems integrator
An individual or business that builds computing systems for clients by combining hardware, software, networking, and storage products from multiple vendors.
#### service-level agreement (SLA)
Part of a standardized service contract where a service is formally defined. Particular aspects of the service scope, quality, responsibilities are agreed between the service provider and the service user. Referred to as *GSA* in Megaport terms (Global Services Agreement).
#### single-mode optical fiber (SMOF)
A fiber cable with only one mode of propagation: a single wavelength of light in the fiber core. Multi-mode optical fiber (MMOF) is less expensive but can only run shorter distances without signal degradation.
#### Transmission Control Protocol/Internet Protocol (TCP/IP)
A set of rules/protocols governing communications among all devices on the internet. More specifically, TCP/IP dictates how information should be packaged (packetized), sent, and received, as well as how to traverse connected networks to reach its ultimate destination.
#### transit
Commodity internet capacity. As distinct from IX routes (specific), transit capacity (a generally paid service) indicates the general default route for internet traffic when routes are otherwise unknown at a settlement free peering exchange.
#### value-added reseller (VAR)
A company that purchases hardware, software, or other technology and resells it to end users as a bundle with additional offerings.
#### virtual LAN (VLAN)
A partitioned and isolated computer network at the data link layer (OSI Layer 2) on a single physical interface (for example, a Port) used to subdivide a network. LAN is an abbreviation of local area network.
#### Virtual Private LAN Service (VPLS)
A way to provide Ethernet-based multipoint to multipoint communication over IP or MPLS networks. It allows geographically dispersed sites to share an Ethernet broadcast domain by connecting sites through pseudo-wires.
#### virtual private network (VPN)
Extends a private network across a public network or internet. It enables users to send and receive data across shared or public networks as if their computing devices were directly connected to the private network. VPNs can provide functionality, security, and network management benefits to the user.
#### Virtual Cross Connect (VXC)
A direct Ethernet connection between two Ports allowing high speed, private connectivity. VXCs are provisioned within minutes allowing rapid deployment of services.
#### XCON or XC
Abbreviation for Cross Connect. A connection scheme between cabling runs, subsystems, and equipment using patch cords or jumpers that attach to networking equipment.
# Welcome to the Megaport Partner Documentation
Source: https://docs.megaport.com/partners/index
Latest partner-related Megaport Portal updates and changes.
Set up and configure your partner account.
Manage managed accounts and permissions.
Provision and monitor customer services.
Partner rates, invoices and billing details.
Automate partner operations with the Megaport API.
Diagnose and resolve common partner issues.
Get help from the Megaport support team.
# Introducing the Partner Portal
Source: https://docs.megaport.com/partners/intro/index
This site provides detailed help and instruction on how to use, configure, and troubleshoot the features available for partners of the Megaport network and services.
The Partner Portal is the component of the Partner Program used by Megaport partners (such as DCOs, channel partners, and MSPs) to sell services to third-parties. Partners can configure and manage a set of accounts, called *managed accounts,* and deploy and manage the services on those accounts.
The Partner Portal provides:
* On-demand self-provisioning of Megaport services, such as Ports, on behalf of managed accounts.
* Management of all appropriate user permission settings on the managed accounts.
* Management of all customer services: Ports, Megaport Cloud Routers (MCRs), Megaport Virtual Edges (MVEs), Virtual Cross Connects (VXCs), and IXs.
* Data collection that is easily leveraged for business expansion opportunities.
Use the Partner Portal to manage and track these account details on behalf of your end customers:
* Customer names
* Products
* Contract terms
This documentation site provides details on using the Partner Portal.
# Frequently Asked Questions (FAQs)
Source: https://docs.megaport.com/partners/pp-faqs/index
This help topic provides questions about and answers for Megaport Partner Portal.
See these FAQs for common questions, suggestions, and resolutions.
### Is there more than one level of managed account?
No, a partner account can have multiple managed accounts but a managed account cannot have its own managed accounts. For more information, see [Partner Program Account Hierarchy](/partners/acct-hierarchy).
### Does a managed account receive a bill directly from Megaport?
No, managed account invoices are collated and billed to the partner account.
### Does an end customer have access to their managed account?
Yes, if the partner has segregated the services into a separate managed account then they can create a [user role](/partners/account/profiles) that provides access for the end customer.
### Can an end customer in a managed account access the partner account?
No, a managed account user can only access their own account and not log in upwards to the partner account or laterally to other managed accounts not owned by the end customer.
### Does a managed account user have permission to associate with a reseller?
Yes, you can move between a partner reseller account and a managed account with approval from all parties (Megaport, the partner, and the end customer).
### Can a managed user change the company name or billing market information?
No, only a partner account user can change the company name or managed account billing details.
# Understanding the Services Page
Source: https://docs.megaport.com/partners/services-page/index
This help topic describes the Services page and its features for partners and managed account users.
The Services page is a bird's eye view of all your Megaport services. You can view, configure, and edit your Ports, MCRs, MVEs, and their connections (VXCs, IXs, and Megaport Internet connections). Each connection is grouped under its associated Port, MCR, or MVE.
Partners can view, configure, and edit all services including Ports, MCRs, MVEs, and their connections (VXCs, IXs, and Megaport Internet) within both their own account and all of their managed accounts.
Managed account users can view, configure, and edit all services including Ports, MCRs, MVEs, and their connections (VXCs, IXs, and Megaport Internet) within their own managed account.
For more information, see [Understanding the Services Page](/portal-admin/services-page).
## Filtering and sorting services
The filtering and sorting tools allow you to customize the Services page to help you find the information you need.
This feature is available to both partners and managed account users.
## Filtering services
To narrow the services shown on the page, enter your text search in the **Filter Services** field. The filter will match against the name, location, and ID of the services. Any services matching your search will be highlighted.
Click (View Additional Filters) to filter services by service type and contract term length, in addition to the text filter. For example, you can filter on Ports on a 12 month term. The filters will persist if you navigate away and return to the Services page in the same session.
The number of matching services is displayed below the **Filter Services** field. Click **Clear Filters** to remove all filters and display all services in the Services page.
### Sorting services
You can change the order of the items on the Services page according to the following criteria:
* **Creation Date** -- Sorts by the date they were created.
* **Name** -- Sorts by name, in alphabetic order.
* **Location** -- Sorts by country, and then by the location within that country.
You can sort in ascending or descending order.
You can only sort Ports, MCRs, and MVEs, not their connections (such as VXCs or IXs), which are displayed in the order they were added.
You can also hide or show all the connections for a Port, MCR, or MVE. By default, the Portal shows all the connections unless there are more than 10, in which case they are collapsed initially. Click the Extra Actions kebab menu and select Expand All Services
to expand all connections under a service, or select Collapse All Services to hide them.
## Downloading a service inventory
The Services page provides a convenient way to get an inventory of all services associated with your account. The inventory includes all live and configured services, along with any services that have been decommissioned.
Partners can download an inventory of all services including Ports, MCRs, MVEs, and their connections (VXC, IXs, and Megaport Internet) within both their own account and all of their managed accounts.
Managed account users can download an inventory of all services including Ports, MCRs, MVEs, and their connections (VXC, IXs, and Megaport Internet), within their own managed account.
**To download an inventory of services**
* On the Services page, click (Extra Actions) > Download Inventory Report.\
The service inventory is saved in the comma-separated values (CSV) file format and downloaded to your Downloads folder.
Partner: Sample CSV
Managed account: Sample CSV
* You can import the CSV data into spreadsheets and databases.
* You can open the CSV file in any text editor.
## Viewing and editing services
By default, services are listed by the date they were created. VXCs, IXs, and Megaport Internet connections are grouped under each Port, MCR, or MVE.
For more information, see [Viewing and editing services](/portal-admin/services-page#viewing-and-editing-services).
## Service details
Each service displays its speed or rate limit, location, and allocation percentage. Ports might also show a diversity zone. The allocation percentage reflects the amount of bandwidth defined for the respective service that has been assigned to VXCs.
For more information, see [Service details](/portal-admin/services-page#servicedetails).
# Creating and Ordering Services
Source: https://docs.megaport.com/partners/services/creating
This help topic describes ordering Megaport services as either a partner or managed user.
This topic describes ordering Megaport services as either a partner or managed user and how user roles affect ordering permissions.
## Network services overview
To set up network services with Megaport through a partner or managed account, you need to order a Port, an MCR, an MVE, or a NAT Gateway. The ordering process is the same for partners and customers, with some [ordering restrictions](/partners/services/creating#orderrestrictions) for managed account users. Through the Megaport Portal, you can set up a complete end-to-end configuration and then proceed to the ordering process.
### Port
A Port lets you connect your equipment to Megaport through 1 Gbps or 10 Gbps fiber interfaces (100 Gbps is available in some locations). With a configured Port, you can establish connections to other Ports, CSPs, or IXs.
* [Create a Port](/connections/creating-port)
### MCR
MCR is a Layer 3 capable virtual router hosted by Megaport in cloud hotspot locations worldwide. An MCR does not require a Port, but you can connect to one as required.
* [Create an MCR](/mcr/creating-mcr)
### MVE
MVE is an on-demand Network Function Virtualization (NFV) service that supports branch-to-cloud connectivity on SD-WAN platforms. An MVE works as a gateway to connect enterprise SD-WAN enabled sites to the Megaport ecosystem, providing cloud-neutral, direct, and secure access to its extensive platform of cloud providers and other services. An MVE does not require a Port, but you can connect to one as required.
* [Create an MVE](/mve)
### NAT Gateway
Megaport NAT Gateway (NAT Gateway) is a network address translation (NAT) service that lets devices in private networks access the internet without each device needing its own public IP address. A NAT Gateway does not require a Port, but you can connect to one as required.
* [Create a NAT Gateway](/nat/creating-nat-gateway)
### Ordering restrictions for managed account users
Managed users have these restrictions on Megaport network service orders:
* When the Service Approval Queue is active for a managed account, creating, changing, and terminating services requires partner approval. For more information, see [Service Approval Queue](/partners/services/service-approval-queue).
* Managed users can only complete orders for billing market locations that have been pre-enabled by the partner. Managed users can request billing market enablement from their partner. (Partners can use the **Enable Markets** button under Configured Services for quick access to billing market set up.)
* Managed accounts and partners acting on behalf of managed accounts cannot order services in the Brazil market due to regulatory limitations. When you enable or edit the Brazil billing market, the Portal displays a warning about this restriction.
* While adding or configuring a Port, managed users cannot set the Marketplace visibility to Public on the Port. The Marketplace visibility option only appears for partner accounts.
* Managed users cannot use a promotional code when ordering services, unless they initially log in to a partner account and then switch into the managed account.
## Completing orders
Partners and managed users with Company Admin, Tech Admin, or Finance permission can order, edit, and terminate services, as shown in this table:
| **Role** | **Ordering Permission** |
| - | - |
| Company Admin | Can complete the orders |
| Tech Admin | Can complete the orders |
| Tech Contact | Cannot complete the orders |
| Finance | Can complete the orders |
| Finance Contact | Can view the orders |
| Read only | Can view the orders |
Managed users without permission to complete orders can instead configure and save services. Saved configurations can include Ports, VXCs, MCRs, and MVEs. After saving a configuration, it is visible to anyone in the organization and is ready to order.
### Saving a configuration
You can save a network configuration before you are ready to go ahead and order. Saved configurations are company wide and will be visible to anyone in your organization.
**To save a configuration**
1. Under Configured Services, click **Save**.
2. Enter a name for the configured services then click **Save**.
The service appears under Saved Configurations.
### Ordering a saved configuration
To order a saved configuration, you must be either:
* A managed account user assigned a role that includes ordering privileges.
or
* A partner assigned a role that includes ordering privileges. Partners can switch into the managed account, load the saved configuration, and complete the order.
**To order a saved configuration**
1. Log in as a partner or managed user with ordering permission.
2. If necessary, switch into the managed account to view the saved configuration.
3. Select the saved configuration.\
Hover the mouse over the configuration name for details.
4. Click **Load**.
5. Click **Replace Configured Services** to replace the saved configuration with the new configuration.
6. Click **Review Order** then **Order Now** to complete the order.
If you see an option to **Send for Approval** instead of **Order Now**, your orders require approval by the partner. For more information, see [Service Approval Queue](/partners/services/service-approval-queue).
7. For Port orders, click **Download the LOA** to review the Letter of Authorization.
The service appears on the Services page for the managed account and the partner account.
After the service goes live, you have access to the Megaport network and can now click **+Connection** to order a Virtual Cross Connect (VXC) for the service. For more information, see [Connections Overview](/connections/overview).
# Quoting Service Cost (Partner)
Source: https://docs.megaport.com/partners/services/creating-estimates
This help topic describes how to create a quote for Megaport services as a partner for yourself, or a managed user.
This topic describes how a partner can quickly create a quote to estimate the cost of deploying Megaport services, before actually ordering the services.
Entering details of the services into the Quoting Tool helps you and your customers plan the overall cost of Megaport services within a specified time period. This provides a clear idea of the design, services needed, and cost breakdown by customer for planning.
Partners can use the Quoting Tool to:
* Create solution quotes outside of the Partner Portal for themselves or managed users
* View the provided discount value
* Save a quote
* View all saved quotes
* Edit saved quotes
* Download saved quotes
* Record that a quote has been registered with a quote ID
* Track quote status: New, Saved, or Registered
* Compare pricing for different terms and currencies side by side.
## Creating a quote
Use your Partner Portal credentials to log in to the [Quoting Tool](https://pricing.megaport.com/).
Your partner login takes you to the Quoting Tool Saved Quotes page. Use the Saved Quotes page to view a list of your quotes and create, duplicate, save, and send quotes for registration.
The Saved Quotes page displays all your saved quotes. The list includes quotes where the created date is less than six months old. Quotes are deleted after six months.
By default, the page is sorted by the date the quote was created, in descending order. The most recent quote is listed first.
**To create a quote**
1. On the Saved Quotes page, click **Create New Quote**.
2. Select whether this is for an **Existing Customer** or a **Potential Customer**.
* **Existing Customer** -- Select this option if the quote is for a customer that already has an account with Megaport. Select the company name from the **Target Company** drop-down list.
* **Potential Customer** -- Select this option if the quote is for a potential customer that does not have an account with Megaport. Enter the potential customer's company name in the **Company Name** field.
The Quote Builder page appears. This page shows the Quote Builder details area, which contains the quote name, quote ID, company name, user who created the quote, created date, and quote status. The **Created By** field automatically populates with the email address of the logged-in user.
3. Enter a name for the quote in the **Quote Name** field.\
The company name cannot be changed.
4. Select a service to add to the quote: Port, MCR, MVE, NAT Gateway, IP Address, or Latitude.sh products.
5. Click **Choose Location** and select the service location.
6. Enter the required fields, such as name, rate limit, currency, term, diversity zone, Cross Connect, and subnet size if available. Requirements vary by service.
7. If you want to exclude the cost of this service from the quote, select **Exclude (service type)** from quote.\
You might do this, for example, if you need the service configured to replicate a network design without including the cost in the quote.
8. Add the service.
9. Click **+Connection** to add a connection to the service. For connections, select a destination type. The procedure varies slightly depending on the destination type.
* **Cloud** -- Select a provider, destination, and a diversity zone if available.
* **Private** -- Select a destination.
* **Marketplace** -- Select a Marketplace provider and destination.
* **Internet Exchange** -- Select a location and a term. The default term is 12 months.
* **Compute** -- Select a Latitude.sh destination.
* **Megaport Internet** -- Select a location.
* **Megaport Object Storage** -- Select a storage destination.
10. Enter the connection name, minimum term, and rate limit, where applicable. Exclude the service cost from the quote if required.
11) Select the **Roll Up Discounts** and **Including Partner Discounts** check boxes to view the provided discount values.
12) Click **Save Connection** to add the connection.
13) Continue adding the required services to the quote.
14) Click **Save** on the right when done.\
The Quote ID field is automatically populated with a system-generated UID and the quote status is set to *Saved*.
15) Click **Close** to view the Saved Quotes page.
### Summary
The summary shows the total monthly cost of all services in the quote, including any add-ons. The summary is updated when you change the term or currency.
For partner accounts, the summary allows you to select the following functions:
* Click the **Roll Up Discounts** check box to view the total discount value for each service and the total monthly cost.
* Click the **Including Partner Discounts** check box to view the total monthly cost including the partner discount value.
* Click **Show Retail & Partner Pricing** to view the retail and partner pricing, including discounts, side-by-side. When this option is selected, the **Including Partner Discounts** check box is automatically selected and cannot be deselected while this option is selected.
## Importing existing services
You can import existing live or configured services from your account into a quote. This allows you to add services that are already deployed without recreating them manually.
**To import existing services**
1. In the Quote Builder, click the import existing services icon.
2. In the **Add Existing Services** dialog, select the services and connections you want to add to the quote. Use the search field to filter by name or service UID.
When you select a connection, its associated A-end service is automatically selected.
3. To keep a service in the quote design but leave it out of pricing calculations, select **Exclude From Quote** for that service.
4. Click **Add Selected** to add the services to your quote.
The imported services and connections appear in your quote with their current configuration details. Each imported row is marked with an import icon and a chip showing a shortened service ID, consisting of # followed by the first part of the service UID. The same indicator appears in the editor header when you open an imported service or connection. Click the chip to copy the full service UID to your clipboard.
### Editing imported services
Imported services and connections represent existing deployments, so some fields are restricted when you edit them in a quote. These restrictions apply only to imported rows and do not affect new services that you add to the quote.
The restrictions take these forms:
* Some fields are read-only and cannot be changed. For all service types, this includes the name, location or connection destination, and currency. The speed or rate limit is also read-only for Port, MCR, MVE, and NAT Gateway services. For MVE services, the vendor, version, and size are read-only. For NAT Gateway services, the session count is read-only.
* For all service types, you can keep the term the same or extend it, but you cannot shorten it. For VXC and IX connections, whether you can change the rate limit depends on the term:
* **On a fixed term** -- you can keep the rate limit the same or increase it, but you cannot reduce it; a lower value cannot be saved.
* **On a month-to-month term** -- you can also reduce the rate limit down to the default minimum rate limit for the connection.
* You cannot remove existing add-ons and features, but you can add to them. For example, you cannot remove a Cross Connect from a Port or IPsec from an MCR, reduce the number of IPsec tunnels, or reduce the number of ports in a link aggregation group (LAG).
## Sorting quotes
You can sort the Saved Quotes list by date, quote ID, quote name, and user who created the quote.
**To sort by column heading**
* Click the up/down triangles next to a column heading.\
The table columns reload, if necessary.
* Click the heading again to reverse the order.\
The triangle color reflects the current bidirectional sort order.
**To delete a quote**
1. On the Saved Quotes page, click the down arrow next to the quote.
2. Choose **Delete**.
3. Click **Yes** to confirm.
You can only delete quotes with a *Saved* status.
## Editing a quote
It's easy to change or duplicate a saved quote. For example, you can add a new service, add a Virtual Cross Connect (VXC) to a previously created service, or create a quote based on an existing quote.
Quotes that have been registered cannot be edited. They can be viewed and duplicated to create a new quote, which can then be edited.
**To edit a quote**
1. On the Saved Quotes page, click **Edit** next to the quote.
2. Make the required changes.\
For example, change the term of a service or add a new connection.\
The changes to the quote are reflected in the pricing.
3. Click **Save**.
4. To return to the Saved Quotes page, click **Close**.
**To create a quote based on an existing quote**
1. On the Saved Quotes page, click the down arrow next to the quote.
2. Choose **Duplicate**.\
A prompt is displayed confirming the quote was successfully duplicated. The new quote is added to the Saved Quotes page, with *(Duplicate)* added to the quote name.
3. Click **Edit** to make changes to the new quote.
4. Enter a unique descriptive name in the **Quote Name** field to identify the quote.
5. Make any changes unique to this quote. For example, add a new service or connection, or change an existing service or connection.\
Duplicating a quote doesn't copy the Submitted Date, or the Created By and Created Date values. These fields are unique for each quote. The Created By and Created Date values automatically populate with the current logged-in user and date.
6. Click **Save**.
## Comparing pricing for different terms and currencies
The Advanced View lists every service and its add-ons in a single table, showing the monthly rate for every available term, currency, and pricing level you have chosen to display.
From the Advanced View, you can add or remove terms and currencies to change the pricing display. This enables you to compare pricing for different terms and currencies side by side, for each service in the quote.
**To compare pricing for different terms and currencies**
1. Click **Analyze & Export** in the Quote Builder to open the Advanced View.
2. Use **Display Terms** to select the terms for which you want to display pricing. You can select one or more terms, and the table updates to show the monthly rate for each service for every selected term.
3. Use **Display Currency** to select the currencies for which you want to display pricing. You can select one or more currencies, and the table updates to show the monthly rate for each service for every selected currency.
The selected terms and currencies carry over into the downloaded CSV or PDF file. The Advanced View also includes a **Download CSV** button and a **Download PDF** button.
## Add-on pricing
When you add an optional add-on (IPsec, Cross Connect, or DDoS Protection) to a service or connection, the Quoting Tool displays an **Includes** indicator with the add-on name on that item, both in the Network Design list and in the Advanced View. A service or connection can display more than one indicator when it has multiple add-ons.
The quote pricing also reflects add-on charges:
* Each service's summary price and the quote subtotal includes the monthly add-on charges, and they recalculate when you change the term.
* In the Advanced View, each add-on appears as a separate line item beneath its service, showing the monthly charge for every available term. When partner pricing is shown, the add-on line items repeat beneath the partner row.
* A term with no add-on charge displays **N/A** instead of a zero amount.
## Downloading a quote
You can download a quote in two formats: PDF and CSV. The PDF version is ideal because it includes the quote details on a Megaport letterhead and a legal disclaimer that the quote is non-binding. Once the quote is downloaded, you can share it for review.
**To download a quote**
1. On the Saved Quotes page, click **Edit** next to the quote.
2. Click **Analyze & Export**.
3. Choose **Download CSV** or **Download PDF**.
* **Download CSV** -- Downloads the quote in the comma-separated values (CSV) format. You can use the CSV file to import the data into spreadsheets and databases. You can open the CSV file in any text editor.
* **Download PDF** -- Shows a preview of the formatted data. Before you print or save the file, you can optionally include these sections:
* **About Section** -- Include or edit the introductory paragraph that describes Megaport.
* **Tax Registration Number** -- Enter a tax registration number to include on the PDF.
* **Company Address** -- Enter a company address to include on the PDF.
Click **Print PDF** to open the Print dialog box. You can then either save to PDF or print. When you are finished, click the browser back button to return to the previous page.
When you download a quote as a CSV or PDF, the file reflects the terms, currencies, and pricing level (retail, partner, or both) you have chosen to display, along with diversity zone information for each service.
## Logging out
Click **Logout** to safely log out of the Megaport application.
If you have the Megaport Portal or Quoting Tool open in multiple tabs in the same browser, logging out in one tab automatically logs you out of all other open tabs of that application. The other tabs update immediately without requiring a refresh and display a message with a link to log in again.
This behavior applies only to tabs in the same browser and is application-specific. Logging out of the Megaport Portal does not log you out of the Quoting Tool, and vice versa.
## Helpful references
* [Billing Overview](/finance/overview)
* [IX Pricing and Contract Terms](/finance/ix-pricing)
* [MCR Pricing and Contract Terms](/finance/mcr-pricing)
* [Megaport Internet Pricing and Contract Terms](/finance/megaport-internet-pricing)
* [Megaport Object Storage Pricing and Contract Terms](/finance/storage-pricing)
* [MVE Pricing and Contract Terms](/finance/mve-pricing)
* [NAT Gateway Pricing and Contract Terms](/finance/nat-gateway-pricing)
* [Port Pricing and Contract Terms](/finance/port-pricing)
* [Quoting Service Cost](/finance/creating-estimates)
* [VXC Pricing and Contract Terms](/finance/vxc-pricing)
# Services Overview
Source: https://docs.megaport.com/partners/services/intro
This help topic provides an overview of viewing and managing services for a partner account or on behalf of a customer.
This topic provides an overview of creating and viewing Megaport services for partner and managed accounts.
## Estimating service cost
You can estimate the cost of Megaport services for partner and managed accounts before actually ordering the services.
For more information about estimating cost for managed users, see [Quoting Service Cost](/partners/services/creating-estimates).
## Creating and ordering services
Partners often use the Partner Portal to order services for their customers. Partners also allow some customers to provision services directly.
Suppose a partner orders a Port and a Virtual Cross Connect (VXC) for a customer in the Partner Portal, and then decides to add another Port with a connection to a Cloud Service Provider (CSP). After provisioning these initial services, a partner can then allow the customer to further provision services themselves in the Partner Portal using their managed account.
For more information about creating services and the ordering restrictions for managed users, see [Creating and Ordering Services](/partners/services/creating).
## Viewing services
From the Services page, a user logged in to a partner account can see all services.
You can switch to a managed account to view that customer's services. For more information, see [Viewing Services](/partners/services/viewing-services) and [Switching Account Types](/partners/account/moving).
## Monitoring maintenance and outage events
The Maintenance & Outages page allows you to monitor maintenance and outage events that affect your services, including current, scheduled, and past events.
For more information, see [Monitoring Maintenance and Outage Events](/partners/services/monitoring-events).
# Monitoring Maintenance and Outage Events
Source: https://docs.megaport.com/partners/services/monitoring-events
This help topic describes the Service Status page and its features.
The Service Status page allows you to monitor maintenance and outage events that affect your services, including current, scheduled, and past events. By staying informed about maintenance activities and service outages, you can plan effectively around scheduled maintenance and provide faster responses during unplanned outages.
Event notifications for service maintenance and outages are sent via email and displayed on the Service Status page. You can quickly access these events and drill down to see the affected services.
For partner and managed accounts, access to the Service Status page is available to both partners and managed accounts. If you, as a partner, want to monitor events for your managed accounts, switch from a partner account to a managed account and access the Service Status page.
Follow these steps to learn how to use the Service Status page.
**To monitor maintenance and outage events**
1. Access the Service Status page in one of these ways:
* Log in as a partner or switch from a partner account to a managed account and click **Service Status**.
* On the Services page, click (Extra Actions) > **Service Status**.
Alternatively, maintenance and outage events are displayed on the Services page for the duration of the ongoing event. Click **View** to access the event on the Service Status page.
2. On the Service Status page, select **Maintenance** or **Outages** to filter the events accordingly.
The maintenance and outage events data automatically refreshes every 5 minutes, but you can also click **Refresh** to get the latest updates immediately.
3. Filter events:
* Search for any text or find a specific event related to a product by entering the product ID.
* For maintenance, filter by:
* **Scheduled** -- Events that are planned but have not started yet.
* **Ongoing** -- Events that are in progress.
* **Completed** -- Events that were completed within the last 90 days.
* **Cancelled** -- Events that were cancelled within the last 90 days.
* For outages, filter by:
* **Ongoing** -- Events that are in progress.
* **Resolved** -- Events that were resolved within the last 90 days.
4. Select the required timezone from the Timezone (UTC) drop-down list.
For example, to select the timezone for Chicago (UTC-5), type **Chicago** in the **Timezone** field then select **America/Chicago**.
* If you select a timezone on the **Maintenance** tab, it will apply only to the maintenance events. Similarly, if you select a timezone on the **Outages** tab, it will apply only to the outage events.
* If you sign out, the timezone resets to the default (UTC).
5. View maintenance events in a **List** or **Calendar** view.
The **Calendar** view allows you to see the start and end times of maintenance events visually, making it easier to track upcoming activities.
In the **Calendar** view, you can toggle between month, week or day views. Double-clicking on a day in the month or week view will narrow the focus to the corresponding day. From there, click the event to view the full details of the event similar to how it appears in the **List** view.
6. Sort events:
* **Status** -- Sort events based on their status, such as Scheduled, Ongoing, Completed, and Cancelled for maintenance events, or Ongoing and Resolved for outages.
* **Start Date** -- Sort events by their start date in ascending or descending order.
7. After you find the service event, you can view detailed information about the affected services.
To search for events related to a particular service, copy the service ID of an event to your clipboard by clicking on it. You can then paste it into the **Filter** field to search for that service. Make sure that relevant filters (Scheduled, Ongoing, Cancelled, Completed) are enabled to see all results.
You can also click **Logs** to view the service logs for the selected service.
If no results are found that match your criteria, try adjusting the filter settings to broaden your search.
# Service Approval Queue
Source: https://docs.megaport.com/partners/services/service-approval-queue
This help topic describes the Service Approval Queue for partner accounts and managed accounts.
The Service Approval Queue allows users in managed accounts to configure services, but prevents them from ordering services. Users can instead submit service configurations for approval by a Technical Contact, Technical Admin, or Company Admin in the Partner company.\
This helps to:
* **Improve control** -- Provides partners with a way to approve or deny orders made by their managed accounts, so there is less risk of unwanted charges.
* **Prevent mistakes** -- Prevent non-technical users from accidentally ordering, changing, or terminating services, which can cost money and create extra work to fix.
* **Make approvals easier** -- Instead of handling approvals in the shopping cart, this provides a queue for managing all approval requests.
For information about user roles, see [Managing User Roles](/partners/account/profiles).
## Activating the Service Approval Queue
To activate the Service Approval Queue for a managed account, either:
* Activate it when creating the managed account. For more information, see [Creating a Managed Account](/partners/account/create-managed).
* Update the configuration for the managed account.
**To activate the Service Approval Queue**
1. Log in as a Company Admin.
2. Click **Partner Admin** in the left navigation.\
The Managed Accounts page opens.
3. From the Manage Accounts page, find the account to modify.\
You can use the filter at the top of the page to focus the list.
4. Click **Edit** next to the managed account.
The Account Overview for the managed account is displayed.
5. Select the **Feature Configuration** tab.
6. Turn on the **Service Approval Queue** setting to activate the service approval queue for the managed account.
## How users request service creation, changes, or termination
When the Service Approval Queue is active for a managed account, the procedures for creating, changing, and terminating service configurations are the same as when the Service Approval Queue is not active. When the user reviews their order to finalize it, they will have the option to **Send for Approval** instead of **Order Now**. After submission, the service disappears from your cart until approved, and you can track your request by clicking **Manage Orders**.
You cannot add connections to a service that has a pending termination request. To resolve this:
* wait for the request to be approved or rejected.
* withdraw the termination request if you no longer want to terminate the service.
For information about ordering services, see [Creating and Ordering Services](/partners/services/creating).
## Add-on requests
When the Service Approval Queue is active for a managed account, add-on requests also go through the approval process. For information about reviewing and approving these requests, see [Reviewing and approving requests](#reviewing-and-approving-requests).
The following add-ons are included in the approval workflow:
* Cross Connect add-ons for Ports
* IPSec add-ons for MCRs
## Reviewing and approving requests
The **Manage Orders** option in the left navigation shows the number of pending requests (if there are any). Partner accounts will always see this option, but managed accounts will see **Manage Orders** only if the partner has activated the Service Approval Queue for their account. This opens the Order Requests page, which:
* **For partners** -- Lists requests for review.
* **For managed users** -- Lists the requests they have submitted for approval.
Partners will receive an email notification when a managed account submits an approval request.
To view pending orders from managed accounts, at least one managed account must have **Service Approval Queue** set to **Required**. If no managed accounts have this setting enabled, the Order Requests page displays a warning message with a link to **Partner Admin** where you can configure this setting.
Pending requests must be approved or rejected within 7 days. After 7 days, requests will automatically expire and cannot be changed. The managed account user must submit a new configuration for approval.
**To view, approve, or reject a request**
1. Click **Manage Orders**.
2. On a **PENDING** request, click **Review** to open the Review Order screen.
3. Click one of the following options:
* **Approve** -- Approve the request and deploy the service(s) requested.
* **Reject** -- Reject the request with a comment for the requester about why you are rejecting it.
* **Close** -- Close the Review Order screen without approving or rejecting the request.
After approving or rejecting a request, the requester will receive an email notification about the decision.
## Viewing historical requests
To view requests that have already been processed, clear the **Pending Only** check box on the Order Requests page. This will show all requests, including those with these statuses:
* **PENDING** -- Requests that are awaiting review and decision.
* **APPROVED** -- Requests that were approved and processed.
* **REJECTED** -- Requests that were reviewed and denied.
* **WITHDRAWN** -- Requests that were withdrawn by the requester.
* **EXPIRED** -- Requests that were not approved or rejected within 7 days and have automatically expired. Expired requests cannot be changed. The managed account user must submit a new configuration for approval.
# Viewing Services
Source: https://docs.megaport.com/partners/services/viewing-services
This help topic describes the Services page and its features.
This topic describes how to use the Services page for partner accounts and managed users.
The Services page provides a bird's eye view of Megaport services. You can view, configure, and edit your Ports, MCRs, MVEs, NAT Gateways, and their connections (VXCs, Megaport Internet, and IXs). Each connection is grouped under its associated Port, MCR, MVE, or NAT Gateway.
Partners can switch to a managed account to view that customer's services. For more information, see [Switching Account Types](/partners/account/moving) and [Understanding the Services Page](/partners/services-page).
## Sorting and filtering services
The sorting and filtering tools allow you to customize the Services page to help you find the information you need.
You can change the order of the services in ascending or descending order, and sort them according to the following criteria:
* **Creation Date** -- Sorts the services by the date they were created.
* **Name** -- Sorts the services by name, in alphabetic order.
* **Location** -- Sorts the services by country, and then by the location within that country.
You can only sort Ports, MCRs, MVEs, and NAT Gateways, not their connections (such as VXCs or IXs), which are displayed in the order they were added.
To narrow the services shown on the page, enter your search in the **Filter Services** field. The filter will match against the name, location, and ID of the services. Any services matching your search will be highlighted.
You can hide or show all the connections for a Port, MCR, MVE, or NAT Gateway. By default, the Portal shows all the connections unless there are more than 10, in which case they will initially be collapsed. Click the down arrow to expand all connections under a service, or click the up arrow to hide them.
## Viewing and editing services
By default, services are listed by the date they were created. VXCs, Megaport Internet connections, and IXs are grouped under each Port, MCR, MVE, or NAT Gateway.
### Service status
The icons for each Megaport service change color to indicate their provisioning status. Any important information relating to the status is shown under each service, such as a pending approval, a cancellation, or a missing billing market.
| **Icon** | **Color** | **Service Status Description** |
| :- | :- | :- |
| | **Green** | The service is configured and live. |
| | **Gray** | The service is not live. This can happen for a number of reasons, for example, the service could be in the process of being deployed, or a Port could be waiting for connection approval from the data center. |
| | **Orange** | The status of this service is unknown. |
| | **Red** | The service is down. |
Each service on the page provides icons so you can modify Port, MCR, MVE, NAT Gateway, VXC, IX, and Megaport Internet configurations at any time. For more information, see [Understanding the Services Page](/portal-admin/services-page#servicedetails).
# Setting Up a Partner Account
Source: https://docs.megaport.com/partners/setting-up/index
This help topic explains how to set up a partner account for access to the Partner Portal.
This topic describes how a new partner account is created for access to the Partner Portal.
## Partner account overview
A partner account centralizes the control and management of multiple organizations through one portal. Partner administrators can view top-level data for their end customers and provision and manage services for any organization they administer.
Partner accounts are created:
* After all legal terms and conditions are approved.
* Without any existing services.
An existing direct customer account cannot be converted to a partner account.
## Request a partner account
Contact your Megaport sales team to create a new partner account and configure settings corresponding to that account. For a list of settings, see [Feature access and views by account type](/partners/access#managedisplay).
After the partner account is created, Megaport provides the Partner Portal account details to the Company Admin by email.
## Getting started in the Partner Portal
Once a partner is enrolled in the Partner Program, Megaport sets up the partner account in the Partner Portal. The partner designates a primary user, who receives an automatically generated email from the Partner Portal with their login credentials and a reminder to change their password.
After your partner account has been created and you’ve received your login credentials, you must log in to the account, create a company profile, and set up billing markets. For more information, see [Updating a Company Profile](/setting-up/company-profile) and [Enabling Billing Markets](/finance/enabling-market). Your partner account was registered when Megaport created it.
When logged in to a partner account, the company switcher in the breadcrumb shows your partner account name and **Partner Admin** is available in the left navigation.
To enable all data center locations, set up all billing markets.
### Verifying your company and Company Admin details
Before setting up managed accounts, make sure that all of your details are correct in the partner account.
**To verify partner account details**
1. Choose User Menu > Admin Settings > Company Profile and verify the details.
2. Choose User Menu > Admin Settings > Account Contacts and verify the Technical Support Team phone number and email address.
3. Choose User Menu > User Settings > Profile and verify the details.
# Contacting Support
Source: https://docs.megaport.com/partners/support/contact
This help topic describes how to contact the Megaport Support team.
Need help with something? A great first step is to check out the Megaport Documentation on this site and save yourself the time collating relevant information and lodging a support request. We regularly update our content to address common call drivers.
If you need further support or information, get in touch with our dedicated Support teams, who are ready to guide you through everything from creating a Megaport account, provisioning network connections, responding to incidents, to answering general inquiries.
Megaport only provides service-related support to partners via the partner contacts specified in the Megaport Portal account, not to users of any managed accounts. Unless otherwise agreed between Megaport and the partner in writing, the partner is responsible for providing support to their customers (GRA, Clause 2).
## Support Requests Portal
Your primary support channel is the Support Requests Portal. Use the Support Requests Portal to create, manage, and follow up on support cases. Our Support team will monitor and process your support cases.
For more information, see [Support Requests Portal](/partners/support/support-portal).
## Partner Portal live chat 24/7/365
Reach out to our in-house Support team any time of day or night. Log in to
[the Partner Portal](https://portal.megaport.com) and click the blue live chat icon to start a conversation.
## Phone
Contact our Support team through the number best for your region.
For members of our Partner Program, select Option 2 when calling Megaport Support.
* Australia +61 7 3062 7601
* New Zealand +64 508 050 877
* USA +1 425 954 2777
* United Kingdom +44 1 202 286 622
* Germany +49 32 211 121 713
* Hong Kong +852 800 906 081
* Japan +81 120 645 081
## Support levels and responsibilities
Before escalating an issue to Megaport, it is expected that partners provide Level 1 and 2 support to the end customers as defined in the following table.
The scope of support is limited to Megaport provided services. However, partners are required to investigate all potential contributing symptoms and components up to and beyond Megaport demarcations before escalating to Megaport at Level 3.
Issues upstream from Megaport within a cloud provider network or other cloud are out of scope for Megaport Support and should be reported directly to the provider’s support team.
| **Support Level** | **Assistance Scope** | **Issues Covered** |
| - | - | - |
| Level 1 | Basic help desk resolution and service desk delivery | Support for basic customer issues such as solving usage problems and fulfilling service desk requests that need IT involvement.
If no solution is available, level 1 personnel escalate incidents to a higher level.
Typical L1 Troubleshooting
Customer premises equipment (CPE)
Customer Local Area Network (LAN)
Customer Wide Area Network (WAN)
Customer Data Center Connections
Customer Application Issues
Customer Premises Power
Customer Premises Configuration
Confirm service is not affected by Partner, Cloud Provider, Megaport or any other service provider
|
| Level 2 | In-depth technical support | Experienced and knowledgeable technicians assess issues and provide solutions for problems that cannot be handled by level 1.
If no solution is available, level 2 support escalates the incident to level 3.
Typical L2 Troubleshooting
Routing and switching issues within Customer LAN & WAN
Verifying service configuration complies with product specification
Isolating the issue into Customer Cloud Provider Network
Physical connectivity investigation, including fiber optical up to Megaport demarcation point
Utilizing diagnostics tools in Megaport Portal
Utilizing Megaport Documentation Portal to verify product operation
|
| Level 3 | Expert product and service support | Access to the highest technical resources available for problem resolution or new feature creation.
Level 3 technicians attempt to duplicate problems and define root causes, using product designs, code, or specifications.
Partners who are unable to resolve level 1 and level 2 calls may contact Megaport level 3 support through the live chat feature in the Partner Portal.
Typical L3 Issues
Multiple Megaport provided services affected at the same time
Services have not recovered after Megaport maintenance scheduled finish time
Any functionality in the Megaport Partner Portal generating an error
Physical connectivity to Megaport remains down following L1/2 troubleshooting
|
## What you need before lodging a support request
Providing the correct information to Megaport is critical for efficient and effective assistance. When engaging our team, include the following information:
* Service ID(s)
* Company / organization
* Description of request
When reporting an incident, also include the following information.
* Problem symptom
* Start time of issue
* End time of issue (if resolved/mitigated)
* What changes or actions were performed before the issue started?
* What troubleshooting steps have already been taken?
# Megaport Partner Program Support Services
Source: https://docs.megaport.com/partners/support/index
This help topic describes the Megaport Support team.
We’re here to help.
Megaport offers a wide variety of support resources designed to enhance the value of your Megaport services. These resources and tools provide several approaches to find solutions and solve problems.
## Megaport Support team
Megaport’s global Support team is available around the clock (24 hours a day, 7 days a week, 365 days a year) to help customers quickly and easily use, manage, and troubleshoot the Megaport products in their network.
Our follow-the-sun support model ensures that high-priority cases can be transferred seamlessly to provide continuous coverage when working to solve critical problems. By using a single unified case tracking system, Megaport Support engineers know they are working with the latest details and status of each case.
The Megaport Support team responsibilities are divided among Technical Support Engineers (TSE), Network Operations Centre (NOC) Engineers, and Operations Engineering (OpsEng).
### Technical Support Engineers (TSE)
TSEs are responsible for all customer-facing activity and communications, such as:
* assisting with incidents
* provisioning new services
* sending maintenance notifications
* answering general inquiries
### Network Operations Centre (NOC) Engineers
TSE escalate any customer issues that they are unable to resolve within their triage processes to the NOC Engineers team. This team is responsible for monitoring the production network and managing any incidents that affect multiple customers. If required, the NOC team will escalate issues to resolutions teams, including third-party backbone providers, data center operators, cloud service providers, or Megaport engineers.
### Operations Engineers
NOC Engineers escalate any customer issues that they are unable to resolve within their triage processes to the Operations Engineering team.
The Operations Engineering team is responsible for the maintenance of the production network. Their area of responsibility is broad and ranges from network software and hardware upgrades to activation of new network components to support expansion. They are also the final escalation point for the Customer and NOC Engineers.
# Network Maintenance
Source: https://docs.megaport.com/partners/support/maintenance
This help topic describes Megaport network maintenance details.
## Why does Megaport perform maintenance?
To ensure uptime and the ongoing stability of the Megaport network, Megaport occasionally performs routine scheduled maintenance. This maintenance might include physical moves, logical changes, or software upgrades.
In rare circumstances where a network fault occurs that impacts partner services, Megaport will perform emergency restorative maintenance.
## Partner services affected by works performed by Cloud Service Providers
Megaport will provide notice for Cloud Service Provider maintenance only if the work impacts the Megaport redundant services. We recommend that all partners are subscribed to the Cloud Service Providers maintenance notices to receive all information related to your cloud services.
## When will I be notified?
When planned maintenance work is required, Megaport will provide all partners with a minimum of 14 days notice as per our [Global Services Agreement](https://www.megaport.com/legal/global-services-agreement/).
For emergency maintenance works, Megaport will strive to provide partners with as much notice as possible; however, the notice period can be limited depending on the severity of the network interruption.
It is the responsibility of a Megaport partner to notify its end customers of any scheduled network maintenance.
Works performed upstream from Megaport’s Network by Cloud and SD-WAN providers are sent by the provider directly to their end customers in accordance with the signed agreement between both parties. Megaport has no visibility of these works.
## How will I be notified?
Megaport partners who have signed up for Partner Program accounts and have their notifications enabled will be notified of all Megaport maintenance works.
To learn how to assign new user roles and configure email notifications, see these topics:
* [Adding and Modifying Managed Account Users](/partners/account/user-management)
* [Managing User Roles](/partners/account/profiles)
* [Configuring Email Notifications](/partners/account/notifications)
If you have a partner-managed account, your partner will communicate with you about any maintenance events that affect your account.
## What does a maintenance notice look like?
Megaport maintenance notices are similar to the example shown here. Details include the reason for the maintenance event, the services that will be impacted, and the length, date, and time of the event.
# Understanding Support Requests
Source: https://docs.megaport.com/partners/support/requests
This help topic describes how to create a support request for an incident, provisioning assistance, or general inquiries.
All incoming support requests are assigned to our Customer Support Team for investigation. If necessary, the team escalates the issue internally to ensure a speedy resolution. For more information, see [Escalating Support Cases](/partners/support/requests-escalation).
Requests are grouped into one of three categories: incidents, provisioning, or general inquiries.
## Incidents
An *incident* is a support request about a previously active service that has ceased functionality, or has degraded to being highly unusable. Incidents do not include new service provisioning issues or general inquiries.
### Severity and response goals
Megaport sets the severity level for each submitted incident. The severity level defines the targeted time frames for the initial response from Megaport and escalation potential. This process assists the appropriate resources within Megaport manage problems quickly and efficiently according to their severity level.
All incidents are prioritized according to their impact on the partner (1 through 3), with 1 being the most critical. The priority of the incident can be upgraded or downgraded depending on troubleshooting progress.
This table outlines Megaport Support targets for initial response time, how often you can expect an update and time to restore a service, prioritized by severity level.
| **Severity Level** | **Initial Response** | **Update Frequency** | **Time to Restore** |
| - | - | - | - |
| 1 - Service loss. Service is down or severely degraded. These incidents can severely impact the partner’s ability to conduct business. This can mean that the services are down or not functioning and no procedural workaround exists. | 15 minutes | 30 minutes | 6 hours |
| 2 - Service is partially degraded or intermittently failing. These incidents are high-impact problems that disrupt the partner’s business operation but there is capacity to remain productive and maintain necessary business level operations. | 15 minutes | 60 minutes | 24 hours |
| 3 - Incidents without impact to service. These incidents are minor or no impact problems that involve partial loss of noncritical functionality. | 30 minutes | 4 hours | 48 business hours |
The *Time to Restore* estimates only apply to incidents. The target time to restore is counted from the time the partner reports the issue to Megaport Support and an incident ticket is created.
Megaport Support makes continuous efforts to isolate, diagnose, and deliver a workaround or repair during Megaport's normal local business hours. When the severity level has been downgraded, the support team follows the appropriate guidelines.
### Caveats
* Any period of time that Megaport Support waits for additional information from the partner is not included in the target restore time.
* If Megaport Support provides a new written date and time for an update, this replaces the previously quoted *Update Frequency* estimate.
## Provisioning
Provisioning requests involve activating new services or troubleshooting issues that relate to service activation. These requests are not assigned severity levels; however, they are handled as a high priority and are resolved as quickly as possible.
## General inquiries
Inquiries are information requests sent to Megaport that are not related to an incident. Inquiry requests are automatically set to Severity 3, as they do not impact any services.
### Solution Architect or Sales questions
Megaport’s Partner Solution Architects can help address any questions on architecting your network, configuring your services, or designing solutions.
If you have any questions for our Solution Architects or Sales Team, see the [Sales page](https://www.megaport.com/contact/sales/) on the Megaport website.
### Billing questions
For questions about your Megaport invoice, start with any of these topics:
* [Viewing and Downloading Invoices](/partners/billing/invoices)
* [Understanding Your Megaport Partner Invoice](/partners/billing/understanding-invoices)
For billing or invoice issues or questions, contact Megaport Accounts Receivable.
# Escalating Support Cases
Source: https://docs.megaport.com/partners/support/requests-escalation
This help topic describes how to escalate a support case for an incident.
All incoming support requests are assigned to our Customer Support Team for investigation. If necessary, the team escalates the issue internally to ensure a speedy resolution.
Requests are grouped into one of three categories: incidents, provisioning, or general inquiries. For more information, see [Understanding Support Requests](/partners/support/requests).
## Escalating a case
You might need to escalate an existing case if circumstances change. Here are some guidelines on when to escalate a case:
* There has been an increase in the impact to your business
* The issue is not being resolved quickly enough
* The support effort is not meeting expectations
Start your case at escalation Level 1. For reference, the escalation path is as follows:
| Level | Contact | Service Loss | Service Degradation |
| - | - | - | - |
| 1 | Global Customer Support Manager Email: [csopm@megaport.com](mailto:csopm@megaport.com?subject=Level%201%20Support%20Case%20Escalation) | 2 hours | 12 hours |
| 2 | VP of Customer and Network Operations Email: [cnsm@megaport.com](mailto:cnsm@megaport.com?subject=Level%202%20Support%20Case%20Escalation) | 6 hours | 24 hours |
| 3 | Chief Operating Officer Email: [coo@megaport.com](mailto:coo@megaport.com?subject=Level%203%20Support%20Case%20Escalation) | 12 hours | 48 hours |
# Support Requests Portal
Source: https://docs.megaport.com/partners/support/support-portal
This help topic describes the Support Requests Portal, and how to use it.
The Support Requests Portal allows you to create, update, and monitor support cases in one centralized location. It is the preferred method for managing all support-related interactions.
Access to the Support Requests Portal is through the Megaport Portal.
If you have any problems with access, contact your Company Admin.
**To access the Support Requests Portal**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Support Requests.
The Support Requests Portal home page opens in a new tab.
## Support Requests Portal home page
The Support Requests Portal home page allows you to create, view, and manage support cases for partner accounts and managed accounts.
The portal header remains the same in all areas of the Support Requests Portal.
It includes these options:
* **Megaport** icon -- This takes you to the Support Requests Portal home page in the same tab. The **Home** tab performs the same function.
* **Portal** -- This takes you back to the Megaport Portal in the same tab. You will return to the page you were on when you clicked Support Requests Portal.
* **Documentation** -- This opens the Megaport documentation in a new tab.
* **Logout** button -- This logs you out of the Support Requests Portal, but leaves you logged in to the Megaport Portal. You are redirected back to the last page you were on in the Megaport Portal.
### Switching Accounts
As a partner account, you can change accounts to a administer the support requests for a managed account.
If you switch to a managed account, you will only see cases for that managed account.
If you switch to a partner account, you will see all cases associated with all managed accounts for that partner.
**To switch from a partner account to a managed account**
1. While logged in to the partner account, go to the Support Requests Portal.\
The upper-left corner of the Support Requests Portal home page confirms that you are in a partner account.
2. Select a managed account from the Select Account drop-down list on the right.
3. Confirm that you want to switch from a partner account to a managed account.
The upper-left corner of the Support Requests Portal home page confirms that you are in a managed account.
**To switch from a managed account to the partner account**
When the focus is on a managed account you can change back to your partner account.
1. On the managed account Support Requests Portal home page, select the partner account from the Select Account drop-down list.
2. Confirm that you want to switch from a managed account to the partner account.\
The upper-left corner of the Dashboard confirms that you are in a partner account.
**To switch from a managed account to another managed account**
1. From the managed account Support Requests Portal home page, select the managed account from the Select Account drop-down list.
2. Confirm that you want to switch from one managed account to another.
## Case status
The home page displays a list of your support cases. There are two tabs:
* **Open** -- Shows new, open, and resolved cases.
* New cases are raised, but not yet addressed by the Megaport support team.
* Open cases have been investigated by the Megaport support team, and are in progress.
* Resolved cases have gone through the case workflow, and are pending customer review.
Resolved cases are shown for eight calendar days after they have been set to resolved. You can reopen the case during this time, if required. After eight days, resolved cases are closed and cannot be reopened.
* **Closed** -- Shows closed cases.\
Only cases closed since 1st December 2025 will be listed on the Closed tab. Cases closed earlier than that date will not be shown on the Support Requests Portal.
The case list shows all cases associated with the partner account or managed account, not just cases you have created.
## Creating a support case
You can create and manage your own support cases using the Support Requests Portal.
**To create a support case**
1. On the Support Requests Portal home page, click **+ Create Case**.
2. Enter these details:
* **Subject** -- Enter the a brief summmary of your case.
* **Description** -- Enter a detailed description explaining the reason for your issue or request, including any troubleshooting steps you have completed.
* **Request Type** -- Select the most relevant request type for your issue or request from the drop-down list.
* **I need to speak to someone about my invoice** - Use this for billing enquiries.
* **I have a general enquiry** -- Use this when you have an enquiry that is not covered by the other request types.
* **I need to report an issue with a previously working service (incident)** -- Use this when you have a problem with your Megaport network.
* **I need assistance with a new set up (Provisioning)** -- Use this for help when you are setting up a service and you can't find the answer in the Megaport documentation.
* **I would like to speak to a sales person** -- Use this if you want to expand your Megaport network.
For more information about request types, see [Understanding Support Requests](/partners/support/requests).
If you select a request type of **I need to report an issue with a previously working service (Incident)** or **I need assistance with a new set up (Provisioning)**, you will see a **Service ID** field. You must enter the service ID of the service you are reporting a problem with.
**To find and use the service ID**
1. Search for the service you are reporting a problem with on the Services page of the Megaport Portal.
2. Next to the service entry, click the service ID button to copy the service ID.
3. Paste the service ID into the **Service ID** field on the Create Case screen of the Support Requests Portal.
* **Collaborators** -- (Optional) Add the email addresses of people you want to be included in interactions and updates on this issue. If the person is known to the Support Requests Portal, their email address will appear when you start typing. If they are not known to the Support Requests Portal, you can enter the email address.
3. Click **Save**.
The new case will appear on the case list on the Support Requests Portal home page.
## Searching your case list
You can search your case list using the **Search** field.
You can search on these fields:
* Case ID
* Created by
* Creation date
## Sorting your case list
You can sort your case list by any field, in either ascending or descending order.
The up or down arrow next to a column heading indicates the current sort order.
* In the Support Requests Portal home page, click the small up/down arrow next to the field name on the case list heading.
The case list reloads.
* Click the arrow again to reverse the sort order.
## Viewing and updating support case details
To view the details of a support case and add more information, click the case **ID** number in the list on the home page.
On the view details page, you will see these tabs:
* **Comments** -- Add more information to the case when it becomes available.\
Click **Submit Comment** to add your comment to the case.
* **Details** -- This tab lists the case details, such as service ID, name, case type, created date, created by, and status. You cannot update these fields.
* **Attachments** -- You can provide additional information by uploading attachments. Valid file types are PDF,
JPG, PNG, and TXT.
1. Click **Upload file** then select your file from the list.\
You will be asked to add a file description.
2. Enter the file description and click **OK**.\
The file description will be added to the comments list.
The **Back** button will take you back to the Support Requests Portal home page.
# Providing Support Contact Details
Source: https://docs.megaport.com/partners/tech-support-details-partner/index
This help topic describes how to provide your internal tech support contact details in the Megaport Portal.
To streamline communication between the Megaport Support team and your organization, we need to know how to contact your internal support team. During the initial account setup, a Company Admin or Sales Team member enters the support phone number and email. These details provide a way for us to reach out if you need any assistance.
Here are the contact detail requirements by account type:
| **Account Type** | **Supported By** | **Contact Details Required?** | **Details Displayed in Megaport Portal?** |
| :- | :- | :-: | :- |
| New direct | Megaport | Yes | Yes |
| Existing direct with no provisioned services | Megaport | Yes | Yes |
| **New partner** | **Partner** | **Yes** | **Yes, visible in managed account list.** |
| **New partner** | **Megaport** | **Yes** | **Yes, visible in managed account list.** |
| **New managed** | **Megaport** | **Yes** | **No** |
| **New managed** | **Partner** | **No** | **No** |
After the support details are added to an account, they can be edited by certain account users but they cannot be deleted. The viewing and editing permissions by account type are:
* Company Admins can view and edit support contact details.
* Direct account users can view the support contact details, but cannot edit them.
* Managed account users supported by their partners can view the support contact details, but cannot edit them.
* Managed account users supported by Megaport cannot view or edit support contact details.
New and existing accounts without any provisioned services cannot place orders until their account setup is complete, including support contact details and a billing market. For more information, see [Enabling Billing Markets](/finance/enabling-market). You can still add services to a saved configuration and view pricing, but the services cannot be ordered until account setup is complete.
**To edit support details**
1. Visit the Megaport Portal and log in.
2. Choose User Menu > Admin Settings > Account Contacts.
3. Enter the phone number of your internal support team.\
The number is validated against the billing market format of your billing contact phone number.
4. Enter the email address of your internal support team.\
The email format and address is validated against the email address provided during account sign up.
5. Click **Save**.
# Troubleshooting Overview
Source: https://docs.megaport.com/partners/troubleshooting/index
This help topic introduces the troubleshooting section.
This section helps you investigate errors and unexpected behaviors with your Megaport services. Each topic includes troubleshooting suggestions as well as next steps.
| **Feature** | **Topics** |
| :- | :- |
| **Activation** |
[Activating Ports](/troubleshooting/activation)
[Errors When Ordering](/troubleshooting/errors/automation-fails)
|
| **Ports and VXCs**
|
[Port or VXC is Down or Flapping](/troubleshooting/port/down)
[Port Latency](/troubleshooting/port/latency)
[Port or VXC Packet Loss](/troubleshooting/port/packet-loss)
[Throughput or Speed](/troubleshooting/port/speed)
[Providing Debug Information for Faster Support](/troubleshooting/debug)
|
## Quick Tip Videos
## Helpful tools
* [ping](https://en.wikipedia.org/wiki/Ping_\(networking_utility\))
* [traceroute](https://www.fortinet.com/resources/cyberglossary/traceroutes)
* [packet capture](https://www.thousandeyes.com/learning/glossary/packet-capture)
# Partner Release Notes
Source: https://docs.megaport.com/partners/whatsnew/index
This help topic describes the latest additions to the Megaport Partner Portal and documentation.
This topic describes changes and enhancements that have been made to the Partner Portal.
For information about general Megaport Portal enhancements, see the [Megaport Portal Release Notes](/whatsnew).
* **Account Identifier for Managed Accounts** -- The Managed Accounts page has a new **Account Identifier** column, and the same field appears on the overview page for each managed account. You can sort the table by account identifier and copy the identifier when needed. For more information, see [Creating a Managed Account](/partners/account/create-managed).
This is in addition to the Account Reference that the partner sets when they create a new managed account, which is the unique identifier for the partner.
* **Company Switcher for Partner and Managed Accounts** -- Partners can now switch between their partner account and managed accounts using the company switcher in the breadcrumb at the top of the Portal. The breadcrumb displays the account you are currently viewing, and if you have access to multiple accounts, you can select the company name to switch accounts. When viewing a partner account, the company switcher lists its managed accounts and displays the managed account name and ID. For larger account lists, you can filter by account name or ID to quickly find the account you want to access. This replaces the previous managed account switcher in the side navigation. For more information, see [Switching Account Types](/partners/account/moving).
- **Quoting Tool Enhancements** -- These improvements have been made to the Quoting Tool:
* **Contract Details for Imported Services** -- When you edit an imported service, the edit screen now shows the service's contract length and contract end date.
* **Subtotals for Each Term** -- When a quote is priced across more than one term, the Advanced View and the downloaded PDF now show a subtotal for each term, in each currency that every service in the quote can be priced in. Previously, only a single subtotal was shown based on the active term selection, which made it difficult to compare monthly costs across term lengths without generating separate quotes.
* **All Currencies Selected by Default** -- When you open **Analyze & Export** for the first time, all available currencies are now selected.
* **IP Address Blocks** -- You can now quote IP Address blocks by metro, and import your existing Live and Configured IP Address blocks into a quote. Imported IP Address lines automatically carry over their held monthly pricing, display their subnet size across the quote and summary panels, and remain billed monthly without altering multi-term discount calculations.
* **Automatic Location Selection and Metro-Based Quoting** -- When you quote an MCR, MVE, or NAT Gateway, you can now choose **Auto** location mode, select a metro, and let Megaport choose the facility and diversity zone within it. **Manual** mode keeps the existing behavior of selecting a specific data center. In **Auto** mode, the available speeds, sizes, and rate limits reflect every orderable facility in the location rather than a single site, and the location is tagged Auto-selected.
* **Partner Co-Branding in Email Notifications** -- Partners can now enable co-branding for emails that Megaport sends to their managed users. When enabled, emails display the partner's logo alongside the Megaport logo, providing consistent branding across the Portal and email communications. For more information, see [Adding Custom Branding](/partners/account/custom-branding).
- **Quoting Tool Enhancements** -- These improvements have been made to the Quoting Tool:
* **Latitude.sh Products in the Quoting Tool** -- You can now quote Latitude.sh products directly.
* **Redesigned Add Services to Quote** -- Existing services are now grouped under Network to align with the Portal.
* **Contract Term End Dates for Imported Services** -- Now displayed in the Quoting Tool.
* **Quoting Tool Enhancements** -- We’ve now completed a series of Quoting Tool improvements over the past few months. Here are the most recent enhancements:
* **Quote Export Improvements** -- The Quoting Tool now allows you to export quotes in CSV and PDF format, reflecting the selected terms, currencies, and partner/retail discounts, including diversity zone information. The updated PDF export includes new optional sections for an introduction about Megaport, a free-text Tax Registration Number field, and a free-text Company Address field.
* **Advanced Pricing View** -- A new Analyze and Export button takes users to an Advanced View page where pricing can be displayed across multiple terms, currencies, and partner/retail discount levels at once. Term selection can also be changed in bulk for all services.
* **Renewals** -- A new Import button allows users to include a customer's existing services in a quote. Users can select which imported services to include/exclude, increase term or speed on imported services, and add new connections alongside imported connections. This streamlines bulk renewal and re-terming workflows.
* **New Partner Admin Menu** -- A new sidebar drop-down menu group has been added that contains **Managed Accounts**, **Custom Branding**, and **Manage Orders**, which displays a pending count badge. The Partner Admin Documentation link has also moved into the Help & Support menu.
* **Partner Ordering Approval** -- The IPsec add-on has been added to the Partner Ordering Approval workflow.
* **Webhook Partner Context and Event Routing** -- Partner accounts can now control webhook event routing to separate their own account activity from events occurring across their managed accounts. When creating a new webhook, partners can select between *Your account* (default) or *Managed accounts* as the event origin. This is set at creation and clearly displayed in the webhooks list via a new Event origin column. This allows partners to receive events from all managed accounts with partner account context included in the payload, while maintaining a distinct stream for their own service notifications.
* **Terraform v1.13.0** -- Version 1.13.0 of the Terraform provider has been released. This release includes managed account support; partners can now provision on behalf of a managed account using their own credentials. This release also includes improvements to Cisco C8000v documentation. For more information, see [https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.13.0](https://github.com/megaport/terraform-provider-megaport/releases/tag/v1.13.0).
* **Partner Portal Menu Redesign** – The Partner Portal navigation menu has been updated with a new Billing menu. Invoices, Billing Markets, and Term Management have been moved into this menu, making billing-related features easier to find.
* **Services Page Refresh** – The Services page in the Partner Portal has been updated with a new look and feel.
* **Full-width layout** – The services list now spans the full page width, allowing you to view your services at a glance.
* **Updated product icons** – Service rows now display gradient-styled product icons consistent with the updated Megaport brand.
* **Improved row density** – Tighter spacing and refined whitespace make it easier to scan your list of services.
* **Expand/Collapse all** – This control has been promoted to a visible button in the page header, making it quicker to expand or collapse all service groups.
* **Row styling improvements** – Updated hover states, rounded corners, and refreshed status and service identifier chips for a cleaner look.
* **In-app guided tour** – A guided tour orients customers to the new layout on the first visit.
* **Bulk Service Term Management** -- A new Term Management page is available under the new Billing menu in the Portal's sidebar navigation. The Term Management page lets you start and update a new contract term for multiple services at once. A guided wizard walks you through selecting eligible services, choosing the new term and auto-renew setting, reviewing the pricing summary and terms and conditions, and submitting the changes, with a per-service result for each selected service.
* Managed Account Support -- Services requiring partner approval automatically generate approval records and return a PENDING\_APPROVAL status.
* Activity Logging -- All successful and failed term changes are recorded in the activity log for auditability.
* **Allow Managed Accounts to Order Cross Connects** -- Megaport-supported managed account users can now order Cross Connects directly in the Partner Portal. Partners control access via a new setting in Partner Admin, and all requests flow through Partner Order Approval for review before provisioning.
A new Upload LOA prompt replaces the Support Requests Portal redirect, allowing users to upload, view, and download Letters of Authorization (PDF, ≤ 5 MB) directly in the Portal.
New API endpoints support LOA upload, download, and listing under `/v3/product/{productUid}/cross_connect/loa` and `/v2/product/{productUid}/cross_connect/loa/{loaDocumentId}`.
Not available for Partner-supported accounts.
* **Quoting Tool Enhancements** -- These improvements have been made to the Quoting Tool:
* You can now add DDoS Protection as an optional add-on when quoting a Megaport Internet connection in the Quoting Tool, at locations where DDoS Protection is available. When added, DDoS Protection appears as a separate line item with its own monthly rate in the quote and is included in the PDF quote export.
* The Download CSV and PDF buttons have moved into a new Advanced View screen. The previous Pricing Comparison button is now named Analyze & Export and opens this screen, where you can download CSV and PDF quotes.
* Megaport Storage is now available as a connection type. When you add a connection to a quote, you can select Megaport Storage as the destination and configure a connection name, rate limit, and contract term.
* Latitude.sh is also now available as a connection type.
* The Quoting Tool now uses the same side menu as the Portal, and the user profile menu includes a theme option.
* You can now import existing services into quotes. These services can be excluded from the quote if needed.
* The Pricing Comparison screen now includes add-on charges (such as IPsec, Cross Connect, and DDoS Protection) as separate line items beneath their parent service. Summary totals have been updated to include add-on monthly rates, ensuring the Pricing Comparison total matches the Quote Summary.
* **New Portal Menu Design** -- We’ve streamlined the Portal to improve navigation and accessibility! The primary navigation menu has moved from the top header to a new left-hand sidebar. You can now find these core categories quickly on the left side of your screen:
* **Dashboard** -- Your centralized overview of network health and activity.
* **Services** -- Manage your Ports, MCRs, MVEs, NAT Gateways, IXs, and VXCs.
* **Marketplace** -- Discover and connect with our global ecosystem of providers.
* **Tools** -- Access telemetry, looking glass, speed tests, and diagnostic utilities.
* **Service Status** -- Real-time updates on network performance, maintenance, and outages.
* **Mandatory Multi-Factor Authentication (MFA)** -- Effective from May 11 2026, MFA is now mandatory for all customers accessing the Portal. This security enhancement requires all users to set up MFA on their accounts, providing an additional layer of protection against unauthorized access. Users will be prompted to configure MFA during their next login if they have not already done so.
* SSO users are exempt from MFA - authentication is handled by their IdP.
* API keys are not affected. However, any automation or scripts using username/password authentication will break. Customers must switch to using API keys instead.
* **Security: Account Lockout After Failed Login Attempts** -- User accounts are now automatically locked after 10 consecutive failed login attempts, protecting against unauthorized access. Once locked, users will see a clear message directing them to contact their company administrator. Company admins can reactivate locked users from the Admin > Manage Users section, which also resets the failed attempts counter so the user can log in normally again.
* **Portal Terms Updated** -- The terms and conditions displayed in the Portal cart when ordering add-on services (IPsec, Cross Connect, IP Address) have been simplified and standardized to match how standalone products work.\
Customers now see one of these standard terms paragraphs based on their account type:
* Partners with GRA signed -- Terms referencing the Global Reseller Agreement
* Direct customers / Partners without GRA signed -- Terms referencing the Global Services Agreement and Service Schedules
* Managed Accounts -- A short message directing them to contact their Megaport partner
* **Quoting Tool Enhancements** -- These improvements have been made to the Quoting Tool:
* **Quoting Tool Import Existing Services** -- A new **Import Existing Services** button is available in the Quoting Tool. You can import your existing services into a quote, search by name or service UID, and optionally exclude imported services from the quote total. This allows you to quote term renewals, and include existing services in your network design without affecting pricing calculations. All imported services are fully editable with pricing.
* **Multi-Currency Pricing** -- The Pricing Comparison view now supports displaying pricing in multiple currencies within a single quote. Select additional currencies in the comparison dialog to see pricing for each service in those currencies alongside the native currency.
* **Multi-Discount Option Display** -- The Multi-Discount Option Display has been added to show Partner Discounted Pricing alongside Standard Pricing in the Network Design Summary.
* **Bulk Update Terms** -- You can now bulk update terms across all services in a quote. When editing the term for any service in the quote, a new option allows you to apply that term change to all services in the quote. This makes it much faster to see how different term lengths affect pricing across your entire design without having to edit each service individually.
* **Download all Term Prices in CSV** -- You can now download the pricing for all term options for each service in a quote as a CSV file. This allows you to analyze and compare pricing across different term lengths in a spreadsheet format, making it easier to identify the best options for your network design. The CSV includes columns for service name, location, term length, standard price, and partner discounted price (if applicable).
* **Issue fixed:**
* When a partner user attempted to save an existing quote for a managed account, the save operation failed with a validation error.
* Emergency planned maintenance notifications were not visible on the Service Status page when viewing from a Partner Managed account context.
* **Quoting Tool Updates** -- These improvements have been made to the Quoting Tool Pricing Comparison:
* Partner Pricing in Partner Comparison screen (Partners only) -- Partner users now have a **Display Partner Pricing** check box in the sticky footer of the Pricing Comparison screen. When selected, every service shows an additional line item with the partner discount applied — making it much faster to show partners the different pricing scenarios.
* Edit Terms in Comparison Screen -- You can now edit the term lengths for each service directly in the Pricing Comparison screen. This allows you to see how different term lengths affect pricing without having to exit the comparison view and reconfigure the quote. Simply click on the term length for any service to select a new term, and the pricing will update in real time to reflect the change.
* **NAT Gateway in the Quoting Tool** -- You can now add NAT Gateway services when creating quotes in the Quoting Tool. When designing a network quote, click **Add NAT Gateway** to configure a NAT Gateway with options for location, name, session count (250K to 10M sessions), rate limit, and contract term. You can optionally exclude the NAT Gateway from the quote total if you want to include it in the design without affecting pricing.
* **Megaport-Supported Managed Accounts Can Now Order Cross Connects** -- Partners now have a self-serve toggle in the Portal to enable Cross Connect ordering for individual managed accounts. Once enabled, eligible managed account users can request Cross Connects directly when ordering a Port or on pre-live Port services. This is planned to be extended to all managed accounts in a future release.
* **Managed Accounts – Improved Action Buttons** -- We've updated the action buttons on the Managed Accounts page for a clearer, more intuitive experience:
* **Edit button** -- The arrow icon (→) has been replaced with a clearly labelled **Edit** button, making it easier to identify how to edit an account.
* **Switch Account button** -- The button styling has been updated so it now appears visually clickable, removing any confusion about whether it was active or inactive.
* **Custom Partner Branding** -- Megaport Partner Branding is now available in the Portal, enabling partners to customize the Portal experience for both partner accounts and their managed accounts. When enabled, the Portal header shows the partner’s branding alongside the Megaport logo.
A new branding profile endpoint has also been created for managing company branding profiles:
* GET /v3/companies//branding\_profile – Retrieve a company’s branding profile
* POST /v3/companies//branding\_profile – Create a branding profile, including uploading the primary logo to AWS S3
* PUT /v3/companies//branding\_profile – Update an existing branding profile, retaining the current logo when no new image is supplied
For more information, see [Adding Custom Branding](/partners/account/custom-branding) and [Customizing your Branding with the API](/partners/api/branding-profile).
* **Quoting Tool Enhancements** -- These improvements have been made:
* Improved the usability of the CSV export file. Service name, Location, and other details are now in separate columns for easier analysis.
* For partner companies only, a new column called **Partner Rates** has been added to the CSV export file. This column shows the discounted price for that partner for the service for the associated term.
* **New Help and Support Menu** -- A new Help menu is available in the Portal header. Click the Help icon (?) to access Documentation, API Documentation, Release Notes, Support Requests, and Send Feedback from a single location. Support Requests and Send Feedback have moved from the User menu to the new Help menu. By bringing these tools together, we've made it faster for you to find answers, manage tickets, and share feedback without switching menus.
* **Increase Service Status History from 7 to 90 Days** -- The service status information history in the Portal has been extended from 7 days to 90 days. This means you can now view the status of your services for a longer period, which can be helpful for troubleshooting and historical analysis. The filters for Maintenance and Outage statuses have also been updated to reflect the extended 90-day window, with label changes to indicate Maintenance (Completed/Cancelled) and Outage (Resolved).
* **Partner Ordering Approvals - IX Speed Changes** -- Partners who have enabled approval requirements for managed account services will now receive approval requests when a managed account changes the speed of a termed IX connection.
* **Activity Logs Enhancement** -- The Activity Logs page now displays User Type and User in separate columns with independent filters, making it easier to filter activity by specific criteria.
* **Quoting Tool Enhancements** -- These improvements have been made:
* Added diversity zone selection so users can specify Red/Blue site preferences when creating quotes for Ports, MCRs, MVEs, and Cloud VXCs.
* Added IX terms so users can generate quotes for an IX connection on terms. The term defaults to 12 months.
* Customers can now quote Ports and VXCs in India.
* Add-on charges (for example, Cross Connects, IPsec) are now on a separate row and diversity zone is now in a separate column when downloading the quote in comma-separated values (CSV) format.
* Added enhanced PDF export options. When downloading a quote as a PDF, users can now optionally include an About Megaport section, a Tax Registration number, and a company address. The downloaded PDF includes the selected options and any text entered in these new fields.
* A new Pricing Comparison view is available in the Quote Summary section, displaying quoted services with all the term options and their respective prices. This allows users to compare term pricing across the entire quote in a single view.
* **Order Approval for Managed Accounts** -- Partners can now require managed accounts to submit service requests for approval. This feature gives partners full control over service fulfillment and billing for their managed users. New services, re-terming, and speed changes now require partner approval before managed account users can proceed if approval is on (approval is off by default, and requests expire if not actioned within 7 days).
Key capabilities include:
* **Partner Review Queue** – A new **Manage Order** dashboard allows partners to approve or reject new service orders, speed changes, and re-terming requests from a centralized queue.
* **Service Integrity** – Services are automatically locked while an approval request is pending to prevent conflicting modifications.
* **Automated Notifications** – Four new notification types are available to keep both partners and managed users informed of order status changes. These notifications are enabled by default for all users.
* **Partner Admin Self-Service** – An updated **Partner Admin** page provides a table view to manage feature toggles across all managed accounts in real time. Partners can configure approval requirements per managed account.
* **Service Termination Approval for Managed Accounts** -- Support has been added for requiring approval of early service terminations. Partners who have enabled approval requirements for managed account services will now receive approval requests when a managed account user attempts to terminate a service that incurs an early termination fee (ETF).
* **Additional IP Address Requests for Managed Accounts** -- Additional public IP address requests are now supported in the Portal for managed accounts.\
For more information, see [Megaport Internet Routing Guide](/megaport-internet/routing).
* **Added IP Address as a Quotable Service in the Quoting Tool** -- IP Address has been added as a standalone product in the Quoting Tool with configurable location, purpose, currency and subnet size, allowing users to add and configure IP addresses as part of a quote.
* **Quoting Tool IPsec Add-on Enhancement** -- You can now add IPsec as an add-on to a quote when pricing an MCR in the Quoting Tool.
* **Introducing the Support Requests Portal** -- We have added more ways for you to get support. The Support Requests Portal is a dedicated hub for managing all your support cases in one centralized location. The portal offers:
* **Streamlined case creation** -- Five targeted request types ensure faster routing to the right team.
* **Complete case tracking** -- Monitor cases from creation through resolution with clear, easy-to-understand status indicators.
* **Team collaboration** -- Add collaborators and attach files to provide complete context for your cases.
You can access the portal through Megaport Portal > User Menu > Support Requests.
The Support Requests Portal is available to direct accounts, partners, and some managed accounts under certain conditions. Managed accounts without chat enabled will not be able to access support requests. Partners can create requests on behalf of any of their managed accounts.
* **Partner Ordering Approval** -- This first iteration of the partner ordering approval feature has been released. This feature allows partners to require approval for new services for some or all of their managed accounts. If you are a Megaport Partner and want to use this feature, contact your Partner Manager.
* **Activity Log Updates** – These improvements have been made to the activity logs:
* The Activity Name filter in the Company Activity page now shows only the activities that have been performed, improving relevance and usability.
* Activity log retention has been increased from 60 days to 6 months, allowing for longer-term auditing.
* Improved consistency and readability of logs.
* **Activity Logs Added** -- These Portal activities have been added to the Activity Log:
* Enabling, resetting, and disabling Multi-Factor Authentication (MFA)
* Updating user notification settings
* Updating user profiles
* Locking and unlocking services
* Creating and updating resource tags
* Updating service terms
* Creating and updating a managed account
* Creating a Megaport Marketplace profile
* Creating and updating Prefix Filter and Packet Filter lists
* **Quoting Tool Improvements** -- These improvements have been made to the Quoting Tool:
* Added Roll Up Discounts and Include Partner Discounts options to the quote summary. This allows for a cleaner quote display and for partners to generate quotes to share with their managed accounts, where discounts are not shown.
* Quotes can now be created for Megaport Internet connections up to 25 Gbps in supported metros.
* **Issue fixed** -- When a Company Admin from a partner company attempted to download the Inventory report for a managed account, the download failed.
* **Partner Consolidation** -- The PV and P1 (Reseller) programs have now been fully consolidated. All partners have been successfully migrated to the standardized Megaport Partner Program (MPP). There is no longer a separate PV or P1; MPP is now the sole partner program moving forward.
* **Partner Service Inventory Report** -- The Service Inventory Report feature has now been made available at the partner level. This provides a single report that captures all of the managed accounts under a partner account hierarchy. The report includes only services whose provision status is LIVE, CONFIGURED, or DECOMMISSIONED.
* **Add Managed Account Information to Emails** -- Improvements have been made to notification emails that partner accounts receive about managed accounts. This makes it clearer which managed accounts and managed account services notification emails refer to.
* **Update Partner Docs Link in Auto Renew Settings** -- In the Partner Admin > Manage Global Settings screen, the Megaport Documentation link has been changed to the [Managing Minimum Term Renewal](/partners/account/auto-renew) page in the Megaport Partner Portal Documentation. This provides information on minimum term renewal in the partner context.
* **Partner and Wholesale Discounts in the Quoting Tool** -- The Quoting Tool has been updated to show the discount breakdown in the quote summary for any discounts that apply (Partner and Wholesale discounts).
* **AUD Added to NZ Billing Market** -- AUD has been added to the New Zealand billing market and NZD has been added to the Australian billing market as available currencies.
This is currently available only to customers setting up their billing market for the first time. If you already have billing markets enabled and want to use these currencies, please contact your Account Manager or Customer Success Manager (CSM) to discuss options.
* **Sort Activity Logs by Date/Time** -- The recently released User Activity and Company Activity pages in the Portal now allow you to sort activity logs by date/time.
* **New Company Activity Logs Page** -- A new Company Activity option has been added to the Megaport Portal settings menu. The Company Activity page allows Company Admins to view the activities of all users in their company. As part of this change, a new option called User Activity was also added to the settings which allows the current user to view a log of their own activities.
* **Maintenance or Outage Updates** -- We have added some CSP notifications to provide better visibility to customers. Emails will not be sent, however, the notifications will be visible in the Service Status page. Please check the notifications from your CSP for more information, as Megaport is not responsible for CSP outages.
* **Minimum Term Renewal for Individual Managed Accounts** -- Partner account Company Admins can manage the default state for the contract term renewal of individual managed accounts in the Partner Admin menu > Edit \[Managed Account] > Minimum Term Renewal tab.
* **Portal Responsive Improvements** -- The navigation bar in the Portal has been updated to show Dashboard, Partner Admin, What’s New, and only change to mobile view when there is no display room available.
* **Dashboard for Managed Accounts** -- Managed accounts can now view the Dashboard in the Megaport Portal.
* **Minimum Term Renewal** -- You can now automatically renew the minimum contract term put on a service. Previously, services would roll over to no contract term at the list price at the end of the contract term, unless a manual action was taken to re-term the service.
Now services can be set to **Automatically Renew** at the same duration and discounted price at the end of the contract term, with no manual re-terming action needed. When ordering services on contract with a minimum term of 12, 24 or 36 months, the option to auto renew the term will be enabled by default.
Company Admins can manage the default state for the contract term renewal in the User Menu > Settings > Minimum Term Renewal page. Partner account Company Admins can manage the default state for all their managed accounts through the Partner Admin > Manage Global Settings > Minimum Term Renewal page.
The Minimum Term Renewal page options are:
* When creating new services on term, the option to Auto Renew the Term will be enabled by default.
* When creating new services on term, the option to Auto Renew the Term will be disabled by default.
Existing services are not impacted by the management of the default state of the Minimum Term Renewal options for the contract term renewal.
At the end of the contract term:
* Notifications are sent at least 30 days before term contracts end including services with the Auto Renew Term option enabled.
* If Auto Renew Term has been set to **on** for your services, no further action is required. The service will be automatically renewed for another term of the same length at the same price. The Auto Renew Term setting remains on and the contract term will continue to auto-renew.
* If you would prefer not to lock services onto a minimum term, before the contract expiry date simply go to the Megaport Portal and turn the Auto Renew Term option off - the monthly recurring charge will retain the same market month-to-month rate for Ports or the pay-as-you-go rate for virtual services as when it was ordered.
For more information, see [Managing Minimum Term Renewal](/partners/account/auto-renew).
* **Portal Settings Reorganized** -- Various user-level and company-level Megaport Portal settings have been consolidated into one settings page, accessible from the user menu. The changes include:
* Creating a consolidated Settings page, accessible from the user menu, with Admin and User sections.
* Moving User Profile and Notification Settings in the user menu into the User section of the new Settings page.
* Moving all Company menu items (Company Profile, Megaport Marketplace Profile, Billing Markets, Manage Users, Account Contacts) into the Admin section of the new Settings page.
* **Vantage Transact becomes Partner** -- VantageTransact has been re-branded to Partner. The portal is now called the Partner Portal.
* **Quoting Tool - Ability to Exclude Services from Quote** -- Customers can now exclude the costs associated with specific top-level services from a quote. When editing a service in a quote, the **Exclude \[service type] from quote** check box can be used to exclude the costs associated with that service from the quote total cost.
* **Remove Distributors** -- The Distributor account type has been removed from all Megaport systems and applications.
* **Service Status Page Calendar** -- Improvements have been made to the Service Status page to assist you in monitoring maintenance and outage events that affect your services. Filtering criteria has been updated, and a calendar has been added that allows you to monitor maintenance events in either a calendar or list view. The calendar view allows you to quickly see start and end times of maintenance events, making it easier to track upcoming activities.\
For more information, see [Monitoring Maintenance and Outage Events](/partners/services/monitoring-events).
* **Term Pricing Display Improvement in Quoting Tool** -- The way that service term pricing is displayed in the Quoting Tool has been improved. You can now see the pricing options at a glance, instead of having to select each term option from a drop-down list.
* **Service Status Timezone Parameter** -- In the Maintenance & Outages page, you can now view maintenance and outage events impacting services in the time zone of your choice. If you select a timezone on the Maintenance tab, it will apply only to the maintenance events. Similarly, if you select a timezone on the Outages tab, it will apply only to the outage events. For more information, see [Monitoring Maintenance and Outage Events](/partners/services/monitoring-events).
* **Deal Estimator Rebranded to Quoting Tool** -- The Deal Estimator has been rebranded and renamed to the Quoting Tool. The Quoting Tool also has a new URL at [https://pricing.megaport.com](https://pricing.megaport.com/).\
For more information, see [Quoting Service Cost](/partners/services/creating-estimates).
* **Megaport VantageTransact Docs RSS Feed** -- An RSS Feed has been added to the Megaport VantageTransact Docs which allows you to be notified when an update or change has been made to the documentation. The RSS Feed icon is available at the bottom right of each page. Simply subscribe to the feed using an RSS reader, for example, Slack or Feedly, to keep up to date with information about all of our latest features!
* **Deal Estimator Enhancement for Partners** -- Partner users can now choose whether they are generating an estimate for:
* Themselves as the partner account.
* One of their existing managed accounts, by selecting the managed account from a list.
* A new managed account.
A **Cancel** button has also been added to the New Estimate screen so that it will not close on mouse click.
* **Support for Monitoring Maintenance and Outage Events** -- The Maintenance & Outages page allows you to monitor events that affect your services, including current, scheduled, and past events.
By staying informed about maintenance activities and service outages, you can plan effectively around scheduled maintenance and provide faster responses during unplanned outages.
Access to the Maintenance & Outages page is available to both partners and managed accounts.
For more information, see [Monitoring Maintenance and Outage Events](/partners/services/monitoring-events).
* **Megaport Marketplace Ports added to Deal Estimator** -- Now when logged in to the Deal Estimator, you can add Megaport Marketplace ports from a Port, MCR, or MVE in your deals. When adding a Megaport Marketplace port, specify the provider, location, connection name, term, and rate limit.
* **Megaport Internet Long Haul is now available in the Deal Estimator** -- Now when logged in to the Deal Estimator, you can add out of metro Megaport Internet connections from a Port, MCR, or MVE in your deals.
* Location allows you to choose from a list of available Megaport Internet locations in the same country as the A-End.
* Location for MVE allows you to choose a Megaport Internet location in the same country as the A-End.
* Megaport Internet connections from Ports and MCRs are allowed only in AU, UK, and US.
* Megaport Internet connections from MVEs are allowed in any country where MVEs can be ordered.
For more information, see [Quoting Service Cost](/partners/services/creating-estimates).
* **Issue fixed** -- A partner wasn’t able to approve service key VXC speed change requests when acting in the managed account context.
* **Partner Vantage** -- Standardised term discounts for Partner Vantage accounts to match direct accounts on newly ordered services.
* **Megaport Support for Managed Account Users** -- We now offer direct technical support for managed account users. In this optional support model, customers managed by a partner contact the Megaport Support team directly with any support requests. Enrolling in the Megaport direct support model provides a way for partners to offer a self-service experience to their customers.
* [Configuring Email Notifications](/partners/account/notifications)
* [Providing Support Contact Details](/partners/tech-support-details-partner)
* [What Users Can View and Access](/partners/access)
* [Creating a Managed Account](/partners/account/create-managed)
* [Contacting Support](/partners/support/contact)
* **Service Terms** -- Partners can now select a 12, 24, or 36-month term to a new service (Port, MCR, or MVE). Partners updating an existing month-to-month service can select a 12, 24, or 36-month term.
* [Port Terms](/finance/port-pricing)
* [MCR Terms](/finance/mcr-pricing)
* [MVE Terms](/finance/mve-pricing)
* [Troubleshooting topics and videos](/partners/troubleshooting) -- A new landing page highlights the troubleshooting topics on the Megaport Documentation site. The topics include steps and quick tip videos to help you investigate errors and unexpected behaviors with Megaport services.
* [Quoting Service Cost](/partners/services/creating-estimates) -- Partners can estimate managed service cost before actually ordering the service.
# Contacting Support
Source: https://docs.megaport.com/support/contact
This help topic describes how to contact the Megaport Support team.
Need help with something? A great first step is to check out the Megaport Documentation on this site and save yourself the time collating relevant information and lodging a support request. We regularly update our content to address common call drivers.
If you need to raise an issue with our Support teams, you can create and manage your own support cases using the Support Requests Portal. For more information, see [Support Requests Portal](/support/support-portal).
Alternatively, get in touch with our dedicated Support teams using live chat or by calling us. The Support teams are ready to guide you through everything from creating a Megaport account, provisioning network connections, responding to incidents, to answering general inquiries.
If your account is managed by a Megaport partner, contact your partner for your support options. Most partners provide their own first-level support.
## Support Requests Portal
Your primary support channel is the Support Requests Portal. Use the Support Requests Portal to create, manage, and follow up on support cases. Our Support team will monitor and process your support cases.
For more information, see [Support Requests Portal](/support/support-portal).
## Live chat 24/7/365
Reach out to our in-house Support team any time of day or night.
1. Log in to the Megaport Portal.
2. Click the blue live chat icon to open a chat window and start a conversation.
## Phone
Reach out to our Support team through the number best for your region:
* USA +1 425 954 2777
* Australia +61 7 3062 7601
* New Zealand +64 508 050 877
* United Kingdom +44 1 202 286 622
* France +33 187 214 799
* Germany +49 32 211 121 713
* Hong Kong +852 800 906 081
* Japan +81 120 645 081
* Singapore +65 6335 3863
## What you need before submitting a support request
Providing the correct information to Megaport is critical for efficient and effective assistance. When engaging our team, include the following information:
* Service ID(s)
* Company / organization
* Description of request
When reporting an incident, also include the following information:
* Problem symptom
* Start time of issue
* End time of issue (if resolved/mitigated)
* What changes or actions were performed before the issue started?
* What troubleshooting steps have already been taken?
# EU Digital Services Act
Source: https://docs.megaport.com/support/eu-digital-services-act
This help topic provides details for compliance with the EU Digital Services Act.
This page includes information relevant to the **EU Digital Services Act (Regulation (EU) 2022/2065** of the European Parliament and of the Council of 19 October 2022 on a Single Market For Digital Services and amending Directive 2000/31/EC) ('the DSA').
## Designated Point of Contact
Pursuant to Articles 11 and 12 of the DSA, Megaport has designated [DigitalServicesAct@megaport.com](mailto:DigitalServicesAct@megaport.com) as the single point of contact for communications with Member State authorities, the European Commission, the European Board for Digital Services, and recipients of the service.
When sending messages to [DigitalServicesAct@megaport.com](mailto:DigitalServicesAct@megaport.com) please be sure to include your full name, reply email address, and the name of the EU-based authority if you are contacting us on their behalf. It is preferable that these communications are in English or German.
## Transparency Reports
Megaport will publish an annual transparency report on the Megaport Documentation Portal addressing the required content as detailed in Article 15 DSA.
### Megaport Annual Transparency Report 2025
**This report relates to the period from 1 January 2025 - 31 December 2025.**
Megaport publishes this annual transparency report in accordance with the EU Digital Services Act, covering the period 1 January 2025 to 31 December 2025.
The report has been prepared using the European Commission's prescribed template and is published in machine-readable format as required.
| Section | Title | Applicability | Link |
| - | - | - | - |
| Section 1 | Reporting Details | Applicable: Mandatory identification information for all providers. | [megaport-dsa-2025-01-reporting-details.csv](https://media.megaport.com/docs/csv/eu-reports/megaport-dsa-2025-01-reporting-details.csv) |
| Section 2 | Illegal Content Category Names | Not conducted: Megaport operates solely as a network connectivity provider. | [megaport-dsa-2025-02-illegal-content-categories.csv](https://media.megaport.com/docs/csv/eu-reports/megaport-dsa-2025-02-illegal-content-categories.csv) |
| Section 3 | Member State Orders | Applicable: No Member State orders received in the reporting period. | [megaport-dsa-2025-03-member-state-orders.csv](https://media.megaport.com/docs/csv/eu-reports/megaport-dsa-2025-03-member-state-orders.csv) |
| Section 4 | Notices | Not applicable: Megaport is an intermediary service. | [megaport-dsa-2025-04-notices.csv](https://media.megaport.com/docs/csv/eu-reports/megaport-dsa-2025-04-notices.csv) |
| Section 5 | Content Moderation: Own Initiative - Illegal Content | Not conducted: Megaport operates solely as a network connectivity provider. | [megaport-dsa-2025-05-moderation-illegal-content.csv](https://media.megaport.com/docs/csv/eu-reports/megaport-dsa-2025-05-moderation-illegal-content.csv) |
| Section 6 | Content Moderation: Own Initiative - Incompatibility with Terms and Conditions | Not conducted: Megaport operates solely as a network connectivity provider. | [megaport-dsa-2025-06-moderation-terms-incompatibility.csv](https://media.megaport.com/docs/csv/eu-reports/megaport-dsa-2025-06-moderation-terms-incompatibility.csv) |
| Section 7 | Appeals and Recidivism | Not applicable: Megaport does not moderate user content and therefore receives no complaints relating to moderation decisions. | [megaport-dsa-2025-07-appeals-and-recidivism.csv](https://media.megaport.com/docs/csv/eu-reports/megaport-dsa-2025-07-appeals-and-recidivism.csv) |
| Section 8 | Automated Means | Not conducted: Megaport operates solely as a network connectivity provider. | [megaport-dsa-2025-08-automated-means.csv](https://media.megaport.com/docs/csv/eu-reports/megaport-dsa-2025-08-automated-means.csv) |
| Section 9 | Human Resources | Not applicable: Megaport is an intermediary service. | [megaport-dsa-2025-09-human-resources.csv](https://media.megaport.com/docs/csv/eu-reports/megaport-dsa-2025-09-human-resources.csv) |
| Section 10 | Average Monthly Active Recipients | Not applicable: Megaport is an intermediary service. | [megaport-dsa-2025-10-amar-monthly-active-recipients.csv](https://media.megaport.com/docs/csv/eu-reports/megaport-dsa-2025-10-amar-monthly-active-recipients.csv) |
| Section 11 | Qualitative Data | Applicable | [megaport-dsa-2025-11-qualitative-data.csv](https://media.megaport.com/docs/csv/eu-reports/megaport-dsa-2025-11-qualitative-data.csv) |
### Megaport Annual Transparency Report 2024
**This report relates to the period from 1 January 2024 - 31 December 2024**
#### Government Orders from Member States
Article 15(1)(a) DSA
**The number of orders received from Member States' authorities to act against illegal content provided by recipients of the service**
During the relevant period, Megaport received zero orders from EU Member States' authorities to act against illegal content provided by recipients of the service.
**The number of orders received from Member States' authorities to provide specific information about one or more individual recipients of the service in the context of illegal content-related incidents**
During the relevant period, Megaport received zero orders from EU Member States' authorities requesting specific information about individual recipients of the service.
**The time needed to inform the authority issuing the order, or any other authority specified in the order, of its receipt, and to give effect to the order.**
As noted above, Megaport received zero orders from EU Member States' authorities requesting specific information about recipients of the service during the relevant period.
#### Megaport's Own-Initiative Content Moderation
Article 15(1)(c) DSA
**Meaningful and comprehensible information about the content moderation engaged in at the providers' own initiative, including the use of automated tools, the measures taken to provide training and assistance to persons in charge of content moderation.**
Megaport does not generate, store, broadcast or make publicly available any content as part of our product offering. As such, we do not have content to moderate nor do we have staff carrying out content moderation.
**The number and type of measures taken that affect the availability, visibility and accessibility of information provided by the recipients of the service**
Megaport does not generate, host, store, broadcast or make publicly available any content as part of our product offering. As such, we do not have content to moderate nor do we take measures that affect the availability, visibility and accessibility of information provided by the recipients of the service.
**The number and type of measures taken that affect the recipients' ability to provide information through the service, and other related restrictions of the service**
Megaport does not host content nor do we provide capabilities for users to share content or interact with other users on our platform. As such, during the relevant period, Megaport did not take measures that affected a recipient's ability to provide information through the service.
#### Appeals
Article 15(1)(d) DSA
**Number of complaints received through the internal complaint-handling systems in accordance with the provider's terms and conditions and additionally, for providers of online platforms, in accordance with Article 20, the basis for those complaints, decisions taken in respect of those complaints, the median time needed for taking those decisions and the number of instances where those decisions were reversed.**
During the relevant period, Megaport received zero appeals of the types of decisions described above.
#### Automated Content Detection
Article 15(1)(e) DSA
**Any use made of automated means for the purpose of content moderation.**
Megaport does not generate, store, broadcast or make publicly available any content as part of our product offering. As such, we do not have content to moderate nor do we have staff carrying out content moderation of any kind.
### Megaport Annual Transparency Report 2023
**This report relates to the period from 1 January 2023 - 31 December 2023**
#### Government Orders from Member States
Article 15(1)(a) DSA
**The number of orders received from Member States' authorities to act against illegal content provided by recipients of the service**
During the relevant period, Megaport received zero orders from EU Member States' authorities to act against illegal content provided by recipients of the service.
**The number of orders received from Member States' authorities to provide specific information about one or more individual recipients of the service in the context of illegal content-related incidents**
During the relevant period, Megaport received zero orders from EU Member States' authorities requesting specific information about individual recipients of the service.
**The time needed to inform the authority issuing the order, or any other authority specified in the order, of its receipt, and to give effect to the order.**
As noted above, Megaport received zero orders from EU Member States' authorities requesting specific information about recipients of the service during the relevant period.
#### Megaport's Own-Initiative Content Moderation
Article 15(1)(c) DSA
**Meaningful and comprehensible information about the content moderation engaged in at the providers' own initiative, including the use of automated tools, the measures taken to provide training and assistance to persons in charge of content moderation.**
Megaport does not generate, store, broadcast or make publicly available any content as part of our product offering. As such, we do not have content to moderate nor do we have staff carrying out content moderation.
**The number and type of measures taken that affect the availability, visibility and accessibility of information provided by the recipients of the service**
Megaport does not generate, host, store, broadcast or make publicly available any content as part of our product offering. As such, we do not have content to moderate nor do we take measures that affect the availability, visibility and accessibility of information provided by the recipients of the service.
**The number and type of measures taken that affect the recipients' ability to provide information through the service, and other related restrictions of the service**
Megaport does not host content nor do we provide capabilities for users to share content or interact with other users on our platform. As such, during the relevant period, Megaport did not take measures that affected a recipient's ability to provide information through the service.
#### Appeals
Article 15(1)(d) DSA
**Number of complaints received through the internal complaint-handling systems in accordance with the provider's terms and conditions and additionally, for providers of online platforms, in accordance with Article 20, the basis for those complaints, decisions taken in respect of those complaints, the median time needed for taking those decisions and the number of instances where those decisions were reversed.**
During the relevant period, Megaport received zero appeals of the types of decisions described above.
#### Automated Content Detection
Article 15(1)(e) DSA
**Any use made of automated means for the purpose of content moderation.**
Megaport does not generate, store, broadcast or make publicly available any content as part of our product offering. As such, we do not have content to moderate nor do we have staff carrying out content moderation of any kind.
# Sending Feedback
Source: https://docs.megaport.com/support/feedback
This help topic describes how to provide feedback.
At Megaport, we value your feedback. Your insights and suggestions help us continually improve our services and better meet your needs. Every feedback item is carefully reviewed and considered by our team, ensuring that your voice directly influences our decisions and actions.
Whether it's a suggestion for a new feature, a comment on our current services, or a report of an issue, we want to hear from you. We are open to all feedback and are committed to responding to your needs effectively.
Follow these steps to provide feedback or click below to watch a quick demo.
**To send feedback**
1. Log in to the Megaport Portal.
2. Choose (Help & Support) > Send Feedback.
3. Submit your feedback.
* Fill out the **Send Feedback** form with your comments, suggestions, or concerns.
* Click **Submit** to send your feedback directly to the Megaport leadership team.
Your feedback is invaluable to us, and we appreciate you taking the time to share your thoughts.
# Megaport Support Services
Source: https://docs.megaport.com/support/index
This help topic describes the Megaport Support team.
We’re here to help.
Megaport offers a wide variety of support resources designed to enhance the value of your Megaport services. These resources and tools provide several approaches to find solutions and solve problems.
If your account is managed by a Megaport partner, contact your partner for your support options. Most partners provide their own first-level support.
## Megaport Support team
Megaport’s global Support team is available around the clock (24 hours a day, 7 days a week, 365 days a year) to help customers quickly and easily use, manage, and troubleshoot the Megaport products in their network.
Our follow-the-sun support model ensures that high-priority cases can be transferred seamlessly to provide continuous coverage when working to solve critical problems. By using a single unified case tracking system, Megaport Support engineers know they are working with the latest details and status of each case.
The Megaport Support team responsibilities are divided among Technical Support Engineers (TSE), Network Operations Centre (NOC) Engineers, and Operations Engineering (OpsEng).
### Technical Support Engineers
TSE are responsible for all customer-facing activity and communications, such as:
* assisting with incidents
* provisioning new services
* sending maintenance notifications
* answering general inquiries
### Network Operations Centre Engineers
TSE escalate any customer issues that they are unable to resolve within their triage processes to the Network Operations Centre (NOC) team. This team is responsible for monitoring the production network and managing any incidents that affect multiple customers. If required, the NOC engineers will escalate issues to resolutions teams, including third-party backbone providers, data center operators, cloud service providers, or Megaport engineers.
### Operations Engineers
NOC engineers escalate any customer issues that they are unable to resolve within their triage processes to the Operations Engineering team.
The Operations Engineering team is responsible for the maintenance of the production network. Their area of responsibility is broad and ranges from network software and hardware upgrades, to activation of new network components to support expansion. They are also the final escalation point for the Technical Support and Network Operations engineers.
# Network Maintenance
Source: https://docs.megaport.com/support/maintenance
This help topic describes Megaport network maintenance details.
## Why does Megaport perform maintenance?
To ensure uptime and the ongoing stability of the Megaport network, Megaport occasionally performs routine scheduled maintenance. This maintenance might include physical moves, logical changes, or software upgrades.
In rare circumstances where a network fault occurs that affects customer services, emergency restorative maintenance will be performed.
## Customer services affected by works performed by Cloud Service Providers
Megaport will only provide notice for Cloud Service Provider maintenance if the work affects the Megaport redundant services. We recommend that all customers and partners are subscribed to the Cloud Service Providers maintenance notices to receive all information related to your cloud services.
## When will I be notified?
When planned maintenance work is required, Megaport will provide all customers with a minimum of 14 days notice as per our [Global Services Agreement](https://www.megaport.com/legal/global-services-agreement/). If you order a service in a location where planned maintenance work is required, you will be notified within a minimum of 24 hours.
For emergency maintenance works, Megaport will strive to provide customers with as much notice as possible; however, the notice period can be limited depending on the severity of the network interruption.
It is the responsibility of a Megaport customer and partner to notify its end customers of any scheduled network maintenance.
Works performed upstream from Megaport’s Network by Cloud and SD-WAN providers are sent by the provider directly to their end customers in accordance with the signed agreement between both parties. Megaport has no visibility of these works.
## How will I be notified?
Megaport customers who have signed up for Megaport Portal accounts and have their notifications enabled will be notified of all Megaport maintenance works.
To learn how to assign new user roles and configure email notifications, see the following help topics:
* [Adding and Modifying Users](/portal-admin/user-management)
* [Managing User Roles](/portal-admin/user-management/roles)
* [Configuring Email Notifications](/portal-admin/email-notifications)
If you have a partner-managed account, your partner will communicate with you regarding any maintenance events that affect your account.
Maintenance event notifications are sent directly to managed accounts supported by Megaport.
## What does a maintenance notice look like?
Megaport maintenance notices are similar to the example shown here. Details include the reason for the maintenance event, the services that will be affected, and the length, date, and time of the event.
# Escalating Support Cases
Source: https://docs.megaport.com/support/request-escalation
This help topic describes how to escalate a support case for an incident.
To ensure we can assist you as efficiently as possible, please submit a support request so our support team can conduct a preliminary investigation. This initial step helps us provide the right context and support. Escalations without a support request will be redirected to the support team.
To learn more about submitting a support request, see these help topics:
* [Contacting Support](/support/contact)
* [Understanding Support Requests](/support/requests)
## Escalating a case
You might need to escalate an existing case if circumstances change. Here are some guidelines about when to escalate a case:
* There has been an increase in the impact to your business
* The issue is not being resolved quickly enough
* The support effort is not meeting expectations
Start your case at escalation Level 1. For reference, the escalation path is as follows:
| Level | Contact | Service Loss | Service Degradation |
| - | - | - | - |
| 1 | Global Customer Support Manager Email: [csopm@megaport.com](mailto:csopm@megaport.com?subject=Level%201%20Support%20Case%20Escalation) Mobile: +61 475 014 959 | 2 hours | 12 hours |
| 2 | VP of Customer and Network Operations Email: [cnsm@megaport.com](mailto:cnsm@megaport.com?subject=Level%202%20Support%20Case%20Escalation) Mobile: +61 475 000 686 | 6 hours | 24 hours |
| 3 | Chief Operating Officer Email: [coo@megaport.com](mailto:coo@megaport.com?subject=Level%203%20Support%20Case%20Escalation) Mobile: +61 438 384 519 | 12 hours | 48 hours |
The escalation email contacts should be used sequentially only when resolution is delayed or the support effort is not meeting expectations.
# Understanding Support Requests
Source: https://docs.megaport.com/support/requests
This help topic describes how to submit a support request for an incident, provisioning assistance, or general inquiries.
All incoming support requests are assigned to our Customer Support Team for investigation. If necessary, the team escalates the issue internally to ensure a speedy resolution. For more information, see [Escalating Support Cases](/support/request-escalation).
Requests are grouped into one of three categories: incidents, provisioning, or general inquiries.
## Incidents
An *incident* is a support request regarding a previously active service that has ceased functionality, or has degraded to being highly unusable. Incidents do not include new service provisioning issues or general inquiries.
### Severity and response goals
Megaport sets the severity level for each submitted incident. The severity level defines the targeted time frames for the initial response from Megaport and escalation potential. This process assists the appropriate resources within Megaport manage problems quickly and efficiently according to their severity level.
All incidents are prioritized according to their impact on the customer (1 through 3), with 1 being the most critical. The priority of the incident can be upgraded or downgraded depending on troubleshooting progress.
This table outlines Megaport Support targets for initial response time, how often you can expect an update and time to restore a service, prioritized by severity level.
| Severity Level | Initial Response | Update Frequency | Time to Restore |
| - | - | - | - |
| 1 - Service loss. Service is down or severely degraded. These incidents can severely impact the customer’s ability to conduct business. This can mean that the services are down or not functioning and no procedural workaround exists. | 15 minutes | 30 minutes | 6 hours |
| 2 - Service is partially degraded or intermittently failing. These incidents are high-impact problems that disrupt the customer’s business operation but there is capacity to remain productive and maintain necessary business level operations. | 15 minutes | 60 minutes | 24 hours |
| 3 - Incidents without impact to service. These incidents are minor or no impact problems that involve partial loss of noncritical functionality. | 30 minutes | 4 hours | 48 business hours |
The *Time to Restore* estimates only apply to incidents. The target time to restore is counted from the time the customer reports the issue to Megaport Support and an incident ticket is created.
Megaport Support makes continuous efforts to isolate, diagnose, and deliver a workaround or repair during Megaport's normal local business hours. When the severity level has been downgraded, the support team follows the appropriate guidelines.
### Caveats
* Any time that Megaport Support waits for additional information from the customer is not included in the target restore time.
* If Megaport Support provides a new written date and time for an update, this replaces the previously quoted *Update Frequency* estimate.
## Provisioning
Provisioning requests involve activating new services or troubleshooting issues that relate to service activation. These requests are not assigned severity levels; however, they are handled as a high priority and are resolved quickly.
## General inquiries
Inquiries are information requests sent to Megaport that are not related to an incident. Inquiry requests are automatically set to Severity 3, as they do not affect any services.
### Solution Architect or Sales questions
Megaport Solution Architects can help address any questions on architecting your network, configuring your services, or designing solutions.
If you have any questions for our Solution Architects or Sales Team, see the [Sales page](https://www.megaport.com/contact/sales/) on the Megaport website.
### Billing questions
For questions regarding your Megaport invoice, start with any of these topics:
* [Downloading an Invoice](/finance/download-invoice)
* [Understanding Your Megaport Invoice](/finance/invoices)
For billing or invoice issues or questions, contact Megaport Accounts Receivable.
# Support Requests Portal
Source: https://docs.megaport.com/support/support-portal
This help topic describes the Support Requests Portal and how to use it.
The Support Requests Portal allows you to create, update, and monitor support cases in one centralized location. It is the preferred method for managing all support-related interactions.
Access to the Support Requests Portal is through the Megaport Portal.
If you have any problems with access, contact your Company Admin.
**To access the Support Requests Portal**
1. Visit the Megaport Portal and log in.
2. Choose (Help & Support) > Support Requests.
The Support Requests Portal home page opens in a new tab.
## Support Requests Portal home page
The Support Requests Portal home page allows you to create, view, and manage your support cases.
The portal header remains the same in all areas of the Support Requests Portal.
It includes these options:
* **Megaport** icon -- This takes you to the Support Requests Portal home page in the same tab. The **Home** tab performs the same function.
* **Portal** -- This takes you back to the Megaport Portal in the same tab. You will return to the page you were on when you clicked Support Requests Portal.
* **Documentation** -- This opens the Megaport documentation in a new tab.
* **Logout** button -- This logs you out of the Support Requests Portal, but leaves you logged in to the Megaport Portal. You are redirected back to the last page you were on in the Megaport Portal.
## Case status
The home page displays a list of your support cases. There are two tabs:
* **Open** -- Shows new, open, and resolved cases.
* New cases are raised, but not yet addressed by the Megaport support team.
* Open cases have been investigated by the Megaport support team, and are in progress.
* Resolved cases have gone through the case workflow, and are pending customer review.
Resolved cases are shown for 8 calendar days after they have been set to resolved. You can reopen the case during this time, if required. After 8 days, resolved cases are closed and cannot be reopened.
* **Closed** -- Shows closed cases.\
Only cases closed since 1st December 2025 will be listed on the Closed tab. Cases closed earlier than that date will not be shown on the Support Requests Portal.
The case list shows all cases associated with your company account, not just cases you have created.
## Creating a support case
You can create and manage your own support cases using the Support Requests Portal.
**To create a support case**
1. On the Support Requests Portal home page, click **+ Create Case**.
2. Enter these details:
* **Subject** -- Enter the a brief summary of your case.
* **Description** -- Enter a detailed description explaining the reason for your issue or request, including any troubleshooting steps you have completed.
* **Request Type** -- Select the most relevant request type for your issue or request from the drop-down list.
* **I need to speak to someone about my invoice** - Use this for billing enquiries.
* **I have a general enquiry** -- Use this when you have an enquiry that is not covered by the other request types.
* **I need to report an issue with a previously working service (incident)** -- Use this when you have a problem with your Megaport network.
* **I need assistance with a new set up (Provisioning)** -- Use this for help when you are setting up a service and you cannot find the answer in the Megaport documentation.
* **I would like to speak to a sales person** -- Use this if you want to expand your Megaport network.
For more information about request types, see [Understanding Support Requests](/support/requests).
If you select a request type of **I need to report an issue with a previously working service (Incident)** or **I need assistance with a new set up (Provisioning)**, you will see a **Service ID** field. You must enter the service ID of the service you are reporting a problem with.
**To find and use the service ID**
1. Search for the service you are reporting a problem with on the Services page of the Megaport Portal.
2. Next to the service entry, click the service ID button to copy the service ID.
3. Paste the service ID into the **Service ID** field on the Create Case screen of the Support Requests Portal.
* **Collaborators** (optional) -- Add the email addresses of people you want to be included in interactions and updates on this issue. If the person is known to the Support Requests Portal, their email address will appear when you start typing. If they are not known to the Support Requests Portal, you can enter the email address.
3. Click **Save**.
The new case will appear on the case list on the Support Requests Portal home page.
## Searching your case list
You can search your case list using the **Search** field.
You can search on these fields:
* Case ID
* Created by
* Creation date
## Sorting your case list
You can sort your case list by any field, in either ascending or descending order.
The up or down arrow next to a column heading indicates the current sort order.
* In the Support Requests Portal home page, click the small up/down arrow next to the field name on the case list heading.
The case list reloads.
* Click the arrow again to reverse the sort order.
## Viewing and updating support case details
To view the details of a support case and add more information, click the case **ID** number in the list on the home page.
On the view details page, you will see these tabs:
* **Comments** -- Add more information to the case when it becomes available.\
Click **Submit Comment** to add your comment to the case.
* **Details** -- This tab lists the case details, such as service ID, name, case type, created date, created by, and status. You cannot update these fields.
* **Attachments** -- You can provide additional information by uploading attachments. Valid file types are PDF,
JPG, PNG, and TXT.
1. Click **Upload File** then select your file from the list.\
You will be asked to add a file description.
2. Enter the file description and click **OK**.\
The file description will be added to the comments list.
The **Back** button will take you back to the Support Requests Portal home page.
# Single Sign-On (SSO) Frequently Asked Questions (FAQs)
Source: https://docs.megaport.com/troubleshooting/sso-faq
This help topic describes some common questions about Single Sign-On (SSO) for the Megaport Portal.
This topic describes some of the commonly asked questions and answers relating to setting up Single Sign-On (SSO) for the Megaport Portal.
For more information about the SSO setup process, see [Setting up Single Sign-On](/setting-up/enforcing-sso).
## I have a whitelist/allowlist set up. Do I need to update it?
If your organization restricts inbound network traffic to specific IP addresses, you might need to add Megaport’s IP ranges to your firewall or security group settings.
These IP ranges are available on request. For more information, [contact our Support team](/support/contact).
## I have set up SSO between Azure AD and Megaport. Why am I now receiving a Login Failed error when trying to log in?
Although this can be caused by several reasons, the most common reason is the email mapping attribute with Megaport not being set to Azure's fully qualified email attribute value. Azure expects this, and if using just “emailaddress” then the integration will fail. To confirm if this is the cause, you can look at the browser console when logging in, and if you see an error containing “mapped email is empty” then this will be the cause.
## I have set up an IdP-initiated flow with my IdP to connect to Megaport and it's not working. Why?
Megaport uses internal software to support SSO, which does not support IdP-initiated flows at this stage. Trying to use an IdP-initiated flow will result in a relayState error. Once SSO has been configured for your Megaport account, you need to log in to Megaport directly via the Megaport Portal login page at [https://portal.megaport.com/login](https://portal.megaport.com/login).
## Why do I receive a relayState error when testing my SSO configuration directly through my IdP?
Some IdPs offer the ability to test the SSO connection through their SSO configuration page. This test typically triggers an IdP-initiated flow which is not supported by Megaport. To test whether SSO has been set up correctly with Megaport, we recommend trying to log in directly via [https://portal.megaport.com/login](https://portal.megaport.com/login) once you have completed the configuration with your IdP.
## I've been invited by my Company Admin to our Company account with SSO and have never logged in directly with Megaport credentials. There are issues logging in via SSO. How can I get into my Company's account?
If you have the role of Company Admin, or SSO hasn't been enforced for your company account, then you can log in with a Megaport username and password. As you have never created a Megaport password with your profile, you will need to create one now.
Go to the Megaport login page at [https://portal.megaport.com/login](https://portal.megaport.com/login), then click **Get help signing in**. When on the Login Help page, click **Forgot Password** and follow the prompts. Once you have set a password, you can use it to log in. You can use the **Get help signing in** option again if needed.
## My SSO sign-in failed and I see a support reference. What should I do with it?
Some login errors display a support reference on the Megaport Portal error page. If a support reference is shown, copy it and include it in your support request to help us investigate the issue more quickly. For more information, see [Contacting Support](/support/contact/).