Hi all,
First time posting to the list - Another way I use to test our
clusters Is to kernel panic the box, in addition to what was already
mentioned.
echo 1 > /proc/sys/kernel/sysrq
echo c > /proc/sysrq-trigger
---
Hope that helps.
Alberto L.
On Sep 30, 2009, at 9:37 PM, Nitin Choudhary wrote:
Hi!
Process I followed similar to what we test for Veritas Clusters.
For two node cluster:
Perform these test on both nodes.
1. Pull out the Ethernet cable, If the channel bonding is
implemented then both.
2. Reboot the server.
3. Power Cycle (forcibly)
4. Disconnect the Fiber cable to simulate fabric failures.
5. Kill the CMAN/rgmanager/qdiskd
6. Manually fence the other node.
Check messages files for any other errors.
Any one has more suggestion ?
Thanks,
Nitin
-----Original Message-----
From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-
bounces@xxxxxxxxxx] On Behalf Of Steve OBrien
Sent: Wednesday, September 30, 2009 4:32 PM
To: linux-cluster@xxxxxxxxxx
Subject: Cluster Pre-Production testing
Does anyone have a reliable method for testing a cluster before
putting
it into production?
TIA,
Steve
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
