Skip to content

Connecting MVEs Integrated with VMware SD-WAN

This topic describes how to connect a Megaport Virtual Edge (MVE) integrated with VMware 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 Virtual Cross Connect (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 (another MVE).

Note

By design, the internet-facing interface on an MVE cannot reach the internet-facing interface on another MVE over the public internet. You must create a private VXC to build connectivity between two MVEs. Available routes on the public, internet-facing MVE interfaces are unfiltered, except for routes of other Megaport MVE IP addresses, which are blackholed. MVE prioritizes the path preference for any inter-MVE routes to send them across VXC connections that are not subject to internet variances and security considerations.

Before you begin

Creating a VXC between two MVEs

Private VXC deployment between two VMware MVEs starts in the Megaport ONE Portal where you will create the VXC. Then, you will configure the A-End and B-End MVE devices in the Orchestrator management console.

To create a VXC

  1. In the Megaport ONE Portal, choose Networking > Services.
  2. Click the Gear icon Gear icon next to the originating A-End MVE and select Add Connection.
  3. Select Private Virtual Cross Connect as the Connection Type. Private VXC
  4. Select the destination B-End MVE and location.
    Search for your preferred data center using the Country drop-down list, or enter a search term to filter results as you type. Click Clear Filters to reset the filters.
    Specify B-End
  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.
    • Rate Limit (Mbps) – Specify a rate limit. The maximum speed is displayed. Although the rate limit for a VXC can be up to 10 Gbps, the compute capacity of the A-End or B-End MVE can influence the circuit throughput. Consult VMware’s documentation for details.
    • 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. Megaport ONE will attempt to use the same VLAN ID at both MVE instances. If you specify a VLAN ID that is already in use, you will be notified when placing the MVE order.
      Private VXC details
  6. Specify the billing details:

    • 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.
    • Monthly Price – The monthly rate is based on location and size.
    • Promo Code – If you have a promo code, enter it and click Add Code.
  7. Click Create Connection to view the Summary screen.

  8. Review the configuration and click Confirm.

Once the VXC is deployed, you can view it in the Megaport ONE Portal Networking > Services page under the A-End MVE and the B-End MVE. Note that the service ID 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 Orchestrator.

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 edge details to Orchestrator

After you create the VXC between your MVEs, you need to configure it in Orchestrator. This involves configuring IP addresses and VLAN tags for the interface.

To configure the A-End edge device

  1. In Orchestrator, go to Configure > Edges.

  2. Click the first edge device to configure (the A-End MVE device).

  3. Select the Device tab and scroll down to the Interface Settings.

  4. Click +Add Subinterface.
    Add Subinterface
    The Select Interface dialog box appears.

  5. From the Select Interface menu, choose GE3 and for the Subinterface ID enter the A-End VLAN ID configured on the MVE in the Megaport ONE Portal.
    Select Interface
    The subinterface settings appear.

  6. Click Next.

  7. Ensure that Sub Interface Enabled is enabled.

  8. Modify segments as needed for your SD-WAN configuration.

  9. Change the Addressing Type to Static and provide the A-End IP Address, CIDR prefix, and Gateway.

  10. Update other options as needed for your SD-WAN configuration.

  11. Ensure Enable VLAN Tagging is enabled.
    The VLAN field is automatically populated with the VLAN ID you specified for the subinterface ID.
    Orchestrator Settings

  12. Click Update GE3:vlan-id.

  13. In the upper-right corner of the Configure > Edges window, click Save Changes and then confirm.
    This configures the interface, VLAN tags, and IP addresses so you can test with ping commands through the CLI. (BGP is not yet configured.)

Note

Adding the subinterface momentarily disrupts the connection.

To set up the MVEs to exchange routing information, follow the steps in To configure BGP in Orchestrator.

To configure the B-End edge device

  1. In Orchestrator, go to Configure > Edges.

  2. Click the second edge device to configure (the B-End MVE device).

  3. Select the Device tab and scroll down to the Interface Settings.

  4. Click +Add Subinterface.
    Add Subinterface
    The Select Interface dialog box appears.

  5. From the Select Interface menu, choose GE3 and for the Subinterface ID enter the A-End VLAN ID configured on the MVE in the Megaport ONE Portal.
    Select Interface
    The subinterface settings appear.

  6. Click Next.

  7. Ensure that Sub Interface Enabled is enabled.

  8. Modify segments as needed for your SD-WAN configuration.

  9. Change the Addressing Type to Static and provide the B-End IP Address, CIDR prefix, and Gateway.

  10. Update other options as needed for your SD-WAN configuration.

  11. Ensure Enable VLAN Tagging is enabled.
    The VLAN field is automatically populated with the VLAN ID you specified for the subinterface ID.
    Orchestrator Settings

  12. Click Update GE3:vlan-id.

  13. In the upper-right corner of the Configure > Edges window, click Save Changes and then confirm.
    This configures the interface, VLAN tags, and IP addresses so you can test with ping commands through the CLI. (BGP is not yet configured.)

Note

Adding the subinterface momentarily disrupts the connection.

At this point, the interface is created. The next step is to optionally create the Border Gateway Protocol (BGP) session.

To configure BGP in Orchestrator (optional)

  1. In Orchestrator, go to Configure > Edges and click the MVE device.

  2. Click the Device tab and in the Configure Segments section click Enable Edge Override for BGP Settings.
    This override lets you define BGP values specific for this device beyond the profile definition.
    Enable BGP

  3. Click the toggle button to turn on BGP and click Edit.
    The BGP Editor appears.
    BGP Editor

  4. Enter the Local ASN for the A-End device.
    Each device has its own unique ASN. BGP Settings

  5. For the Neighbor IP, add the IP address from the B-End MVE device.

  6. Add the B-End device ASN to the ASN field for the neighbor.

  7. View all Additional Options and enable BGP options as needed.
    For details on BGP options in Orchestrator, see the VMware Documentation.

  8. Click OK and then click Save Changes.

Validating your connection

  • In Orchestrator under Test & Troubleshoot > Remote Diagnostics, select the MVE and click Run for Troubleshoot BGP - Show BGP Summary to verify the BGP session and ensure the edge device is up.

You can also check connectivity and BGP status from the CLI of the edge device. For details, see Reviewing your VMware MVE connection settings.


Last update: 2023-01-21