Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Site to Site VPN's 2 ISP network redundancy

I have a network with 5 ASA 5505. One site is home office (main) and the others are remote locations.
Currently all sites have two ISP's, a primary, and a secondary used for fail over.
All remote sites have a vpn configured to the main site's primary line. This is configured for both
primary and secondary ISP's for the remote sites to main site. The problem is if the main site goes down, there
are no tunnels configured to use main secondary line.
I need to add a peer ip to all remote sites to look for main site secondary line.
I need to configure main site to create tunnels to all remote sites using secondary line as primary is already up.
See diagram below.

I assume it would just be checking the crypto map of the remote and adding a peeer ip. Example existing:
SiteA# conf t
SiteA(config)# crypto map outside_map0  set peer

So if I add the main secondary i would run this command:

SiteA(config)# crypto map outside_map0  set peer

And the ASA remote should be looking for that ip. What about ACL and NAT for the new peer ip?

The main site has no configuration to use its secondary for any vpn tunnels. So on the main I need to create a new tunnel
and set the IP address.
Do I need a tunnel group for each IP or can I make a list?
What about ACL and NAT?

I thank you in advance for helping me think this through before implementing the changes.

  • VPN
Everyone's tags (3)
New Member

Site to Site VPN's 2 ISP network redundancy

This widget could not be displayed.