After you create VLAN attachments for a Partner Interconnect connection, you can request connections from a supported service provider with whom you already have connectivity. The service provider must configure your VLAN attachments before the attachments can start passing traffic. To request an Interconnect connection, contact your service provider or visit their portal.
For definitions of terms used on this page, see Cloud Interconnect key terms.
To help you solve common issues that you might encounter when using Partner Interconnect, see Troubleshooting.
When you request a connection, your service provider requires the following information:
Your VLAN attachment's pairing key. This pairing key is generated when you create the VLAN attachment.
The VLAN attachment's region. The region that you select must be supported by a Partner Interconnect location, which is a city where the service provider's network meets Google Cloud's network. Traffic between your Virtual Private Cloud (VPC) network and the service provider's network passes through this location. Typically, you would choose a location that's close to your data center to reduce the latency to your Google Cloud workloads.
Each service provider location supports only some regions. Check with your service provider to determine which regions each location supports.
Your VLAN attachment's connection capacity. This capacity can range from 50 Mbps to 50 Gbps. The capacity depends on your bandwidth requirements and what's offered by your service provider. Also, pricing for each VLAN attachment is based on its capacity.
After you request a connection, wait until the service provider completes the
VLAN attachment configuration. After their configuration is complete, you
receive an email notification from Google. The state of your attachment changes
PENDING_CUSTOMER. If you
attachment, it changes to
If you pre-activated your VLAN attachment and are using a Layer 3 connection, the attachment can immediately start passing traffic. If not, you must activate the attachment before it can pass traffic.
When your service provider completes the VLAN attachment configuration, Google automatically configures an interface and a BGP peering session on the associated Cloud Router. Do not modify these Google-defined configurations because doing so shuts down the BGP session. However, if you delete your attachment, you can delete these configurations.
For Layer 3 connections, the service provider supplies their ASN, which is automatically added to your Cloud Router's BGP session and allows BGP to establish a session.