Dedicated Interconnect provisioning overview

This page describes the steps to successfully create and configure a Dedicated Interconnect connection.

To create and configure an Interconnect connection, follow these steps:

  1. Order a Dedicated Interconnect connection

    Submit an order, specifying the details of your Interconnect connection. Google then emails you an order confirmation. After your resources have been allocated, you receive another email with your LOA-CFAs.

  2. Retrieve LOA-CFAs

    Send the LOA-CFAs to your vendor. They provision the connections between the Google peering edge and your on-premises network. Google automatically starts testing the light levels on each allocated port after 24 hours.

  3. Test the connection

    Google sends you automated emails with configuration information for two different tests. First, Google sends an IP address configuration to test light levels on every circuit in an Interconnect connection. After those tests pass, Google sends the final IP address configuration to test the IP connectivity of each connection's production configuration.

    Apply these configurations to your routers so that Google can confirm connectivity. If you don't apply these configurations (or apply them incorrectly), Google sends an automated email with troubleshooting information. After all tests have passed, your Interconnect connection is ready to use.

  4. Create VLAN attachments

    When your Interconnect connection is ready to use, you need to connect Virtual Private Cloud (VPC) networks to your on-premises network. To do that, first create a VLAN attachment, specifying an existing Cloud Router that's in the VPC network that you want to reach.

  5. Configure on-premises routers

    After you create a VLAN attachment, to start sending traffic between networks, you need to configure your on-premises router to establish a BGP session with your Cloud Router. To configure your on-premises router, use the VLAN ID, interface IP address, and peering IP address provided by the VLAN attachment.

What's next