similar to: CentOS 5.5 - VMware Fencing in Cluster

I am not sure this is the proper forum for this question, feel free to redirect me if you like to the correct place. I have the following setup: vmware esxi 2 CentOS 5.3 servers (vmware virtual hosts) these 2 servers are running conga(luci, ricci) and the rest of the cluster suite with a simple IP address setup to failover for testing. My problem comes in when I need to setup fencing for

I think I know the answer to this question based on all of the research I've done, but figured I'd ask anyway. I needed a couple of servers for an HA cluster, and our "order" guy here ordered me a couple of Dell PowerEdge T110 II. I'd planned on using IPMI to fence these things with, but later found out that this model is only one of two PE servers Dell sells that has a

Hi all, A recent update to CentOS 5.9 has broken my cluster's ability to fence nodes. I have two Dell's which are both fenced via their DRAC6 cards. The current configuration in cluster.conf for the fencing devices is: <fencedevice agent="fence_drac5" cmd_prompt="admin1-&gt;" ipaddr="192.168.251.11" login="fencer" name="ms1-drac"

Hi there. I have 2 days trying to resolve this issue ... I have 2 xen servers in cluster ... and I installed Luci on another server separate from the 2 xen servers. I created a cluster ... I create a failed over domain .... I did migration and live migration from a dom0 to another ... My problem is .... I don`t have "Add a virtual Service" tab to add A VM as a cluster service ...

Hi. I'm new to configuring Clustering . The CentOS 5.5 guest machines will be running on ESXi 4.1 . I'm configuring the clustering using "Conga" . I see that there is support for using ESX to do the fencing. The problem I have is that the guest machines are not allowed to have access the "management network" as per security policies. The guest machines don't no

Hello all. I posted this in the forum and was told to instead post it to the mailing list. My apologies for the redundancy if you have already seen and been irritated by my blatherings. Thanks. _________________________ I am working on a CentOS clustered LAMP stack and running into problems. I have searched extensively and have come up empty. Here's my setup: Two node cluster

Hello everyone. I am currently working on setting up new servers for my employer. Basically we want two servers, all of them running several VEs (virtual environments, OpenVZ) which can dynamically take over each others job if necessary. Some services will run concurrently on both servers like apache2 (load balancing), so those need concurrent access to specific data. We had a close look at

Charles, Thanks for your reply. Indeed you may be right that the NUT fencing agent might be written with networked UPSes in mind, as healthy nodes could use the network to issue "fence" orders to remove unhealthy ones. I will post here if I find more info. The problem with the resupply of services is that NUT doesn't restart on the node that comes back up. To recap, I pull the

By default, o2cb fences the box by calling emergency_restart(). While this scheme works well in production, it comes in the way during testing as it does not let the tester take stack/core dumps for analysis. This patch allows user to dynamically change the fence method to panic() by: # echo "panic" > /sys/kernel/config/cluster/<clustername>/fence_method Signed-off-by: Sunil

Hi to all, this is My first time on this mailinglist. I have a problem with Ocfs2 on Debian etch 4.0 I'd like when a node go down or freeze without unmount the ocfs2 partition the heartbeat not fence the server that work well ( kernel panic ). I'd like disable or heartbeat or fencing. So we can work also with only 1 node. Thanks

I'm interested in the idea of sharing a bunch of SAS JBOD devices between two CentOS servers in an active-standby HA cluster sort of arrangement, and found something about using scsi3 persistent reservations as a fencing method. I'm not finding a lot of specifics about how this works, or how you configure two initiator systems on a SAS chain. I don't have any suitable

Rework fencing workflow. Stop using ttm helpers, use the virtio_gpu_array_* helpers instead. Due to using the gem reservation object it is initialized and ready for use before calling ttm_bo_init. So we can simply use the standard fencing workflow and drop the tricky logic which checks whenever the command is in flight still. v6: rewrite most of the patch. Signed-off-by: Gerd Hoffmann

Rework fencing workflow. Stop using ttm helpers, use the virtio_gpu_array_* helpers instead. Due to using the gem reservation object it is initialized and ready for use before calling ttm_bo_init. So we can simply use the standard fencing workflow and drop the tricky logic which checks whenever the command is in flight still. v6: rewrite most of the patch. Signed-off-by: Gerd Hoffmann

Roger, Thanks for your reply. As I understand it, for reliable fencing a node cannot be responsible for fencing itself, as it may not be functioning properly. Hence my "cross over" setup. The direct USB connection from Webserver1 to UPS-Webserver2 means that Webserver1 can fence (cut the power to) Webserver2 if the cluster software decides that it is necessary. If my UPSes were able to

Now with ttm initialization being out of the way we can simplify virtio_gpu_object_create fencing even more. No need to check whenever the command is still running after ttm_bo_init() returned. We have a fully initialized gem bo before we kick off the resource creation command, so we can simply add the fence to the bo's reservation object beforehand. Signed-off-by: Gerd Hoffmann <kraxel

Hi CentOS folks! A few days ago, I announced this to the Linux-Clustering mailing list. I think it might be of interest to some on this list, too, as most people who use CentOS are more "roll your own" types. This project was actually developed and tested on CentOS 5.4 x86_64. :) --------------------------------------------------------------------- I wanted to announce a new

I need to shutdown a cluster member for maintenance. The member is a VM and uses VM fencing, which tries to reboot the VM as part of its operation. What would be the best method to shutdown this cluster member to perform maintenance on the servers? I have already moved the cluster services to other nodes. Thank you, Ryan Palamara ZAIS Group, LLC 2 Bridge Avenue, Suite 322 Red Bank, New Jersey

Dear All, I am newbie to Linux Clustering, i have 2 standalone CentOS servers, i want to setup a cluster on those servers, to synchronize between each other, and to make a one as standby to the other, if a one fails the other will switchover. I will mostly use Apache, Mysql, and PHP. I have read the "Cluster Administration" document, i found that there are multiple methods to setup

Hi guys ... I have a problem ... here is my settup luci xen0 xen1 [root at xen1 ~]# clustat Cluster Status for XEN_Cluster @ Mon Jun 29 03:31:23 2009 Member Status: Quorate Member Name ID Status ------ ---- ---- ------ xen0.genx.local

Rework fencing workflow, starting with virtio_gpu_execbuffer_ioctl. Stop using ttm helpers, use the virtio_gpu_array_* helpers (which work on the reservation objects directly) instead. Also store the object array in struct virtio_gpu_vbuffer, so we explicitly keep a reference of all buffers used instead of depending on ttm_bo_put() checking whenever the object is actually idle before releasing