<?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: Using VMware ESX Virtual Switch Tagging with HP Virtual Connect</title>
	<atom:link href="http://blog.scottlowe.org/2009/07/06/using-vmware-esx-virtual-switch-tagging-with-hp-virtual-connect/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scottlowe.org/2009/07/06/using-vmware-esx-virtual-switch-tagging-with-hp-virtual-connect/</link>
	<description>The weblog of an IT pro specializing in virtualization, storage, and servers</description>
	<lastBuildDate>Wed, 08 Feb 2012 17:13:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2009/07/06/using-vmware-esx-virtual-switch-tagging-with-hp-virtual-connect/comment-page-1/#comment-50194</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Thu, 03 Feb 2011 01:27:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1446#comment-50194</guid>
		<description>Ken, thanks for jumping on here and helping out some of these readers. Will this vCenter plugin help them resolve their ARP issues?

(BTW, for those that don&#039;t know, Ken---aka @bladeguy on Twitter---works for HP and is a great resource for these sorts of questions.)</description>
		<content:encoded><![CDATA[<p>Ken, thanks for jumping on here and helping out some of these readers. Will this vCenter plugin help them resolve their ARP issues?</p>
<p>(BTW, for those that don&#8217;t know, Ken&#8212;aka @bladeguy on Twitter&#8212;works for HP and is a great resource for these sorts of questions.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Henault</title>
		<link>http://blog.scottlowe.org/2009/07/06/using-vmware-esx-virtual-switch-tagging-with-hp-virtual-connect/comment-page-1/#comment-50192</link>
		<dc:creator>Ken Henault</dc:creator>
		<pubDate>Wed, 02 Feb 2011 21:41:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1446#comment-50192</guid>
		<description>RT,

Try using the Virtual Connect plug-in for Virtual Center.  It is available at http://h18004.www1.hp.com/products/servers/management/integration.html  This will give you a graphical end-to-end view of your network connectivity:  vNIC -&gt; vSwitch -&gt; Virtual Connect -&gt; upstream switch.

This will help you confirm that you have the network set up the way you think you do.

Some additional resources:

HP/VMware home page
http://www.hp.com/go/vmware 

Virtual Connect Ethernet Cookbook
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01990371/c01990371.pdf
               I often use Scenario 2:3 for ESX implementations

Let me know if this helps.

Ken</description>
		<content:encoded><![CDATA[<p>RT,</p>
<p>Try using the Virtual Connect plug-in for Virtual Center.  It is available at <a href="http://h18004.www1.hp.com/products/servers/management/integration.html" rel="nofollow">http://h18004.www1.hp.com/products/servers/management/integration.html</a>  This will give you a graphical end-to-end view of your network connectivity:  vNIC -&gt; vSwitch -&gt; Virtual Connect -&gt; upstream switch.</p>
<p>This will help you confirm that you have the network set up the way you think you do.</p>
<p>Some additional resources:</p>
<p>HP/VMware home page<br />
<a href="http://www.hp.com/go/vmware" rel="nofollow">http://www.hp.com/go/vmware</a> </p>
<p>Virtual Connect Ethernet Cookbook<br />
<a href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01990371/c01990371.pdf" rel="nofollow">http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01990371/c01990371.pdf</a><br />
               I often use Scenario 2:3 for ESX implementations</p>
<p>Let me know if this helps.</p>
<p>Ken</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2009/07/06/using-vmware-esx-virtual-switch-tagging-with-hp-virtual-connect/comment-page-1/#comment-50188</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Wed, 02 Feb 2011 15:43:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1446#comment-50188</guid>
		<description>All, I don&#039;t have any additional information on this, but let me see if I can find an HP resource who might be able to help.</description>
		<content:encoded><![CDATA[<p>All, I don&#8217;t have any additional information on this, but let me see if I can find an HP resource who might be able to help.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rt</title>
		<link>http://blog.scottlowe.org/2009/07/06/using-vmware-esx-virtual-switch-tagging-with-hp-virtual-connect/comment-page-1/#comment-50180</link>
		<dc:creator>rt</dc:creator>
		<pubDate>Wed, 02 Feb 2011 00:14:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1446#comment-50180</guid>
		<description>same issue as chuck, diego, jon, daniel any resolution to this?</description>
		<content:encoded><![CDATA[<p>same issue as chuck, diego, jon, daniel any resolution to this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://blog.scottlowe.org/2009/07/06/using-vmware-esx-virtual-switch-tagging-with-hp-virtual-connect/comment-page-1/#comment-48910</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Tue, 03 Aug 2010 20:04:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1446#comment-48910</guid>
		<description>I&#039;m actually having this bizarre problem as Chuck, Diego and Jon.  Has anyone had any luck with this?  Maybe even where the problem lies (HP VC, switch or esx/vm)?</description>
		<content:encoded><![CDATA[<p>I&#8217;m actually having this bizarre problem as Chuck, Diego and Jon.  Has anyone had any luck with this?  Maybe even where the problem lies (HP VC, switch or esx/vm)?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://blog.scottlowe.org/2009/07/06/using-vmware-esx-virtual-switch-tagging-with-hp-virtual-connect/comment-page-1/#comment-47520</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Fri, 19 Feb 2010 13:48:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1446#comment-47520</guid>
		<description>Hello Chuck, and Diego.  We are having the same problem have you been able to resolve the issue.  We have been working with HP, Cisco, and VmWare and no one seems to be able to find out what is happening.</description>
		<content:encoded><![CDATA[<p>Hello Chuck, and Diego.  We are having the same problem have you been able to resolve the issue.  We have been working with HP, Cisco, and VmWare and no one seems to be able to find out what is happening.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vote Early (But Don&#8217;t Vote Often) - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers</title>
		<link>http://blog.scottlowe.org/2009/07/06/using-vmware-esx-virtual-switch-tagging-with-hp-virtual-connect/comment-page-1/#comment-47228</link>
		<dc:creator>Vote Early (But Don&#8217;t Vote Often) - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers</dc:creator>
		<pubDate>Tue, 05 Jan 2010 03:35:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1446#comment-47228</guid>
		<description>[...] VMware ESX Networking via CLI Introduction to Nehalem Memory (by guest author Aaron Delp) Using VMware ESX Virtual Switch Tagging with HP Virtual Connect Another Reason Not to Use PVSCSI or [...]</description>
		<content:encoded><![CDATA[<p>[...] VMware ESX Networking via CLI Introduction to Nehalem Memory (by guest author Aaron Delp) Using VMware ESX Virtual Switch Tagging with HP Virtual Connect Another Reason Not to Use PVSCSI or [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diego</title>
		<link>http://blog.scottlowe.org/2009/07/06/using-vmware-esx-virtual-switch-tagging-with-hp-virtual-connect/comment-page-1/#comment-47023</link>
		<dc:creator>Diego</dc:creator>
		<pubDate>Sat, 12 Dec 2009 05:45:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1446#comment-47023</guid>
		<description>Hello Chuck Hooper, how you resolve the issue with ARP?, i have the same problem.
Regards</description>
		<content:encoded><![CDATA[<p>Hello Chuck Hooper, how you resolve the issue with ARP?, i have the same problem.<br />
Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chuck Hooper</title>
		<link>http://blog.scottlowe.org/2009/07/06/using-vmware-esx-virtual-switch-tagging-with-hp-virtual-connect/comment-page-1/#comment-46453</link>
		<dc:creator>Chuck Hooper</dc:creator>
		<pubDate>Wed, 28 Oct 2009 16:29:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1446#comment-46453</guid>
		<description>We&#039;re setting things up similar to Greg, however I&#039;ve run into an ODD issue where the ARP requests from a Guest VM to the Cisco Gateway is never getting back to the VM. I can use ICMP pings of other servers on the same VLAN (across switches mind you) and it works fine. Have a case open with Vmware on it, but haven&#039;t heard back</description>
		<content:encoded><![CDATA[<p>We&#8217;re setting things up similar to Greg, however I&#8217;ve run into an ODD issue where the ARP requests from a Guest VM to the Cisco Gateway is never getting back to the VM. I can use ICMP pings of other servers on the same VLAN (across switches mind you) and it works fine. Have a case open with Vmware on it, but haven&#8217;t heard back</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Palmer</title>
		<link>http://blog.scottlowe.org/2009/07/06/using-vmware-esx-virtual-switch-tagging-with-hp-virtual-connect/comment-page-1/#comment-46163</link>
		<dc:creator>Greg Palmer</dc:creator>
		<pubDate>Thu, 08 Oct 2009 02:05:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=1446#comment-46163</guid>
		<description>We have set up our flex 10&#039;s with an LACP port channel to each flex 10 module. The shared uplink sets are named like sus_VDC-Set1-A and
sus_VDC-Set1-A-B. Suppose these carry vlan ids 100,200, 300 and 400.
 I define networks on each of the uplink sets as nw_100-A and nw_100-B for the respective uplink sets. Then when setting up NICs you choose an uplink set for the NIC and only select networks defined on that uplink set. This prevents loops as the left NIC&#039;s go out sus A and the right NIC&#039;s go out sus B. Then we make a failover ot TeLB bond for the NIC&#039;s. Done! Dual redundant LACP paths back to different switches with the host responsible for failover.

One other thing to think about is that if you alternate the sever profiles so that say everyblade in an odd slot uses sus A for the left NIC and every even slot uses sus B for the left NIC then you can get the incoming traffic to the blades coming in both sus&#039;s rather than just the left without mucking around too much with preferences in the teaming config. Setting the first NIC always as the preferred master will then cause things to failover and fail back at the host level.</description>
		<content:encoded><![CDATA[<p>We have set up our flex 10&#8242;s with an LACP port channel to each flex 10 module. The shared uplink sets are named like sus_VDC-Set1-A and<br />
sus_VDC-Set1-A-B. Suppose these carry vlan ids 100,200, 300 and 400.<br />
 I define networks on each of the uplink sets as nw_100-A and nw_100-B for the respective uplink sets. Then when setting up NICs you choose an uplink set for the NIC and only select networks defined on that uplink set. This prevents loops as the left NIC&#8217;s go out sus A and the right NIC&#8217;s go out sus B. Then we make a failover ot TeLB bond for the NIC&#8217;s. Done! Dual redundant LACP paths back to different switches with the host responsible for failover.</p>
<p>One other thing to think about is that if you alternate the sever profiles so that say everyblade in an odd slot uses sus A for the left NIC and every even slot uses sus B for the left NIC then you can get the incoming traffic to the blades coming in both sus&#8217;s rather than just the left without mucking around too much with preferences in the teaming config. Setting the first NIC always as the preferred master will then cause things to failover and fail back at the host level.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

