Skip to content

Planning Your VMware SD-WAN MVE Deployment

This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport ONE 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 branch to any destination on the Megaport network and interoperation with other Megaport products and services
Customer premises equipment (CPE) installed in branch Distributed denial-of-service (DDoS) connection to the internet to terminate tunnel between MVE and CPE at branch
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 VMware SD-WAN, which uses VMware’s Orchestrator management console to create the private overlay network. Additional SD-WAN providers are available.

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 Internet Access *
MVE 2/4/20 2 4 GB 8 GB 20 Mbps
MVE 4/8/20 4 8 GB 8 GB 20 Mbps
MVE 2/4/100 2 4 GB 8 GB 100 Mbps
MVE 4/8/200 4 8 GB 8 GB 200 Mbps
MVE 2/4/500 2 4 GB 8 GB 500 Mbps
MVE 4/8/1000 4 8 GB 8 GB 1000 Mbps
MVE 8/16/5000 8 16 GB 8 GB 5000 Mbps
MVE 12/24/5000 12 24 GB 8 GB 5000 Mbps

* Internet access is symmetric, redundant, and diverse, and includes DDoS protection.

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.

  • Plans to scale the network.

What if I need more MVE capacity in the future?

You can:

  • Provision another MVE instance, add it to your SD-WAN overlay network, and split the workload between the two MVEs.

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


MVE provides capacity to and from your internet-enabled branch locations securely, to any endpoint or service provider on Megaport ONE’s SDN. CSP-hosted instances of partner SD-WAN products route critical traffic across Megaport ONE’s SDN, reducing internet dependence. Traffic remains encrypted and under your policy control while traveling across the Megaport ONE SDN, to or from, MVE.

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


You bring your own VMware 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 details on obtaining a VMware license, see Edge Licensing or ask your VMware Sales Associate or Reseller.

VLAN tagging

Megaport uses Q-in-Q to differentiate between customer MVEs on a host hardware system. The tenant MVE receives an untagged VLAN on the internet-facing link, and single-tagged 802.1Q traffic toward other destinations on the Megaport network (such as CSP onramps or other MVEs). For details, see Configuring Q-in-Q.

Last update: 2022-07-20