These messages are caused by the fact that in default configuration, the DHCP lease record (which station was assigned which IP address) are held only in the RAM of the router or switch. When you reload it, these leases are forgotten, and when DHCP server starts assigning IP addresses anew, it may try to assign an address that is already being used (assigned previously). Hence the messages.
The only solution is to configure a permanent storage for the leases. This is called DHCP Server Database. Information about this functionality and the configuration can be found, for example, here:
In short, the idea is to have the switch store these leases permanently to a network-accessible server via TFTP, FTP or HTTP. When the switch reloads, it downloads the stored leases file and continues assigning the addresses appropriately.
Python based Script to BULK Import/Delete devices using Cisco Prime API
Check my Repo on GitHub for all the details ( see below link )
ASR9001 DC chassis doesn't prints a syslog incase voltage for one of the Power Modules goes below certain threshold. Because of this the monitoring of PowerModule for any failure becomes difficult. This may cause outage incase of double fa...
16.6.4 Beta Release for Catalyst Switches
Enterprise Switching Business Unit is happy to announce availability of first Beta release of 16.6.4. This will be the first beta rebuild on the 16.6.4 targeted towards Catalyst 9500/9400/9300/3850/36...