大网数据广告活动
服务器运维问答

NTP high-availability behind a Virtual IP

· 52CE 我爱测

Is it a bad practice to put a NTP server behind a Virtual IP? (VRRP) How much would it be preferred to simply have the clients talk directly to the 2 instances? Since the NTP clients keeps the server's refid, I suppose it would d…

问题原文

原帖链接 · Phil · CC BY-SA 3.0

Is it a bad practice to put a NTP server behind a Virtual IP? (VRRP)

How much would it be preferred to simply have the clients talk directly to the 2 instances?

Since the NTP clients keeps the server's refid, I suppose it would distinguish when the server behind the IP is swapped, but I'm not sure how it would affect it's behavior otherwise.

已采纳解答

原帖链接 · HBruijn · CC BY-SA 3.0

After my initial comment a slightly longer answer.

As a rule of thumb when the protocol itself, or the common implementations of said protocol, already natively support resilience, high availability and failover, you don't need to provide those at the infrastructure level.

(Except when you use cases do require them...)

Load balancing and clustering are useful techniques, but they also require expert maintenance and I have seen far more high availability clusters crash catastrophically than I have seen admins break two different servers at the same time.


With regards to NTP, you either provide a single NTP server to your clients, or optimally you configure 4 or more...

Ntpd needs a majority of servers to agree on the time before it can sync.

If you only have one server, that server will be believed. That has the benefit that at least all your systems will be set to the same (albeit maybe an incorrect) time and you can still correlate security events and rely on time dependant protocols such as Kerberos.

If you have two servers behind a loadbalancer your clients behave as if there is only one NTP sever. If time on those two back-end servers differs (depending on your loadbalancing algorithm) either half of your servers will use a completely different date from the others or you might get to see random jumps in time when failover does occur.

If you configure multiple NTP servers most (if not all) NTP client implementations are capable (if you have configured sufficient servers) to distinguish a "false ticker" and disregard it by reaching a majority vote.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-09-28)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。