We have been seeing these as well, and VMware suggested I contact HP. I had already upgraded the iLO formware to 2.25. They have stated in no uncertain terms, though cannot provide any bulletin (or the like) to support their view, that these messages 'can be safely ignored'.
This is the actual text from HP support:
As discussed with you over the phone, the below mentioned messages that we are getting are only informational and the same could be ignored.
The below mentioned messages would not have any impact on the server’s performance hence the same could be ignored.
I haven't found a fix for this, but I do have a theory ... I only see this on my older HP DL585 G6 (with ILO 2's), and don't see the same on my newer HP DL380p Gen8 servers (with ILO 4's).
These are the log entries I was concerned about;
2014-07-14T15:56:24.054Z cpu18:9601)<3>hpilo 0000:01:04.2: Open could not dequeue a packet
2014-07-14T15:58:48.412Z cpu23:8215)<4>hpsa 0000:02:00.0: cp 0x41002040a000 has status 0x2 Sense: 0x5, ASC: 0x24, ASCQ: 0x0, Returning result: 0x2
My assumption at the moment is that the current / latest HP management agents are not designed to work with older ILO 2's or have some functionality that only works with newer ILO 3/4's?? I'm yet to log this to HP as I have heaps of other priorities and these hosts will be refreshed in 6 months anyway. I would obviously like to understand what is going on here, so please let me know if you find anything before I do - thanks.