Logic looks the same. But you should understand that the polling doesn't work in true deltas. The way it works is that a snapshot is taken when the policy is first registered. Then, each poll will check the current value to that initial snapshot. When the delta equals 100 (in your case) then the event fires and a new snapshot is taken. This means that a snapshot will NOT NECESSARILY be taken after each polling interval. Hopefully that will help demystify some of this with what you're seeing.
Thanks, Joseph. As usual, you were spot on. Both of the proposed scripts shown above work, but I wasn't aware of the behavior you described. Things were getting screwed up anytime I cleared the interface counters. To combat this, I wrote a script to 're-register' my dirty circuit script anytime the counters were cleared:
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...