<?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: Primary and Standby Heartbeat IP in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379651#M671709</link>
    <description>I cannot find my answer in there.</description>
    <pubDate>Mon, 16 Mar 2009 06:26:55 GMT</pubDate>
    <dc:creator>Jason Ng Teng Po</dc:creator>
    <dc:date>2009-03-16T06:26:55Z</dc:date>
    <item>
      <title>Primary and Standby Heartbeat IP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379649#M671707</link>
      <description>Hi Guys,&lt;BR /&gt;&lt;BR /&gt;I'm going to implement MCSG on 2 node.&lt;BR /&gt;&lt;BR /&gt;For both primary and standby heartbeat IP, can both be on the same segment? See example below.&lt;BR /&gt;&lt;BR /&gt;Node1&lt;BR /&gt;Primary HB: 192.168.1.1&lt;BR /&gt;Standby HB: 192.168.1.2&lt;BR /&gt;&lt;BR /&gt;Node2&lt;BR /&gt;Primary HB: 192.168.1.3&lt;BR /&gt;Standby HB: 192.168.1.4&lt;BR /&gt;&lt;BR /&gt;Are they any impact on this if I implement it this way?</description>
      <pubDate>Mon, 16 Mar 2009 05:17:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379649#M671707</guid>
      <dc:creator>Jason Ng Teng Po</dc:creator>
      <dc:date>2009-03-16T05:17:34Z</dc:date>
    </item>
    <item>
      <title>Re: Primary and Standby Heartbeat IP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379650#M671708</link>
      <description>Hi Jason,&lt;BR /&gt;&lt;BR /&gt;Would recommend to take look below link&lt;BR /&gt;&lt;BR /&gt;Understanding and Designing Serviceguard Disaster Tolerant Architectures, 1st Edition, December 2006 HP-UX 11i v1, 11i v2 [ PDF ]  [ HTML ]  &lt;BR /&gt; &lt;BR /&gt;Understanding and Designing Serviceguard Disaster Tolerant Architectures, 3rd Edition, December 2007 HP-UX 11i v1, 11i v2, 11i v3 [ PDF ]  [ HTML ]  &lt;BR /&gt; &lt;BR /&gt;&lt;A href="http://docs.hp.com/en/ha.html#Serviceguard" target="_blank"&gt;http://docs.hp.com/en/ha.html#Serviceguard&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;JOhnson</description>
      <pubDate>Mon, 16 Mar 2009 05:29:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379650#M671708</guid>
      <dc:creator>Johnson Punniyalingam</dc:creator>
      <dc:date>2009-03-16T05:29:58Z</dc:date>
    </item>
    <item>
      <title>Re: Primary and Standby Heartbeat IP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379651#M671709</link>
      <description>I cannot find my answer in there.</description>
      <pubDate>Mon, 16 Mar 2009 06:26:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379651#M671709</guid>
      <dc:creator>Jason Ng Teng Po</dc:creator>
      <dc:date>2009-03-16T06:26:55Z</dc:date>
    </item>
    <item>
      <title>Re: Primary and Standby Heartbeat IP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379652#M671710</link>
      <description>Hi Jason,&lt;BR /&gt;&lt;BR /&gt;Check below link &lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1237191979480+28353475&amp;amp;threadId=122662" target="_blank"&gt;https://forums11.itrc.hp.com/service/forums/questionanswer.do?admit=109447626+1237191979480+28353475&amp;amp;threadId=122662&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Some info on configuring lan card &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/onlinedocs/B3936-90024/B3936-90024.html" target="_blank"&gt;http://docs.hp.com/hpux/onlinedocs/B3936-90024/B3936-90024.html&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;and HA FAQ.. &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://us-support.external.hp.com/iv/bin/doc.pl/sid=cc4d5bf606752687a6/screen=ivH" target="_blank"&gt;http://us-support.external.hp.com/iv/bin/doc.pl/sid=cc4d5bf606752687a6/screen=ivH&lt;/A&gt;&lt;BR /&gt;ome/?NODEID=English_SHW::WW_SW_UX_RCFAQ_EN_E/Q1.2&amp;amp;WARP=1 &lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Johnson</description>
      <pubDate>Mon, 16 Mar 2009 07:31:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379652#M671710</guid>
      <dc:creator>Johnson Punniyalingam</dc:creator>
      <dc:date>2009-03-16T07:31:38Z</dc:date>
    </item>
    <item>
      <title>Re: Primary and Standby Heartbeat IP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379653#M671711</link>
      <description>As long as the second nic is defined as the failover lan card, the primary IP will be bound to that NIC card upon failover. You can support multiple IP's on the same NIC but they have to be in the same subnet for that to work. &lt;BR /&gt;&lt;BR /&gt;Port aggregation &amp;amp; teaming software could work for you as well. &lt;BR /&gt;&lt;BR /&gt;By the way don't forget to put heartbeat's on each segment that is defined on your cluster. It helps with keeping up the pings. &lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Johnson</description>
      <pubDate>Mon, 16 Mar 2009 07:32:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379653#M671711</guid>
      <dc:creator>Johnson Punniyalingam</dc:creator>
      <dc:date>2009-03-16T07:32:58Z</dc:date>
    </item>
    <item>
      <title>Re: Primary and Standby Heartbeat IP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379654#M671712</link>
      <description>They can be on the same segment but it is better to have them as two distinct networks.&lt;BR /&gt;&lt;BR /&gt;If you switch fails with the 192.168.1.x network on it your whole cluster is down.&lt;BR /&gt;No failover to the other NIC.&lt;BR /&gt;&lt;BR /&gt;Advice:&lt;BR /&gt;two networks&lt;BR /&gt;two physical switches.</description>
      <pubDate>Mon, 16 Mar 2009 07:36:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379654#M671712</guid>
      <dc:creator>B. Hulst</dc:creator>
      <dc:date>2009-03-16T07:36:59Z</dc:date>
    </item>
    <item>
      <title>Re: Primary and Standby Heartbeat IP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379655#M671713</link>
      <description>Thanks Thanks&lt;BR /&gt;&lt;BR /&gt;BTW I won't be using switches for my heartbeat. I'm going to use cross-cables</description>
      <pubDate>Mon, 16 Mar 2009 07:41:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379655#M671713</guid>
      <dc:creator>Jason Ng Teng Po</dc:creator>
      <dc:date>2009-03-16T07:41:54Z</dc:date>
    </item>
    <item>
      <title>Re: Primary and Standby Heartbeat IP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379656#M671714</link>
      <description>1.) HP-UX in general gets very confused if you configure two separate NICs to use two IP addresses within the same network segment. This configuration is not supported. (It can be made to work, but this configuration can be unpredictable in failure situations. Not recommended for a HA environment.)&lt;BR /&gt;&lt;BR /&gt;2.) If your heartbeat goes through only one segment, there may be a Single Point of Failure: even one failed NIC sending a constant stream of garbage packets can block the entire segment, unless your network switches are smart enough to isolate a NIC with this type of fault on their own.&lt;BR /&gt;&lt;BR /&gt;Two heartbeat IP segments are obviously better than one. But if you can have only one, you might want to use APA or ServiceGuard's Local LAN Failover on the heartbeat NICs.&lt;BR /&gt;&lt;BR /&gt;With APA, you can join two NICs into an active/active "team", so both NICs are used for heartbeats, even though there is only one heartbeat IP address per node.&lt;BR /&gt;&lt;BR /&gt;With SG's Local LAN Failover, the pair of NICs must be in active/passive configuration, so only one NIC at a time is used. The other one will be idle until the first NIC loses its network link or can otherwise be detected as failed. At that point, the IP address of the first NIC will be switched over to the second NIC.&lt;BR /&gt;&lt;BR /&gt;In configurations like this, if your heartbeat NICs are not all connected to a single switch (to avoid a single point of failure), you should test the failover very carefully when setting up the cluster, e.g. by disconnecting one LAN cable at a time and verifying the nodes can still reach each other. &lt;BR /&gt;The most challenging test is probably when Node1's active HB NIC is connected to switch A, Node2's active HB NIC is connected to switch B and the interconnection between the switches is lost.&lt;BR /&gt;&lt;BR /&gt;MK</description>
      <pubDate>Mon, 16 Mar 2009 07:54:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379656#M671714</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2009-03-16T07:54:35Z</dc:date>
    </item>
    <item>
      <title>Re: Primary and Standby Heartbeat IP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379657#M671715</link>
      <description>So I should put it like this?&lt;BR /&gt;&lt;BR /&gt;Node1&lt;BR /&gt;Primary HB: 192.168.1.1&lt;BR /&gt;Standby HB: 10.0.0.1&lt;BR /&gt;&lt;BR /&gt;Node2&lt;BR /&gt;Primary HB: 192.168.1.2&lt;BR /&gt;Standby HB: 10.0.0.2</description>
      <pubDate>Mon, 16 Mar 2009 09:35:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379657#M671715</guid>
      <dc:creator>Jason Ng Teng Po</dc:creator>
      <dc:date>2009-03-16T09:35:59Z</dc:date>
    </item>
    <item>
      <title>Re: Primary and Standby Heartbeat IP</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379658#M671716</link>
      <description>Yes.</description>
      <pubDate>Wed, 18 Mar 2009 08:59:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/primary-and-standby-heartbeat-ip/m-p/4379658#M671716</guid>
      <dc:creator>B. Hulst</dc:creator>
      <dc:date>2009-03-18T08:59:40Z</dc:date>
    </item>
  </channel>
</rss>

