Skip to content

Creating a Google Cloud Services Connection for an MVE with VMware SD-WAN

You can create a network connection from an MVE (VMware Edge) to Google Cloud through Partner Interconnect.

When connecting to Google Cloud Platform (GCP) through Partner Interconnect with Megaport ONE, the Virtual Cross Connect (VXC) forms the Layer 2 component of the connection and Layer 3 BGP is established directly between the customer and GCP.


Before you begin, create an MVE (Edge) in Orchestrator. For details, see Creating an MVE Integrated with VMware. The MVE needs to be in the active state.


Google Cloud requires BGP multihop support, which is first supported in VMware SD-WAN 4.3. If needed, you can upgrade the VMware version on the MVE through the VMware console.

There are three parts to adding a Google Cloud connection to your MVE and Orchestrator.

  1. Create a Partner Interconnect attachment in Google Cloud Console or gcloud CLI. Copy the pairing key that is provided as part of the attachment creation. For additional details, see the Google documentation on Google Partner Interconnects.

  2. In the Megaport ONE Portal, create a VXC from your MVE to connect to your Google Cloud attachment.

  3. In VMware Orchestrator, create a new interface and add the details of the Google Cloud connection.

These instructions step through the second and third parts.


MVE for VMware SD-WAN requires configuration steps in both VMware Orchestrator and the Megaport ONE Portal for all cloud connections.

Adding the Google Cloud connection in the Megaport ONE Portal

To set up the GCP connection, you need to create the connection in the Megaport ONE Portal. If you haven’t already created an MVE, see Creating an MVE Integrated with VMware.

To deploy a VXC to Google Cloud Platform from the Megaport ONE Portal

  1. In the Megaport ONE Portal, choose Networking > Services.
  2. Click the gear icon Gear icon next to the MVE you want to use.
  3. Select Add Connection.
    Add Connection

  4. Specify the General connection details:

    • Connection Type – Select Cloud VXC.
    • Cloud Provider – Select Google Cloud. New Connection
  5. Specify the Google Configuration details:

    • Google Partner Pairing Key – Copy and paste the pairing key from the Google Cloud console. The relevant Google targets appear based on the region of your GCI Partner connection.
    • Available Google Ports – Select the target location for your connection.
      Google as the provider
  6. Specify the VXC Configuration details:

    • Connection Name – The name of your VXC to be shown in the Megaport ONE Portal.
    • Rate Limit – The speed of your connection in Mbps. The speed cannot be changed once deployed. Enter the same rate you selected for your Google port speed.
    • A-End VLAN – This is the VLAN for this connection that you will receive through the MVE. 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 ONE will assign one.
  7. Specify the Billing Details:

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


      Partner-managed accounts can apply a Partner Deal to a service.

    • Monthly Price – The monthly rate is based on location and size.

    • Promo Code – If you have a promotional code, enter it and click Add Code.

  8. Click Create Connection.

  9. Review the new configuration and pricing then click Confirm.

  10. After you have deployed the VXC, go back to your attachment in the Google Cloud Console and accept it.
    You will be provided your private IP address from Google to configure BGP.
    Ensure that you pre-activate the attachment or mark the attachment as active after configuring the VXC. Otherwise, you cannot set up BGP with your SD-WAN instance.


The Google ASN will always be 16550.

Adding Google Cloud connection details to Orchestrator

After you create the connection from your MVE to Google Cloud and set up the connection in the Google console, you need to configure it in Orchestrator. This involves configuring BGP settings, ASNs, and VLANs.

To add the Google Cloud connection in Orchestrator

  1. Collect the connection details from the Google console.
    Display the details of the connection you created in Google Cloud for this connection. Note the values for the Peer ASN, Cloud Router BGP IP, and BGP Peer ID.
    Google connection details

  2. Collect the connection details from the Megaport ONE Portal.
    Click the gear icon Gear icon for the Google connection from your MVE, select Edit, then select the Details tab. Note the value for the A-End VLAN.

  3. In Orchestrator, go to Configure > Edges and click the MVE device.
    Select the Edge

  4. Click the Device tab and scroll down to the Interface Settings.

  5. Click +Add Subinterface.
    Add Subinterface
    The Select Interface dialog box appears.

  6. From the Select Interface menu, choose GE3 and for the Subinterface ID enter the A-End VLAN ID configured on the MVE in the Megaport ONE Portal.
    Select Interface
    The subinterface settings appear.

  7. Change the Addressing Type to Static and provide the IP Address, CIDR value, and Gateway.
    These values are available in the VLAN attachment details in the Google Cloud console. The IP address appears in the BGP Peer ID field; the Gateway appears in the Cloud Router BGP IP field.
    Subinterface Settings

  8. Ensure Enable VLAN Tagging is enabled.
    The field is automatically populated with the VLAN ID you specified for the subinterface ID.

  9. Click Update GE3:vlan-id.

  10. In the upper-right corner of the Configure > Edges window, click Save Changes and then confirm.
    This configures the interface, VLAN tags, and IP addresses, which you can test with ping commands through the CLI. (BGP is not yet configured.)


    Adding the subinterface momentarily disrupts the connection.

To configure BGP for the Google Cloud connection in Orchestrator

  1. In Orchestrator, go to Configure > Edges and click the MVE device.

  2. Click the Device tab and in the Configure Segments section click Enable Edge Override for BGP Settings.
    This override lets us define BGP values specific for this device beyond the profile definition.
    Enable BGP

  3. Click the toggle button to turn on BGP and click Edit.
    The BGP Editor appears.

  4. For Local ASN, add the Peer ASN that you defined in the BGP configuration for the VLAN attachment in the Google Cloud console.

  5. For the Neighbor IP, add the Cloud Router BGP IP from the VLAN attachment details in the Google Cloud console.

  6. Add the Google Cloud ASN of 16550 to the ASN field for the neighbor.
    This is a fixed value from Google Cloud.
    BGP Settings

  7. Click OK and then click Save Changes.

Validating your connection

Under Test & Troubleshoot > Remote Diagnostics, select the MVE and click Run for Troubleshoot BGP - Show BGP Summary to verify the BGP session and ensure the Google Cloud Router is up.

BGP Settings

You can also check connectivity and BGP status from the CLI of the edge device. For details, see Reviewing your VMware MVE connection settings.

Last update: 2023-09-22