Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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 1070076

Summary:	SNMP HRPROCESSORLOAD RETURNS INCORRECT VALUES FOR PROCESSOR #'S > 100
Product:	Red Hat Enterprise Linux 7	Reporter:	Jan Safranek <jsafrane>
Component:	net-snmp	Assignee:	Jan Safranek <jsafrane>
Status:	CLOSED ERRATA	QA Contact:	Dalibor Pospíšil <dapospis>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	dapospis, jianhai.luan, joe.jin, ksrot, lmiksik
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: When reading CPU statistics, snmpd daemon did not expect that the CPU number can have more than two digits. Consequence: snmpd did not show more than 100 processors in HOST-RESOURCES-MIB::hrProcessorTable. Fix: snmpd now does not have any assumption about CPU ID length. Result: All CPUs are shown in HOST-RESOURCES-MIB::hrProcessorTable.	Story Points:	---
Clone Of:	1069979	Environment:
Last Closed:	2015-03-05 08:38:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1069979
Bug Blocks:	1070075

Description Jan Safranek 2014-02-26 08:22:15 UTC

+++ This bug was initially created as a clone of Bug #1069979 +++

Description of problem:
using snmp monitor cpu usage with more than 100 processors. hrProcessorLoad will returns incorrect values for processor #'s > 100

Version-Release number of selected component (if applicable):
RHEL 5.x RHEL 6.x

How reproducible:

Steps to Reproduce:
1. using snmp monitor cpu usage with more than 100 processors.

Actual results:
hrProcessorLoad will return incorrect values for processor #'s

Expected results:
hrProcessorLoad will return correct values for processor #'s (letter than 100)

Additional info:
http://mailing.unix.net-snmp-users.narkive.com/o21D50GY/hrprocessorload-returns-incorrect-values-for-processor-s-100

The file agent/mibgroup/hardware/cpu/cpu_linux.c: netsnmp_cpu_arch_load() use below  hard code to skip cpuN
  b1 = b2+5; /* Skip "cpuN " */

When processor more than 100, the value will be wrong.

--- Additional comment from Luan Jianhai on 2014-02-25 21:41:40 EST ---

The patch have be applied to net-snmp upstream:
  http://git.code.sf.net/p/net-snmp/code: 
commit eef2f64b46357b353c79504bc593535ebe7421e7
Author: Niels Baggesen <nba.net>
Date:   Thu Jan 23 16:27:07 2014 +0100

    cpu_linux: support systems with more than 100 cpus.

Comment 7 errata-xmlrpc 2015-03-05 08:38:21 UTC

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.

https://rhn.redhat.com/errata/RHBA-2015-0607.html