<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: [DL380 G5] Problem with multiple bonds on Red Hat ES 4 64bit in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/dl380-g5-problem-with-multiple-bonds-on-red-hat-es-4-64bit/m-p/4420261#M82088</link>
    <description>I managed with this problem by setting all options manually by sysfs. I wrote a script and put it in the network init script. Anything else didn't work.&lt;BR /&gt;&lt;BR /&gt;I'm curious if anyone else experienced problems with multiple bonds on red hat es 4 u5 64bit.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Tomasz</description>
    <pubDate>Fri, 15 May 2009 20:40:34 GMT</pubDate>
    <dc:creator>Tomasz Czlapski</dc:creator>
    <dc:date>2009-05-15T20:40:34Z</dc:date>
    <item>
      <title>[DL380 G5] Problem with multiple bonds on Red Hat ES 4 64bit</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl380-g5-problem-with-multiple-bonds-on-red-hat-es-4-64bit/m-p/4420257#M82084</link>
      <description>Hi, I have problem with configuration bonding on red hat enterprise 4 update 5 64bit. &lt;BR /&gt;I have kernel buit from sources (trying 2.6.29.3 and 2.6.28.9) and cannot configure two bonding interfaces with different options.&lt;BR /&gt;I think the problem is that I can't load bonding module two times (even using different names). The same is happening on stock red hat kernel 2.6.9-55.Elsmp&lt;BR /&gt;&lt;BR /&gt;When I'm trying to load manually bonding for second time I get:&lt;BR /&gt;kernel: Oops: 0002 [#1] SMP&lt;BR /&gt;kernel: last sysfs file: /sys/class/vc/vcsa6/dev&lt;BR /&gt;&lt;BR /&gt;When I'm trying load bonding modules with sysconfig, after reboot I have in var/log/messages:&lt;BR /&gt;ifup: /sbin/modprobe device bond1 does not seem to be present, delaying initialization.&lt;BR /&gt;hal.hotplug[3649]: timout(10000 ms) waiting for /class/net/bond1&lt;BR /&gt;network: Bringing up interface bond1:  failed&lt;BR /&gt;kernel: bonding: ARP monitoring set to 1000 ms, validate none, with 1 target(s): X.X.X.X&lt;BR /&gt;kernel: bonding: ARP monitoring set to 1000 ms, validate none, with 1 target(s): Y.Y.Y.Y&lt;BR /&gt;kernel: sysfs: duplicate filename 'bonding_masters' can not be created&lt;BR /&gt;kernel: Modules linked in: bond1(+) bonding cciss&lt;BR /&gt;kernel:  [&lt;FFFFFFFFA0037A4D&gt;] bond_create_sysfs+0xd/0x50 [bond1]&lt;BR /&gt;kernel:  [&lt;FFFFFFFFA0044349&gt;] bonding_init+0x349/0x95a [bond1]&lt;BR /&gt;kernel:  [&lt;FFFFFFFFA0044000&gt;] bonding_init+0x0/0x95a [bond1]&lt;BR /&gt;kernel: Modules linked in: bond1(+) bonding cciss&lt;BR /&gt;LOK1WWW2 kernel:  [&lt;FFFFFFFFA002BCA7&gt;] ? bond_destructor+0x67/0x70 [bond1]&lt;BR /&gt;kernel:  [&lt;FFFFFFFFA00443AF&gt;] ? bonding_init+0x3af/0x95a [bond1]&lt;BR /&gt;kernel:  [&lt;FFFFFFFFA0044000&gt;] ? bonding_init+0x0/0x95a [bond1]&lt;BR /&gt;&lt;BR /&gt;And only first bond is working.&lt;BR /&gt;Here is my modprobe.conf (only part about bonding):&lt;BR /&gt;alias bond0 bonding&lt;BR /&gt;options bond0 mode=1 arp_interval=1000 arp_ip_target=X.X.X.X&lt;BR /&gt;install bond1 /sbin/modprobe --ignore-install bonding -o bond1 mode=1 arp_interval=1000 arp_ip_target=Y.Y.Y.Y&lt;BR /&gt;&lt;BR /&gt;ifcfg-X files are standard taken from documentation without any BONDING_OPTS so I don't think it's necessary to put it here.&lt;BR /&gt;&lt;BR /&gt;Oh, and my kernel is 2.6.28.9 SMP x86_64&lt;BR /&gt;&lt;BR /&gt;I will be grateful for any advices?&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Tomasz&lt;/FFFFFFFFA0044000&gt;&lt;/FFFFFFFFA00443AF&gt;&lt;/FFFFFFFFA002BCA7&gt;&lt;/FFFFFFFFA0044000&gt;&lt;/FFFFFFFFA0044349&gt;&lt;/FFFFFFFFA0037A4D&gt;</description>
      <pubDate>Thu, 14 May 2009 14:34:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl380-g5-problem-with-multiple-bonds-on-red-hat-es-4-64bit/m-p/4420257#M82084</guid>
      <dc:creator>Tomasz Czlapski</dc:creator>
      <dc:date>2009-05-14T14:34:57Z</dc:date>
    </item>
    <item>
      <title>Re: [DL380 G5] Problem with multiple bonds on Red Hat ES 4 64bit</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl380-g5-problem-with-multiple-bonds-on-red-hat-es-4-64bit/m-p/4420258#M82085</link>
      <description>a little addition, there should be:&lt;BR /&gt;alias bond1 bonding in a line before - instal...&lt;BR /&gt;the modprobe like this up generate : "device bond1 not seem to be present"&lt;BR /&gt;&lt;BR /&gt;If I add max_bonds=2 in the second line then bond1 is up but with the settings from bond0.&lt;BR /&gt;&lt;BR /&gt;Why bonding module can't be loaded twice? :(&lt;BR /&gt;&lt;BR /&gt;When I try this:&lt;BR /&gt;alias bond0 bonding&lt;BR /&gt;options bond0 -o bond0 mode=1 arp_interval=1000 arp_ip_target=X.X.X.X&lt;BR /&gt;alias bond1 bonding&lt;BR /&gt;options bond1 mode=1 arp_interval=1000 arp_ip_target=Y.Y.Y.Y primary=eth3 max_bonds=2&lt;BR /&gt;&lt;BR /&gt;I get unknown parameter for bond0. When I without -o then I get that bond1 is not present.&lt;BR /&gt;&lt;BR /&gt;I'm confused about all this bonding issue.</description>
      <pubDate>Thu, 14 May 2009 16:18:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl380-g5-problem-with-multiple-bonds-on-red-hat-es-4-64bit/m-p/4420258#M82085</guid>
      <dc:creator>Tomasz Czlapski</dc:creator>
      <dc:date>2009-05-14T16:18:58Z</dc:date>
    </item>
    <item>
      <title>Re: [DL380 G5] Problem with multiple bonds on Red Hat ES 4 64bit</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl380-g5-problem-with-multiple-bonds-on-red-hat-es-4-64bit/m-p/4420259#M82086</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;I suggest a simpler configuration.&lt;BR /&gt;&lt;BR /&gt;Get the IP information out of modprobe.conf and put it where it belongs in /etc/sysconfig/network-scripts/ifcfg-bond0&lt;BR /&gt;&lt;BR /&gt;Why can't you load the module twice? Because it was designed to be loaded once.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Fri, 15 May 2009 02:06:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl380-g5-problem-with-multiple-bonds-on-red-hat-es-4-64bit/m-p/4420259#M82086</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-05-15T02:06:36Z</dc:date>
    </item>
    <item>
      <title>Re: [DL380 G5] Problem with multiple bonds on Red Hat ES 4 64bit</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl380-g5-problem-with-multiple-bonds-on-red-hat-es-4-64bit/m-p/4420260#M82087</link>
      <description>Hi, &lt;BR /&gt;&lt;BR /&gt;I think my version of init scripts doesn't support BONDING_OPTS in ifcfg-bondX files. I already tried that.&lt;BR /&gt;According to bonding.txt in kernel docs there should be a way to load bonding module two times, but with different names (with -o paramater).&lt;BR /&gt;&lt;BR /&gt;Just for sure I'll try again with BONDING_OPTS.&lt;BR /&gt;Another thing that I forgot to mention is that bonds doesn't enslaves eth interfaces automatically during boot. I needed to put ifenslave commands in rc.local script.</description>
      <pubDate>Fri, 15 May 2009 05:58:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl380-g5-problem-with-multiple-bonds-on-red-hat-es-4-64bit/m-p/4420260#M82087</guid>
      <dc:creator>Tomasz Czlapski</dc:creator>
      <dc:date>2009-05-15T05:58:28Z</dc:date>
    </item>
    <item>
      <title>Re: [DL380 G5] Problem with multiple bonds on Red Hat ES 4 64bit</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl380-g5-problem-with-multiple-bonds-on-red-hat-es-4-64bit/m-p/4420261#M82088</link>
      <description>I managed with this problem by setting all options manually by sysfs. I wrote a script and put it in the network init script. Anything else didn't work.&lt;BR /&gt;&lt;BR /&gt;I'm curious if anyone else experienced problems with multiple bonds on red hat es 4 u5 64bit.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Tomasz</description>
      <pubDate>Fri, 15 May 2009 20:40:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl380-g5-problem-with-multiple-bonds-on-red-hat-es-4-64bit/m-p/4420261#M82088</guid>
      <dc:creator>Tomasz Czlapski</dc:creator>
      <dc:date>2009-05-15T20:40:34Z</dc:date>
    </item>
    <item>
      <title>Re: [DL380 G5] Problem with multiple bonds on Red Hat ES 4 64bit</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl380-g5-problem-with-multiple-bonds-on-red-hat-es-4-64bit/m-p/4420262#M82089</link>
      <description>hello,&lt;BR /&gt;&lt;BR /&gt;shouldn't option max_bonds=2 be put twice ?&lt;BR /&gt;&lt;BR /&gt;Jean-Yves</description>
      <pubDate>Tue, 19 May 2009 06:22:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl380-g5-problem-with-multiple-bonds-on-red-hat-es-4-64bit/m-p/4420262#M82089</guid>
      <dc:creator>Jean-Yves Picard</dc:creator>
      <dc:date>2009-05-19T06:22:40Z</dc:date>
    </item>
    <item>
      <title>Re: [DL380 G5] Problem with multiple bonds on Red Hat ES 4 64bit</title>
      <link>https://community.hpe.com/t5/operating-system-linux/dl380-g5-problem-with-multiple-bonds-on-red-hat-es-4-64bit/m-p/4420263#M82090</link>
      <description>Hi, I don't think so. The max_bonds option should be used when you want multiple bonds with the same settings as the first one. So if I put max_bonds=2 then bond0 and bond1 will have exactly the same options enabled.&lt;BR /&gt;But like I wrote earlier I did a little workaround to made it work.</description>
      <pubDate>Tue, 19 May 2009 06:28:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/dl380-g5-problem-with-multiple-bonds-on-red-hat-es-4-64bit/m-p/4420263#M82090</guid>
      <dc:creator>Tomasz Czlapski</dc:creator>
      <dc:date>2009-05-19T06:28:38Z</dc:date>
    </item>
  </channel>
</rss>

