Host IPMI System Event Log Status

[thinks2much]

I have an IBM BladeCenter S chassis with three HS22 blade servers, each with embedded hypervisors that have been upgraded to ESXi 4.1, 260247.

I'm running vCenter 4.1, 258902

When adding hosts to vCenter, each of them appears with a Red Alert, which seems to be related to these Events.

Alarm 'Host IPMI System Event Log Status' on server changed from Grey to Red

Alarm 'Host IPMI System Event Log Status' on server triggered an action

Alarm 'Host IPMI System Event Log Status': an SNMP trap for entity server was sent

How can I find out further information about what these messages mean?

Thanks,

k.

[bverm]

I've got the exact same issue, with a Sun blade chassis. Did you ever find out what it meant?

Regards,

Bram

[thinks2much]

Yes i did work it out:

I should have read the description of the Alarm definition more clearly - there it states "See the host's Hardware Status Tab for more details".

In that tab it showed that the System Event Log (reported by the IPMI SEL Sensor) was full. Resetting the event log and then resetting the sensors removed the alarm.

In my environment this was caused by firmware updates of the blade server filling the event log up with nonsense messages.

[tu_ha]

Hi,

Can you show me how to resetting the event log? Where event log ?

Thanks

[tu_ha]

I found them in Tab Hardware Status of vCenter.

If you access Hardware Status tab displays the error : "An error occurred, please try again in another vSphere session" you can fix follow this link : http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101421...

Thanks .

-

---

Blog Virtualization Technology in Vietnam

http://congngheaohoa.blogspot.com

[sasser1970]

Thanks for solution "[~173377]", i have the same error but no more :smileysilly:

[cypherx]

Hi, I am having this on 2 dell poweredge r710's.  I reset the sensors and the alarm goes away for awhile but it just keeps coming back.  Any ideas?

I have 2 new r620's due to arrive friday.  Depending how late in the day they arrive, if I can get them loaded and added to my cluster, I can then vmotion stuff to them and reboot the poweredge servers.  I also noticed I cant access the DRAC any more on our R710's.  I think it was a result of internal penetration testing and maybe their tools confused and froze up the DRAC's.

We really outgrew our vmware infrastructure so I don't have enough resources to vmotion things without causing outages until our 2 new servers come in.

[souperstar]

I'm having the same issue with one Dell R620, the other two are fine.  It simply has a hardware status of "unknown" on everything but CPU.  Did you find any resolve cypherx?  Did a reboot of the host fix the issue?

I wonder if there is an ESXi service that could be restarted to fix the issue without a host reboot.  I think some management services could be restarted to fix this, maybe.