Symevent timestamp inconsistencies.

If I run a symevent list command, it will give me a list of it's entries. If I run the same command again, I notice that the timestamps sometimes change by a second on the same entries. Also, sometimes it will create a timestamp way in the future for a new event. (I don't think the microcode is smart enough to predict when something is "going" to happen.

)

Does anynone know where it pulls the values from for it's timestamps? The host date is correct and the service processor is close too. Both are set to Eastern time (USA) zones.

I'm running symcli 6.4.1.0 and it happens on any type of DMX.

thanks.

Responses(2)

Helene3

1 Message

0

October 22nd, 2007 13:00

I found the same on our Symms... We are running SE 6.4.2 and all the Symm's time zones are set to GMT. Pre 6.4.2, the timestamps in symevent was +- 5h in the future, but since we upgraded to 6.4.2, the time stamps seem to be our local time (South Africa), except on one of the two 8830s we have. Other Symms are all DMX. I also found that the same events will be listed with a different timestamp (1 sec difference) in a follow up symevent commnd, and the next symevent will return the original timestamps.

xe2sdc

2 Intern

•

2.8K Posts

0

October 24th, 2007 04:00

Service processor time is different from DMX/Symmetrix time ... The former is the time you set on the SP .. the later is the time that the processors use while working.

Since events comes from the DA and from FA, you have silly dates coming from the future ..

Unfortunatly I don't have a fix right now for this "behaviour"

even if I know that you can ask your CE to change the DMX-time

If you want to change the time in your 8830, simply schedule a complete offline of the whole box .. Now it's up to you .. do you prefer events from the future or to shutdown all your hosts ??

Message was edited by:
Stefano Del Corno

View All

No Events found!

Host Systems

Symevent timestamp inconsistencies.