[cisco-voip] suggested/best practices for DHCP settings on routers

[Lelio Fulgenzi]

Yeah, we're gonna have to set up an alarm for when we get these so we can go back and clear them. I'd rather have a ip address conflict logged than to have an actual ip address conflict occur. 


--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message -----
From: "Robert Kulagowski" <rkulagow at gmail.com> 
To: "cisco-voip (cisco-voip at puck.nether.net)" <cisco-voip at puck.nether.net> 
Sent: Tuesday, May 10, 2011 11:23:59 AM 
Subject: Re: [cisco-voip] suggested/best practices for DHCP settings on routers 

On Mon, May 9, 2011 at 3:16 PM, Ryan Ratliff <rratliff at cisco.com> wrote: 
> An address conflict occurs when two hosts use the same IP address. During 
> address assignment, DHCP checks for conflicts using ping and gratuitous 
> Address Resolution Protocol (ARP). If a conflict is detected, the address is 
> removed from the pool. The address will not be assigned until the 
> administrator resolves the conflict. 
> 
> Yes it does. 
> -Ryan 

We ended up adding: 

no ip dhcp conflict logging 

to our router configuration so that we wouldn't end up with _all_ 
addresses unassignable. 
_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20110510/eb882a37/attachment.html>