[c-nsp] Freezing counters at 6500

[Tony]

Depending on what software you're using to monitor with you might look into whether it supports "filtering" values retrieved via SNMP to within a sane range that you configure ? 

Eg. On an E1 interface the maximum should only ever be 2048Kbps so it is ok to discard anything with a value greater than that as being a wrong value. To be safe usually we would configure it a little above the theoretical maximum, so maybe 2500Kbps in this example.

The solution you are looking for is on the SNMP software side, not the router.


regards,
Tony


--- On Wed, 29/7/09, Grzegorz Janoszka <Grzegorz at Janoszka.pl> wrote:

> From: Grzegorz Janoszka <Grzegorz at Janoszka.pl>
> Subject: [c-nsp] Freezing counters at 6500
> To: cisco-nsp at puck.nether.net
> Date: Wednesday, 29 July, 2009, 7:14 AM
> 
> Hi,
> 
> We have several 6500's, some of them heavily loaded. We use
> snmp to graph traffic on all interfaces - just the simplest
> solution. Since some time we have had an issue with the
> interface counters. When the CPU box is really loaded
> (usually synchronization of BGP sessions), the counters just
> freeze. The important thing is that only the displaying
> freezes, the counters are still counting. Both snmp and
> 'show interface' data is frozen and does not update for
> various time - from 30 seconds to 3-4 minutes. As the result
> we have spikes on graphs - there is always spike down, when
> snmp gives frozen data from the past, and after that spike
> up, when the counters unlock and start displaying correct
> data.
> 
> Have you had similar problems? It is not the big issue,
> only the graphs look not so nice with the rows of spikes
> down/up. If there is a simple solution to the problem we
> would like to know it.
> 
> Kind regards,
> 
> -- Grzegorz Janoszka