*** From dhcp-server -- To unsubscribe, see the end of this message. ***
On Tue, 11 May 1999, Ted Lemon wrote:
> Not yet. The best mechanism to use currently is two servers serving
> different address ranges, or two servers serving the same set of
> static addresses, or a combination of both.
>
> > Some positive answer would be needed before the computer centre in this
> > college would consider changing from their failure prone NT DHCP server
> > to the ISC server running on Linux.
I listened to Ted's advice a while back, and we implemented 2 servers with
disjoint address pools this past semester. It works great! In the
upgrade process, I forgot to add dhcpd in my rc3.d directory (oops) on one
server. One power outage later all classrooms on campus were still up and
working for professors with laptops. That second server saved me, and
allowed classes to function without any problems once power was restored.
If your management needs more convincing, point out the following:
The ISC DHCP code is very reliable. Anyone on this list will attest to
that.
It's widely used. It's on every continent. I got the e-mails to prove
it. Antarctica? Yep, it's there too.
You have easy access to a good support base (this list), and to the main
developer. Try getting anything except "just reboot the server", or "add
more RAM" from a certain other company's tech support..
Disjoint pools work.
This code actually follows RFC standards
You can purchase a support plan
I haven't had a single call because someone hasn't been able to get an IP
since we've put the ISC server in place.
Our server downtime has been limited only to power outages. I haven't had
to restart the process, or anything like that. I guess you could say that
it's completely hands free once you set up your config file.
As someone else on this list put it, "it's fire and forget technology"
If you want to, you can cut over slowly to it. Have disjoint pools
between the NT server, and your ISC server. That way, if you find the ISC
to be unreliable (yeah, right), you're able to switch back to the NT
"solution". This gives you a chance to prove that the product is good,
while providing management the warm-fuzzies of having a way to undo things
in a "worst-case" scenario.
All it will cost to give it a try is at most a few hours of your time, and
some CPU time on some server.
Keep pushing for it. It's worth it, and good luck.
Brian Davidson
Server Administrator
George Mason University
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
Archives for this mailing list are available at
http://www.webnology.com/list-archives/dhcp/dhcp-server
------------------------------------------------------------------------------
