Using an acl with log like this is drawing heavy on the CPU because there are many cycles involved in handling a packet. Your DS3 will handle a lot more traffic than the CPU can handle. In this case I presume that subsequent packets are by-passed in one way or another and listed as "missed" i.e. not processed by the acl/logger.
It would be better to attempt to capture the traffic with an packet analyzer (wireshark) and get your information that way.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...