time differences in ilo event log DL380G3

[PaulDas]

We have the following entries in ILO:

Informational
iLO
08/13/2009 21:29
08/13/2009 21:29
1
On-board clock set; was 08/13/2009 20:29:49.

Caution
iLO
08/13/2009 21:28
08/13/2009 21:28
1
Server reset.

Informational
iLO
08/13/2009 20:28
08/13/2009 20:28
1
Browser logout: Administrator

Informational
iLO
08/13/2009 20:28
08/13/2009 20:28
1
On-board clock set; was 08/13/2009 21:28:31.

Informational
iLO
08/03/2009 20:22
08/03/2009 20:22
1
On-board clock set; was 08/03/2009 19:22:13.

Caution
iLO
08/03/2009 20:20
08/03/2009 20:20
1
Server reset.

Informational
iLO
08/03/2009 19:20
08/03/2009 19:20
1
On-board clock set; was 08/03/2009 20:20:48.


Can somebody help with:

What is the meaning of On-board clock set; was .... and why does it vary in advance and behind its respective ilo entry by exactly 1 hour. The linux system time (BST) has not changed in the same period...

Thanks in advance

[pratap m keshava]

Check if the battery on server is dying. Replace the battery and check if the problem persists. The clock may be drifting hence it is being corrected (i guess).

[acartes]

Probably what is happening is this:

Server reboots and iLO gets the time from the system RTC. This is stored as GMT (for Linux boxes)
- iLO clock is updated, event is logged

OS loads and Linux agent notifies iLO of local time (GMT + offset; 1 hour).
- iLO clock is updated, event is logged.

The issue is related to how the Linux OS stores and reports the time, but stores GMT in the system RTC. You could expect this couple of events each time the system is reset and runs through post. (Unless your system happens to be located in the GMT zone :)

Windows OTOH, stores the local time in the system RTC, so the POST / OS load process does not normally perturb the iLO clock.