10-02-2019 06:08 PM
Hey Guys,
Might be a silly question, but i thought I would rather post this and get confirmation.
I currently have an ASA that is not reachable at the moment because we have set up an IPSEC tunnel as a temp workaround at the new site (long story).
This was done by my colleague and ever since then we are not able to get connectivity to the ASA but we are able to remotely connect to other device behind the ASA,
Looking at the config, it has the following:-
nat (INSIDE,OUTSIDE) source static net-INSIDE net-INSIDE destination static net-HQ net-HQ
I beleive its missing a route-lookup and a no-proxy-arp option at the end of the nat statement.
My question is, as this site is live and can't afford any downtime, will me adding the command route-lookup and no-proxy-arp at the end of the NAT cause any temporary outage?
Thanks.
Solved! Go to Solution.
10-03-2019 01:27 AM
Hello
Curious have you tired connecting to the FW via its tunnel addressing?
Can you post the config of the asa?
10-03-2019 01:27 AM
Hello
Curious have you tired connecting to the FW via its tunnel addressing?
Can you post the config of the asa?
11-07-2019 08:09 PM
Hi Paul,
Thats weird that i did not get an email saying that someone responded to my post.
Upon checking, the firewall on both ends did not have a tunnel IP assigned on each end.
That was the issue.
Thank you for guiding me to the right solution.
Regards,
Han
11-08-2019 01:31 AM - edited 11-08-2019 01:31 AM
Hello
Glad to hear your issue is now sorted
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