Cluster resources are shifting but in a particular scenario its not shifting,,,,
Dear friends.
I was testing my cluster. It was working fine. I shutdown my primary server by using commandline, then resources are shifting fine. I was happy. Because it is my first cluster. After few minutes something wild comes in my mind, May be this concept comes in all trechy guys.
I just suddenly unplugged the powercable from the server. and it goes down, and found resources are not shifting. :-(. Did eu test this? Just unplugged the power suddenly. So that server goes down immidiately. Resources are not shifitng.
Tried a lot. and still trying to solve this scenario. Please suggest,
rgds,
Jack
Responses
Just to add to my previous update:
When the active cluster node fails, standy by nodes will try to fence the active node before it can take over the cluster service.
If fencing is failed, the service won't be relocated because it has no idea about the actual status of the Active node.
It is important to know what sort of fencing have you configured on the box
For example when Dell Drac is used https://access.redhat.com/knowledge/node/42518
Rahman,
Reason why resources are not shifting/relocating is basically due to the fact that the fence is failing when you unplug the power cable from the active node
HP ILO is a hardware based management board.
Please read the "Note" section in the below URL
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Configuration_Example_-_Fence_Devices/HPiLO_Configuration.html
The behavior that you are observing seems to be an expected one when you use hardware based management board
When you do a graceful shutdown, relocation is initiated by the active node and fencing is not required
Let me know if you have any further questions
For iLO3 you should use fence_ipmilan, and ensure you have a power_wait="4" (or more) set:
How do I configure a cluster fence device for the HP ILO 3 in RHEL 5 or 6?
https://access.redhat.com/knowledge/solutions/54453
For ilo1 and 2, you can use fence_ipmilan or fence_ilo.
If your fencing is indeed failing, you should see messages saying so in /var/log/messages, and possibly more verbose error messages. Do you see any? What do they say?
What does your configuration in /etc/cluster/cluster.conf look like (feel free to strip out any passwords or sensitive information before posting)?
Thanks,
John Ruemker, RHCA
Software Maintenance Engineer
Global Support Services
Red Hat, Inc.
The problem is that even though you've created fencedevice definitions:
<fencedevices>
<fencedevice agent="fence_ilo_mp" ipaddr="clusnode1-ilo" login="****" name="cdbilo1" passwd="****1234" power_wait="4"/>
<fencedevice agent="fence_ilo_mp" ipaddr="clusnode2-ilo" login="****" name="cdbilo2" passwd="****1234" power_wait="4"/>
</fencedevices>
You have not assigned them to the nodes:
<clusternodes>
<clusternode name="dcdb-ibs-clusnode1-pv" nodeid="1"/>
<clusternode name="dcdb-ibs-clusnode2-pv" nodeid="2"/>
</clusternodes>
Normally it would look something like this:
<clusternodes>
<clusternode name="dcdb-ibs-clusnode1-pv" nodeid="1">
<fence>
<method name="1">
<device name="clustnode1-ilo"/>
</method>
</fence>
</clusternode>
<clusternode name="dcdb-ibs-clusnode2-pv" nodeid="2">
<fence>
<method name="1">
<device name="clustnode2-ilo"/>
</method>
</fence>
</clusternode>
</clusternodes>
You can see more specific instructions for assigning fence devices to cluster members here (RHEL 6):
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Cluster_Administration/index.html#s1-config-member-conga-CA
Or here (RHEL 5):
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Linux/5/html-single/Cluster_Administration/index.html#s1-config-fence-devices-conga-CA
Hope this helps.
Thanks,
John Ruemker, RHCA
Senior Software Maintenance Engineer
Global Support Services
Red Hat, Inc.
Your configuration looks ok to me, assuming that fence_ilo_mp is the correct fence agent for your specific hardware. Are you sure that's the one you need? If you're using traditional iLOs, you'll just need fence_ilo (iLO 1 or 2) or fence_ipmilan (iLO 1, 2, or 3). If you're sure fence_ilo_mp is the right agent, then everything else looks fine.
I definitely recommend testing your fencing configuration though. From dcdb-ibs-clusnode1-pv, you can fence dcdb-ibs-clusnode2-pv with:
# fence_node dcdb-ibs-clusnode2-pv
And you should see that node power cycle. When it comes back up, you can test fencing dcdb-ibs-clusnode1-pv from dcdb-ibs-clusnode2-pv:
# fence_node dcdb-ibs-clusnode1-pv
If either node did not power cycle during its test, then there is a problem with your configuration that you should correct before deploying the cluster into production.
Regards,
John
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
