Showing results for 
Search instead for 
Did you mean: 

Community Helping Community


ASA 5510s not Initiating Site to Site VPN

Hi All

I am having a bit of an issue.

I have 2 sets of ASA 5510 Firewalls with the SSM-10 module (Failover) and I have them all set up but I am having issues setting up the Site to Site VPN I am trying to configure to make sure it works and for testing before installing them at 2 different sites.

Currently I can not get the VPN to establish connection between the 2 Firewalls. I have done many different things from direct connection between the 2 sets of Firewalls over a switch, change IPs, etc.

I can not see any attempt to connect the VPN between the 2 sets of firewalls. I am running continues pings from Devices connect to the Switch on both ends of the VPN and they constantly failing.

Nothing showing in the logs of each firewall and the show crypto isakmp sa shows no active ikev1 or ikev2 connections, I have tried connecting them up to a switch and setting up a session monitor to get a wireshark of what is going on but all I see is no communication between the 2 firewalls, they can ping each other. But any ping attempt from one of the laptops on each end looks like its being forwarded out the OUTSIDE interface not over the VPN, thus initiating the VPN Tunnel.

I am having zero luck, I have licenses and I have been able to get a Client Anyconnect VPN set up on one set of firewall.

Any help with be much appreciated.

See attached Config Files (I have removed some information from the configuration but nothing related to the VPN)


May need to go over again but

May need to go over again but the VPN looks OK. I have had this issue before when testing and needed a default route on the outside interface or routes for the specific blocks on the outside. I know the VPN endpoints in your example are in the same subnet but blocks you wish to tunnel over the VPN are obviously not and therefore technically on the outside interface even though they will get encapsulated/tunneled. The order of operation is the ASA will do a route lookup early on before VPN and if no route exists it will drop the packet. This sounds odd as you're not planning to route the interesting traffic directly out the outside interface but until the VPN/encryption process to encapsulate this traffic it's no idea what to do with the packet.


CreatePlease to create content
Content for Community-Ad
FusionCharts will render here