Hi,

could you please post the output of the following command ?

[nasadmin@CONTROL_STATION ~]$ server_date server_2 timesvc stats ntp
server_2 :
Time synchronization statistics since start:
hits= 2, misses= 0, first poll hit= 1, miss= 0
Last offset: 0 secs, -3672 usecs
Current State: Running, connected, interval=60
Time sync hosts:
0 1 10.1.1.1
0 1 10.1.1.2


Gustavo Barreto.

can you run server_date ALL ..just to confirm the time/date from cli. Time difference between datamovers and domain controllers should not exceed 5 minutes.

Hi,

Here are the outputs from the two commands:

[nasadmin@ifcdasd2a nasadmin]$ server_date ALL
server_2 : Fri Sep 25 09:12:55 EDT 2009
server_3 : Fri Sep 25 08:35:37 EDT 2009
[nasadmin@ifcdasd2a nasadmin]$ server_date server_2 timesvc stats ntp
server_2 :
Time synchronization statistics since start:
hits= 11734, misses= 3045, first poll hit= 1, miss= 0
Last offset: 0 secs, 197701 usecs
Current State: Running, disconnected, interval=60
Time sync hosts:
0 1 192.168.22.100

It looks to me like there is a problem seeing that the two datamovers are over half an hour out of sync and the "Current State" of the second command shows "disconnected". I unfortunately don't know how to fix either of these issues.

Any ideas?

Thanks

Andrew

Hi,

Thanks for all the help. Once I modified the time of the two data movers to match each others and our networks, I can now access the share.

Thanks again.

Andrew

It's nice to see that your problem is solved now. But I suspect whether your NTP is working properly. Since you manually adjusted the Time on the data mover and the NTP status shows disconnected - I suspect you may have issues later of again manually adjusting time.

It seems to me that the NTP server IP Address may be an issue - please check the NTP server IP address configuration. If the NAS data movers are using 192.168.1 network for internal IP addressing - it can be a routing issue to connect to the NTP server (IP address in the 192.168.22.100).

My delayed 2 cents
Thanks,
Sandip