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 Creating 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 MVE subscriptions instead of MVE 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.
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 – 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. 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.
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.
Click Create IP Transit VXC to proceed, or click Not now to provision Internet access at a later time.
A destination port in the same diversity zone as the MVE will be assigned automatically.
MVE requires connectivity to the Internet. You can either provision a Transit VXC or provide your own Internet access.
Specify the connection details:
- Connection Name – Specify a unique name for the Transit VXC.
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.
Use the same Service Level Reference numbers for the Transit VXC and MVE to help identify the matching pair in your invoice.
Rate Limit – The rate limit specifies the speed of the Transit VXC and 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. This selection removes the VLAN tagging for this connection and it will be configured without a VLAN ID.
Click Next to proceed to the connection detail summary, click Add VXC, and order the connection.
- Review the Order Services agreement.
Click Save to save the configured MVE before placing the order.
- Click Order.
- If you have a promotional code, click Add Promo Code, enter it, then click Add Code.
- Click Order Now.
Ordering an 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 on the Services page. For details on the Services page, see Understanding the Services Page.
The Transit VXC icon differs from a standard VXC icon in the Megaport Portal, as shown in the image.
Updating the Transit VXC
Click the gear icon next to the Transit VXC in the Megaport Portal to make changes.
You can modify the Transit VXC details including the connection name, rate limit, VLAN ID, or invoice reference. Once submitted, those changes take effect in a few minutes.
To delete the Transit VXC, click the trash icon.
To lock or unlock the Transit VXC, click the padlock icon.
To view the public IP addresses assigned to the MVE
- Click the gear icon next to the Transit VXC.
The Connection Configuration screen appears. From here, you can modify any of the Transit VXC details.
- Click the Details tab.
- Locate the Public IP address (IPv4 or IPv6). These are the public IP addresses assigned to the MVE.
If you have set Orchestrator to automatically approve and upgrade the EC-V appliance, you will see the EC-V under Discovered Appliances. If not, you need to manually approve and upgrade its software to version 184.108.40.206_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.
Log in to your enterprise Aruba Orchestrator system.
Choose Configuration > Discovery | Discovered Appliances or click Appliances Discovered on the upper right of the screen.
You’ll see a new device awaiting approval.
- 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.
- Choose a 9.x software version from the drop-down list that is compatible with your version of Orchestrator.
- Click Upgrade & Reboot Appliance.
The upgrade and reboot process takes approximately 5 to 10 minutes.
- Click Close when the upgrade is complete.
- Click Refresh Discovery Information in the Discovered Devices screen to verify the new software version.
- Click Approve.
The Upgrade Appliance screen shows that no upgrades are available, confirming that Orchestrator is up to date.
- Click Skip.
- Click Run Manual Configuration Wizard in the Apply Appliance Preconfiguration screen.
You can also select a preconfiguration template, if available.
- 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.
- Click Next.
- Select a profile in the Deployment Profile drop-down list, or click Next to skip.
- (Optional) Click Add to add a loopback interface and IP address that meet your network requirements, or click Next.
- As required for your network, select Use SD-WAN Fabric Learned Routes and/or Automatically include local subnets and click Next.
- 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.
- Click Apply.
The Appliance Wizard applies the configuration updates to the MVE EC-V appliance.
- Click Close.
The appliance is now managed via Aruba Orchestrator and you can view it in the list of Discovered Devices.
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.