DHCP servers using failover

Marc Werner marc.werner at cc-itzehoe.de
Tue Aug 25 10:38:42 UTC 2009


Ouch! That's the point. Now it works fine. Many thanks!

Greets
Marc

Am Dienstag, den 25.08.2009, 11:18 +0200 schrieb Hendrickx Stijn:
> ...
>    address 10.16.1.126;
>    port 647;
>    peer address 10.16.1.127;
>    port 647;                  -> change this to "peer port 647;"
> ...
>    address 10.16.1.127;
>    port 647;
>    peer address 10.16.1.126;
>    port 647;                  -> change this to "peer port 647;"
> ...
> 
> Greets,
> 
> Stijn
> 
>  
>  
> 
> 
> -----Oorspronkelijk bericht-----
> Van: dhcp-users-bounces at lists.isc.org [mailto:dhcp-users-bounces at lists.isc.org] Namens Marc Werner
> Verzonden: dinsdag 25 augustus 2009 11:02
> Aan: dhcp-users at lists.isc.org
> Onderwerp: DHCP servers using failover
> 
> Hello folks,
> 
> I'm trying to configure two DHCP servers using the failover option. Both
> servers are running RHEL5 with the isc-dhcpd-V3.0.5-RedHat. The system
> clocks are synchronized.
> 
> Here are the config number one:
> 
> ###
> failover peer "dhcp-failover2" {
>    primary;
>    address 10.16.1.126;
>    port 647;
>    peer address 10.16.1.127;
>    port 647;
>    max-response-delay 30;
>    max-unacked-updates 10;
>    load balance max seconds 3;
>    mclt 1800;
>    split 128;
> }
> 
>  pool {
>       failover peer "dhcp-failover2"; 
>       deny dynamic bootp clients;
>       range 10.xx.xx.1 10.xx.xx.30;
>       allow members of "xyz"; 
>    }
> 
> ###
> 
> ....and number two:
> 
> ###
> failover peer "dhcp-failover" {
>    secondary;
>    address 10.16.1.127;
>    port 647;
>    peer address 10.16.1.126;
>    port 647;
>    max-response-delay 30;
>    max-unacked-updates 10;
>    load balance max seconds 3;
> }
>  
>   pool {
>       failover peer "dhcp-failover"; 
>       deny dynamic bootp clients;
>       range 10.xx.xx.1 10.xx.xx.30;
>       allow members of "xyz";  
>    }
> ###
> 
> /var/log/messages says: 
> 
> failover peer dhcp-failover: I move from recover to startup
> dhcpd: dhcpd startup succeeded
> dhcpd: failover peer dhcp-failover: I move from startup to recover
> 
> I expected the servers to start synchronisation after the mclt (half an hour). But nothing happens. Not even an error message (e.g. timeout).
> Did anyone had the problem and may provide me some information about what went wrong?
> Many thanks in advance!
> 
> Kind regards
> M.Werner
> 
> _______________________________________________
> 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




More information about the dhcp-users mailing list