ONTAP Discussions
ONTAP Discussions
I have DOT 8.1.4 running on my FAS. NTP was configured and working fine. but now its showing a time difference of about 295Secs.
how can i check the difference b/w filer and time server.
Why filer is not sync its time with NTP server. I can ping the NTP server plus there is no messages in /etc/messages regarding adjusting time ......
options timed are as under:-
timed.enable on
timed.log on
timed max_skew 30m
timed.min_skew 0
timed.proto ntp
timed.sched 1hr
timed.window 0s
Regards
have you seen this bug?
http://mysupport.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=459942
it's observed in 8.1.4 (without P1) and causes the filer to stop syncing with ntp - try update ontap - perhaps it helps
if not you can have a closer look to this KB-article, it helps you verify if ntp-sync works: https://kb.netapp.com/support/index?page=content&id=1010058&locale=en_US
-AJ
I can't open the above document 😞
how can i ??
plus ... in KB article i don't see any single entry in /etc/log/mlog/messages.log regarding ntp.. Does this mean that NTP is not working?
Thanks alot for ur reply.
it just copy it here for you:
Bug ID
459942 | |
Title | Data ONTAP fails to sync with remote NTP server after reboot |
Duplicate of | |
Bug Severity | 2 - System barely usable |
Bug Status | Fixed |
Product | Data ONTAP |
Bug Type | Kernel/Op Sys |
Description Formatted | In some situations Data ONTAP's NTP service will fail to initialize properly on system boot. As a result the system will not maintain time with remote peers and over time the system time will diverge. |
Workaround Formatted | To workaround the issue add the following entries to the /etc/rc file: options timed.enable off options timed.enable on This workaround will force the NTP service to initialize again later in the boot process. |
Notes Formatted | Additional NTP troubleshooting steps are in a knowledge base article: https://kb.netapp.com/support/index?page=content&id=1010058 |
Fixed-In Version |
|
as far as i know you want find any log-entry within messages or mlog regarding ntp sync - you have to follow the procedures explained in the KB-article