Connecting MVEs Integrated with Versa Secure SD-WAN

This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with Versa Secure SD-WAN to another MVE.

This deployment uses the Megaport private software defined network (SDN) to reduce reliance on the internet and connect enterprise branch locations.

Branch to branch

With two MVEs configured, you can create a private VXC to connect them on the Megaport network without the need for any physical infrastructure. A VXC is essentially a private point-to-point Ethernet connection between an A-End MVE and a B-End MVE.

Before you begin

Creating a VXC between two MVEs

A private VXC deployment between two MVEs integrated with Versa starts in the Megaport Portal where you create the VXC (choose A-End and B-End devices, IP addressing, VLANs, and optional BGP parameters). Then, you configure the A-End and B-End MVE devices in Director.

To create a VXC

  1. In the Megaport Portal, go to the Services page and click + Connection next to the originating A-End MVE.

  2. Select Private VXC and click Next.

    Private VXC

  3. Select the destination B-End MVE and location.
    Use the Country filter to narrow the selection.

  4. Click Next.

  5. Specify the VXC details.

    • Connection Name – Specify a name for the VXC that is easily identifiable. For example: LA MVE 2 to Dallas MVE 4. You can change the name later, if you like.

    • Service Level Reference (optional) – Specify a unique identifying number for the 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. You can also edit this field for an existing service.

    • Rate Limit – Specify a rate limit, in Mbps. The maximum speed available is limited to the smallest of the originating or destination Port. The maximum speed is displayed.

    • Preferred VLAN – Specify the 802.1q VLAN tag for this connection. Each VXC is delivered as a separate VLAN on the MVE. The VLAN ID must be unique 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.

  6. Click Next to view the Summary screen.

  7. Confirm the configuration and click Add VXC to save the VXC.

  8. Click Order to proceed through the checkout process.

Once the VXC is deployed, you can view it in the Megaport Portal Services page. The Services page displays the VXC under the A-End MVE and the B-End MVE. Note that the service identifier number is the same for the VXC at both ends of the connection.

The next step is to configure the A-End and B-End MVEs in Versa Director.

Note

The next procedure configures IP connectivity with BGP, providing just one solution out of many. Consult your SD-WAN vendor documentation for specific network design and configuration options before configuring interfaces for the MVEs.

Adding MVE details to Director

After you create the VXC between your MVEs, you need to configure it in Versa Director. This involves configuring subinterfaces, IP addresses, next hops, and BGP settings for each Versa MVE.

To configure the A-End MVE

  1. Collect the connection details from the Megaport Portal.

    To display the details, click the gear icon for the VXC connection from your MVE and click the Details view.

  2. Log in to Versa Director.

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

  4. Select Template > Templates in the left navigation.

    Connection details

  5. Click the template you want to edit, then select the Interfaces tab.

  6. In the WAN Interfaces section, locate the Sub Interface column and click the Add icon Add icon to add a subinterface.

    Add subinterface

    A new row appears in the table.

  7. Specify these values for the new subinterface.

    • VLAN ID - Enter the VLAN value from the Megaport Portal.

    • Network Name - Choose + Create WAN Network from the dropdown menu to open the Create WAN Network window. Specify a meaningful name for the network, click OK, and then select the WAN network you created. (Or, if appropriate for your environment, select an existing network name.)

    • IPv4 - Choose Static from the dropdown menu.

    Inteface details

  8. Select the Routing tab to add BGP configuration information.

  9. In the BGP section, select the network name you previously created in the Network column.

    Routing details

  10. Specify the following values according to your MVE configuration:

    • Local AS - This is the A-End MVE.
    • Neighbor IP Address - This is the B-End MVE.
    • Peer AS - This is the B-End ASN.
    • Optionally, you can optionally enable BFD (as appropriate for your network).

    Note

    The values for Local AS and Peer AS come from your network design. They are not part of the Megaport MVE/VXC.

  11. Click the Add icon Add icon to the right of the settings.

  12. Click Recreate (at the bottom of the page).

    A window opens that shows the differences of the configuration. The auto-merged version is recommended, and selected by default.

  13. Click Deploy.

You can use variables in the template to specify values per device for these fields: Router ID, Local AS, Peer AS, and Password.

Note

The Instance ID cannot be modified (the system automatically specifies a value) and the Static IP address is parameterized by default.

To parameterize Router ID, BGP Local AS, Peer AS, and Password

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

  2. Select Templates > Device Templates in the horizontal menu bar.

    Device Templates

  3. Click your template.

    By default, the Interfaces column appears.

  4. In the left navigation, select Virtual Routers and click your network to open the Edit window.

    Virtual routers

  5. In the Edit window, select BGP, then click the Instance ID to open the Edit BGP Instance window.

    BGP details

  6. In the Edit BGP Instance window, click the Parameterize icon Parameterize icon next to each of the following fields: Router ID, Local AS, Peer AS, and Password.

    Edit BGP Instance

  7. Click OK two times to update.

  8. Select the Workflows tab in the top menu bar, then select Devices > Devices in the left navigation.

  9. Click your device to specify values for the variables you just created.

    Versa devices

    The Add Device window opens.

  10. Select the Bind Data tab.

    Bind data

  11. Specify values for the variables.

    • Local AS - Enter the A-End ASN.
    • Password - Enter the MD5 password.
    • Peer AS - Enter the B-End ASN.
    • Router ID - Enter the A-End IP address.
    • Hop Address - Enter the B-End IP address.
    • Static Address - Enter the A-End IP address, including the mask value.
  12. Click Redeploy when finished.

    When the new configurations for the device are prepared successfully, a green checkmark appears at the bottom of the Versa Director window.

  13. To push the changes to the device, click Commit Template (on the upper right).

    Commit template

    The Commit Template to Devices window opens.

    Commit Template to Devices window

  14. Specify the following in the Commit Template to Devices window:

    • Organization - Select your organization from the dropdown menu.

    • Select Template - Select the template to push to the device from the dropdown menu.

    Note that the Template State is OUT_OF_SYNC.

  15. Click the eye icon in the Differences column to verify your configuration changes.

  16. Click Commit to Device.

    A green checkmark appears at the bottom right of the screen when the push is successful. The Template State is now IN_SYNC.

Next, configure the B-End MVE.

There are multiple ways to configure A-End and B-End MVEs using Versa templates and workflows. The steps depend on how you have grouped devices and assigned templates. For example, if both MVEs are in the same device group and shared the same template, you can make changes to the variables in Bind Data for the B-End device to configure the connection.

These steps describe how to configure them using different templates.

To configure the B-End MVE

  1. In Director, select the Workflows tab in the top menu bar.

  2. Select Template > Templates in the left navigation.

  3. Click the template you want to edit, then select the Interfaces tab.

  4. In the WAN Interfaces section, locate the Sub Interface column and click the Add icon Add icon to add a subinterface.

    A new row appears in the table.

  5. Specify these values for the new subinterface.

    • VLAN ID - Enter the VLAN value from the Megaport Portal.

    • Network Name - Choose the same network name as the A-End device from the dropdown menu.

    • IPv4 - Choose Static from the dropdown menu.

    Interface details

  6. Select the Routing tab to add BGP configuration information.

  7. In the BGP section, select the network name for the connection in the Network column.

    Routing details

  8. Specify the following values according to your MVE configuration:

    • Local AS - This is your local MVE: B-End.
    • Neighbor IP Address - This is the A-End IP address.
    • Peer AS - This is the A-End ASN.
    • Optionally, you can optionally enable BFD (as appropriate for your network).
  9. Click the Add icon Add icon to the right of the settings.

  10. Select the Management Servers tab, then click Recreate (at the bottom of the page).

    A window opens that shows the differences of the configuration. The auto-merged version is recommended and selected by default.

  11. Click Deploy.

You can use variables in the template to specify values per device for these fields: Router ID, Local AS, Peer AS, and Password.

Note

The Instance ID cannot be modified (the system automatically specifies a value) and the Static IP address is parameterized by default.

To parameterize Router ID, BGP Local AS, Peer AS, and Password

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

  2. Select Templates > Device Templates in the horizontal menu bar.

  3. Click your template.

    By default, the Interfaces section appears.

  4. In the left navigation, select Virtual Routers and click your network to open the Edit window.

  5. In the Edit window, select BGP, then click the Instance ID to open the Edit BGP Instance window.

  6. In the Edit BGP Instance window, click the Parameterize icon Parameterize icon next to each of the following fields: Router ID, Local AS, Peer AS, and Password.

  7. Click OK two times to update.

  8. Select the Workflows tab in the top menu bar, then select Devices > Devices in the left navigation.

  9. Click your device to specify values for the variables you just created.

    The Add Device window opens.

  10. Select the Bind Data tab.

    Bind Data

  11. Specify values for the variables.

    • Local AS - Enter the B-End ASN.
    • Password - Enter the MD5 password.
    • Peer AS - Enter the A-End ASN.
    • Router ID - Enter the B-End IP address.
    • Hop Address - Enter the A-End IP address.
    • Static Address - Enter the local IP address, including the mask value.
  12. Click Redeploy when finished.

    When the new configurations for the device are prepared successfully, a green checkmark appears at the bottom of the Versa Director window.

  13. To push the changes to the device, click Commit Template (on the upper right).

    Commit Template

    The Commit Template to Devices window opens.

    Commit details

  14. Specify the following in the Commit Template to Devices window:

    • Organization - Select your organization from the dropdown menu.

    • Select Template - Select the template to push to the device from the dropdown menu.

    Note that the Template State is OUT_OF_SYNC.

  15. Click the eye icon in the Differences column to verify your configuration changes.

  16. Click Commit to Device.

    A green checkmark appears at the bottom right of the screen when the push is successful. The Template State is now IN_SYNC.

To verify the connection

  1. Select the Monitor tab in the top navigation bar, select Devices in the horizontal navigation bar, and then select your device to view details in the Summary screen.

    AWS BGP Session Up

  2. In the Summary screen you can review your subinterface in the Interface column, and the Operational and Admin Status.

    AWS BGP Session Up


Last update: