<?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 RedHat Linux High Availability add-on behaviour in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/redhat-linux-high-availability-add-on-behaviour/m-p/6348597#M58739</link>
    <description>&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;We are testing the RedHat High Availability add-on software with the Resilient storage add-on. We are having a slight issue:-&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We&amp;nbsp;have created a 2 node RedHat Linux cluster using virtual machines.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The cluster forms correctly, and the Global File system is fenced.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If&amp;nbsp;we now reboot the one system, the system leaves the cluster correctly, but it does not rejoin the cluster on boot up.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If they reset the node and boot, it joins the cluster correctly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If anybody can advise on why this should happen we would really appreaciate it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Andrew&lt;/P&gt;</description>
    <pubDate>Fri, 24 Jan 2014 10:39:15 GMT</pubDate>
    <dc:creator>A.W.R</dc:creator>
    <dc:date>2014-01-24T10:39:15Z</dc:date>
    <item>
      <title>RedHat Linux High Availability add-on behaviour</title>
      <link>https://community.hpe.com/t5/operating-system-linux/redhat-linux-high-availability-add-on-behaviour/m-p/6348597#M58739</link>
      <description>&lt;P&gt;HI,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;We are testing the RedHat High Availability add-on software with the Resilient storage add-on. We are having a slight issue:-&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We&amp;nbsp;have created a 2 node RedHat Linux cluster using virtual machines.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The cluster forms correctly, and the Global File system is fenced.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If&amp;nbsp;we now reboot the one system, the system leaves the cluster correctly, but it does not rejoin the cluster on boot up.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If they reset the node and boot, it joins the cluster correctly.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If anybody can advise on why this should happen we would really appreaciate it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Andrew&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jan 2014 10:39:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/redhat-linux-high-availability-add-on-behaviour/m-p/6348597#M58739</guid>
      <dc:creator>A.W.R</dc:creator>
      <dc:date>2014-01-24T10:39:15Z</dc:date>
    </item>
    <item>
      <title>Re: RedHat Linux High Availability add-on behaviour</title>
      <link>https://community.hpe.com/t5/operating-system-linux/redhat-linux-high-availability-add-on-behaviour/m-p/6355665#M58740</link>
      <description>&lt;P&gt;Which version of RHEL? 5.x? 6.x?&lt;/P&gt;&lt;P&gt;What kind of virtual machines? VMware? RHEV? Other?&lt;/P&gt;&lt;P&gt;Which fencing method are you using?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Have you verified that multicast works between the nodes?&lt;/P&gt;&lt;P&gt;Here are some tools and procedures for testing:&lt;/P&gt;&lt;P&gt;&lt;A target="_blank" href="https://access.redhat.com/site/articles/22304"&gt;https://access.redhat.com/site/articles/22304&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With some switches (e.g. Cisco), IGMP snooping will work correctly only if there is a source of IGMP queries in the network segment/VLAN. If there is no source of IGMP queries, cluster can form if two nodes are started simultaneously, but if one node is stopped and then restarted, it will fail to rejoin the cluster because the forwarding of multicast traffic between the switches will not be restarted.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;RedHat document:&lt;/P&gt;&lt;P&gt;&lt;A target="_blank" href="https://access.redhat.com/site/node/216463/40/0"&gt;https://access.redhat.com/site/node/216463/40/0&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cisco document:&lt;/P&gt;&lt;P&gt;&lt;A target="_blank" href="http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008059a9df.shtml"&gt;http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a008059a9df.shtml&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2014 12:17:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/redhat-linux-high-availability-add-on-behaviour/m-p/6355665#M58740</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2014-01-29T12:17:08Z</dc:date>
    </item>
  </channel>
</rss>

