Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Linux-HA: Users

How to prevent IP fall-back after bringing failed resource online ?

 

 

Linux-HA users RSS feed   Index | Next | Previous | View Threaded


Bernard_Wu at ncci

Sep 8, 2009, 5:46 AM

Post #1 of 2 (477 views)
Permalink
How to prevent IP fall-back after bringing failed resource online ?

Hi List,
I have a test 2 node cluster with a floating IP with heartbeat and pingd.
Initially, the floating IP is on nodeA as eth0:0.
If I down eth0 of nodeA, the IP migrates over to nodeB as eth0:0. This is what I expected.
However, when I bring up eth0 on nodeA, the floating IP now appears back on nodeA but as eth0:1 and not eth0:0.

When I up the interface on nodeA, how can I :

1. prevent the floating IP from migrating back to its original node

2. and how to migrate it back as eth0:0


My cib.xml , ha.cf and ptest files are attached.
Any help or pointers would be much appreciated.

TIA
Bernie

________________________________
The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
Attachments: cib.xml (4.56 KB)
  ha.cf (0.25 KB)
  ptest.txt (5.74 KB)


andrew at beekhof

Sep 14, 2009, 6:33 AM

Post #2 of 2 (398 views)
Permalink
Re: How to prevent IP fall-back after bringing failed resource online ? [In reply to]

On Tue, Sep 8, 2009 at 2:46 PM, Bernie Wu <Bernard_Wu [at] ncci> wrote:
> Hi List,
> I have a test 2 node cluster with a floating IP with heartbeat and pingd.
> Initially, the floating IP is on nodeA as eth0:0.
> If I down eth0 of nodeA, the IP migrates over to nodeB as eth0:0.   This is what I expected.
> However, when I bring up eth0 on nodeA, the floating IP now appears back on nodeA but as eth0:1 and not eth0:0.
>
> When I up the interface on nodeA, how can I :
>
> 1.      prevent the floating IP from migrating back to its original node

search for resource-stickiness on the configuration explained pdf.
http://clusterlabs.org/w/Documentation

>
> 2.      and how to migrate it back as eth0:0
>
>
> My cib.xml , ha.cf and ptest files are attached.
> Any help or pointers would be much appreciated.
>
> TIA
> Bernie
>
> ________________________________
> The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.
>
> _______________________________________________
> Linux-HA mailing list
> Linux-HA [at] lists
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Linux-HA users RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.