04-06-2005 11:25 PM
Hi,
We are using LMS 2.2 on solaris system, RME 3.5 and syslog message times are wrong.
this appeared after daylight saving changes.
is there a bug about that or a solution?
thanks
04-07-2005 12:37 AM
Time zones and time settings are matter of the OS on the server and the client (web browser client).
04-07-2005 12:47 AM
hi,
I ve solved my problem, I installed IDU10.
04-18-2005 06:13 AM
I got a bug for this issue: CSCsa27163. I think a fix is available, but don't remember in which RME IDU.
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCsa27163&Submit=Search
I don't think it can be explained away by DST, although the symptom certainly seems to be triggered by DST. A 7200 router reloaded
at 12:19 EDT on 5/4/2004. RME Reloads Report reported the reload as 13:19 EDT.
This couldn't be explained by the Daylight Savings Time or Standard Time
difference, since then RME should have reported 11:19 instead.
As far as I can tell, every timestamp is correct, except in the Reload
Report (which got it in turn from DEV_RLD_HIST), where it's one hour
behind.
According to the DEV_RLD_HIST table at
http://ciscoworks:1741/dbreader/dbreader.html
82 2004-05-04 13:19:55.000 processor memory parity error at PC
0x604C210C,
address 0x0 2004-05-04 12:36:15.000
Reload time is "2004-05-04 13:19:55.000".
Updated time is "2004-05-04 12:36:15.000".
How could cw2k update its own database at 12:36 about a router's reload at
13:19, a time in the future?
This problem did not go away even after restarting cw2k daemons (twice) as TAC suggested.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide