Se o status de uma das conexões não estiver recebendo um sinal, verifique se você ativou
a porta do Azure correspondente, conforme descrito em
Ativar as portas.
Verificar a tabela de rota
Para verificar se o Azure aprendeu suas rotas do Google Cloud, consulte a tabela de rotas do circuito ExpressRoute.
DEVICE_PATH: para verificar o circuito principal, use primary. Para verificar o circuito secundário, use secondary
CIRCUIT_NAME: o nome do circuito ExpressRoute
RESOURCE_GROUP: o grupo de recursos associado ao circuito
Se você não conseguir os resultados esperados, revise o peering particular que você criou para seu circuito ExpressRoute. Tente inverter os valores da sub-rede IPv4 principal e da sub-rede secundária IPv4 e, em seguida, verifique a tabela de rota novamente.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2024-12-05 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)."]]
