<?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: toc in cluster nodes in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/toc-in-cluster-nodes/m-p/3790133#M698206</link>
    <description>Hi Shiv:&lt;BR /&gt;&lt;BR /&gt;Yes, in a 2-node cluster, failure to detect a heart-beat will result in one node undergoing a TOC (Transfer-of-Control, or reboot) thereby allowing the remaining node to acquire all resources and packages.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
    <pubDate>Wed, 17 May 2006 19:47:46 GMT</pubDate>
    <dc:creator>James R. Ferguson</dc:creator>
    <dc:date>2006-05-17T19:47:46Z</dc:date>
    <item>
      <title>toc in cluster nodes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/toc-in-cluster-nodes/m-p/3790132#M698205</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;In case of 2 cluster nodes if a node develope some problem then is it desirable if one node goes for TOC ?&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Shiv&lt;BR /&gt;</description>
      <pubDate>Wed, 17 May 2006 19:32:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/toc-in-cluster-nodes/m-p/3790132#M698205</guid>
      <dc:creator>Shivkumar</dc:creator>
      <dc:date>2006-05-17T19:32:54Z</dc:date>
    </item>
    <item>
      <title>Re: toc in cluster nodes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/toc-in-cluster-nodes/m-p/3790133#M698206</link>
      <description>Hi Shiv:&lt;BR /&gt;&lt;BR /&gt;Yes, in a 2-node cluster, failure to detect a heart-beat will result in one node undergoing a TOC (Transfer-of-Control, or reboot) thereby allowing the remaining node to acquire all resources and packages.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Wed, 17 May 2006 19:47:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/toc-in-cluster-nodes/m-p/3790133#M698206</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2006-05-17T19:47:46Z</dc:date>
    </item>
    <item>
      <title>Re: toc in cluster nodes</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/toc-in-cluster-nodes/m-p/3790134#M698207</link>
      <description>It depends upon the nature of the problem but as has already been said if no heartbeat is detected then one of the nodes should die -- otherwise, imagine both nodes trying to activate the same VG and mount filesystems. Also on a two-node cluster you now do not node have quorum and this is why a 2-node cluster must use a quorum server or lock disk -- to avoid split-brain syndrome.  On the other hand if a simple disk failure occurred (possibly the boot disk) then this should be a complete non-event on either node and even the node with the failed disk shouldn't care because I'm sure that you mirrored it. Right?</description>
      <pubDate>Wed, 17 May 2006 23:09:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/toc-in-cluster-nodes/m-p/3790134#M698207</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2006-05-17T23:09:45Z</dc:date>
    </item>
  </channel>
</rss>

