Re: [Users] power management for drac6

2013-03-22 Thread Yuriy Demchenko

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, 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 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=,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=

out err Unable to connect/login to fencing device



___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] power management for drac6

2013-03-22 Thread Gianluca Cecchi
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 ipmilan fence agent provided by rhcs because drac5
didn't work.
So possibly you can have success too with ipmilan agent for drac6 on oVirt.

I don't know how it exactly could map to oVirt setup, but on my rhcs
based cluster I set this:

 fencedevice agent=fence_ipmilan ipaddr=drac_ip_addr
auth=password login=fenceuser name=dracnode01
passwd_script=/usr/local/bin/pwd_dracnode01.sh lanplus=1
privlvl=operator/

and on drac mgmt we interface I enabled power mgmt for the designated user.

Gianluca
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] power management for drac6

2013-03-22 Thread Yuriy Demchenko

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://comments.gmane.org/gmane.comp.emulators.ovirt.user/3528

engine didnt pass options string when talking to vdsm

you can try and patch it:

diff --git a/vdsm/BindingXMLRPC.py b/vdsm/BindingXMLRPC.py
index cc5300f..8b548e4 100644
--- a/vdsm/BindingXMLRPC.py
+++ b/vdsm/BindingXMLRPC.py
@@ -357,7 +357,7 @@ class BindingXMLRPC(object):
secure=False, options=''):
  api = API.Global()
  return api.fenceNode(addr, port, agent, username, password,
-action, secure)
+action, secure, options)

  def setLogLevel(self, level):
  api = API.Global()

Yuriy Demchenko

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


Re: [Users] power management for drac6

2013-03-22 Thread Thomas Scofield
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 at 3:33 AM, Yuriy Demchenko demchenko...@gmail.comwrote:

 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://comments.gmane.org/**
 gmane.comp.emulators.ovirt.**user/3528http://comments.gmane.org/gmane.comp.emulators.ovirt.user/3528
 engine didnt pass options string when talking to vdsm

 you can try and patch it:

 diff --git a/vdsm/BindingXMLRPC.py b/vdsm/BindingXMLRPC.py
 index cc5300f..8b548e4 100644
 --- a/vdsm/BindingXMLRPC.py
 +++ b/vdsm/BindingXMLRPC.py
 @@ -357,7 +357,7 @@ class BindingXMLRPC(object):
 secure=False, options=''):
   api = API.Global()
   return api.fenceNode(addr, port, agent, username, password,
 -action, secure)
 +action, secure, options)

   def setLogLevel(self, level):
   api = API.Global()

 Yuriy Demchenko


___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users


[Users] power management for drac6

2013-03-21 Thread Thomas Scofield
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=,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=

out  err Unable to connect/login to fencing device
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users