dhcpd: failover: link startup timeout ... Failover wont' work ...

[Sébastien CRAMATTE]

I've just installed ntpdate but one server won't synchronise properly 
(20mn less than the other).
2 servers are Xen DOM U with Lenny.  Dom0 distribution are different 
(Debian sarge, Ubuntu Gutsy). Each Dom0 are setup to have independent 
clock. Moreover Dom0 time is correct...

I still investigate thank you for you help.



Sten Carlsen escribió:
> The roughly half hour difference in times will be significant if these 
> two log excerpts are simultaneous.
>
> Sébastien CRAMATTE wrote:
>> Hello
>>
>> I've setup  dhcp 3.1.0 with ldap patch under debian lenny.
>> twice daemons on primary and secondary are launched and 
>> communications with ldap is fine.
>> This server act as main DHCP daemon for  various vlan segment with 
>> dhcp relay.
>>
>> The problem is that "Failover" doesn't works" ...
>>
>> On the primary
>>
>> May  3 18:28:16 dhcp1 dhcpd: failover peer failover1: I move from 
>> recover to startup
>> May  3 18:28:31 dhcp1 dhcpd: failover peer failover1: I move from 
>> startup to recover
>> May  3 18:28:31 dhcp1 dhcpd: failover: link startup timeout
>>
>> On the secondary
>>
>> May  3 19:05:14 dhcp2 dhcpd: failover peer failover1: I move from 
>> recover to startup
>> May  3 19:05:29 dhcp2 dhcpd: failover peer failover1: I move from 
>> startup to recover
>>
>>
>> Using tcpdump I can't see communications between  primary and secondary.
>>
>> Setup on primary
>>
>> failover peer "failover1" { primary; address 192.168.0.2 ; port 519; 
>> peer address 192.168.03; peer port 519; max-response-delay 60; 
>> max-unacked-updates 10; load balance max seconds 3; split 128; mclt 
>> 3600; }
>>
>> Setup on secondary
>>
>> failover peer "failover1" { secondary; address 192.168.0.3; port 519; 
>> peer address 192.168.0.2; peer port 519; max-response-delay 60; 
>> max-unacked-updates 10; load balance max seconds 3; }
>>
>> Subnet are setup as this :
>>
>> subnet 192.168.0.0 netmask 255.255.255.0 {
>> option broadcast-address 192.168.0.255;
>> option routers 192.168.0.1;
>> option domain-name-servers  84.232.1.100,194.179.1.100;
>> pool {
>> range 192.168.0.234 192.168.0.244;
>> deny dynamic bootp clients;
>> max-lease-time 86400;
>> default-lease-time 86400;
>> failover peer "failover1";
>> }
>> }
>>
>> subnet 192.168.2.0 netmask 255.255.255.0 {
>> option broadcast-address 192.168.2.255;
>> option routers 192.168.2.1;
>> option domain-name-servers  194.179.1.100;
>> pool {
>> range 192.168.2.100 192.168.2.254;
>> deny dynamic bootp clients;
>> max-lease-time 86400;
>> default-lease-time 86400;
>> failover peer "failover1";
>> }
>> }
>>
>> subnet 192.168.1.0 netmask 255.255.255.0 {
>> option broadcast-address 192.168.1.255;
>> option routers 192.168.1.1;
>> option domain-name-servers  194.179.1.100;
>> pool {
>> range 192.168.2.100 192.168.2.254;
>> deny dynamic bootp clients;
>> max-lease-time 86400;
>> default-lease-time 86400;
>> failover peer "failover1";
>> }
>> }
>>
>>
>> Not that I've disable the iptables (all policies set to ACCEPT)
>>
>> Any tips, ideas are welcome
>> Thanks
>>
>>
>>
>>
>