Re: DHCP Conflict

From: gladston@br.ibm.com
Date: Tue Sep 06 2005 - 11:33:03 GMT-3


It seems the DOC CD is wrong about disabling conflict logging.

Tests shows logging conflict is very useful, even if not configuring a DHCP database agent:

Any comments appreciated.

Tests:

Rack2R1#sh ip dhc conflict
IP address Detection method Detection time VRF

*Feb 28 22:45:46: DHCPD: DHCPDISCOVER received from client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30 through relay 148.5.46.4.
*Feb 28 22:45:46: DHCPD: Sending DHCPOFFER to client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30 (148.5.46.1).
*Feb 28 22:45:46: DHCPD: unicasting BOOTREPLY for client 0000.0c3b.d6a9 to relay 148.5.46.4.
*Feb 28 22:45:46: DHCPD: DHCPREQUEST received from client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30.
*Feb 28 22:45:46: DHCPD: Sending DHCPACK to client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30 (148.5.46.1).
Rack2R1#
*Feb 28 22:45:46: DHCPD: unicasting BOOTREPLY for client 0000.0c3b.d6a9 to relay 148.5.46.4.
Rack2R1#
*Feb 28 22:45:50: DHCPD: DHCPDECLINE received from client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30.
*Feb 28 22:45:50: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30 declined 148.5.46.1.
Rack2R1#
*Feb 28 22:45:50: DHCPD: DHCPDISCOVER received from client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30 through relay 148.5.46.4.
Rack2R1#
*Feb 28 22:45:52: DHCPD: Sending DHCPOFFER to client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30 (148.5.46.2).
*Feb 28 22:45:52: DHCPD: unicasting BOOTREPLY for client 0000.0c3b.d6a9 to relay 148.5.46.4.
*Feb 28 22:45:52: DHCPD: DHCPREQUEST received from client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30.
*Feb 28 22:45:52: DHCPD: client rejected 148.5.46.2, sent 148.5.46.104.
*Feb 28 22:45:52: DHCPD: DHCPREQUEST received from client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30.
Rack2R1#
*Feb 28 22:45:54: DHCPD: DHCPREQUEST received from client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30.
Rack2R1#
*Feb 28 22:45:56: DHCPD: DHCPREQUEST received from client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30.

Rack2R1#sh ip dhc conflict
IP address Detection method Detection time VRF
148.5.46.1 Gratuitous ARP Feb 28 1993 10:45 PM

*Feb 28 22:46:12: DHCPD: DHCPDISCOVER received from client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30 through relay 148.5.46.4.
Rack2R1#
*Feb 28 22:46:14: DHCPD: Sending DHCPOFFER to client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30 (148.5.46.3).
*Feb 28 22:46:14: DHCPD: unicasting BOOTREPLY for client 0000.0c3b.d6a9 to relay 148.5.46.4.
*Feb 28 22:46:14: DHCPD: DHCPREQUEST received from client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30.
*Feb 28 22:46:14: DHCPD: client rejected 148.5.46.3, sent 148.5.46.105.
Rack2R1#
Rack2R1#
*Feb 28 22:46:33: DHCPD: DHCPDISCOVER received from client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30 through relay 148.5.46.4.
Rack2R1#
*Feb 28 22:46:35: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 148.5.46.4.
Rack2R1#
*Feb 28 22:46:37: DHCPD: Sending DHCPOFFER to client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30 (148.5.46.5).
*Feb 28 22:46:37: DHCPD: unicasting BOOTREPLY for client 0000.0c3b.d6a9 to relay 148.5.46.4.
*Feb 28 22:46:37: DHCPD: DHCPREQUEST received from client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30.
*Feb 28 22:46:37: DHCPD: client rejected 148.5.46.5, sent 148.5.46.106.

Rack2R1#sh ip dhc conflict
IP address Detection method Detection time VRF
148.5.46.1 Gratuitous ARP Feb 28 1993 10:45 PM
148.5.46.4 Ping Feb 28 1993 10:46 PM

*Feb 28 22:47:02: DHCPD: DHCPDISCOVER received from client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30 through relay 148.5.46.4.
Rack2R1#
*Feb 28 22:47:03: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 148.5.46.6.
Rack2R1#
*Feb 28 22:47:05: DHCPD: Sending DHCPOFFER to client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30 (148.5.46.7).
*Feb 28 22:47:05: DHCPD: unicasting BOOTREPLY for client 0000.0c3b.d6a9 to relay 148.5.46.4.
*Feb 28 22:47:05: DHCPD: DHCPREQUEST received from client 0063.6973.636f.2d30.3030.302e.3063.3362.2e64.3661.392d.4574.30.
*Feb 28 22:47:05: DHCPD: client rejected 148.5.46.7, sent 148.5.46.107.

Rack2R1#sh ip dhc conflict
IP address Detection method Detection time VRF
148.5.46.1 Gratuitous ARP Feb 28 1993 10:45 PM
148.5.46.4 Ping Feb 28 1993 10:46 PM
148.5.46.6 Ping Feb 28 1993 10:47 PM



This archive was generated by hypermail 2.1.4 : Sun Oct 02 2005 - 14:40:14 GMT-3