uid lease is duplicate?

Matt Ashfield mda at unb.ca
Thu Nov 1 13:31:49 UTC 2007


Hello,

Running 3.0.5-Redhat. We're having a problem where a client computer is
unable to obtain an address. We are running two servers in peer mode and the
logs of the server look like (please ignore timestamps as they may not
correlate, just grabbed some problem lines) the following:

 

First server:

Nov  1 10:16:02 newpluto dhcpd: DHCPDISCOVER from 00:01:6c:ea:36:ad
(IBM-7773F56AF6C) via 131.202.96.1

Nov  1 10:16:02 newpluto dhcpd: DHCPOFFER on 131.202.98.173 to
00:01:6c:ea:36:ad (IBM-7773F56AF6C) via 131.202.96.1

Nov  1 10:16:03 newpluto dhcpd: uid lease 131.202.98.200 for client
00:01:6c:ea:36:ad is duplicate on 131.202.96/22

Nov  1 10:16:03 newpluto dhcpd: DHCPREQUEST for 131.202.98.173
(131.202.3.124) from 00:01:6c:ea:36:ad (IBM-7773F56AF6C) via 131.202.96.1

Nov  1 10:16:03 newpluto dhcpd: DHCPACK on 131.202.98.173 to
00:01:6c:ea:36:ad (IBM-7773F56AF6C) via 131.202.96.1

Nov  1 10:16:04 newpluto dhcpd: DHCPDISCOVER from 00:01:6c:ea:36:ad via
131.202.96.1: load balance to peer pluto

Nov  1 10:16:09 newpluto dhcpd: DHCPDISCOVER from 00:01:6c:ea:36:ad via
131.202.96.1

Nov  1 10:16:09 newpluto dhcpd: DHCPOFFER on 131.202.98.200 to
00:01:6c:ea:36:ad (IBM-7773F56AF6C) via 131.202.96.1

Nov  1 10:16:10 newpluto dhcpd: uid lease 131.202.96.90 for client
00:01:6c:ea:36:ad is duplicate on 131.202.96/22

Nov  1 10:16:10 newpluto dhcpd: DHCPREQUEST for 131.202.98.200
(131.202.3.124) from 00:01:6c:ea:36:ad (IBM-7773F56AF6C) via 131.202.96.1

Nov  1 10:16:10 newpluto dhcpd: DHCPACK on 131.202.98.200 to
00:01:6c:ea:36:ad (IBM-7773F56AF6C) via 131.202.96.1

 

2nd Server:

Nov  1 10:29:44 mercury dhcpd: DHCPDISCOVER from 00:01:6c:ea:36:ad via
131.202.96.1: peer holds all free leases

Nov  1 10:29:45 mercury dhcpd: DHCPREQUEST for 131.202.96.90 (131.202.3.124)
from 00:01:6c:ea:36:ad via 131.202.96.1: lease 131.202.96.90 unavailable.

Nov  1 10:29:45 mercury dhcpd: DHCPNAK on 131.202.96.90 to 00:01:6c:ea:36:ad
via 131.202.96.1

 

If we shut off the 2nd server, the client is able to obtain an address. If
we shut off the first server and keep the 2nd one running, the client cannot
get an address and spits out the following log entries:

Nov  1 10:29:46 mercury dhcpd: DHCPDISCOVER from 00:01:6c:ea:36:ad via
131.202.96.1: peer holds all free leases

Nov  1 10:25:11 mercury dhcpd: DHCPDISCOVER from 00:01:6c:ea:36:ad via
131.202.96.1: peer holds all free leases

 

This is only happening for 2 machines on our campus, the rest (about 200
others) work fine. Any help is appreciated.

 

Thanks

 

Matt 

mda at unb.ca

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20071101/370d1790/attachment.html>


More information about the dhcp-users mailing list