server_date ALL question (datamover date/time issues)

I just re-read my post. The server_date ALL output is not what we saw on Sunday, Nov. 2. It was just an example ... produced today . Sorry if that was confusing.

Hi,
Can you show the output of the below command
# date

Also check emc148532 and emc150583

Hi,

Please ensure that the NTP server is configured for both Control Station and the Data Mover. Also ensure the NTP server is pinging from both control station and data mover - you may run ping command on control station and server_ping server_2 for the data mover.

It looks to me that, you are setting the timezone correctly but no NTP server.

Also, please note that, by default the time zone on the data mover is the same as the time zone set on the control station.

But for the standby data mover - (I assume server_3 is the standby one in your case) - you can not configure the NTP server - so, it may have a different time on it. In case of data mover failure - server_3 becomes server_2 and you get the correct time. So, I'll not worry much about the time shown on the standby data mover. If you want, you can manually change it.

Hope this helps,
Thanks,
Sandip

[nasadmin@usat0nas003 ~]$ date
Fri Nov 7 11:38:17 EST 2008
[nasadmin@usat0nas003 ~]$ server_date ALL
server_2 : Fri Nov 7 11:38:24 EST 2008
server_3 : Fri Nov 7 15:38:33 EST 2008

So ... from the control station the server_2 date/time matches the control station but in the Celerra Manager GUI it does not.

I believe there is a small bug in the Celerra Manager GUI for server_2 date/time display. I also think the celerra manager gui for server_3 is a little buggy. We have everything set up identically to server_2. No good reason for it to display date/time 6 hours in the future (which is what we see at the moment). On the control station server_date ALL shows server_3 date/time 4 hours in the future. Seems a little screwy.

As Sandip says, we won't worry about the server_3 date/time since it will get the correct time if standby becomes active. I'm just not liking the unexpected results.

Thanks for your feedback!!

NTP server(s) are configured for both control station and data mover. NTP servers are pingable from control station and server_2. Not pingable from server_3.

Yes, server_3 is the standby data mover.

With knowledgebase search I found the two items you listed Amol (148532 & 150583) ... but I was unable to view them. Beats me why.

[nasadmin@usat0nas003 ~]$ server_date server_2 timesvc stats ntp
server_2 :
Time synchronization statistics since start:
hits= 978, misses= 0, first poll hit= 1, miss= 3
Last offset: 0 secs, -25368 usecs
Current State: Running, connected, interval=60
Time sync hosts:
0 1 143.242.2.12
0 1 143.242.2.11
0 1 143.242.2.13


Thanks again Sandip!

It seems to me that the Time on the control station and the active data mover is working properly - set by the NTP server. So, you need not to worry about.

However, you may run this command on server_2 to be 100% confirmed -

server_date server_2 timesvc stats ntp

Look at the number of hits, current state and time sync hosts.

For the standby data mover, as I mentioned earlier, I'll not be worried at all as this data mover is not doing anything as server_3, when the data mover failover occurs, it renames as server_2 and all server_2 configuration are effective on this data mover.

However, to make it look good -
1) either set the time on the standby data mover (server_3) manually through GUI or CLI
2) Failover the active data mover to standby data mover - ensure things are working properly - when data mover 2 completes rebooting, failback to the original data mover. Now you'll find both the data movers are having correct time.

But, please note that NTP configuration is not applicable on the standby data mover (server_3) as this is a standby one. Thus earlier, I mentioned not to worry about the time on server_3.

Hope this help,
Thanks,
Sandip

Hey,

good to know your problem got fixed.