Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm testing out a Cisco SA520W for some remote retail locations we manage.

The one thing that is currently holding me back on it is I haven't found a way to set the VPN connection to connect when the device comes on, or better yet to "always have it up" to where if it loses the connection it tries to re-open it.

I can live with it just coming up on boot as the users on site are typically familiar with power cycling the firewall before calling in with issues.

The IPSec VPN comes up and functions fine, but has to be done so manually.

share|improve this question
up vote 2 down vote accepted

From my experience, Cisco devices won't preemptively initiate IPsec connections until it sees some traffic destined for the remote subnet on the other end of the VPN.

Have you tried just pinging across the VPN tunnel? That should force it to start up.

share|improve this answer
I will give that a try to see, it might be enough. However, the communication won't always be initiated from the network that is behind the Cisco firewall. – ManiacZX Nov 3 '10 at 0:19
What I've done in similar circumstances is just have use cron or a scheduled task to sind a single ping through the VPN, one host in each direction, once per minute. That should take care of keeping the tunnel up as well as getting it established again following an outage. – EEAA Nov 3 '10 at 0:23
It does look like it brings up the tunnel when traffic destined for that network arises. – ManiacZX Nov 3 '10 at 15:45

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.