Planning Your Versa Secure SD-WAN Deployment

This topic provides an overview of the provisioning process and describes deployment considerations for the Megaport Virtual Edge (MVE).

​

Versa Secure SD-WAN features

Versa Secure SD-WAN focuses on these key capabilities:

• SD-WAN and Secure Access Service Edge (SASE) — A single platform with a best-of-class security offering. For more information, see Securing the Network with SASE.
• One software stack — A single-pipeline integrated architecture for security, advanced networking, robust analytics, and automation.

The Versa Operating System (VOS) delivers both next-generation firewall (NGFW) and SD-WAN services on a single virtual machine. The VOS appliance deployed as a virtual machine on MVE not only optimizes edge-to-cloud network connectivity, but also enforces advanced security services and policies across the Megaport backbone segments. Versa SASE gateway functionality can also be deployed on MVE as part of the many VOS capabilities. Versa refers to this deployment model as private gateways, which offer the same functionality as Versa Cloud Gateways but instead run on a customer or service provider platform. The highly flexible VOS hosted on MVE provides these core SASE services:

• Cloud access security broker (CASB)
• Next-generation firewall (NGFW)
• Secure web gateway (SWG)
• Zero trust network access (ZTNA)

The Versa Secure Access Client (VSAC) is the endpoint security agent that extends SD-WAN and security services to client devices. The VSAC provides Intelligent Gateway Selection, allowing the client to connect to a Versa Cloud Gateway or a private gateway (on MVE). The VSAC policies steer client network traffic based on the specific application. For example, client network traffic for a real-time financial trading application hosted in AWS can be routed through VOS on MVE, whereas traffic for a cloud-based file storage repository can be routed through the Versa Cloud Gateway. For more information, see VOS Versa Operating System and Versa Secure Private Access.

​

Deployment considerations

This section provides an overview of the MVE deployment options and features.

​

SD-WAN vendors

MVE is integrated with Versa Secure SD-WAN, which uses Versa’s Director console to create the private overlay network. 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.

To check which MVE instance sizes are available for your deployment, use the Megaport Portal during the MVE setup process. Instance size availability depends on both the selected vendor and the deployment location, and might vary accordingly. The Megaport Portal displays the sizes that are available for your selected vendor and location. To check the MVE instance sizes in the Megaport Portal

1. In the , go to the Services page.
2. Click Add Services, then select MVE.
3. Select Versa FlexVNF.
4. Select the software version.
5. Click Next.
6. Select an MVE location. Select a location geographically close to your target branch and/or on-premises locations. You can use the Search field to find the Port name, Country, Metro City, or address of your destination Port. You can also filter by diversity zone.
7. A list of available instance sizes appear based on the selected location. Available sizes are highlighted in green and labeled Available. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly.
   If the MVE size you want is not in the list, then 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.

What if I need more MVE capacity in the future? To increase your MVE capacity, you have these options:

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

​

Security

MVE provides secure capacity to and from your internet-enabled branch locations, to any endpoint or service provider on the Megaport SDN. CSP-hosted instances of partner SD-WAN products route critical traffic across the Megaport SDN, reducing internet dependence. Traffic remains encrypted and under your policy control while traveling across the Megaport SDN, to or from, MVE. Versa Secure SD-WAN includes access to a comprehensive security feature: . Versa on MVE natively supports SASE and SD-WAN services. For more information, see Securing the Network with SASE.

​

Licensing

You bring your own Versa (Director) 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.

​

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

For more information, see Types of vNIC Connections.