MACsec for Cloud Interconnect can help you secure traffic on
Cloud Interconnect connections. If you want
MACsec for Cloud Interconnect, you must select it when you order a
Dedicated Interconnect connection.
MACsec for Cloud Interconnect is available for 100‑Gbps links,
regardless of location. If you want a 10G‑Gpbs link with MACsec
support, verify that it is available in your desired
locations.
Submit an order, specifying the details of your connection.
Google then emails you an order confirmation. After your resources have been
allocated, you receive another email with your 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.
If the light level of your physical ports is within the expected threshold,
the ports are operational and Google sends you an automated email
containing configuration details for connectivity testing. Apply these
configurations to your router so that Google can confirm connectivity.
This process confirms the IP connectivity of your connection's production
configuration.
If you don't apply these configurations (or apply them incorrectly), Google
sends an automated email with troubleshooting information.
If the light level of your physical ports is not within the expected
threshold, Google sends an automated email to notify you of the failure.
After all tests have passed, your Dedicated Interconnect
connection is ready to use.
When your 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.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[],[],null,["# Dedicated Interconnect provisioning overview\n\nThis page describes the steps to successfully create and configure a\nDedicated Interconnect connection.\n| **Note:** For definitions of terms used on this page, see [Cloud Interconnect key\n| terms](/network-connectivity/docs/interconnect/concepts/terminology).\n\nTo create and configure a Cloud Interconnect connection for\nDedicated Interconnect, follow these steps:\n\n1. Decide if you want\n [MACsec for Cloud Interconnect](/network-connectivity/docs/interconnect/concepts/macsec-overview).\n\n MACsec for Cloud Interconnect can help you secure traffic on\n Cloud Interconnect connections. If you want\n MACsec for Cloud Interconnect, you must select it when you order a\n Dedicated Interconnect connection.\n\n MACsec for Cloud Interconnect is available for 100‑Gbps links,\n regardless of location. If you want a 10G‑Gpbs link with MACsec\n support, verify that it is [available in your desired\n locations](/network-connectivity/docs/interconnect/concepts/macsec-overview#macsec-availability).\n2. [Order a Dedicated Interconnect connection](/network-connectivity/docs/interconnect/how-to/dedicated/ordering-dedicated-interconnect)\n\n Submit an order, specifying the details of your connection.\n Google then emails you an order confirmation. After your resources have been\n allocated, you receive another email with your LOA-CFAs.\n3. [Retrieve LOA-CFAs](/network-connectivity/docs/interconnect/how-to/dedicated/retrieving-loas)\n\n Send the LOA-CFAs to your vendor. They provision the connections between\n the Google peering edge and your on-premises network. Google\n automatically starts testing the light levels on each allocated port after\n 24 hours.\n4. [Test the connection](/network-connectivity/docs/interconnect/how-to/dedicated/testing-connections)\n\n If the light level of your physical ports is within the expected threshold,\n the ports are operational and Google sends you an automated email\n containing configuration details for connectivity testing. Apply these\n configurations to your router so that Google can confirm connectivity.\n This process confirms the IP connectivity of your connection's production\n configuration.\n\n If you don't apply these configurations (or apply them incorrectly), Google\n sends an automated email with troubleshooting information.\n\n If the light level of your physical ports is *not* within the expected\n threshold, Google sends an automated email to notify you of the failure.\n\n After all tests have passed, your Dedicated Interconnect\n connection is ready to use.\n5. [Create VLAN attachments](/network-connectivity/docs/interconnect/how-to/dedicated/creating-vlan-attachments)\n\n When your connection is ready to use, you need to connect\n Virtual Private Cloud (VPC) networks to your on-premises network. To do that,\n first create a VLAN attachment, specifying an existing Cloud Router\n that's in the VPC network that you want to reach.\n\n If you want to deploy\n [HA VPN over Cloud Interconnect](/network-connectivity/docs/interconnect/concepts/ha-vpn-interconnect),\n you must\n [create encrypted VLAN attachments](/network-connectivity/docs/interconnect/how-to/dedicated/creating-vlan-attachments#encrypted-attachments).\n6. [Configure on-premises routers](/network-connectivity/docs/interconnect/how-to/dedicated/configuring-onprem-routers)\n\n After you create a VLAN attachment, to start sending traffic between\n networks, you need to configure your on-premises router to establish a BGP\n session with your Cloud Router. To configure your on-premises\n router, use the VLAN ID, interface IP address, and peering IP address\n provided by the VLAN attachment.\n7. Optional: [Configure HA VPN over Cloud Interconnect](/network-connectivity/docs/interconnect/how-to/configure-ha-vpn-interconnect)\n\n If you are deploying\n HA VPN over Cloud Interconnect,\n you must build the HA VPN tunnels that carry IPsec-encrypted\n traffic over your VLAN attachment."]]
