> From: [email protected] [mailto:[email protected]] > On Behalf Of Roy McMorran > > 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?
Just configure the new server to ping an IP before assigning that IP to a new client. (I forget what it's called, but there's a checkbox in Windows DHCP server, disabled by default, to enable this test.) And then simply shut off the old server. It doesn't matter if the new server has any knowledge of the old leases. (Provided that you copy over all the scope options and reservations, if any.) I just looked it up - it's called "conflict detection" and it's a numeric field, "number of attempts" which is set to 0 by default. Just make it 1 or 2. You can also lookup somewhere, what precisely is used to detect conflicts (arp vs ping vs whatever). That's configurable somehow - might be domain policy, or registry settings or something. Off the top of my head, I think it uses arp by default, and no ping. When I looked at it before, I decided the default was good, and didn't need to be changed. _______________________________________________ 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/
