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 ONE Portal and to Versa.

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

Tip

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 a Versa MVE in the Megaport ONE Portal.
• View the MVE public IP address assignment in the Megaport ONE 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: cloud211.versa-networks.com.

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

  

• Local Auth String – The default is SDWAN-Branch@Versa.com which can be modified in Versa Director.

• Remote Auth String – The default is Controller-1-staging@Versa.com 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.

   

4. Click (Add) 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 drop-down menu.
   • Organization – Select the provider organization to associate with the template.
   • Device Type – Select SDWAN from the drop-down 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.

     

   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 drop-down 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 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.

   Note

   You can optionally enter circuit information.

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

   

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.

   

4. Click (Add) 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 drop-down.
   • Post Staging Template – Select the template you created previously.

   

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.

   

4. Click (Add) to open the Add Device window.

   

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 drop-down.
   • Deployment Type – Choose CPE-Baremetal Device from the drop-down.
   • 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 ONE 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 an MVE in the Megaport ONE Portal

Before you create an MVE in the Megaport ONE 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 ONE Portal, choose Networking > Services.

2. Click Create Service and select MVE.
   

3. Select an MVE location geographically close to your target branch and/or on-premises locations.
   You can search for your preferred location using the Country drop-down list, or enter a search term to filter results as you type. Click Clear Filters to reset the filters. Note that 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, see Enabling Billing Markets.
   

4. Specify the MVE Configuration details:

   • MVE Name – Enter a name for the MVE that is easily identifiable, particularly if you plan on provisioning more than one. This name appears in the Megaport ONE Portal.
   • Vendor – Select Versa FlexVNF and the software version. The MVE will be configured to be compatible with this software version from Versa.
   • Service – Displays the vendor name and software version, and any important information such as upgrade requirements.
   • MVE Size – Select a size from the drop-down list. The list displays all sizes that match the CPU capacity at the selected location. The sizes support varying numbers of concurrent connections, and individual partner product metrics vary slightly. For sizing details, see Planning Your Versa Secure SD-WAN Deployment.
     

5. Specify the VersaFlexVNF Configuration details:

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

6. Specify the Billing Details:

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

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

     Note

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

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

   • Monthly Price – The monthly rate is based on location, size, and contract term.

   • Promo Code – If you have a promotional code, enter it and click Add Code.

     Note

     Partner-managed accounts can apply a Partner Deal to a service.

     

7. Click Deploy MVE.
   A summary screen appears.
   

8. Review the new configuration and pricing then click Confirm.
   You are prompted to create a Transit Virtual Cross Connect (VXC). A Transit VXC provides connectivity and allows MVE to register and communicate with the Versa SD-WAN overlay network.
   

To create the Transit VXC

1. Click Create IP Transit VXC to proceed (recommended), or click Not now to provision your own internet access at a later time.
   A destination port in the same diversity zone as the MVE will be assigned automatically.

   Note

   MVE requires connectivity to the internet onto the management plane virtual interface. You can either provision a Transit VXC or configure a third-party internet connection using a private VXC. We strongly recommend that you order a Megaport Transit VXC for the initial MVE startup and deployment to ensure that the MVE is provisioned and functioning correctly.

2. Specify the VXC Configuration details:

   • Connection Name – Specify a unique name for the Transit VXC.

   • Rate Limit (Mbps) – Specify the speed for the Transit VXC.
     This speed is adjustable from 20 Mbps to 10 Gbps in increments of 1 Mbps. You can change the speed as needed after you create the Transit VXC. Monthly billing details appear based on location and rate limit.

   • Preferred A-End VLAN (optional) – Specify an unused VLAN ID for this connection.
     This must be a unique VLAN ID on this MVE and can range from 2 to 4093. If you specify a VLAN ID that is already in use, the system displays the next available VLAN number. The VLAN ID must be unique to proceed with the order. If you don’t specify a value, Megaport will assign one. Alternatively, you can click Untag VLAN. This selection removes the VLAN tagging for this connection and it will be configured without a VLAN ID.

     

3. Specify the Billing Details:

   • Service Level Reference (optional) – Specify a unique identifying number for the Transit VXC 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.

     Tip

     Use the same Service Level Reference numbers for the Transit VXC and MVE to help identify the matching pair in your invoice.

   • Monthly Price – The monthly rate is based on location and size.

   • Promo Code – If you have a promotional code, enter it and click Add Code.

4. Click Create Connection to order the connection.
   A summary screen appears.
   

5. Review the new connection details and pricing then click Confirm.
   The MVE and Transit VXC are created.
   

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 in the Megaport ONE Portal

After creating the MVE, you can view it in the Megaport ONE Portal on the Services page. You can also view the MVE public IP address assignment.

To view an MVE in the Megaport ONE Portal

• Go to the Networking > Services page.

Under the new MVE, you will see a Transit VXC to “Megaport IP Transit”. The Transit VXC icon differs from a standard VXC icon in the Megaport ONE Portal, as shown in the image.

For details on the Services page, see Viewing Network Services.

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

To view the public IP addresses assigned to the MVE

1. Click the gear icon next to the Transit VXC and select Edit Service.
   The VXC Configuration details appear. From here, you can modify any of the Transit VXC details.
   
2. Click the Details tab.
   
3. 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.

Viewing the MVE in Versa Director

After creating the MVE, you can monitor the status in Director. In Director, verify that the new MVE configuration is synced, the service is up, and it is reachable.

To view an MVE in Director

1. Log in to Versa Director.
2. Select the Monitor tab, then select Devices in the horizontal menu.

3. Review the Config Synchronized, Reachability and Service columns.

   

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.

For details, see Creating a VXC to an MVE Integrated with Versa.

---

Last update: 2023-11-08