| View previous topic :: View next topic |
| Author |
Message |
milamontagne
n00b
Joined: 01 Oct 2005
Posts: 41
|
 Posted: Mon Apr 02, 2007 9:49 pm Post subject: Failover Dhcp with bootp prolbems |
 |
|
Hi. Im trying to get Dhcp fail over going with two of my servers, but keep getting the error:
[dhcpd] /etc/dhcp/dhcpd.conf line 58: pools with failover peers may not permit dynamic bootp
On the secondary server on startup.
As far as i know, my clients are getting a static ip:
(/etc/dhcp/dhcpd.conf on the secondary)
| Quote: |
ddns-update-style interim;
# Declare FailOver
failover peer "dhcp-failover" {
secondary; # declare this to be the secondary server
address 10.0.0.4;
port 520;
peer address 10.0.0.2;
peer port 520;
max-response-delay 30;
max-unacked-updates 10;
load balance max seconds 3;
}
subnet 10.0.0.0 netmask 255.255.255.0 {
# Declare that we are the authoritative source in this
# Domain for dhcp info
authoritative;
# Declare clients can't change their own records
ignore client-updates;
# Declare the Domain Name, the DNS servers, and the router
# (aka gateway) for this subnet so the clients know what to
# use
option domain-name "CthuWulf.lan";
option domain-name-servers 10.0.0.2;
option routers 10.0.0.1;
# Declare Dynamic Domain Name and update options
ddns-updates on;
ddns-domainname "CthuWulf.lan";
ddns-rev-domainname "in-addr.arpa.";
ddns-ttl 14400;
update-static-leases on;
include "/etc/bind/rndc.key";
# Declare Domain Key and secret
key "CthuKey" {
algorithm hmac-md5;
secret "secret";
}
# Declare DNS Zones, foward and reverse, and key to use
zone CthuWulf.lan {
primary 10.0.0.2;
key "CthuKey";
}
zone 0.0.10.in-addr.arpa {
primary 10.0.0.2;
key "CthuKey";
}
# Unknown clients get this pool.
pool {
# Declare Failover
failover peer "dhcp-failover";
# Failover Declaration Above
option domain-name-servers CthuServ.CthuWulf.lan;
max-lease-time 14400;
range 10.0.0.51 10.0.0.253;
allow unknown-clients;
}
# Known clients get this pool.
pool {
# Declare Failover
failover peer "dhcp-failover";
# Failover Declaration Above
option domain-name-servers CthuServ.CthuWulf.lan;
max-lease-time 28800;
range 10.0.0.10 10.0.0.50;
deny unknown-clients;
}
# Declare Known clients below for use with above
# host dr1 {
# option host-name "dr1";
# hardware ethernet 00:50:ba:b3:0a:a2;
# filename "remote.boot";
# fixed-address 10.0.0.4;
# server-name "CthuServ.CthuWulf.lan";
# }
host CthuServTwo {
option host-name "CthuServTwo";
hardware ethernet 00:00:F8:04:02:AC;
filename "remote.boot";
fixed-address 10.0.0.3;
server-name "CthuServ.CthuWulf.lan";
}
host IczerOne {
option host-name "IczerOne";
hardware ethernet 00:90:27:9d:16:fa;
fixed-address 10.0.0.5;
if substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
filename "iczerone.zpxe";
} else if substring (option vendor-class-identifier, 0, 9) = "Etherboot" {
filename "iczerone.nbi";
option vendor-encapsulated-options 3c:09:45:74:68:65:72:62:6f:6f:74:ff;
}
server-name "CthuServ.CthuWulf.lan";
}
host BedBitch {
option host-name "BedBitch";
hardware ethernet 00:08:C7:39:F8:D6;
filename "remote.boot";
fixed-address 10.0.0.6;
server-name "CthuServ.CthuWulf.lan";
}
host MaryBeth {
option host-name "MaryBeth";
hardware ethernet 00:50:BA:47:96:07;
filename "MaryBeth.nbi";
fixed-address 10.0.0.7;
server-name "CthuServ.CthuWulf.lan";
}
#############Reserved For Future Use#######################
# host Reserved {
# option host-name "Reserved";
# hardware ethernet ;
# filename "remote.boot";
# fixed-address 10.0.0.8;
# server-name "CthuServ.CthuWulf.lan";
# }
#############Reserved For Future Use#######################
# host Reserved {
# option host-name "Reserved";
# hardware ethernet ;
# filename "remote.boot";
# fixed-address 10.0.0.9;
# server-name "CthuServ.CthuWulf.lan";
# }
host BattleAngel {
option host-name "BattleAngel";
hardware ethernet 00:C0:F0:46:12:C0;
filename "BATTLE.NBI";
fixed-address 10.0.0.10;
server-name "CthuServ.CthuWulf.lan";
}
host Covalt {
option host-name "Covalt";
hardware ethernet 00:C0:F0:46:12:C3;
filename "COVALT.NBI";
fixed-address 10.0.0.11;
server-name "CthuServ.CthuWulf.lan";
}
host DelosTheta {
option host-name "DelosTheta";
hardware ethernet 00:C0:F0:46:0E:5D;
filename "DELOS.NBI";
fixed-address 10.0.0.12;
server-name "CthuServ.CthuWulf.lan";
}
host Eddie {
option host-name "Eddie";
hardware ethernet 00:C0:F0:46:B8:C8;
filename "EDDIE.NBI";
fixed-address 10.0.0.13;
server-name "CthuServ.CthuWulf.lan";
}
host Guyver {
option host-name "Guyver.nbi";
hardware ethernet 00:C0:F0:47:61:BF;
filename "GUYVER.NBI";
fixed-address 10.0.0.14;
server-name "CthuServ.CthuWulf.lan";
}
host LumChan {
option host-name "LumChan";
hardware ethernet 00:C0:F0:47:67:2D;
filename "LUMCHAN.NBI";
fixed-address 10.0.0.15;
server-name "CthuServ.CthuWulf.lan";
}
host Nagisa {
option host-name "Nagisa";
hardware ethernet 00:C0:F0:55:24:62;
filename "NAGISA.NBI";
fixed-address 10.0.0.16;
server-name "CthuServ.CthuWulf.lan";
}
host Sepia {
option host-name "Sepia";
hardware ethernet 00:C0:F0:55:24:76;
filename "SEPIA.NBI";
fixed-address 10.0.0.17;
server-name "CthuServ.CthuWulf.lan";
}
host SirViolet {
option host-name "SirViolet";
hardware ethernet 00:C0:F0:55:0C:78;
filename "SIRVIO.NBI";
fixed-address 10.0.0.18;
server-name "CthuServ.CthuWulf.lan";
}
host SiYohko {
option host-name "SiYohko";
hardware ethernet 00:C0:F0:55:0C:A3;
filename "SIYOHKO.NBI";
fixed-address 10.0.0.19;
server-name "CthuServ.CthuWulf.lan";
}
host Vic {
option host-name "Vic";
hardware ethernet 00:C0:F0:55:2C:51;
filename "VIC.NBI";
fixed-address 10.0.0.20;
server-name "CthuServ.CthuWulf.lan";
}
host Yohko {
option host-name "Yohko";
hardware ethernet 00:C0:F0:55:2C:59;
filename "YOHKO.NBI";
fixed-address 10.0.0.21;
server-name "CthuServ.CthuWulf.lan";
}
########## End Of Game Stations / First 12-Node Beowulf Cluster###############
########## Begin Kingston Nics, Extras #######################################
host Kingston1 {
option host-name "Kingston 1";
hardware ethernet 00:C0:F0:55:24:8D;
filename "Reload.nbi";
fixed-address 10.0.0.22;
server-name "CthuServ.CthuWulf.lan";
}
host Kingston2 {
option host-name "Kingston 2";
hardware ethernet 00:C0:F0:55:11:90;
filename "Reload.nbi";
fixed-address 10.0.0.23;
server-name "CthuServ.CthuWulf.lan";
}
host Kingston3 {
option host-name "Kingston 3";
hardware ethernet 00:C0:F0:55:24:63;
filename "Reload.nbi";
fixed-address 10.0.0.24;
server-name "CthuServ.CthuWulf.lan";
}
host Kingston4 {
option host-name "Kingston 4";
hardware ethernet 00:C0:F0:55:24:8F;
filename "Reload.nbi";
fixed-address 10.0.0.25;
server-name "CthuServ.CthuWulf.lan";
}
##########################End Kingston Extra Nics###########################
##########################Begin Friends Parked Pc's#########################
host John {
option host-name "John";
hardware ethernet 00:30:1B:38:FE:A0;
filename "John.nbi";
fixed-address 10.0.0.30;
server-name "CthuServ.CthuWulf.lan";
}
# host Ken {
# option host-name "Ken";
# hardware ethernet ;
# filename "Ken.nbi";
# fixed-address 10.0.0.31;
# server-name "CthuServ.CthuWulf.lan";
# }
}
|
As far as i know, I've setup all my clients to have a static ip.
What i dont understand is why im getting the error above if all my clients are configured
with a static ip.
Am I misunderstanding the error message? |
|
| Back to top |
|
 |
Will Scarlet
Apprentice
Joined: 19 Mar 2004
Posts: 239
|
| Posted: Tue Apr 03, 2007 6:32 pm Post subject: |
|
|
From the man of dhcpd.conf:
| Quote: | CONFIGURING FAILOVER
In order to configure failover, you need to write a peer declaration
that configures the failover protocol, and you need to write peer ref-
erences in each pool declaration for which you want to do failover.
You do not have to do failover for all pools on a given network seg-
ment. You must not tell one server its doing failover on a particu-
lar address pool and tell the other it is not. You must not have any
common address pools on which you are not doing failover. A pool dec-
laration that utilizes failover would look like this:
pool {
failover peer "foo";
deny dynamic bootp clients;
pool specific parameters
};
Dynamic BOOTP leases are not compatible with failover, and, as such,
you need to disallow BOOTP in pools that you are using failover for. |
So, in a nutshell, with failover you have to disable bootp.
I found this at http://www.bind9.net/dhcpd.conf.5. There is also more at http://www.bind9.net/manuals-dhcp
Hope this helps...  |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
