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.

Description of problem:
sysObjectID can be configured in /etc/snmp/snmpd.conf.  However, if you set it to an OID with a length greater than 10 (the default value's length), it only reports the first 10 digits.  For example, the default value is ".1.3.6.1.4.1.8072.3.2.10".  If you change it to ".1.3.6.1.4.1.9.8.7.6.5.4.3", the agent will only report ".1.3.6.1.4.1.9.8.7.6".

Version-Release number of selected component (if applicable):
net-snmp-5.5-37.el6_2.1.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Edit /etc/snmp/snmpd.conf, and add a line to specify the sysObjectID - something like "sysObjectID .1.3.6.1.4.1.9.8.7.6.5.4.3"
2. Restart the agent
3. Query the sysObjectId
  
Actual results:
The agent will return the specified OID truncated to ".1.3.6.1.4.1.9.8.7.6"

Expected results:
The agent should return the whole OID as specified in the config file.

Additional info:
Here is the link to the net-snmp git repository with the patch that fixes it:
http://net-snmp.git.sourceforge.net/git/gitweb.cgi?p=net-snmp/net-snmp;a=commit;h=beff228a976472e53d67e56f7e820cb3eb411639

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Before this release, length of OID parameter of "sysObjectID"  snmpd.conf config file option was not correctly stored in snmpd, which resulted in SNMPv2-MIB::sysObjectID being truncated if the OID had more than 10 components. In this update, handling of the length of the OID is fixed and SNMPv2-MIB::sysObjectID is returned correctly.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2012-0876.html