Creating an AWS Hosted VIF for an MVE with Versa Secure SD-WAN

Hosted VIFs can connect to public or private AWS cloud services: a Hosted VIF cannot connect to a transit virtual interface. These connections share bandwidth.

To create a Hosted VIF from an MVE to AWS

  1. In the Megaport Portal, go to the Services page and select the MVE for the connection.

  2. Click +Connection and click Cloud.

  3. Select AWS as the service provider, select Hosted VIF as the AWS Connection Type, select the destination port, and click Next.
    You can use the Country filter to narrow the selection.
    Add Hosted VIF connection

  4. Specify these connection details:

    • Connection Name – The name of your VXC to be shown in the Megaport Portal. (Tip – match this to the AWS Connection Name on the next screen for easy mapping.)
    • Service Level Reference (optional) – Specify a unique identifying number for the 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. You can also edit this field for an existing service.

    Note

    Partner managed accounts can apply a Partner Deal to a service. For details, see Applying a Deal to a Service.

    • Rate Limit – This is the speed of your connection in Mbps. Accepted values range from 1 Mbps to 5 Gbps in 1 Mbps increments. Note the sum of all hosted virtual VXCs to a service can exceed the MVE capacity, but the total aggregate will never burst beyond the MVE capacity.
    • Preferred A-End VLAN – Optionally, 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.
      Connection details
  5. Click Next.

  6. Specify the details for the AWS service. AWS connection details

    Here are details for each field:

    • Select Public or Private.
      Private – Access private AWS services such as a VPC, EC2 instances, load balancers, RDS DB instances, on private IP address space.
      Public – Access public AWS services such as Amazon Simple Storage Service (S3), DynamoDB, CloudFront, and Glacier. You’ll also receive Amazon’s global IP prefixes (approximately 2,000 prefixes).
      Note: Public VIFs require manual intervention from Amazon and could take up to 72 hours.

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

    • Customer ASN – An optional field, specifies the ASN used for BGP peering sessions on any VXCs connected to the MVE. This value is defined when you configure the MVE and, once defined, it cannot be changed.

    • BGP Auth Key – An optional field to specify the BGP MD5 key. If you leave this blank, Megaport negotiates a key automatically for you with AWS, and displays the key in the Megaport Portal. (The key is not displayed in the AWS console.)

    • Customer IP Address – The IP address space (in CIDR format) used on your network for peering. This field is optional for private connections and if left blank, Megaport assigns an address.

    • Amazon IP Address – The IP address space in CIDR format assigned in the AWS VPC network for peering. This field is optional for private connections and if left blank, Megaport automatically assigns an address.

    • Prefixes – (visible for Public connections only) An optional field for IP Prefixes to announce to AWS. Specify the prefixes you will advertise when deploying a Public Direct Connect (RIR-assigned IPv4 addresses only).

      Once you configure Prefixes for a Public connection, you cannot change them and the field is dimmed. To change this value, create a support ticket with AWS so they can make this change in a non-impacting way. Or, you can cancel the Hosted VIF and reorder. In both cases, you need to wait for AWS to manually approve the request.

  7. Click Next to proceed to the connection detail summary, add the VXC to the cart, and order the connection.

The AWS VXC appears as a connection for the MVE in the Megaport Portal.

VXC details

Next, accept the connection in AWS.

Accepting the Virtual Interface for Private Connections

A few minutes after ordering a private Hosted VIF VXC, the corresponding inbound VIF request is visible on the AWS Direct Connect > Virtual Interfaces page in the AWS console. (This is specific to the region associated with the target AWS port.) If your VIF doesn’t appear after a few minutes, confirm you are viewing the correct region.

To review and accept the private virtual interface

  1. From the AWS Direct Connect > Virtual Interfaces page, click the ID of the interface to display the configuration and peering details.
    Accepting AWS Virtual Interfaces

    The name and account ID of the VIF should match the values supplied in the Portal and the BGP ASN should match the Customer ASN configured with the VXC. The Amazon ASN is the default region’s AWS ASN and not the value specified during the configuration - this is updated when the virtual interface is accepted and assigned.

  2. Click Accept.

  3. Select the gateway type and then the specific gateway for this new virtual interface.
    Specify a gateway

  4. Click Accept virtual interface.

The state of the connection changes from confirming to pending, and then changes to available once BGP is established. Note that sometimes there is a delay in the available BGP status appearing on the AWS end, though you can confirm the current state of the Layer 3 link through the Portal view.

Accepting the Virtual Interface for Public Connections

Several minutes after ordering a public Hosted VIF VXC, the corresponding inbound VIF request appears on the AWS Direct Connect > Virtual Interfaces page in the AWS console. (This is specific to the region associated with the target AWS port.)

To review and accept the public virtual interface

  1. From the AWS Direct Connect > Virtual Interfaces page, click the ID of the interface to display the configuration and peering details.
  2. Review the configuration details and click Accept, and when prompted, click Confirm.

The state of the connection changes from confirming to verifying. At this point, the connection needs to be verified by Amazon - a process that can take up to 72 hours. When verified, the state changes to available.

Adding AWS connection details to Versa Director

After you create the connection from your MVE to AWS and set up the connection in the AWS console, you need to configure it in Versa Director. This involves revising Versa Director templates to add a device interface and configure BGP settings, ASNs, VLANs, and MD5 values.

To add a subinterface in Versa Director

  1. Collect the connection details from the Megaport Portal.

    To display the details, click the Gear icon Gear icon for the AWS connection from your MVE and click the Details view. Note the values for the A-End VLAN, Customer Address (and CIDR), Amazon IP Address, and Customer ASN.

    AWS connection details

  2. Log in to Versa Director.

  3. Select the Workflows tab in the top menu bar.

  4. Select Template > Templates in the left navigation.

    Choose template

  5. Click the template you want to edit, then select the Interfaces tab.

  6. In the WAN Interfaces section, locate the Sub Interface column and click the Add icon Add icon to add a subinterface.

    Add a subinterface

    A new row appears in the table.

  7. Specify these values for the new subinterface.

    • VLAN ID - Enter the VLAN value from the Megaport Portal.

    • Network Name - Choose + Create WAN Network from the dropdown menu to open the Create WAN Network window. Specify a meaningful name for the network, click OK, and then select the WAN network you created.

    • IPv4 - Choose Static from the dropdown menu.

    Subinterface details

  8. Select the Routing tab to add BGP configuration information.

  9. In the BGP section, select the network name for the connection in the Network column.

    BGP details

  10. Specify the following values according to your MVE configuration:

    • Local AS - This is the Customer ASN (your local MVE), collected in Step 1.
    • Neighbor IP Address - This is the Amazon IP address, collected in Step 1.
    • Peer AS - This is the AWS ASN. By default, this value is 64512.
    • Optionally, you can enable BFD (as appropriate for your network).
  11. Click the Add icon Add icon to the right of the settings.

  12. Click Recreate (at the bottom of the page).

    A window opens that shows the differences of the configuration. The auto-merged version is recommended, and selected by default.

  13. Click Deploy.

You can use variables in the template to specify values per device for these fields: Router ID, Local AS, Peer AS, Static IP address, and Password.

Note

The Instance ID cannot be modified (the system automatically specifies a value) and Static IP Address is parameterized by default.

To parameterize Router ID, BGP Local AS, Peer AS, and Password

  1. Select the Configuration tab in the top menu bar.

  2. Select Templates > Device Templates in the horizontal menu bar.

    Device Templates

  3. Click your template.

    By default, the Interfaces column appears.

  4. In the left navigation, select Virtual Routers, and click your device to open the Edit window.

    Edit device templates

  5. In the Edit window, select BGP, then click the Instance ID to open the Edit BGP Instance window.

    Edit BGP Instance window

  6. In the Edit BGP Instance window, click the Parameterize icon Parameterize icon next to each of the following fields: Router ID, Local AS, Peer AS, and Password.

    Parameterize fields

  7. Click OK two times to update.

  8. Select the Workflows tab in the top menu bar, then select Devices > Devices in the left navigation.

  9. Click your device to specify values for the variables you just created.

    Define variables

    The Add Device window opens.

  10. Select the Bind Data tab.

    Bind Data tab

  11. Specify values for the variables.

    • Local AS - Enter the Customer ASN.
    • Password - Enter the MD5 password.
    • Peer AS - Enter the Amazon side ASN.
    • Router ID - Enter the Customer IP address (your local IP address).
    • Hop Address - Enter the Amazon IP address.
    • Static Address - Enter the Customer IP address (your local IP address, including the mask value).
  12. Click Redeploy when finished.

    When the new configurations for the device are prepared successfully, a green checkmark appears at the bottom of the Versa Director window.

  13. To push the changes to the device, click Commit Template (on the upper right).

    Commit Template link

    The Commit Template to Devices window opens.

    Commit Template

  14. Specify the following in the Commit Template to Devices window:

    • Organization - Select your organization from the dropdown menu.

    • Select Template - Select the template to push to the device from the dropdown menu.

    Note that the Template State is OUT_OF_SYNC.

  15. Click the eye icon in the Differences column to verify your configuration changes.

  16. Click Commit to Device.

    A green checkmark appears at the bottom right of the screen when the push is successful. The Template State is now IN_SYNC.

  17. Close the window.

Validating your AWS connection

  1. Select the Monitor tab in the top navigation bar, select Devices in the horizontal navigation bar, and then select your device to view details in the Summary screen.

    AWS Session Status

  2. In the Summary screen you can review your subinterface in the Interface column, and the Operational and Admin Status.

    AWS Session Summary

  3. In the AWS Direct Connect portal, refresh the screen and verify that the Virtual interface state is available and BGP Status is up. An AWS BGP session that is up looks like this:

    AWS session from AWS side

To view the BGP status for a device in Versa Director

  1. Log in to Versa Director.

  2. Select the Monitor tab in the top menu bar.

  3. Select your device from the list.
    Director device list

  4. Scroll to the Health Monitor.

  5. Click BGP Adjacencies to view the BGP status.
    Health Monitor

  6. Verify whether the BGP status for the device is Established.
    BGP details


Last update: