Skip to content
Megaport ONE Documentation
Creating an MVE Manually

Creating an MVE Integrated with Aruba Manually

This topic describes how to manually 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 ONE Portal and to Aruba.

For details on setting up a Megaport ONE account, see Creating an Account. For details on creating an MVE integrated with Aruba using a system tag, see Creating an MVE Using a System Tag.

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 ONE Portal. The basic steps are:

  • Obtain a license from Aruba.
  • Create the Aruba MVE in the Megaport ONE Portal.
  • View the MVE public IP address assignment in the Megaport ONE 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 ONE 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 ONE 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 ONE Portal, choose Networking > Services.
  2. Click Create and select MVE.
    Create MVE button

  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. MVE Location

  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 Aruba EC-V and the software version.
    • 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 Deployment.

      MVE Configuration details

  5. Specify the Aruba EC-V Configuration details:

    • 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 New 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. See Creating an MVE Integrated with Aruba Using a System Key.

  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.

      Note

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

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

    • Promo Code – If you have a promo 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.
    MVE summary

  8. Review the new configuration and pricing and click Confirm.
    To add more MVEs in other locations, go to the Networking > Services page, click Create, and choose MVE.

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 ONE Portal

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

To view an MVE in the Megaport ONE Portal

  • Go to the Networking > Services page.

MVE and transit VXC in MP Portal

As part of the MVE provisioning, Megaport ONE 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.

To view the public IP addresses assigned to the MVE

  1. Select the transit VXC to Megaport Internet.
  2. Locate the public IP address (IPv4 or IPv6) in the Details tab. These are the public IP addresses assigned to the MVE.
    Transit VXC details

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

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.

For details, see Creating a VXC.

Last update: 2023-01-21