Bug 1703752

Summary:	UCD-SNMP-MIB uses INTEGER32 instead of COUNTER64 for memory OIDs which limits to 2TiB
Product:	Red Hat Enterprise Linux 7	Reporter:	Chris Cheney <ccheney>
Component:	net-snmp	Assignee:	Josef Ridky <jridky>
Status:	CLOSED ERRATA	QA Contact:	David Jež <djez>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.6	CC:	apmukher, djez, grbrown, ovasik
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:	net-snmp-5.7.2-44.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-31 19:54:44 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:
Bug Blocks:	1716965

Description Chris Cheney 2019-04-28 06:26:15 UTC

UCD-SNMP-MIB uses INTEGER32 instead of COUNTER64 for memory OIDs which limits the reporting to 2 TiB (using KiB as the base).

Large modern servers often contain more than 2 TiB of memory leading to the OIDs rolling over and reporting negative values.

http://www.net-snmp.org/docs/mibs/ucdavis.html

Comment 2 Josef Ridky 2019-04-29 13:11:27 UTC

We can't modify any value from UCD-SNMP-MIB, due this MIB isn't owned by Red Hat (owner is U.C.Davis, ECE Dept.).

Unless owner will change it to Counter64, we can't do it as downstream patch.

Comment 6 Josef Ridky 2019-05-20 09:10:21 UTC

From upstream, this issue has been resolved by adding new <var>X values. (See https://github.com/net-snmp/net-snmp/blob/master/mibs/UCD-SNMP-MIB.txt#L642) 

This change is available in Fedora and RHEL-8 already. I'll prepare patch for RHEL-7.8.

Comment 7 Josef Ridky 2019-08-14 09:56:31 UTC

Commit: http://pkgs.devel.redhat.com/cgit/rpms/net-snmp/commit/?h=rhel-7.8&id=c0b4f3bdec4f46ff49ffdaf3230305e8868ea175

Comment 11 errata-xmlrpc 2020-03-31 19:54:44 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://access.redhat.com/errata/RHSA-2020:1081