Cloud Interconnect 진단을 사용하면 프로비저닝 중 및 활성화 후에 교차 사이트 Interconnect 연결 문제를 해결할 수 있습니다.
필요 시 진단을 통해Google Cloud 교차 사이트 Interconnect 연결에 대한 자세한 기술 정보를 확인할 수 있습니다.
서비스 중단 시 진단
전역 중단이 발생한 경우 네트워크 트래픽을 리디렉션할 위치를 결정하는 데 교차 사이트 Interconnect 연결의 진단 결과를 사용하지 마세요. 교차 사이트 Interconnect 연결은 전역 리소스입니다. 전역 중단이 발생하면 Cloud Interconnect 진단의 올바른 작동이 방해될 수 있습니다.
프로비저닝 중 진단
진단 결과를 보면 온프레미스 라우터 구성의 문제를 해결하고 고치는 데 필요한 정보를 얻을 수 있으므로 교차 사이트 Interconnect 연결이 프로비저닝 프로세스를 통해 진행되지 않을 경우에 유용합니다.
진단 결과에는 교차 사이트 Interconnect 연결이 있는 프로비저닝 프로세스의 단계에 따라 다른 데이터가 포함됩니다. 주 단계와 부 단계는 다음 섹션에 나열되어 있습니다. 이 진단 정보는 프로비저닝 프로세스를 더 이상의 문제 없이 진행하기 위해 수행하는 가능한 다음 단계를 제시합니다.
진단 명령어 결과 또는 Google Cloud 콘솔에서 제공되는 정보를 해석하려면 명령어 출력 참조를 사용하세요.
프로비저닝 단계
교차 사이트 Interconnect 연결 프로비저닝 프로세스는 다음 단계에서 발생합니다. 2단계로 넘어가기 전에 1단계의 요구사항을 충족해야 합니다.
1단계, 회선 연결
연결의 각 링크에 대한 광출력 상태는 OK입니다.
2단계, 프로덕션 구성
연결의 각 링크에 대한 광출력 상태는 OK입니다.
임시 IP 주소는 태그가 지정되지 않은 번들 인터페이스에 할당됩니다.Google Cloud 는 핑을 통해 연결을 확인합니다. 활성화 프로세스가 완료되면 테스트 IP 주소가 삭제됩니다.
진단 사용
교차 사이트 Interconnect 연결의 진단 정보를 보려면 다음 단계를 따르세요.
이 태스크에 필요한 권한
이 태스크를 수행하려면 다음 권한 또는 다음 Identity and Access Management(IAM) 역할을 부여 받아야 합니다.
[[["이해하기 쉬움","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,["# Get diagnostics\n\nCloud Interconnect diagnostics let you troubleshoot your\nCross-Site Interconnect connections during provisioning and after\nactivation.\n\nThe diagnostics provide you detailed technical information about the\nGoogle Cloud Cross-Site Interconnect connections on\ndemand.\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\nDiagnostics during outages\n--------------------------\n\nIn the event of a [global outage](https://status.cloud.google.com/),\ndon't use the diagnostics results from your\nCross-Site Interconnect connection to make decisions about\nwhere to redirect your network traffic. A Cross-Site Interconnect\nconnection is a global resource. A global outage can prevent the diagnostics for\nCloud Interconnect from functioning properly.\n\nDiagnostics during provisioning\n-------------------------------\n\nViewing diagnostics provides you with the information required to troubleshoot\nand fix problems in your on-premises router configuration, which can be helpful\nif your Cross-Site Interconnect connection fails to progress\nthrough the provisioning process.\n\nThe diagnostics results contain different data depending on [what\nstage](#provisioning-stages) in the provisioning process your\nCross-Site Interconnect connection is in. The major and minor\nsteps are listed in the next section. This diagnostic information provides you\nwith possible next steps\nto take to help ensure that the provisioning process progresses without further\nissues.\n\nUse the [command output reference](#output-reference) to interpret diagnostic\ncommand results or the information provided in the Google Cloud console.\n\n### Provisioning stages\n\nThe Cross-Site Interconnect connection provisioning process\noccurs in the following stages. You must meet the requirements in stage 1\nbefore you can move on to stage 2:\n\n- **Stage 1, circuit connection**\n\n - The optical power state is `OK` for each link in the connection.\n- **Stage 2, production configuration**\n\n - The optical power state is `OK` for each link in the connection.\n - A temporary IP address is assigned to the untagged bundle interface. Google Cloud verifies connectivity through a ping. The test IP address is removed when the activation process is complete.\n\nUse diagnostics\n---------------\n\nTo see diagnostics information for the Cross-Site Interconnect\nconnection, follow these steps.\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.get`\n- `compute.interconnects.use`\n\n**Roles**\n\n- Compute Network Admin (`roles/compute.networkAdmin`) \n\n### Console\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 name of a\n Cross-Site Interconnect connection.\n\n3. Diagnostics information is in the following locations on the connection\n details page:\n\n - For warnings or errors, see the **Status** field.\n - For the provisioned capacity of the Cross-Site Interconnect, see the **Provisioned capacity** field.\n - For additional details, such as link status and light levels, see the **Link circuit info** section.\n - For details such as the effective capacity of the connection or status of its wire groups, see the **Wire groups** section.\n\n### gcloud\n\nUse the [`gcloud beta compute interconnects get-diagnostics` command](/sdk/gcloud/reference/beta/compute/interconnects/get-diagnostics): \n\n```\ngcloud beta compute interconnects get-diagnostics NAME \\\n --project=PROJECT_ID\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eNAME\u003c/var\u003e: the name of the Cross-Site Interconnect connection in your project\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of the Google Cloud project\n\n### API\n\nUse the [`interconnects.getDiagnostics`\nmethod](/compute/docs/reference/rest/beta/interconnects/getDiagnostics): \n\n```\nGET https://compute.googleapis.com/compute/beta/projects/PROJECT_ID/global/interconnects/NAME/getDiagnostics\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of the Google Cloud project\n- \u003cvar translate=\"no\"\u003eNAME\u003c/var\u003e: the name of the Cross-Site Interconnect connection in your project\n\nIf this command succeeds, it returns `InterconnectDiagnostics` output. To interpret the output, see the\n[command output reference](#output-reference) later in this document.\n\nCommand output reference\n------------------------\n\nThe definitions for the output parameters for the `gcloud` commands and the\n[`interconnects.getDiagnostics`](/compute/docs/reference/rest/beta/interconnects/getDiagnostics)\nAPI are listed in the following table.\n| **Note:** If you want to trigger on-premises warnings for the value of the transmitting and receiving optical power, you can take a known good optical value, give it a 10% margin, and trigger warnings relative to that value. In general, a `-7dBm` warning and a `-11dBm` alarm are good optical value estimates for most links.\n\nWhat's next\n-----------\n\n- To create a Cross-Site Interconnect connection, see the\n [Cross-Site Interconnect provisioning 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)."]]
