Converting from load sharing to stand alone
Ian.Anderson at clearwire.com
Sun Jun 10 18:44:37 UTC 2007
In case anyone ever runs across this, migrating from load sharing to standalone is easy.
Stop both dhcp servers (This is a must in order to keep the dhcpd.leases file from being updated)
Edit your config file and remove the "pool" statements and just use "range". (I am not sure if this step is required but that is what I did)
Comment out the failover-include file in dhcpd.conf
dhcpd is going to complain about an unknown directive for "failover peer" in the dhcpd.leases file, but it will continue to load. After it has processed the dhcpd.leases file, it removes the failover declaration from it. You will have slightly higher load on the server as the server-identifier for the secondary server no longer exists, so clients will need to do a full DHCPDISCOVER to get an IP.
From: dhcp-users-bounce at isc.org on behalf of Ian Anderson
Sent: Fri 6/8/2007 12:06 PM
To: dhcp-users at isc.org
Subject: Converting from load sharing to stand alone
We are having some problems with our dhcp servers in a failover setup. Our managment has asked me to convert the failover setup to a stand alone. (Against my better judgment) I know dhcpd.leaes keeps track of every ip address for both peers, but are their any pitfalls I should be aware of when converting to this? My plan was to copy the dhcpd.leases file from the current primary server, and remove the "failover" stanzas that dictate what state each peer is in. I know there are additional fields for each lease, but my hope is dhcp will recognize this field as not needed and simply ignore it. Is this correct, or am I biting off more than I can chew?
More information about the dhcp-users