<?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: NIC Teaming Update: Hyper-V Still Cloudy as Ever</title>
	<atom:link href="http://www.vcritical.com/2011/05/nic-teaming-update-hyper-v-still-cloudy-as-ever/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.vcritical.com/2011/05/nic-teaming-update-hyper-v-still-cloudy-as-ever/</link>
	<description>Informed Virtualization Criticism</description>
	<lastBuildDate>Fri, 07 Jun 2013 16:44:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Mark</title>
		<link>http://www.vcritical.com/2011/05/nic-teaming-update-hyper-v-still-cloudy-as-ever/#comment-12394</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Wed, 31 Aug 2011 19:50:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=3606#comment-12394</guid>
		<description><![CDATA[We have been seeing issues that randomly a VM will stop responding, either the router can&#039;t find it or it just isn&#039;t answering.  Sometimes it comes back and sometimes we have to move it to a different Hyper V server.  Our setup is Dell, Hyper V, Windows 2008, Broadcom going to Nexus 2248&#039;s.  Any ideas why we would randomly have VM&#039;s stop responding?  And it isn&#039;t all the VM&#039;s on the chassis usually just 1 of up to 40 VM&#039;s that are on a chassis.

Thanks]]></description>
		<content:encoded><![CDATA[<p>We have been seeing issues that randomly a VM will stop responding, either the router can&#8217;t find it or it just isn&#8217;t answering.  Sometimes it comes back and sometimes we have to move it to a different Hyper V server.  Our setup is Dell, Hyper V, Windows 2008, Broadcom going to Nexus 2248&#8242;s.  Any ideas why we would randomly have VM&#8217;s stop responding?  And it isn&#8217;t all the VM&#8217;s on the chassis usually just 1 of up to 40 VM&#8217;s that are on a chassis.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://www.vcritical.com/2011/05/nic-teaming-update-hyper-v-still-cloudy-as-ever/#comment-12052</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Sat, 09 Jul 2011 02:45:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=3606#comment-12052</guid>
		<description><![CDATA[Gartner now concludes that Hyper-V is well on its way - quite a jump from the article posted:

http://www.gartner.com/technology/media-products/reprints/microsoft/vol2/article8a/article8a.html]]></description>
		<content:encoded><![CDATA[<p>Gartner now concludes that Hyper-V is well on its way &#8211; quite a jump from the article posted:</p>
<p><a href="http://www.gartner.com/technology/media-products/reprints/microsoft/vol2/article8a/article8a.html" rel="nofollow">http://www.gartner.com/technology/media-products/reprints/microsoft/vol2/article8a/article8a.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry</title>
		<link>http://www.vcritical.com/2011/05/nic-teaming-update-hyper-v-still-cloudy-as-ever/#comment-11959</link>
		<dc:creator>Larry</dc:creator>
		<pubDate>Wed, 08 Jun 2011 05:54:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=3606#comment-11959</guid>
		<description><![CDATA[Teaming works fine with Hyper V.  Dont think of it as Hyper V teaming its Windows OS teaming really.

Long before Hyper V teaming of Nics on Windows servers has been working fine.  I am talking Windows 2000 server on Compaq hardware back in the day, wit 2 or more 100meg NIC&#039;s.

I use Broadcom 10gig NIC&#039;s and use their BACS software to set it up before I even add the Hyper V role.  That softare allows you to chop up a LACP Team of 10gig ports (2 or more) into various virtual ports.

Windows and Hyper V thinks its physical NIC&#039;s, say 4 as an example.  Then use them how you want, managment, live migration, virtuaul switch for VM&#039;s etc.  Setup right with dual switches, say Nexus, with LACP VPC&#039;s you can get 20gig going full rate if need be.

Any Windows admin worth anything can setup NIC teaming.  Dell, HP and IBM provide good documentation and support for this....regardless of Hyper V.  NIC teaming happens all the time outside of Hyper V, say on a SQL server that wants NIC redundency and throuput.]]></description>
		<content:encoded><![CDATA[<p>Teaming works fine with Hyper V.  Dont think of it as Hyper V teaming its Windows OS teaming really.</p>
<p>Long before Hyper V teaming of Nics on Windows servers has been working fine.  I am talking Windows 2000 server on Compaq hardware back in the day, wit 2 or more 100meg NIC&#8217;s.</p>
<p>I use Broadcom 10gig NIC&#8217;s and use their BACS software to set it up before I even add the Hyper V role.  That softare allows you to chop up a LACP Team of 10gig ports (2 or more) into various virtual ports.</p>
<p>Windows and Hyper V thinks its physical NIC&#8217;s, say 4 as an example.  Then use them how you want, managment, live migration, virtuaul switch for VM&#8217;s etc.  Setup right with dual switches, say Nexus, with LACP VPC&#8217;s you can get 20gig going full rate if need be.</p>
<p>Any Windows admin worth anything can setup NIC teaming.  Dell, HP and IBM provide good documentation and support for this&#8230;.regardless of Hyper V.  NIC teaming happens all the time outside of Hyper V, say on a SQL server that wants NIC redundency and throuput.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://www.vcritical.com/2011/05/nic-teaming-update-hyper-v-still-cloudy-as-ever/#comment-11889</link>
		<dc:creator>John</dc:creator>
		<pubDate>Fri, 27 May 2011 21:09:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.vcritical.com/?p=3606#comment-11889</guid>
		<description><![CDATA[I have been teaming NIC&#039;s in Hyper-v for years. It has not been an issue. If you are talking about teaming them inside the guest, no I don&#039;t think that will work, but what would that accomplish anyway, if the underlying NIC(s) are teamed.]]></description>
		<content:encoded><![CDATA[<p>I have been teaming NIC&#8217;s in Hyper-v for years. It has not been an issue. If you are talking about teaming them inside the guest, no I don&#8217;t think that will work, but what would that accomplish anyway, if the underlying NIC(s) are teamed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
