Order Cross-Site Interconnect connections

In the Google Cloud console, go to the Interconnectpage.

Go to Interconnect

Click add Set up physical connection.

Select Cross-Site Interconnect connection, and then click Continue.

If you haven't already, check your bandwidth quotas and limits to ensure that you can successfully create a cross-site network with your required bandwidth.

After you have confirmed that you have sufficient quota, click Next: I acknowledge.

Specify the details of the Cross-Site Interconnect connection:

• Name: A name for the connection. This name is displayed in the Google Cloud console and is used by the Google Cloud CLI to reference the connection, such as my-interconnect .
• Colocation facility: The physical location where the connection is created. Your on-premises network must meet Google Cloud's network in this location.

• Capacity: The total capacity of your connection, which is determined by the number and size of the circuits that you order.

  Select one of the following options:

  • 1 x 10-Gbps circuit
  • 1 x 100-Gbps circuit

Click Next.

If you plan to create a cross-site network with a redundant or box-and-cross topology, specify details for your duplicate connection, and then click Next.

Specify your contact information:

• Company name: The name of your organization to put in the LOA as the party authorized to request a connection.

• Technical contact: An email address where notifications about this connection are sent. You don't need to enter your own address; you are included in all notifications. You can specify only one address.

  If you are creating a connection through workforce identity federation , specifying a Technical contactis required.

Review your order. Check that your connection details and contact information are correct. If everything is correct, click Place order. If not, go back and edit the connection details.

On the order confirmation page, review the next steps, and then click Done.

To order connections for your second site, repeat the steps in this section.

Create a Cross-Site Interconnect connection that is a connection type of DEDICATED and specifies the CROSS_SITE_NETWORK feature. If you plan to use MACsec for Cloud Interconnect , include MACSEC in the list of requested features.

gcloud beta compute interconnects create INTERCONNECT_NAME 
\
    --customer-name= NAME 
\
    --interconnect-type=DEDICATED \
    --requested-features=CROSS_SITE_NETWORK[,MACSEC] \
    --link-type= LINK_TYPE 
\
    --location= LOCATION_NAME 
\
    [--noc-contact-email= EMAIL_ADDRESS 
] \
    [--description= STRING 
]

Replace the following values:

• INTERCONNECT_NAME : a name for the Cross-Site Interconnect connection; this name is displayed in the Google Cloud console and is used by the Google Cloud CLI to reference the connection, such as my-interconnect
• NAME : the name of your organization to put in the LOA as the party authorized to request a connection
• LINK_TYPE :
  • If you want your Cross-Site Interconnect connection to be made up of a 10-Gbps circuit, replace LINK_TYPE with LINK_TYPE_ETHERNET_10G_LR .
  • If you want your connection to be made up of a 100-Gbps circuit, replace LINK_TYPE with LINK_TYPE_ETHERNET_100G_LR .
• LOCATION_NAME : specifies the location where the Cross-Site Interconnect connection is created; to list the names of locations, see List locations for Cross-Site Interconnect
• EMAIL_ADDRESS and STRING : optional; for the NOC contact, you can specify only one email address—you don't need to enter your own address because you are included in all notifications. If you are creating a connection through workforce identity federation , providing an email address with the ‑‑noc-contact-email flag is required.

If you plan to create a cross-site network with a redundant or box-and-cross topology, create a duplicate Cross-Site Interconnect connection that is in the same metro but in a different edge availability domain (metro availability zone).

gcloud beta compute interconnects create REDUNDANT_INTERCONNECT_NAME 
\
     --customer-name= NAME 
\
     --interconnect-type=DEDICATED \
     --requested-features=CROSS_SITE_NETWORK[,MACSEC] \
     --link-type= LINK_TYPE 
\
     --location= LOCATION_NAME 
\
     [--noc-contact-email= EMAIL_ADDRESS 
] \
     [--description= STRING 
]

Replace the following:

• REDUNDANT_INTERCONNECT_NAME : a name for the redundant Cross-Site Interconnect connection
• NAME : the name of your organization to put in the LOA as the party authorized to request a connection
• LINK_TYPE : the per-circuit capacity of your Cross-Site Interconnect connection; use the same value as the existing connection:
  • If your existing connection is made up of 10-Gbps circuits, replace LINK_TYPE with LINK_TYPE_ETHERNET_10G_LR .
  • If your existing connection is made up of 100-Gbps circuits, replace LINK_TYPE with LINK_TYPE_ETHERNET_100G_LR .

• LOCATION_NAME : the location where the redundant Cross-Site Interconnect connection is created

  From the list of locations , select one that's in the same metro but in a different edge availability domain from the existing connection.

  For example, if the existing connection is in iad-zone2-1 , select a location that's in Ashburn but in zone 1, such as iad-zone1-1 .

• EMAIL_ADDRESS and STRING : optional; for the NOC contact, you can specify only one email address—you don't need to enter your own address because you are included in all notifications

To order connections for your second site, repeat the steps in this section.