[erlang-patches] SNMP erlNodeReductions defined too narrow

Stefan Zegenhagen <>
Mon Jul 15 16:47:49 CEST 2013


Hi Tobias,

> However, I think extending this and probably some other values to a
> wider type is actually a good thing because providing a value that
> typically overflows within a few hours is quite meaningless. I would
> like to make another patch that actually fixes the problem but I'm not
> sure what the desired behaviour would be for a counter. Should it
> always reflect the highest valid value when overflowing or should it
> start over?

I only know this for network counters. Here the desired behaviour is
that the counter starts again from zero. If someone wants to get
accurate numbers from the device, he has to poll those counters in
regular intervals to detect overflows. The minimum time (in which the
counter can overflow) can easily be calculated from the link speed
(10/100/1000 MBit) here.

This behaviour sounds reasonable for other counters as well, especially
when there's no counter-reset MIB object.

Kind regards,

-- 
Dr. Stefan Zegenhagen

arcutronix GmbH
Garbsener Landstr. 10
30419 Hannover
Germany

Tel:   +49 511 277-2734
Fax:   +49 511 277-2709
Email: 
Web:   www.arcutronix.com

*Synchronize the Ethernet*

General Managers: Dipl. Ing. Juergen Schroeder, Dr. Josef Gfrerer -
Legal Form: GmbH, Registered office: Hannover, HRB 202442, Amtsgericht
Hannover; Ust-Id: DE257551767.

Please consider the environment before printing this message.



More information about the erlang-patches mailing list