05-04-2023 06:32 AM
Hello, I have a vpn tunnel from my servers behind a cisco to my azure server. I have to ping from the servers behind the cisco to the azure before I can ping from the azure to the cisco.
05-04-2023 06:36 AM
Hello @andrew52,
It's possible that the VPN keep-alive option is contributing to the issue, as it could be causing the VPN tunnel to stay active even when there is no traffic passing through it. However, keep-alive should not cause the behavior you're describing where you need to ping from one side to the other to establish connectivity.
Instead, it's more likely that there is a routing issue between your servers behind the Cisco and your Azure server. When you ping from the servers behind the Cisco to the Azure server, it could be triggering the routing table to update and establish the proper route for traffic coming from the Azure server to the servers behind the Cisco. Without this initial trigger, the routing table may not be properly updated to allow traffic to flow both ways.
05-04-2023 06:47 AM - edited 05-04-2023 07:03 AM
ASA have keepalive and it run by default in l2l vpn
from cisco doc.
In every tunnel group, IKE keepalives are enabled by default with default threshold and retry values. You can apply this attribute only to IPsec remote access and IPsec LAN-to-LAN tunnel group types.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide