Jump to content
Main menu
Main menu
move to sidebar
hide
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
TetraWiki
Search
Search
Appearance
Create account
Log in
Personal tools
Create account
Log in
Pages for logged out editors
learn more
Contributions
Talk
Editing
RHCS HA Over NFS at BITS Pilani
Page
Discussion
English
Read
Edit
View history
Tools
Tools
move to sidebar
hide
Actions
Read
Edit
View history
General
What links here
Related changes
Special pages
Page information
Appearance
move to sidebar
hide
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
[[category:Bits pilani]] ==<center>'''HIGH AVAILABILITY OVER NFS'''</center>== '''NAVDEEP MATHUR''' =='''ISSUE'''== * Need to set up highly available NFS * Need clients to connect to an NFS service that can gracefully fail over to another system should the node providing the NFS service fail =='''CLUSTERING'''== * First ensure both servers are NTP sync'd and ensure that their hosts file contain entries of each other, and are the same. * We first install the cluster packages '''<nowiki>#</nowiki>'''yum groupinstall ‘Clustering’ ‘ClusterStorage’ =='''FENCING'''== We now change cluster.conf manually to define our fencing devices for the base machines. (While luci-ricci can be used, I personally prefer editing the conf file directly due to the random bugs that keep popping up in luci-ricci , this time error occurred when adding fencing devices or resources/services.) The fence that we are using is IBM’s IPMILAN v2. We need the IP address, username and password for access the Management interface. Management Interface (IPMI) By default username and password is “USERID” and “PASSWORD” So first, we shall put the base machines on a cluster. We modify 'cluster.conf' to include the fencing agents, 'fence_bits' and 'fence_bits1', as shown: <nowiki><?xml version="1.0"?></nowiki> <nowiki><cluster alias="nfs-cluster" config_version="19" name="nfs-cluster"></nowiki> <nowiki><cman expected_votes="1" two_node="1"></nowiki> <nowiki></cman></nowiki> <nowiki><clusternodes></nowiki> <nowiki><clusternode name="ibm-39.bits.ac" nodeid="1"></nowiki> <nowiki><fence></nowiki> <nowiki><method name="1"></nowiki> <nowiki><device name="ibm-39_fence"/></nowiki> <nowiki></method></nowiki> <nowiki></fence></nowiki> <nowiki></clusternode></nowiki> <nowiki><clusternode name="ibm-40.bits.ac" nodeid="2"></nowiki> <nowiki><fence></nowiki> <nowiki><method name="1"></nowiki> <nowiki><device name="ibm-40_fence"/></nowiki> <nowiki></method></nowiki> <nowiki></fence></nowiki> <nowiki></clusternode></nowiki> <nowiki></clusternodes></nowiki> <nowiki><rm></nowiki> <nowiki><resources></nowiki> <nowiki><ip address="172.20.4.43" monitor_link="on" sleeptime="10"/></nowiki> <nowiki><script file="/etc/init.d/nfs" name="nfs"/></nowiki> <nowiki></resources></nowiki> <nowiki><service autostart="1" name="nfs" recovery="relocate"></nowiki> <nowiki><ip ref="172.20.4.43"/></nowiki> <nowiki><script ref="nfs"/></nowiki> <nowiki></service></nowiki> <nowiki></rm></nowiki> <nowiki><fencedevices></nowiki> <nowiki><fencedevice agent="fence_ipmilan" auth="password" ipaddr="172.20.4.41" login="fence_bits" name="ibm-39_fence" passwd="password"/></nowiki> <nowiki><fencedevice agent="fence_ipmilan" auth="password" ipaddr="172.20.4.42" login="fence_bits1" name="ibm-40_fence" passwd="password"/></nowiki> <nowiki></fencedevices></nowiki> <nowiki><fence_daemon clean_start="0" post_fail_delay="0" post_join_delay="3"/></nowiki> <nowiki></cluster></nowiki> Then Rsync this file to the other machine as well. On both the servers simultaneously : <nowiki>#service cman start ; chkconfig cman on</nowiki> <nowiki># service rgmanager start ; chkconfig cman on</nowiki> <nowiki>#clustat</nowiki> [[Image:bits-2.png]] =='''TROUBLESHOOTING'''== Checking cluster service: <nowiki># clustat </nowiki> Enabling cluster service: <nowiki># clusvcadm -e <cluster service name> -m <node hostname></nowiki> Disabling cluster service: <nowiki># clusvcadm -d <cluster service name></nowiki>
Summary:
Please note that all contributions to TetraWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
TetraWiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)