What kind of device is your router attempting to learn time from. You say that it is one of the servers on your network. Can you supply some detail about what kind of server? If it is a Windows server you may have a problem. Windows server usually run a simplified implementation of the time service and not a full implementation of NTP. So an IOS router will have problems in attempting to learn NTP time if the server is not running the full implementation of NTP. If it is a *nix type server it is more likely that it is running a full implementation of NTP.
It might help us understand the problem if you would post the output of show ntp association detail from your router.
I do not see any obvious problem with the config as you have given it.
I believe that there are 3 alternatives that you can consider:
- configure your router to learn time from an external/Internet NTP server. Advantages include that you will learn accurate NTP time. Disadvantages include that you are dependent on an external resource.
- configure your router to use SNTP rather than NTP. (sntp server x.x.x.x rather than ntp server x.x.x.x) Advantages include that you learn time from an internal resource and are not dependent on an external resource. Disadvantages include that SNTP is not as accurate as NTP - though for your purposes I believe that it is probably adequate).
- add some software or a hardware device on your Windows server that will run NTP and allow your router to learn NTP this way. Advantages include that you learn accurate NTP time from your internal resource. Disadvantages include potential expense to obtain the software or device, and the effort expended to install and run it.
I would suggest that you not use the configuration command: ntp master. If you do this your router will believe that it is authoritative and will use its own internal clock for sending time to other devices which use it as an NTP server. The internal clock of a router is generally not designed to be accurate enough to base an entire network to learn time from.
Depending on the router type the ntp update-calendar may or may not be a supported command.
Learning time from us.pool.ntp.org is a good idea and should work (assuming that you have IP connectivity to those devices and assuming that your network edge devices are not filtering traffic in a way that would deny NTP traffic. Keeping ntp server 10.10.1.40 prefer in the config does no harm. But it seems that we have already identified that it is not working.
I am glad that you got it resolved and that my suggestions were helpful. Thank you for posting back to the forum indicating that you had resolved the problem and what was the resolution. It makes the forum more helpful when people can read about a problem and can read what the problem turned out to be and what was done to resolve the problem.
The forum is an excellent place to learn about Cisco networking. I encourage you to continue your participation in the forum.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...