I have three servers that I'm trying to create IP failover on with
heartbeat. I have three IPs, one for each machine, and I want an IP to be
assigned to a different machine when it goes down. This is all working
splendidly.
But in addition, I also want an IP to be assigned to a different machine
w
e-1.0/raw-file/tip/extra/resources/ping
Anlu
On Fri, Feb 17, 2012 at 11:09 AM, Anlu Wang wrote:
> Also, in my constraints section, for the ping connectivity resource
> location definitions, a node attribute is not specified on rsc_location.
> What is the default value of node then?
>
Also, in my constraints section, for the ping connectivity resource
location definitions, a node attribute is not specified on rsc_location.
What is the default value of node then?
Anlu
On Fri, Feb 17, 2012 at 10:57 AM, Anlu Wang wrote:
> I'm running 1.0.8. In accordance with the bu
t; On Thu, Feb 16, 2012 at 07:57:14PM -0800, Anlu Wang wrote:
> > I have three machines named anlutest1, anlutest2, and anlutest3 that I'm
> > trying to get IP failover working on. I'm using heartbeat for the
> messaging
> > layer, and everything works great when a ma
I have three machines named anlutest1, anlutest2, and anlutest3 that I'm
trying to get IP failover working on. I'm using heartbeat for the messaging
layer, and everything works great when a machine goes down. But I also
would like to failover an IP when EITHER the eth0 or eth1 network
interfaces fa
