<?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: SG two node cluster - startup(boot) in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-two-node-cluster-startup-boot/m-p/4348359#M537840</link>
    <description>&lt;BR /&gt;check for a /etc/rc.config.d/cmcluster &lt;BR /&gt;   or something like that with the AUTOSTART_CMCLD variable.&lt;BR /&gt;&lt;BR /&gt;I forget what the path is on linux.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;script that starts serviceguard at boot time where the node will join a existing clsuter.</description>
    <pubDate>Sat, 31 Jan 2009 00:42:42 GMT</pubDate>
    <dc:creator>Emil Velez</dc:creator>
    <dc:date>2009-01-31T00:42:42Z</dc:date>
    <item>
      <title>SG two node cluster - startup(boot)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-two-node-cluster-startup-boot/m-p/4348356#M537837</link>
      <description>Hi! We are running 2 node serviceguard linux cluster (SLES). Suppose this scenario:&lt;BR /&gt;One node fail for a long time. Packages are fail over to second node. This works OK.  &lt;BR /&gt;Now I am going to reboot second node. After reboot the cluster is not running. I can start it using cmruncl -n node2. &lt;BR /&gt;Is there any solutions to form cluster automatic - without manual intervention. (cmcluster.rc AUTOSTART_CMCLD=1). &lt;BR /&gt;Perhaps I must delete failing node from configuration? Is there more elegant solution. Thank's!&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 30 Jan 2009 11:06:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sg-two-node-cluster-startup-boot/m-p/4348356#M537837</guid>
      <dc:creator>edi_4</dc:creator>
      <dc:date>2009-01-30T11:06:34Z</dc:date>
    </item>
    <item>
      <title>Re: SG two node cluster - startup(boot)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-two-node-cluster-startup-boot/m-p/4348357#M537838</link>
      <description>if a failed node is down and is likely to stay down for a long time, then yes it can make sense to delete it from the cluster configuration.&lt;BR /&gt;&lt;BR /&gt;this is because initial cluster formation can *only* occur when all cluster nodes are present. if you think about it, this makes sense as otherwise the cluster isn't aware of whether a node has failed or whether it has just lost communication. you need to avoid split brain situations, so this rule is always the case.&lt;BR /&gt;&lt;BR /&gt;don't get tempted to code the "cmruncl -n node2" into a startup script - that would be a *very* bad idea!&lt;BR /&gt;&lt;BR /&gt;HTH&lt;BR /&gt;&lt;BR /&gt;Duncan</description>
      <pubDate>Fri, 30 Jan 2009 12:07:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sg-two-node-cluster-startup-boot/m-p/4348357#M537838</guid>
      <dc:creator>Duncan Edmonstone</dc:creator>
      <dc:date>2009-01-30T12:07:31Z</dc:date>
    </item>
    <item>
      <title>Re: SG two node cluster - startup(boot)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-two-node-cluster-startup-boot/m-p/4348358#M537839</link>
      <description>If the failed node will be out of commission for an extended period and you want the running (functional) node to be able to auto-start Serviceguard at boot time, then you must remove the down node from the cluster.  You can do that by removing all references to the down node in the package configuration file(s) and the cluster configuration file (comment the references out for now).  Then run cmapplyconf on ALL the configuration files at the same time.  eg:&lt;BR /&gt;&lt;BR /&gt;# cmapplyconf -f -v -C &lt;CLUSTER.ASCII&gt; -P &lt;PKG1.ASCII&gt; -P &lt;PKG2.ASCII&gt; ...&lt;BR /&gt;&lt;BR /&gt;After the cluster is reconfigured down to a 1-node cluster, the remaining node should auto-start the cluster at boot time because there are no other nodes it will be waiting on to join with.&lt;/PKG2.ASCII&gt;&lt;/PKG1.ASCII&gt;&lt;/CLUSTER.ASCII&gt;</description>
      <pubDate>Fri, 30 Jan 2009 14:05:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sg-two-node-cluster-startup-boot/m-p/4348358#M537839</guid>
      <dc:creator>Stephen Doud</dc:creator>
      <dc:date>2009-01-30T14:05:46Z</dc:date>
    </item>
    <item>
      <title>Re: SG two node cluster - startup(boot)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-two-node-cluster-startup-boot/m-p/4348359#M537840</link>
      <description>&lt;BR /&gt;check for a /etc/rc.config.d/cmcluster &lt;BR /&gt;   or something like that with the AUTOSTART_CMCLD variable.&lt;BR /&gt;&lt;BR /&gt;I forget what the path is on linux.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;script that starts serviceguard at boot time where the node will join a existing clsuter.</description>
      <pubDate>Sat, 31 Jan 2009 00:42:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sg-two-node-cluster-startup-boot/m-p/4348359#M537840</guid>
      <dc:creator>Emil Velez</dc:creator>
      <dc:date>2009-01-31T00:42:42Z</dc:date>
    </item>
    <item>
      <title>Re: SG two node cluster - startup(boot)</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/sg-two-node-cluster-startup-boot/m-p/4348360#M537841</link>
      <description>Thank's for answers. I came from Tru64 - there is a litle diference... If I can understand I have to delete failed member from configuration in order to form cluster on boot, there are not other solutions. Yhank you!</description>
      <pubDate>Mon, 02 Feb 2009 06:53:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/sg-two-node-cluster-startup-boot/m-p/4348360#M537841</guid>
      <dc:creator>edi_4</dc:creator>
      <dc:date>2009-02-02T06:53:06Z</dc:date>
    </item>
  </channel>
</rss>

