Google Cloud Partner Interconnect provides a private, dedicated network connection between your enterprise network and Google Cloud through a supported service provider, replacing the public internet for Google Cloud workloads. IZO™+ Multi Cloud Connect delivers Partner Interconnect as a fully managed service over Tata Communications’ MPLS backbone.
IZO™+ Multi Cloud Connect delivers Google Cloud connectivity as Partner Interconnect (VLAN attachments), over either a Tata Communications-managed direct interconnect (50 Mbps–50 Gbps) or a Interconnection partner-routed path (up to 10 Gbps). Google Cloud Partner Interconnect supports private peering only. Both Layer 3 (BGP) and Layer 2 (L2VPN) service types are available. Tata Communications uses ASN 4755; Google uses ASN 16550. On the default Layer 3 delivery, Tata Communications runs the BGP to Google and Google assigns the VLAN ID and peering IPs; on Layer 2 you run BGP to Google yourself.
How Tata Communications delivers Partner Interconnect
Google Cloud Partner Interconnect uses pairing keys to associate your VLAN attachment with the service provider:
-
In your Google Cloud console, create a Partner Interconnect VLAN attachment, providing the mandatory details: Redundancy (redundant pair or single VLAN), Network (VPC), Region, Cloud Router, a VLAN attachment Name, the IP stack (IPv4 or dual-stack), and the BGP IP allocation method (automatically allocate the link-local range, or specify custom ranges). Google generates a pairing key.
-
Pre-approve (activate) the VLAN attachment and share the pairing key with Tata Communications via the TCˣ Portal. Without customer approval, Tata Communications cannot begin provisioning.
-
Tata Communications provisions the VLAN attachment circuit over its interconnect with Google and activates the pairing key on the partner portal (with partner ASN 4755 on the default Layer 3 delivery).
-
Google automatically assigns the VLAN ID and the BGP peering IP addresses (from a link-local /29); the configuration reflects in your Google Cloud console. There is nothing for you to key in.
-
On the default Layer 3 delivery, BGP comes up between the Tata Communications MPLS PE (ASN 4755) and Google (ASN 16550), and you reach Google Cloud across the Tata Communications L3VPN. (On a Layer 2 delivery, you run BGP from your CPE directly to Google – see GCP L2VPN Services)
Google issues a pairing key ending in /1 (Zone 1) or /2 (Zone 2).
Zone 1 originates from Tata Communications’ primary router port and Zone 2 from the secondary, which is how redundancy is built – see the setup and routing pages. If you choose Create a single VLAN (no redundancy), Google creates the pairing key in either Zone 1 or Zone 2 automatically – you cannot choose which. For a redundant pair, Google issues one /1 (Zone 1) and one /2 (Zone 2) key.
Connection paths
IZO™+ Multi Cloud Connect offers two paths to Google Cloud Partner Interconnect.
|
Capability |
Tata Communications-managed direct |
Interconnection Partner-routed |
|
Bandwidth range |
50 Mbps – 50 Gbps |
50 Mbps – 10 Gbps |
|
20 / 50 Gbps support |
Yes (on 100 Gbps ports) |
Only on a 100 Gbps port or advanced package |
|
Encapsulation |
Dot1Q (C-tag) |
QinQ (S-tag + C-tag) |
|
Peering |
Private only |
Private only |
|
L2VPN service |
Yes |
Yes |
|
L3VPN service |
Yes (BGP private peering) |
Yes (BGP private peering) |
|
Bandwidth changes |
Hot (no teardown) |
In-place on the Interconnection partner exchange |
Choose the direct path for the full bandwidth range up to 50 Gbps and the simplest operational model; choose the Interconnection partner-routed path where the target metro is better served via a Interconnection partner exchange.
Service types: L3 and L2
-
Layer 3 (private peering) – Tata Communications manages BGP with Google over the VLAN attachment. Google offers private peering only; Google assigns the BGP peering addresses, and the service is built using L3VPN topologies (hub-and-spoke or full mesh) so you can reach Google Cloud from your remote sites.
-
Layer 2 (L2VPN) – Tata Communications provides a transparent point-to-point L2VPN tunnel and you manage IP addressing and BGP directly with Google. See GCP L2VPN Services.
Bandwidth and VLAN attachments
Standard bandwidth tiers for the direct path are 50, 100, 200, 300, 400, 500 Mbps and 1, 2, 5, 10 Gbps, with 20 and 50 Gbps available where 100 Gbps ports exist. A 10 Gbps interconnect supports 16 VLAN attachments by default (raised to 25 via the Google Cloud console); a 100 Gbps interconnect supports 75 by default. These are per-port limits, and the quota can be raised further by submitting a quota-increase request to Google. Google permits oversubscription up to 3X. Bandwidth changes are applied without tearing the attachment down.
What’s on the Google Cloud side
These are configured in your Google Cloud console:
-
Creating the VLAN attachment and obtaining the pairing key, choosing the region and IP stack.
-
Creating and configuring the Cloud Router (BGP);
-
VPC route configuration.
The end-to-end walkthrough is documented in full under Provisioning & Configuration.