<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1705902170274878&amp;ev=PageView&amp;noscript=1">
Skip to content
Talk to Us
  • There are no suggestions because the search field is empty.

GCP Partner Interconnect Setup (Direct Interconnect)

IZO™+ Multi Cloud Connect delivers Google Cloud as a Partner Interconnect VLAN attachment that you create in your own Google Cloud console. The ordering journey is the standard IZO™+ Multi Cloud Connect flow, documented in full  under Provisioning & Configuration. This page shows how that flow applies to Google Cloud, and the Google Cloud-side hand-off is the same whether you ordered IZO™+ Multi Cloud Connect Direct or IZO™+ Multi Cloud Connect Flex. 

This page sits alongside the ordering journey rather than repeating it. The TCx Portal steps, that place and provision the connection are common to every IZO™+ Multi Cloud Connect order and live under Provisioning & Configuration. Here we focus on how the flow applies to Google Cloud: creating the VLAN attachment and pairing key and completing the hand-off in your Google Cloud console.  

[Prerequisites: Google Cloud side] : Before placing the order, in your Google Cloud console: have a VPC network and a Cloud Router created and associated in the target region (both are required to create a pairing key). Then create the Partner Interconnect VLAN attachment, setting Redundancy, Network, Region, Cloud Router, a Name, the IP stack (IPv4 or dual-stack) and the BGP IP allocation method (automatically allocate the link-local range, or specify custom ranges). Copy the pairing key and pre-approve (activate) the attachment. Without customer approval, Tata Communications cannot begin provisioning. 

How Google Cloud setup fits together

The end-to-end flow is the standard IZO™+ Multi Cloud Connect order, with the Google Cloud-side hand-off around it:

  1. Create the Partner Interconnect VLAN attachment in the Google Cloud console, copy the pairing key, and pre-approve (activate) the attachment.

  2. Place your IZO™+ Multi Cloud Connect order for Google Cloud in the  TCx Portal (Direct or Flex), sharing the pairing key (for a redundant pair, both the Zone 1 and Zone 2 keys).

  3. Tata Communications provisions the VLAN attachment circuit and activates the pairing key.

  4. Google automatically assigns the VLAN ID and the BGP peering IP addresses.

  5. Routing comes up.

Steps 2 and 3 are covered end to end under Provisioning & Configuration. See the IZO™+ Multi Cloud Connect Direct and IZO™+ Multi Cloud Connect Flex order pages for Google Cloud. This page covers the Google Cloud-side steps around them.

Addressing is assigned by Google

Unlike some other clouds, there is no addressing to retrieve or key in for Google Cloud. Once Tata Communications activates the pairing key, Google automatically assigns the VLAN ID and the BGP peering IP addresses from a link-local range, and the configuration reflects in your Google Cloud console. You do not enter a peer IP, a VLAN ID, or a BGP key on the Google Cloud side. You can track provisioning status in the TCx Portal inventory.

On the Google Cloud side

Because Google Cloud is delivered as a Partner Interconnect VLAN attachment in your own console, the Google Cloud-side hand-off is the same whether you ordered IZO™+ Multi Cloud Connect Direct or IZO™+ Multi Cloud Connect Flex. In your Google Cloud console you:

  • Create the VLAN attachment - Choose Partner Interconnect and "I already have a service provider", set the mandatory fields (Redundancy, Network, Region, Cloud Router, Name, IP stack and BGP IP allocation), and copy the pairing key. Google assigns the VLAN ID; you cannot specify it.

  • Pre-approve (activate) the attachment - Activate the VLAN attachment so Tata Communications can complete provisioning against the pairing key.

  • Let Google bring up the peering - After Tata Communications activates the key, Google assigns the peering addresses and the session comes up.

On the default Layer 3 delivery, Tata Communications runs the BGP to Google (ASN 4755 to Google's ASN 16550) and you reach Google Cloud across the Tata Communications L3VPN, so there is no CPE-to-Google session for you to configure. If your circuit is delivered as Layer 2 (a point-to-point L2VPN), you run BGP from your CPE directly to Google (remote ASN 16550), using the Google-assigned peering addresses.

For a redundant deployment, create two VLAN attachments so Google issues a Zone 1 key (ending /1) and a Zone 2 key (ending /2); Tata Communications terminates these on diversified router ports. If you create a single VLAN (no redundancy), Google assigns the zone automatically and you cannot choose it.

The click-by-click walkthrough is under Provisioning & Configuration.  For the Google Cloud-specific detail on this side, see GCP Routing and BGP Configuration for the routing model, and GCP L2VPN Services for the Layer 2 delivery.

Bandwidth changes

Google supports a hot bandwidth change of a VLAN attachment. Tata Communications applies the change without tearing the attachment down. The per-attachment ceiling and any quota on the number of attachments follow Google's limits, which can be raised by a quota-increase request. See GCP Partner Interconnect Setup via Partner Exchange for the partner-routed path.

Related pages