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).
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 Portal and to Aruba.
For details on setting up a Megaport account, see Registering an Account.
For details on creating an MVE integrated with Aruba manually, see Creating an MVE Integrated with Aruba Manually.
Aruba provides documentation for their SD-WAN product, including Orchestrator and cloud connections, at Aruba (SilverPeak) Documentation Library.
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 the Aruba MVE in the Megaport 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.
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 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
- Log in to Aruba Orchestrator.
- Choose Configuration > Overlays & Security > Discovery > Preconfiguration.
Name the template.
- Enable Auto Approve when Discovered.
- 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 Portal later. Orchestrator will match this tag with the MVE during discovery.
- 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.
- Delete any unused parameters.
- Click Validate to test the configuration.
- Click Save.
Once you have saved the template, you are ready to create the MVE in the Megaport 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
- In the Megaport Portal, go to the Services page.
Click Create MVE.
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 Billing Markets.
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 Aruba EC-V and the software version.
Specify the 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. 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.
Partner managed accounts can associate a Partner Deal to a service with a minimum 12-month subscription. For details, see Associating a Deal With a 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.
Partner and partner managed accounts select MCR subscriptions instead of MCR contract terms.
For details on contract terms, see MVE Pricing and Contract Terms.
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.
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.
System Tag – Enter the Appliance/System Tag you specified when you created the preconfiguration template in Orchestrator.
Click Next to view the Summary screen.
The monthly rate is based on location and size.
Confirm the configuration and pricing and click Add MVE.
Click Create MVE to add more MVEs in other locations.
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 MVE after discovering and approving it using the system tag.
Viewing the MVE
You can view the MVE in Orchestrator and the Megaport Portal.
Viewing in 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
- Log in to Orchestrator.
- Choose Orchestrator > Configuration > Deployment.
- Click the Edit icon next to the appliance.
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.
Viewing 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.
To view the public IP addresses assigned to the MVE
- Click the gear icon next to the transit VXC to Megaport Internet.
- Locate the public IP address (IPv4 or IPv6). These are the public IP addresses assigned to the MVE.
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.