Anaconda/kickstart: Bonding Device Not Created As Expected

Home » CentOS » Anaconda/kickstart: Bonding Device Not Created As Expected
CentOS 1 Comment


I am currently struggling with the right way to configure a bonding device via kickstart (via PXE).

I am installing servers which have “eno” network interfaces. Instead of the expected bonding device with two active slaves (bonding mode is balance-alb), I get a bonding device with only one active slave and an independent, non-bonded network device. Also the bonding device gets its MAC address from the second instead of from the first device.

I appreciate any hint (or rtfm with the name of the correct fm ;-) on how to achieve the desired setup through kickstart. Please find the used PXE and kickstart settings and resulting network configuration below.

I did this with CentOS 7.2.1511. We cannot go further due to Infiniband and lustre drivers which are currently only supported for this CentOS
7.x version

Cheers frank


One thought on - Anaconda/kickstart: Bonding Device Not Created As Expected

  • Hi Frank,

    This is from my satellite kickstart where I’m building the bond at the point of PXE booting, and using static (I’m working on doing this with DHCP and tagged VLANs but currently cant get to the hardware needed since messing up the BMC config :( )

    LABEL linux
    KERNEL boot/RedHat-7.3-x86_64-vmlinuz
    APPEND initrd=boot/RedHat-7.3-x86_64-initrd.img ks= ks.device=bootif network ks.sendmac bond=bond0:eno1,eno2:mode