MVE Frequently Asked Questions (FAQs)
Click any of these FAQs for suggestions and resolution.
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 Transit VXC 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.
Is there any DDoS protection for MVE?
Yes, each MVE is protected against distributed denial-of-service (DDoS) attacks. DDoS Scrubbing will keep you online while the malicious traffic is removed and clean traffic is passed to its destination. DDoS protection is included at no additional charge.
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 multi-cloud 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 four 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 order a Transit VXC which provides the IP Transit connectivity. Transit VXC bandwidth is adjustable from 20Mbps to 10Gbps, so the price of the Transit VXC will be a flat monthly recurring charge depending on the amount of selected bandwidth. Transit VXCs will be charged separately to the MVE compute.
These fees include the MVE, public IP address, and internet connectivity with DDoS protection. Transit VXC 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. See MVE Pricing and Contract Terms for details.
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.