Bug 174466 - Can't retrieve reliable values on 64 bits computer's mib with a 32 bits snmp client
Summary: Can't retrieve reliable values on 64 bits computer's mib with a 32 bits snmp ...
Keywords:
Status: CLOSED DUPLICATE of bug 174374
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: net-snmp
Version: 3.0
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Radek Vokál
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-11-29 12:19 UTC by saveline
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-11-29 12:25:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description saveline 2005-11-29 12:19:25 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; fr-FR; rv:1.7.12) Gecko/20050919 Firefox/1.0.7

Description of problem:
When I try to retrieve some values on my 64 bits box such as ifInOctets with a 32 bits snmp client, I get wrong values. But when I try to get it with another box like a 64 bits snmp client it seems ok.


Version-Release number of selected component (if applicable):
net-snmp-5.0.9

How reproducible:
Always

Steps to Reproduce:
1. snmpwalk -v 2c -c xxxxx xxxx .1.3.6.1.2.1.2.2.1
2.
3.
  

Actual Results:  IF-MIB::ifInOctets.1 = Counter32: 55192
IF-MIB::ifInOctets.2 = Counter32: 55192

Interface 1 is for lo and interface 2 is for eth0


Expected Results:  The ifInOctets.2 and the ifInOctets.1 should be different. And ifInOctets.2 should increase at each query.

Additional info:

As I said, this error appears when I try to query a 64 bits computer's mib with a 32 bits computer's snmp client.
On my 64 box I got net-snmp-5.0.9 and on my 32 bits snmp client I got the same version.
I got the same problem with 64 bits computers under RHEL 4 with net-snmp-5.1.2 .

Comment 1 Radek Vokál 2005-11-29 12:25:44 UTC

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


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