<?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: lanfailover testing in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543824#M669044</link>
    <description>There must be something else that has to be set up regarding local lan failover. I have a very simple setup. Serviceguard A11.19 on a BL870 blade. Lan0 is the primary and lan1 is the standby. If is stop the Enet module in interconnect bay 1 lan0 fails over fine to lan1. But if I just down the interface (ifconfig lan0 down) nothing happens. Both lan0 and lan1 remain down.</description>
    <pubDate>Sun, 06 Dec 2009 02:55:48 GMT</pubDate>
    <dc:creator>pz7rx8</dc:creator>
    <dc:date>2009-12-06T02:55:48Z</dc:date>
    <item>
      <title>lanfailover testing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543817#M669037</link>
      <description>hi&lt;BR /&gt;&lt;BR /&gt;I am using hp11.31 bl860C servers 2node mc sericeguard cluster.&lt;BR /&gt;service guard version 11.19&lt;BR /&gt;config stationary IP on lan0&lt;BR /&gt;standby lan3&lt;BR /&gt;heartbeat IP on lan2 and standby lan1&lt;BR /&gt;&lt;BR /&gt;I am testing lan failover scenario.&lt;BR /&gt;using  ifconfig lan0 down ip switched to standby lan3. &lt;BR /&gt;but if I give ifconfig lan2 down it is rebooting the second node.&lt;BR /&gt;&lt;BR /&gt;can any one tell me how to validate network failover in blade servers cluster.&lt;BR /&gt;&lt;BR /&gt;also I noted one thing that if I disable both public lan card where I enabled IP monitoring to gateway, eventhough I am not able to ping to gateway from server the cluster is working ok.&lt;BR /&gt;&lt;BR /&gt;pls help.&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;</description>
      <pubDate>Thu, 03 Dec 2009 15:37:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543817#M669037</guid>
      <dc:creator>Sreejith Kaliyam</dc:creator>
      <dc:date>2009-12-03T15:37:54Z</dc:date>
    </item>
    <item>
      <title>Re: lanfailover testing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543818#M669038</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Blades all get their networking via a NIC card in the blade enclosure.&lt;BR /&gt;&lt;BR /&gt;A valid testing scenario would involve setting up stand by connections and then physically disconnecting the network cable from one of the network ports on the blade enclosure.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 03 Dec 2009 16:04:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543818#M669038</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2009-12-03T16:04:08Z</dc:date>
    </item>
    <item>
      <title>Re: lanfailover testing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543819#M669039</link>
      <description>Hi, &lt;BR /&gt;&lt;BR /&gt;The node is rebooting because NODE_FAIL FAST is enabled.&lt;BR /&gt;&lt;BR /&gt;May be your hearbeat standby not working properly. Try to increase the NODE TIMEOUT parameter and do that. &lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sooraj U</description>
      <pubDate>Thu, 03 Dec 2009 16:04:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543819#M669039</guid>
      <dc:creator>SoorajCleris</dc:creator>
      <dc:date>2009-12-03T16:04:17Z</dc:date>
    </item>
    <item>
      <title>Re: lanfailover testing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543820#M669040</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;I cant do the test of removing cable from the enclosure because this is a virtual connect configuration sharing with other servers. &lt;BR /&gt;&lt;BR /&gt;I will check the node time out value. Can you please tell me if ifconfig lan* down is a valid option to test the service guard.&lt;BR /&gt;&lt;BR /&gt;rgds</description>
      <pubDate>Thu, 03 Dec 2009 16:11:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543820#M669040</guid>
      <dc:creator>Sreejith Kaliyam</dc:creator>
      <dc:date>2009-12-03T16:11:05Z</dc:date>
    </item>
    <item>
      <title>Re: lanfailover testing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543821#M669041</link>
      <description>Hi, &lt;BR /&gt;&lt;BR /&gt;The network port which we see is UP Link port of swithes not the connctions from the servers. So untill and unless you have a patch pathpannel (very rare) installed instead of a an ethernet switch blade, removing cable is not possible.&lt;BR /&gt;&lt;BR /&gt;I dont know if we have an option of desabling downlink port of the switch from OA.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Sooraj&lt;BR /&gt;</description>
      <pubDate>Thu, 03 Dec 2009 16:11:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543821#M669041</guid>
      <dc:creator>SoorajCleris</dc:creator>
      <dc:date>2009-12-03T16:11:07Z</dc:date>
    </item>
    <item>
      <title>Re: lanfailover testing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543822#M669042</link>
      <description>hi&lt;BR /&gt;&lt;BR /&gt;I can disable profile of the server and nic is switching, but the IP monitor is not working. I am looking for some test case from HP.&lt;BR /&gt;&lt;BR /&gt;rgds</description>
      <pubDate>Thu, 03 Dec 2009 16:24:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543822#M669042</guid>
      <dc:creator>Sreejith Kaliyam</dc:creator>
      <dc:date>2009-12-03T16:24:51Z</dc:date>
    </item>
    <item>
      <title>Re: lanfailover testing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543823#M669043</link>
      <description>Hi &lt;BR /&gt;&lt;BR /&gt;can you please post the cluster config ascii file as well as the packahge config file.&lt;BR /&gt;&lt;BR /&gt;make sure that in pkg config file you have &lt;BR /&gt;&lt;BR /&gt;NODE_FAIL_FAST_ENABLED and &lt;BR /&gt;SERVICE_FAIL_FAST_ENABLED as set to NO&lt;BR /&gt;&lt;BR /&gt;also &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Set LOCAL_LAN_FAILOVER_ALLOWD to YES&lt;BR /&gt;regards&lt;BR /&gt;sujit&lt;BR /&gt;</description>
      <pubDate>Sat, 05 Dec 2009 16:15:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543823#M669043</guid>
      <dc:creator>sujit kumar singh</dc:creator>
      <dc:date>2009-12-05T16:15:11Z</dc:date>
    </item>
    <item>
      <title>Re: lanfailover testing</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543824#M669044</link>
      <description>There must be something else that has to be set up regarding local lan failover. I have a very simple setup. Serviceguard A11.19 on a BL870 blade. Lan0 is the primary and lan1 is the standby. If is stop the Enet module in interconnect bay 1 lan0 fails over fine to lan1. But if I just down the interface (ifconfig lan0 down) nothing happens. Both lan0 and lan1 remain down.</description>
      <pubDate>Sun, 06 Dec 2009 02:55:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lanfailover-testing/m-p/4543824#M669044</guid>
      <dc:creator>pz7rx8</dc:creator>
      <dc:date>2009-12-06T02:55:48Z</dc:date>
    </item>
  </channel>
</rss>

