<?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: Polyserve failover in Storage Software</title>
    <link>https://community.hpe.com/t5/storage-software/polyserve-failover/m-p/4367646#M367</link>
    <description>You would have to go into your clients and see if you can change the re-arp interval.</description>
    <pubDate>Sun, 22 Mar 2009 23:38:38 GMT</pubDate>
    <dc:creator>Emil Velez</dc:creator>
    <dc:date>2009-03-22T23:38:38Z</dc:date>
    <item>
      <title>Polyserve failover</title>
      <link>https://community.hpe.com/t5/storage-software/polyserve-failover/m-p/4367643#M364</link>
      <description>We've been using a two-node PolyServe Matrix Server cluster for NFS/Cifs hosting for a while now, on two linux hosts. Recently, we noticed that during some failovers of virtual IP's servicing NFS between nodes, some client systems would fail to see the NFS share for 1-5 minutes, as if they couldn't see the new location of the IP. Not the same system every time, and not always for the same amount of time, but it's happened twice so far.&lt;BR /&gt;Anyone else seen this? More importantly, how does the failover work? Is it just a gratuitous ARP like Heartbeat?</description>
      <pubDate>Thu, 26 Feb 2009 20:29:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storage-software/polyserve-failover/m-p/4367643#M364</guid>
      <dc:creator>jknightcs1</dc:creator>
      <dc:date>2009-02-26T20:29:52Z</dc:date>
    </item>
    <item>
      <title>Re: Polyserve failover</title>
      <link>https://community.hpe.com/t5/storage-software/polyserve-failover/m-p/4367644#M365</link>
      <description>&lt;BR /&gt;Depends on NFS client.  NFS client has to timeout and the re-arp the IP address.  So this is somehwhat totally depenent on the client and the timeout of ARP information in the cache.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Sat, 28 Feb 2009 01:03:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storage-software/polyserve-failover/m-p/4367644#M365</guid>
      <dc:creator>Emil Velez</dc:creator>
      <dc:date>2009-02-28T01:03:31Z</dc:date>
    </item>
    <item>
      <title>Re: Polyserve failover</title>
      <link>https://community.hpe.com/t5/storage-software/polyserve-failover/m-p/4367645#M366</link>
      <description>Any way to change that setting?</description>
      <pubDate>Mon, 02 Mar 2009 19:48:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storage-software/polyserve-failover/m-p/4367645#M366</guid>
      <dc:creator>jknightcs1</dc:creator>
      <dc:date>2009-03-02T19:48:35Z</dc:date>
    </item>
    <item>
      <title>Re: Polyserve failover</title>
      <link>https://community.hpe.com/t5/storage-software/polyserve-failover/m-p/4367646#M367</link>
      <description>You would have to go into your clients and see if you can change the re-arp interval.</description>
      <pubDate>Sun, 22 Mar 2009 23:38:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storage-software/polyserve-failover/m-p/4367646#M367</guid>
      <dc:creator>Emil Velez</dc:creator>
      <dc:date>2009-03-22T23:38:38Z</dc:date>
    </item>
  </channel>
</rss>

