Deployment considerations
This section describes MVE deployment options and sizing for Netskope One SD-WAN. For an overview of Netskope One SD-WAN features, see Netskope One SD-WAN with Megaport Virtual Edge. For information about all supported 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. To size your MVE correctly, consult the vendor’s sizing documentation to ensure it aligns with the number and type of features you plan to enable. 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 affect the maximum throughput speed.
- Future plans to scale the network.
- In the , go to the Services page.
- Click Add Service, then select Virtual Edge (MVE). The Create Virtual Edge page opens.
- In the Select Vendor / Product section, select Netskope One SD-WAN.
-
In the Location section, select an MVE location.
Select a location geographically close to your target branch or on-premises locations. Use the Search field to find a location by metro or country name. Alternatively, browse the region tabs, then select a location. Size availability can differ between data centers at the same location. To check a specific data center, select Manual mode, then select the provider and data center. -
View the available sizes in the MVE Size section.
Each size shows its vCPU and RAM allocation. Only sizes supported by the selected product are listed, and sizes that are not available at the selected location are grayed out and labeled Not available here. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.If the MVE size you want is not available, there is not enough capacity at the selected location. You can either select another location with enough capacity or contact your Account Manager to discuss requirements.
- You can provision another MVE instance, add it to your network, and split the workload between the two MVEs.
- You can provision a larger MVE instance, migrate connections from the old MVE to the new larger MVE, and then retire the old MVE.
Security
MVE provides secure capacity to and from your internet-enabled branch locations, 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. You also need a valid Netskope One SD-WAN license and access to the Netskope One portal to generate the activation token and URI (if using activation). For more information, see the Netskope website.VLAN tagging
Megaport uses 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). For more information, see Configuring Q-in-Q.vNICs
Each MVE can have up to five vNICs. A Netskope One SD-WAN MVE is created with one vNIC by default, named WAN, LAN, Mgmt. You can add up to four more, making a total of five. Before specifying the number of vNICs on your MVE:- You cannot change the number of vNICs after ordering an MVE. Decide in advance how many vNICs to specify when you create the MVE.
- Consult your service provider to verify that adding a vNIC does not affect functionality.
If you need to change the number of vNICs after an MVE has been ordered, you must cancel and re-order the MVE.