2

I want to deploy RHEL (6x64, though I think this should be applicable across versions) onto systems which may or may not have more than one NIC card.

Will kickstart error if I have multiple lines like

network --device=eth0 --bootproto=dhcp
network --device=eth1 --bootproto=dhcp
...

even if there is only one NIC on the host?

1 Answer 1

1

You don't have to specify the --device at all.

network --bootproto=dhcp should be enough. In fact, bootproto=dhcp by default so you shouldn't even need a network line, assuming that the kickstart script is grabbed over the network (like when installing via PXE).

If you want to control what interface is being used on systems with multiple interfaces, take a look at the 'ksdevice' boot option.

References:
Starting a Kickstart Install

Kickstart Options

6
  • That was my thinking, too, but only one adapter in a multiadapter system is getting an address
    – warren
    Jan 10, 2014 at 15:06
  • Why would you need more than one adapter to have an address during install? I can understand the need to specify which (and you can with ksdevice), but multiple?
    – user143703
    Jan 10, 2014 at 18:49
  • they're on different networks, and I want them to be up and running via dhcp from the get-go
    – warren
    Jan 10, 2014 at 19:37
  • I would just configure the interfaces in a post-install script. They'll be ready and online after the install is complete.
    – user143703
    Jan 10, 2014 at 19:42
  • 1
    It could, but that's usually easily correctable. Just need to set the correct name in /etc/udev/rules.d/70-persistent-net.rules. In the most recent versions of RHEL / CentOS there is a new package called biosdevname that may be of help. It's disabled by default except for a limited set of Dell servers, but the goal is consistent naming. Biosdevname - Consistent Network Device Naming
    – user143703
    Jan 10, 2014 at 20:59

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .