Failover Configuration

[Nathan McDavit-Van Fleet]

I am trying to configure a failover configuration with DHCP 4.1.1. I
programmed each server with the failover and assigned it to a test subnet.
However, no matter what I do it just stays in recovery mode and never
assigns IP addresses. I left it for a good 20 minutes and neither started
assigning IPs. The primary says that it is "not responding (recovering)" and
the secondary says that the "peer holds all free leases".

I read that changing the mclt might shorten the beginning recovery period so
I set it to 60 seconds. It did not change anything and it never got out of
recovery. 

I also deleted both dhcpd.leases files and it was still stuck in recovery. 

Is this something to do with the first time the servers have connected to
each other? Does it do this every time they start out. When can it be
expected to start working?

SELinux also shows that the ports 647 and 847 are open for DHCPD. I also
tried 647 & 647 with no effect.

Here is my configuration:
//primary.ca
failover peer "dhcp-failover" {
  primary; # declare this to be the primary server
  address primary.ca;
  port 647;
  peer address secondary.ca;
  peer port 847;
  max-response-delay 30;
  max-unacked-updates 10;
  load balance max seconds 3;
  mclt 1800;
  split 128;
}

//secondary.ca
failover peer "dhcp-failover" {
  secondary; # declare this to be the secondary server
  address secondary.ca;
  port 847;
  peer address primary.ca;
  peer port 647;
  max-response-delay 30;
  max-unacked-updates 10;
  load balance max seconds 3;
}

Thanks,

Nathan Van Fleet

> -----Original Message-----
> From: dhcp-users-bounces+nmcdavit=alcor.concordia.ca at lists.isc.org
> [mailto:dhcp-users-bounces+nmcdavit=alcor.concordia.ca at lists.isc.org]
> On Behalf Of Fred Zwarts
> Sent: Monday, November 08, 2010 3:22 AM
> To: Users of ISC DHCP
> Subject: Re: Dual stack DHCP server
> 
> As far as I know, no. I could not find such a guide.
> It was unclear for us what part of the configuration can be shared
> between the two servers.
> Some IPv4 statements do not cause errros on the IPv6 server, but most
> IPv6 statements are rejected by the IPv4 server.
> We split the IPv4 configuration into several separate files,
> (general options; network (subnet, range, pools) definitions;
> hosts definitions with fixed addresses, host definitions used in pools)
> included from the main configuration file.
> The IPv6 configuration is splitted similarly.
> The more static files are rewritten for the IPv6 server (general
> options and network definitions).
> The host definitions are changed frequently. Here we edit the IPv4
> version as we do already for years,
> and we created a script to generate the IPv6 version from the IPv4
> ones.
> (Changing fixed-address to fixed-address6.
> It is a pity that fixed-address6 does not allow a DNS name,
> but only a numerical IPv6 address, but this is solved in the script as
> well.
> We have rather simple host definitions, so the script does not need
> much more.)
> We did not yet enable address pools with dynamic addresses for IPv6
> because we could not find a way to exclude unknown clients from thise
> pools.
> 
> Fred.Zwarts.
> 
> 
> ---- Original Message ----
> From: "Anders Rosendal" <anders at rosendal.nu>
> To: <dhcp-users at lists.isc.org>
> Sent: Saturday, November 06, 2010 11:18 AM
> Subject: Dual stack DHCP server
> 
> >> Hi
> >> Are there any guides howto setup two ISC DHCP instances on the same
> >> server, serving both v4 and v6.
> >>
> >> Regards Anders
> >>
> >
> >
> >
> >> _______________________________________________
> >> dhcp-users mailing list
> >> dhcp-users at lists.isc.org
> >> https://lists.isc.org/mailman/listinfo/dhcp-users
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users