• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 319
  • Last Modified:

Changed ISPs on ASA - having problems with VPNs, etc.

Hi
We have a Cisco ASA 5510 at our main facility.  it's performing the following service:

- Gateway for the main facility to the internet
- Site to Site VPN tunnel to two other facilities (each one running an ASA 5505)
- Easy VPN setup to three remote facilities (easy one running an ASA 5505)
- Incoming Client VPNs
- NAT for internally hosted services (mail, etc)

We have a new ISP, and have to configure the ASA for the new ISP.  We switched the connections, and configured the interface and default route on the 5510 for the new connection.  Immediately traffic started flowing.

We then pointed the remote side of the site-to-sites at the new peer (new ISP at main facility), cleared crypto, and the tunnels re-established just fine.

We ran into a problem with the Easy VPNs though.  We pointed the clients at the new IP, but the tunnel wouldn't re-establish.  We restarted several of the endpoint ASA 5505s, but no avail.

Note that throughout this, we never restarted the ASA 5510.  The reason was so we could reload it and go back to saved config if we had to.

I tried the NAT,and that didnt' seem to work either, but before i could troubleshoot more, we'd reached our maintenance window, and had to revert back to the old connection for now.

I'm curious if anyone has any suggestions.  Obviously the public IP of the ASA must have been accessible for the site to sites to come back up, but yet although the Easy VPNs use the same IP, they wouldn't establish.

Anyone have any suggestions?
What troubleshooting points can i walk through?  I wasn't sure what logging i could turn on to try to find out why it wasn't working.
Also any suggestions as to testing NAT, and why it wasn't working.  I'm wondering if something may be blocking it on the ISP's equipment?
0
Mystical_Ice
Asked:
Mystical_Ice
2 Solutions
 
TimotiStCommented:
Are the working VPNs using NAT-T, while the non-working ones don't? The ISP might block ESP/AH (which is plain dumb, but sometimes happens).
0
 
Henk van AchterbergCommented:
why don't you write the current config to disk0 and reload the ASA?

You can also prepare the changes of the new ISP in a config, put it on disk0.

When you are ready to switch just issue:

copy running-config disk0:/old.isp.config
copy disk0:/new.isp.config startup-config
reload

when it fails just revert:

copy disk0:/old.isp.config startup-config
reload

Are you sure the speed and duplex settings are correct for the new ISP? I have had issues before where the new ISP had 100/full fixed instead of auto.

You can enable logging to ASDM on informational level, this should give a good idea if remote easy vpn connections are coming in.
0
 
Mystical_IceAuthor Commented:
Thanks all for the advice.  It turns out there was a firewall still turned on on the cable modem, which may have had something to do with it.

Tried it again and it worked fine
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now