I need to stop a site to site VPN between two ASA5505's. I don't want to remove all the configuration as I'll need to reinstate it once I've completed some client VPN testing from the remote site.
Would I need to alter configurations at both ends of the link or is it ok to leave one end trying but failing to establish the link.
Up to you really. If you remove the peer address, easiest thing, at one end only as you say the other end will still try to connect which takes up firewall resources and, some although very limited, bandwidth.
Cisco are currently donating money to the Haiti earthquake appeal for every rating so please consider rating all helpful posts.
I'll give that a go then, I was a bit worried about how much resource would be used at the fully configured end. As it's only for a test I think I'll give it a go.
Out of interest my problem is related to a client server application that is running very slowly via a site to site VPN, other engineers say they have not noticed any slowdown when the application is running via a client to site VPN.
Any suggestion on what could be different once the links have been established.
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...