<?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: New VMware VI network port diagram request for comments</title>
	<atom:link href="http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/</link>
	<description></description>
	<lastBuildDate>Fri, 30 Jul 2010 06:01:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Chris Chapman</title>
		<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/comment-page-1/#comment-1042</link>
		<dc:creator>Chris Chapman</dc:creator>
		<pubDate>Thu, 16 Jul 2009 15:17:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=655#comment-1042</guid>
		<description>Point of order - I dont&#039; think VC uses port 443 to talk to esx.</description>
		<content:encoded><![CDATA[<p>Point of order &#8211; I dont&#8217; think VC uses port 443 to talk to esx.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cannot connect to VM Console &#171; Think Virtualization.net</title>
		<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/comment-page-1/#comment-618</link>
		<dc:creator>Cannot connect to VM Console &#171; Think Virtualization.net</dc:creator>
		<pubDate>Mon, 09 Mar 2009 05:49:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=655#comment-618</guid>
		<description>[...] to ensure the necessary ports were open – ports 902 and 903 in particular – something which the VI3 Network Communications Diagram came quite handy in [...]</description>
		<content:encoded><![CDATA[<p>[...] to ensure the necessary ports were open – ports 902 and 903 in particular – something which the VI3 Network Communications Diagram came quite handy in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Think Virtualization.net &#187; Cannot connect to VM Console</title>
		<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/comment-page-1/#comment-584</link>
		<dc:creator>Think Virtualization.net &#187; Cannot connect to VM Console</dc:creator>
		<pubDate>Wed, 25 Feb 2009 23:17:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=655#comment-584</guid>
		<description>[...] to ensure the necessary ports were open – ports 902 and 903 in particular – something which the VI3 Network Communications Diagram came quite handy in [...]</description>
		<content:encoded><![CDATA[<p>[...] to ensure the necessary ports were open – ports 902 and 903 in particular – something which the VI3 Network Communications Diagram came quite handy in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMware VI Network Port Diagram &#124; Weblog.BassQ.nl</title>
		<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/comment-page-1/#comment-574</link>
		<dc:creator>VMware VI Network Port Diagram &#124; Weblog.BassQ.nl</dc:creator>
		<pubDate>Sun, 22 Feb 2009 13:40:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=655#comment-574</guid>
		<description>[...] You can find the high res diagram over here: http://www.boche.net/blog/?p=655 [...]</description>
		<content:encoded><![CDATA[<p>[...] You can find the high res diagram over here: <a href="http://www.boche.net/blog/?p=655" rel="nofollow">http://www.boche.net/blog/?p=655</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diagramme des ports réseau utilisés par Vmware ESX &#124; Sur le fil technologique</title>
		<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/comment-page-1/#comment-542</link>
		<dc:creator>Diagramme des ports réseau utilisés par Vmware ESX &#124; Sur le fil technologique</dc:creator>
		<pubDate>Mon, 09 Feb 2009 14:03:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=655#comment-542</guid>
		<description>[...] http://www.boche.net/blog/?p=655 [...]</description>
		<content:encoded><![CDATA[<p>[...] <a href="http://www.boche.net/blog/?p=655" rel="nofollow">http://www.boche.net/blog/?p=655</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joaquin Avellan</title>
		<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/comment-page-1/#comment-468</link>
		<dc:creator>Joaquin Avellan</dc:creator>
		<pubDate>Tue, 13 Jan 2009 22:00:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=655#comment-468</guid>
		<description>I take my comment back, after a quick wireshark in my environments I&#039;ve confirmed you do need tcp 902,903 to the ESX server regardless if you&#039;re using the vCenter. However you can place an additional setting on the ESX host to proxy the Remote Console data session to 902 instead of using 903. 
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;docType=kc&amp;externalId=749640&amp;sliceId=2&amp;docTypeID=DT_KB_1_1&amp;dialogID=18254837&amp;stateId=0%200%2018256101</description>
		<content:encoded><![CDATA[<p>I take my comment back, after a quick wireshark in my environments I&#8217;ve confirmed you do need tcp 902,903 to the ESX server regardless if you&#8217;re using the vCenter. However you can place an additional setting on the ESX host to proxy the Remote Console data session to 902 instead of using 903.<br />
<a href="http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;docType=kc&amp;externalId=749640&amp;sliceId=2&amp;docTypeID=DT_KB_1_1&amp;dialogID=18254837&amp;stateId=0%200%2018256101" rel="nofollow">http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&amp;docType=kc&amp;externalId=749640&amp;sliceId=2&amp;docTypeID=DT_KB_1_1&amp;dialogID=18254837&amp;stateId=0%200%2018256101</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VI Network Port Diagram &#187; Werts Networking</title>
		<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/comment-page-1/#comment-455</link>
		<dc:creator>VI Network Port Diagram &#187; Werts Networking</dc:creator>
		<pubDate>Fri, 09 Jan 2009 13:12:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=655#comment-455</guid>
		<description>[...] Jason Boche (http://www.boche.net/blog/) heeft een mooi diagram voor VI met TCP port informatie. Hier te downloaden http://www.boche.net/blog/?p=655 [...]</description>
		<content:encoded><![CDATA[<p>[...] Jason Boche (<a href="http://www.boche.net/blog/" rel="nofollow">http://www.boche.net/blog/</a>) heeft een mooi diagram voor VI met TCP port informatie. Hier te downloaden <a href="http://www.boche.net/blog/?p=655" rel="nofollow">http://www.boche.net/blog/?p=655</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Welke poorten gebruikt VMware &#171; EarlyBert</title>
		<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/comment-page-1/#comment-451</link>
		<dc:creator>Welke poorten gebruikt VMware &#171; EarlyBert</dc:creator>
		<pubDate>Thu, 08 Jan 2009 20:18:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=655#comment-451</guid>
		<description>[...] van VMware staat vermeld. Het schema is gemaakt door Shlomo Rivkin en door Jason Boche op zijn blog geplaatst met het verzoek om te controleren of e.e.a. [...]</description>
		<content:encoded><![CDATA[<p>[...] van VMware staat vermeld. Het schema is gemaakt door Shlomo Rivkin en door Jason Boche op zijn blog geplaatst met het verzoek om te controleren of e.e.a. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brandon</title>
		<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/comment-page-1/#comment-450</link>
		<dc:creator>Brandon</dc:creator>
		<pubDate>Thu, 08 Jan 2009 15:25:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=655#comment-450</guid>
		<description>This is awesome!
Since the service console and vmkernel port groups have different requirements, how about separating them on the ESX server then moving the lines to the appropriate port groups.  It would also be nice to see ssh, dns, and snmp on the diagram.</description>
		<content:encoded><![CDATA[<p>This is awesome!<br />
Since the service console and vmkernel port groups have different requirements, how about separating them on the ESX server then moving the lines to the appropriate port groups.  It would also be nice to see ssh, dns, and snmp on the diagram.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMware: VI Network Port Diagram &#171; ICT-Freak.nl</title>
		<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/comment-page-1/#comment-448</link>
		<dc:creator>VMware: VI Network Port Diagram &#171; ICT-Freak.nl</dc:creator>
		<pubDate>Thu, 08 Jan 2009 12:48:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=655#comment-448</guid>
		<description>[...] You can find the high res diagram over here: http://www.boche.net/blog/?p=655 [...]</description>
		<content:encoded><![CDATA[<p>[...] You can find the high res diagram over here: <a href="http://www.boche.net/blog/?p=655" rel="nofollow">http://www.boche.net/blog/?p=655</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adil Laari</title>
		<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/comment-page-1/#comment-409</link>
		<dc:creator>Adil Laari</dc:creator>
		<pubDate>Tue, 30 Dec 2008 14:25:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=655#comment-409</guid>
		<description>This is a great post. very very useful, and helps quite a lot in troubleshooting.

Thanks Shlomo</description>
		<content:encoded><![CDATA[<p>This is a great post. very very useful, and helps quite a lot in troubleshooting.</p>
<p>Thanks Shlomo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joaquin Avellan</title>
		<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/comment-page-1/#comment-378</link>
		<dc:creator>Joaquin Avellan</dc:creator>
		<pubDate>Sat, 20 Dec 2008 01:19:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=655#comment-378</guid>
		<description>I believe a VI Client/Web connecting through vCenter only needs tcp 903 to the ESX 3.5 server for console, if a VI Client connects directly to an ESX 3.5 server it would need tcp 443+903. Can anyone show me which documentation tcp 902 to the ESX 3.5 servers for Remote Console access is being pulled from? Thanks!
-Joaquin</description>
		<content:encoded><![CDATA[<p>I believe a VI Client/Web connecting through vCenter only needs tcp 903 to the ESX 3.5 server for console, if a VI Client connects directly to an ESX 3.5 server it would need tcp 443+903. Can anyone show me which documentation tcp 902 to the ESX 3.5 servers for Remote Console access is being pulled from? Thanks!<br />
-Joaquin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Virtualization Short Take #24 - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers</title>
		<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/comment-page-1/#comment-335</link>
		<dc:creator>Virtualization Short Take #24 - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers</dc:creator>
		<pubDate>Mon, 15 Dec 2008 15:57:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=655#comment-335</guid>
		<description>[...] up to 100 virtual machines Version 4 of the PowerVDI tool Go Daddy Wildcard Certificate with VI3 New VMware VI network port diagram request for comments Auditing ESX root logins with [...]</description>
		<content:encoded><![CDATA[<p>[...] up to 100 virtual machines Version 4 of the PowerVDI tool Go Daddy Wildcard Certificate with VI3 New VMware VI network port diagram request for comments Auditing ESX root logins with [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Roger Lund</title>
		<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/comment-page-1/#comment-333</link>
		<dc:creator>Roger Lund</dc:creator>
		<pubDate>Mon, 15 Dec 2008 15:14:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=655#comment-333</guid>
		<description>Looks nice, but I would love to see it with a full network diagram with full Network Production / iSCSI / NFS / FC network configuration.

Roger L

http://rogerlunditblog.blogspot.com/</description>
		<content:encoded><![CDATA[<p>Looks nice, but I would love to see it with a full network diagram with full Network Production / iSCSI / NFS / FC network configuration.</p>
<p>Roger L</p>
<p><a href="http://rogerlunditblog.blogspot.com/" rel="nofollow">http://rogerlunditblog.blogspot.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: matt</title>
		<link>http://www.boche.net/blog/index.php/2008/12/12/new-vmware-vi-network-port-diagram-request-for-comments/comment-page-1/#comment-332</link>
		<dc:creator>matt</dc:creator>
		<pubDate>Mon, 15 Dec 2008 10:18:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.boche.net/blog/?p=655#comment-332</guid>
		<description>You guys rock!  I&#039;ll drop yo you line. And the linked PDF looks great as well.  thank you!</description>
		<content:encoded><![CDATA[<p>You guys rock!  I&#8217;ll drop yo you line. And the linked PDF looks great as well.  thank you!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
