Creating an AWS Hosted Connection for an MVE with Aruba EdgeConnect SD-WAN

1. In the , go to the Services page and select the MVE for the connection.
2. Click +Connection then click Cloud.
3. Select AWS as the service provider, select Hosted Connection as the AWS Connection Type, select the destination port, then click Next.
   You can use the Select Destination Port search field to narrow the selection.
   Each destination port has either a blue or red icon to indicate its diversity zone. To achieve diversity, you need to create two connections with each one in a different zone.
4. Specify the connection details:
   • Connection Name — The name of your VXC to be shown in the .
   • Service Level Reference (optional) — Specify a unique identifying number for your Megaport service to be used for billing purposes, such as a cost center number, unique customer ID, or purchase order number. 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.
   • Rate Limit — The speed of your connection. This value cannot be changed after deployment. The drop-down list displays predefined rate limits available for your MVE, with speeds varying by location and service capabilities.
   • VXC State — Select Enabled or Shut Down to define the initial state of the connection. For more information, see Shutting Down a VXC for Failover Testing.
     If you select Shut Down, traffic will not flow through this service and it will behave as if it was down on the Megaport network. Billing for this service will remain active and you will still be charged for this connection.
   • A-End vNIC — Select an A-End vNIC from the drop-down list. For more information about vNICs, see Creating an MVE in the Megaport Portal.
   • 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.
   • Minimum Term — Select No Minimum Term, 12 Months, 24 Months, 36 Months, 48 Months, or 60 Months. Longer terms result in a lower monthly rate. 12 Months is selected by default. Take note of the information on the screen to avoid early termination fees (ETF). Select Automatically Renew at the same price at the end of Contract Term for services with a 12, 24, 36, 48 or 60-month term to automatically renew the contract at the same discounted price and term length at the end of the contract. If you don’t renew the contract, at the end of the term, the contract will automatically roll over to month-to-month contract for the following billing period, at the same price, without term discounts. For more information, see Managing Minimum Term Renewal. For more information, see VXC Pricing and Contract Terms and VXC, Megaport Internet, and IX Billing.
   • Resource Tags — You can use resource tags to add your own reference metadata to a Megaport service.
     To add a tag:
     1. Click Add Tags.
     2. Click Add New Tag.
     3. Enter details into the fields:
        • Key — String, maximum length 128 characters. Valid values are a-z 0-9 _ : . / \ -
        • Value — String, maximum length 256 characters. Valid values are a-z A-Z 0-9 _ : . @ / + \ - and spaces
     4. Click Save.
        If you already have resource tags for that service, you can manage them by clicking Manage Tags.
     Never include sensitive information in a resource tag. Sensitive information includes commands that return existing tag definitions and information that will identify a person or company.
5. Click Next.
6. Specify the connection details for the AWS service.
   • AWS Connection Name — This is a text field and will be the name of your virtual interface that appears in the AWS console. The AWS Connection Name is automatically populated with the name specified in a previous step.
   • AWS Account ID — This is the ID of the account you want to connect. You can find this value in the management section of your AWS console.
7. Click Next to proceed to the connection detail summary, then click Add VXC.
8. Click Review Order to proceed through the checkout process, or click Save to save the configured services before placing the order.
9. Review the Important Information section and confirm agreement with the Service Agreements. If you do not have a promotion code, skip to the Order Now step. If you do have a promotion code, enter it into the Enter discount code field then click Apply. Alternatively, if a code already appears in the Discounts field, verify it is correct and click Apply. The promotional discount appears below the Standard Term discount. This discount is not reflected in the Monthly Rate shown here, it is applied at the time of billing. If an invalid or expired code causes an error with your order, contact your Megaport Account Manager for a replacement code. If you entered an incorrect promotion code, you can remove it by clicking Remove.
   In addition to entering a promotion code manually, there are two other ways to apply promotion codes.

   • Auto-apply — Megaport automatically applies the promotion code to your order. It appears automatically on the Checkout page.
   • Manual list — Eligible promotion codes appear at checkout for any applicable services in your cart. You can then select and apply them.
10. Click Order Now.

1. In AWS, go to Services > AWS Direct Connect > Connections and click the connection name.
2. Click Accept at the top right of the window. The state will be pending for a few minutes while AWS deploys the connection. After it is deployed, the state changes from ordering to available.

​

Creating a virtual interface

1. In the AWS console, click Create Virtual Interface.
2. Select the interface type. The type will vary depending on the type of service you need to access.
   • Private — Access resources running into a VPC using their private IP addresses. You can choose to terminate a private virtual interface on a private virtual gateway (to access a single VPC) or to a Direct Connect gateway (and map up to 10 VPCs to the VIF).
   • Public — Access all AWS public endpoints, as well as all AWS resources that are reachable by a public IP address.
   • Transit — Transport traffic from a Direct Connect gateway to one or more transit gateways.
3. Specify the configuration details:
   • Virtual interface name — Enter a name for the virtual interface.
   • Connection — The physical connection where you want this virtual interface to be provisioned. The name you provided for the Hosted Connection in the Megaport Portal appears here.
   • Virtual interface owner — The account that will own the virtual interface. Select My AWS account.
   • Direct Connect gateway — Select the Direct Connect gateway to attach this virtual interface to. A transit VIF is not directly attached to a Transit gateway, but to a Direct Connect gateway.
   • VLAN — The VLAN assigned to the virtual interface. Leave this value as is. The VLAN address is populated and appears to be editable; however, you will get an error if you try to change it.
   • BGP ASN — Enter the Border Gateway Protocol (BGP) autonomous system number (ASN) for the MVE side of the BGP session.
   The following BGP details can be filled out or left blank. When left blank, they are auto-populated by AWS. You can also choose whether you want the virtual interface to support Jumbo frames. Enable Jumbo MTU to support an Ethernet packet of 8500 bytes.
4. Click Create virtual interface. To view the VIF details and state, navigate to Services > AWS Direct Connect > Connections > Name of the Megaport-Created-Hosted Connection. BGP hasn’t been configured, so the interface state appears as down.

​

Adding AWS connection details to Aruba Orchestrator

1. Collect the connection details from the AWS console.
   Display the details of the Virtual Interface you created in AWS for this Hosted Connection. Note the values for the BGP ASN, BGP Auth Key, Your Peer IP, and Amazon Peer IP.
2. Collect the connection details from the Megaport Portal. To display the details, click the gear icon for the AWS connection from your MVE and click the Details view. Note the value for the A-End VLAN.
3. Log in to Aruba Orchestrator.
4. Go to Configuration > Networking | Routing | Deployment.
5. Locate the appliance by the hostname and click the Edit (pencil) icon.
6. If you do not have a wan0 LAN side interface: Click +Add next to LAN Interfaces and in the Interface drop-down menu, choose wan0. If you already have a wan0 LAN interface, click +IP to add a new configuration.
7. In the VLAN field, enter the A-End VLAN for the AWS connection (found in the Megaport Portal in Step 2).
8. (Optional) Select a preconfigured Label or select None.
9. In the IP/Mask field, enter the IP address and mask for the MVE side of the AWS connection. This value is the Your Peer IP value from the AWS console from Step 1.
10. For the Next Hop, enter the IP address for the Amazon side of the connection. This value is the Amazon Peer IP value from the AWS console.
11. Specify in and out bandwidth values. The bandwidth must be equal to or less than the MVE bandwidth limit. This image shows sample configuration values.
12. Click Apply.
13. If prompted, reboot the appliance. A reboot is required only when adding the first LAN interface, as the system switches the appliance from server mode to router mode.

1. In Orchestrator, go to Configuration > Networking | Routing | BGP.
2. Click the Edit (pencil) icon for the appliance.
3. Move the slider to Enable BGP.
4. Provide the autonomous system number (ASN). This is the BGP ASN (for the MVE), collected in Step 1.
5. In the Router ID field, enter the loopback 0 IP specified during the initial acceptance of the appliance or another system IP, as required by your network. You can use any IP address on the appliance, such as the interface IP on the MVE side of the VXC or the transit IP address.
6. In the BGP Peers section, click Add and provide the following information:
   • Peer IP — This is the Amazon Peer IP address, collected in Step 1 from the AWS console.
   • Local Interface — Choose the associated LAN interface (the interface is in the format wan0+VLAN).
   • Peer ASN — This is the AWS ASN. By default, this value is 64512.
   • Peer Type — Choose Branch.
   • Enable Password — If required, select this and then enter and confirm your MD5 password.
7. Click Add.
8. Click Apply.

​

Validating your AWS connection

• show interface wan0.<subinterface id> — Displays configuration details and current status for the appliances.
• show bgp neighbors or show bgp summary — Displays configuration details and current status for the BGP neighbors.

1. In Orchestrator, use the mouse to hover over the appliance and click the Appliance Menu icon to the right of the appliance name.
2. Choose CLI Session from the menu.
3. Enter enable mode to use the recommended CLI commands to display configuration details.