I posted this in a different forum but probably should have posted it here instead. I have run into an interesting issue with the 3000 series concentrators. It has happened on a 3030 several times and just recently to a 3005. Whenever the concentrator loses physical connectivity, when the connection comes back, the concentrator needs to be rebooted to get it back online. I've had this happen to the 3030 a couple of times when I've had to reboot the core switch it is connected to for an upgrade or whatever. The 3005 got moved to a new core switch over the weekend and it had to be rebooted to be usable. Not sure if this is by design or if there is some inherent flaw in the code that causes this to happen. It's not a big deal because it only takes it a matter of seconds to come back up and be available but I would be interested to know if others have had this issue and why it is this way?
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...