dhcpd 3.0.1 stops responding to requests

[Wil Birkmaier]

Hello All, I have tried searching thru the archives as well as google
the last couple days and have come to my wits end trying to figure this
one out.  The only thought I have at this point is the failover has
problems with using other ports (Using 521 instead of 520) or WANs
 

In the archives I found something similar with a 3.0.beta client but
never saw an answer.  After X amount of hours, either from 3 to 18
hours, the DHCPd server stops accepting and responding to requests.

 

Nothing shows in the logs, other than the normal traffic. 

May 22 10:56:12 repsws02 dhcpd: DHCPACK to 10.40.4.122
(00:12:79:56:0e:f1) via 10.40.4.4

May 22 10:56:12 repsws02 dhcpd: DHCPINFORM from 10.40.4.122 via
10.40.4.5

May 22 10:56:12 repsws02 dhcpd: DHCPACK to 10.40.4.122
(00:12:79:56:0e:f1) via 10.40.4.5

May 22 10:56:16 repsws02 dhcpd: DHCPINFORM from 10.40.4.122 via
10.40.4.4

May 22 10:56:16 repsws02 dhcpd: DHCPACK to 10.40.4.122
(00:12:79:56:0e:f1) via 10.40.4.4

May 22 10:56:16 repsws02 dhcpd: DHCPINFORM from 10.40.4.122 via
10.40.4.5

May 22 10:56:16 repsws02 dhcpd: DHCPACK to 10.40.4.122
(00:12:79:56:0e:f1) via 10.40.4.5

May 22 10:56:16 repsws02 dhcpd: BOOTREQUEST from 00:01:42:0a:05:c0 via
172.17.64.3: network unknown

May 22 10:56:49 repsws02 dhcpd: BOOTREQUEST from 00:01:42:09:fd:00 via
172.17.65.1: network unknown

May 22 10:56:53 repsws02 dhcpd: BOOTREQUEST from 00:01:42:0a:05:c0 via
172.17.64.3: network unknown 

 

It just then stops

 

 

My set up is Red Hat 4 ES with the DHCPd 3.0.1  I have it set up in
failover mode using Port 521.  All the requests from cisco VLANs are
forwarded via the ip helper command over our WAN.

 

Below is a snippet of what I have in the DHCPD.CONF

 

My DHCPD.CONF is:

failover peer "peer2" {

        primary;

        address repsws02.bea.com;

        port 521;

        peer address rcpsws01.bea.com;

        peer port 521;

        max-response-delay 60;

        max-unacked-updates 10;

        mclt 600;

        split 255;

        load balance max seconds 3;

}

 

# Blank subnet declaration for local network

subnet 10.160.29.0 netmask 255.255.255.0 {

}

 

include "/etc/dhcp/global.conf";

include "/etc/dhcp/master2.conf";

 

GLOBAL.CONF

ddns-update-style interim;

allow client-updates;

authoritative;

 

option domain-name              "bea.com";

option ntp-servers              172.XXX.XX.13;

option nis-domain               "beasys.com";

option nis-servers              206.XXX.XXX.10;

 

default-lease-time              259200;

max-lease-time                  259200;

use-host-decl-names             on;

 

MASTER2.CONF

 

option domain-name-servers      10.XXX.XXX.86, 10.XXX.XXX.86;

option netbios-name-servers     10.XXX.XXX.52, 172.XXX.XXX.35;

 

subnet 10.38.0.0 netmask 255.255.255.0 {

        pool {

                failover peer           "peer2";

                range           10.38.0.100 10.38.0.254;

                deny dynamic bootp clients;

        }

        option subnet-mask              255.255.255.0;

        option routers          10.38.0.1;

}

 

subnet 10.40.0.0 netmask 255.255.255.0 {

        pool {

                failover peer           "peer2";

                range           10.40.0.250 10.40.0.254;

                deny dynamic bootp clients;

        }

        option subnet-mask              255.255.255.0;

        option routers          10.40.0.1;

}

 

Thanks!

 

Wil

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.