RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 995141 - fence_ilo3 documentation request
Summary: fence_ilo3 documentation request
Keywords:
Status: CLOSED DUPLICATE of bug 1610494
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-High_Availability_Add-On_Reference
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: rc
: ---
Assignee: Steven J. Levine
QA Contact: michal novacek
URL:
Whiteboard:
: 1392106 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-08 16:03 UTC by michal novacek
Modified: 2019-03-06 01:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-31 18:26:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description michal novacek 2013-08-08 16:03:14 UTC 
This is documentaiton request. 

I tried to find out how to configure fencing in a cluster using fence_ilo3 and
found out that it's not documented anywhere. 

This is not too straightforward and it would be nice to have it. The thing that
makes it difficult is that there needs to be three resources for three nodes.

I figured out the configuration for myself so I thought it would be worth putting
in Cluster administration guide as another example.

# pcs status
Cluster name: light
Last updated: Thu Aug  8 17:51:29 2013
Last change: Thu Aug  8 17:51:28 2013 via cibadmin on light-01
Stack: corosync
Current DC: light-01 (1) - partition with quorum
Version: 1.1.10-5.el7-9abe687
3 Nodes configured
3 Resources configured


Online: [ light-01 light-03 light-02 ]

Full list of resources:

 fencing-light01        (stonith:fence_ilo3):   Started light-01 
 fencing-light02   	(stonith:fence_ilo3):   Started light-02 
 fencing-light03        (stonith:fence_ilo3):	Started light-03 

For each node I created fencing as follows:

# pcs stonith create fencing-light03 fence_ilo3 params login="admin" \
 passwd="admin" action="reboot" ipaddr="light-03-ilo"
 pcmk_host_list="light-03" verbose=""

# pcs resource show fencing-light03
 Resource: fencing-light03 (class=stonith type=fence_ilo3)
  Attributes: login=admin passwd=admin action=reboot ipaddr=10.34.70.20 \
pcmk_host_list=light-03 verbose= 
  Operations: monitor interval=60s (fencing-light03-monitor-interval-60s)
Comment 2 Andrew Beekhof 2013-08-09 08:40:14 UTC 
Re-assigning to the docs team, though they can't cover every permutation of every fencing device....
Comment 3 Jaroslav Kortus 2013-08-09 09:10:54 UTC 
this was probably more meant for the pacemaker documentation at project page, from where it could be easily cut&pasted (more or less) by anyone looking for that info.

Sometimes it helps if you see it used in some config. Pacemaker docs are full of these helpful hints, so this would be also a nice addition. I'd also like to add fence_scsi examples as soon as we figure them out :)
Comment 4 Steven J. Levine 2014-05-15 20:32:30 UTC 
This information -- and other small examples of pieces of different fence device configurations -- could be added to the fencing chapter of the reference manual, which at the moment is somewhat bare-bones. The plans are to expand that chapter, to provide more information about fencing concerns in general -- and adding some specifics like this would be great (the useful hints that Jaroslav notes).

Jaroslav has also pointed to some existing fencing documentation (for RHEL 6) on the customer portal, so this is an area where we need to coordinate the available information.

It's not likely there is time to do this by 7.0 GA, so I'm moving this to 7.1, but this should be part of the fencing documentation in the Reference manual.
Comment 5 Steven J. Levine 2014-09-24 15:29:59 UTC 
Current plans are to document specific fence devices as separate portal articles and not in the product doc. I'm moving this to 7.2 because it is not release-specific.
Comment 6 Steven J. Levine 2015-05-05 20:30:36 UTC 
This is really a sub-BZ of BZ#1175833, but I'm leaving it as a separate bug since we may simply use this particular device as an example. But in general the issue of documenting each specific fence device is not yet wholly settled.
Comment 7 Steven J. Levine 2018-02-12 22:09:48 UTC 
*** Bug 1392106 has been marked as a duplicate of this bug. ***
Comment 8 Steven J. Levine 2018-07-31 18:26:18 UTC 
Consolidating general HA documentation improvement issues into one BZ:

https://bugzilla.redhat.com/show_bug.cgi?id=1610494

*** This bug has been marked as a duplicate of bug 1610494 ***
Note You need to log in before you can comment on or make changes to this bug.