failover peer dhcp: address not available
Oscar Ricardo Silva
osilva at scuff.cc.utexas.edu
Fri May 31 17:09:25 UTC 2013
I recently reinstalled the operating system on our two dhcp servers and
we're now seeing this message on the primary:
May 31 11:38:25 primary-dhcp dhcpd: failover peer dhcp: address not
available
May 31 11:39:55 primary-dhcp dhcpd: failover peer dhcp: address not
available
May 31 11:41:25 primary-dhcp dhcpd: failover peer dhcp: address not
available
May 31 11:42:55 primary-dhcp dhcpd: failover peer dhcp: address not
available
May 31 11:44:25 primary-dhcp dhcpd: failover peer dhcp: address not
available
May 31 11:45:55 primary-dhcp dhcpd: failover peer dhcp: address not
available
May 31 11:47:25 primary-dhcp dhcpd: failover peer dhcp: address not
available
May 31 11:48:55 primary-dhcp dhcpd: failover peer dhcp: address not
available
From looking at past messages to the list, it's been suggested there
was a mismatch in dhcpd versions but I'm using the same configurations
and version as I was before the OS replacement. Here are the version
numbers and configurations:
Primary:
# dhcpd -v
Internet Systems Consortium DHCP Server 4.1-ESV-R7
Copyright 2004-2012 Internet Systems Consortium.
option domain-name-servers 192.168.185.41, 192.168.185.40 ;
option ntp-servers 192.168.185.40, 192.168.185.41;
default-lease-time 172800;
max-lease-time 172800;
one-lease-per-client true;
ddns-update-style ad-hoc;
ddns-updates off;
authoritative;
key-off-mac-address true;
if substring (option dhcp-client-identifier, 0, 5) = 01:52:41:53:20 {
deny booting;
}
option voip-tftp-server-address code 150 = array of ip-address ;
set vendor-string = option vendor-class-identifier;
failover peer "dhcp" {
primary;
address 192.168.200.2;
port 647;
peer port 847;
peer address 192.168.201.2;
max-response-delay 60;
max-unacked-updates 10;
mclt 300;
split 128;
load balance max seconds 5;
}
subnet 192.168.200.0 netmask 255.255.255.224 {
}
include "/dhcpd/dhcpd.networks.conf";
Secondary:
dhcpd -v
Internet Systems Consortium DHCP Server 4.1-ESV-R7
Copyright 2004-2012 Internet Systems Consortium.
option domain-name-servers 192.168.185.40, 192.168.185.41 ;
option ntp-servers 192.168.185.41, 192.168.185.40;
default-lease-time 172800;
max-lease-time 172800;
one-lease-per-client true;
ddns-update-style ad-hoc;
ddns-updates off;
authoritative;
key-off-mac-address true;
if substring (option dhcp-client-identifier, 0, 5) = 01:52:41:53:20 {
deny booting;
}
option voip-tftp-server-address code 150 = array of ip-address ;
set vendor-string = option vendor-class-identifier;
failover peer "dhcp" {
secondary;
address 192.168.201.2;
port 847;
peer port 647;
peer address 192.168.200.2;
max-response-delay 60;
max-unacked-updates 10;
load balance max seconds 5;
}
subnet 192.168.201.0 netmask 255.255.255.224 {
}
include "/dhcpd/dhcpd.networks.conf";
All the network definitions are in "/dhcpd/dhcpd.networks.conf" and the
file looks like this:
subnet 192.168.235.0 netmask 255.255.255.128 {
pool {
range 192.168.235.13 192.168.235.126;
deny dynamic bootp clients ;
failover peer "dhcp" ;
}
option subnet-mask 255.255.255.128;
option broadcast-address 255.255.255.255;
option routers 192.168.235.1;
}
There are router ACLs between the two servers and iptables running on
each but the entire /24 network for each server is allowed through. I
can see traffic being exchanged between the two servers on ports 647 and
847.
Any idea what's causing this error?
Oscar
More information about the dhcp-users
mailing list