<?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: Bonding versus MPIO explained</title>
	<atom:link href="http://blog.open-e.com/bonding-versus-mpio-explained/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.open-e.com/bonding-versus-mpio-explained/</link>
	<description>Open-E - Enterprise Class Storage OS For Every Business</description>
	<lastBuildDate>Mon, 07 May 2012 20:13:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: TooMeeK</title>
		<link>http://blog.open-e.com/bonding-versus-mpio-explained/#comment-31763</link>
		<dc:creator>TooMeeK</dc:creator>
		<pubDate>Mon, 04 Jul 2011 23:03:34 +0000</pubDate>
		<guid isPermaLink="false">https://blog.open-e.com/?p=483#comment-31763</guid>
		<description>eee... what? with good switch and bonding mode round-robin (just like iSCSI MCS does) You can get raw performance at twice of Gigabit link (or more) for NFS for example. Check this by iperf, should get 1,8-1,9Gbit/s even with single connection. It utilises all slaves.
But better solution is to always have redundand link (2 switches at least) and use different bonding mode (balance-alb) or many paths for iSCSI. This means seaparate IP for all network cards.</description>
		<content:encoded><![CDATA[<p>eee&#8230; what? with good switch and bonding mode round-robin (just like iSCSI MCS does) You can get raw performance at twice of Gigabit link (or more) for NFS for example. Check this by iperf, should get 1,8-1,9Gbit/s even with single connection. It utilises all slaves.<br />
But better solution is to always have redundand link (2 switches at least) and use different bonding mode (balance-alb) or many paths for iSCSI. This means seaparate IP for all network cards.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruno PELZER - CELEM</title>
		<link>http://blog.open-e.com/bonding-versus-mpio-explained/#comment-4783</link>
		<dc:creator>Bruno PELZER - CELEM</dc:creator>
		<pubDate>Wed, 16 Mar 2011 13:25:59 +0000</pubDate>
		<guid isPermaLink="false">https://blog.open-e.com/?p=483#comment-4783</guid>
		<description>If I use MPIO (3 gigabit NIC) and I use cluster Failover for my iSCSI connection, my gigabit replication link is the bottleneck and performances are about 100Mbps instead of 300 Mbps... If I disable cluster failover my performance is better (about 300Mbps). How can I get very good performances (300Mbps) WITH cluster Failover enabled ? I have a solution : using 10Gigabit ethernet link between 2 Open-E SAN (for replication link) but it&#039;s a very expensive solution... Do you have another idea ?</description>
		<content:encoded><![CDATA[<p>If I use MPIO (3 gigabit NIC) and I use cluster Failover for my iSCSI connection, my gigabit replication link is the bottleneck and performances are about 100Mbps instead of 300 Mbps&#8230; If I disable cluster failover my performance is better (about 300Mbps). How can I get very good performances (300Mbps) WITH cluster Failover enabled ? I have a solution : using 10Gigabit ethernet link between 2 Open-E SAN (for replication link) but it&#8217;s a very expensive solution&#8230; Do you have another idea ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dan pugh</title>
		<link>http://blog.open-e.com/bonding-versus-mpio-explained/#comment-4633</link>
		<dc:creator>dan pugh</dc:creator>
		<pubDate>Tue, 14 Dec 2010 21:57:45 +0000</pubDate>
		<guid isPermaLink="false">https://blog.open-e.com/?p=483#comment-4633</guid>
		<description>interesting, surely what you describe is different depending on circumstances
lacp bonds together 2 x 1gb links and (assuming it is switch assisted) using single virutal mac address so 1 flow can = 200
mpio can = 200 when 2 flows but otherwise hits maximum with 1 flow of 100
network load balancing (adaptor teaming) is maxed out like mpio at 1-in and 1-out so 100
although there are several options for loadbalancing overall throughput is not increased unless the switch helps

thats how i understood it anyway

http://en.wikipedia.org/wiki/Link_aggregation

&quot;Network interface cards (NICs) trunked together can also provide network links beyond the throughput of any one single NIC&quot;

microsoft doesnt support adaptor teaming isci, but you can bond using lacp at the storage end.


testing (lacp bonded iscsi with cisco switch in port-channel) ive just done seems to be slower with mpio, but the failover cluster validation seems happier with mpio

could be wrong of course ;-)</description>
		<content:encoded><![CDATA[<p>interesting, surely what you describe is different depending on circumstances<br />
lacp bonds together 2 x 1gb links and (assuming it is switch assisted) using single virutal mac address so 1 flow can = 200<br />
mpio can = 200 when 2 flows but otherwise hits maximum with 1 flow of 100<br />
network load balancing (adaptor teaming) is maxed out like mpio at 1-in and 1-out so 100<br />
although there are several options for loadbalancing overall throughput is not increased unless the switch helps</p>
<p>thats how i understood it anyway</p>
<p><a href="http://en.wikipedia.org/wiki/Link_aggregation" rel="nofollow">http://en.wikipedia.org/wiki/Link_aggregation</a></p>
<p>&#8220;Network interface cards (NICs) trunked together can also provide network links beyond the throughput of any one single NIC&#8221;</p>
<p>microsoft doesnt support adaptor teaming isci, but you can bond using lacp at the storage end.</p>
<p>testing (lacp bonded iscsi with cisco switch in port-channel) ive just done seems to be slower with mpio, but the failover cluster validation seems happier with mpio</p>
<p>could be wrong of course <img src='http://blog.open-e.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>

