Failover and pools with single machines

Tina Siegenthaler tina at zool.unizh.ch
Mon Dec 18 09:49:21 UTC 2006


Sorry to bother you again...  my new setup seems to work, at least  
more or less. At least, I haven't heard anyone complaining about not  
getting an IP address. What is odd, though, is that my "old" dhcp  
server (which is now primary) still handles most of the leases. The  
"new" peer assigns only very few addresses, about one each hour.  
Shouldn't reach peer distribute roughly half of the addresses? What  
did I miss?

These are my configuration files:


DHCP-0456 (primary):

failover peer "DHCP-0465" {
	primary;
	address 130.60.23.4;
	port 520;
	peer address 130.60.23.114;
	peer port 520;
	max-response-delay 60;
	max-unacked-updates 10;
	mclt 3600;
	split 128;
	load balance max seconds 3;
}

ddns-update-style none;
option domain-name-servers 130.60.128.3, 130.60.64.51;
option domain-name "unizh.ch";
authoritative;
log-facility local1;


# some (not all) of my hosts, classes and subclasses (for fixed  
addresses)

host PBG4 { hardware ethernet 00:0a:95:e6:89:2a; }
host CODEC { hardware ethernet 00:50:60:80:80:e9; }

class "PBG4" { match pick-first-value (option dhcp-client-identifier,  
hardware); }
class "CODEC" { match pick-first-value (option dhcp-client- 
identifier, hardware); }

subclass "PBG4" 1:0:0a:95:e6:89:2a;
subclass "CODEC" 1:0:50:60:80:80:e9;

# One of my subnets

subnet 130.60.225.0 netmask 255.255.255.128 {
	option routers 130.60.225.1;
	option broadcast-address 130.60.225.127;
	pool { allow members of "CODEC"; range 130.60.225.93; }
	pool { allow members of "PBG4"; range 130.60.225.90; }
	pool {
		failover peer "DHCP-0465";
		deny dynamic bootp clients;
		allow unknown-clients;
		range 130.60.225.20 130.60.225.80;
	}
	max-lease-time 21600;
}



DHCP-0352 (secondary):

failover peer "DHCP-0352" {
	secondary;
	address 130.60.23.114;
	port 520;
	peer address 130.60.23.4;
	peer port 520;
	max-response-delay 60;
	max-unacked-updates 10;
	load balance max seconds 3;
}

ddns-update-style none;
option domain-name-servers 130.60.128.3, 130.60.64.51;
option domain-name "unizh.ch";
authoritative;
log-facility local1;

# some (not all) of my hosts, classes and subclasses (for fixed  
addresses)

host PBG4 { hardware ethernet 00:0a:95:e6:89:2a; }
host CODEC { hardware ethernet 00:50:60:80:80:e9; }

class "PBG4" { match pick-first-value (option dhcp-client-identifier,  
hardware); }
class "CODEC" { match pick-first-value (option dhcp-client- 
identifier, hardware); }

subclass "PBG4" 1:0:0a:95:e6:89:2a;
subclass "CODEC" 1:0:50:60:80:80:e9;

# One of my subnets

subnet 130.60.225.0 netmask 255.255.255.128 {
	option routers 130.60.225.1;
	option broadcast-address 130.60.225.127;
	pool { allow members of "CODEC"; range 130.60.225.93; }
	pool { allow members of "PBG4"; range 130.60.225.90; }
	pool {
		failover peer "DHCP-0352";
		deny dynamic bootp clients;
		allow unknown-clients;
		range 130.60.225.20 130.60.225.80;
	}
	max-lease-time 21600;
}


BTW, I'm still not sure whether the statement "failover peer" should  
be the name of the server itself or the name of its peer? That is, on  
my server DHCP-0456 should the statement be "failover peer DHCP-0456"  
or "failover peer DHCP-0352"??


Thanks, Tina




More information about the dhcp-users mailing list