We have a L2L VPN from our corporate office to a remote office which the remote office has an ASA 5510 with version 8.2. The VPN is working fine but because the broadband at the remote office is no longer sufficient for a new project which is to transfer medical images from the remote to the corporate office, a 100Mb point-to-point circuit was installed. The goal is to have all traffic destined to the corporate office network (10.0.0.0) to use the 100Mb line and vice-versa to the remote office (192.168.50.0) while keeping the existing VPN as a backup to the 100Mb circuit.
I’m not sure where to begin for the configuration at the remote office for it to use the VPN as a backup and the 100Mb circuit as primary so I appreciate any help.
SLA Monitor (Route Tracking) is the solution on the remote office side but on the corporate side we have to change the routing manually if the point-to-point circuit goes down. This is doable as the office won't be without connectivity for long and their hours are normal business hours so the manual change on the corporate side is not a problem.
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...