<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Multiple-Paths on sigtar.com</title>
		<link>https://sigtar.com/tags/multiple-paths/</link>
		<description>Recent content in Multiple-Paths on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Sat, 22 Aug 2009 00:00:00 +1200</lastBuildDate>
		
			<atom:link href="https://sigtar.com/tags/multiple-paths/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>ESX - network utilization</title>
				<link>https://sigtar.com/2009/08/22/esx-network-utilization/</link>
				<pubDate>Sat, 22 Aug 2009 00:00:00 +1200</pubDate>
				<guid>https://sigtar.com/2009/08/22/esx-network-utilization/</guid>
				<description>&lt;p&gt;One of the best articles i have found on this subject is here : &lt;a href=&#34;http://blog.scottlowe.org/2008/07/16/understanding-nic-utilization-in-vmware-esx/&#34;&gt;http://blog.scottlowe.org/2008/07/16/understanding-nic-utilization-in-vmware-esx/&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;There is some additional information here on setting up an etherchannel on the cisco side : &lt;a href=&#34;http://blog.scottlowe.org/2006/12/04/esx-server-nic-teaming-and-vlan-trunking/&#34;&gt;http://blog.scottlowe.org/2006/12/04/esx-server-nic-teaming-and-vlan-trunking/&lt;/a&gt;&lt;/p&gt;&#xA;&lt;p&gt;This can be handy if you need a single VM to use both physical nics in a load-balanced manner - both outbound and &lt;strong&gt;inbound&lt;/strong&gt;. Of course its not really that simple though. This will really only add a benefit if the VM is communicating to &lt;em&gt;multiple&lt;/em&gt; destinations (using ip hash - a single destination from a single VM with one IP will always be limited to the same physical nic).&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
