Skip to content

Creating an AWS Hosted Connection for an MVE with Palo Alto VM-Series

A Hosted Connection can support one private, public, or transit virtual interface. These are dedicated connections and are recommended for production environments.

To create a Hosted Connection 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 Connection as the AWS Connection Type, select the destination port, and click Next.
    You can use the Country filter to narrow the selection.
    Each destination port has either a blue or an orange icon to indicate its diversity zone. To achieve diversity, you need to create two connections with each one in a different zone.
    Add AWS Hosted Connection

  4. Specify the connection details:

    • Connection Name – The name of your VXC to be shown in the Megaport Portal.
    • 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 Associating a Deal With a Service.

    • Rate Limit – This is the speed of your connection in Mbps. The speed cannot be changed once deployed. The drop-down list shows predefined rate limits available for your MVE, up to 10 Gbps.

    • Minimum Term – Select No Minimum Term, 12 months, 24 months, or 36 months. Longer terms result in a lower monthly rate. No Minimum Term is selected by default, which allows you to finalize the configuration of the VXC before locking in a term.
      Take note of the information on the screen to avoid Early Termination Fees (ETF). See VXC Pricing and Contract Terms and VXC, Megaport Internet, and IX Billing for more information.

    • A-End vNIC – Select an A-End vNIC from the drop-down list. See Creating an MVE in the Megaport Portal for more information about vNICs.

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

  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.
      AWS connection details

  7. Click Next to proceed to the connection detail summary, click Add VXC, and order the connection.

Once the VXC connection is deployed successfully, it appears on the Megaport Portal Services page and is associated with the MVE. Click the VXC name to display the details of this connection. Note that the service status (Layer 2) is up but BGP (Layer 3) will be down because the configuration does not exist yet.

VXC details

Once deployed in the Megaport Portal, you need to accept the connection in the AWS console and create a Virtual Interface for the connection:

To accept a Hosted Connection

  1. In AWS, go to Services > AWS Direct Connect > Connections and click the connection name.
    AWS Connections

  2. Click Accept at the top right of the window.
    Accept AWS Connections

    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.

The connection is now available, however you need to create a VIF to connect to AWS services.

Tip

For more information about accepting AWS connections, see the AWS documentation.

Creating a virtual interface

Once you have created and accepted a Hosted Connection, create a VIF and attach the Hosted Connection to a gateway.

Tip

AWS provides detailed instructions for creating Public, Private, and Transit interfaces.

To create and attach a VIF

  1. In the AWS console, click Create Virtual Interface.
    AWS 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. When you select Transit for the VIF, slower connections are filtered and no longer appear in the interface.
      AWS interface type
  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.
    AWS BGP details

    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.
    VIF details

    BGP hasn’t been configured, so the interface state appears as down.

Once you accept the connection and create the VIF in AWS, the VXC state changes to configured in the Megaport Portal.

Adding AWS connection details to VM-Series

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 VM-Series. This involves creating an interface and configuring BGP settings.

To add the AWS connection in VM-Series

  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.
    Connection Details

  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 the VM-Series.

  4. Choose Network > Interfaces.

  5. Click Add Subinterface.

  6. Provide these details:

    • Interface Name – Enter a name for the subinterface. In the adjacent field, enter a number to identify the subinterface.

    • Comment – Enter an alternate name, for example, AWS VIF dxvif-fh9aokej.

    • Tag – Specify the A-End inner VLAN value associated with the AWS VXC you created in the Megaport Portal.

    • Virtual Router – Select a virtual router to the interface, as required by your network.

  7. Select the IPv4 tab.

  8. Select Static as the Type.
  9. Click +Add to add a new IP address.
  10. Enter the IPv4 address and netmask.
    These values are available in the virtual interface details in the AWS console. The IP address and netmask appear in the Your Peer IP field.
  11. Click OK.
  12. Click Commit in the top right corner.
    Commit button
  13. Review the changes and click Commit. Commit changes
    The new VLAN interface appears with your ethernet1/1 physical interface.

Next, you will create a security zone so the interface can route traffic.

To create a security zone

  1. Select the ethernet1/1.1010 subinterface.
  2. Select New Zone from the Security Zone drop-down list.
  3. Specify a name for the security zone.
    Security zone settings
  4. Click +Add under Interfaces and add ethernet1/1.1010 to the security zone.
  5. Specify any additional details as required for your network security.
  6. Select New Zone Protection Profile from the Zone Protection Profile drop-down list.
  7. Specify any details as required for your network security. This example uses all the defaults.
    Zone Protection profile
  8. Click OK.
  9. Click OK in the Layer3 Subinterface screen.
  10. Click Commit in the top right corner.
    Commit button
  11. Review the changes and click Commit. Commit changes

At this point, you have created the interface. Next, you will create the BGP session.

To create the BGP session

  1. In VM-Series, choose Network > Virtual Routers.
  2. Select the virtual router.
    Select virtual router
  3. In the left pane, select BGP.
  4. Provide the following BGP details:

    • Enable – Select this check box to start the BGP session after committing these changes.
    • Router ID – Enter the IP address that appears in the Your Peer IP field for the virtual interface details in the AWS console.
    • AS Number – Provide the ASN for the MVE connection. Use the BGP ASN from the virtual interface details in the AWS console. BGP details
  5. Click +Add under Auth Profiles.

  6. Specify a Profile Name.
    Profile name
  7. Enter and confirm the auth password.
  8. Click OK.
  9. Select the Peer Group tab.
    Peer Group tab
  10. Click +Add to add a peer group.
  11. Specify a name for the peer group. For example, AWS-xxxx.
  12. Specify eBGP as the session type.
  13. Specify any additional details as required for your network.
  14. Click +Add to add a new peer.
  15. Specify the details for the peer:
    • Name – Specify a name for the peer.
    • Peer AS – Specify the Amazon-side Autonomous System Number (ASN). By default this is 64512.
    • Local Address – Select the proper subinterface and IP address from the drop-down list.
    • Peer Address – Enter the AWS side IPv4 address. This is the Amazon Peer IP from the virtual interface details in the AWS console.
      BGP Peer Group screen
  16. Select the Connection Options tab.
    Connection Options tab
  17. Select the previously created Auth Profile.
  18. Click OK in the Peer Group - Peer screen.
  19. Click OK in the BGP - Peer Group/Peer screen.
  20. Click OK in the Virtual Router screen.
  21. Click Commit in the top right corner.
    Commit button
  22. Review the changes and click Commit. Commit changes

Validating the AWS connection

To check the status of the BGP peer

  1. Choose Network > Virtual Routers.
  2. Locate your virtual router (default).
  3. Click More Runtime Stats in the Runtime Stats column on the right.
    Runtime stats
  4. Select the BGP tab, and then select the Peer tab.
  5. Verify that the peer status is Established.
    Established status

    You can also check the status in your AWS Direct Connect portal (this might take a few minutes to refresh).
    AWS status


Last update: 2024-02-14