Creating an MVE Integrated with Aruba

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

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

Tip

Aruba provides documentation for their SD-WAN product, including Orchestrator and cloud connections, at Aruba (SilverPeak) Documentation Library.

Basic steps

This section provides an overview of the configuration steps in Aruba Orchestrator and the Megaport Portal. The basic steps are:

  • Obtain a license from Aruba.
  • Create the Aruba MVE in the Megaport Portal.
  • View the MVE public IP address assignment in the Megaport Portal.
  • Configure the Aruba EdgeConnect (EC-V) in Aruba Orchestrator.
  • Apply the license to the EC-V.

The next sections provide details.

Licensing

Before you create an MVE in the Megaport Portal, you need to buy a valid EdgeConnect SD-WAN license from Aruba. All licenses are managed by the Aruba Cloud Portal.

Creating an MVE in the Megaport Portal

Before you create an MVE, 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 Aruba EC-V and the software version.
    MVE requires Aruba Orchestrator version 9 or later. If you create an MVE with an earlier version of EC-V, you must immediately upgrade to version 9.

  6. Specify the MVE details.
    MVE 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 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 Deployment.

      Note

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

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

      Note

      The transit VXC associated with the MVE is automatically updated with the MVE service level reference number.

    • Orchestrator Account Name – Enter the Account Name from Aruba Orchestrator. To view your Account Name, log in to Orchestrator and choose Orchestrator > Licensing | Cloud Portal.

    • Account Key – Enter the Account Key from Aruba Orchestrator. The key is linked to the Account Name. To view your Account Key, log in to Orchestrator and choose Orchestrator > Licensing | Cloud Portal. If a key isn’t visible in Orchestrator, click Generate Account Key.
      Account Name and Account Key

    • System Tag (optional) – Aruba Orchestrator System Tags and preconfiguration templates register the EC-V with the Cloud Portal and Orchestrator, and enable Orchestrator to automatically accept and configure newly discovered EC-V appliances. If you created a preconfiguration template in Orchestrator, enter the System Tag you specified here.

  7. Click Next to view the Summary screen.

    The monthly rate is based on location and size.
    MVE summary

  8. Confirm the configuration and pricing and click Add MVE.
    Click Create MVE to add more MVEs in other locations.

  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 appliance and assigns IP addresses from the Megaport SDN. The MVE provisioning takes only a few minutes to complete. The provisioning process spins up an Aruba EdgeConnect (EC-V).

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

  • Go to the Services page.

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 Aruba SD-WAN overlay network. The overlay network is created and maintained by Aruba 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.

MVE and transit VXC in MP Portal

To view the public IP addresses assigned to the MVE

  1. Click the gear icon next to the transit VXC to Megaport Internet.
    Transit VXC details
  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.

Approve and upgrade the MVE EC-V appliance

After you create the new EC-V appliance, it will be visible under Discovered Appliances in Aruba Orchestrator. Next, you will accept it as a new appliance and upgrade its software to version 9.1.0.0_91199.

To approve and upgrade the new EC-V appliance

Before Aruba Orchestrator adds the EC-V to its list of managed appliances, you need to manually approve it.

  1. Log in to your enterprise Aruba Orchestrator system.

  2. Choose Configuration > Discovery | Discovered Appliances or click Appliances Discovered on the upper right of the screen.
    You’ll see a new device awaiting approval.
    Discovered appliances

  3. Click Approve next to the new device.
    The Upgrade Appliance screen appears. MVE requires that you upgrade Aruba Orchestrator to a minimum of version 9 or later.
    Upgrade Appliance
  4. Choose a 9.x software version from the drop-down list that is compatible with your version of Orchestrator.
  5. Click Upgrade & Reboot Appliance.
    The upgrade and reboot process takes approximately 5 to 10 minutes.
  6. Click Close when the upgrade is complete.
  7. Click Refresh Discovery Information in the Discovered Devices screen to verify the new software version.
    Refresh Discovery Information
  8. Click Approve.
    The Upgrade Appliance screen shows that no upgrades are available, confirming that Orchestrator is up to date.
  9. Click Skip.
  10. Click Run Manual Configuration Wizard in the Apply Appliance Preconfiguration screen.
    You can also select a preconfiguration template, if available.
  11. Provide the appliance details:
    • Hostname – Megaport assigns a hostname by default, however this is a free text field allowing you to assign an easily identifiable name for this appliance.
    • Group – As required for your network, specify a group name for the appliance.
    • Admin Password – Specify and confirm a secure password.
    • Serial Number – This number is assigned by default.
      The rest of the fields are optional.
  12. Click Next.
    Appliance details
  13. Select a profile in the Deployment Profile drop-down list, or click Next to skip.
    Deployment profile
  14. (Optional) Click Add to add a loopback interface and IP address that meet your network requirements, or click Next.
    Loopback interface
  15. As required for your network, select Use SD-WAN Fabric Learned Routes and/or Automatically include local subnets and click Next.
    Add local routes
  16. As required for your network, select or deselect the appropriate options under Add Business Intent Overlays to this Site and Select Template Groups to be applied to this Site.
    Note that improper configuration of overlays and/or labels can result in Orchestrator communication errors. See the Aruba documentation for details.
    Business Intent Overlays and Template Groups
  17. Click Apply.
    The Appliance Wizard applies the configuration updates to the MVE EC-V appliance.
    Applying configuration
  18. Click Close.

The appliance is now managed via Aruba Orchestrator and you can view it in the list of Discovered Devices.

Deleting an MVE

You can terminate an MVE directly from the Megaport Portal.

To delete an MVE

  1. In the Megaport Portal, go to the Services page.

  2. Click the trash can icon next to the MVE you want to delete.

    A list of all services connected to the MVE appear.

    Terminate an MVE

  3. Click Yes - Terminate Services to confirm the MVE termination, or click No, Keep Services to cancel.

    The MVE and its associated VXCs are deleted from the Megaport network. In Aruba Orchestrator, choose Administration > Software | Remove Appliances to view options for deleting the MVE EC-V.

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: