Have you checked this article: Using SCSI Persistent Reservation Fencing
(fence_scsi) with pacemaker in a Red Hat High Availability cluster - Red Hat
Customer Portal
|
|
|
| | |
|
|
|
| |
Using SCSI Persistent Reservation Fencing (fence_scsi) with pacemaker in...
This article describes how to properly configure fence_scsi and the
requirements for using it.
|
|
|
Have you checked if your storage supports persistent reservations?
Best Regards,Strahil Nikolov
В сряда, 30 октомври 2019 г., 8:42:16 ч. Гринуич-4, RAM PRASAD TWISTED
ILLUSIONS написа:
Hi everyone,
I am trying to set up a storage cluster with two nodes, both running debian
buster. The two nodes called, duke and miles, have a LUN residing on a SAN box
as their shared storage device between them. As you can see in the output of
pcs status, all the demons are active and I can get the nodes online without
any issues. However, I cannot get the fencing resources to start.
These two nodes were running debian jessie before and had access to the same
LUN in a storage cluster configuration. Now, I am trying to recreate a similar
setup with both nodes now running the latest debian. I am not sure if this is
relevant, but this LUN already has shared VG with data on it. I am wondering
if this could be the cause of the trouble? Should I be creating my stonith
device on a different/fresh LUN?
### pcs status
Cluster name: jazz
Stack: corosync
Current DC: duke (version 2.0.1-9e909a5bdd) - partition with quorum
Last updated: Wed Oct 30 11:58:19 2019
Last change: Wed Oct 30 11:28:28 2019 by root via cibadmin on duke
2 nodes configured
2 resources configured
Online: [ duke miles ]
Full list of resources:
fence_duke (stonith:fence_scsi): Stopped
fence_miles (stonith:fence_scsi): Stopped
Failed Fencing Actions:
* unfencing of duke failed: delegate=, client=pacemaker-controld.1703,
origin=duke,
last-failed='Wed Oct 30 11:43:29 2019'
* unfencing of miles failed: delegate=, client=pacemaker-controld.1703,
origin=duke,
last-failed='Wed Oct 30 11:43:29 2019'
Daemon Status:
corosync: active/enabled
pacemaker: active/enabled
pcsd: active/enabled
###
I used the following commands to add the two fencing devices and set their
location constraints .
###
sudo pcs cluster cib test_cib_cfg
pcs -f test_cib_cfg stonith create fence_duke fence_scsi pcmk_host_list=duke
pcmk_reboot_action="off"
devices="/dev/disk/by-id/wwn-0x600c0ff0001e8e3c89601b580100" meta
provides="unfencing"
pcs -f test_cib_cfg stonith create fence_miles fence_scsi pcmk_host_list=miles
pcmk_reboot_action="off"
devices="/dev/disk/by-id/wwn-0x600c0ff0001e8e3c89601b580100" delay=15 meta
provides="unfencing"
pcs -f test_cib_cfg constraint location fence_duke avoids duke=INFINITY
pcs -f test_cib_cfg constraint location fence_miles avoids miles=INFINITY
pcs cluster cib-push test_cib_cfg
###
Here is the output in /var/log/pacemaker/pacemaker.log after adding the fencing
resources
Oct 30 12:06:02 duke pacemaker-schedulerd[1702]
(determine_online_status_fencing) info: Node miles is active
Oct 30 12:06:02 duke pacemaker-schedulerd[1702] (determine_online_status)
info: Node miles is online
Oct 30 12:06:02 duke pacemaker-schedulerd[1702]
(determine_online_status_fencing) info: Node duke is active
Oct 30 12:06:02 duke pacemaker-schedulerd[1702] (determine_online_status)
info: Node duke is online
Oct 30 12:06:02 duke pacemaker-schedulerd[1702] (unpack_node_loop) info:
Node 2 is already processed
Oct 30 12:06:02 duke pacemaker-schedulerd[1702] (unpack_node_loop) info:
Node 1 is already processed
Oct 30 12:06:02 duke pacemaker-schedulerd[1702] (unpack_node_loop) info:
Node 2 is already processed
Oct 30 12:06:02 duke pacemaker-schedulerd[1702] (unpack_node_loop) info:
Node 1 is already processed
Oct 30 12:06:02 duke pacemaker-schedulerd[1702] (common_print) info: fence_duke
(stonith:fence_scsi): Stopped
Oct 30 12:06:02 duke pacemaker-schedulerd[1702] (common_print) info:
fence_miles (stonith:fence_scsi): Stopped
Oct 30 12:06:02 duke pacemaker-schedulerd[1702] (RecurringOp) info: Start
recurring monitor (60s) for fence_duke on miles
Oct 30 12:06:02 duke pacemaker-schedulerd[1702] (RecurringOp) info: Start
recurring monitor (60s) for fence_miles on duke
Oct 30 12:06:02 duke pacemaker-schedulerd[1702] (LogNodeActions) notice:
* Fence (on) miles 'required by fence_duke monitor'
Oct 30 12:06:02 duke pacemaker-schedulerd[1702] (LogNodeActions) notice:
* Fence (on) duke 'required by fence_duke monitor'
Oct 30 12:06:02 duke pacemaker-schedulerd[1702] (LogAction) notice: * Start
fence_duke ( miles )
Oct 30 12:06:02 duke pacemaker-schedulerd[1702] (LogAction) notice: * Start
fence_miles ( duke )
Oct 30 12:06:02 duke pacemaker-schedulerd[1702] (process_pe_message) notice:
Calculated transition 63, saving
