I have a VPN 3060 with the most recent code on it. We added an IP for temp syslog machine to test functionality, as soon as that was verified we removed the IP for that syslog server from the 3060 so we could put in the IP of our production syslog server.
Well the 3060 has somehow held onto the ip for the temp Syslog server, which appears nowhere in the config, and is slamming the hell out of the temp Syslog server.
the 3060 is configured now for the production syslog server IP and it isnt seeing a single message from the 3060.
Is there a way to kill a process on the 3060? Maybe restart the syslog deamon on the 3060?
We would really like to avoid a full blown boot of the 3060 as we currently run well over 400 tunnels.
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...