<?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: Heartbeat messages in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/heartbeat-messages/m-p/2972655#M710040</link>
    <description>The HB messages are sent in parallel using all configured HB networks. Of course, the cluster is happy to get messages through at least one of the paths.&lt;BR /&gt;&lt;BR /&gt;Best regards...&lt;BR /&gt; Dietmar.</description>
    <pubDate>Wed, 14 May 2003 07:20:13 GMT</pubDate>
    <dc:creator>Dietmar Konermann</dc:creator>
    <dc:date>2003-05-14T07:20:13Z</dc:date>
    <item>
      <title>Heartbeat messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/heartbeat-messages/m-p/2972654#M710039</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I'm configuring several Heartbeat pathes (one dedicated with small hub and one through the network) in order to prevent from SPOF.&lt;BR /&gt;&lt;BR /&gt;NODE_NAME               ftsys9&lt;BR /&gt;  NETWORK_INTERFACE     lan0&lt;BR /&gt;    HEARTBEAT_IP   15.13.171.32&lt;BR /&gt;  NETWORK_INTERFACE     lan3&lt;BR /&gt;    HEARTBEAT_IP   192.6.7.3&lt;BR /&gt;&lt;BR /&gt;But I wonder if HB messages are sent to both ways simultaneously (lan0 and lan3) or if one way (f.e. dedicated one - lan0) is primary and the other one (lan3) secondary ??&lt;BR /&gt;&lt;BR /&gt;Are Heartbeat messages working in active/standby mode ??</description>
      <pubDate>Wed, 14 May 2003 06:55:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/heartbeat-messages/m-p/2972654#M710039</guid>
      <dc:creator>a8965</dc:creator>
      <dc:date>2003-05-14T06:55:25Z</dc:date>
    </item>
    <item>
      <title>Re: Heartbeat messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/heartbeat-messages/m-p/2972655#M710040</link>
      <description>The HB messages are sent in parallel using all configured HB networks. Of course, the cluster is happy to get messages through at least one of the paths.&lt;BR /&gt;&lt;BR /&gt;Best regards...&lt;BR /&gt; Dietmar.</description>
      <pubDate>Wed, 14 May 2003 07:20:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/heartbeat-messages/m-p/2972655#M710040</guid>
      <dc:creator>Dietmar Konermann</dc:creator>
      <dc:date>2003-05-14T07:20:13Z</dc:date>
    </item>
    <item>
      <title>Re: Heartbeat messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/heartbeat-messages/m-p/2972656#M710041</link>
      <description>Hi Dietmar&lt;BR /&gt;&lt;BR /&gt;is right ... I hope you are&lt;BR /&gt;not under the impression that&lt;BR /&gt;lan3 can be used as a standy&lt;BR /&gt;for lan0 in the configuration&lt;BR /&gt;you sent ...&lt;BR /&gt;The main data standby lan has&lt;BR /&gt;to be unconfigured in order to be used by MCSG.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Christos</description>
      <pubDate>Thu, 15 May 2003 08:11:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/heartbeat-messages/m-p/2972656#M710041</guid>
      <dc:creator>Christos Magdalinos</dc:creator>
      <dc:date>2003-05-15T08:11:16Z</dc:date>
    </item>
    <item>
      <title>Re: Heartbeat messages</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/heartbeat-messages/m-p/2972657#M710042</link>
      <description>Very good question.  To the best of my knowledge MC/SG has always just provided one primary heartbeat for signaling.  Use 'cmverify -v' or 'cmscancl -o file' for this.&lt;BR /&gt;&lt;BR /&gt;Having two LANs designated as heartbeat LANs within the cluster.ascii file is an indication that they qualified during the creation of the cluster binary.  'cmquerycl' performs this qualifying.  &lt;BR /&gt;&lt;BR /&gt;There are disasters to test for during your failover testing after the cluster has been created.  You should be pulling LAN cables as a part of this testing to see how the primary heartbeat LAN is picked up by the standby heartbeat LAN.  Again, use 'cmviewcl -v' and 'cmscancl -o file' for this.&lt;BR /&gt;&lt;BR /&gt;This URL gives a nice example.  Please ignore the SAM references.  I'm not advocating that you use SAM for this, in fact, just the contrary.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B3936-90053/B3936-90053_top.html&amp;amp;con=/hpux/onlinedocs/B3936-90053/00/00/36-con.html&amp;amp;toc=/hpux/onlinedocs/B3936-90053/00/00/36-toc.html&amp;amp;searchterms=heartbeat%7ccmquerycl%7ccluster&amp;amp;queryid=20030515-054222" target="_blank"&gt;http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B3936-90053/B3936-90053_top.html&amp;amp;con=/hpux/onlinedocs/B3936-90053/00/00/36-con.html&amp;amp;toc=/hpux/onlinedocs/B3936-90053/00/00/36-toc.html&amp;amp;searchterms=heartbeat%7ccmquerycl%7ccluster&amp;amp;queryid=20030515-054222&lt;/A&gt;</description>
      <pubDate>Thu, 15 May 2003 10:50:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/heartbeat-messages/m-p/2972657#M710042</guid>
      <dc:creator>Michael Steele_2</dc:creator>
      <dc:date>2003-05-15T10:50:19Z</dc:date>
    </item>
  </channel>
</rss>

