Scenario: 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# SiteA# conf t SiteA(config)# crypto map outside_map0 set peer 126.96.36.199
So if I add the main secondary i would run this command:
SiteA(config)# crypto map outside_map0 set peer 188.8.131.52 184.108.40.206
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.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
[toc:faq]Introduction:This document describes details on how NAT-T
works.Background:ESP encrypts all critical information, encapsulating
the entire inner TCP/UDP datagram within an ESP header. ESP is an IP
protocol in the same sense that TCP and UDP are I...