01-09-2020 11:56 AM
We have a ASA 5585 firewall, running version 9.8(2)28 and we saw a strange issue. I configured a new IPsec tunnel, using ikev1. However, our partner was not ready so I configured everything but the PSK. Today, we noticed that an another active was down. The only update to firewall was above mentioned tunnel configuration. On the down active tunnel, both ikev1 and ikev2 were selected (viewing it via asdm). This tunnel was configured with ikev1. We fixed the issue by configuring the PSK on the new tunnel. Once PSK was configured on the new tunnel, the active tunnel came back online. huh? Not sure why that happened, there is not relation between these 2 tunnels as fare as I can see. Has anyone seen strange scenario like this? Please let me know if more info is required for clarity. thanks
01-09-2020 01:02 PM
01-13-2020 10:36 AM
RJI
We could not send any interesting traffic over the tunnel that was down. However, once we finished the configuration on the new tunnel, which was to add the psk to the tunnel group, the tunnel came up and was able to send interesting traffic.
01-13-2020 09:54 PM
If you are able to reproduce the issue, run a debug . We should be able to get a better idea of why it was failing from that.
IKEv1:
debug crypto condition peer x.x.x.x
debug crypto ikev1 127
debug crypto ipsec sa 127
IKEv2
debug crypto condition peer x.x.x.x
debug crypto ikev2 platform 127
debug crypto ikev2 protocol 127
01-09-2020 02:58 PM
This should definately not happen. I have preconfigured many site to site VPNs without having the issue you have described. Do you have a backup of the configuration when the issue was happening?
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