How to reset HP Proliant memory sensor?

[LzN]

Hi all,

several weeks ago, on one of my HP servers I found a hardware problem with one of installed memory basket. After replacement, I tried to reset HP hardware sensor within ESXi (via vSphere Client). But I was not success. I still see the warning notification on this ESXi host.

After 'reset alarm to green' I fixed notification icon in vCenter hosts list, but unable to reset (or fix) warning in hardware status.

So, the simple question is "How I can fix this warning notification?"

Screenshot with mentioned warning below:

[SimonStrutt]

Hi,

If the warning doesn't clear once you've clicked on "Reset sensors" in the Hardware Status tab, or comes back after 5 mins, then there is probably something still wrong.

The info on this page comes from the HP CIM provider, so if you've got iLO, log into that and take a look around, though the available info can be a bit poor.  Alternatively you might need to take the ESX down and boot into the HP diagnostics (on the SmartStart CD) to see what's up.

[LzN]

This warning was not cleared after I click on "reset sensor".

When I connect directly to the ESXi (not via vCenter) in Configuration->Health status I see "green status" or "Normal". Also, when I connect to HP via iLO I also see normal responses from inventory, include memory.

I think this is problem with vCenter, but have no idea how to fix it.

[SimonStrutt]

In which case it sounds like you need to refresh the data through from the ESX to the vCentre to replace the dodgy data in the vCentre database.

Try restarting the ESX's managment agent, ie via SSH...

services.sh restart

If that doesn't work you can try disconnecting and reconnecting the ESX in vCentre.

If neither of these work you can get a bit more brutal and restart the vCenter Server service; or disconnect the ESX, remove it from the inventory, and them re-add it (make sure you know the ESX's root password and have your VM's off it 1st)

[LzN]

so, steps below didn't solve my problem:

1. ESXi was reconnected in vCenter (was removed and added as new host)
1. vCenter was restarted;
2. ESXi was restarted too;

and for now, i still see the warning in hardware status (via vSphere).

[SimonStrutt]

I'm not convinced that the vCenter and ESX are actually displaying exactly the same data, and so it might be possible that there is warning being reported by the server hardware, which isn't being displayed by the ESX, but is visible to the vCentre (???).

I'd probably suggest taking the ESX down, and performing the HP diagnostics to be absolutley sure that it isn't reporting any problems, assuming this doesn't turn up anything, open a support request to VMware to investigate.  There were some bugs in how vCentre handled hardware events, though all the ones I'd experienced (towards the end of last year) have been resolved - are you running a recent release of vCentre?

[SimonStrutt]

Having had an HP memory error recently, I suspect that your HP System Event Log isn't being cleared down and/or its not propagating through to the vCentre, with a bit of luck the following should resolve...

1. Go to Hardware Status tab, and select the  System event log view
2. Click on Reset event log, and allow to  complete
3. Click on Update, once complete the memory  error should clear
4. Select the Alerts and warnings view
5. Click on Reset sensors, and allow to  complete
6. Click on Update, once complete and the memory  error might clear
7. If not, SSH to the ESX and restart the management agents, eg for an ESXi server
   • services.sh restart
8. Click on Update again, and once complete the memory error should clear

[LzN]

Hi Simon,

after several days of inactivity, I tried to restart ESXi services today morning (via services.sh), and notification was cleared.

Many thanks.

[iforbes]

Thanks! That worked for me.

[petrovych]

+1 worked fo me

[RobinvdS]

Worked for me thx! :smileycool:

[yannigbeyet]

reset event log worked for me !

[vfk]

Yup the warning is just the event log filling up...resetting the event logs usually resolved the problem.

[asac74]

+1 worked fo me

[John_Nicholson1]

This worked for me too!  Unfortuanately, I called HP and we went thru a lot of hardware (repaced a cpu and a system board) before I found this post, but I am very thankful for this solution.  Thank you SimonStrutt!

[kniedzwiecki]

Has anyone found a root cause for this? On some of my 5.5U1 hosts, I'm seeing the issue crop up periodically. There are no issues in iLO/AHS/IML, just the vague memory warning for a subset of the memory DIMMs.

[Ras14]

Thanks Simon, reset of the event log and then sensors helped me