<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Multipathing status changed in StoreVirtual Storage</title>
    <link>https://community.hpe.com/t5/storevirtual-storage/multipathing-status-changed/m-p/6329267#M7872</link>
    <description>&lt;P&gt;We're been running an 8 node multi-site Lefthand solution for some time now and when it was originally set up a lot of time was taken configuring the multi-pathing to ensure we had full redundancy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't know where but somewhere along the line this has changed and when I check the datastore status now it's showing as 'Partial/No Redundancy' for all volumes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this expected? &amp;nbsp;Or more imporantly is there a way to get back to Full Redundancy?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I suspect the change occurred when we upgraded vSphere from v4.1 to v5.0. &amp;nbsp;We're now running v5.1 and have 3 VMKernel adapters bound to the iSCSI Software Adapter.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm guessing (but would appreciate confirmation) that the system considers us to only have partial redundancy because we're still ultimately dependent on a SPOF which would be the iSCSI Software Adapter.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Grateful for any comments on this one.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pete&lt;/P&gt;</description>
    <pubDate>Thu, 09 Jan 2014 11:33:49 GMT</pubDate>
    <dc:creator>Peter J West</dc:creator>
    <dc:date>2014-01-09T11:33:49Z</dc:date>
    <item>
      <title>Multipathing status changed</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/multipathing-status-changed/m-p/6329267#M7872</link>
      <description>&lt;P&gt;We're been running an 8 node multi-site Lefthand solution for some time now and when it was originally set up a lot of time was taken configuring the multi-pathing to ensure we had full redundancy.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don't know where but somewhere along the line this has changed and when I check the datastore status now it's showing as 'Partial/No Redundancy' for all volumes.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is this expected? &amp;nbsp;Or more imporantly is there a way to get back to Full Redundancy?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I suspect the change occurred when we upgraded vSphere from v4.1 to v5.0. &amp;nbsp;We're now running v5.1 and have 3 VMKernel adapters bound to the iSCSI Software Adapter.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm guessing (but would appreciate confirmation) that the system considers us to only have partial redundancy because we're still ultimately dependent on a SPOF which would be the iSCSI Software Adapter.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Grateful for any comments on this one.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Pete&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jan 2014 11:33:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/multipathing-status-changed/m-p/6329267#M7872</guid>
      <dc:creator>Peter J West</dc:creator>
      <dc:date>2014-01-09T11:33:49Z</dc:date>
    </item>
    <item>
      <title>Re: Multipathing status changed</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/multipathing-status-changed/m-p/6329495#M7873</link>
      <description>&lt;P&gt;are you targeting the VIP of the cluster for your LUNs? &amp;nbsp;If so, you should have all the redundancy required since any node that fails while it is acting as an individual LUN target will automatically failover to the next available node. &amp;nbsp;It really shouldn't take a lot of time to setup the SAN specifically "for redundancy" unless you are talking about many LUNs on many servers which is time consuming just because of the quantity. &amp;nbsp;I"m a hyper-V shop so I won't speak about the specifics of how to setup the ESX hosts, but if you read the setup guide for ESX+StoreVirtual it really doesn't take that much to get it correct/redundant. &amp;nbsp;Now, it might be that ESX is just reporting non-redundant because it only things you are connecte to a single IP and it assumes a single IP is not a clustered SAN and that is why its giving you a warning and then I bet it probably can be ignored.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Jan 2014 14:31:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/multipathing-status-changed/m-p/6329495#M7873</guid>
      <dc:creator>oikjn</dc:creator>
      <dc:date>2014-01-09T14:31:37Z</dc:date>
    </item>
  </channel>
</rss>

