<?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: iSCSI multipathing with esxcli! Exploring the next version of ESX</title>
	<atom:link href="http://www.yellow-bricks.com/2009/03/18/iscsi-multipathing-with-esxcliexploring-the-next-version-of-esx/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.yellow-bricks.com/2009/03/18/iscsi-multipathing-with-esxcliexploring-the-next-version-of-esx/</link>
	<description>Building blocks for virtualization...</description>
	<lastBuildDate>Fri, 19 Mar 2010 21:53:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Arian van der Pijl</title>
		<link>http://www.yellow-bricks.com/2009/03/18/iscsi-multipathing-with-esxcliexploring-the-next-version-of-esx/comment-page-1/#comment-5981</link>
		<dc:creator>Arian van der Pijl</dc:creator>
		<pubDate>Fri, 15 Jan 2010 12:37:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=2368#comment-5981</guid>
		<description>Sorry to ask but what about the guest?
Should the guest continue to use their own iSCSI initiator as best practices? (Boot on VMFS and data volumes on iSCSI).</description>
		<content:encoded><![CDATA[<p>Sorry to ask but what about the guest?<br />
Should the guest continue to use their own iSCSI initiator as best practices? (Boot on VMFS and data volumes on iSCSI).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frankie Majowich</title>
		<link>http://www.yellow-bricks.com/2009/03/18/iscsi-multipathing-with-esxcliexploring-the-next-version-of-esx/comment-page-1/#comment-5760</link>
		<dc:creator>Frankie Majowich</dc:creator>
		<pubDate>Mon, 28 Dec 2009 19:08:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=2368#comment-5760</guid>
		<description>Duncan,

Something I came across when setting this up was during a failover. If you failed one of the paths I can no longer use vmkping to verify that storage is accessible. However, IO to the backend storage is still flowing over the other paths. Have you seen this before? I have replicated this on 2 separate VM deployments and 2 differente backend iSCSI SANs.</description>
		<content:encoded><![CDATA[<p>Duncan,</p>
<p>Something I came across when setting this up was during a failover. If you failed one of the paths I can no longer use vmkping to verify that storage is accessible. However, IO to the backend storage is still flowing over the other paths. Have you seen this before? I have replicated this on 2 separate VM deployments and 2 differente backend iSCSI SANs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chuck8773</title>
		<link>http://www.yellow-bricks.com/2009/03/18/iscsi-multipathing-with-esxcliexploring-the-next-version-of-esx/comment-page-1/#comment-4727</link>
		<dc:creator>chuck8773</dc:creator>
		<pubDate>Fri, 09 Oct 2009 10:54:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=2368#comment-4727</guid>
		<description>One thing I am running into is as follows.  Still getting details so this is a little vague.  If the first vmkernel for that subnet, has no access to the network, vmkpings to that subnet will fail.  Regardless of how many other vmkernels are in that subnet.  In our case the physical nic attached to vmk0 is down for switch maintenance.  While it is down, we are unable to mount additional volumes.  Investigating reveals that the service console is able to ping that subnet, but vmkping fails.  I confirmed with other hosts.  Hosts that have vmk0 up, due to being attached to the other switch stack, are able to ping and vmkping just fine.  All hosts that have vmk0 down are able to ping but not vmkping.

The other concern is that our EqualLogic SAN makes load balancing decisions that cause connections to log out and back into a different IP.  I am not sure what will happen if a connection tries to reconnect.</description>
		<content:encoded><![CDATA[<p>One thing I am running into is as follows.  Still getting details so this is a little vague.  If the first vmkernel for that subnet, has no access to the network, vmkpings to that subnet will fail.  Regardless of how many other vmkernels are in that subnet.  In our case the physical nic attached to vmk0 is down for switch maintenance.  While it is down, we are unable to mount additional volumes.  Investigating reveals that the service console is able to ping that subnet, but vmkping fails.  I confirmed with other hosts.  Hosts that have vmk0 up, due to being attached to the other switch stack, are able to ping and vmkping just fine.  All hosts that have vmk0 down are able to ping but not vmkping.</p>
<p>The other concern is that our EqualLogic SAN makes load balancing decisions that cause connections to log out and back into a different IP.  I am not sure what will happen if a connection tries to reconnect.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jefferson</title>
		<link>http://www.yellow-bricks.com/2009/03/18/iscsi-multipathing-with-esxcliexploring-the-next-version-of-esx/comment-page-1/#comment-4716</link>
		<dc:creator>Jefferson</dc:creator>
		<pubDate>Tue, 06 Oct 2009 22:57:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=2368#comment-4716</guid>
		<description>Just to followup on my prior comment, I was able to make this work by disabling the iSCSI adapter and then rebooting. At that point I could turn on the multi-pathing and re-enable iSCSI without a problem. I&#039;m not sure why vCenter froze the first time I tried that, but it worked properly on the rest of my hosts.</description>
		<content:encoded><![CDATA[<p>Just to followup on my prior comment, I was able to make this work by disabling the iSCSI adapter and then rebooting. At that point I could turn on the multi-pathing and re-enable iSCSI without a problem. I&#8217;m not sure why vCenter froze the first time I tried that, but it worked properly on the rest of my hosts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jefferson</title>
		<link>http://www.yellow-bricks.com/2009/03/18/iscsi-multipathing-with-esxcliexploring-the-next-version-of-esx/comment-page-1/#comment-4710</link>
		<dc:creator>Jefferson</dc:creator>
		<pubDate>Tue, 06 Oct 2009 03:24:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=2368#comment-4710</guid>
		<description>How do you remove the extra (pre-multipathing) path? Mordock above said that you can do that by removing the targets and re-adding them, but I can&#039;t figure out how do to that. I&#039;ve tried simply removing the targets from the dynamic/static discovery tabs, but the vSphere client just hangs when I try to do that. I also tried to disable iSCSI on the host with the same result. As a result I can&#039;t figure out how to remove the storage so I can re-add it without the extra path.</description>
		<content:encoded><![CDATA[<p>How do you remove the extra (pre-multipathing) path? Mordock above said that you can do that by removing the targets and re-adding them, but I can&#8217;t figure out how do to that. I&#8217;ve tried simply removing the targets from the dynamic/static discovery tabs, but the vSphere client just hangs when I try to do that. I also tried to disable iSCSI on the host with the same result. As a result I can&#8217;t figure out how to remove the storage so I can re-add it without the extra path.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duncan</title>
		<link>http://www.yellow-bricks.com/2009/03/18/iscsi-multipathing-with-esxcliexploring-the-next-version-of-esx/comment-page-1/#comment-4390</link>
		<dc:creator>Duncan</dc:creator>
		<pubDate>Thu, 27 Aug 2009 16:09:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=2368#comment-4390</guid>
		<description>no, you can do this with any version.</description>
		<content:encoded><![CDATA[<p>no, you can do this with any version.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jimheuton</title>
		<link>http://www.yellow-bricks.com/2009/03/18/iscsi-multipathing-with-esxcliexploring-the-next-version-of-esx/comment-page-1/#comment-4389</link>
		<dc:creator>jimheuton</dc:creator>
		<pubDate>Thu, 27 Aug 2009 15:12:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=2368#comment-4389</guid>
		<description>Does iSCSI multipathing require the new Enterprise Plus license?</description>
		<content:encoded><![CDATA[<p>Does iSCSI multipathing require the new Enterprise Plus license?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Duncan</title>
		<link>http://www.yellow-bricks.com/2009/03/18/iscsi-multipathing-with-esxcliexploring-the-next-version-of-esx/comment-page-1/#comment-4135</link>
		<dc:creator>Duncan</dc:creator>
		<pubDate>Wed, 29 Jul 2009 18:56:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=2368#comment-4135</guid>
		<description>they seem to be working here perfectly</description>
		<content:encoded><![CDATA[<p>they seem to be working here perfectly</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: onojdnob</title>
		<link>http://www.yellow-bricks.com/2009/03/18/iscsi-multipathing-with-esxcliexploring-the-next-version-of-esx/comment-page-1/#comment-4134</link>
		<dc:creator>onojdnob</dc:creator>
		<pubDate>Wed, 29 Jul 2009 18:11:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=2368#comment-4134</guid>
		<description>Could you please checl/update your image links? I think they&#039;re broken.</description>
		<content:encoded><![CDATA[<p>Could you please checl/update your image links? I think they&#8217;re broken.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ascheale</title>
		<link>http://www.yellow-bricks.com/2009/03/18/iscsi-multipathing-with-esxcliexploring-the-next-version-of-esx/comment-page-1/#comment-4090</link>
		<dc:creator>ascheale</dc:creator>
		<pubDate>Thu, 23 Jul 2009 10:24:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.yellow-bricks.com/?p=2368#comment-4090</guid>
		<description>Sorry, didn´t read it to the end</description>
		<content:encoded><![CDATA[<p>Sorry, didn´t read it to the end</p>
]]></content:encoded>
	</item>
</channel>
</rss>
