<?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"
	>
<channel>
	<title>Comments on: iSCSI and ESX Server 3</title>
	<atom:link href="http://blog.scottlowe.org/2006/07/10/iscsi-and-esx-server-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scottlowe.org/2006/07/10/iscsi-and-esx-server-3/</link>
	<description>The weblog of an IT pro specializing in virtualization, storage, and servers</description>
	<pubDate>Thu, 20 Nov 2008 11:59:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2006/07/10/iscsi-and-esx-server-3/#comment-16858</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Fri, 05 Jan 2007 22:09:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=295#comment-16858</guid>
		<description>Don,

Glad to hear you've found the site helpful.

Thanks,
Scott</description>
		<content:encoded><![CDATA[<p>Don,</p>
<p>Glad to hear you&#8217;ve found the site helpful.</p>
<p>Thanks,<br />
Scott</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don Lapre James</title>
		<link>http://blog.scottlowe.org/2006/07/10/iscsi-and-esx-server-3/#comment-16758</link>
		<dc:creator>Don Lapre James</dc:creator>
		<pubDate>Fri, 05 Jan 2007 00:01:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=295#comment-16758</guid>
		<description>Your info here has helped me trouble shoot a few of my own errors.  Just wanted to thank you for the info and the blog.

Best regards, 

Jim	
Don Lapre James	
webmaster@donlaprewilliams.com	
www.donlaprewilliams.com</description>
		<content:encoded><![CDATA[<p>Your info here has helped me trouble shoot a few of my own errors.  Just wanted to thank you for the info and the blog.</p>
<p>Best regards, </p>
<p>Jim<br />
Don Lapre James<br />
<a href="mailto:webmaster@donlaprewilliams.com">webmaster@donlaprewilliams.com</a><br />
<a href="http://www.donlaprewilliams.com" rel="nofollow">http://www.donlaprewilliams.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2006/07/10/iscsi-and-esx-server-3/#comment-2887</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Thu, 26 Oct 2006 20:34:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=295#comment-2887</guid>
		<description>David,

Sounds like your issue is not the ESX firewall but instead a default setting in ESX that only lets it see 8 LUNs.  Anything after 8 is invisible.  Look for the Disk.MaxLUN setting and set it higher than your highest LUN to be presented to the servers.  I'm not in front of ESX right at this moment so I can't directly you to the exact place where it is set.</description>
		<content:encoded><![CDATA[<p>David,</p>
<p>Sounds like your issue is not the ESX firewall but instead a default setting in ESX that only lets it see 8 LUNs.  Anything after 8 is invisible.  Look for the Disk.MaxLUN setting and set it higher than your highest LUN to be presented to the servers.  I&#8217;m not in front of ESX right at this moment so I can&#8217;t directly you to the exact place where it is set.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Blaisdell</title>
		<link>http://blog.scottlowe.org/2006/07/10/iscsi-and-esx-server-3/#comment-2881</link>
		<dc:creator>David Blaisdell</dc:creator>
		<pubDate>Thu, 26 Oct 2006 03:12:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=295#comment-2881</guid>
		<description>I just experienced the issue relating to iSCSI and the VM ESX firewall.  The twist I encountered was that after the initial build of 4 ESX hosts everything worked fine and I added 8 LUNs and had a dozen VMs running with no issue.  However when trying to add a 9th LUN I could not.  Somehow the firewall was enabled for inbound/outbound iSCSI connections but then got turned off somehow??

Thanks for your coverage of this - it will save many some unnecessary frustration.

David</description>
		<content:encoded><![CDATA[<p>I just experienced the issue relating to iSCSI and the VM ESX firewall.  The twist I encountered was that after the initial build of 4 ESX hosts everything worked fine and I added 8 LUNs and had a dozen VMs running with no issue.  However when trying to add a 9th LUN I could not.  Somehow the firewall was enabled for inbound/outbound iSCSI connections but then got turned off somehow??</p>
<p>Thanks for your coverage of this - it will save many some unnecessary frustration.</p>
<p>David</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2006/07/10/iscsi-and-esx-server-3/#comment-2294</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Fri, 15 Sep 2006 10:35:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=295#comment-2294</guid>
		<description>Jae,

Good question--I'd hazard to say NIC as opposed to Filer CPU, but I'm not a NetApp guru so don't quote me on that.  I'll see if I can get a NetApp guru from my office to provide his perspective.</description>
		<content:encoded><![CDATA[<p>Jae,</p>
<p>Good question&#8211;I&#8217;d hazard to say NIC as opposed to Filer CPU, but I&#8217;m not a NetApp guru so don&#8217;t quote me on that.  I&#8217;ll see if I can get a NetApp guru from my office to provide his perspective.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jae Ellers</title>
		<link>http://blog.scottlowe.org/2006/07/10/iscsi-and-esx-server-3/#comment-2279</link>
		<dc:creator>Jae Ellers</dc:creator>
		<pubDate>Thu, 14 Sep 2006 20:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=295#comment-2279</guid>
		<description>We're doing this now, have 740 GB coming online in 3 luns for migrating ESX 2 --&#62; 3.  Vmotion works great so far with limited usage on ibm x366 systems.  Will have to see how the iSCSI load impacts the filer.  We've already got a new 4-port card to add if the production network becomes overloaded.  Anyone comment on where we should see the bottleneck?  Filer CPU or NIC?  It's a FAS 3050.</description>
		<content:encoded><![CDATA[<p>We&#8217;re doing this now, have 740 GB coming online in 3 luns for migrating ESX 2 &#8211;&gt; 3.  Vmotion works great so far with limited usage on ibm x366 systems.  Will have to see how the iSCSI load impacts the filer.  We&#8217;ve already got a new 4-port card to add if the production network becomes overloaded.  Anyone comment on where we should see the bottleneck?  Filer CPU or NIC?  It&#8217;s a FAS 3050.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2006/07/10/iscsi-and-esx-server-3/#comment-1718</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Fri, 18 Aug 2006 20:14:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=295#comment-1718</guid>
		<description>Dennis,

I reviewed the NetApp documents you mentioned in your comment, but none of them pertain to iSCSI configuration or troubleshooting; they are all high-level overviews of using NetApp Filers and Snapshot technology with VMware.  I would suggest you step back from that and fall back to troubleshooting the basic iSCSI connectivity:  make sure you have correctly mapped the LUNs on the Filer, make sure the initiator groups are correctly configured, and (on the VMware side) make sure you have allowed the software iSCSI traffic through the firewall.

Let me know how I can help further.</description>
		<content:encoded><![CDATA[<p>Dennis,</p>
<p>I reviewed the NetApp documents you mentioned in your comment, but none of them pertain to iSCSI configuration or troubleshooting; they are all high-level overviews of using NetApp Filers and Snapshot technology with VMware.  I would suggest you step back from that and fall back to troubleshooting the basic iSCSI connectivity:  make sure you have correctly mapped the LUNs on the Filer, make sure the initiator groups are correctly configured, and (on the VMware side) make sure you have allowed the software iSCSI traffic through the firewall.</p>
<p>Let me know how I can help further.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2006/07/10/iscsi-and-esx-server-3/#comment-1717</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Fri, 18 Aug 2006 20:07:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=295#comment-1717</guid>
		<description>Tim,

iSCSI works reasonably well as a storage mechanism, but that's only part of the picture when it comes to VMotion.  Since the virtual disk file (the VMDK file) doesn't move during a VMotion operation, the storage is kind of secondary to the whole equation.  You will need Gigabit Ethernet connectivity on the same subnet for VMotion to work between ESX servers, and you should be using Gigabit Ethernet for iSCSI anyway.  Although I have not tested NFS yet (plan to soon), VMware's product page indicates full support for the storage of VMDK files and VMotion with NFS.  Refer to http://www.vmware.com/products/vi/esx/#interoperability and see the section titled "Storage" for the official party line.</description>
		<content:encoded><![CDATA[<p>Tim,</p>
<p>iSCSI works reasonably well as a storage mechanism, but that&#8217;s only part of the picture when it comes to VMotion.  Since the virtual disk file (the VMDK file) doesn&#8217;t move during a VMotion operation, the storage is kind of secondary to the whole equation.  You will need Gigabit Ethernet connectivity on the same subnet for VMotion to work between ESX servers, and you should be using Gigabit Ethernet for iSCSI anyway.  Although I have not tested NFS yet (plan to soon), VMware&#8217;s product page indicates full support for the storage of VMDK files and VMotion with NFS.  Refer to <a href="http://www.vmware.com/products/vi/esx/#interoperability" rel="nofollow">http://www.vmware.com/products/vi/esx/#interoperability</a> and see the section titled &#8220;Storage&#8221; for the official party line.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Teller</title>
		<link>http://blog.scottlowe.org/2006/07/10/iscsi-and-esx-server-3/#comment-1716</link>
		<dc:creator>Tim Teller</dc:creator>
		<pubDate>Fri, 18 Aug 2006 19:54:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=295#comment-1716</guid>
		<description>Scott,

We have a NetApp Filer that is configured with iSCSI.  We haven't used it yet.  We are purchasing VMWare I 3 enterprise.  I am wondering if VMotion works well with iSCSI.  We also have an OnStore NAS gateway that support NFS, could you do VMotion with NFS?

Thanks in advance,
Tim Teller</description>
		<content:encoded><![CDATA[<p>Scott,</p>
<p>We have a NetApp Filer that is configured with iSCSI.  We haven&#8217;t used it yet.  We are purchasing VMWare I 3 enterprise.  I am wondering if VMotion works well with iSCSI.  We also have an OnStore NAS gateway that support NFS, could you do VMotion with NFS?</p>
<p>Thanks in advance,<br />
Tim Teller</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2006/07/10/iscsi-and-esx-server-3/#comment-1548</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Tue, 08 Aug 2006 16:06:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/?p=295#comment-1548</guid>
		<description>Are you seeing iSCSI operations on the Filer?  At the console, you'll see regular status updates showing how many HTTP, CIFS, NFS, and iSCSI operations...do you see any iSCSI operations?  If not, you may still be blocking outbound iSCSI traffic from the ESX Server.  Run the "esxcfg-firewall -e swiSCSIClient" (if you haven't already) to make sure that iSCSI traffic is being allowed out from the ESX server.

In the meantime, I'll review those NetApp documents and see what additional information I may be able to provide.</description>
		<content:encoded><![CDATA[<p>Are you seeing iSCSI operations on the Filer?  At the console, you&#8217;ll see regular status updates showing how many HTTP, CIFS, NFS, and iSCSI operations&#8230;do you see any iSCSI operations?  If not, you may still be blocking outbound iSCSI traffic from the ESX Server.  Run the &#8220;esxcfg-firewall -e swiSCSIClient&#8221; (if you haven&#8217;t already) to make sure that iSCSI traffic is being allowed out from the ESX server.</p>
<p>In the meantime, I&#8217;ll review those NetApp documents and see what additional information I may be able to provide.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
