<?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 disable TOC reboot in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/disable-toc-reboot/m-p/3844636#M57276</link>
    <description>Is there a way to disable the TOC reboot of a node if it loses communication with the cluster?  I want to troubleshoot communication problems of a test cluster, there is no shared storage so no risk of split brain and data corruption.  NODE_TOC_BEHAVIOR in cmcluster.rc defaults to reboot, the only other option I see is panic.</description>
    <pubDate>Wed, 16 Aug 2006 10:34:46 GMT</pubDate>
    <dc:creator>John Maki</dc:creator>
    <dc:date>2006-08-16T10:34:46Z</dc:date>
    <item>
      <title>disable TOC reboot</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disable-toc-reboot/m-p/3844636#M57276</link>
      <description>Is there a way to disable the TOC reboot of a node if it loses communication with the cluster?  I want to troubleshoot communication problems of a test cluster, there is no shared storage so no risk of split brain and data corruption.  NODE_TOC_BEHAVIOR in cmcluster.rc defaults to reboot, the only other option I see is panic.</description>
      <pubDate>Wed, 16 Aug 2006 10:34:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disable-toc-reboot/m-p/3844636#M57276</guid>
      <dc:creator>John Maki</dc:creator>
      <dc:date>2006-08-16T10:34:46Z</dc:date>
    </item>
    <item>
      <title>Re: disable TOC reboot</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disable-toc-reboot/m-p/3844637#M57277</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;No.&lt;BR /&gt;&lt;BR /&gt;TOC is critical to prevent split brain syndrome corrupting your shared data.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 16 Aug 2006 13:30:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disable-toc-reboot/m-p/3844637#M57277</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-08-16T13:30:03Z</dc:date>
    </item>
    <item>
      <title>Re: disable TOC reboot</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disable-toc-reboot/m-p/3844638#M57278</link>
      <description>Hi John,&lt;BR /&gt;&lt;BR /&gt;To troubleshoot communication problems, instead of trying to deactivate TOC, you may try tcpdump or any other IP traffic sniffer (Ethereal, ...)&lt;BR /&gt;&lt;BR /&gt;Good lcuk.&lt;BR /&gt;Kodjo</description>
      <pubDate>Wed, 16 Aug 2006 17:26:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disable-toc-reboot/m-p/3844638#M57278</guid>
      <dc:creator>Kodjo Agbenu</dc:creator>
      <dc:date>2006-08-16T17:26:33Z</dc:date>
    </item>
    <item>
      <title>Re: disable TOC reboot</title>
      <link>https://community.hpe.com/t5/operating-system-linux/disable-toc-reboot/m-p/3844639#M57279</link>
      <description>Those that you see are the only two options.  With the panic you should be able to set up a dump.</description>
      <pubDate>Thu, 17 Aug 2006 08:18:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/disable-toc-reboot/m-p/3844639#M57279</guid>
      <dc:creator>Serviceguard for Linux</dc:creator>
      <dc:date>2006-08-17T08:18:10Z</dc:date>
    </item>
  </channel>
</rss>

