<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for vUniverse</title>
	<atom:link href="http://v-universe.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://v-universe.com</link>
	<description>Musings about all things Virtual</description>
	<lastBuildDate>Thu, 12 May 2011 18:03:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Weird MLT (aka EtherChannel) issues with vSphere / ESX 3.5 by MkH</title>
		<link>http://v-universe.com/2010/02/02/weird-mlt-aka-etherchannel-issues-with-vsphere-esx-3-5/#comment-4</link>
		<dc:creator><![CDATA[MkH]]></dc:creator>
		<pubDate>Thu, 12 May 2011 18:03:40 +0000</pubDate>
		<guid isPermaLink="false">http://v-universe.com/?p=22#comment-4</guid>
		<description><![CDATA[Ignore my last post. It was so long since I wrote the post that I forgot what the problem was! 

We still don&#039;t know why the on-board nics don&#039;t auto-negotiate correctly if the switch stack is rebooted. We have at least 20 servers with the same hard ware spec/configuration and all the add-on nic cards exhibit the same behaviour.

Thankfully, once we sorted out the stack issue, we have never had to reboot it again since!]]></description>
		<content:encoded><![CDATA[<p>Ignore my last post. It was so long since I wrote the post that I forgot what the problem was! </p>
<p>We still don&#8217;t know why the on-board nics don&#8217;t auto-negotiate correctly if the switch stack is rebooted. We have at least 20 servers with the same hard ware spec/configuration and all the add-on nic cards exhibit the same behaviour.</p>
<p>Thankfully, once we sorted out the stack issue, we have never had to reboot it again since!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Weird MLT (aka EtherChannel) issues with vSphere / ESX 3.5 by MkH</title>
		<link>http://v-universe.com/2010/02/02/weird-mlt-aka-etherchannel-issues-with-vsphere-esx-3-5/#comment-3</link>
		<dc:creator><![CDATA[MkH]]></dc:creator>
		<pubDate>Thu, 12 May 2011 17:59:43 +0000</pubDate>
		<guid isPermaLink="false">http://v-universe.com/?p=22#comment-3</guid>
		<description><![CDATA[Hi Max.

Thanks for taking the time to reply. The issue actually was cause by a faulty backplane cable that was used to connect the switches into a stack. The traces and logs never showed an error. But replacing it, did.]]></description>
		<content:encoded><![CDATA[<p>Hi Max.</p>
<p>Thanks for taking the time to reply. The issue actually was cause by a faulty backplane cable that was used to connect the switches into a stack. The traces and logs never showed an error. But replacing it, did.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Weird MLT (aka EtherChannel) issues with vSphere / ESX 3.5 by Max Lukjanenko</title>
		<link>http://v-universe.com/2010/02/02/weird-mlt-aka-etherchannel-issues-with-vsphere-esx-3-5/#comment-2</link>
		<dc:creator><![CDATA[Max Lukjanenko]]></dc:creator>
		<pubDate>Mon, 09 May 2011 14:02:16 +0000</pubDate>
		<guid isPermaLink="false">http://v-universe.com/?p=22#comment-2</guid>
		<description><![CDATA[Your problem is Layer 1, so forget about VLANs and routing.

If you are using nortel 5510/5520 baystack switches, they autonegotiate perfectly with all new equipment.

Your problem will occur if: cables are damaged/not punched-in correctly or are not connected properly in any way. Or if the signal is too weak due to attenuation caused by the distance of the cable.

You must make sure that you are using fully straight-thru cable configuration between the switch and the server. You must also make sure you are using CAT6 cables.

Alternatively, you may use fiber, which is more expensive but does not have the same L1 issues as copper cables.]]></description>
		<content:encoded><![CDATA[<p>Your problem is Layer 1, so forget about VLANs and routing.</p>
<p>If you are using nortel 5510/5520 baystack switches, they autonegotiate perfectly with all new equipment.</p>
<p>Your problem will occur if: cables are damaged/not punched-in correctly or are not connected properly in any way. Or if the signal is too weak due to attenuation caused by the distance of the cable.</p>
<p>You must make sure that you are using fully straight-thru cable configuration between the switch and the server. You must also make sure you are using CAT6 cables.</p>
<p>Alternatively, you may use fiber, which is more expensive but does not have the same L1 issues as copper cables.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hello world! by Mr WordPress</title>
		<link>http://v-universe.com/2010/01/08/hello-world/#comment-1</link>
		<dc:creator><![CDATA[Mr WordPress]]></dc:creator>
		<pubDate>Fri, 08 Jan 2010 17:05:31 +0000</pubDate>
		<guid isPermaLink="false">#comment-1</guid>
		<description><![CDATA[Hi, this is a comment.&lt;br /&gt;To delete a comment, just log in, and view the posts&#039; comments, there you will have the option to edit or delete them.]]></description>
		<content:encoded><![CDATA[<p>Hi, this is a comment.<br />To delete a comment, just log in, and view the posts&#8217; comments, there you will have the option to edit or delete them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

