Troubleshooting ActiveMesh Transit Gateway

  1. Check IPsec Tunnel. For BGP learned routes, check if the IPsec tunnel is up. Go to Site2Cloud > Setup. Find the connection and make sure it is in Up state. If it is not, go to Site2Cloud > Diagnostics and run Show log. Since all BGP sessions run inside IPsec tunnel, this is the first thing you should check.

  2. Check BGP Session. For BGP learned routes, check if BGP session is established. Go to Multi-Cloud Transit > BGP. Look for the BGP session and make sure it is in Established State. If it is not, go to the Diagnostics tab. Select the transit gateway, run commands, such as "show ip bgp".

  3. Check BGP Learned Routes For BGP learned routes, check if routes are learned. Go to Multi-Cloud Transit > BGP > Diagnostics tab. Select the transit gateway, run "show ip bgp" to make sure the transit gateway under inspection has learned the routes you are looking for.

  4. Check Route Database For all routes, check if the Controller see all the learned routes from TGW, BGP, Transit Peering, and Static. Go to Multi-Cloud Transit > List. Select the Transit Gateway and click Show Details. Scroll down and refresh Route Info DB Details. This table contains learned routes from all sources.

  5. Check Aviatrix Transit Gateway Programmed Routes Go Multi-Cloud Transit Network > List. Select the Transit Gateway, click Actions > Show Details. Scroll down to the Gateway Routing Table and click to open. Make sure the route you are looking for is in the table and has a next hop with metric 100 or lower.

  6. Sync Routes If for any reason the Route Database on the Controller become inconsistent with the Aviatrix Transit Gateway route table, sync the routes to force program the routes on the gateway again. Go to Multi-Cloud Transit > Advanced Config. Select the Aviatrix Transit Gateway in question, scroll down to the Sync Controller Best Routes to Transit Gateway, click Sync Routes.

If any of the above steps show failure, there is an error, please open a support ticket at Aviatrix Support Portal for more debugging assistance.

If all above steps succeed, the connectivity issue lies somewhere else. Check Spoke VPC/VNet route table and TGW route table if applicable.

If this is TGW based deployment, run an Audit by going to TGW Orchestrator > Audit. Any missing routes in either VPC/VNet route table or TGW route table should be discovered.