<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<STYLE type=text/css>DIV {
MARGIN: 0px
}
</STYLE>
<META name=GENERATOR content="MSHTML 8.00.6001.18939"></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=593192813-09092010><FONT color=#0000ff
size=2 face=Arial>For what it is worth, our experiences with HP iLO management
cards:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=593192813-09092010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=593192813-09092010><FONT color=#0000ff
size=2 face=Arial>iLO found on G1 servers does not need to be licensed, AFAIK,
it does not have the option to do so anyways.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=593192813-09092010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=593192813-09092010><FONT color=#0000ff
size=2 face=Arial>iLO2 found on G2 and beyond does not need to be licensed
either, if you are only using it as a fencing device. We licensed all of
ours, because it enabled useful KVM with remote media capabilities that are
superior than our Raritan KVM infrastructure.</FONT></SPAN></DIV>
<DIV><SPAN class=593192813-09092010><FONT color=#0000ff size=2
face=Arial></FONT></SPAN> </DIV>
<DIV><SPAN class=593192813-09092010><FONT color=#0000ff size=2 face=Arial>Both
management cards should have their firmware updated -- they were both
problematic to us as factory-shipped, but applying their update
packs allowed them to work as advertised.</FONT></SPAN></DIV>
<DIV><FONT color=#0000ff size=2 face=Arial></FONT><FONT color=#0000ff size=2
face=Arial></FONT><FONT color=#0000ff size=2 face=Arial></FONT> </DIV>
<DIV><FONT color=#0000ff size=2 face=Arial><SPAN class=593192813-09092010>Also,
can't you add "-v" for verbose output and also something like "-D
/tmp/fence.out" to save debugging info to an output file? It might help
some to see where exactly the failure is occuring. Good
luck.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial></FONT><FONT
color=#0000ff size=2 face=Arial></FONT><FONT color=#0000ff size=2
face=Arial></FONT><BR></DIV>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> linux-cluster-bounces@redhat.com
[mailto:linux-cluster-bounces@redhat.com] <B>On Behalf Of </B>Girish
Prajapati<BR><B>Sent:</B> Wednesday, September 08, 2010 6:06 AM<BR><B>To:</B>
Linux-cluster@redhat.com<BR><B>Subject:</B> [Linux-cluster] need help - Fencing
problem<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV
style="FONT-FAMILY: times new roman, new york, times, serif; FONT-SIZE: 12pt">
<DIV>Hello Everybody,</DIV>
<DIV>i am having problem of fencing a cluster node let me explain indetail
:</DIV>
<DIV>I have installed RHEL 5.4 on HP Prolaint DL280 G5 servers and iLO 2as
fencing device. Am managing cluster through Luci - (Conga). itseems everything
is working fine. I can reboot cluster nodes through Luci and service get
transfer to another node. After rebooting node connect to cluster automatically
without any error.</DIV>
<DIV>Problem is i can not do Fence this node through Luci, when i try to fence
any node i get following error :</DIV>
<DIV><BR>Sep 8 14:51:16 node2 fence_node[9106]: agent "fence_ilo" reports:
Unable to connect/login to fencing device<BR>Sep 8 14:51:16 node2
fence_node[9106]: Fence of "node1.drctmb.com" was unsuccessful</DIV>
<DIV><BR>my iLO license is : iLO 2 Advanced Evaluation</DIV>
<DIV>Do i need to have license of iLO or there is problem in configuration
of cluster ?</DIV>
<DIV>how i can check cluster log in details.</DIV>
<DIV> </DIV>
<DIV>Appreciate your help.<BR>Thank you in advance.</DIV>
<DIV> </DIV>
<DIV>Regards,<BR>Girishkumar R Prajapati</DIV></DIV><BR></BODY></HTML>