That's an interesting perspective. I also find CSCsm33227 that says "In 7.0(5), 7.1(2), 7.2(1), 8.0(1) and later software, the information available through SNMP is refreshed approximately every 5 seconds. Therefore, it is advised to wait for at least 5 seconds between consecutive polls." I read CSCsm32972 as just another way of describing this inherent limitation, in other words it's entirely due to the SNMP poller's behavior. But your interpretation seems to suggest something wrong on the PIX OS side, that the MIB counters are indeed stuck, as I've seen on our PIXes, triggered by overly frequent polling. For completeness, I should mention that we have one script that's been polling every 10 secs for months if not years, and an assortment of other tools that poll mostly in 5-min intervals. The ifInOctets/ifOutOctets on the management interface (light traffic) on these PIXes never stopped incrementing, while all the other active interfaces that are actually used for client traffic did. Can the problem still be attributed to the CSCsm32972 bug?
