<?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: linux Redhat Cluster Suite in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/linux-redhat-cluster-suite/m-p/3712003#M21371</link>
    <description>I'm not sure you can, but will look into it.&lt;BR /&gt;&lt;BR /&gt;Good luck.&lt;BR /&gt;&lt;BR /&gt;Countdown=3&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Thu, 19 Jan 2006 08:43:51 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2006-01-19T08:43:51Z</dc:date>
    <item>
      <title>linux Redhat Cluster Suite</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-redhat-cluster-suite/m-p/3711999#M21367</link>
      <description>hi all,&lt;BR /&gt;can anyone tell me how to change the default behavior of cluster suite in case of loss of connectivity with shared partitions/media.&lt;BR /&gt;default action is reboot, but i read that is possible to configure stop/ignore/halt&lt;BR /&gt;&lt;BR /&gt;Any suggestions,&lt;BR /&gt;thanks</description>
      <pubDate>Wed, 18 Jan 2006 07:01:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-redhat-cluster-suite/m-p/3711999#M21367</guid>
      <dc:creator>Marco_113</dc:creator>
      <dc:date>2006-01-18T07:01:13Z</dc:date>
    </item>
    <item>
      <title>Re: linux Redhat Cluster Suite</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-redhat-cluster-suite/m-p/3712000#M21368</link>
      <description>Hi&lt;BR /&gt;Assuming you are using redhat  try this:&lt;BR /&gt;system-config-cluster &lt;BR /&gt;or &lt;BR /&gt;Select Main Menu =&amp;gt; System Settings =&amp;gt; Server Settings =&amp;gt; Cluster&lt;BR /&gt;&lt;BR /&gt;Hope this will help you in achieving ur goal.&lt;BR /&gt;&lt;BR /&gt;Cheers</description>
      <pubDate>Wed, 18 Jan 2006 07:49:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-redhat-cluster-suite/m-p/3712000#M21368</guid>
      <dc:creator>Vipulinux</dc:creator>
      <dc:date>2006-01-18T07:49:06Z</dc:date>
    </item>
    <item>
      <title>Re: linux Redhat Cluster Suite</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-redhat-cluster-suite/m-p/3712001#M21369</link>
      <description>Shalom Marco,&lt;BR /&gt;&lt;BR /&gt;The default behavior of the cluster is reboot for a reason. The reason is to prevent possible scenarios where two machines are trying to mount and change data in the shared data area.&lt;BR /&gt;&lt;BR /&gt;Such a scenario is  a disaster waiting to happen.&lt;BR /&gt;&lt;BR /&gt;One one of the nodes is supposed to boot. If they are both booting, here is a handly checklist from our exerpience:&lt;BR /&gt;&lt;BR /&gt;1) Make sure qlogic or equivalent fiber drivers are latest version and installed correctly.&lt;BR /&gt;2) If its an hp server, get san surfer for configuring the shared data. Install it on both nodes.&lt;BR /&gt;3) See that the firmware is the same and up to date on both shared storage controllers, if there are two. &lt;BR /&gt;&lt;BR /&gt;4) Make sure every driver that deals with shared storage, fiber card, controller, shared storage unit is consistent and the same version on redundant components.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 18 Jan 2006 13:51:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-redhat-cluster-suite/m-p/3712001#M21369</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-01-18T13:51:59Z</dc:date>
    </item>
    <item>
      <title>Re: linux Redhat Cluster Suite</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-redhat-cluster-suite/m-p/3712002#M21370</link>
      <description>Thanks for replying.&lt;BR /&gt;Sep, i've no problem with my configuration... All works fine.&lt;BR /&gt;&lt;BR /&gt;My question was only to understand how eventually change (because on the manual i read it is possible but not how to do it) the default behavior, for example to stop the cluster (and switch on the other node) not to reboot. I'm not going to change it...&lt;BR /&gt;&lt;BR /&gt;I know that reboot is the best and the right behavior.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 19 Jan 2006 04:49:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-redhat-cluster-suite/m-p/3712002#M21370</guid>
      <dc:creator>Marco_113</dc:creator>
      <dc:date>2006-01-19T04:49:05Z</dc:date>
    </item>
    <item>
      <title>Re: linux Redhat Cluster Suite</title>
      <link>https://community.hpe.com/t5/operating-system-linux/linux-redhat-cluster-suite/m-p/3712003#M21371</link>
      <description>I'm not sure you can, but will look into it.&lt;BR /&gt;&lt;BR /&gt;Good luck.&lt;BR /&gt;&lt;BR /&gt;Countdown=3&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 19 Jan 2006 08:43:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/linux-redhat-cluster-suite/m-p/3712003#M21371</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-01-19T08:43:51Z</dc:date>
    </item>
  </channel>
</rss>

