Understanding HUB vnet route tables relation

Copper Contributor

Hi there

 

Please help me understand the relation/usage between/of the different route tables in a Hub vnet.
Let's say I have a Hub vnet with ExpressRoute GWs for on-prem connectivity, and VPN GWs for Vnet-Vnet VPN connections to other HUBs. Spokes are peered to the Hub.

The ER GW holds a route table.

The VPN GW. holds its route table.
And the GatewaySubnet holds a route table.

I can view the ER GW Private Peering route table.
I can see the BGP Peers/Routes in the VPN virtual gateway.
But in the hub I cannot really see the effective GatewaySubnet route table.

(I know I can by deploying a VM in a subnet in the hub)

 

When exactly is the GatewaySubnet route table consulted/used? In which flows?

Please elaborate on the GatewaySubnet vs. ER GW vs. VPN GW route tables and their exhange of routes or lack of.

 

Thanks in advance!

 

/Thomas

0 Replies