search for: bondopts

...network" kickstart section: # "Public" network, bond0 created, it works fine, network --device=bond0 --noipv6 --bootproto=static --onboot=yes --hostname=box.example.com --ip=192.168.1.3 --netmask=255.255.255.0 --gateway=192.168.1.1 --nameserver=192.168.1.1 --bondslaves=p1p1,p1p2 --bondopts=mode=active-backup,primary=p1p1,miimon=80,updelay=60000 # Cluster network, not created on install network --device=bond1 --noipv6 --nodns --nodefroute --bootproto=static --onboot=yes --ip=192.168.2.2 --netmask=255.255.255.0 --bondslaves=em1,em2 --bondopts=mode=active-backup,primary=em1,miimon=80,...

...append initrd=centos-7/initrd.img ip=dhcp nameserver=xx.xx.xx.xx ksdevice=eno1 inst.repo=http://our.mirror.server/7/os/x86_64 inst.ks.sendmac inst.ks=http://our.kickstart.server/ks.cgi and the network settings in the kickstart file are network --device bond0 --bondslaves=eno1,eno2 --bondopts=mode=balance-alb --bootproto=dhcp --hostname=myhost --activate I would have expected to get a bonding device with eno1 and eno2 as slave devices, the bonding device inheriting the MAC address from eno1 (otherwise DHCP won't work). Instead the result is a bonding device with eno2 as - sole...

...really don't want to have to manually manipulate the ifcfg-bond* interfaces and create the ifcfg-BRIDGE* interfaces manually so I'd like this to work. # Configure a bond over the slaves in failover mode network --device=bond0 --noipv6 --bootproto=dhcp --onboot=yes --bondslaves=em1,em2 --bondopts=mode=active-backup;primary=em1 --activate # Configure VLANs network --device=bond0 --vlanid=11 --noipv6 --onboot=yes --bootproto=dhcp --activate network --device=bond0 --vlanid=100 --noipv6 --onboot=yes --bootproto=dhcp --activate network --device=bond0 --vlanid=302 --noipv6 --onboot=yes --bootpro...

...m bonded interfaces. Has anyone managed to get this working? Bonding modes 1, 5, 6 work fine, and they do not need any particular support on the switch. But modes 0, 2-4 are a different story, no luck here. network --onboot yes --device bond0 --activate --bootproto static --bondslaves=eth0,eth1 --bondopts=mode=balance-rr,miimon=100 --ip 1.2.3.4 --netmask 255.255.255.0 --gateway 1.2.3.1 --nameserver 1.2.3.99 --hostname server network --onboot yes --device eth0 --activate No interactive shell becomes available on vc 2, all I see logged on vc 3 is that eth0 becomes active. Then bond0 becomes active, a...

...convert my kickstart file using the new bonding feature. The kickstart file has: network --onboot=yes --noipv6 --device=eth0 --bootproto=static network --onboot=yes --noipv6 --device=eth1 --bootproto=static network --onboot=yes --noipv6 --device=bond0 --bootproto=static --bondslaves=eth0,eth1 --bondopts=... Kickstart gives an error to the bond0 line saying "The provided network interface bond0 does not exist". Why? Then I put a 'modprobe bonding' line to my %pre section. Now same error in the following line: network --onboot=yes --noipv6 --device=bond0 --vlanid=1 --bootproto=st...

...nitrd.img ip=dhcp nameserver=xx.xx.xx.xx > ksdevice=eno1 inst.repo=http://our.mirror.server/7/os/x86_64 > inst.ks.sendmac inst.ks=http://our.kickstart.server/ks.cgi > > > and the network settings in the kickstart file are > > network --device bond0 --bondslaves=eno1,eno2 > --bondopts=mode=balance-alb --bootproto=dhcp --hostname=myhost --activate > > > I would have expected to get a bonding device with eno1 and eno2 as > slave devices, the bonding device inheriting the MAC address from eno1 > (otherwise DHCP won't work). Instead the result is a bonding device...