Jika status salah satu koneksi tidak menerima sinyal, periksa kembali apakah Anda telah mengaktifkan
port Azure yang sesuai, seperti yang dijelaskan dalam
Mengaktifkan port.
Memeriksa tabel rute
Untuk memverifikasi bahwa Azure telah mempelajari rute Google Cloud , lihat tabel rute untuk sirkuit ExpressRoute.
DEVICE_PATH: untuk memeriksa sirkuit utama, gunakan
primary; untuk memeriksa sirkuit sekunder, gunakan secondary
CIRCUIT_NAME: nama sirkuit ExpressRoute Anda
RESOURCE_GROUP: grup resource yang terkait dengan
sirkuit
Jika Anda tidak melihat hasil yang diharapkan, tinjau
peering pribadi yang Anda buat untuk sirkuit ExpressRoute. Coba ubah nilai untuk
Subnet Utama IPv4 dan Subnet Sekunder IPv4, lalu periksa kembali tabel rute.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-12 UTC."],[],[],null,["# Verify your connections\n\n| **Note:** This page includes instructions about Azure products. Google doesn't guarantee that this guidance is up to date or that the sample configuration choices are ideal for your use case. For the most current information, refer to the [Azure documentation](https://learn.microsoft.com/azure/?product=networking).\n\nTo check connectivity between your Google Cloud and Azure networks, complete\nthe following tasks.\n\nCheck for a signal from Azure\n-----------------------------\n\n\nIn Google Cloud, check to see whether your\nCross-Cloud Interconnect port is receiving a signal from the\nExpressRoute Direct port.\n\n### Console\n\n1. In the Google Cloud console, go to the Cloud Interconnect **Physical\n connections** page.\n\n [Go to **Physical\n connections**](https://console.cloud.google.com/hybrid/interconnects/list?tab=interconnects)\n2. Click the name of your primary Cross-Cloud Interconnect connection.\n3. On the **Interconnect details** page, locate the **Link circuit info** table. Check the **Receiving Optical Power** column. This column indicates whether the Cross-Cloud Interconnect connection is receiving input from the Azure port. The value in this column should be **OK**.\n4. Repeat the preceding steps for your redundant Cross-Cloud Interconnect connection.\n\nIf the status of either connection is not receiving a signal, double-check that you enabled\nthe corresponding Azure port, as described in\n[Enable the ports](/network-connectivity/docs/interconnect/how-to/cci/azure/order-azure-ports#enable-ports).\n\nCheck the route table\n---------------------\n\nTo verify that Azure has learned your Google Cloud routes, view the route\ntable for your ExpressRoute circuit. \n\n### Azure PowerShell\n\nUse the [`Get-AzExpressRouteCircuitRouteTable` command](https://learn.microsoft.com/powershell/module/az.network/get-azexpressroutecircuitroutetable?view=azps-8.2.0): \n\n```\nGet-AzExpressRouteCircuitRouteTable -DevicePath DEVICE_PATH `\n -ExpressRouteCircuitName CIRCUIT_NAME `\n -PeeringType AzurePrivatePeering `\n -ResourceGroupName RESOURCE_GROUP\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eDEVICE_PATH\u003c/var\u003e: to check the primary circuit, use `primary`; to check the secondary circuit, use `secondary`\n- \u003cvar translate=\"no\"\u003eCIRCUIT_NAME\u003c/var\u003e: the name of your ExpressRoute circuit\n- \u003cvar translate=\"no\"\u003eRESOURCE_GROUP\u003c/var\u003e: the resource group associated with the circuit\n\nIf you don't see the results that you expect, review the\n[private peering you created](/network-connectivity/docs/interconnect/how-to/cci/azure/configure-azure#set-up-private-peering) for your ExpressRoute circuit. Try reversing the values for\n**IPv4 Primary subnet** and **IPv4 Secondary subnet**, and then check the route table again.\n\nReview the Troubleshooting page\n-------------------------------\n\nFor additional guidance, see\n[Troubleshooting](/network-connectivity/docs/interconnect/support/troubleshooting)."]]
