Issues With DHCP Failover (3.0.5)

Paul E. Virgo Paul.E.Virgo.1 at gsfc.nasa.gov
Fri Mar 23 00:17:34 UTC 2007


All,

I have configured two CentOS 4.4 systems to run in primary/secondary 
failover mode.
When I restarted the daemon on both, I receive this message:

Mar 22 19:44:17 cne-dhcp1-temp dhcpd: Wrote 358 leases to leases file.
Mar 22 19:44:17 cne-dhcp1-temp dhcpd: Listening on 
LPF/eth1/00:15:c5:60:df:cf/128.154.140/22
Mar 22 19:44:17 cne-dhcp1-temp dhcpd: Sending 
on   LPF/eth1/00:15:c5:60:df:cf/128.154.140/22
Mar 22 19:44:17 cne-dhcp1-temp dhcpd: Sending on   Socket/fallback/fallback-net
Mar 22 19:44:17 cne-dhcp1-temp dhcpd: failover peer CNE-DHCP-FAILOVER: I 
move from recover to startup
Mar 22 19:44:17 cne-dhcp1-temp dhcpd: failover peer CNE-DHCP-FAILOVER: 
address not available
Mar 22 19:44:17 cne-dhcp1-temp dhcpd: dhcpd startup succeeded
6 fewer lines

This DEFINITELY tells me that neither the primary (cne-dhcp1) or its 
secondary (cne-dhcp2, similar message)
are not syncing up. I have added the line to allow DHCP to bind in the 
local.te for SELinux purposes, but I do not
see either machine listening on their ports when I do a netstat -an. This 
vexeth me sorely, since this is part of a requirement
to have failover. Here is my failover definition as well:

failover peer "CNE-DHCP-FAILOVER" {
         primary; # This is the primary DHCP server
         address 128.154.44.10;
         port 5251;
         peer port 5250;
         peer address 128.154.44.11;
         max-response-delay 30;
         max-unacked-updates 10;
         load balance max seconds 30;
         mclt 1800;
         split 128;
}


I don't think anything else looks too untoward...If any of you out there 
HAS done this successfully, would like to hear from you.

Thanks in advance.

PEV



More information about the dhcp-users mailing list