This page provides important terms that apply to Cloud Interconnect. Review these terms to better understand how Cloud Interconnect works.
For more information, see the Cloud Interconnect overview.
Cloud Interconnect terms
The following key terminology describes the concepts on which Cloud Interconnect is built. These terms might apply to Dedicated Interconnect, Partner Interconnect, or both.
For Dedicated Interconnect, a colocation facility is where Google has a point of presence, allowing you to connect your on-premises network with Google's network. In the colocation facility, work with the facility provider to provision your routing equipment before using Dedicated Interconnect. For a list of facilities and their supported regions, see Choosing colocation facility locations.
For Partner Interconnect, supported service providers are connected to Google in at least one of these facilities.
Each metropolitan area has at least two zones called edge availability domains. These domains provide isolation during scheduled maintenance, meaning that two domains in the same metro won't be down for maintenance at the same time. This isolation is important when you're building for redundancy.
Edge availability domains span a single metro, not across metros. To maintain
availability and an SLA,
you must build duplicate Interconnect connections in different domains in the same metro.
For example, building connections in
dfw-zone2-4 provides redundancy across different edge availability
do not because they are in the same edge availability domain.
Maintenance windows are not coordinated across metros. For example, the edge
could experience overlapping maintenance events. When connecting to multiple metros for
redundancy, it is important to connect to different edge availability domains in each of those
metros, as described in the
A Letter of Authorization and Connecting Facility Assignment (LOA-CFA) identifies the connection ports that Google has assigned for your connection, and grants permission for a vendor in a colocation facility to connect to them. LOA-CFA documents are required when you order Dedicated Interconnect connections in a colocation facility.
When you order Dedicated Interconnect connections, Google allocates resources
for your connections and then generates an LOA-CFA document for each one. The LOA-CFA
lists the demarcation points that Google allocated for your connections.
Submit this form to the facility vendor to provision cross-connects between
Google's equipment and your own. After the status of a connection changes
PROVISIONED, the LOA-CFA is no longer valid, necessary, or available
in the Google Cloud Console.
For more information about the provisioning flow, see the Dedicated Interconnect Provisioning overview.
A metropolitan area (metro) is the city where a colocation facility is located. When you create an Interconnect connection, you select the colocation facility and metro where the connection lives.
The metro that you choose depends on the location of your on-premises network and the location of your Compute Engine VM instances (their Google Cloud region). Typically, you might want to pick a metro that's geographically close to your on-premises network to reduce latency. For redundancy, you might choose a metro that is further away.
In regards to the Google Cloud region, each metro supports a subset of regions. You can create interconnect attachments (VLANs) in these supported regions only. For example, if you pick a facility in Ashburn, you can only create interconnect attachments in the North American regions. Assuming that your VM instances are also in these regions, you can create interconnect attachments in the same regions to reduce latency and egress costs. Otherwise, traffic would have to travel between regions to reach your VM instances or on-premises network.
For more information, see Choosing colocation facility locations.
Pairing keys are used only for Partner Interconnect. It's a unique identifier that allows service providers to identify particular interconnect attachments without anyone sharing potentially sensitive information about their VPC network or Google Cloud project. Treat the pairing key as sensitive information until your interconnect attachment is configured. If it's discovered, it's possible for other parties to use it to connect to your network. The key is for one-time use and can't be modified. If you need a new pairing key, delete your interconnect attachment and then create a new one.
Pairing keys use the following format:
a pairing key for an interconnect attachment (VLAN) in the
region and edge availability domain
Border Gateway Protocol (BGP) terms
The following terminology applies to the Border Gateway Protocol (BGP), which Cloud VPN and Cloud Interconnect use for dynamic routing.
Google Cloud terms
The following terminology applies to Google Cloud and its features.