Skip to content

Planning Your Aruba EdgeConnect SD-WAN MVE Deployment

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 IP Transit connection with Distributed Denial of Service (DDoS) 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 details, visit the Aruba (SilverPeak) Documentation Library.

SD-WAN vendors

MVE is integrated with Aruba SD-WAN, which uses the Aruba Orchestrator console to create the private overlay network.

Additional SD-WAN providers include Cisco SD-WAN, Fortinet Secure SD-WAN, Versa SD-WAN, and VMware SD-WAN.

MVE locations

For a list of global locations where you can connect to an MVE, see Megaport Virtual Edge Locations.

Sizing your MVE instance

The instance size determines the MVE capabilities, such as how many concurrent connections it can support. The MVE instances are consolidated into these sizes:

Package Size vCPUs DRAM Storage IP Transit Speed *
MVE 2/8 2 8 GB 30 GB Adjustable from 20 Mbps to 10 Gbps
MVE 4/16 4 16 GB 30 GB Adjustable from 20 Mbps to 10 Gbps
MVE 8/32 8 32 GB 30 GB Adjustable from 20 Mbps to 10 Gbps
MVE 12/48 12 48 GB 30 GB Adjustable from 20 Mbps to 10 Gbps

* IP Transit access is symmetric, redundant, diverse, and includes DDoS scrubbing protection. IP Transit access is adjustable through the Transit VXC connection that you attach to the MVE.

These performance and capacity metrics are estimates and your speeds will vary. 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 impact the maximum throughput speed.

  • Future plans to scale the network.

What if I need more MVE capacity in the future?

You have a couple of 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 Transit VXC bandwidth at any time without having to tear down the virtual machine.


MVE provides capacity to and from your internet-enabled branch locations securely, 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.

Each MVE subscription includes distributed denial-of-service (DDoS) attack protection for no additional charge.


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 Q-in-Q 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 onramps or other MVEs).

Last update: 2023-09-25