04-04-2016 05:27 AM - edited 03-12-2019 12:34 AM
I have updated ASA ver 9.1 from 8.2. After copying the config in asdm I found out that all the NAT statements was missing hence tried to configure NAT. But struggled due to new format of commands. After configuring the NAT I tried to establish Site to site vpn tunnel with our main firewall but unsuccessful, not sure if its due to NAT or the tunnel configuration. Have copied the old config in 8.2 and the new config in 9.1.
Please somebody help me if I have configured it wrong.
Thanks in advance
Sana
Solved! Go to Solution.
04-04-2016 10:03 AM
Hi,
I do not think there is any config issue here.
Could you turn on the debugs on the ASA :
debug crypto ikev1 200
debug cry
Initiate traffic to the remote subnet and share the debugs.
Use
Regards,
Aditya
Please rate helpful posts and mark correct answers.
04-04-2016 10:03 AM
Hi,
I do not think there is any config issue here.
Could you turn on the debugs on the ASA :
debug crypto ikev1 200
debug cry
Initiate traffic to the remote subnet and share the debugs.
Use
Regards,
Aditya
Please rate helpful posts and mark correct answers.
04-04-2016 10:10 AM
Hi,
Can you please try changing your NAT statement to:
nat (inside,any) source static Inside Inside destination static sikker sikker no-proxy-arp route-lookup
CF
04-04-2016 10:14 AM
Hi roanlunner - I had the same problem last year, moving our L2L tunnels from 8.2 code to 8.6.
8.6 and higher has NAT statement changes. From personal experience, I would suggest you use ASDM on the new 8.6 for atleast one tunnel to see what the CLI difference is.
HTH,
Rez
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