12-21-2023 02:18 PM
Hi all,
I have a s2s tunnel going to Azure and it is up and functioning. The azure team wants a secondary tunnel up going to their other gateway for redundancy. I copied the exact same configuration over from the primary tunnel but the tunnel interface is staying down/down. This is the debug I was getting, I noticed errors at the bottom as "Auth Exchange Failed" and "Failed to receive the AUTH msg before the timer expired". I was thinking it may have to do with PSK, but we verified the PSK was the same on both sides (I applied it to the tunnel-group, not a key ring, not sure if that's necessary). I copied the config exactly as its done, which was based off of this guide https://www.petenetlive.com/KB/Article/0001515.
The debug I received is this attached. Any help is appreciated.
12-21-2023 11:35 PM
You use same Azure destination IP for both tunnels?
MHM
12-21-2023 11:56 PM
Hope either side you have 2 different Public IP address
is the ASA directly connected to internet or behind NAT ?
IKEv2-PROTO-2: (1001): Auth exchange failed - check the configuration again. ?
look below VPN guide from Azure :
https://learn.microsoft.com/en-us/azure/vpn-gateway/vpn-gateway-activeactive-rm-powershell
Hope you may have already cisco document - just for reference :
12-23-2023 12:39 PM
Copy exact config is ok for policy proposals but not for key and profile.
The IP must change.
MHM
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