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.
Let's clarify Spanning Tree Protocol, because it can be confusing.
I’m going to make this as painless as possible in the short beginning of this post, but details will follow for the rest that are curious in nature.
DOMINO168.NET BANDAR JUDI POKER ONLINE TERPERCAYA DI INDONESIADomino168.net merupakan situs agen bandarq, bandarkiu, agen bandarq, bandar66, bandar qq online terbaik,agen judi domino terpercaya. Connection alternatif bandarq, Daftar bandarkiu online terpe...
i have one switch and two ports for two dirrent network they is ring both port in same vlan configuration, i want solution if one port down then autometic traafic gone from 2nd port it is possible? Note: switch1 in 2 ethernet port avaibal...
How to upgrade Cisco IOS from Serial Port
In this topic, i will show how to upgrade Cisco IOS from the Serial Port using a console cable and Hyper Terminal without network connectivity (that would be needed for TFTP, in example). We will be using a 2960X...