<?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: Floating ip is not pingable after failover in a Clustering Setup in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/floating-ip-is-not-pingable-after-failover-in-a-clustering-setup/m-p/4143458#M83409</link>
    <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Check if its pingable from the node its supposedly configured on.&lt;BR /&gt;&lt;BR /&gt;If not: Cluster configuration or cluster manager is not working correctly. See /var/log/messages&lt;BR /&gt;&lt;BR /&gt;If yes:&lt;BR /&gt;Check externally. Check main network configuration is correct because you can not specify netmask and such in the cluster.conf file.&lt;BR /&gt;&lt;BR /&gt;CISCO routers may need to be configured to have the same IP address appear on two ports. That would make this a CISCO problem, not a Linux problem.&lt;BR /&gt;&lt;BR /&gt;Make sure the Linux system is patched correctly, a bad kernel release could contribute to this problem.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
    <pubDate>Tue, 12 Feb 2008 11:38:39 GMT</pubDate>
    <dc:creator>Steven E. Protter</dc:creator>
    <dc:date>2008-02-12T11:38:39Z</dc:date>
    <item>
      <title>Floating ip is not pingable after failover in a Clustering Setup</title>
      <link>https://community.hpe.com/t5/operating-system-linux/floating-ip-is-not-pingable-after-failover-in-a-clustering-setup/m-p/4143457#M83408</link>
      <description>We have 2 linux boxes which form part of Clustering solution.The active host has a floating ip assigned to it. However whenever there is failover the floating ip is brought up on the the formerly-standby and the now-to-be-active host.The floating ip is assigned to a logical interface (which has mac address of the physical interface, as a result when failover happens the floating ip on the new host has mac address corresponding to the physical interface of the new host)&lt;BR /&gt;However when we ping from outside , say from a separate subnet,the ping fails after the failover even when ip is brought up on the new host.&lt;BR /&gt;It seems for some reason the CISCO switch doesnt update its arp table or the mac address resulting in failure of the ping.&lt;BR /&gt;&lt;BR /&gt;Any suggestions/solutions making the floating ip failover transparent such that the pings are not lost when the failover happens will be great.</description>
      <pubDate>Mon, 11 Feb 2008 23:18:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/floating-ip-is-not-pingable-after-failover-in-a-clustering-setup/m-p/4143457#M83408</guid>
      <dc:creator>Amit R</dc:creator>
      <dc:date>2008-02-11T23:18:50Z</dc:date>
    </item>
    <item>
      <title>Re: Floating ip is not pingable after failover in a Clustering Setup</title>
      <link>https://community.hpe.com/t5/operating-system-linux/floating-ip-is-not-pingable-after-failover-in-a-clustering-setup/m-p/4143458#M83409</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;Check if its pingable from the node its supposedly configured on.&lt;BR /&gt;&lt;BR /&gt;If not: Cluster configuration or cluster manager is not working correctly. See /var/log/messages&lt;BR /&gt;&lt;BR /&gt;If yes:&lt;BR /&gt;Check externally. Check main network configuration is correct because you can not specify netmask and such in the cluster.conf file.&lt;BR /&gt;&lt;BR /&gt;CISCO routers may need to be configured to have the same IP address appear on two ports. That would make this a CISCO problem, not a Linux problem.&lt;BR /&gt;&lt;BR /&gt;Make sure the Linux system is patched correctly, a bad kernel release could contribute to this problem.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Tue, 12 Feb 2008 11:38:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/floating-ip-is-not-pingable-after-failover-in-a-clustering-setup/m-p/4143458#M83409</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2008-02-12T11:38:39Z</dc:date>
    </item>
    <item>
      <title>Re: Floating ip is not pingable after failover in a Clustering Setup</title>
      <link>https://community.hpe.com/t5/operating-system-linux/floating-ip-is-not-pingable-after-failover-in-a-clustering-setup/m-p/4143459#M83410</link>
      <description>Thanks for the reply,&lt;BR /&gt;I think I complicated the matters.&lt;BR /&gt;I am not using Clustering Solution of Linux but something else.To simplify on failover we do bring down the ip on the failing node and bring it up on the new node.&lt;BR /&gt;However if some one is continously pinging it from outside (diff subnet) , the pings hang when it is brought down on the old host and brought up on the new host.Note that the ip is up when u do ifconfig on the new node.&lt;BR /&gt;</description>
      <pubDate>Tue, 12 Feb 2008 17:27:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/floating-ip-is-not-pingable-after-failover-in-a-clustering-setup/m-p/4143459#M83410</guid>
      <dc:creator>Amit R</dc:creator>
      <dc:date>2008-02-12T17:27:50Z</dc:date>
    </item>
    <item>
      <title>Re: Floating ip is not pingable after failover in a Clustering Setup</title>
      <link>https://community.hpe.com/t5/operating-system-linux/floating-ip-is-not-pingable-after-failover-in-a-clustering-setup/m-p/4143460#M83411</link>
      <description>The following command exactly does what I wanted.&lt;BR /&gt;It sends an arp broadcast to all .In the process the CISCO updates its arp table to the new mac address associated with the floating ip on the new host. &lt;BR /&gt;&lt;BR /&gt; arping -U &lt;FLOATINGIP&gt; -c &lt;COUNT&gt; -I &lt;FLOATINGIPINTERFACENAME&gt; &lt;BR /&gt;However one needs to mention the interface else it takes the default interface say eth0 and is of no use.&lt;BR /&gt;Also one needs to specify count else its infinite like ping.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;arping [ -AbDfhqUV]  [ -c count]  [ -w deadline]  [ -s source]  -I interface destination &lt;BR /&gt;&lt;BR /&gt;DESCRIPTION &lt;BR /&gt;&lt;BR /&gt;Ping destination on device interface by ARP packets, using source address source. &lt;BR /&gt;OPTIONS &lt;BR /&gt;&lt;BR /&gt;-c count &lt;BR /&gt;Stop after sending count ARP REQUEST packets. With deadline option, arping waits for count ARP REPLY packets, until the timeout expires. &lt;BR /&gt;&lt;BR /&gt;-I interface &lt;BR /&gt;Name of network device where to send ARP REQUEST packets. This option is required. &lt;BR /&gt;-U &lt;BR /&gt;Unsolicited ARP mode to update neighbours' ARP caches. No replies are expected. &lt;BR /&gt;&lt;/FLOATINGIPINTERFACENAME&gt;&lt;/COUNT&gt;&lt;/FLOATINGIP&gt;</description>
      <pubDate>Thu, 14 Feb 2008 16:14:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/floating-ip-is-not-pingable-after-failover-in-a-clustering-setup/m-p/4143460#M83411</guid>
      <dc:creator>Amit R</dc:creator>
      <dc:date>2008-02-14T16:14:22Z</dc:date>
    </item>
  </channel>
</rss>

