<?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: 2 Network cards only in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/2-network-cards-only/m-p/5273171#M660409</link>
    <description>Maybe I wasn't clear enough...&lt;BR /&gt;The servers have each two NIC's.&lt;BR /&gt;Lan0 is for heartbeat and is in the same vlan or network (e.g. 10.100.1.10)&lt;BR /&gt;Lan1 has a 10.100.1.20 ip address. &lt;BR /&gt;So, the question again: &lt;BR /&gt;Is serviceguard able to fail over from lan1:1 to lan0:1 if lan1 fails?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;PS:&lt;BR /&gt;I now HP recommends that the heartbeat packages should go over an additional vlan/network.&lt;BR /&gt;</description>
    <pubDate>Tue, 08 Feb 2011 18:03:12 GMT</pubDate>
    <dc:creator>Stefan Huber</dc:creator>
    <dc:date>2011-02-08T18:03:12Z</dc:date>
    <item>
      <title>2 Network cards only</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/2-network-cards-only/m-p/5273169#M660407</link>
      <description>Hi, &lt;BR /&gt;&lt;BR /&gt;I have two servers with two network cards only.&lt;BR /&gt;I configure one interface (lan0) for heartbeat. The other interface (lan1) gets the servers physical ip.&lt;BR /&gt;&lt;BR /&gt;What happens, if lan1 fails. Is service guard able to switch the package ip over to the heartbeat interface?&lt;BR /&gt;&lt;BR /&gt;Cheers</description>
      <pubDate>Tue, 08 Feb 2011 15:57:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/2-network-cards-only/m-p/5273169#M660407</guid>
      <dc:creator>Stefan Huber</dc:creator>
      <dc:date>2011-02-08T15:57:05Z</dc:date>
    </item>
    <item>
      <title>Re: 2 Network cards only</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/2-network-cards-only/m-p/5273170#M660408</link>
      <description>Hi stefan,&lt;BR /&gt;&lt;BR /&gt;As of my knowledge, an interface that has to act as a failover for another interface in terms of NIC or talking about the terminology "standby", one typical requirement being that the standy interface should not be configured with an IP address!!&lt;BR /&gt;&lt;BR /&gt;This is one of the primary rules of classic serviceguard.&lt;BR /&gt;&lt;BR /&gt;&amp;gt; Is service guard able to switch the package ip over to the heartbeat interface.&lt;BR /&gt;&lt;BR /&gt;The package ip is supposed to be different from your stationary IP address in case of your scenario lan1. The "package" should be failing over to another node. You are talking about a standy lan interface if I am not mistaken . :)&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Ismail Azad</description>
      <pubDate>Tue, 08 Feb 2011 17:43:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/2-network-cards-only/m-p/5273170#M660408</guid>
      <dc:creator>Ismail Azad</dc:creator>
      <dc:date>2011-02-08T17:43:39Z</dc:date>
    </item>
    <item>
      <title>Re: 2 Network cards only</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/2-network-cards-only/m-p/5273171#M660409</link>
      <description>Maybe I wasn't clear enough...&lt;BR /&gt;The servers have each two NIC's.&lt;BR /&gt;Lan0 is for heartbeat and is in the same vlan or network (e.g. 10.100.1.10)&lt;BR /&gt;Lan1 has a 10.100.1.20 ip address. &lt;BR /&gt;So, the question again: &lt;BR /&gt;Is serviceguard able to fail over from lan1:1 to lan0:1 if lan1 fails?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;PS:&lt;BR /&gt;I now HP recommends that the heartbeat packages should go over an additional vlan/network.&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Feb 2011 18:03:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/2-network-cards-only/m-p/5273171#M660409</guid>
      <dc:creator>Stefan Huber</dc:creator>
      <dc:date>2011-02-08T18:03:12Z</dc:date>
    </item>
    <item>
      <title>Re: 2 Network cards only</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/2-network-cards-only/m-p/5273172#M660410</link>
      <description>I configure one interface (lan0) for heartbeat. &amp;gt;&amp;gt;The other interface (lan1) gets the servers physical ip.&lt;BR /&gt;&lt;BR /&gt;&amp;gt;Lan0 is for heartbeat and is in the same vlan or network (e.g. 10.100.1.10)&lt;BR /&gt;&amp;gt;Lan1 has a 10.100.1.20 ip address. &lt;BR /&gt;&lt;BR /&gt;Looks like both are in same network&lt;BR /&gt;&lt;BR /&gt;You clearly said that the lan1 has physical IP,so it`s might be for  heartbeat + data&lt;BR /&gt;&lt;BR /&gt;lan0 has heart beat IP ,so it`s dedicated heartbeat ( no data )&lt;BR /&gt;&lt;BR /&gt;PS ::check cluster.conf file for the same.&lt;BR /&gt;&lt;BR /&gt;So you just have fulfilled the minimum cluster requirement.&lt;BR /&gt;&lt;BR /&gt;If lan0 fails ,then both heartbeat + data may go through lan1.&lt;BR /&gt;&lt;BR /&gt;But if lan1 fails there will be no data transfer only heartbeats.So there would be issues with data transactions.&lt;BR /&gt;&lt;BR /&gt;Doesn`t looks like a very good setup ,good to have a standby heartbeat &amp;amp; data lan card.&lt;BR /&gt;&lt;BR /&gt;Yes heartbeat &amp;amp; data are good to keep in different subnets.&lt;BR /&gt;&lt;BR /&gt;Do post you cluster.conf file for further queries.&lt;BR /&gt;&lt;BR /&gt;Hope this helps.&lt;BR /&gt;&lt;BR /&gt;Manix</description>
      <pubDate>Tue, 08 Feb 2011 19:19:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/2-network-cards-only/m-p/5273172#M660410</guid>
      <dc:creator>Manix</dc:creator>
      <dc:date>2011-02-08T19:19:31Z</dc:date>
    </item>
    <item>
      <title>Re: 2 Network cards only</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/2-network-cards-only/m-p/5273173#M660411</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Yes.... If you need a standby lancard you need one more NIC without an IP configured so as Manix said the failure of lan1 failsover where??&lt;BR /&gt;&lt;BR /&gt;I know you know this but:-&lt;BR /&gt;&lt;BR /&gt;One of the rules of serviceguard is to not put the same subnet for two interface cards on the same node of the cluster. This is not only for a serviceguard cluster but also a rule for troubleshooting network connectivity which states that if you do this, both your interface cards might not function "simultaneously" but might function separately. Jus curious but especially in a cluster environment why would u want this??&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;Ismail Azad</description>
      <pubDate>Tue, 08 Feb 2011 19:55:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/2-network-cards-only/m-p/5273173#M660411</guid>
      <dc:creator>Ismail Azad</dc:creator>
      <dc:date>2011-02-08T19:55:32Z</dc:date>
    </item>
    <item>
      <title>Re: 2 Network cards only</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/2-network-cards-only/m-p/5273174#M660412</link>
      <description>Thanks for all the answers.&lt;BR /&gt;I knew, that this configuration would fulfill the minimum requirements...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 08 Feb 2011 20:18:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/2-network-cards-only/m-p/5273174#M660412</guid>
      <dc:creator>Stefan Huber</dc:creator>
      <dc:date>2011-02-08T20:18:37Z</dc:date>
    </item>
    <item>
      <title>Re: 2 Network cards only</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/2-network-cards-only/m-p/5273175#M660413</link>
      <description>closed</description>
      <pubDate>Tue, 08 Feb 2011 20:19:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/2-network-cards-only/m-p/5273175#M660413</guid>
      <dc:creator>Stefan Huber</dc:creator>
      <dc:date>2011-02-08T20:19:02Z</dc:date>
    </item>
  </channel>
</rss>

