扫一扫
分享文章到微信
扫一扫
关注官方公众号
至顶头条
!
access-list 101 permit udp any any eq ntp time-range sntp-dial
access-list 101 deny udp any any eq ntp
access-list 101 permit ip any any
dialer-list 1 protocol ip list 101
!
time-range sntp-dial
absolute end 00:00 01 January 2000
!
The time there doesn't really matter as long as it is later than the epoch time for the device in question, and earlier than the current time. 01/01/2000 was just the arbitrary choice I made last time I configured that.
With that config, NTP will bring up the line if and only if the clock on the Cisco has not already been set.
For an unattended installation which may not dial up very frequently,
it may be worth using a time-range which allows dialling once per day to keep the clock reasonably well synced. If your usage pattern results in the line coming up frequently, that is an unnecessary step. Constructing an appropriate time-range statement is left as an exercise for the reader.
If it's a small single user LAN, it's considered polite to avoid the stratum-1 servers. Most ISPs should provide NTP servers for customer use, eg try ntp..net,timehost..net, ntp0..net,
ntp1..net, etc. Apart from not overloading valuable global resources, using a NTP server local to your ISP will probably provide a more stable time service due to lower latency between the client and server.
如果您非常迫切的想了解IT领域最新产品与技术信息,那么订阅至顶网技术邮件将是您的最佳途径之一。
现场直击|2021世界人工智能大会
直击5G创新地带,就在2021MWC上海
5G已至 转型当时——服务提供商如何把握转型的绝佳时机
寻找自己的Flag
华为开发者大会2020(Cloud)- 科技行者