<?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: Serviceguard failover problems in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-failover-problems/m-p/3423766#M703473</link>
    <description>Karthiknarayan,&lt;BR /&gt;&lt;BR /&gt;&amp;gt; if we stop the public interface card &lt;BR /&gt; &lt;BR /&gt;What do you mean with "stop"? If you simply perform "ifconfig lan0 down", then indeed this is no failure SG is supposed to detect. The network sensor is designed to detect interface HW failures only... setting the IP state to down is not a HW failure.&lt;BR /&gt; &lt;BR /&gt;&amp;gt; remote the patch cord from that interface&lt;BR /&gt; &lt;BR /&gt;This indeed would cause the driver state of the interface to go DOWN which should be detected by SG. Don't you see messages like "lan0 down" from cmcld in syslog.log?&lt;BR /&gt;&lt;BR /&gt;Have you configured the corresponding SUBNET to be monitored by the package? (Using the SUBNET statement in the package conf file?).&lt;BR /&gt; &lt;BR /&gt;Best regards...&lt;BR /&gt;Dietmar.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 17 Nov 2004 05:36:07 GMT</pubDate>
    <dc:creator>Dietmar Konermann</dc:creator>
    <dc:date>2004-11-17T05:36:07Z</dc:date>
    <item>
      <title>Serviceguard failover problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-failover-problems/m-p/3423763#M703470</link>
      <description>we have installed and configured the HP MC Service Guard for clustering. &lt;BR /&gt;When we shutdown the system the failover of resource from system A to system B and from System B to System A are working fine. But failover doesn't happen if we stop the public interface card (i.e. LAN 0) or remote the patch cord from that interface. &lt;BR /&gt;&lt;BR /&gt;Please Help me here</description>
      <pubDate>Wed, 17 Nov 2004 04:58:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-failover-problems/m-p/3423763#M703470</guid>
      <dc:creator>karthiknarayan</dc:creator>
      <dc:date>2004-11-17T04:58:57Z</dc:date>
    </item>
    <item>
      <title>Re: Serviceguard failover problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-failover-problems/m-p/3423764#M703471</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;if you are on MC/SG 11.16 please read the following in your cmclconf.ascii:&lt;BR /&gt;&lt;BR /&gt;# Network Monitor Configuration Parameters.&lt;BR /&gt;# The NETWORK_FAILURE_DETECTION parameter determines how LAN card failures are detected.&lt;BR /&gt;# If set to INONLY_OR_INOUT, a LAN card will be considered down when its inbound&lt;BR /&gt;# message count stops increasing or when both inbound and outbound&lt;BR /&gt;# message counts stop increasing.&lt;BR /&gt;# If set to INOUT, both the inbound and outbound message counts must&lt;BR /&gt;# stop increasing before the card is considered down.&lt;BR /&gt;NETWORK_FAILURE_DETECTION  INONLY_OR_INOUT&lt;BR /&gt;&lt;BR /&gt;So setting to INONLY_OR_INOUT should initiate failover if you pull the patch cable into your production lan, if you have a standby card, you need to pull both. Plus your subnet needs to be monitored (set in the pkg.conf).&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Bernhad&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 17 Nov 2004 05:29:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-failover-problems/m-p/3423764#M703471</guid>
      <dc:creator>Bernhard Mueller</dc:creator>
      <dc:date>2004-11-17T05:29:27Z</dc:date>
    </item>
    <item>
      <title>Re: Serviceguard failover problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-failover-problems/m-p/3423765#M703472</link>
      <description>What is output for "cmviewcl -v" ? &lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Fred&lt;BR /&gt;</description>
      <pubDate>Wed, 17 Nov 2004 05:30:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-failover-problems/m-p/3423765#M703472</guid>
      <dc:creator>Fred Ruffet</dc:creator>
      <dc:date>2004-11-17T05:30:13Z</dc:date>
    </item>
    <item>
      <title>Re: Serviceguard failover problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-failover-problems/m-p/3423766#M703473</link>
      <description>Karthiknarayan,&lt;BR /&gt;&lt;BR /&gt;&amp;gt; if we stop the public interface card &lt;BR /&gt; &lt;BR /&gt;What do you mean with "stop"? If you simply perform "ifconfig lan0 down", then indeed this is no failure SG is supposed to detect. The network sensor is designed to detect interface HW failures only... setting the IP state to down is not a HW failure.&lt;BR /&gt; &lt;BR /&gt;&amp;gt; remote the patch cord from that interface&lt;BR /&gt; &lt;BR /&gt;This indeed would cause the driver state of the interface to go DOWN which should be detected by SG. Don't you see messages like "lan0 down" from cmcld in syslog.log?&lt;BR /&gt;&lt;BR /&gt;Have you configured the corresponding SUBNET to be monitored by the package? (Using the SUBNET statement in the package conf file?).&lt;BR /&gt; &lt;BR /&gt;Best regards...&lt;BR /&gt;Dietmar.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 17 Nov 2004 05:36:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-failover-problems/m-p/3423766#M703473</guid>
      <dc:creator>Dietmar Konermann</dc:creator>
      <dc:date>2004-11-17T05:36:07Z</dc:date>
    </item>
    <item>
      <title>Re: Serviceguard failover problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-failover-problems/m-p/3423767#M703474</link>
      <description>Do you have a second (stand by) interface?  If so - then package won't failover - only the interface - that way package stays up.&lt;BR /&gt;&lt;BR /&gt;post a: cmgetconf&lt;BR /&gt;&lt;BR /&gt;Rgds...Geoff</description>
      <pubDate>Wed, 17 Nov 2004 07:50:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-failover-problems/m-p/3423767#M703474</guid>
      <dc:creator>Geoff Wild</dc:creator>
      <dc:date>2004-11-17T07:50:48Z</dc:date>
    </item>
    <item>
      <title>Re: Serviceguard failover problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-failover-problems/m-p/3423768#M703475</link>
      <description>That stop needs to be either a cable pull or switch shutdown. Since most of us admins don't like touching switches shared by othere, I recommend the cable pull test during a planned maintenance downtime.&lt;BR /&gt;&lt;BR /&gt;While you are at it draw up some test commands to run to make sure packages fail over properly.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 17 Nov 2004 08:41:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-failover-problems/m-p/3423768#M703475</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-11-17T08:41:17Z</dc:date>
    </item>
    <item>
      <title>Re: Serviceguard failover problems</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-failover-problems/m-p/3423769#M703476</link>
      <description>Hi Karthiknarayan,&lt;BR /&gt;&lt;BR /&gt;Can you post your configuration?. (your cluster ascii and package configuration files). Failover will not happen based on quite a few reasons.&lt;BR /&gt;&lt;BR /&gt;1. If the IP is not part of serviceguard.&lt;BR /&gt;2. AUTORUN is disabled in package configuration.&lt;BR /&gt;3. If the subnet is not monitored in the package configuration. Search for "SUBNET" in the package configuration file.&lt;BR /&gt;&lt;BR /&gt;-Sri</description>
      <pubDate>Wed, 17 Nov 2004 10:01:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/serviceguard-failover-problems/m-p/3423769#M703476</guid>
      <dc:creator>Sridhar Bhaskarla</dc:creator>
      <dc:date>2004-11-17T10:01:24Z</dc:date>
    </item>
  </channel>
</rss>

