There was a time discrepancy issue in OM Enterprise Tech release in the 3.0 version, that 3.1 fixed. I would suggest updating to the latest OM Enterprise edition and let me know if the issue is resolved.
Hi MailingLists.ps, It look like time zone issue, can you please check the iDRAC time and OS time are same? share the current time in OS time and iDRAC time, will help to debug further Just need clarification regarding OM version v9.3.1 no such official release from Dell. Is it OM v9.3.0?
The idrac timezone is UTC while the OS timezone is US/Eastern. Given the timezone is different, the timestamp shouldn't be different between 'esmlog' vs 'alertlog'. Why this inconsistency?
Here's the environent I am having this issue it is same across all model of Dell.
Time will be based on Time Zone. Difference between UTC and US/Eastern time zone is 4 hours. that is the reason you are seeing 4 hours difference.
In this case when PSU is unplugged, time in OS is 17:18 and time in iDRAC is 21:18. ESMLog timestamp will be based on iDRAC time and Alert log will be based on OS time.
Maintain the same timezone in both idrac and OS to see consistency in the timestamp between esmlog and alertlog.
Hi, were you able to compare the OS time to the idrac time? You can get the idrac time by using putty to ssh to the idrac IP, then run racadm getractime.
My question was why is the timestamp returned by a utility that runs on OS has different timestamps for 'alertlog' vs 'esmlog'? It would be helpful if there was a trailing timezone info. Or show same time for both output either UTC or local OS time.
'alertlog' vs 'esmlog' in OMSA is addressing two different usecase
alertlog show the log which is supported by OMSA, logs are processed in OMSA utility so the timestamp will be same as OS. That is the reason you could see each alert entry have alert ID with hyperlink which takes to the page which have more information about the alert and with recommendation to act on these alerts.
esmlog names as "Embedded System Management log", which is nothing but iDRAC hardware logs. esmlog page usecase is to replicate idrac hardware log page in OMSA GUI. As we need to replicate and maintain consistency with iDRAC page no processing of the content. Main reason to have esmlog in OMSA GUI, customer can access/view idrac hardward log without login into iDRAC.
DELL-Chris H
Moderator
•
9.7K Posts
0
May 9th, 2019 08:00
MailingLists.ps,
There was a time discrepancy issue in OM Enterprise Tech release in the 3.0 version, that 3.1 fixed. I would suggest updating to the latest OM Enterprise edition and let me know if the issue is resolved.
Thanks
mailinglists.ps
8 Posts
0
May 9th, 2019 09:00
We are using the OMSA pkgs and not OME. Are they patched/going to be patched as well? I am using "srvadmin-omacore-9.3.0-3465.14818.el7.x86_64.rpm"
DELL-Chris H
Moderator
•
9.7K Posts
0
May 9th, 2019 12:00
Let me look into if there is an issue with the OM 9.3 version. I will get back with you shortly.
dlangesh
18 Posts
0
May 13th, 2019 02:00
mailinglists.ps
8 Posts
0
May 13th, 2019 06:00
The idrac timezone is UTC while the OS timezone is US/Eastern. Given the timezone is different, the timestamp shouldn't be different between 'esmlog' vs 'alertlog'. Why this inconsistency?
Here's the environent I am having this issue it is same across all model of Dell.
OS: RedHat 7.6
OM Report Version = 9.3.0.3465
Tried both 9.1,9.2 & 9.3
dlangesh
18 Posts
0
May 14th, 2019 06:00
Hi,
Time will be based on Time Zone. Difference between UTC and US/Eastern time zone is 4 hours. that is the reason you are seeing 4 hours difference.
In this case when PSU is unplugged, time in OS is 17:18 and time in iDRAC is 21:18. ESMLog timestamp will be based on iDRAC time and Alert log will be based on OS time.
Maintain the same timezone in both idrac and OS to see consistency in the timestamp between esmlog and alertlog.
mailinglists.ps
8 Posts
0
May 14th, 2019 09:00
Hmm, but why the inconsistency between esmlog and alertlog? Simply restating the current way it works isn't an argument for why it should be that way.
DELL-Rey G
3 Apprentice
•
1.1K Posts
0
May 20th, 2019 08:00
Hi, were you able to compare the OS time to the idrac time? You can get the idrac time by using putty to ssh to the idrac IP, then run racadm getractime.
#Iwork4Dell
mailinglists.ps
8 Posts
0
May 20th, 2019 10:00
Yes. I know.
iDRAC Timezone: UTC
OS Timezone(rhel7): US/Eastern
My question was why is the timestamp returned by a utility that runs on OS has different timestamps for 'alertlog' vs 'esmlog'? It would be helpful if there was a trailing timezone info. Or show same time for both output either UTC or local OS time.
dlangesh
18 Posts
0
May 22nd, 2019 04:00
Hi MailingLists.ps,
'alertlog' vs 'esmlog' in OMSA is addressing two different usecase
alertlog show the log which is supported by OMSA, logs are processed in OMSA utility so the timestamp will be same as OS. That is the reason you could see each alert entry have alert ID with hyperlink which takes to the page which have more information about the alert and with recommendation to act on these alerts.
esmlog names as "Embedded System Management log", which is nothing but iDRAC hardware logs. esmlog page usecase is to replicate idrac hardware log page in OMSA GUI. As we need to replicate and maintain consistency with iDRAC page no processing of the content. Main reason to have esmlog in OMSA GUI, customer can access/view idrac hardward log without login into iDRAC.
Hope this helps