Verify your connections

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.

To check connectivity between your Google Cloud and Azure networks, complete the following tasks.

Check for a signal from Azure

In Google Cloud, check to see whether your Cross-Cloud Interconnect port is receiving a signal from the ExpressRoute Direct port.

Console

1. In the Google Cloud console, go to the Cloud Interconnect Physical connections page.

   Go to Physical connections

2. Click the name of your primary Cross-Cloud Interconnect connection.
3. 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.
4. Repeat the preceding steps for your redundant Cross-Cloud Interconnect connection.

If the status of either connection is not receiving a signal, double-check that you enabled the corresponding Azure port, as described in Enable the ports.

Check the route table

To verify that Azure has learned your Google Cloud routes, view the route table for your ExpressRoute circuit.

Azure PowerShell

Use the Get-AzExpressRouteCircuitRouteTable command:

Get-AzExpressRouteCircuitRouteTable -DevicePath DEVICE_PATH `
   -ExpressRouteCircuitName CIRCUIT_NAME `
   -PeeringType AzurePrivatePeering `
   -ResourceGroupName RESOURCE_GROUP

Replace the following:

• DEVICE_PATH: to check the primary circuit, use primary; to check the secondary circuit, use secondary
• CIRCUIT_NAME: the name of your ExpressRoute circuit
• RESOURCE_GROUP: the resource group associated with the circuit

If you don't see the results that you expect, review the private peering you created for your ExpressRoute circuit. Try reversing the values for IPv4 Primary subnet and IPv4 Secondary subnet, and then check the route table again.

Review the Troubleshooting page

For additional guidance, see Troubleshooting.