chelenegro
MIS
I had been assuming that when a router (Cisco) detects a DHCP address conflict, it would at some point reassign the address. Unfortunately, I've discovered that that's wrong and if an address conflict is detected, the address is removed from the pool, and the address will not be assigned until an administrator resolves the conflict.
We have routers where a significant portion of their available address pool is taken by conflicts. I can't find any reference in Cisco documentation or in this forum mail threads to a "timeout" feature of some sort to automatically clear these conflicts. Perhaps disabling conflict logging would accomplish the same thing, though for troubleshooting purposes it's nice to know if there are excessive conflicts. It occurs to me that we need a process to review and remove these manually if we can't get a way to do it automatically. The result where sites run routers for long periods of time between reboots will be service calls to us because the site runs out of available address space.
Any idea is appreciated.
Jose Luis Martin Cenjor - CCNP, PMP
HP Managed Services - WAN
We have routers where a significant portion of their available address pool is taken by conflicts. I can't find any reference in Cisco documentation or in this forum mail threads to a "timeout" feature of some sort to automatically clear these conflicts. Perhaps disabling conflict logging would accomplish the same thing, though for troubleshooting purposes it's nice to know if there are excessive conflicts. It occurs to me that we need a process to review and remove these manually if we can't get a way to do it automatically. The result where sites run routers for long periods of time between reboots will be service calls to us because the site runs out of available address space.
Any idea is appreciated.
Jose Luis Martin Cenjor - CCNP, PMP
HP Managed Services - WAN