Hi,
We would like comments from the HP IPMI group before we make changes to the ESX
version of the IPMI driver in the OEM message handling behaviour.
The current version of the open source IPMI driver supports handling of OEM
messages. However the IPMI driver shipped with all versions of ESX since ESX
3.5 included support for handling OEM messages specifically for HP ILO OEM
messages.
In our implementation we were re-queuing the messages received at init back to
the queue for the OEM application to read once it is ready, which is not what
the open source version of the driver doing. The open source version of the
driver discards these messages.
We would like to know what the current implementation of the HP application is?
Does it still expect old messages to be available for processing once it is
initialized or is it adequate that only current messages are available? i.e.,
Is it okay if the ESX version of the IPMI driver mimics the open source driver
behaviour in handling OEM messages?
Regards,
Ashvin
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Openipmi-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openipmi-developer
