BMC IMPI Watchdog Timer Timeout Action: ASR. Why?

[BiEmme]

Our new HP Proliant DL 380 DL G6 server reboots itself ocassionally (approx. once a day or more).

ILO2 log entry says:
BMC IPMI Watchdog Timer Timeout: Action=System Power Reset.

We've followed all recomended steps (complete hardware check, firmware upgrade...), but without success.

Any suggestion?

[Jan Soska]

Hello,
could be issue with ILO management.
Have you checked your server log?
Are there any ID 57 errors pointing to ILO?
If yes - upgrade ILO2 firmware, ILO windows driver and ILO management driver, then reboot your server, should be OK.

Jan

[BiEmme]

No, there aren't any EventID 57 in event log.
We can only notice EventID 36, source Time-Service, and after that reboot occurs.

[Erdogan Temur]

Hi,

update the last version BIOS, iLO2 firmware and iLO2 driver.

Regards.
Erdogan.

[BiEmme]

ILO firmware and driver was already up to date. Today morning, we updated BIOS, too. However, we didn't expect any changes, since latest BIOS doesn't include any noticeable changes.

Today evening, we received two BMC IPMI Watchdog Timer Timeouts in just 20 minutes.
ASR occurs again.

System is up to date, we've checked everything twice.

[Jan Soska]

no idea,
I would rise a case to HP support... :(

jan

[BiEmme]

@jan:

Yes, we've already did that. Still waitin' and waitin'.

[Jan Soska]

Hello,
if there is no visible problem on your server - disable ASR feature via system bios. If your server works fine, then OK, you can wait for hp support. But if your server hangs/is not responding, you have real problem.

- Another option - If one your server is free for "testing" - install different OS there and let him run. IF work, you have an OS/driver issue on other system...

jan

[BiEmme]

@Jan:

We've disabled ASR few days ago, but the server rebooted again.
Now we'll try to re-install OS and try again.

[Gerardo Arceri]

You can try a hard powercycle of the server (poweroff / remove power cables / wait a couple of mins and power it back on, reseating DIMMS and CPUs would be a good idea also.

Just my $0.02
Don't forget to assign points, that's the way we thank each other around here.

[BiEmme]

That was one of our first steps few weeks ago, when problem occurs. Even after that, we 'removed' our server from power couple of times, without success.

[SStidham]

Any resolution on this? Seeing the same symptoms on a DL380 G5.