Hello there, Thank you for your replay.
On 1/26/12 5:14 PM, Robert Story wrote: > On Thu, 26 Jan 2012 12:31:55 +0200 Hristo wrote: > HH> I'm running a Debian based rtg snmp poller. As a polling daemon rtg > HH> lives on top of libsnmp (I'll list exact versions later in the message). > HH> The system was in fine working condition for a long time. > > Has anything changed, software wise? Like an update of snmp on either the > polling machine, or the machines being polled? nop, nothing. Actually we had flawlessly working install for year and more. The host and polling daemon were not restarted during that time. > > HH> Next Poll: 10...*** Counter Wrap > HH> ([email protected]) [poll: 190447615][last: > HH> 3788532698][insert: 696882212] > > This looks like a normal wrap.. Yep, exactly. > > HH> *** Counter Wrap ([email protected]) [poll: > HH> 2864663][last: 43611440][insert: 18446744073668804838] > > This does not.. It looks like a 32bit value that got sign-extended. The > question is, is that happening on the remote agent or on the poller side. Well, I'm willing to blame SNMP implementation on the devices's side. But are there any tools in net-snmp projects, which analyze snmp network traffic? > > HH> No log handling enabled - turning on stderr logging > HH> truncating signed value to 32 bits (10) > HH> truncating signed value to 32 bits (10) > HH> truncating signed value to 32 bits (10) > HH> truncating signed value to 32 bits (10) > HH> truncating signed value to 32 bits (10) > HH> truncating signed value to 32 bits (10) > HH> truncating signed value to 32 bits (10) > HH> === snip === > > HH> === snip === > HH> rtg:/home/lisp/work/c/net-snmp-5.4.1~dfsg > > 5.4.1 is not the most recent in that line. I'd suggest updating to at least > 5.4.4. Yep, I'll do so on next update cycle. > > # egrep -r 'truncating signed > HH> value to 32 bits' . > HH> ./snmplib/asn1.c: snmp_log(LOG_ERR,"truncating signed value > HH> to 32 bits (%d)\n",y); \ > HH> ./man/netsnmp_asn1_packet_parse.3: > HH> snmp_log(LOG_ERR,'truncating signed value to 32 bits (%d)\n',y); \ > HH> rtg:/home/lisp/work/c/net-snmp-5.4.1~dfsg# > HH> === snip === > HH> > HH> I'm not so familiar with SNMP protocol internals, more I'm a regular C > HH> API user :). Due to my understanding CHECK_OVERFLOW_S macros make a > HH> integer underflow/overflow check. Is that right? > > Yes, a SNMP Integer is 32 bits. The bad wrap above is for a Counter64, which > in SNMP is two 32 bit values representing the high/low portions of a 64 bit > value. > Understood. One more question about this issue? I did not find any values for x inside debug log. Is that normal behavior? === snip === No log handling enabled - turning on stderr logging truncating signed value to 32 bits (10) truncating signed value to 32 bits (10) truncating signed value to 32 bits (10) === snip === Best regards Hristo ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
