Transit Gateway to External Device FAQ
If I already have a Transit to External Device connection using IKEv1, could I create another one using IKEv2?
The prerequisite for IKEv2 is that you need to create the first Transit to External Device connection with IKEv2 enabled. If your current Transit gateway already has a connection using IKEv1 either is created by attaching the Spoke Gateway or is built in Multi-Cloud Transit > Attach/Detach tab, you need to delete it first before creating the Transit to External Device connection with IKEv2.
How do I find out what routes are being propagated from on-prem?
On-prem routes are propagated to the VGW which in turn propagates to the Transit GW. There are two ways to see what learned routes are by the Transit GW:
-
Go to Site2Cloud, select the connection you specified at Step 3 during the Transit Network Workflow. Scroll down, you will see the Learned Network. Search for a learned route by typing a specific CIDR.
-
Go to Peering > Transitive Peering. Click the box next to Destination CIDR column for a specific Spoke VPC/VNet GW. The Learned Routes are displayed and searchable.
-
Go to Multi-Cloud transit > BGP > select a Transit GW, and click Detail.
How do I know if the tunnel between the VGW and the Transit GW is up?
Go to Site2Cloud on the left sidebar. The tunnel status is displayed for each connection.