<?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: Reboot Single Node in StoreVirtual Storage</title>
    <link>https://community.hpe.com/t5/storevirtual-storage/reboot-single-node/m-p/6908988#M10374</link>
    <description>&lt;P&gt;The short answer is, yes.&amp;nbsp; Just right click on the node in CMC and there should be a shutdown/reboot option.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd suggest that you change your LUNs from NR5 to NR10 as HP suggests NR5 for archive and read-only data.&lt;/P&gt;</description>
    <pubDate>Wed, 19 Oct 2016 12:51:53 GMT</pubDate>
    <dc:creator>oikjn</dc:creator>
    <dc:date>2016-10-19T12:51:53Z</dc:date>
    <item>
      <title>Reboot Single Node</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/reboot-single-node/m-p/6908853#M10373</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I have a four node p4500G2 cluster in NR5, LeftHand OS12 on each node and esxi 5.5 on the hosts. I discovered one of the nodes has the raid cache incorrectly set and is causing bad io latency.&lt;/P&gt;&lt;P&gt;Same issue as mention here;&lt;/P&gt;&lt;P&gt;&lt;A href="https://blog.mrpol.nl/2013/07/02/high-write-latency-on-hp-storevirtual-environment-with-vmware-vsphere-5-1/" target="_blank"&gt;https://blog.mrpol.nl/2013/07/02/high-write-latency-on-hp-storevirtual-environment-with-vmware-vsphere-5-1/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;My question is can i reboot the single node via the cmc so i can get into the cache settings without affecting the running vm's ?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 19 Oct 2016 04:14:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/reboot-single-node/m-p/6908853#M10373</guid>
      <dc:creator>Conky</dc:creator>
      <dc:date>2016-10-19T04:14:20Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Single Node</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/reboot-single-node/m-p/6908988#M10374</link>
      <description>&lt;P&gt;The short answer is, yes.&amp;nbsp; Just right click on the node in CMC and there should be a shutdown/reboot option.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd suggest that you change your LUNs from NR5 to NR10 as HP suggests NR5 for archive and read-only data.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Oct 2016 12:51:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/reboot-single-node/m-p/6908988#M10374</guid>
      <dc:creator>oikjn</dc:creator>
      <dc:date>2016-10-19T12:51:53Z</dc:date>
    </item>
    <item>
      <title>Re: Reboot Single Node</title>
      <link>https://community.hpe.com/t5/storevirtual-storage/reboot-single-node/m-p/6909605#M10379</link>
      <description>&lt;P&gt;Agree with &lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/1210971"&gt;@oikjn&lt;/a&gt; about changing to NW10 if you have a "normal" environment. &amp;nbsp;You will see a lot of latency using NW5 for writes. &amp;nbsp;However, if you do change to NR10, your total capacity will drop to 50% where currently it's 75% with a 4 node cluster.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 20 Oct 2016 20:24:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storevirtual-storage/reboot-single-node/m-p/6909605#M10379</guid>
      <dc:creator>CalvinZito</dc:creator>
      <dc:date>2016-10-20T20:24:32Z</dc:date>
    </item>
  </channel>
</rss>

