An old vdsm agent was the source of some of my issues. After updating to
4.10.3 I was able to get it working, the options are being passed now. I
had to add a login_timeout as well since one of the drac interfaces is a
bit slow on login.
cmd_prompt=admin,login_timeout=15
On Fri, Mar 22, 2013 a
vdsm.log
Thread-1978569::DEBUG::2013-03-21
11:30:38,769::API::1024::vds::(fenceNode)
fenceNode(addr=vm2-mgt,port=,agent=drac5,user=root,passwd=,action=status,secure=,options=)
btw, looking at this log string i presume you hit the bug from this
tread (if you using ovirt 3.1):
http://comm
On Fri, Mar 22, 2013 at 2:07 AM, Thomas Scofield wrote:
> Has anyone been able to get a drac6 management interface working by using
> the drac5 fencing agent? From testing on the command line I was able to
For a CentOS 5.9 cluster (RHCS) between two Dell servers with idrac7 I
was able to setup ip
Hi,
I've been using drac5 fence with drac7 equipment for some time now -
works well
you need to pass option "cmd_prompt=admin1->" (without quotes), so you
missing "->" sign
secure or not - depends on enabled/disabled ssh in your drac.
Hope it helps.
Yuriy Demchenko
On 03/22/2013 05:07 AM, T
4 matches
Mail list logo
