[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間:2025-09-05 (世界標準時間)。"],[],[],null,["# Duplicate a connection for redundancy\n\nIf you have a single Cross-Site Interconnect connection, you can create\na second one so that you have redundant connections. Google recommends\nredundancy so that if one connection fails, the other connection can continue to\nserve traffic.\n|\n| **Preview**\n|\n|\n| This product is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA products are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n\nTo create a redundant Cross-Site Interconnect connection,\nyou must create it in the same\nmetropolitan area (city) as the existing one, but in a different\n[edge availability domain](/network-connectivity/docs/interconnect/concepts/terminology#edge-availability-domain)\n(metro availability zone). If you don't, the connections won't be redundant.\n| **Note:** To build a redundant topology, you must create and configure additional resources. For more information, see [Wire group topologies](/network-connectivity/docs/interconnect/concepts/cross-site-overview#wire-group-topologies) in the Cross-Site Interconnect overview.\n\n#### Permissions required for this task\n\nTo perform this task, you must have been granted the following permissions\n*or* the following Identity and Access Management (IAM) roles.\n\n**Permissions**\n\n- `compute.interconnects.create`\n- `compute.interconnects.get`\n- `compute.interconnectLocations.get`\n- `compute.interconnectLocations.list`\n\n**Roles**\n\n- Owner (`roles/owner`)\n- Editor (`roles/editor`)\n- Compute Network Admin (`roles/compute.networkAdmin`) \n\n### Console\n\nTo find the city of the existing Cross-Site Interconnect connection:\n\n1. In the Google Cloud console, go to the **Interconnect** page.\n\n\n [Go to Interconnect](https://console.cloud.google.com/hybrid/interconnects/list)\n\n \u003cbr /\u003e\n\n2. On the **Physical connections** tab, select the existing\n Cross-Site Interconnect connection to view its details\n page.\n\n3. In the **Details** section, view the location address and record the city\n name. This is the city where the redundant connection must be\n configured.\n\nTo create the redundant Cross-Site Interconnect connection:\n\n1. In the Google Cloud console, go to the **Interconnect** page.\n\n\n [Go to Interconnect](https://console.cloud.google.com/hybrid/interconnects/list)\n\n \u003cbr /\u003e\n\n2. On the **Physical connections** tab, click\n **Set up physical connection**.\n\n3. Select **Cross-Site Interconnect connection** , and then click\n **Continue**.\n\n4. If you haven't already, [check your bandwidth quotas and limits](/network-connectivity/docs/interconnect/how-to/cross-site/check-bandwidth-quota) to ensure that you\n can successfully create a cross-site network with your required bandwidth.\n\n After you have confirmed that you have sufficient quota, click\n **Next: I acknowledge**.\n5. Specify the details of the Cross-Site Interconnect connection:\n\n - **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-redundant`.\n - **Location** : Select **Choose** , and then filter the list of locations to the city where your existing connection is located. Select the same facility (if it supports more than one edge availability domain) or a different facility. To view the list of cities and their edge availability domains, see [Colocation facilities for Cross-Site Interconnect](/network-connectivity/docs/interconnect/concepts/cross-site-locations).\n - **Capacity**: The total capacity of your connection, which is determined by the size of the circuit that you order. Use the same value as the existing connection.\n6. Click **Next**.\n\n7. Clear the **Create redundant interconnect** checkbox, and then click\n **Continue** to dismiss the SLA message.\n\n Normally, when you create a Cross-Site Interconnect\n connection, we recommend that you order a second redundant connection.\n In this case, because you're creating a redundant connection for an\n existing connection, you don't need to order another connection.\n8. Optional: Select an edge availability domain (metro availability zone).\n\n If the location that you selected has more than one edge availability\n domain, you can choose a particular zone. Choose the zone that doesn't\n contain the existing Cross-Site Interconnect connection\n that you're building redundancy for. If you have no additional\n connections in the same city, the Google Cloud console chooses the\n correct zone for you.\n9. Click **Next**.\n\n10. Specify your contact information:\n\n - **Company name**: The name of your organization to put in the LOA as the party authorized to request a connection.\n - **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.\n11. Review your order. Check that your Cross-Site Interconnect\n connection details and contact information are correct. If everything is\n correct, click **Place order**. If not, go back and edit the connection\n details.\n\n12. On the order confirmation page, review the next steps and then select\n **Done**.\n\n### gcloud\n\nTo find the city of the existing Cross-Site Interconnect connection:\n\n1. [View connection details](/network-connectivity/docs/interconnect/how-to/cross-site/view-connections) to view its location:\n\n ```\n gcloud beta compute interconnects describe INTERCONNECT_NAME\n ```\n\n In the output, view the `location` field, which shows a URL such as\n `https://www.googleapis.com/compute/...\u003cexample\u003e.../iad-zone1-1`.\n The last part of the URL is the name of the location (`iad-zone1-1`).\n2. [Describe the location](/network-connectivity/docs/interconnect/how-to/cross-site/list-locations)\n to view the city in which it's located, passing the location\n name from the previous step:\n\n ```\n gcloud beta compute interconnects locations describe LOCATION_NAME\n ```\n\nTo create the redundant Cross-Site Interconnect connection:\n\n1. Choose a facility where the redundant\n Cross-Site Interconnect connection is to be\n located. From the list of\n [locations](/network-connectivity/docs/interconnect/concepts/cross-site-locations#locations-table),\n select one that's in the same city but in a different edge availability\n domain from the existing connection.\n\n For example, if the existing connection is in `iad-zone2-1`, select a\n location that's in Ashburn but in zone 1, such as `iad-zone1-1`. You need\n this location name when you create the redundant connection.\n2. Create the redundant Cross-Site Interconnect connection in\n the location that you selected. If you are using [MACsec for Cloud Interconnect](/network-connectivity/docs/interconnect/concepts/macsec-overview), include `MACSEC` in the list of\n requested features.\n\n ```\n gcloud beta compute interconnects create INTERCONNECT_NAME \\\n --customer-name=NAME \\\n --interconnect-type=DEDICATED \\\n --requested-features=CROSS_SITE_NETWORK[,MACSEC] \\\n --link-type=LINK_TYPE \\\n --location=LOCATION_NAME \\\n [--noc-contact-email=EMAIL_ADDRESS] \\\n [--description=STRING]\n ```\n\n Replace the following:\n - \u003cvar translate=\"no\"\u003eINTERCONNECT_NAME\u003c/var\u003e: the 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-redundant`.\n - \u003cvar translate=\"no\"\u003eNAME\u003c/var\u003e: the name of your organization to put in the LOA as the party authorized to request a connection\n - \u003cvar translate=\"no\"\u003eLINK_TYPE\u003c/var\u003e: the per-circuit capacity of your Cross-Site Interconnect connection; use the same value as the existing connection:\n - If your existing connection is made up of 10-Gbps circuits, replace \u003cvar translate=\"no\"\u003eLINK_TYPE\u003c/var\u003e with `LINK_TYPE_ETHERNET_10G_LR`.\n - If your existing connection is made up of 100-Gbps circuits, replace \u003cvar translate=\"no\"\u003eLINK_TYPE\u003c/var\u003e with `LINK_TYPE_ETHERNET_100G_LR`.\n - \u003cvar translate=\"no\"\u003eLOCATION_NAME\u003c/var\u003e: the name of the location that you selected in the previous step\n - \u003cvar translate=\"no\"\u003eEMAIL_ADDRESS\u003c/var\u003e and \u003cvar translate=\"no\"\u003eSTRING\u003c/var\u003e: 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\n\nAfter you order a Cross-Site Interconnect connection, Google\nemails you a confirmation and\nallocates ports for you. When the allocation is complete, Google generates\nLOA-CFAs for your connections and emails them to you. All of the automated\nemails are sent to the NOC contact and the person who ordered the\nCross-Site Interconnect connection.\n\nYou can use the Cross-Site Interconnect connection only after your connections have been provisioned and tested for light levels and IP connectivity.\n\nWhat's next\n-----------\n\n- To upgrade your wire group type using your duplicate connection, see\n [Upgrade or downgrade your wire group type](/network-connectivity/docs/interconnect/how-to/cross-site/modify-network#upgrade-downgrade).\n\n- To create a new Cross-Site Interconnect connection, see the\n [Cross-Site Interconnect provisioning\n overview](/network-connectivity/docs/interconnect/how-to/cross-site/provisioning-overview).\n\n- To help you solve common issues that you might encounter when using\n Cloud Interconnect, see\n [Troubleshooting](/network-connectivity/docs/interconnect/support/troubleshooting)."]]