Hi all, Someone played with kickstart bonding with centos 6.4 ? CentOS 6.4, as upstream now support ifcae bonding in kickstart network section. I've an issue with configuring a second bonding iface in kicstart on CentOS 6.4. The first bonding (bond0) works as espected but the second is not configured during installation. I've a 6 nic server (two for "puclic" network, two for cluster network, two for iscsi network) here is my "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,updelay=60000 # ISCSI network network --device=p1p3 --noipv6 --nodns --nodefroute --bootproto=static --onboot=yes --mtu=9000 --ip=192.168.3.1 --netmask=255.255.255.0 network --device=p1p4 --noipv6 --nodns --nodefroute --bootproto=static --onboot=yes --mtu=9000 --ip=192.168.3.2 --netmask=255.255.255.0 # bond slave network --device=em1 --noipv6 --nodns --bootproto=static --onboot=yes # bond slave network --device=em2 --noipv6 --nodns --bootproto=static --onboot=yes # bond slave network --device=p1p1 --noipv6 --nodns --bootproto=static --onboot=yes # bond slave network --device=p1p2 --noipv6 --nodns --bootproto=static --onboot=yes when i check anaconda-ks.cfg on the installed host, the second bonding iface (bond1) is not present. No error displayed during install or present in install log files on installed hosts. Maybe Have a nice day. Regards. Baptiste.
Hi all, Someone played with kickstart bonding with centos 6.4 ? CentOS 6.4, as upstream now support ifcae bonding in kickstart network section. I've an issue with configuring a second bonding iface in kicstart on CentOS 6.4. The first bonding (bond0) works as espected but the second is not configured during installation. I've a 6 nic server (two for "puclic" network, two for cluster network, two for iscsi network) here is my "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,updelay=60000 # ISCSI network network --device=p1p3 --noipv6 --nodns --nodefroute --bootproto=static --onboot=yes --mtu=9000 --ip=192.168.3.1 --netmask=255.255.255.0 network --device=p1p4 --noipv6 --nodns --nodefroute --bootproto=static --onboot=yes --mtu=9000 --ip=192.168.3.2 --netmask=255.255.255.0 # bond slave network --device=em1 --noipv6 --nodns --bootproto=static --onboot=yes # bond slave network --device=em2 --noipv6 --nodns --bootproto=static --onboot=yes # bond slave network --device=p1p1 --noipv6 --nodns --bootproto=static --onboot=yes # bond slave network --device=p1p2 --noipv6 --nodns --bootproto=static --onboot=yes when i check anaconda-ks.cfg on the installed host, the second bonding iface (bond1) is not present. No error displayed during install or present in install log files on installed hosts. Maybe Have a nice day. Regards. Baptiste.