I'm curious if anyone who has enabled port-security has experienced this issue. I've enabled port-security on some distribution switches. Two of those switches are connected for redundancy. On a few occassions, I have seen port-security errors crop up on those switches that don't make sense. For example, I've seen a violation error come up on both of those switches, at the same time, for a device that is actually plugged into an access switch's port. I know for sure that the violating device wasn't plugged into these two distribution ports simultaneously. I also know for sure that the device was never moved off of the access switch. So why would the distribution switches report a violation? Could this be because of some STP change? Bug? Something else?
True. But what if the violating device was never plugged into the switch's port? Why would I be seeing a mac address on a port, causing port-security's violation mode to trigger, when the physical connection to that port hasn't changed? ARP table corruption? Flapping? If it was a consistent problem I'd have a better idea and more to offer. But I appreciate the input.
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...