13.11.2013 04:46, Jefferson Ogata wrote:
...
>
> In practice i ran into failover problems under load almost immediately.
> Under load, when i would initiate a failover, there was a race
> condition: the iSCSILogicalUnit RA will take down the LUNs one at a
> time, waiting for each connection to ter
13.11.2013 06:10, Jefferson Ogata wrote:
> Here's a problem i don't understand, and i'd like a solution to if
> possible, or at least i'd like to understand why it's a problem, because
> i'm clearly not getting something.
>
> I have an iSCSI target cluster using CentOS 6.4 with stock
> pacemaker/C
On 13 Nov 2013, at 2:10 pm, Jefferson Ogata wrote:
> Here's a problem i don't understand, and i'd like a solution to if possible,
> or at least i'd like to understand why it's a problem, because i'm clearly
> not getting something.
>
> I have an iSCSI target cluster using CentOS 6.4 with stoc
Here's a problem i don't understand, and i'd like a solution to if
possible, or at least i'd like to understand why it's a problem, because
i'm clearly not getting something.
I have an iSCSI target cluster using CentOS 6.4 with stock
pacemaker/CMAN/corosync and tgt, and DRBD 8.4 which i've bui
Greetings.
I'm working on a high-availability iSCSI target (tgt) cluster using
CentOS 6.4, to support a blade VM infrastructure. I've encountered a
number of problems i haven't found documented elsewhere (not for lack of
looking), and i want to run some solutions past the list to see what
sti
Hi,
Generally, ping uses ICMP which has no concept about "port".
ocf:pacemaker:pingd and calls internally ocf:pacemaker:ping are
implemented using fping.
BTW, I googled, to knock any tcp/udp port like ping.
hping looks be useable.
Of course, modify/create the resource agent is required. :)
rega
Hi All,
I would like to know, is it possible to change the ping port as 5060 using
ocf::pingd? Means to say need to send ping at port 5060.
If it is possible please advise what parameters do I need to enable it?
--
Regards,
Ahmed Munir Chohan
___
Lin