What are the recommended values that should be set?

* you should use lanplus option 
* you should use power_wait = 4 (on some machines this is not needed at all)

Created attachment 473324 [details]
Proposed patch

Is the fix from bug 642700 from rhel5 going to be ported over to the fence_ilo on rhel6 as well so you can use fence_ilo instead of ipmi for the ilo3?

@Don:

The bug 642700 does not talk about adding support to fence_ilo. It contains fix for fence_ipmilan to be able to work with ilo3. Do you have any specific reason why you want to use fence_ilo instead of ipmi?

I did test fence_ipmilan actaully yesterday and got it to work.  However, I was hoping that fence_ilo would work with the ILO3 for one specific reason.

HP in all their infinate wisdom apparently only lets ILO accounts that have full administrator priv's use ipmi to do the stuff that is required for fencing (view and control power), so I have to create an account on my ILO that now has every privelage enabled except for user mgmt apparently.  

With fence_ilo I could create a login on the ILO with the single priv of "control power" and take away all other priveleages. 

I was much more comforatable doing this because the fence username and password are pretty much out there for anyone on the system to get if they wanted to.

Maybe I am just one of those rare security consuous systems admins, but the way fence_ipmilan makes me kinda leery of using it since it will be bascially putting login credentials with nearly full control of the ilo out into the open.

We have no plans to write a new fence agent specific to iLO3 hardware.  Our general policy is that if a fence device exposes a generic/standards compliant interface then we use that interface and do not develop a custom device specific one.  (i.e. snmp/ifmib, ipmi, scsi are the primary standard interfaces that we target)

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0745.html