Skip to content

Creating an MVE Integrated with Versa

This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Versa Secure SD-WAN. Before you begin, you need user accounts with ordering permissions that provide access to the Megaport Portal and to Versa.

For details on setting up a Megaport account, see Registering an Account.


Versa provides documentation for their SD-WAN product, including Versa Director and cloud connections, at VOS SD-WAN Configuration Product Documentation. (Access requires registration.)

Basic steps

The basic steps to configure an MVE with Versa are:

  • Obtain information for Versa Director.
  • Create a new workflow template in Director.
  • Add a new device group in Director.
  • Add a new device in Director.
  • Create the Versa MVE Instance in the Megaport Portal.
  • View the MVE public IP address assignment in the Megaport Portal.
  • Verify that the MVE is registered and is in-sync from the Versa Director UI.

The following sections provide detailed instructions.

Obtaining required information for Versa Director

To set up Versa you need the following information:

  • Versa Director IPv4 address or FQDN – For example:
  • Versa Controller IPv4 address or FQDN – In Versa Director, select the Configuration tab in the top menu bar. Select Templates > Device Templates in the horizontal menu bar, and select a template. In the template details page, select the Services tab (the gear icon) and then select SDWAN > System > Controller Config. The window displays a list of controllers, their IP address, and any assigned FQDNs.

    Navigate to Template > Templates

  • Local Auth String – The default is which can be modified in Versa Director.

  • Remote Auth String – The default is which can be modified in Versa Director.
  • Serial Number – This value is created when you add a new device in Versa Director.

Creating a new workflow template in Director

The next step is to create a new workflow template and device in Versa Director. Versa strongly suggests using their workflows for creating templates and devices. The workflows automatically build and create some behind-the-scenes configurations and variable values that could otherwise be missed.

To create a new workflow template in Director

  1. Log in to Versa Director.

  2. Select the Workflows tab in the top menu bar.

  3. In the left navigation, select Template > Templates.

    Navigate to Template > Templates

  4. Click the Add icon Add icon to create a template.

  5. In the Basic tab, specify these details.

    • Name – Enter a name for the staging template.
    • Type – Select the template type SDWAN Post Staging from the dropdown menu.
    • Organization – Select the provider organization to associate with the template.
    • Device Type – Select SDWAN from the dropdown menu.
      • Select the appropriate role (Full Mesh, Hub, Hub Controller, or Spoke).
    • Controllers – Select a controller node from your network to associate with the template.
    • Subscription – Select the appropriate subscription information for your network.
      • Solution Tier – Network service to be configured.
      • Service Bandwidth – Allocated bandwidth for the service in Mbps.
    • Preferred Software Version – Preferred version of the software that should be deployed on Versa Director. The preferred software version applies to zero-touch provisioning (ZTP). During ZTP, Versa Director upgrades a branch to the preferred version, if applicable. The preferred version can be backward compatible for up to two previous VOS versions.

      Create Workflow Template

    For details about creating Versa staging templates, see Create and Manage Staging and Post-Staging Templates.

  6. Select the Interfaces tab and specify these details.

    • Number of Ports – Choose 4. MVE requires 4 ports.
      Note, Port 0 is reserved for management (Mgmt) and cannot be changed.
    • Click the icon for port 1 and select WAN from the dropdown menu. A row is added to the WAN Interfaces list. (The WAN interface is automatically configured by the MVE creation process to connect through the included transit VXC with bandwidth determined by the MVE size.)
    • VLAN ID – The value should be set to 0.
    • Network Name – The value should be set to INET-1.
    • IPv4 – The value should be set to DHCP.
    • The remaining fields can be left unchanged.


    You can optionally enter circuit information.

  7. Click Continue (at the bottom right) until you see the Create option, then click Create.

    Finalize Creation of Workflow Template

You can now apply the template to a new device group.

Adding a new device group in Director

The next step is to create a new device group.

  1. Log in to Versa Director.

  2. Select the Configuration tab in the top menu bar.

  3. In the horizontal menu bar, select Devices > Device Groups.

    Director: Add New Device

  4. Click the Add icon Add icon to add a device group.

  5. Specify these details:

    • Name – Enter a name for the device group that is easily identifiable.
    • Description – Enter descriptive information about the device group.
    • Tags – Optionally, enter strings for users to search on.
    • Organization – Select your organization from the dropdown.
    • Post Staging Template – Select the template you created previously.

    Director: Add New Device Group

  6. Click OK.

Adding a new device in Director

The next step is to add a new device.

  1. Log in to Versa Director.
  2. Select the Workflows tab in the top menu bar.

  3. In the left navigation, select Devices > Devices.

    Director: Navigate to Devices

  4. Click the Add icon Add icon to open the Add Device window.

    Director: Add New Device

  5. In the Basic tab, specify these details.

    • Name - Specify a meaningful name for the device.
    • Global Device ID - Versa Director automatically assigns the next available ID.
    • Organization - Choose your organization from the dropdown.
    • Deployment Type - Choose CPE-Baremetal Device from the dropdown.
    • Serial Number - Enter a serial number for the device. Specify a unique and meaningful value for the device and make a note of it, as you need it again when creating the Versa MVE instance in the Megaport Portal.
    • Device Groups - Choose the device group you created previously. This will assign the new device to that device group.
  6. Click Continue.

  7. In the Location Information tab, enter the country where the device is located.

  8. Click Continue until you see the Deploy button.

  9. Click Deploy.

    The new device is now deployed in Versa Director.

Creating the Versa MVE instance in the Megaport Portal

Before you create an MVE in the Megaport Portal, you need to determine the best location - one that supports MVE and one that is in the most compatible metro area. You can connect multiple locations to an individual MVE. For location details, see Planning Your Deployment.

You can deploy multiple MVEs within the same metropolitan area for redundancy or capacity reasons.

To create an MVE

  1. In the Megaport Portal, go to the Services page.
  2. Click Create MVE.
    Create MVE button

  3. Select the MVE location.

    Select a location geographically close to your target branch and/or on-premises locations.

    The country you choose must be a market in which you have already registered.

    If you haven’t registered a billing market in the location where you will deploy the MVE, follow the procedure in Enabling a Billing Market.

    To search for your local market in the list, enter a country in the Country Filter or a metro region detail in the Search filter.

    Select MVE location

  4. Click Next.

  5. Select Versa FlexVNF and the software version.

    The MVE will be configured to be compatible with this software version from Versa.

  6. Specify the MVE details.

    Megaport Portal: Create Versa MVE Instance

    • MVE Name – Specify a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport Portal.
    • Size – Select a size from the drop-down list: Small, Medium, or Large. Three sizes are available to support varying numbers of concurrent connections. Individual partner product metrics vary slightly, but in general the small size can handle greater than 40 concurrent branch connections and up to 500 Mbps of traffic, a medium size up to 100 connections and 1 Gbps, and a large size approximately 500 connections and approximately 5 Gbps of traffic. For sizing details, see Planning Your Versa Deployment.


      Partner managed accounts can apply a Partner Deal to a service. For details, see Applying a Deal to a Service.

    • Minimum Term – Select No Minimum Term to pay-as-you-go, or select a term of 12, 24, or 36 months. Longer terms result in a lower monthly rate. By default, a 12-month term is selected.


      Partner and partner managed accounts cannot view or change MVE contract terms.

      For details on contract terms, see MVE Pricing and Contract Terms.

    • Service Level Reference (optional) – Specify a unique identifying number for the MVE to be used for billing purposes, such as a cost center number or a unique customer ID. The service level reference number appears for each service under the Product section of the invoice. You can also edit this field for an existing service.

    • Director Address – Enter the FQDN or IPv4 address of your Versa Director.
    • Controller Address – Enter the FQDN or IPv4 address of your Versa Controller.
    • Local Auth – Enter the Local Auth string as configured in your Versa Director.
    • Remote Auth – Enter the Remote Auth string as configured in your Versa Director.
    • Serial Number – Enter the serial number that you used when creating the device in Versa Director.
  7. Click Next to view the Summary screen.

    The monthly rate is based on location and size.

  8. Confirm the configuration and pricing and click Add MVE.

    Megaport Portal: Add MVE

  9. Click Order.

  10. Review the Order Services agreement, and click Order Now.

    • Click Save to save the configured MVE before placing the order.
    • Click Add Promo Code to enter a promotional code, and click Add Code.

    Ordering MVE provisions the instance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up a Versa FlexVNF.

Viewing the MVE public IP address assignment in the Megaport Portal

After creating the MVE, you can view it in the Megaport Portal.

To view the MVE in the Megaport Portal and Director

  • Go to the Services page.

MVE and transit VXC in MP Portal

As part of the MVE provisioning, Megaport creates a transit Virtual Cross Connect (VXC) to provide internet connectivity and to allow MVE to register and communicate with the Versa SD-WAN overlay network. The overlay network is created and maintained by Versa to provide secure tunnels from the branch locations. The transit VXC is a fixed size, based on the size of the MVE. You cannot modify or delete the transit VXC. The transit VXC icon differs from a standard VXC icon in the Megaport Portal, as shown in the image.

To view the public IP addresses assigned to the MVE

  1. Click the Gear icon Gear icon next to the transit VXC to Megaport Internet.

  2. Locate the public IP address (IPv4 or IPv6).

    These are the public IP addresses assigned to the MVE. Make a note of these addresses for use later.

  3. Verify that you see your new MVE device in the Megaport Portal under Services.

  4. In Versa Director, verify that the new MVE configuration is synced, the service is up, and it is reachable. Select the Monitor tab, then select Devices in the horizontal menu. Review the Config Synchronized, Reachability and Service columns.

    MVE status


It can take up to 10 minutes for the MVE to register with Versa Director.

Next steps

Now that you’ve deployed an MVE, the next step is to connect a VXC to a CSP, a local port, or a third-party network. You can optionally connect a physical Port to the MVE through a private VXC or connect to a service provider in the Megaport Marketplace.

Last update: 2022-02-09