Stay organized with collections
Save and categorize content based on your preferences.
Cloud Interconnect diagnostics let you troubleshoot your
Cross-Cloud Interconnect connections during provisioning and after
activation. The diagnostics provide you with current, detailed technical
information about the Google Cloud side of your
Cross-Cloud Interconnect connection.
Diagnostics during outages
Diagnostic results might not be available during a
global outage because the
Cross-Cloud Interconnect connection information is provided as
a global resource. A global outage might affect the diagnostics for
Cross-Cloud Interconnect from being fetched. However, these
global outages don't necessarily reflect the functional state of the
interconnects or attachments.
Diagnostics during provisioning
Diagnostics contain different data depending on the stage of the
provisioning process. Your connection must meet the requirements of each
stage before it can move on to the next one.
The stages are as follows:
Stage 1 - Circuit connection:
The optical power state is OK.
bundleOperationalStatus is Down.
Stage 2 - Circuit qualification (multiple links):
The optical power state is OK.
bundleOperationalStatus is Down.
Stage 3 - Production configuration:
The optical power state is OK.
bundleOperationalStatus is Up.
Use diagnostics
To interpret information that you get from the Google Cloud console,
the Google Cloud CLI, or the API, see the
Command output reference section.
Permissions required for this task
To perform this task, you must have been granted the following permissions
or the following Identity and Access Management (IAM) roles.
Permissions
compute.interconnects.get
compute.interconnects.use
Roles
roles/compute.networkAdmin
Console
In the Google Cloud console, go to the Cloud Interconnect Physical
connections tab.
Select the name of your Cross-Cloud Interconnect
connection.
Review the following fields:
For warnings or errors, see the Status field in the upper-left
corner of the page.
For the provisioned capacity of the Cloud Interconnect connection, see
the Provisioned capacity field.
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.
For additional details, such as light levels, see the Link
circuit info section.
To interpret diagnostics output, see the following table.
Output parameter
Description
macAddress
Describes the MAC address of the Cloud Interconnect connection bundle on
the Google Cloud side.
arpCache
Describes individual neighbors seen by the Cloud Router
in the ARP cache for the Cloud Interconnect connection. This is empty when
the connection is not bundled.
arpCache[].macAddress
Lists the MAC address of this ARP neighbor.
arpCache[].ipAddress
Lists the IP address of this ARP neighbor.
links[]
Describes the status for each link on the Cloud Interconnect connection.
links[].circuitId
Lists the Google-assigned unique ID for this circuit, as assigned
during circuit turn-up.
links[].googleDemarc
Describes the Google-assigned demarc, as assigned at circuit
turn-up.
links[].receivingOpticalPower
Describes the current value and status for the received light
level.
links[].receivingOpticalPower.value
Lists the current value of the received light level, in dBm.
links[].receivingOpticalPower.state
The status of the current value when compared to the warning
and alarm levels for the receiving transceiver:
OK: The value has not crossed a warning threshold.
LOW_WARNING: The value has crossed below the low warning threshold.
HIGH_WARNING: The value has crossed above the high warning threshold.
LOW_ALARM: The value has crossed below the low alarm threshold.
HIGH_ALARM: The value has crossed above the high alarm threshold.
links[].transmittingOpticalPower
The current value and status for the transmit light level.
links[].transmittingOpticalPower.value
The current value of the transmitting light level,
in dBm.
links[].transmittingOpticalPower.state
The status of the current value when compared to the warning and
alarm levels for the transmitting transceiver:
OK: The value has not crossed a warning threshold.
LOW_WARNING: The value has crossed below the low warning threshold.
HIGH_WARNING: The value has crossed above the high warning threshold.
LOW_ALARM: The value has crossed below the low alarm threshold.
HIGH_ALARM: The value has crossed above the high alarm threshold.
links[].lacpStatus
The LACP information for the single link.
links[].lacpStatus.state
ACTIVE: The link is configured and active
within the bundle.
DETACHED: The link is not configured within
the bundle; this state is used when the
bundleAggregationType is STATIC.
links[].lacpStatus.googleSystemId
The system ID of the port on the Google Cloud side of the
LACP exchange.
links[].lacpStatus.neighborSystemId
The system ID of the port on the remote cloud side of the LACP
exchange.
links[].arpCache[]
A list of InterconnectDiagnostics.ARPEntry objects,
describing the ARP neighbor entries seen on this link. This is empty
if the link is bundled.
links[].arpCache[].macAddress
The MAC address of this ARP neighbor on this link.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 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)."]]