Bug 1252053
| Summary: | net-snmp does not display correct lm_sensors sensor data / missing CPU cores | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Dalibor Pospíšil <dapospis> |
| Component: | net-snmp | Assignee: | Jan Safranek <jsafrane> |
| Status: | CLOSED ERRATA | QA Contact: | Dalibor Pospíšil <dapospis> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.1 | ||
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause:
snmpd expected, that sensor names reported by lm_sensors library are unique. However, on systems with multiple sockets with Xeon family CPUs, the thermal sensors on all CPUs have the same name.
Consequence:
snmpd reported temperature only of one CPU.
Fix:
snmpd adds prefix to all sensors, that have the same name.
Result:
snmpd reports temperature of all CPUs.
For example, on 2-socket machine with two-core CPUs, the old snmpd reported just two thermal sensors (from the first CPU) in LM-SENSORS-MIB::lmTempSensorsTable:
lmTempSensorsDevice.2 = STRING: Core 0
lmTempSensorsDevice.3 = STRING: Core 1
With this update, all four thermal sensors are reported. Notice the prefix of second set of sensor names:
lmTempSensorsDevice.2 = STRING: Core 0
lmTempSensorsDevice.3 = STRING: Core 1
lmTempSensorsDevice.6 = STRING: coretemp-isa-0004:Core 0
lmTempSensorsDevice.7 = STRING: coretemp-isa-0004:Core 1
The first set of sensors is kept without prefix to keep compatibility with old applications, which may expect sensor named 'Core 0'.
|
Story Points: | --- |
| Clone Of: | 967871 | Environment: | |
| Last Closed: | 2015-11-19 11:46:14 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: | |||
|
Description
Dalibor Pospíšil
2015-08-10 14:48:53 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/RHSA-2015-2345.html |