Duplicating an Existing Interconnect for Redundancy

If you have single dedicated interconnect, you can create a second one so that you have redundant interconnects. Google recommends redundancy so that if one interconnect fails, the other one can continue to serve traffic.

To create a redundant interconnect, you must create it in the same metropolitan area (city) as the existing one, but in a different metropolitan availability zone. If you don't, the interconnects won't be redundant.

Console

To find the city of the existing interconnect:

  1. Go to the Cloud Interconnect Physical connections tab in the Google Cloud Platform Console.
    Go to Physical connections tab
  2. Select the existing interconnect to view it's details page.
  3. In the Details section, view the location address and record the city name. This is the city where the redundant interconnect must be configured.

To create the redundant interconnect:

  1. Go to the Cloud Interconnect Physical connections tab in the Google Cloud Platform Console.
    Go to Physical connections tab
  2. Select Set up connection.
  3. Select Dedicated Interconnect and then select Continue.
  4. Select Order new Dedicated Interconnect and then select Continue.
  5. Specify the details of the interconnect and then select Next.
    • Name — A name for the interconnect. This name is displayed in the console and used by the gcloud command-line tool to reference the interconnect, such as my-interconnect-redundant.
    • Location — Select Choose, and then filter the list of locations to the city where your existing interconnect is located. Select the same facility (if it supports more than one metro availability zone) or a different facility. To view the list of cities and their metro availability zones, see Colocation Facility Locations.
    • Capacity — The total capacity of your interconnect. Use the same value as the existing interconnect.
  6. Clear Create redundant interconnect, and then select Continue to dismiss the SLA message.
    Normally, when you create an interconnect, Google recommends that you order a second redundant interconnect. In this case, because you're creating a redundant interconnect for an existing one, you don't need to order another interconnect.
  7. [Optional] Expand the Advanced provisioning options to select a metro availability zone.
    If the location you selected has more than one metro availability zone, you can choose a particular zone. Choose the zone that doesn't contain the existing interconnect that you're building redundancy for. If you have no additional interconnects in the same city, the console chooses the correct zone for you.
  8. Select Next.
  9. Specify your contact information.
    • Company name — The name of your organization to put in the LOA as the party authorized to request a cross connect.
    • Technical contact — An email address where notifications about this interconnect are sent. You don't need to enter your own address; you'll be included in all notifications. Note that you can specify only one address.
  10. Review your order. Check that your interconnect details and contact information are correct. If everything is correct, select Place order. If not, go back and edit the interconnect details.
  11. On the order confirmation page, review the next steps and then select Done.

gcloud

To find the city of the existing interconnect:

  1. Describe the existing interconnect to view its location.

    gcloud compute interconnects describe [INTERCONNECT_NAME]

    In the output, view the location field, which shows a URL like https://www.googleapis.com/compute/...<example>.../sin-zone1-388. The last part of the URL is the name of the location (sin-zone1-38).

  2. Describe the location to view the city in which it's located, passing the location name from the previous step.

    gcloud compute interconnects locations describe [LOCATION_NAME]

To create the redundant interconnect:

  1. Choose a facility where the redundant interconnect will be located. From the list of locations, select one that's in the same city but in a different metro availability zone as the existing interconnect. For example, if the existing interconnect is in iad-zone2-1, select a location that's in Ashburn but in zone 1, such as iad-zone1-1. You'll need this location name when you create the redundant interconnect.

  2. Create the redundant interconnect in the location that you selected.

    gcloud compute interconnects create [INTERCONNECT_NAME] \
      --customer-name [NAME] \
      --interconnect-type DEDICATED \
      --link-type ETHERNET_10G_LR \
      --location [LOCATION_NAME] \
      --requested-link-count [NUMBER_OF_LINKS] \
      [--noc-contact-email [EMAIL_ADDRESS]] \
      [--description [STRING]]

    • --customer-name — The name of your organization to put in the LOA as the party authorized to request a cross connect.
    • --interconnect-type — Specify DEDICATED.
    • --link-type — Only supports 10 Gbps circuits (ETHERNET_10G_LR).
    • --location — The name of the location that you selected in the previous step.
    • --requested-link-count — Number of circuits of type link-type. Use the same value as the existing interconnect.
    • --noc-contact-email and --description are optional. For the NOC contact, you can specify only one email address. You don't need to enter your own address; you'll be included in all notifications.

After you order an interconnect, Google emails you a confirmation and allocates ports for you. When the allocation is complete, Google generates LOA-CFAs for your cross connects and emails them to you. All of the automated emails are sent to the NOC contact and the person who ordered the interconnect.

You'll be able to use the interconnect only after your cross connects have been provisioned and tested for light levels and IP connectivity.

What's next

Create the resources that are required to build a redundant topology, such as VLAN attachments and Cloud Routers. For examples, see Creating a Topology for Production-level Applications or Creating a Topology for Non-critical Applications.

Send feedback about...

Interconnect