<?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: Peer Persistance switchover, iscsi timeout in Array Performance and Data Protection</title>
    <link>https://community.hpe.com/t5/array-performance-and-data/peer-persistance-switchover-iscsi-timeout/m-p/7111024#M1337</link>
    <description>&lt;P&gt;Hi Nick,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanck you for response.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ok for "IO pause".&lt;/P&gt;&lt;P&gt;For "teaming" the iSCSI and Group interfaces, can i do it without redeploing the arrays?&lt;/P&gt;&lt;P&gt;Just add VLAN tag for 10Gbits interfaces at the same time as changing switch port configuration?&lt;/P&gt;&lt;P&gt;I can stop the host's IO, the arrays is not in production yet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;</description>
    <pubDate>Fri, 27 Nov 2020 18:09:35 GMT</pubDate>
    <dc:creator>Major88</dc:creator>
    <dc:date>2020-11-27T18:09:35Z</dc:date>
    <item>
      <title>Peer Persistance switchover, iscsi timeout</title>
      <link>https://community.hpe.com/t5/array-performance-and-data/peer-persistance-switchover-iscsi-timeout/m-p/7111009#M1335</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I am novice in Nimble solution storage.&lt;/P&gt;&lt;P&gt;I want to know if my configuration is correct for have a peer persitance and automatic switch over.&lt;/P&gt;&lt;P&gt;We have two AF20 with 2 10Gbit/s/ sfp+ ports per controller. ie. 4 per array for Data ang group trafic&lt;/P&gt;&lt;P&gt;and 2 10Gbit/s BaseT per controller for management.&lt;/P&gt;&lt;P&gt;The 1st port SFP+ of each controler reserved for iSCSI&amp;nbsp; - single subnet&lt;/P&gt;&lt;P&gt;and 2nd SFP+ is reseved for Group synch - single subnet&lt;/P&gt;&lt;P&gt;The arrays are installed in two sites and linked by 20gbits/s fibre&lt;/P&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Clip2net_201127161250.png" style="width: 1067px;"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/120009i431379FE89B62511/image-size/large?v=v2&amp;amp;px=2000" role="button" title="Clip2net_201127161250.png" alt="Clip2net_201127161250.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;When I test the ASO, the VMs is locked for 30-50 seconds before Nimble can deliver IOs, is it a normal situation or not?&lt;/P&gt;</description>
      <pubDate>Fri, 27 Nov 2020 15:21:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-performance-and-data/peer-persistance-switchover-iscsi-timeout/m-p/7111009#M1335</guid>
      <dc:creator>Major88</dc:creator>
      <dc:date>2020-11-27T15:21:39Z</dc:date>
    </item>
    <item>
      <title>Re: Peer Persistance switchover, iscsi timeout</title>
      <link>https://community.hpe.com/t5/array-performance-and-data/peer-persistance-switchover-iscsi-timeout/m-p/7111018#M1336</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;when performing some kind of failover across sites, it's commonplace to have an IO pause in order to ensure that:&lt;/P&gt;
&lt;P&gt;a) data doesn't get corrupted&lt;BR /&gt;b) you don't experience "split brain" with both sites thinking they're active due to a temporary outage.&lt;BR /&gt;c) your VMs don't get destroyed or corrupted&lt;/P&gt;
&lt;P&gt;Therefore 30-50 seconds of IO pause (NOT timeout) is expected and normal.&lt;/P&gt;
&lt;P&gt;However - i must warn you on your network configuration. Only having a single 10Gb port for your iSCSI data most likely is going to cause problems - as you have no resilliency in your network should something happen on your switch. And Peer Persistence will not failover should a switch fail. Your current network setup is deemed to be non-recommended, and will most likely cause issues somewhere down the line.&lt;/P&gt;
&lt;P&gt;Instead, run all four ports across both arrays trunked with both group and iSCSI data on different VLANs across those ports. this will give you the resilliency you need.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Nov 2020 17:02:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-performance-and-data/peer-persistance-switchover-iscsi-timeout/m-p/7111018#M1336</guid>
      <dc:creator>Nick_Dyer</dc:creator>
      <dc:date>2020-11-27T17:02:26Z</dc:date>
    </item>
    <item>
      <title>Re: Peer Persistance switchover, iscsi timeout</title>
      <link>https://community.hpe.com/t5/array-performance-and-data/peer-persistance-switchover-iscsi-timeout/m-p/7111024#M1337</link>
      <description>&lt;P&gt;Hi Nick,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanck you for response.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ok for "IO pause".&lt;/P&gt;&lt;P&gt;For "teaming" the iSCSI and Group interfaces, can i do it without redeploing the arrays?&lt;/P&gt;&lt;P&gt;Just add VLAN tag for 10Gbits interfaces at the same time as changing switch port configuration?&lt;/P&gt;&lt;P&gt;I can stop the host's IO, the arrays is not in production yet.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;</description>
      <pubDate>Fri, 27 Nov 2020 18:09:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-performance-and-data/peer-persistance-switchover-iscsi-timeout/m-p/7111024#M1337</guid>
      <dc:creator>Major88</dc:creator>
      <dc:date>2020-11-27T18:09:35Z</dc:date>
    </item>
    <item>
      <title>Re: Peer Persistance switchover, iscsi timeout</title>
      <link>https://community.hpe.com/t5/array-performance-and-data/peer-persistance-switchover-iscsi-timeout/m-p/7111026#M1338</link>
      <description>&lt;P&gt;Yessir, you can jump into the network configuration on the system and edit the setup to create VLANs on the NICs very easily. What's more, you can save the configuration as a draft - to ensure that maybe some networking folks check it over before you commit. Should you then commit and something not work - not a problem, you can restore the previous network configuration back.&lt;/P&gt;
&lt;P&gt;Please feel free to give Nimble Support a call whilst you're doing the changes - they'll be able to walk you through it too.&lt;/P&gt;
&lt;P&gt;Thank you for your custom and trust &lt;LI-EMOJI id="lia_slightly-smiling-face" title=":slightly_smiling_face:"&gt;&lt;/LI-EMOJI&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 27 Nov 2020 18:12:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/array-performance-and-data/peer-persistance-switchover-iscsi-timeout/m-p/7111026#M1338</guid>
      <dc:creator>Nick_Dyer</dc:creator>
      <dc:date>2020-11-27T18:12:27Z</dc:date>
    </item>
  </channel>
</rss>

