<?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: VLANs and Port Groups</title>
	<atom:link href="http://blog.scottlowe.org/2006/04/17/vlans-and-port-groups/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scottlowe.org/2006/04/17/vlans-and-port-groups/</link>
	<description>The weblog of an IT pro specializing in virtualization, storage, and servers</description>
	<pubDate>Tue, 16 Mar 2010 07:25:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ESX Server, NIC Teaming, and VLAN Trunking at Virtualisation and SBC blog</title>
		<link>http://blog.scottlowe.org/2006/04/17/vlans-and-port-groups/comment-page-1/#comment-7592</link>
		<dc:creator>ESX Server, NIC Teaming, and VLAN Trunking at Virtualisation and SBC blog</dc:creator>
		<pubDate>Sun, 10 Dec 2006 12:20:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=226#comment-7592</guid>
		<description>[...] There are actually two different pieces described in this article.&#160; The first is NIC teaming, in which we logically bind together multiple physical NICs for increased throughput and increased fault tolerance.&#160; The second is VLAN trunking, in which we configure the physical switch to pass VLAN traffic directly to ESX Server, which will then distribute the traffic according to the port groups and VLAN IDs configured on the server.&#160; I wrote about ESX and VLAN trunking a long time ago and ran into some issues then; here Iâ€™ll describe how to work around the issues I ran into at that time. [...]</description>
		<content:encoded><![CDATA[<p>[...] There are actually two different pieces described in this article.&nbsp; The first is NIC teaming, in which we logically bind together multiple physical NICs for increased throughput and increased fault tolerance.&nbsp; The second is VLAN trunking, in which we configure the physical switch to pass VLAN traffic directly to ESX Server, which will then distribute the traffic according to the port groups and VLAN IDs configured on the server.&nbsp; I wrote about ESX and VLAN trunking a long time ago and ran into some issues then; here Iâ€™ll describe how to work around the issues I ran into at that time. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
