?
Solved

NetApp NTP

Posted on 2012-12-31
9
Medium Priority
?
3,271 Views
Last Modified: 2013-01-08
We recently started to receive error alerts from our NetApp monitoring services saying that our NetApp is not NTP synchronized with any peer, so it's time may be incorrect. It says:

NTP is running, but no peers have passed the selection process. The local time may be too far off; or the configured NTP peers may not be reachable.

I check the ntp.conf to ensure valid time servers are listed, I also turned ON/OFF "options timed.enable".

Next, I looked into this article: https://kb.netapp.com/support/index?page=content&actp=LIST&id=S:1012660

After following all the instructions, I was able to see the error message that might be truly the root cause of the problem: I think it says the NTP server is reachable, but it was rejected by the following reason:

It says flash=400 not_proventic.

At this point I'm stuck and not sure how to proceed further. Any help would be greatly appreciated.
0
Comment
Question by:pzozulka
  • 5
  • 4
9 Comments
 
LVL 9

Accepted Solution

by:
FilipZahradnik earned 2000 total points
ID: 38733898
What version of ONTAP are you using?
What NTP server(s) are you syncing with?

NTP functionality has been changed substantially in ONTAP 8. In some configurations, a Windows domain controller may not be considered a suitable timesource.

These might help:

How to determine if a Windows Domain Controller is a suitable NTP server for Data ONTAP 8
https://kb.netapp.com/support/index?page=content&id=1013468

How to verify NTP operation in Data ONTAP 8
https://kb.netapp.com/support/index?page=content&id=1010058
0
 
LVL 8

Author Comment

by:pzozulka
ID: 38741360
We are running 8.1 7-mode.

We are trying to sync with our domain controller which has the role PDC emulator.

I tried running the command ntpq -p <ip of NetApp management port>
And get results which indicate reach=377 meaning there are no communication problems, however it is getting rejected as an NTP peer.
0
 
LVL 9

Expert Comment

by:FilipZahradnik
ID: 38742037
Did you manage to have a look at this article:

How to determine if a Windows Domain Controller is a suitable NTP server for Data ONTAP 8
https://kb.netapp.com/support/index?page=content&id=1013468

It describes an issue where a DC might be rejected as a time source because it does not offer the required accuracy.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
LVL 8

Author Comment

by:pzozulka
ID: 38742106
That setting is only applicable if using the local CMOS clock of the DC -- which in our case we aren't. Our DC uses an external internet time source.
0
 
LVL 9

Expert Comment

by:FilipZahradnik
ID: 38742887
Interesting.

As a troubleshooting step, you can try to sync directly with the external NTP source.

If that works, then the issue is likely related to the fact that your time source is a Windows DC. If if fails, then the issue is probably an NTP or ONTAP problem, in which case NetApp Support should be able to help.
0
 
LVL 8

Author Comment

by:pzozulka
ID: 38745407
Can't sync directly because our NetApps are on an internal VLAN which doesn't have access to outside world.
0
 
LVL 9

Expert Comment

by:FilipZahradnik
ID: 38745416
Ok, can you try syncing with another internal NTP that is not a Windows DC - e.g. a Cisco router?
0
 
LVL 8

Author Comment

by:pzozulka
ID: 38745787
I am able to connect to other time sources. By the way, it magically started working...out of the blue.

I'm really stumped.
0
 
LVL 9

Expert Comment

by:FilipZahradnik
ID: 38757945
Aaah, the joys of random tinkering... :)

Well done.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Windows Server 2003 introduced persistent Volume Shadow Copies and made 2003 a must-do upgrade.  Since then, it's been a must-implement feature for all servers doing any kind of file sharing.
Article by: evilrix
Looking for a way to avoid searching through large data sets for data that doesn't exist? A Bloom Filter might be what you need. This data structure is a probabilistic filter that allows you to avoid unnecessary searches when you know the data defin…
This video teaches viewers how to encrypt an external drive that requires a password to read and edit the drive. All tasks are done in Disk Utility. Plug in the external drive you wish to encrypt: Make sure all previous data on the drive has been …
This Micro Tutorial will teach you how to reformat your flash drive. Sometimes your flash drive may have issues carrying files so this will completely restore it to manufacturing settings. Make sure to backup all files before reformatting. This w…
Suggested Courses
Course of the Month8 days, 5 hours left to enroll

616 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question