<?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: Design Challenges Of Virtualized vCenter With A vNetwork Distributed Switch</title>
	<atom:link href="http://vmetc.com/2010/03/07/design-challenges-of-virtualized-vcenter-with-a-vnetwork-distributed-switch/feed/" rel="self" type="application/rss+xml" />
	<link>http://vmetc.com/2010/03/07/design-challenges-of-virtualized-vcenter-with-a-vnetwork-distributed-switch/</link>
	<description>Go Green with Virtualization. Go UGLY Green with vmetc.com.</description>
	<lastBuildDate>Tue, 17 Apr 2012 03:50:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: vDS &#8211; vCenter Problem - Admins Goodies</title>
		<link>http://vmetc.com/2010/03/07/design-challenges-of-virtualized-vcenter-with-a-vnetwork-distributed-switch/comment-page-1/#comment-5921</link>
		<dc:creator>vDS &#8211; vCenter Problem - Admins Goodies</dc:creator>
		<pubDate>Thu, 18 Aug 2011 22:52:47 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=5539#comment-5921</guid>
		<description>[...] a lot of discussion about this and other similar Catch 22 variations in this blog post by Rich Brambley on VM /ETC and in this post by Jason [...]</description>
		<content:encoded><![CDATA[<p>[...] a lot of discussion about this and other similar Catch 22 variations in this blog post by Rich Brambley on VM /ETC and in this post by Jason [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VCAP-DCA Study notes &#8211; 2.1 Implement and Manage Complex Virtual Networks &#124; www.vExperienced.co.uk</title>
		<link>http://vmetc.com/2010/03/07/design-challenges-of-virtualized-vcenter-with-a-vnetwork-distributed-switch/comment-page-1/#comment-5881</link>
		<dc:creator>VCAP-DCA Study notes &#8211; 2.1 Implement and Manage Complex Virtual Networks &#124; www.vExperienced.co.uk</dc:creator>
		<pubDate>Thu, 31 Mar 2011 18:48:06 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=5539#comment-5881</guid>
		<description>[...] Design considerations for the vDS (Rich Brambley) [...]</description>
		<content:encoded><![CDATA[<p>[...] Design considerations for the vDS (Rich Brambley) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Virtual Distributed Switch (vDS): Clearing it up (to myself).</title>
		<link>http://vmetc.com/2010/03/07/design-challenges-of-virtualized-vcenter-with-a-vnetwork-distributed-switch/comment-page-1/#comment-5860</link>
		<dc:creator>Virtual Distributed Switch (vDS): Clearing it up (to myself).</dc:creator>
		<pubDate>Wed, 16 Feb 2011 09:40:03 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=5539#comment-5860</guid>
		<description>[...] Rich @ VM / ETC also weighed in on the issue dvSwitch Design considerations [...]</description>
		<content:encoded><![CDATA[<p>[...] Rich @ VM / ETC also weighed in on the issue dvSwitch Design considerations [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Migration from vCenter 4.0 to 4.1 &#8211; One Geeks Journey&#8230; : My Geek Finds</title>
		<link>http://vmetc.com/2010/03/07/design-challenges-of-virtualized-vcenter-with-a-vnetwork-distributed-switch/comment-page-1/#comment-5850</link>
		<dc:creator>Migration from vCenter 4.0 to 4.1 &#8211; One Geeks Journey&#8230; : My Geek Finds</dc:creator>
		<pubDate>Mon, 31 Jan 2011 13:29:27 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=5539#comment-5850</guid>
		<description>[...] Design Challenges Of Virtualized vCenter With A vNetwork Distributed Switch    Share and Enjoy: [...]</description>
		<content:encoded><![CDATA[<p>[...] Design Challenges Of Virtualized vCenter With A vNetwork Distributed Switch    Share and Enjoy: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Habibalby</title>
		<link>http://vmetc.com/2010/03/07/design-challenges-of-virtualized-vcenter-with-a-vnetwork-distributed-switch/comment-page-1/#comment-5811</link>
		<dc:creator>Habibalby</dc:creator>
		<pubDate>Mon, 06 Dec 2010 06:17:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=5539#comment-5811</guid>
		<description>hi rbrambley, 

MSCS will keep the vCenter highly available. The concern here is all about vNetwork and DvS, what if the vCenter is part of the Dvs, and vCenter failed, or the host which the vCenter runs on failed, the answer is no access to DvS because the vCenter is not available. 

I believe with vCenter MSCS running separated on each host, DvS will be available as long as the vCenter shutdown/not available.

</description>
		<content:encoded><![CDATA[<p>hi rbrambley, </p>
<p>MSCS will keep the vCenter highly available. The concern here is all about vNetwork and DvS, what if the vCenter is part of the Dvs, and vCenter failed, or the host which the vCenter runs on failed, the answer is no access to DvS because the vCenter is not available. </p>
<p>I believe with vCenter MSCS running separated on each host, DvS will be available as long as the vCenter shutdown/not available.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rbrambley</title>
		<link>http://vmetc.com/2010/03/07/design-challenges-of-virtualized-vcenter-with-a-vnetwork-distributed-switch/comment-page-1/#comment-5810</link>
		<dc:creator>rbrambley</dc:creator>
		<pubDate>Mon, 06 Dec 2010 01:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=5539#comment-5810</guid>
		<description>Habibalby,

Although a MSCS config seems to cover making the VCenter highly available,
the issue is really what virtual networking switch and portgroup the VCenter
connects to. In your case, what both VCenter nodes connect to. I&#039;m not sure
this accounts for the problem I was trying to point out.</description>
		<content:encoded><![CDATA[<p>Habibalby,</p>
<p>Although a MSCS config seems to cover making the VCenter highly available,<br />
the issue is really what virtual networking switch and portgroup the VCenter<br />
connects to. In your case, what both VCenter nodes connect to. I&#8217;m not sure<br />
this accounts for the problem I was trying to point out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Habibalby</title>
		<link>http://vmetc.com/2010/03/07/design-challenges-of-virtualized-vcenter-with-a-vnetwork-distributed-switch/comment-page-1/#comment-5809</link>
		<dc:creator>Habibalby</dc:creator>
		<pubDate>Sun, 05 Dec 2010 20:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=5539#comment-5809</guid>
		<description>hello, 

what about vCenter in MSCS each node sets in the local datastore of the esx server? and have the SQL DB inside a vmdk. 

Don&#039;t you think this will solve the issue?</description>
		<content:encoded><![CDATA[<p>hello, </p>
<p>what about vCenter in MSCS each node sets in the local datastore of the esx server? and have the SQL DB inside a vmdk. </p>
<p>Don&#8217;t you think this will solve the issue?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMware vFabric: A Hypervisor For Networkers? &#8211; Gestalt IT</title>
		<link>http://vmetc.com/2010/03/07/design-challenges-of-virtualized-vcenter-with-a-vnetwork-distributed-switch/comment-page-1/#comment-4677</link>
		<dc:creator>VMware vFabric: A Hypervisor For Networkers? &#8211; Gestalt IT</dc:creator>
		<pubDate>Thu, 12 Aug 2010 20:02:00 +0000</pubDate>
		<guid isPermaLink="false">http://vmetc.com/?p=5539#comment-4677</guid>
		<description>[...] and advanced management features. See this comparison of vSwitch, vSS, vDS, and 1000v as well as Rich Brambley’s vSS/vDS [...]</description>
		<content:encoded><![CDATA[<p>[...] and advanced management features. See this comparison of vSwitch, vSS, vDS, and 1000v as well as Rich Brambley’s vSS/vDS [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

