You shouldn't have to install NetworkManager for servers. It is *NOT*
your friend. Neither is DHCP for servers, since sometimes upstream
switches have not yet detected the active device by the time your
client has scurried its way through the local host restart. In
general, I keep servers set statically, and only set them to DHCP when
planning a migration. You might this and see if it brings up the
network at boot time reliably.

If the upstream detection is the issue, put a "sleep 10" in the
"start" stanza of /etc/nit.d/network. Amusingly enough, you can even
put it in /etc/sysconfig/network-scripts/ifcfg-eth0, although that can
get irritating and tools like system-config-network or NetworkManager
will happily overwrite it.


On Sat, Nov 30, 2013 at 11:44 AM, ~Stack~ <[log in to unmask]> wrote:
> On 11/30/2013 09:34 AM, olli hauer wrote:
>> Sample from my minimal unattended install config
>>> grep network minimal.cfg
>>  network --onboot yes --device eth0 --bootproto dhcp
>>
>> In case this param was not given check /etc/sysconfig/network
>>> grep -i network /etc/sysconfig/network
>>   NETWORKING=yes
>
> On 11/30/2013 09:23 AM, Tom H wrote:> On Sat, Nov 30, 2013 at 7:03 AM, >
> Do you have "--onboot=yes" on the "network" line of the kickstart
>> file?
>
> Hello! Thank you for the responses. I tinkered with a few variations,
> but have not made much progress.
>
> I started out with this line in my kickstart:
> network --bootproto=dhcp --device=eth0 --onboot=on
>
> And I thought maybe that was the problem, but even after the change I
> still have the same problem with no DHCP on boot. Here is some more
> information:
>
> $ sed -e '/^#/d' -e '/^$/d'  anaconda-ks.cfg
> install
> url --url=http://192.168.1.34/scientificlinux/6.4/x86_64/os
> lang en_US.UTF-8
> keyboard us
> network --onboot yes --device eth0 --mtu=1500 --bootproto dhcp
> rootpw  --iscrypted
> $6$p86*T9ho$nNJYlm8M9ocYpBDsEUhLv74Uw12DuAi4N5a558PXBWAQwS0P9ZGC0ZTAe4l6/oKOaaWzek3w.PuDBori9WIB81
> reboot
> firewall --service=ssh
> authconfig --useshadow --passalgo=sha512
> selinux --enforcing
> timezone --utc America/Chicago
> bootloader --location=mbr --driveorder=sda --append="crashkernel=auto
> rhgb quiet" --password=$1$YHRi71$G/Lmi/o1xz60RrBLSeyCU/
> repo --name="SL"
> --baseurl=http://192.168.1.34/scientificlinux/6.4/x86_64/os --cost=100
> repo --name="SLFastbugs"
> --baseurl=http://192.168.1.34/scientificlinux/6.4/x86_64/updates/fastbugs/
> --cost=1000
> repo --name="SLSecurity"
> --baseurl=http://192.168.1.34/scientificlinux/6.4/x86_64/updates/security/
> --cost=1000
> %packages --nobase
> @Core
> %end
> %post --interpreter=/bin/bash
> yum install -y --nogpgcheck
> http://yum.puppetlabs.com/el/6/products/x86_64/puppetlabs-release-6-7.noarch.rpm
> yum install -y puppet
> chkconfig puppet on
> %end
>
> $ cat /etc/sysconfig/network-scripts/ifcfg-eth0
> DEVICE="eth0"
> BOOTPROTO="dhcp"
> HWADDR="00:22:19:E1:28:36"
> IPV6INIT="yes"
> MTU="1500"
> NM_CONTROLLED="yes"
> ONBOOT="yes"
> TYPE="Ethernet"
> UUID="61008086-5e0e-4db2-8732-5b62bf5fc866"
>
> I changed that to the following, but still it doesn't get a DHCP IP
> until I run `ifup eth0`:
> DEVICE="eth0"
> BOOTPROTO="dhcp"
> HWADDR="00:22:19:E1:28:36"
> IPV6INIT="yes"
> MTU="1500"
> NM_CONTROLLED="no"
> NETWORKING="yes"
> ONBOOT="yes"
> TYPE="Ethernet"
> UUID="61008086-5e0e-4db2-8732-5b62bf5fc866"
>
> I went back to the original ifcfg-eth0 and installed NetworkManager (and
> all of these other packages: ConsoleKit ConsoleKit-libs ModemManager
> NetworkManager-glib avahi-autoipd dbus dnsmasq eggdbus libdaemon
> libgudev1 libnl libpcap libudev mobile-broadband-provider-info polkit
> ppp wpa_supplicant), and now I get a DHCP IP on boot, but I don't
> understand why I have to install a bunch of extra packages to get a DHCP
> IP on boot.
>
> What am I missing here?
>
> Thank you!
>
> ~Stack~
>
>