Troubleshooting

The troubleshooting guide can help you solve common issues that you might encounter when using Cloud Interconnect:

General troubleshooting

Can't connect to resources in other regions

By default, VPC networks are regional, meaning Cloud Router advertises only the subnets in its region. To connect to other regions, set the dynamic routing of your VPC network to global so that Cloud Router can advertise all subnets. For more information, see Dynamic routing mode in the Cloud Router documentation.

Sharing connections with other projects in my organization

Use Shared VPC to share a connection, such as a VLAN attachment or a dedicated interconnect, in a host project. For more information about setting up a Shared VPC network, see Provisioning Shared VPC.

Dedicated Interconnect

Google can't ping you during the interconnect provisioning process

  • Check that you're using the correct IP configuration. During the testing process, Google sends you two different IP configurations for your on-premises router. Don't configure VLANs for either of these tests.
    1. The first set of IP addresses is for testing link level connectivity only. You must configure the correct IP address on every physical circuit, as instructed in the emails that Google sent you. Google pings all of those IPs. Don't configure LACP for this test.
    2. For the second test, remove all of the IP addresses from the first test. Configure the port channel with LACP even if your interconnect has only one circuit. Google pings the port channel address. Don't modify IP addresses or the LACP configuration on your port channel after you have passed the final test.

You can't ping Cloud Router

  • Check that you can ping Google's port channel IP address. The IP address is the googleIpAddress value when you view the interconnect details.
  • Check that you have the correct VLAN on your on-premises router's subinterface. The VLAN information should match the information provided by the VLAN attachment.
  • Check that you have the right IP address on your on-premises router's subinterface. When you create a VLAN attachment, it allocates a pair of link local IP addresses. One is for an interface on a Cloud Router (cloudRouterIpAddress) and the other is for a subinterface on your on-premises router's port channel, not the port channel itself (customerRouterIpAddress).
  • If you're testing the performance of your interconnect attachments, don't ping Cloud Router. Instead, create and then use a VM in your VPC network. For more information, see Performance testing.

BGP session not working

  • Enable multi-hop BGP on your on-premises router with at least two hops.
  • Check that you have the correct neighbor IP address configured on your on-premises router. Use the BGP peer IP address (cloudRouterIpAddress) that was allocated by the VLAN attachment.
  • Check that the local ASN configuration on your on-premises router matches the peer ASN on the Cloud Router and vice versa.

Can't reach VM instances in your VPC network

  • Check that you can ping the port channel and VLAN attachment.
  • Check that your BGP session is active.
  • Check that routes are being advertised and received by your on-premises router.
  • Set the MTU size to 1440 on your on-premises router.

Performance testing over your interconnect attachments

If you need to test the performance of your interconnect attachments, use a VM in your VPC network. Add the performance tools that you require on the VM. Don't use the Cloud Router link-local IP address to test for latency, such as ICMP Ping or path MTU. Using Cloud Router can give unpredictable results.

Partner Interconnect

BGP session not working (layer 2 connections)

  • Check that your on-premises router has been configured with a BGP session to your Cloud Routers.
  • Enable multi-hop BGP on your on-premises router with at least two hops.
  • Check that you have the correct neighbor IP address configured on your on-premises router. Use the BGP peer IP address (cloudRouterIpAddress) that was allocated by the VLAN attachment.
  • Check that the local ASN configuration on your on-premises router matches the peer ASN on the Cloud Router (16550) and vice versa.
  • Check that you can ping the IP address of the Cloud Router from your on-premises router. If not, see You can't ping Cloud Router.

BGP session not working (layer 3 connections)

  • Your Cloud Router must be configured with your service provider's ASN. Reach out to your service provider for assistance.

You can't ping Cloud Router (layer 2 connections)

  • Check that you have the correct VLAN on your on-premises router's subinterface. The VLAN information should match the information provided by your service provider.
  • Check that you have the right IP address on your on-premises router's subinterface. After your service provider configures your VLAN attachment, the attachment allocates a pair of link local IP addresses. One is for an interface on the associated Cloud Router (cloudRouterIpAddress) and the other is for a subinterface on your on-premises router's port channel, not the port channel itself (customerRouterIpAddress).
  • If you're testing the performance of your attachments, don't ping Cloud Router. Instead, create and then use a VM in your VPC network. For more information, see Performance testing.

All other issues

Reach out to your service provider for additional assistance. If needed, your service provider will reach out to Google to fix issues related to Google's side of the network.

Var denne side nyttig? Giv os en anmeldelse af den:

Send feedback om...