<?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: PowerEdge 6650 NIC Issues</title>
	<atom:link href="http://www.mymegabyte.com/2008/07/poweredge-6650-nic-issues/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mymegabyte.com/2008/07/poweredge-6650-nic-issues/</link>
	<description>Random tech things that I come across.</description>
	<lastBuildDate>Fri, 13 Nov 2009 03:20:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Justin</title>
		<link>http://www.mymegabyte.com/2008/07/poweredge-6650-nic-issues/comment-page-1/#comment-47</link>
		<dc:creator>Justin</dc:creator>
		<pubDate>Sat, 07 Feb 2009 19:11:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.mymegabyte.com/?p=28#comment-47</guid>
		<description>Oh great!  Well at least it&#039;s not just me!  I just started a job setting up CentOS servers.  I am running samba with an NFS mounted drive.  When transferring large amounts of data, the machine just locks up.  A restart of the networks seems to clear up the problem, but it takes about 7 mins to see the network drive again.</description>
		<content:encoded><![CDATA[<p>Oh great!  Well at least it&#8217;s not just me!  I just started a job setting up CentOS servers.  I am running samba with an NFS mounted drive.  When transferring large amounts of data, the machine just locks up.  A restart of the networks seems to clear up the problem, but it takes about 7 mins to see the network drive again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://www.mymegabyte.com/2008/07/poweredge-6650-nic-issues/comment-page-1/#comment-16</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Fri, 08 Aug 2008 17:16:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.mymegabyte.com/?p=28#comment-16</guid>
		<description>Update 2:
The fix did not work. Today I have crashed the NIC in the NFS server twice. This is frustrating! Back to the drawing board.</description>
		<content:encoded><![CDATA[<p>Update 2:<br />
The fix did not work. Today I have crashed the NIC in the NFS server twice. This is frustrating! Back to the drawing board.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://www.mymegabyte.com/2008/07/poweredge-6650-nic-issues/comment-page-1/#comment-15</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Wed, 06 Aug 2008 02:50:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.mymegabyte.com/?p=28#comment-15</guid>
		<description>Update 1:
Last week the server which has NOT had the firmware upgrade crashed one its internal Broadcom NICs. Believe it or not it did it while handing out IP addresses with DHCP! Not exactly a very intensive task. Oh well, needless to say I upgraded the firmware on that server too. Now I&#039;m testing the firmware as a fix for the NIC crashes on both PowerEdge 6650&#039;s.

I got a kick out of the change logs for the BMC firmware. For almost every release between 1.64 and 1.78 the Dell comment for the revision is &quot;maintenance&quot;. Oh great, thanks! That really helps me understand if this update might resolve my issue.</description>
		<content:encoded><![CDATA[<p>Update 1:<br />
Last week the server which has NOT had the firmware upgrade crashed one its internal Broadcom NICs. Believe it or not it did it while handing out IP addresses with DHCP! Not exactly a very intensive task. Oh well, needless to say I upgraded the firmware on that server too. Now I&#8217;m testing the firmware as a fix for the NIC crashes on both PowerEdge 6650&#8242;s.</p>
<p>I got a kick out of the change logs for the BMC firmware. For almost every release between 1.64 and 1.78 the Dell comment for the revision is &#8220;maintenance&#8221;. Oh great, thanks! That really helps me understand if this update might resolve my issue.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
