On Fri, Apr 6, 2012 at 6:23 PM, zxq9 <[email protected]> wrote: > On 04/07/2012 03:28 AM, Konstantin Olchanski wrote: > >> I tend to think that these days one should go back to static IP addresses >> for server-type machines, after all, all DHCP, network manager& co do is >> assign >> the same IP address to the same machine over and over and over again with >> the only >> variation when they fail to do the boring thing and you have a machine >> down, staying >> down until somebody physically walks to it to reboot it. >> > > Do you mean there are serious networks that use DHCP by default for > systems other than transient network guests residing in their own little > subnet (like laptops)? And server IP assignment by DHCP... I can't believe > this is really done, or am I being naive about naivete? > Yes, there are. I've done for Beowulf clusters of hundreds of servers. It's very handy to be able to have a single kickstart file, with DHCP reservations, to assign hostnames and roles for rebuilding machines. It's also handy for installation test environments. I've also used it for multiple-OS hosts, to stabilize their network configuraton and allow changes to propagate even after the host is rebooted to the other OS. It's also very useful for PXE and live CD booting, to assure that the machine being recovered is at the same network location as the hardware being reviewed, tested, or patched.
Mind you, many environments refuse to use it as their *standard* network configuraton, because they consider the DHCP server itself a point of failure that should be avoided in a server environment. But I find > That just sounds like a recipe for disaster for a lot of reasons. Without > some thought and preparation any network setup is doomed to get wacky after > a while, and maybe I'm just being too old school -- but being explicit > about setup I've never had a single network problem like the ones described > here, whether letting NM run the show or using the older networking > subsystem. > And the DHCP is very, very helpful for cleaning up the wackiness. Updating DNS servers and searchable domains, manually, really stinks. >
