[oh-tracker] [ openhpi-Bugs-3491218 ] Wrong sensor number may be in ipmidirect events

[SourceForge.net <no...@so...>]

Bugs item #3491218, was opened at 2012-02-22 10:58
Message generated for change (Comment added) made by avpak
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=532251&aid=3491218&group_id=71730

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: IPMI Direct plugin
Group: 3.0.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: David McKinley (davidmckinley)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong sensor number may be in ipmidirect events

Initial Comment:
When the ipmidirect plugin creates RDRs for sensors found in SDRs, it creates a "virtual sensor number" to use for the sensor in the RDR.  Typically, this is the same value as the sensor number found in the SDR, but if there are multiple sensors found in the SDR with the same sensor number (could happen if they have different LUNs, for example) then the "virtual sensor number" used in the RDR will be changed for one of them.

The problem is that when events are generated (both regular sensor events and sensor enable change events), the code puts the SDR sensor number in the HPI event instead of the virtual sensor number.  It should use the virtual sensor number, since that is how the sensor is known to the HPI user.

----------------------------------------------------------------------

>Comment By: Anton Pak (avpak)
Date: 2012-02-22 11:06

Message:
There is one more issue with the numbers.
IPMI Direct allows sensor virtual number be in range [0,255).
So the maximum number of IPMI sensors for a FRU resource is 256.
However IPMI limit is 768.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=532251&aid=3491218&group_id=71730