Leave out the "bond0" and you will be fine.  Cobbler puts the bonding opts in the interface config file instead of in the modprobe.conf

On Mon, Mar 23, 2009 at 8:59 AM, James Cammarata <jimi@sngx.net> wrote:

On Mon, 23 Mar 2009 12:54:20 +0000, Tom Brown <tom@ng23.net> wrote:
> Tom Brown wrote:
>>> Yes.  That box is used to specify bonding options in modprobe.conf
>>>
>>>
>>>
>
> i dont seem to quite be able to get this going - in the ks this is what
> is shown
>
> echo "# Cobbler generated non-physical interface" >
> /etc/sysconfig/network-scripts/cobbler/ifcfg-eth0
> echo "DEVICE=eth0" >> /etc/sysconfig/network-scripts/cobbler/ifcfg-eth0
> cat >> /etc/sysconfig/network-scripts/cobbler/ifcfg-eth0 << EOF
> BONDING_OPTS="bond0 mode=1 primary=eth0 arp_interval=60
> arp_ip_target=192.168.11.1"
> EOF
> echo "ONPARENT=yes" >> /etc/sysconfig/network-scripts/cobbler/ifcfg-eth0
> echo "BOOTPROTO=static" >>
> /etc/sysconfig/network-scripts/cobbler/ifcfg-eth0
> echo "IPADDR=192.168.11.4" >>
> /etc/sysconfig/network-scripts/cobbler/ifcfg-eth0
> echo "NETMASK=255.255.255.0" >>
> /etc/sysconfig/network-scripts/cobbler/ifcfg-eth0
> echo "DNS1=<<inherit>>" >>
> /etc/sysconfig/network-scripts/cobbler/ifcfg-eth0
> #  End configuration for eth0
>
> and
>
> echo "DEVICE=eth1" > /etc/sysconfig/network-scripts/cobbler/ifcfg-eth1
> echo "HWADDR=00:16:3E:5B:BB:05" >>
> /etc/sysconfig/network-scripts/cobbler/ifcfg-eth1
> echo "ONBOOT=yes" >> /etc/sysconfig/network-scripts/cobbler/ifcfg-eth1
> echo "SLAVE=yes" >> /etc/sysconfig/network-scripts/cobbler/ifcfg-eth1
> echo "MASTER=eth0" >> /etc/sysconfig/network-scripts/cobbler/ifcfg-eth1
> echo "HOTPLUG=no" >> /etc/sysconfig/network-scripts/cobbler/ifcfg-eth1
> echo "BOOTPROTO=none" >>
/etc/sysconfig/network-scripts/cobbler/ifcfg-eth1
> echo "DNS1=<<inherit>>" >>
> /etc/sysconfig/network-scripts/cobbler/ifcfg-eth1
> #  End configuration for eth1
>
> and modprobe.conf looks like
>
> options bonding max_bonds=1
> alias eth1 xennet
> alias eth0 bonding
>
> my system report for this machine is as follows
>
> # cobbler system report virt02
> system                : virt02
> profile               : CentOS-5.2-xen-x86_64
> comment               :
> created               : Thu Mar 12 11:00:37 2009
> gateway               : 192.168.11.1
> hostname              : virt02.linux.lab.xxxxxxxx.com
> image                 :
> kernel options        : {'ip': '192.168.11.4', 'netmask':
> '255.255.255.0', 'acpi': 'False', 'dns': '192.168.11.1', 'gateway':
> '192.168.11.1'}
> kernel options post   : {}
> kickstart             : <<inherit>>
> ks metadata           : {'nameserver': '192.168.11.1'}
> mgmt classes          : []
> modified              : Mon Mar 23 12:32:52 2009
> name servers          : ['<<inherit>>']
> name servers search   : ['<<inherit>>']
> netboot enabled?      : True
> owners                : ['admin']
> server                : <<inherit>>
> template files        : {}
> virt cpus             : <<inherit>>
> virt file size        : <<inherit>>
> virt path             : <<inherit>>
> virt ram              : <<inherit>>
> virt type             : <<inherit>>
> power type            : ipmitool
> power address         :
> power user            :
> power password        :
> power id              :
> interface        : eth0
>   mac address    : 00:16:3E:59:16:91
>   bonding        : master
>   bonding_master :
>   bonding_opts   : bond0 mode=1 primary=eth0 arp_interval=60
> arp_ip_target=192.168.11.1
>   is static?     : True
>   ip address     : 192.168.11.4
>   subnet         : 255.255.255.0
>   static routes  : []
>   dns name       : virt02.linux.lab.xxxxxxxx.com
>   dhcp tag       :
>   virt bridge    : xenbr0
> interface        : eth1
>   mac address    : 00:16:3e:5b:bb:05
>   bonding        : slave
>   bonding_master : eth0
>   bonding_opts   :
>   is static?     : True
>   ip address     :
>   subnet         :
>   static routes  : []
>   dns name       :
>   dhcp tag       :
>   virt bridge    : xenbr0
>
>
> am i missing something blindingly obvious ??
>
> thanks

I think that was my fault :/  It looks like the post network configuration
script puts the BONDING_OPTS variable in each interface, not in
modprobe.conf (that's where I assumed it went, as that's how I always
configure it on systems).

After building a system, you should be able to verify the settings it's
using by looking at /proc/net/bonding/bond#


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________



--
Adam Leach
BS Computer/Electrical Engineering
West Virginia University
Systems Administrator - Raytheon
(304)677-4455