Requesting Connections

After you create partner VLAN attachments, request connections from a 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 a connection, reach out to your service provider or visit their portal.

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 you select must be supported by a Partner Interconnect location, which is a city where the service provider's network meets Google's network. Traffic between your 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 cloud workloads. Each partner location supports only some regions. Check with your partner to determine what regions each partner location supports.
  • Your VLAN attachment's connection capacity, which 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. You'll receive an email notification after they complete the configuration, and the state of your attachment changes from PENDING_PARTNER to PENDING_CUSTOMER or ACTIVE (if you pre-activated your attachment).

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. You can't modify these Googled-defined configurations, but you can delete them if you delete your attachment.

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.

What's next?