Default Route with next-hop type as VPN_S2S_Gateway missing from Effective Routes
I have setup a vWAN with One HUB inside. In addition, two VPN gateways have been configured as Site-to-Site to connect with On-premise Gateway.
I have already attached the required vNET to this hub and vNET subnet is visible on my on-premise gateway,
Tunnel/VPN site Status shows up,
vWAN Topology for reference,
I have setup routing on-premise to use this Tunnel and I am able to reach the VM hosted in Azure from VM hosted on-premise. Now, comes the main issue, although Azure VM is responding to the Ping packets, response ping packets are not able to make it out of Azure as a default Route entry is missing from 'effective route' entries inside the Hub.
Is there a way whereby I can add entries[default Route/Specific Route] inside effective route table manually using next-hop type as VPN_S2S_Gateway so that Hub can route back
Closing This Thread. It was an issue where VPN Objects were created with a wrong Route object at the time of Creation.
Thank you sharing the cause of the issue, @Tyagi, Rahul (Nokia - SG/Singapore) .
Glad to hear that the issue is now fixed.
Sign in to comment