<?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: Bonding RED HAT ENTERPRISE LINUX 5.2 in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/bonding-red-hat-enterprise-linux-5-2/m-p/4444696#M82215</link>
    <description>I've only played with the bonding driver a little under Integrity Linux, but enough to be confident that the underlying system hardware is a don't care to the bonding driver.  There is probably just some minor config file issue somewhere.&lt;BR /&gt;&lt;BR /&gt;I would suggest trying the plain command-line stuff - iirc ifenslave - and then commandline ifconfig commands and see what comes of that and then work-out what the config files should say.  Pity RHEL5.2 doesn't have some sysadmin tool to do that automagically - or does it?&lt;BR /&gt;&lt;BR /&gt;However...  a hub implies 10/100 speeds only, and not GbE.  And the core interfaces on an rx3600 are GbE links, which suggests that if the goal is to see higher outbound throughput it would be "better" to simply replace the hub with a proper GbE switch (see &lt;A href="http://www.hp.com/go/procurve" target="_blank"&gt;http://www.hp.com/go/procurve&lt;/A&gt; for a slew of choices, among others) and not worry about bonding.</description>
    <pubDate>Tue, 23 Jun 2009 15:54:17 GMT</pubDate>
    <dc:creator>rick jones</dc:creator>
    <dc:date>2009-06-23T15:54:17Z</dc:date>
    <item>
      <title>Bonding RED HAT ENTERPRISE LINUX 5.2</title>
      <link>https://community.hpe.com/t5/operating-system-linux/bonding-red-hat-enterprise-linux-5-2/m-p/4444691#M82210</link>
      <description>Hi &lt;BR /&gt;I am trying to configure a bond0 of two network card on  a integrity machine rx3600 running red hat enterprise linux 5.2.&lt;BR /&gt;&lt;BR /&gt;I have follow this procedure &lt;BR /&gt;# vi /etc/sysconfig/network-scripts/ifcfg-bond0 Append following lines to DEVICE=bond0&lt;BR /&gt;BOOTPROTO=static&lt;BR /&gt;ONBOOT=yes&lt;BR /&gt;IPADDR=10.1.1.145&lt;BR /&gt;NETMASK=255.255.255.0&lt;BR /&gt;GATEWAY=10.1.5.1&lt;BR /&gt;USERCTL=no&lt;BR /&gt;&lt;BR /&gt;TASK 2: Modify eth0 and eth1 config files:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;[root@linuxhost network-scripts]# more ifcfg-eth0&lt;BR /&gt;DEVICE=eth0&lt;BR /&gt;ONBOOT=no&lt;BR /&gt;MASTER=bond0&lt;BR /&gt;SLAVE=yes&lt;BR /&gt;USERCTL=no&lt;BR /&gt;[root@linuxhost network-scripts]# more ifcfg-eth1&lt;BR /&gt;DEVICE=eth1&lt;BR /&gt;ONBOOT=no&lt;BR /&gt;MASTER=bond0&lt;BR /&gt;SLAVE=yes&lt;BR /&gt;USERCTL=no&lt;BR /&gt;&lt;BR /&gt;TASK 3: Load driver module:&lt;BR /&gt;&lt;BR /&gt;I have modify the kernel modules configuration file so that it looks like the one below.&lt;BR /&gt;&lt;BR /&gt;[root@linuxhost network-scripts]# more /etc/modprobe.conf&lt;BR /&gt;alias bond0 bonding&lt;BR /&gt;options bond0 mode=balance-alb miimon=100&lt;BR /&gt;&lt;BR /&gt;TASK 4: Test configuration by modprobe and service network restart commands.&lt;BR /&gt;&lt;BR /&gt;[root@linuxhost network-scripts]# modprobe bonding&lt;BR /&gt;[root@linuxhost network-scripts]# service network restart&lt;BR /&gt;&lt;BR /&gt;But when the network service is restarted the bond0 never come up.&lt;BR /&gt;&lt;BR /&gt;Question &lt;BR /&gt;Some special switch is required?&lt;BR /&gt;I am using a hub for test.&lt;BR /&gt;Regards &lt;BR /&gt;&lt;BR /&gt;W.S&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Jun 2009 20:53:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/bonding-red-hat-enterprise-linux-5-2/m-p/4444691#M82210</guid>
      <dc:creator>WilliamSmith11</dc:creator>
      <dc:date>2009-06-22T20:53:55Z</dc:date>
    </item>
    <item>
      <title>Re: Bonding RED HAT ENTERPRISE LINUX 5.2</title>
      <link>https://community.hpe.com/t5/operating-system-linux/bonding-red-hat-enterprise-linux-5-2/m-p/4444692#M82211</link>
      <description>In my configuration I have:&lt;BR /&gt;&lt;BR /&gt;ONBOOT=yes&lt;BR /&gt;&lt;BR /&gt;For the physical interfaces and it's working.&lt;BR /&gt;&lt;BR /&gt;My modprobe.conf:&lt;BR /&gt;&lt;BR /&gt;alias bond0 bonding&lt;BR /&gt;options bond0 mode=1 miimon=100 max_bonds=2 primary=eth0&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Jun 2009 21:34:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/bonding-red-hat-enterprise-linux-5-2/m-p/4444692#M82211</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2009-06-22T21:34:36Z</dc:date>
    </item>
    <item>
      <title>Re: Bonding RED HAT ENTERPRISE LINUX 5.2</title>
      <link>https://community.hpe.com/t5/operating-system-linux/bonding-red-hat-enterprise-linux-5-2/m-p/4444693#M82212</link>
      <description>No special switches requirement are mandatory ?&lt;BR /&gt;&lt;BR /&gt;I was trying with a Hub, so I think that is the reason cause was not working , &lt;BR /&gt;&lt;BR /&gt;I will modified the modprobe.conf file too.&lt;BR /&gt;&lt;BR /&gt;Some other ideas are wellcome, some ideas about when the network service are restarted the bond0 does not come up?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;W.S</description>
      <pubDate>Tue, 23 Jun 2009 00:08:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/bonding-red-hat-enterprise-linux-5-2/m-p/4444693#M82212</guid>
      <dc:creator>WilliamSmith11</dc:creator>
      <dc:date>2009-06-23T00:08:33Z</dc:date>
    </item>
    <item>
      <title>Re: Bonding RED HAT ENTERPRISE LINUX 5.2</title>
      <link>https://community.hpe.com/t5/operating-system-linux/bonding-red-hat-enterprise-linux-5-2/m-p/4444694#M82213</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;more info :&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.howtoforge.com/network_card_bonding_centos" target="_blank"&gt;http://www.howtoforge.com/network_card_bonding_centos&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;mikap</description>
      <pubDate>Tue, 23 Jun 2009 10:03:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/bonding-red-hat-enterprise-linux-5-2/m-p/4444694#M82213</guid>
      <dc:creator>Michal Kapalka (mikap)</dc:creator>
      <dc:date>2009-06-23T10:03:00Z</dc:date>
    </item>
    <item>
      <title>Re: Bonding RED HAT ENTERPRISE LINUX 5.2</title>
      <link>https://community.hpe.com/t5/operating-system-linux/bonding-red-hat-enterprise-linux-5-2/m-p/4444695#M82214</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Hub does not impact this. I've bonded RHEL 5.x systems on a hub.&lt;BR /&gt;&lt;BR /&gt;What does /var/log/messages say when the service network restart command is issued?&lt;BR /&gt;&lt;BR /&gt;Can you attempt a reboot?&lt;BR /&gt;&lt;BR /&gt;This may have something to do with the rx system hardware being a little special.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 23 Jun 2009 14:13:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/bonding-red-hat-enterprise-linux-5-2/m-p/4444695#M82214</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-06-23T14:13:13Z</dc:date>
    </item>
    <item>
      <title>Re: Bonding RED HAT ENTERPRISE LINUX 5.2</title>
      <link>https://community.hpe.com/t5/operating-system-linux/bonding-red-hat-enterprise-linux-5-2/m-p/4444696#M82215</link>
      <description>I've only played with the bonding driver a little under Integrity Linux, but enough to be confident that the underlying system hardware is a don't care to the bonding driver.  There is probably just some minor config file issue somewhere.&lt;BR /&gt;&lt;BR /&gt;I would suggest trying the plain command-line stuff - iirc ifenslave - and then commandline ifconfig commands and see what comes of that and then work-out what the config files should say.  Pity RHEL5.2 doesn't have some sysadmin tool to do that automagically - or does it?&lt;BR /&gt;&lt;BR /&gt;However...  a hub implies 10/100 speeds only, and not GbE.  And the core interfaces on an rx3600 are GbE links, which suggests that if the goal is to see higher outbound throughput it would be "better" to simply replace the hub with a proper GbE switch (see &lt;A href="http://www.hp.com/go/procurve" target="_blank"&gt;http://www.hp.com/go/procurve&lt;/A&gt; for a slew of choices, among others) and not worry about bonding.</description>
      <pubDate>Tue, 23 Jun 2009 15:54:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/bonding-red-hat-enterprise-linux-5-2/m-p/4444696#M82215</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2009-06-23T15:54:17Z</dc:date>
    </item>
    <item>
      <title>Re: Bonding RED HAT ENTERPRISE LINUX 5.2</title>
      <link>https://community.hpe.com/t5/operating-system-linux/bonding-red-hat-enterprise-linux-5-2/m-p/4444697#M82216</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;The option entries in modprobe.conf file don't seem to work in RHEL 5.2. I had to move the options to ifcfg-bond0 file and it worked for me. Example:&lt;BR /&gt;BONDING_OPTS='miimon=100 mode=1 primary=eth0'&lt;BR /&gt;&lt;BR /&gt;Beside setting ONBOOT=yes in ifcfg-eth0 and ifcfg-eth1, you might want to hard-code their respective MAC addresses in the file.&lt;BR /&gt;&lt;BR /&gt;Cheers</description>
      <pubDate>Mon, 20 Jul 2009 13:04:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/bonding-red-hat-enterprise-linux-5-2/m-p/4444697#M82216</guid>
      <dc:creator>loco_vikide</dc:creator>
      <dc:date>2009-07-20T13:04:32Z</dc:date>
    </item>
  </channel>
</rss>

