The message is seen when some packet-matching logs were missed because the access list log messages were rate limited, or no access list log buffers were available.
The problem here is that your switch is receiving too much traffic at the same time and he is not able to log every packet. The reason why it doesn't log them is to protect itself from crashing, because it takes processor usage to handle the ACLs logs.
Now we have two solutions for this log message:
1) If you want to disable the messages you need to erase the log keyword from the ACL
statements. (the keyword log :Logs a packet when it matches the ACE)
2)Increasing the amount of packets log (but that will decrease the performance of your
The logging of acl hits has always been rate limited, but before this enhancement all the packets for which we couldn't issue the log message were just 'forgotten about'. Now with this enhancement we count for how many packets we didn't issue syslog message. This is not configurable behaviour.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...