RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 641113 - snmpd always returns an incorrect sysObjectID of ".1.3" or ".0.1"
Summary: snmpd always returns an incorrect sysObjectID of ".1.3" or ".0.1"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: net-snmp
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Jan Safranek
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 652223
TreeView+ depends on / blocked
 
Reported: 2010-10-07 19:09 UTC by Jeff Gehlbach
Modified: 2018-10-27 11:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 640848
Environment:
Last Closed: 2011-05-19 14:13:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 640848 0 low CLOSED snmpd always returns an incorrect sysObjectID of ".1.3" or ".0.1" 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHBA-2011:0729 0 normal SHIPPED_LIVE net-snmp bug fix update 2011-05-18 18:09:25 UTC

Internal Links: 640848

Description Jeff Gehlbach 2010-10-07 19:09:39 UTC 
+++ This bug was initially created as a clone of Bug #640848 +++

Description of problem:
The "sysObjectID" scalar MIB object (.1.3.6.1.2.1.1.2.0) conveys what kind of device one is talking to via SNMP.  The correct value for a Net-SNMP agent on GNU/Linux is ".1.3.6.1.4.1.8072.3.2.10", but a bug in the Net-SNMP 5.5 code causes this value always to be truncated to ".1.3" on i386 or ".0.1" on x86_64.  The result is that SNMP management applications (e.g. OpenNMS) are unable to determine from the sysObjectID that they're in fact talking to a Net-SNMP agent at all, let alone one running on Linux.

Version-Release number of selected component (if applicable):
5.5-23 (and all previous releases of 5.5)

How reproducible:
Always

Steps to Reproduce:
1. Install package "net-snmp" and start service "snmpd"
2. Run "snmpget -On -v1 -c public localhost sysObjectID.0"
  
Actual results:
[root@rhel6b2 ~]# snmpget -On -v1 -c public localhost sysObjectID.0
.1.3.6.1.2.1.1.2.0 = OID: .0.1

Expected results:
[jeffg@mephesto ~]$ snmpget -On -v1 -c public localhost sysObjectID.0
.1.3.6.1.2.1.1.2.0 = OID: .1.3.6.1.4.1.8072.3.2.10


Additional info:


[root@rhel6b2 ~]# rpm -q net-snmp
net-snmp-5.5-23.el6.x86_64

This bug is fixed in upstream Subversion trunk and upstream version 5.6 release candidates.  It's a one-line fix, which is attached as a proposed patch to bug 640848, from which this report was cloned.

This problem affects not just RHEL6 beta 2 as reported but also Fedora 13, Fedora 14 beta, and rawhide.

I'm happy to provide more information as needed; this is my first bug report against RHEL, so please let me know if I've broken any conventions.
Comment 2 Jeff Gehlbach 2010-10-07 23:19:22 UTC 
See Bug 640848 (comment number 5) for a patch that corrects this problem in Fedora 13 for release 12 of the same upstream version of this package; there's also a discussion of the reasoning for including and excluding what I did in that patch.  I'm checking now whether the same patch applies cleanly to package release 23.
Comment 3 Jeff Gehlbach 2010-10-08 13:37:37 UTC 
Verified that my proposed patch for Bug 640848 also applies cleanly and fixes the problem against release 23 of this package as included in RHEL6 beta 2.  Rather than attach that patch separately to this report (in case the patch should be obsoleted), please see Attachment 452222 [details].
Comment 4 Jeff Gehlbach 2010-10-15 21:12:09 UTC 
Setting this bug's Version to 6.0 -- not sure how it became set to 6.1, perhaps a mistake on my part.  The report is actually filed against 6.0 beta 2.

It's conceivable that the severity should also be bumped, as this problem renders many (most?) SNMP-based management platforms unable to identify a RHEL6 system as such, but I'm too new here to go mucking with that field.

In any case, I'd love to see this bug get the same kind of attention that its Fedora cousin (bug 640848) has seen.

Thanks for keeping it FaiF!

-jeff
Comment 12 Jeff Gehlbach 2010-11-15 14:10:31 UTC 
Hi Jan,

Congratulations to you and the whole RHEL team on getting 6.0 out the door :)

Can you explain to me the disposition of this bug?  I see that a copy of it got nominated for inclusion in ZStream; does that mean that the fix will never be included in the updates repo for non-ZStream RHN?  Sorry if that seems a stupid question; I'm just not that familiar with how the various streams fit together.

Thanks,
-jeff
Comment 13 Jan Safranek 2010-11-16 08:31:35 UTC 
(In reply to comment #12)
> Can you explain to me the disposition of this bug?  I see that a copy of it got
> nominated for inclusion in ZStream; does that mean that the fix will never be
> included in the updates repo for non-ZStream RHN?  Sorry if that seems a stupid
> question; I'm just not that familiar with how the various streams fit together.

Don't worry, the streams fit together very well and every customer gets all the updates in 6.1 at the latest. And this one should be released even earlier (and for everybody).
Comment 14 Jeff Gehlbach 2010-11-16 14:12:59 UTC 
Thank you, Jan!
Comment 17 errata-xmlrpc 2011-05-19 14:13:25 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0729.html
Note You need to log in before you can comment on or make changes to this bug.