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

Ola Sandstad ola at tantec.no
Sun May 4 07:41:47 UTC 2008


Hi Sèbastien.

Maybe this is already fixed in your actual conf-file, but I couldn't help noticing that your peer address in the primary setup ends with .03 and not .0.3

If this is the current config, one could think that this would lead to some misbehaviour ;)
(no access to a dhcp binary right now, haven't been able to check whether a warning/error is thrown or not)

Ola

----- Opprinnelig melding -----
Fra: Sébastien CRAMATTE <s.cramatte at wanadoo.fr>
Sendt: 3. mai 2008 22:14
Til: dhcp-users at isc.org
Emne: dhcpd: failover: link startup timeout  ... Failover wont' work ...

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







More information about the dhcp-users mailing list