We use ASA firewall at many of our offices to provide S-S IPSEC VPN connectivity to our customers.Typically we need to establish S-S vpn to two different sites at customer end, one being primary and other being backup.Both tunnels need to have the same VPN parameters including encryption domain.Offcourse, the only difference between the tunnels will be peer ip.We build VPN config just by adding the backup peer ip in the same crypto map.The failover doesnt work automatically. Even if the primary tunnel goes down, the backup tunnel doesnt get established and traffic dont pass through it.The firewall has only static route for peer ip's. Please suggest if there is a better way to handle VPN failover for the above requirement.
Thanks in advance.
crypto map ciscovpn 1 match address ciscoacl
crypto map ciscovpn 1 set peer 184.108.40.206 <<PRIMARY PEER>>
crypto map ciscovpn 1 set peer 220.127.116.11 <<BACKUP PEER>>
crypto map ciscovpn 1 set transform-set ciscocts
crypto map ciscovpn 1 set security-association lifetime seconds 28800
crypto map ciscovpn 1 set security-association lifetime kilobytes 4608000
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...
Table of Contents 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 an...