On Wed, 27 Aug 2008, [EMAIL PROTECTED] wrote:
I have two RHEL 4 systems set up using heartbeat. Generally speaking, they
are doing what I want them to do
When I send an NTP request to the virtual interface eth0:0 (.231), the
response to the request comes from eth0 (.232). NTP of course does not
like sending a request to one IP address and receiving its response from
another, so it fails the operation. Why is the source address of the
virtual interface not respond, rather the eth0 address is used?
this is a bug in you NTP server, however it's a common one.
my solution to this is to have the clients point at the individual boxes. the
NTP protocol is designed to deal with multiple sources so it doesn't need to
work through the VIP.
David Lang
Thanks! Phil
LNXPNTP1: primary system, eth0 = 10.255.213.232
CHARNTP1: backup system, eth0 = 10.255.213.233
Virtual address shared by systems (eth0:0): 10.255.213.231
eth0 Link encap:Ethernet HWaddr 00:06:5B:8C:C7:42
inet addr:10.255.213.232 Bcast:10.255.213.239
Mask:255.255.255.240
eth0:0 Link encap:Ethernet HWaddr 00:06:5B:8C:C7:42
inet addr:10.255.213.231 Bcast:10.255.213.239
Mask:255.255.255.240
FAILS because of response from wrong IP
[EMAIL PROTECTED] ha.d]# ntpdate -q 10.255.213.231
server 10.255.213.231, stratum 0, offset 0.000000, delay 0.00000
27 Aug 17:02:47 ntpdate[7887]: no server suitable for synchronization found
17:03:42.483985 IP 10.255.213.233.32775 > 10.255.213.231.ntp: NTPv4,
Client, length 48
17:03:42.484152 IP 10.255.213.232.ntp > 10.255.213.233.32775: NTPv4,
Server, length 48
17:03:43.488479 IP 10.255.213.233.32775 > 10.255.213.231.ntp: NTPv4,
Client, length 48
17:03:43.488651 IP 10.255.213.232.ntp > 10.255.213.233.32775: NTPv4,
Server, length 48
17:03:44.493045 IP 10.255.213.233.32775 > 10.255.213.231.ntp: NTPv4,
Client, length 48
17:03:44.493241 IP 10.255.213.232.ntp > 10.255.213.233.32775: NTPv4,
Server, length 48
17:03:45.497586 IP 10.255.213.233.32775 > 10.255.213.231.ntp: NTPv4,
Client, length 48
17:03:45.497752 IP 10.255.213.232.ntp > 10.255.213.233.32775: NTPv4,
Server, length 48
SUCCEEDS because of response from specified IP.
[EMAIL PROTECTED] ha.d]# ntpdate -q 10.255.213.232
server 10.255.213.232, stratum 3, offset 0.017126, delay 0.02574
27 Aug 17:04:40 ntpdate[7892]: adjust time server 10.255.213.232 offset
0.017126 sec
17:04:40.905198 IP 10.255.213.232.ntp > 10.255.213.233.32775: NTPv4,
Server, length 48
17:04:40.904462 IP 10.255.213.233.32775 > 10.255.213.232.ntp: NTPv4,
Client, length 48
17:04:40.904670 IP 10.255.213.232.ntp > 10.255.213.233.32775: NTPv4,
Server, length 48
17:04:40.904736 IP 10.255.213.233.32775 > 10.255.213.232.ntp: NTPv4,
Client, length 48
17:04:40.904866 IP 10.255.213.232.ntp > 10.255.213.233.32775: NTPv4,
Server, length 48
17:04:40.904903 IP 10.255.213.233.32775 > 10.255.213.232.ntp: NTPv4,
Client, length 48
17:04:40.905031 IP 10.255.213.232.ntp > 10.255.213.233.32775: NTPv4,
Server, length 48
17:04:40.905069 IP 10.255.213.233.32775 > 10.255.213.232.ntp: NTPv4,
Client, length 48
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
