Re: [Pacemaker] Virtual IP migration fails to cleanup IP from failed interface

2014-08-20 Thread Andrew Beekhof
On 20 Aug 2014, at 11:45 pm, Arjun Pandey wrote: > Hi > > I have a 2 Node(Active-Passive) mode cluster on CentOS 6.4 > After setting up the cluster things work fine. > > There are 4 resources (2 virtual IP's and my application (master-slave ) > mode). > Additionally i have a constraint that v

Re: [Pacemaker] Error: cluster is not currently running on this node

2014-08-20 Thread Miha
tnx! will do that and let you know. miha Dne 8/20/2014 5:03 PM, piše emmanuel segura: Hi, You need to give every cluster parameter to the fence_bladecenter_snmp, so from sp2 you neet to use " Attributes: action=off ipaddr=172.30.0.2 port=8 community=test login=snmp8 passwd=soft1234", command

Re: [Pacemaker] Error: cluster is not currently running on this node

2014-08-20 Thread emmanuel segura
Hi, You need to give every cluster parameter to the fence_bladecenter_snmp, so from sp2 you neet to use " Attributes: action=off ipaddr=172.30.0.2 port=8 community=test login=snmp8 passwd=soft1234", command to use from sp2 for test your fencing "fence_bladecenter_snmp -a 172.30.0.2 -l snmp8 -p so

Re: [Pacemaker] Error: cluster is not currently running on this node

2014-08-20 Thread Miha
ok, will do that. This will not affect sip2? sorry for my noob question but I must be careful as this is in production ;) So, "fence_bladecenter_snmp reboot" right? br miha Dne 8/19/2014 11:53 AM, piše emmanuel segura: sorry, That was a typo, fixed "try to poweroff sp1 by hand, using the fen

[Pacemaker] Virtual IP migration fails to cleanup IP from failed interface

2014-08-20 Thread Arjun Pandey
Hi I have a 2 Node(Active-Passive) mode cluster on CentOS 6.4 After setting up the cluster things work fine. There are 4 resources (2 virtual IP's and my application (master-slave ) mode). Additionally i have a constraint that virtual IP's are colocated with the master. If i bring the interface

Re: [Pacemaker] "op monitor timeout" not supported in my RA.

2014-08-20 Thread N, Ravikiran
On 20 Aug 2014, at 5:15 pm, N, Ravikiran wrote: > On 19 Aug 2014, at 5:31 pm, N, Ravikiran wrote: > >> Hi >> >> I have resource as ocf:heartbeat:ocrtms. > > Please do not use the 'heartbeat' namespace for custom agents. > [Ravikiran ] : Thanks for this info. Can u tell me which provider to u

Re: [Pacemaker] "op monitor timeout" not supported in my RA.

2014-08-20 Thread Andrew Beekhof
On 20 Aug 2014, at 5:15 pm, N, Ravikiran wrote: > On 19 Aug 2014, at 5:31 pm, N, Ravikiran wrote: > >> Hi >> >> I have resource as ocf:heartbeat:ocrtms. > > Please do not use the 'heartbeat' namespace for custom agents. > [Ravikiran ] : Thanks for this info. Can u tell me which provider to u

Re: [Pacemaker] "op monitor timeout" not supported in my RA.

2014-08-20 Thread N, Ravikiran
On 19 Aug 2014, at 5:31 pm, N, Ravikiran wrote: > Hi > > I have resource as ocf:heartbeat:ocrtms. Please do not use the 'heartbeat' namespace for custom agents. [Ravikiran ] : Thanks for this info. Can u tell me which provider to use if not "Heartbeat"..? > I'm trying to create resource using