<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font face="Times New Roman">Thanks Vasil.<br>
<br>
Adding delay to only one fenced device certainly solved my issue.<br>
<br>
Regards,<br>
Jatin<br>
</font><br>
<div class="moz-cite-prefix">On 4/27/2015 3:26 PM, Vasil Valchev
wrote:<br>
</div>
<blockquote
cite="mid:CAFZxf=+bOcYAMNRkjjNbHhWFn4973Q72VL1tNbFbYUq7Zu690A@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<div dir="ltr">Hi Jatin,
<div><br>
</div>
<div>Yes, you are definitely not using it properly :)</div>
<div>Put delay=20, just on one of the devices. This device will
wait for 20 sec (or 10 if you choose), before sending fence
request. By that time, the device without delay will have sent
the request and will have fenced it.</div>
<div>Also you only have to modify cluster.conf on one node. Pay
attention that you need to increment the config number.</div>
<div><br>
</div>
<div>You can see the current config version with cman_tool, I
don't remember the exact option - status maybe.</div>
<div>You can first verify the syntax of the file, then tell the
cluster to update it - check google for the exact commands for
RHEL 6.</div>
<div><br>
</div>
<div>Let me know if you have troubles.</div>
</div>
</blockquote>
<br>
</body>
</html>