> ## Documentation Index
> Fetch the complete documentation index at: https://docs.megaport.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating a Google Cloud Services Connection for an MVE with Arista VeloCloud SD-WAN

> This help topic describes how to provision connections between an MVE and Google Cloud Services and integrate the connection with Arista VeloCloud SD-WAN.

export const Image = ({src, alt = '', caption, width, height, shadow}) => {
  const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Image -';
  if (typeof src !== 'string') {
    src = String(src);
  }
  if (!src || src === 'undefined') {
    console.error(`${errorPrefix} \`src\` is required — rendering an empty string instead`);
    return <></>;
  }
  const img = <img className={['mega-image-style', shadow ? 'shadow' : ''].join(' ')} src={src} alt={alt} width={width} height={height} style={{
    display: 'block'
  }} />;
  return caption ? <figure>
      {img}
      <figcaption style={{
    textAlign: 'center',
    width
  }}>{caption}</figcaption>
    </figure> : img;
};

export const Link = ({href, children}) => {
  const errorPrefix = '\x1b[31;1;4mERROR\x1b[0m: Link -';
  if (typeof href !== 'string') {
    href = String(href);
  }
  if (!href || href === 'undefined') {
    console.error(`${errorPrefix} the \`href\` property is required — rendering an empty string instead`);
    return <></>;
  }
  if (href.includes('{') || href.toUpperCase().includes('%7B')) {
    console.error(`${errorPrefix} could not resolve a variable in href "${href}" — rendering an empty string instead`);
    return <></>;
  }
  const isExternal = (/^https?:\/\//).test(href);
  return <a href={href} className="link" target={isExternal ? '_blank' : undefined} rel={isExternal ? 'noreferrer' : undefined}>
      {children ?? href}
      {isExternal && <span className="sr-only"> (opens in a new tab)</span>}
    </a>;
};

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

When connecting to Google Cloud Platform (GCP) through Partner Interconnect with Megaport, 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.

<Callout icon="triangle-exclamation" color="red">
  Before you begin, create an MVE (Edge) in Orchestrator. For more information, see [Creating an MVE](/mve/vmware/creating-mve). The MVE needs to be in the active state.
</Callout>

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](https://cloud.google.com/interconnect/docs/how-to/partner/provisioning-overview).

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

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

These instructions step through the second and third parts.

<Note>
  MVE for Arista VeloCloud SD-WAN requires configuration steps in both Orchestrator and the Megaport Portal for all cloud connections.
</Note>

## Adding the Google Cloud connection in the Megaport Portal

To set up the GCP connection, you need to create the connection in the Megaport Portal.

**To create a connection to GCP from the Megaport Portal**

1. In the <Link href="https://portal.megaport.com">Megaport Portal</Link>, go to the **Services** page and select the MVE for the connection.

2. Click **+Connection** then click **Cloud**.
   <Image src="/images/cloud/mve/vmware/add-connection.png" alt="Add connection" shadow={true} width={700} />

3. Select Google as the provider.

   <Image src="/images/cloud/megaport/google/gc-vxc-config.png" alt="Google as the provider" shadow={true} width={700} />

   <Tip>
     To check the latency and price of connecting to a particular Google location, click **View all Google Partner locations**. You can proceed to the Connection Details page without a pairing key and review the pricing of the selected port. To place an order for a Google connection, you need to provide a pairing key.
   </Tip>

4. Copy and paste the pairing key from the Google Cloud console into the Google Partner Pairing Key field.\
   The relevant Google targets appear based on the region of your GCI Partner connection.

5. Select the target location for your connection then click **Next**.

6. Specify the connection details:

   * **Connection Name** -- The name of your VXC to be shown in the <Link href="https://portal.megaport.com">Megaport Portal</Link>.

   * **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 in Mbps. Enter the same rate you selected for your Google port speed.

   * **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](/connections/shut-down-vxc).

     <Note>
       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.
     </Note>

   * **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](/mve/vmware/creating-mve#creating-mve).

   * **Preferred A-End VLAN** -- 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 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).

     Enable the [Minimum Term Renewal](/portal-admin/auto-renew/#auto-renew) option 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 [VXC Pricing and Contract Terms](/finance/vxc-pricing) and [VXC, Megaport Internet, and IX Billing](/finance/billing-details).

   * **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. Valid values are a-z 0-9 \_ : . / \ -
        * **Value** -- string maximum length 256. Valid values are a-z A-Z 0-9 \_ : . @ / + \ - (space)
     4. Click **Save**.
        If you already have resource tags for that service, you can manage them by clicking **Manage Tags**.
     <Warning>
       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.
     </Warning>

   <Image src="/images/cloud/mve/portal-cloud-create-details.png" alt="Google connection details" shadow={true} width={550} />

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.

   <Image src="/images/snippets/add-promo-code.png" alt="Add Promo Code" shadow={true} width={750} />

   If you entered an incorrect promotion code, you can remove it by clicking **Remove**.

10. Click **Order Now**.

11. Once you have deployed the VXC, go back to your attachment in the Google Cloud Console and activate the attachment and configure BGP.\
    You will be provided your private IP address from Google to configure BGP.  The BGP configuration requires your ASN for the MVE.

<Note>
  The Google ASN will always be 16550.
</Note>

## 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**.
   <Image src="/images/cloud/mve/google-connection-settings.png" alt="Google connection details" shadow={true} width={800} />

2. Collect the connection details from the Megaport Portal.\
   Click the gear icon for the Google connection from your MVE and click the Details view.
   Note the value for the **A-End VLAN**.

3. In Orchestrator, go to Configure > Edges and click the MVE device.
   <Image src="/images/cloud/mve/vmware/orch-select-device.png" alt="Select the Edge" shadow={true} width={600} />

4. Select the **Device** tab and scroll down to the Interface Settings.

5. Click **+Add Subinterface**.
   <Image src="/images/cloud/mve/vmware/orch-add-subinterface.png" alt="Add Subinterface" shadow={true} width={600} />
   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 Portal.
   <Image src="/images/cloud/mve/vmware/orch-select-interface.png" alt="Select Interface" shadow={true} width={400} />
   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.
   <Image src="/images/cloud/mve/vmware/google/orch-interface-gc-settings.png" alt="Subinterface Settings" shadow={true} width={700} />

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

    <Note>
      Adding the subinterface momentarily disrupts the connection.
    </Note>

**To configure BGP for the Google Cloud connection in Orchestrator**

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

2. Select 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.
   <Image src="/images/cloud/mve/vmware/orch-bgp-enable.png" alt="Enable BGP" shadow={true} width={700} />

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.
   <Image src="/images/cloud/mve/vmware/google/orch-bgp-settings-gcp.png" alt="BGP Settings" shadow={true} width={800} />

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.

<Image src="/images/cloud/mve/vmware/google/orch-bgp-summary-gcp.png" alt="BGP Settings" shadow={true} width={800} />

You can also check connectivity and BGP status from the CLI of the edge device. For more information, see [Reviewing your Arista VeloCloud MVE connection settings](/cloud/mve/vmware/generic/mve-vxc-details).