Planning Your 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 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|
This section provides an overview of the MVE deployment options and features.
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 three sizes.
|Size||Maximum Throughput||SD-WAN Endpoints||DRAM|
|Small (2 vCPUs)||500 Mbps||40||4 GB|
|Medium (4 vCPUs)||1 Gbps||100||8 GB|
|Large (8 vCPUs)||5 Gbps||500||16 GB|
These performance and capacity metrics are estimates and your speeds will vary. When choosing an MVE instance size, keep in mind these items:
The maximum throughput numbers are characterized using a pure SD-WAN hub for hub-and-spoke connections.
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 have a couple 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.
MVE provides capacity to and from your internet-enabled branch locations securely, to any endpoint or service provider on Megaport’s SDN. CSP-hosted instances of partner SD-WAN products route critical traffic across Megaport’s 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 Cisco Interconnect Gateway (Cisco Catalyst 8000v Edge Software) license for Cisco SD-WAN 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 refer to the Cisco Catalyst 8000V Edge Software Ordering Guide.
Megaport uses Q-in-Q, also known as 802.1ad nested VLANs, to differentiate between customer MVEs on a given host hardware system.