<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: IP Bonding or Teaming in Linux &#8211; RHEL 5</title>
	<atom:link href="http://www.linuxmonk.org/2009/06/24/ip-bonding-or-teaming-in-linux-rhel-5/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.linuxmonk.org/2009/06/24/ip-bonding-or-teaming-in-linux-rhel-5/</link>
	<description>A Journey Towards Infinity...</description>
	<lastBuildDate>Sun, 17 Jul 2011 15:20:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Ahmed</title>
		<link>http://www.linuxmonk.org/2009/06/24/ip-bonding-or-teaming-in-linux-rhel-5/comment-page-1/#comment-7257</link>
		<dc:creator>Ahmed</dc:creator>
		<pubDate>Sun, 13 Mar 2011 10:03:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.linuxmonk.org/?p=282#comment-7257</guid>
		<description>]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.4.0 (October 7, 2008)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: eth2 (primary_reselect always)
Currently Active Slave: eth2
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
ARP Polling Interval (ms): 200
ARP IP target/s (n.n.n.n form):

Slave Interface: eth2
MII Status: up
Link Failure Count: 13087
Permanent HW addr: 68:b5:99:c5:dd:28

Slave Interface: eth3
MII Status: up
Link Failure Count: 1213
Permanent HW addr: 68:b5:99:c5:dd:2a</description>
		<content:encoded><![CDATA[<p>]# cat /proc/net/bonding/bond0<br />
Ethernet Channel Bonding Driver: v3.4.0 (October 7, 2008)</p>
<p>Bonding Mode: fault-tolerance (active-backup)<br />
Primary Slave: eth2 (primary_reselect always)<br />
Currently Active Slave: eth2<br />
MII Status: up<br />
MII Polling Interval (ms): 0<br />
Up Delay (ms): 0<br />
Down Delay (ms): 0<br />
ARP Polling Interval (ms): 200<br />
ARP IP target/s (n.n.n.n form):</p>
<p>Slave Interface: eth2<br />
MII Status: up<br />
Link Failure Count: 13087<br />
Permanent HW addr: 68:b5:99:c5:dd:28</p>
<p>Slave Interface: eth3<br />
MII Status: up<br />
Link Failure Count: 1213<br />
Permanent HW addr: 68:b5:99:c5:dd:2a</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ahmed</title>
		<link>http://www.linuxmonk.org/2009/06/24/ip-bonding-or-teaming-in-linux-rhel-5/comment-page-1/#comment-7256</link>
		<dc:creator>Ahmed</dc:creator>
		<pubDate>Sun, 13 Mar 2011 09:40:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.linuxmonk.org/?p=282#comment-7256</guid>
		<description>2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux

Red Hat Enterprise Linux Server release 5.5 (Tikanga)

I did not copy but I checked and hardware address is different.</description>
		<content:encoded><![CDATA[<p>2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux</p>
<p>Red Hat Enterprise Linux Server release 5.5 (Tikanga)</p>
<p>I did not copy but I checked and hardware address is different.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rosario</title>
		<link>http://www.linuxmonk.org/2009/06/24/ip-bonding-or-teaming-in-linux-rhel-5/comment-page-1/#comment-7255</link>
		<dc:creator>Rosario</dc:creator>
		<pubDate>Sun, 13 Mar 2011 08:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.linuxmonk.org/?p=282#comment-7255</guid>
		<description>@Ahmed, What version of redhat are you using?
1. Double check if the hardware addresses in the files ifcfg-eth1 and /ifcfg-eth0? Normally when copying people forget to change the hardware addresses.

2. Check the bug fix below
https://bugzilla.redhat.com/show_bug.cgi?id=483034

Hope it helps Let me know.</description>
		<content:encoded><![CDATA[<p>@Ahmed, What version of redhat are you using?<br />
1. Double check if the hardware addresses in the files ifcfg-eth1 and /ifcfg-eth0? Normally when copying people forget to change the hardware addresses.</p>
<p>2. Check the bug fix below<br />
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=483034" rel="nofollow">https://bugzilla.redhat.com/show_bug.cgi?id=483034</a></p>
<p>Hope it helps Let me know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ahmed</title>
		<link>http://www.linuxmonk.org/2009/06/24/ip-bonding-or-teaming-in-linux-rhel-5/comment-page-1/#comment-7252</link>
		<dc:creator>Ahmed</dc:creator>
		<pubDate>Sun, 13 Mar 2011 06:46:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.linuxmonk.org/?p=282#comment-7252</guid>
		<description>I keep on getting the following messages (in /var/log/messages) after bonding two interfaces. What could be the reason?

bonding: bond0: link status definitely down for interface eth2, disabling it
Mar 13 11:52:49 dr102 kernel: bonding: bond0: making interface eth3 the new active one.
Mar 13 11:52:49 dr102 kernel: bonding: bond0: link status definitely up for interface eth2.
Mar 13 11:52:49 dr102 kernel: bonding: bond0: making interface eth2 the new active one.
Mar 13 11:52:50 dr102 kernel: bonding: bond0: link status definitely down for interface eth2, disabling it
Mar 13 11:52:50 dr102 kernel: bonding: bond0: making interface eth3 the new active one.
Mar 13 11:52:50 dr102 kernel: bonding: bond0: link status definitely up for interface eth2.
Mar 13 11:52:50 dr102 kernel: bonding: bond0: making interface eth2 the new active one.
Mar 13 11:52:51 dr102 kernel: bonding: bond0: link status definitely down for interface eth2, disabling it
Mar 13 11:52:51 dr102 kernel: bonding: bond0: making interface eth3 the new active one.
Mar 13 11:52:51 dr102 kernel: bonding: bond0: link status definitely up for interface eth2.</description>
		<content:encoded><![CDATA[<p>I keep on getting the following messages (in /var/log/messages) after bonding two interfaces. What could be the reason?</p>
<p>bonding: bond0: link status definitely down for interface eth2, disabling it<br />
Mar 13 11:52:49 dr102 kernel: bonding: bond0: making interface eth3 the new active one.<br />
Mar 13 11:52:49 dr102 kernel: bonding: bond0: link status definitely up for interface eth2.<br />
Mar 13 11:52:49 dr102 kernel: bonding: bond0: making interface eth2 the new active one.<br />
Mar 13 11:52:50 dr102 kernel: bonding: bond0: link status definitely down for interface eth2, disabling it<br />
Mar 13 11:52:50 dr102 kernel: bonding: bond0: making interface eth3 the new active one.<br />
Mar 13 11:52:50 dr102 kernel: bonding: bond0: link status definitely up for interface eth2.<br />
Mar 13 11:52:50 dr102 kernel: bonding: bond0: making interface eth2 the new active one.<br />
Mar 13 11:52:51 dr102 kernel: bonding: bond0: link status definitely down for interface eth2, disabling it<br />
Mar 13 11:52:51 dr102 kernel: bonding: bond0: making interface eth3 the new active one.<br />
Mar 13 11:52:51 dr102 kernel: bonding: bond0: link status definitely up for interface eth2.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

