Since this is a small shop, you probably have enough IP addresses that you
can have the new DHCP server issue different addresses than the old ones,
at which point you don't really care if some boxes get stuck on the old
ones for a while.
David Lang
On Mon, 15 Oct 2012, David Parter wrote:
and then plan for a convenient squirell suicide at the transformer that
night (power outage forcing a reboot).
--david
On Mon, 15 Oct 2012, Roy McMorran wrote:
The ancient Sun Fire 280R that's been our DHCP server for about a
decade needs to be out of here, and soon. It's running the stock
Solaris 10 DHCP server software. I'm inclined to let one of our
Windows 2008 R2 servers take over the DHCP duties (although I might be
persuaded to go a different way, e.g. ISC DHCP on RedHat, but DNS is
already on Windows so...). This is a pretty small environment, with
only about 130 dynamically-assigned addresses, all in one contiguous
range. I assume there's no way to transport the current lease
information between such disparate servers. Any suggestions on making
the transition go smoothly?
change the lease time to a small value, wait until everyone has new
leases with this smaller value, then swap out the servers when they are
all home overnight.
the only people who will be affected are then ones who are online at the
time you change the server.
_______________________________________________
Tech mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
