<?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 Re: Failure scenario with arbiter in HPE SimpliVity</title>
    <link>https://community.hpe.com/t5/hpe-simplivity/failure-scenario-with-arbiter/m-p/7101509#M1785</link>
    <description>&lt;P&gt;By the way, what about returning to a nominal situation ? Does it mean that to get back the ESXi working the failed nodes and arbiter must be back online to allow the "surviving" node working Read / Write or is there a&amp;nbsp; solution to allow the last node to be able to work ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;If Node and arbiter are down for 3 days the last runing node in Read Only can be set to RW by the support ?&lt;/P&gt;&lt;P&gt;Hope to be clear.&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;</description>
    <pubDate>Wed, 16 Sep 2020 08:59:04 GMT</pubDate>
    <dc:creator>J-Philippe</dc:creator>
    <dc:date>2020-09-16T08:59:04Z</dc:date>
    <item>
      <title>Failure scenario with arbiter</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/failure-scenario-with-arbiter/m-p/7100969#M1770</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;&lt;P&gt;knowing that article from vmware :&amp;nbsp;&lt;A href="https://kb.vmware.com/s/article/51462" target="_blank"&gt;https://kb.vmware.com/s/article/51462&lt;/A&gt;&lt;/P&gt;&lt;P&gt;But what happen in the following scenario (sur that BP is to have arbiter on a third site) :&lt;/P&gt;&lt;P&gt;Server 1 in site A&lt;/P&gt;&lt;P&gt;Server 2 in site B&lt;/P&gt;&lt;P&gt;Arbiter in site B&lt;/P&gt;&lt;P&gt;If site B is isolated from A, VM continue to run on server 2 in B, and VM that were on&amp;nbsp; server 1 in A are restared on B site, correct ?&lt;/P&gt;&lt;P&gt;If site B is lost (server 2 and arbiter down) what happen to site A ? I suppose that A will be in Data Unavailability because not able to reach Server 1 and Arbiter in B, correct ?&lt;/P&gt;&lt;P&gt;Thanks for your help,&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;Jean-Philippe&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 11 Sep 2020 09:47:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/failure-scenario-with-arbiter/m-p/7100969#M1770</guid>
      <dc:creator>J-Philippe</dc:creator>
      <dc:date>2020-09-11T09:47:02Z</dc:date>
    </item>
    <item>
      <title>Re: Failure scenario with arbiter</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/failure-scenario-with-arbiter/m-p/7101014#M1771</link>
      <description>&lt;P&gt;Correct. The nodes in Site A will go "Read Only", because they will believe they have been isolated from the network (unable to contact other nodes, unable to contact Arbiter).&lt;/P&gt;&lt;P&gt;That's why it is important to have the Arbiter in a third site (which coudl eb the cloud if your latency is low)&lt;/P&gt;&lt;P&gt;Note that the Arbiter can be moved , so if necessary, you can deploy it in Site A or B in order to get everythig running - just don't forget to move it to a third site to make the cluster fully fault tolerant &amp;lt;g&amp;gt;.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Sep 2020 14:29:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/failure-scenario-with-arbiter/m-p/7101014#M1771</guid>
      <dc:creator>JohnHHaines</dc:creator>
      <dc:date>2020-09-11T14:29:15Z</dc:date>
    </item>
    <item>
      <title>Re: Failure scenario with arbiter</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/failure-scenario-with-arbiter/m-p/7101159#M1773</link>
      <description>&lt;P&gt;Thank you John.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Sep 2020 08:19:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/failure-scenario-with-arbiter/m-p/7101159#M1773</guid>
      <dc:creator>J-Philippe</dc:creator>
      <dc:date>2020-09-14T08:19:08Z</dc:date>
    </item>
    <item>
      <title>Re: Failure scenario with arbiter</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/failure-scenario-with-arbiter/m-p/7101509#M1785</link>
      <description>&lt;P&gt;By the way, what about returning to a nominal situation ? Does it mean that to get back the ESXi working the failed nodes and arbiter must be back online to allow the "surviving" node working Read / Write or is there a&amp;nbsp; solution to allow the last node to be able to work ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;If Node and arbiter are down for 3 days the last runing node in Read Only can be set to RW by the support ?&lt;/P&gt;&lt;P&gt;Hope to be clear.&lt;/P&gt;&lt;P&gt;Thanks for your help.&lt;/P&gt;</description>
      <pubDate>Wed, 16 Sep 2020 08:59:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/failure-scenario-with-arbiter/m-p/7101509#M1785</guid>
      <dc:creator>J-Philippe</dc:creator>
      <dc:date>2020-09-16T08:59:04Z</dc:date>
    </item>
    <item>
      <title>Re: Failure scenario with arbiter</title>
      <link>https://community.hpe.com/t5/hpe-simplivity/failure-scenario-with-arbiter/m-p/7104205#M1862</link>
      <description>&lt;P&gt;Case 1 : If DRS is manual ; VM's needs to be manually migrated to the compute of Site A while storage continues to stay in the existing NFS.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Case 2 : If DRS is partial /fully automated ; VM's will continue to stay on the compute of site B or migrate to the compute of site A based on the DRS rules.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Arbiter : Arbiter has no role play in VM's or OVC failback.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Oct 2020 12:15:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-simplivity/failure-scenario-with-arbiter/m-p/7104205#M1862</guid>
      <dc:creator>Shivam1</dc:creator>
      <dc:date>2020-10-08T12:15:11Z</dc:date>
    </item>
  </channel>
</rss>

