Hi,
I am now using the IPMI plugin for HPI and noticed that the assertion value
in the threshold based sensor event is not correctly set.
The setting now is carried out this way:
in [plugin/ipmi/ipmi_sensor_event.c]:
set_thresholed_sensor_event_state:
if ((dir == IPMI_ASSERTION && high_low == IPMI_GOING_HIGH) ||
(dir == IPMI_DEASSERTION && high_low == IPMI_GOING_LOW))
event->Assertion = SAHPI_TRUE;
else if ((dir == IPMI_ASSERTION && high_low == IPMI_GOING_LOW) ||
(dir == IPMI_DEASSERTION && high_low == IPMI_GOING_HIGH))
event->Assertion = SAHPI_FALSE;
But according to the "Table 6-10. Mapping the HPI Sensor event to IPMI Event
Request Message" in Service AvailabilityTM Forum HPI-to-AdvancedTCA(R)
Mapping Specification, the mapping should be:
Assertion <--> Event Dir: 0b => SAHPI_TRUE; 1b=>
SAHPI_FALSE.
In fact those in IPMI that generate IPMI event should have set the Event Dir
correctly according to the IPMI specification, so it is not necessary to set
the assertion by taking into accout the GOING_HIGH or GOING_LOW.
I also found that this has been reported as a bug in impidirect and was
fixed:
[ 1230835 ] Wrong assertion value in threshold based sensors events.
Dose anyone know if it is the same problem as that in ipmidirect and should
it be fixed the same way as that in ipmidirect?
Jason HU
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
