On Fri, Feb 10, 2012 at 3:53 PM, Doug Manley wrote:
> In any case, I patched my net-snmp to always leave SNMP_USE_TIMES
> undefined, and I am 99% certain that my change will fix the crazy
> issues that I've been seeing. I'd be interested to see how this patch
> performs in my situation.
>
In ca
On Fri, Feb 10, 2012 at 7:16 PM, Bart Van Assche wrote:
> However, I found this in RFC 3414 (http://tools.ietf.org/html/rfc3414):
>
>When an SNMP engine is first installed, it sets its local values of
>snmpEngineBoots and snmpEngineTime to zero. If snmpEngineTime ever
>reaches its ma
On Fri, Feb 10, 2012 at 3:53 PM, Doug Manley wrote:
> After weeks of testing, we concluded this:
> 1. It had something to do with net-snmp; the memory was not getting
> clobbered by anything else.
> 2. It had something to do with the fact that we would send out a
> msgAuthoritativeEngineTime with
> On Fri, Feb 3, 2012 at 8:47 AM, Bart Van Assche wrote:
>> It is known that backwards and forwards adjustments of the system clock can
>> cause snmpd and libsnmp to behave different than documented. The patch below
>> addresses this. Because of the impact of this patch (it changes the ABI
>> some
Hi all,
I have 2 questions regarding UDS in SNMP:
1. Does SNMP ( any version ) support abstract names? if so, from which
version? and how they are configured?
Note: UDS abstract name is a UDS socket which is opened in the process
memory rather than as a file path.
2. snmpd opens /etc/snmptrap UDS.
