com]
> Sent: 10 March 2016 15:01
> To: users@clusterlabs.org
> Subject: Re: [ClusterLabs] FLoating IP failing over but not failing back
> with active/active LDAP (dirsrv)
>
> On 03/10/2016 08:48 AM, Bernie Jones wrote:
>> A bit more info..
>>
>>
>>
>> If,
[mailto:kgail...@redhat.com]
Sent: 10 March 2016 15:01
To: users@clusterlabs.org
Subject: Re: [ClusterLabs] FLoating IP failing over but not failing back
with active/active LDAP (dirsrv)
On 03/10/2016 08:48 AM, Bernie Jones wrote:
> A bit more info..
>
>
>
> If, after I restart th
if the cleanup is changing the status in some way..
>
>
>
> From: Bernie Jones [mailto:ber...@securityconsulting.ltd.uk]
> Sent: 10 March 2016 08:47
> To: 'Cluster Labs - All topics related to open-source clustering welcomed'
> Subject: [ClusterLabs] FLoating IP failing o
mailto:ber...@securityconsulting.ltd.uk]
Sent: 10 March 2016 08:47
To: 'Cluster Labs - All topics related to open-source clustering welcomed'
Subject: [ClusterLabs] FLoating IP failing over but not failing back with
active/active LDAP (dirsrv)
Hi all, could you advise please?
I'm trying to configure a f
Hi all, could you advise please?
I'm trying to configure a floating IP with an active/active deployment of
389 directory server. I don't want pacemaker to manage LDAP but just to
monitor and switch the IP as required to provide resilience. I've seen some
other similar threads and based my
