Planning Your 6WIND 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 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 on the 6WIND-specific settings, see 6WIND - Virtual Service Router.
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 NFVsThe MVE is an on-demand, vendor-neutral Network Function Virtualization (NFV) platform that provides virtual infrastructure for network services at the edge of Megaport’s global software-defined network (SDN). Network technologies such as SD-WAN and NGFW are hosted directly on Megaport’s global network via Megaport Virtual Edge.
on the MVE platform, see the Megaport Virtual Edge (MVE) product page.
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 | Megaport Internet Speed * |
---|---|---|---|---|
MVE 2/8 | 2 | 8 GB | 64 GB | Adjustable from 20 Mbps to 10 Gbps |
MVE 4/16 | 4 | 16 GB | 64 GB | Adjustable from 20 Mbps to 10 Gbps |
MVE 8/32 | 8 | 32 GB | 64 GB | Adjustable from 20 Mbps to 10 Gbps |
MVE 12/48 | 12 | 48 GB | 64 GB | Adjustable from 20 Mbps to 10 Gbps |
* Megaport Internet access is symmetric, redundant, and diverse. Megaport Internet access is adjustable through the Megaport Internet 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 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 four 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: 35 Gbps 1M Routes |
Up to: 25 Gbps 100K CPS |
Up to: 25 Gbps 100K CPS 5M sessions |
Up to: 7 Gbps 25K IPsec tunnels |
4 CPU / 16 GB RAM | Up to: 105 Gbps 2M Routes |
Up to: 75 Gbps ~250K CPS |
Up to: 75 Gbps ~250K CPS 15M sessions |
Up to: 21 Gbps 50K IPsec tunnels |
8 CPU / 32 GB RAM | Up to: 245 Gbps 4M Routes |
Up to: 175 Gbps ~600K CPS |
Up to: 175 Gbps ~600K CPS 30M sessions |
Up to: 49 Gbps 100K IPsec tunnels |
12 CPU / 48 GB RAM | Up to: 350 Gbps 4M Routes |
Up to: 250 Gbps ~800K CPS |
Up to: 250 Gbps ~800K CPS 40M sessions |
Up to: 70 Gbps 100K IPsec tunnels |
Note
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, with the exception of the 12 CPU system which has 2 CPUs allocated to the control plane.
Security
MVE provides capacity to and from your internet-enabled branch locations securely, 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.
In addition, you need a valid license from 6WIND. To request an evaluation license key from 6WIND, raise your request through the 6WIND VSR evaluation page, 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 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 on-ramps or other MVEs).
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 can’t 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.
Note
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.