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 determine that we need to add the option cmd_prompt=admin1.  But for some reason I can’t get any options to work.  From the logs below you can see that the ovirt-engine is passing the options along, but on the vdsm log those options are no longer there.

 

ovirt_engine/engine.log

 

2013-03-21 11:30:33,408 INFO  [org.ovirt.engine.core.bll.FenceExecutor] (ajp--127.0.0.1-8702-9) Executing <Status> Power Management command, Proxy Host:vm1, Agent:drac5, Target Host:, Management IP:vm2, User:root, Options:cmd_prompt=admin1,secure=true,slot=0

 

2013-03-21 11:30:33,411 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (ajp--127.0.0.1-8702-9) START, FenceVdsVDSCommand(HostName = vm1, HostId = 63336472-4bbd-11e2-b2fc-5bc78da11d0c, targetVdsId = f80052ad-993e-4778-9924-d4e603425d32, action = Status, ip = vm2-mgt, port = , type = drac5, user = root, password = ******, options = 'cmd_prompt=admin1,secure=true,slot=0'), log id: 3773df59

 

2013-03-21 11:30:44,123 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.FenceVdsVDSCommand] (ajp--127.0.0.1-8702-9) FINISH, FenceVdsVDSCommand, return: Test Failed, Host Status is: unknown. The fence-agent script reported the following error: Unable to connect/login to fencing device

, log id: 3773df59

 

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=XXXX,action=status,secure=,options=)

 

Thread-1978569::DEBUG::2013-03-21 11:30:44,113::API::1050::vds::(fenceNode) rc 1 in agent=fence_drac5

ipaddr=vm2-mgt

login=root

option=status

passwd=XXXX

out  err Unable to connect/login to fencing device