Bug 193088 - net-snmp (snmp v2) 64bit counters not working
net-snmp (snmp v2) 64bit counters not working
Status: CLOSED DUPLICATE of bug 158630
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: net-snmp (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Radek Vokal
Depends On:
  Show dependency treegraph
Reported: 2006-05-25 01:49 EDT by David Ash
Modified: 2008-08-02 19:40 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-07-20 01:30:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Ash 2006-05-25 01:49:25 EDT
Description of problem:
Using snmp with cacti on gigabit network using 64bit counters doesn't graph
correctly.  Tried using the original RHEL4 U0 version and upgrading to the
latest net-snmp-5.1.2-11 but still failing.  Works successfully when compiling
netsnmp with:
--enable-mfd-rewrites.  I can't find this anywhere in net-snmp SPEC file or
source however so not sure what it does.

Version-Release number of selected component (if applicable):
net-snmp-5.1.2-11 (as well as original U0 version)

How reproducible:
net-snmp with cacti

Steps to Reproduce:
Actual results:
Graphs incorrectly without recompile, but graphs correctly when recompiled with

Expected results:
Not have to recompile.

Additional info:
Not sure if it is a bug as I've heard people using snmp v2 with mrtg but need
confirmation that "--enable-mfd-rewrites" isn't something missing in redhat
release of net-snmp.
Comment 1 Radek Vokal 2006-05-25 05:15:09 EDT
Are you sure that --enable-mfd-rewrites is in net-snmp-5.1.2? I thought it was
added later, in net-snmp-5.2.x and above.
Comment 2 David Ash 2006-07-20 01:30:04 EDT
Yes your right.  This bug looks to be a duplicate of 158630

*** This bug has been marked as a duplicate of 158630 ***

Note You need to log in before you can comment on or make changes to this bug.