[Linux-cluster] Autostart of cman/fencing, qdiskd & cluster services when server is rebooted : can't see/mount SAN disk partition occasionally
From: sunhux G <sunhux gmail com>
To: linux clustering <linux-cluster redhat com>
Subject: [Linux-cluster] Autostart of cman/fencing, qdiskd & cluster services when server is rebooted : can't see/mount SAN disk partition occasionally
Date: Sat, 25 Apr 2009 13:39:45 +0800
My colleague has difficulty with this : he said he could only start up the various Redhat (RHES 5.1) cluster services manually after the Redhat LInux OS is rebooted/booted up :
a) cd /etc/init.d
b) ./cman start c) ./clvmd ... d) ./qdiskd ... e) ./rgmanager ...
I'm not sure if the sequence of d or e should be interchanged.
Anyway, we would like all the above to be automatic started when the
pair of linux servers (call it lnx3 and lnx4) are booted up.
Q1 : Would the following actually help or what we're missing :
Enable cluster software to start upon reboot. At each node run /sbin/chkconfig as follows:
# chkconfig --level 2345 rgmanager on # chkconfig --level 2345 gfs on # chkconfig --level 2345 clvmd on
# chkconfig --level 2345 cman on
We're not using GFS as the Netapp SAN partition is probably mounted as Unix file system (UFS)
Q2: Also, occasionally, when both servers lose connection to the network together, the SAN partition would be lost and despite rebooting the
servers and running those commands given in a-e above on the primary node alone (or both nodes), we are not able to mount the SAN partition. Sometimes after waiting for about ten minutes, it's able to mount. So
what did we miss, or is this just a matter of waiting or between the a-e services, we need to pause for a while before proceeding to the next command?
Q3: How do I know if our current SAN partition is GFS or not? (As the
previous person has left after setting up the cluster which I felt is still missing something)
Q4: How can I convert it to GFS if it's not on GFS yet?
Q5: We're not using Oracle RAC, how can I set up Oracle instances as
part of the cluster failover service?
Q6: We have a pair of cross cables (as fencing) connecting NIC ports of lnx3 & lnx4 servers : at all times, only one of the fencing NIC port's LED on lnx3's is on while on lnx4, it's also one of the NIC port's LED is on.
Is this normal?
Sorry, rather green to this, so need step by step instruction