Re: [Linux-cluster] PCS Cluster

2019-04-25 Thread Jan Pokorný
ux-cluster@redhat.com > Subject: Re: [Linux-cluster] PCS Cluster > > > I can give you the current arp table, but we do not log ARP so > there’s no way to tell you what the table looked like at that > particular time. > Or we need to wait for the next time if someone in Engin

Re: [Linux-cluster] PCS Cluster

2019-02-01 Thread Nicola Contu
Hello, any news on this? Is there anything else we can do to troubleshoot before this happens again? From: Nicola Contu Sent: Wednesday, January 30, 2019 4:08:20 PM To: linux-cluster@redhat.com Subject: Re: [Linux-cluster] PCS Cluster I can give you the

Re: [Linux-cluster] PCS Cluster

2019-01-30 Thread Nicola Contu
you the current ARP? From: linux-cluster-boun...@redhat.com on behalf of Michael Schwartzkopff Sent: Wednesday, January 30, 2019 1:15:01 PM To: linux-cluster@redhat.com Subject: Re: [Linux-cluster] PCS Cluster Am 30.01.19 um 09:59 schrieb Nicola Contu: > He

Re: [Linux-cluster] PCS Cluster

2019-01-30 Thread Michael Schwartzkopff
Am 30.01.19 um 09:59 schrieb Nicola Contu: > Hello, > I've setup a cluster using pacemaker and corosync for HA using HAProxy. > Two resources : Haproxy and a floating IP. > They are running on Centos7 on vmware. > > The strange thing that happens sometime is that the floating IP won't be > pingab

[Linux-cluster] PCS Cluster

2019-01-30 Thread Nicola Contu
Hello, I've setup a cluster using pacemaker and corosync for HA using HAProxy. Two resources : Haproxy and a floating IP. They are running on Centos7 on vmware. The strange thing that happens sometime is that the floating IP won't be pingable from outside the LAN. So for example, a server on the