아직 확인하지 않았다면 대역폭 할당량 및 한도를 확인하여 필요한 대역폭으로 Cross-Site 네트워크를 만들 수 있는지 확인합니다.
할당량이 충분한지 확인한 후 다음: 확인함을 클릭합니다.
Cross-Site Interconnect 연결의 세부정보를 지정합니다.
이름: 연결의 이름입니다. 이 이름은 Google Cloud 콘솔에 표시되며 Google Cloud CLI에서 연결을 참조하는 데 사용됩니다(예: my-interconnect-redundant).
위치: 선택을 선택하고 위치 목록을 기존 연결이 있는 도시로 필터링합니다. 동일한 시설(에지 가용성 도메인이 두 개 이상 지원되는 경우) 또는 다른 시설을 선택합니다. 도시와 에지 가용성 도메인의 목록을 보려면 Cross-Site Interconnect를 위한 코로케이션 시설을 참조하세요.
용량: 연결의 총 용량으로, 주문한 회선의 크기를 기준으로 결정됩니다. 기존 연결과 동일한 값을 사용합니다.
다음을 클릭합니다.
중복 상호 연결 만들기 체크박스를 선택 취소한 후 계속을 클릭하여 SLA 메시지를 닫습니다.
일반적으로 Cross-Site Interconnect 연결을 만들 때 두 번째 중복 연결을 함께 주문하는 것이 좋습니다.
여기에서는 기존 연결에 대한 중복 연결을 만들 것이므로 연결을 추가로 주문할 필요가 없습니다.
(선택사항) 에지 가용성 도메인(권역 가용성 영역)을 선택합니다.
선택한 위치에 에지 가용성 도메인이 둘 이상 있으면 특정 영역을 선택할 수 있습니다. 중복화하려는 기존 Cross-Site Interconnect 연결이 포함되지 않은 영역을 선택합니다. 동일한 도시에 추가 연결이 없으면 Google Cloud 콘솔에서 자동으로 올바른 영역을 선택합니다.
다음을 클릭합니다.
연락처 정보를 지정합니다.
회사 이름: 연결을 요청할 권한이 있는 관계자로 LOA에 기재할 조직의 이름입니다.
기술 담당자: 이 Interconnect 연결 관련 알림을 전송할 이메일 주소입니다. 주소를 직접 입력할 필요가 없습니다. 모든 알림을 확인할 수 있습니다. 주소는 하나만 지정할 수 있습니다.
주문을 검토합니다. Cross-Site Interconnect 연결 세부정보와 연락처 정보가 올바른지 확인합니다. 모든 정보가 올바르면 주문하기를 클릭합니다. 그렇지 않으면 뒤로 돌아가서 연결 세부정보를 수정합니다.
주문 확인 페이지에서 다음 단계를 검토하고 완료를 선택합니다.
gcloud
기존 Cross-Site Interconnect 연결의 도시를 찾으려면 다음 안내를 따르세요.
[[["이해하기 쉬움","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-07-26(UTC)"],[],[],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)."]]
