Search results

Heh, I am on the learning curve, thank you for this, I corrected my config :D

It seems you are missing two_node="1" in cman.. at least this is the correct config for 2 nodes cluster with quorum

12 SAS 10k rpm drives in a single raid10 configuration should achieve about 840iops (140iops per drive), you only get 463 ( in one of your tests ). Can you test without anything running except fio? I get a better performance with 4 drives (15k rpm) in raid5.. Of course without write caching...

What is a bit weird to me is if your server has no power what are the chances that the PDU has power so you can control it? ( Except with some batteries to maintain the network connectivity and functionality ). Maybe just if you'll have a power-supply problem on the server. I didn't say that you...

fence agent fails because it cannot connect to IPMI/iLO.. it expects a successful command to be performed on the ipmi device and since you pull the power plug from the node, that's not possible. So the node is physically fenced, it will not overlap with cluster communication, network or storage...

Can you tell me exactly what disk drives are you using? Also did you activate in your raid setup write back caching? do you have BBU installed on the perc?

What I see wrong with your approach is that you want computing redundancy ( 2 nodes ), but for storage it seems you have a major single-point-of-failure having a single box without internal redundancy ( yes I imagine it would have some raid, but it's still a simple box with one motherboard )...

What is that firewall you mention in the traceroute? is it a vm and you route everything through it? on the same subnet?

I would test I/O performance with "fio" Just apt-get install fio And then use the command: fio /usr/share/doc/fio/examples/iometer-file-access-server First edit the file and at the [global] section add: "directory = /var/lib/vz" if you want to test the performance of /dev/mapper/pve-data You do...

Please give us the output of: ip route and iptables -L -n and iptables -L -n -t nat

Please give us an output of: ip route and iptables -L -n

I am not exactly sure how to do it, but you should have a main fencing device: IPMI and then you can just have a call to /bin/true ( http://osdir.com/ml/linux-cluster/2010-12/msg00012.html )

Click on datacenter leaf of the tree, go to storage, select the storage you want, click edit and then at the drop-list select backup. This way you configure a storage as backup capable ( you can also select how many backup instances per vm can pe stored. )

You could use an ethernet controlled PDU to achieve fencing, however I am thinking that the only reason for your IPMI not to work is power outage to that node, then you could setup also a secondary fake fencing device that would return success no matter what so that rgmanager would restart the...

Maybe I misread this: "You also have to choose shared nics which means you can reach IPMI web interface on all nics in the server" Did you choose one NIC or all the NICs for IPMI? I have no idea about iLo.. so maybe I am asking something stupid and choosing all NICs it's not possible, but I...

I suspect that the way of BMC port sharing on all interfaces works ( it has to do some internal bridging ) together with bridging interfaces via the host causes a loop. You could use a different vlan for the BMC ( i guess it's configurable ) and you can bring up an eth0.vlan with a different...

Because you reject FORWARDING with iptables -P FORWARD DROP You should have something like iptables -A FORWARD -s vms_subnet -j ACCEPT and iptables -A FORWARD -d vms_subnet -j ACCEPT together with the drop policy or just make the policy ACCEPT and do per VM firewall, or if you really want a...

Although I read this before, it seems I forgot some important things mentioned here: https://alteeve.ca/w/2-Node_Red_Hat_KVM_Cluster_Tutorial "Hooking DRBD Into The Cluster's Fencing" for example: "We will use a script, written by Lon Hohberger of Red Hat. This script will capture fence calls...

1. Fencing means isolating a node that maybe is working on its own outside the cluster control. You want this to prevent a case that such a node is writing to the shared storage and probably overlapping with a node that is entitled ( by the cluster ) to write in that area. So when a node is...

But I thought you just mentioned that you can be in a situation where from the cluster perspective everything is fine ( nodes inter-operate properly ), but drbd fails for some reason. In this situation fencing will not get triggered right? Since you gave my that perspective, I have some trouble...