Skip to content
Megaport ONE Documentation
Creating an MVE Using a System Tag

Creating an MVE Integrated with Aruba Using a System Tag

This topic describes how to create and configure a Megaport Virtual Edge (MVE) with Aruba EdgeConnect SD-WAN using a system tag.

System tag configuration simplifies MVE deployment by automating several required configuration tasks. This method automatically performs these tasks:

  • Enables Aruba Orchestrator to approve and configure the newly discovered EC-V without user intervention.
  • Upgrades Orchestrator to version 9 or later.
  • Registers the MVE with the Cloud Portal and Orchestrator.
  • Assigns the appropriate group memberships and roles to the MVE.
  • Applies the MVE configuration using your custom deployment settings.
  • Spins up an EdgeConnect (EC-V).

Note

In Orchestrator, a Megaport MVE is called an Aruba EdgeConnect (EC-V). The terms EC-V and MVE are used interchangeably in this topic.

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 manually, see Creating an MVE Integrated with Aruba Manually.

Tip

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

Basic steps

The basic configuration steps using a system tag are:

  • Obtain a license from Aruba.
  • Create a preconfiguration template in Aruba Orchestrator. The template includes a system tag.
  • Create an Aruba MVE in the Megaport ONE Portal, assigning the system tag to the MVE. Orchestrator configures the MVE using the deployment parameters specified in the template.

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 a preconfiguration template

Aruba Orchestrator system tags identify a unique preconfiguration template used to register the MVE with the Cloud Portal and Orchestrator, and enable Orchestrator to automatically accept and configure the newly discovered MVE appliance.

To preconfigure a template

  1. Log in to Aruba Orchestrator.
  2. Choose Configuration > Overlays & Security > Discovery > Preconfiguration.

  3. Click New.

    MVE preconfiguration

  4. Name the template.

  5. Enable Auto Approve when Discovered.
  6. Enter the Appliance/System Tag name to use as the unique identifier to associate with the MVE. For example, aruba-test-1. Make a note of the system tag for use in the Megaport ONE Portal later. Orchestrator will match this tag with the MVE during discovery.
  7. Enter any deployment-specific parameters by modifying the script values on the right side of the page. The example script applies these deployment settings automatically:
    • Upgrades the appliance to the specified 9.x software version.
    • Assigns appropriate roles and group memberships to the appliance.
    • Converts the appliance to inline router mode.
    • Creates a LAN-side placeholder interface.
    • Assigns WAN-side bandwidth calculations based on the MVE sizing.
    • Enables stateful source NAT (SNAT) firewall settings on the WAN public-facing interface.
  8. Delete any unused parameters.
  9. Click Validate to test the configuration.
  10. Click Save.

Once you have saved the template, you are ready to create the MVE in the Megaport ONE 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 Service 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 Aruba MVE 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 – Enter the appliance/system tag you specified when you created the preconfiguration template in Orchestrator.
      Aruba EC-V Configuration details

  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.

      Aruba billing details

  7. Click Deploy MVE.
    A summary screen appears.
    MVE summary

  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 Aruba SD-WAN overlay network.
    Create Transit VXC

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.

      Transit VXC connection details

  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.
    Transit VXC summary

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

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 MVE after discovering and approving it using the system tag.

Viewing the MVE

You can view the MVE in the Megaport ONE Portal and Aruba Orchestrator. You can also view the MVE public IP address assignment in the Megaport ONE Portal.

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.

MVE and Transit VXC in MP Portal

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.

To view the public IP addresses assigned to the MVE

  1. Click the gear icon 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.
    Transit VXC Connection details
  2. Click the Details tab.
    Transit VXC details
  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 Aruba Orchestrator

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

To view an MVE in Orchestrator

  1. Log in to Orchestrator.
  2. Choose Orchestrator > Configuration > Deployment.
  3. Click the Edit icon next to the appliance.

MVE preconfiguration deployment

As you add to your network, you can clone and modify the template for reuse with other EC-V deployments, assigning each EC-V a unique system tag.

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

Last update: 2023-11-08