Key terms

This page provides key terminology that applies to Network Connectivity products. Review these terms to better understand how each product works.

Google Cloud terms

The following terminology applies to Google Cloud and its features.

Google Cloud
Google Cloud is a suite of public cloud computing services offered by Google. For more information, see Google Cloud products.
project ID
The ID of your Google Cloud project. A project contains networking resources such as networks, subnets, and Cloud VPN gateways as described in the VPC network overview. For a description of the difference between project name, project ID, and project number, see Identifying projects. You can view the project ID in the Google Cloud Console.

Cloud VPN terms

The following terms apply to Cloud VPN gateways and tunnels as well as gateways on your peer network.

Cloud VPN gateway
A virtual VPN gateway running in Google Cloud managed by Google, using a configuration that you specify in your project, and used only by you. Each Cloud VPN gateway is a regional resource that uses one or more regional external IP addresses. A Cloud VPN gateway can connect to a peer VPN gateway.
Classic VPN
The predecessor to HA VPN. For more information, see Types of Cloud VPN.
HA VPN
Replaces Classic VPN with a gateway that provides a 99.99% availability SLA. For more information, see Types of Cloud VPN.
external VPN gateway
A gateway resource that you configure in Google Cloud for HA VPN that provides information to Google Cloud about your peer VPN gateway or gateways. Depending on the high availability recommendations from your peer VPN gateway vendor, you can create an external VPN gateway resource for the different types of peer VPN gateways described in Cloud VPN topologies.
peer VPN gateway
A gateway that is connected to a Cloud VPN gateway. A peer VPN gateway can be one of the following:
  • Another Cloud VPN gateway
  • A VPN gateway hosted by another cloud provider such as AWS or Microsoft Azure
  • An on-premises VPN device or VPN service
remote peer IP address

For an HA VPN gateway interface that connects to an external VPN gateway, the remote peer IP address is the IP address of the interface on the external VPN gateway that is used for the tunnel.

For an HA VPN gateway interface that connects to another HA VPN gateway, the remote peer IP address is the IP address of the other HA VPN gateway's interface that is used for the tunnel.

For Classic VPN, the remote peer IP address is the public IP address of the peer VPN gateway.

VPN tunnel
A VPN tunnel connects two VPN gateways and serves as a virtual medium through which encrypted traffic is passed. Two VPN tunnels must be established to create a connection between two VPN gateways: each tunnel defines the connection from the perspective of its gateway, and traffic can only pass after the pair of tunnels is established. A Cloud VPN tunnel is always associated with a specific Cloud VPN gateway resource.
connection
As defined for Google Cloud, a logical link between Cloud VPN and peer VPN locations as identified by a vpnGateway resource at one end, and an externalVpnGateway or another Google Cloud VpnGateway resource at the peer end. A connection also includes all of the vpnTunnel resources and BGP sessions between the gateway resources.
Internet Key Exchange (IKE)
IKE is the protocol used for authentication and to negotiate a session key for encrypting traffic.

Cloud Interconnect terms

The following key terminology describes the concepts on which Cloud Interconnect is built. Each section indicates whether a term applies to Dedicated Interconnect, Partner Interconnect, or both.

Cloud Interconnect elements

Interconnect connection (Dedicated Interconnect)

A specific physical connection between Google and your on-premises network. This connection exists in a colocation facility where your on-premises network and Google's network meet.

A single connection can be a single 10-Gbps link, a single 100-Gbps link, or a link bundle. If you have multiple connections to Google at different locations or to different devices, you must create separate Interconnect connections.

connection type
A Dedicated Interconnect connection or a Partner Interconnect connection.
VLAN attachment (Dedicated Interconnect and Partner Interconnect)

Also known as an interconnect attachment, or interconnectAttachment resource in the Compute Engine API, a VLAN (virtual local area network) attachment is a logical connection between your on-premises network and a single region in your Virtual Private Cloud (VPC) network.

When you create a VLAN attachment, you associate it with a project, a region, an existing or new Cloud Router, and an existing Interconnect connection. Cloud Router then establishes a point-to-point Border Gateway Protocol (BGP) session over the attachment to your on-premises router.

  • For Dedicated Interconnect, the VLAN attachment uses a dedicated connection that you create to your on-premises router.
  • For Partner Interconnect, the attachment uses a connection that your chosen partner sets up and manages.

Although a VLAN attachment used with Dedicated Interconnect or Partner Interconnect is not directly associated with a VPC network, it is indirectly tied to a single network because a Cloud Router can only be associated with a single VPC network. Therefore, the VLAN attachment is tied to the network that its Cloud Router is located in.

For Dedicated Interconnect

A VLAN attachment for Dedicated Interconnect allocates a single 802.1Q VLAN on your Dedicated Interconnect connection and connects it to a specific VPC network. Because each connection for Dedicated Interconnect supports multiple VLAN attachments, you can access multiple VPC networks without creating multiple connections.

Each attachment that you create is associated with a VPC network and a Google Cloud region:

  • When you associate an attachment for Dedicated Interconnect with a VPC network, this network must be in a project in the same organization as the project that contains the Interconnect connection.
  • The set of valid regions for an attachment depends on the colocation facility used by the Cloud Interconnect.

You can set the capacity of each attachment. For a list of capacities, see the Pricing page. The default attachment capacity is 10 Gbps.

The capacity setting limits the maximum bandwidth that an attachment can use. If you have multiple attachments on a single Interconnect connection, the capacity limitation might be helpful in cases where you want to prevent network congestion on your connection. The maximum bandwidth is approximate, so it's possible for an attachment to use more bandwidth than the selected capacity.

Because the capacity setting only limits the egress bandwidth from Google Cloud to the colocation facility for the Interconnect connection, we recommend that you configure an egress rate limiter on your router for your connection. Configuring this limiter enables you to cap the maximum ingress bandwidth to your VPC network for traffic using that connection.

For Partner Interconnect

To request Partner Interconnect connectivity from a service provider, you create a VLAN attachment in your Google Cloud project. The VLAN attachment generates a unique pairing key that you share with your service provider. The service provider uses the pairing key, along with your requested connection location and capacity, to complete the configuration of your VLAN attachment.

After your service provider configures the attachment, they allocate a specific 802.1q VLAN on your on-premises connection.

Cloud Router (Dedicated Interconnect and Partner Interconnect)

Cloud Router uses Border Gateway Protocol (BGP) to dynamically exchange routes between your VPC network and your on-premises network. Before you can create a VLAN attachment, you must create or use an existing Cloud Router in the VPC network that you want to connect to. You then associate the attachment with this Cloud Router. The Cloud Router creates a BGP session that connects to your on-premises (peer) router.

For detailed information about Cloud Router, see the overview.

The BGP configuration of the Cloud Router depends on whether you're using layer 2 or layer 3 connectivity. Dedicated Interconnect uses only layer 2 connectivity. Partner Interconnect can use layer 2 or layer 3 connectivity.

  • For layer 2, you establish a BGP session between your Cloud Router and your on-premises router.
  • For layer 3, your service provider establishes a BGP session between your Cloud Router and their edge router. For more information, see Layer 2 versus layer 3 connectivity.

Cloud Router advertises subnets in its VPC network and propagates learned routes to those subnets. Unless you configure custom route advertisements, Cloud Router advertises the following routes:

  • If your VPC network uses regional dynamic routing mode, Cloud Router advertises subnet routes in the region where it is located.
  • If your VPC network uses global dynamic routing mode, Cloud Router advertises subnet routes in all regions.

Cloud Router also creates custom dynamic routes in your VPC network for destinations that it learns from your on-premises (peer) router. According to the dynamic routing mode of the VPC network (regional or global), Cloud Router makes those routes available to only the Cloud Router's region or to all regions.

Cloud Interconnect locations

Interconnect connection location or colocation facility (Dedicated Interconnect, with notes for Partner Interconnect)

The colocation facility where a physical Interconnect connection is provisioned. This location is where your on-premises routing equipment meets Google's peering edge.

A colocation facility is where Google has a point of presence (PoP), enabling you to connect your on-premises network with Google's network. In the colocation facility, you work with the facility provider to provision your routing equipment before using Dedicated Interconnect.

Each Interconnect connection location supports a subset of Google Cloud regions. For example, lga-zone1-16 supports VLAN attachments in the regions northamerica-northeast1, us-east1, us-west1, us-west2, us-east4, and us-central1.

For a list of all locations and their supported regions, see Choosing colocation facility locations.

When using Partner Interconnect, partners have already set up connections to Google's network. The set of locations varies, depending on which partner you choose. When you set up your VLAN attachment, you can select from the partner's available locations. For a list of locations that each service provider supports, see the Service providers page.

Each partner location supports a subset of Google Cloud regions. These supported regions are where you can connect to your Cloud Routers and associated VLAN attachments. For example, if you choose the Ashburn location, you can reach all the North American regions, such as us-east1 and us-west1. For a list of Google Cloud regions, see the Regions and zones page.

service provider (Partner Interconnect)

A network service provider for Partner Interconnect. To use Partner Interconnect, you must connect to a supported service provider. The service provider provides connectivity between your on-premises network and your VPC network.

metropolitan area (metro) (Dedicated Interconnect or Partner Interconnect)

The city where a colocation facility is located.

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. When configuring a redundant connection, you might choose an additional metro that is further away.

Each metro supports a subset of Google Cloud regions. You can create VLAN attachments only in these supported regions. For example, if you pick a facility in Ashburn, you can only create VLAN attachments in the North American regions. Assuming that your VM instances are also located in these regions, you can create VLAN attachments in the same regions as your VMs 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.

metro availability zone (Dedicated Interconnect or Partner Interconnect)

An older term for edge availability domain.

edge availability domain (Dedicated Interconnect or Partner Interconnect)

Each metropolitan area has at least two zones called edge availability domains. These domains provide isolation during scheduled maintenance, which means that two domains in the same metro are not 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 edge availability domains in the same metro. For example, building connections in dfw-zone1-4 and dfw-zone2-4 provides redundancy across different edge availability domains, whereas building them in dfw-zone1-4 and dfw-zone1-505 does not because they are in the same edge availability domain.

Maintenance windows are not coordinated across metros. For example, the edge availability domains dfw-zone1-4 and ord-zone1-7 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 production topology.

Provisioning and configuration

Letter of Authorization and Connecting Facility Assignment (LOA-CFA) (Dedicated Interconnect)

An LOA-CFA identifies the connection ports that Google has assigned for your Dedicated Interconnect 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 to 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.

pairing key (Partner Interconnect)

A unique identifier that lets service providers identify particular VLAN attachments without anyone sharing potentially sensitive information about their VPC network or Google Cloud project. Pairing keys are used only for Partner Interconnect.

Treat the pairing key as sensitive information until your VLAN 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 VLAN attachment and create a new one.

Pairing keys use the following format:
<random>/<vlan-attachment-region>/<edge-availability-domain>.

For example, 7e51371e-72a3-40b5-b844-2e3efefaee59/us-central1/2 is a pairing key for a VLAN attachment in the us-central1 region and edge availability domain 2.

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.

Border Gateway Protocol (BGP)
An exterior gateway routing protocol standardized by the Internet Engineering Task Force (IETF) in RFC 1722. BGP automatically exchanges routing and reachability information among autonomous systems on the internet. Your device is BGP-capable if it can perform BGP routing, which means that you can enable the BGP protocol on it and assign it a BGP IP address and an autonomous system number. To determine if your device supports BGP, see the vendor information for your device or contact your device's vendor.
autonomous system (AS)
A collection of connected IP routing prefixes under the control of a single administrative entity or domain that presents a common routing policy to the internet, such as an internet service provider (ISP), a large company, or a university.
autonomous system number (ASN)
A unique identifier allocated to each autonomous system that uses BGP routing. For more information, see RFC 1930.