Cloud Interconnect 진단을 사용하면 프로비저닝 중 및 활성화 후에 Cross-Cloud Interconnect 연결 문제를 해결할 수 있습니다. 진단에서는 Cross-Cloud Interconnect 연결의 Google Cloud 측에 대한 자세한 최신 기술 정보를 제공합니다.
서비스 중단 시 진단
전역 서비스 중단 시에는 Cross-Cloud Interconnect 연결 정보가 전역 리소스로 제공되므로 진단 결과가 제공되지 않을 수 있습니다. 전역 서비스 중단이 Cross-Cloud Interconnect 진단 가져오기에 영향을 줄 수 있습니다. 하지만 이러한 전역 서비스 중단은 상호 연결 또는 연결의 기능 상태를 반드시 반영하지는 않습니다.
프로비저닝 중 진단
진단에는 프로비저닝 프로세스 단계에 따라 다른 데이터가 포함됩니다. 연결이 각 단계의 요구 사항을 충족해야 다음 단계로 넘어갈 수 있습니다.
단계는 다음과 같습니다.
1단계 - 회선 연결
광출력 상태는 OK입니다.
bundleOperationalStatus는 Down입니다.
2단계 - 회선 검증(다중 연결)
광출력 상태는 OK입니다.
bundleOperationalStatus는 Down입니다.
3단계 - 프로덕션 구성
광출력 상태는 OK입니다.
bundleOperationalStatus는 Up입니다.
진단 사용
Google Cloud 콘솔, Google Cloud CLI 또는 API에서 가져온 정보를 해석하려면 명령어 출력 참조 섹션을 확인하세요.
이 태스크에 필요한 권한
이 태스크를 수행하려면 다음 권한 또는 다음 Identity and Access Management(IAM) 역할을 부여 받아야 합니다.
권한
compute.interconnects.get
compute.interconnects.use
역할
roles/compute.networkAdmin
콘솔
Google Cloud 콘솔에서 Cloud 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-09-05(UTC)"],[],[],null,["# Get diagnostics\n\nCloud Interconnect diagnostics let you troubleshoot your\nCross-Cloud Interconnect connections during provisioning and after\nactivation. The diagnostics provide you with current, detailed technical\ninformation about the Google Cloud side of your\nCross-Cloud Interconnect connection.\n\nDiagnostics during outages\n--------------------------\n\nDiagnostic results might not be available during a\n[global outage](https://status.cloud.google.com/) because the\nCross-Cloud Interconnect connection information is provided as\na global resource. A global outage might affect the diagnostics for\nCross-Cloud Interconnect from being fetched. However, these\nglobal outages don't necessarily reflect the functional state of the\ninterconnects or attachments.\n\nDiagnostics during provisioning\n-------------------------------\n\nDiagnostics contain different data depending on the stage of the\nprovisioning process. Your connection must meet the requirements of each\nstage before it can move on to the next one.\n\nThe stages are as follows:\n\n- **Stage 1 - Circuit connection:**\n\n - The optical power state is `OK`.\n - bundleOperationalStatus is `Down`.\n- **Stage 2 - Circuit qualification (multiple links):**\n\n - The optical power state is `OK`.\n - bundleOperationalStatus is `Down`.\n- **Stage 3 - Production configuration:**\n\n - The optical power state is `OK`.\n - bundleOperationalStatus is `Up`.\n\nUse diagnostics\n---------------\n\nTo interpret information that you get from the Google Cloud console,\nthe Google Cloud CLI, or the API, see the\n[Command output reference](#output-reference) section.\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- `roles/compute.networkAdmin` \n\n### Console\n\n1. In the Google Cloud console, go to the Cloud Interconnect **Physical\n connections** tab.\n\n [Go to Physical connections](https://console.cloud.google.com/hybrid/interconnects/list?tab=interconnects)\n2. Select the name of your Cross-Cloud Interconnect\n connection.\n\n3. Review the following fields:\n\n - For warnings or errors, see the **Status** field in the upper-left corner of the page.\n - For the provisioned capacity of the Cloud Interconnect connection, see the **Provisioned capacity** field.\n - If you suspect issues with the Cloud Interconnect connection, see the **VLAN attachments** section for information such as the effective capacity of the connection or the number of down links.\n - For additional details, such as light levels, see the **Link\n circuit info** section.\n\n### gcloud\n\nUse the\n[`gcloud compute interconnects get-diagnostics` command](/sdk/gcloud/reference/compute/interconnects/get-diagnostics): \n\n```\ngcloud 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 connection\n- \u003cvar translate=\"no\"\u003ePROJECT_ID\u003c/var\u003e: the ID of the Google Cloud project\n\nThe command output should look similar to the following: \n\n```\nresult:\nbundleAggregationType: BUNDLE_AGGREGATION_TYPE_LACP\nbundleOperationalStatus: BUNDLE_OPERATIONAL_STATUS_UP\nlinks:\n- circuitId: GCP-00112\ngoogleDemarc: MARKL:MMR A/ 4th floor Cab 04.105.004.704 FP 4 Port 3 Fibers 77,78\n -LC\nlacpStatus:\n googleSystemId: 9c:e1:76:7a:40:de\n neighborSystemId: ec:ce:13:e2:99:07\n state: ACTIVE\noperationalStatus: LINK_OPERATIONAL_STATUS_UP\nreceivingOpticalPower:\n state: OK\n value: -2.94\ntransmittingOpticalPower:\n state: OK\n value: -1.66\nmacAddress: 9c:e1:76:7a:40:e3\n```\n\n### API\n\nUse the [`interconnects.getDiagnostics` method](/compute/docs/reference/rest/v1/interconnects/getDiagnostics): \n\n```\n GET https://compute.googleapis.com/compute/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 your connection\n\nIf this command succeeds, it returns `InterconnectDiagnostics` output in the\nfollowing format. \n\n```\n{\n\"result\": {\n\"macAddress\": \"9c:e1:76:7a:40:e3\",\n\"links\": [\n {\n \"circuitId\": \"GCP-00112\",\n \"googleDemarc\": \"MARKL:MMR A/ 4th floor Cab 04.105.004.704 FP 4 Port 3 Fibers 77,78 -LC\",\n \"receivingOpticalPower\": {\n \"value\": -2.97,\n \"state\": \"OK\"\n },\n \"transmittingOpticalPower\": {\n \"value\": -1.67,\n \"state\": \"OK\"\n },\n \"lacpStatus\": {\n \"state\": \"ACTIVE\",\n \"googleSystemId\": \"9c:e1:76:7a:40:de\",\n \"neighborSystemId\": \"ec:ce:13:e2:99:07\"\n },\n \"operationalStatus\": \"LINK_OPERATIONAL_STATUS_UP\"\n }\n],\n\"bundleOperationalStatus\": \"BUNDLE_OPERATIONAL_STATUS_UP\",\n\"bundleAggregationType\": \"BUNDLE_AGGREGATION_TYPE_LACP\"\n}\n}\n```\n\nCommand output reference\n------------------------\n\nTo interpret diagnostics output, see the following table.\n| **Note:** If you want to create an alert for the value of the transmitting and receiving optical power, you can take a known good optical value, give it a 10% margin, and create alerts 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 learn more about Cross-Cloud Interconnect, see the\n [Cross-Cloud Interconnect overview](/network-connectivity/docs/interconnect/concepts/cci-overview).\n\n- To learn about common issues that you might encounter when using\n Cross-Cloud Interconnect, see\n [Troubleshooting](/network-connectivity/docs/interconnect/support/troubleshooting#cci)."]]
