Re: Rép. : DHCP Failover not working
Ryan McCain
Ryan.McCain at dss.state.la.us
Fri Dec 8 17:27:40 UTC 2006
Ok. I will download the 3.05. Has anyone seen a SLES 9/10 rpm for this version?
Thanks, Ryan
>>> On Thu, Dec 7, 2006 at 3:52 PM, in message <s5784700.034 at bp.cslaval.qc.ca>,
"Serveur-Faucon Surveillance" <SrvFaucon at cslaval.qc.ca> wrote:
> I am not sure, but I think between version 3.0.1 and 3.0.3 the leases format
> is not compatible.
> Of course, the better road is to use the same version on both server.
>
> Also, 3.0.5 is out, and is more mature. There where some errors before
> version 3.0.3 with failover so upgrading is recommended.
>
>
> ---------------------------------------------------
> Alexandre Racine - Gardien Virtuel - Sécurité Informatique
> www.gardienvirtuel.com
> Montréal, Québec, Canada
>>>> Ryan.McCain at dss.state.la.us 2006- 12- 07 13:05:42 >>>
>
>
> I am attempting to get DHCP failover working between a SLES 9 s390 box
> running dhcp- server- 3.0.1rc13- 28.18 and a SLES 10 s390x box running
> dhcp- server- 3.0.3- 23.5.
>
> The primary is the SLES 9 box.
>
> I start both of them and both output this to the logs:
>
> failover peer failover: I move from recover to startup
> failover peer failover: I move from startup to recover
>
> Is that right?
>
>
> Also, when stop dhcpd on the primary server, the secondary server logs
> this:
>
> Dec 6 16:41:31 dss- ml93la10 dhcpd: failover: listener: no matching
> state
>
> and never takes over handling dhcp requests.
>
> ---
>
> below are sniplets from the dhcpd.conf files for the primary and
> secondary servers, respectively.
>
> ---- PRIMARY inet addr:10.120.11.70 Bcast:10.120.11.255
> Mask:255.255.252.0----
>
>
> failover peer "failover" {
> primary; # declare this to be the primary server
> address 10.120.11.70;
> port 520;
> peer address 10.120.11.95;
> peer port 520;
> max- response- delay 30;
> max- unacked- updates 10;
> load balance max seconds 3;
> mclt 1800;
> split 128;
> }
>
> authoritative;
> log- facility local3;
> subnet 10.120.11.0 netmask 255.255.255.0 {
> }
>
> subnet 10.125.4.0 netmask 255.255.252.0 {
> option routers 10.125.7.254;
> pool {
> failover peer "failover";
> deny dynamic bootp clients;
> range 10.125.4.1 10.125.7.179;
> }
> }
>
>
> ---- SECONDARY inet addr:10.120.11.95 Bcast:10.120.11.255
> Mask:255.255.252.0 ----
>
> #authoritative;
> log- facility local3;
> subnet 10.120.11.0 netmask 255.255.255.0 {
> }
>
> failover peer "failover" {
> secondary; # declare this to be the secondary server
> address 10.120.11.95;
> port 520;
> peer address 10.20.11.70;
> peer port 520;
> max- response- delay 30;
> max- unacked- updates 10;
> load balance max seconds 3;
> }
>
> subnet 10.125.4.0 netmask 255.255.252.0 {
> option routers 10.125.7.254 ;
> pool {
> failover peer "failover";
> deny dynamic bootp clients;
> range 10.125.4.1 10.125.7.179;
> }
> }
>
> ------
>
>
> any ideas?
More information about the dhcp-users
mailing list