On Thu, 23 Jan 2014 16:45:04 + wrote:
> Uhhh..I got the same configuration as the example config you sent me
> now. But I cause high cpu load on our cisco asa firewall..
>
> I guess this traffic is not normal?
When you want your cluster to repair failures _fast_, the components
have to sync
Hello,
I running corosync with success now.
But I got a problem, because I got two different subnet and I don't know which
ClusterIP I have to use.
I got 10.128.61.0 and 10.128.62.0, so a ClusterIP like 10.128.61.61 will not
routed in 10.128.62.0.
How I can use different ClusterIP's per sid
Thanks Kristoffer.
How is tuning done for lrm now?
Tom
On 01/24/2014 01:41 AM, Kristoffer Grönlund wrote:
> On Sat, 28 Dec 2013 11:18:44 -0500
> Tom Parker wrote:
>
>> Hello
>>
>> /usr/sbin/lrmadmin is missing from the latest version of cluster-glue
>> in SLES SP3. Has the program been depreca
>>> Lars Marowsky-Bree schrieb am 24.01.2014 um 14:24 in
Nachricht
<20140124132433.gh18...@suse.de>:
> On 2014-01-24T08:16:03, Ulrich Windl
wrote:
>
>> We have a server with a "network traffic light" on the front. With
>> corosync/pacemaker the light is constantly flickering, even if the cluster
On 2014-01-24T08:16:03, Ulrich Windl wrote:
> We have a server with a "network traffic light" on the front. With
> corosync/pacemaker the light is constantly flickering, even if the cluster
> "does nothing".
> So I guess it's normal.
Yes. Totem and other components have on-going health checks, s
