<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Malaysia VMware Communities &#187; cluster</title>
	<atom:link href="http://malaysiavm.com/blog/tag/cluster/feed/" rel="self" type="application/rss+xml" />
	<link>http://malaysiavm.com/blog</link>
	<description></description>
	<lastBuildDate>Mon, 21 Nov 2011 15:50:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Microsoft Cluster on VMware ESX 4.1</title>
		<link>http://malaysiavm.com/blog/microsoft-cluster-on-vmware-esx-4-1/</link>
		<comments>http://malaysiavm.com/blog/microsoft-cluster-on-vmware-esx-4-1/#comments</comments>
		<pubDate>Thu, 06 Jan 2011 09:28:35 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[Server]]></category>
		<category><![CDATA[Storage]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[cluster]]></category>
		<category><![CDATA[ESX 4.1]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=2161</guid>
		<description><![CDATA[To deploy Microsoft Cluster on VMware ESX 4.1 is not new thing, you may need to choose the right storage protocol in this case. According to VMware best practices, on Fiber Channel SAN will be supported with the current version. You will need to present the Share Storage via FC LUN to build the microsoft [...]]]></description>
			<content:encoded><![CDATA[<p>To deploy Microsoft Cluster on VMware ESX 4.1 is not new thing, you may need to choose the right storage protocol in this case. According to VMware best practices, on Fiber Channel SAN will be supported with the current version. You will need to present the Share Storage via FC LUN to build the microsoft cluster in VMware environment. ISCSI &amp; NFS both are not supported in this case.</p>
<p>You can view the Official VMware Documentation from <a href="http://www.vmware.com/pdf/vsphere4/r41/vsp_41_mscs.pdf">here</a>.</p>
<p><span id="more-2161"></span></p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/microsoft-cluster-on-vmware-esx-4-1/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>Running SuSE Linux Cluster on VMware</title>
		<link>http://malaysiavm.com/blog/running-suse-linux-cluster-on-vmware/</link>
		<comments>http://malaysiavm.com/blog/running-suse-linux-cluster-on-vmware/#comments</comments>
		<pubDate>Fri, 12 Sep 2008 07:13:21 +0000</pubDate>
		<dc:creator>jlchannel</dc:creator>
				<category><![CDATA[Operating Systems]]></category>
		<category><![CDATA[Tips]]></category>
		<category><![CDATA[cluster]]></category>
		<category><![CDATA[ESX]]></category>
		<category><![CDATA[HA]]></category>
		<category><![CDATA[heartbeat]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[SuSE]]></category>
		<category><![CDATA[VM]]></category>
		<category><![CDATA[VMware]]></category>

		<guid isPermaLink="false">http://malaysiavm.com/blog/?p=251</guid>
		<description><![CDATA[What? Running SuSE Linux Cluster on VMware ESX? Basically if you have VMware HA and DRS enable, your virtual machine is running on cluster mode. Then, why running Linux cluster on VMware? Who care? It&#8217;s just for fun and for personal testing purpose only. 1st, create two SuSE Linux(I&#8217;m running SLES 10 SP2) on VMware [...]]]></description>
			<content:encoded><![CDATA[<p>What? Running <a href="http://malaysiavm.com/blog/tag/suse">SuSE</a> <a href="http://malaysiavm.com/blog/tag/linux">Linux</a> <a href="http://malaysiavm.com/blog/tag/cluster">Cluster</a> on VMware ESX? Basically if you have VMware <a href="http://malaysiavm.com/blog/tag/ha">HA</a> and <a href="http://malaysiavm.com/blog/tag/drs">DRS</a> enable, your virtual machine is running on cluster mode. Then, why running Linux cluster on <a href="http://malaysiavm.com/blog/tag/vmware">VMware</a>? Who care? It&#8217;s just for fun and for personal testing purpose only.</p>
<p>1st, create two SuSE Linux(I&#8217;m running SLES 10 SP2) on VMware running on same network said cluster1(192.168.1.1) and cluster2(192.168.1.2).</p>
<p>2nd, add new hard disk on VMware infrastructure client. Please remember to choose &#8216;<strong>Use an existing virtual disk</strong>&#8216;.</p>
<p><img src="http://www.malaysiavm.com/images/hdd.JPG" alt="VMware" width="516" height="267" /><br />
Click <a href="http://www.malaysiavm.com/images/hdd.JPG" rel="shadowbox[sbpost-251];player=img;">here</a> for bigger image.</p>
<p>3rd, install and configure Linux cluster <a href="http://malaysiavm.com/blog/tag/heartbeat">heartbeat</a>.</p>
<p><strong>Make sure you have heartbeat RPM install</strong><br />
cluster1:~ # rpm -qa|grep heartbeat<br />
sles-heartbeat_en-10.1-0.20<br />
heartbeat-pils-2.1.3-0.9<br />
heartbeat-stonith-2.1.3-0.9<br />
yast2-heartbeat-2.13.13-0.3<br />
heartbeat-2.1.3-0.9</p>
<p>cluster2:~ # rpm -qa|grep heartbeat<br />
sles-heartbeat_en-10.1-0.20<br />
heartbeat-pils-2.1.3-0.9<br />
heartbeat-stonith-2.1.3-0.9<br />
yast2-heartbeat-2.13.13-0.3<br />
heartbeat-2.1.3-0.9</p>
<p><strong>Install Linux cluster heartbeat RPM package if you haven&#8217;t install</strong><br />
cluster1:~ # rpm -ivh heartbeat-xxxxxx<br />
cluster1:~ # rpm -ivh heartbeat-stonith-xxxxxx<br />
and etc</p>
<p><strong>Edit Authentication file (same for cluster1 and cluster2)</strong><br />
cluster1:~ #vi /etc/ha.d/authkeys<br />
auth 2<br />
2 sha1 MVM_CLUS2!</p>
<p><span id="more-251"></span><br />
<strong>Edit <a href="http://www.malaysiavm.com/blog/tag/ha">HA</a> configuration file</strong><br />
cluster1<br />
cluster1:~ #vi /etc/ha.d/ha.cf<br />
logfile /var/log/ha-log<br />
logfacility local0<br />
node cluster1<br />
node cluster2<br />
keepalive 1<br />
warntime 30<br />
deadtime 60<br />
initdead 120<br />
udpport 694<br />
ucast eth0 192.168.1.1<br />
ucast eth0 192.168.1.2<br />
auto_failback off<br />
ping_group group1 192.168.1.254<br />
respawn hacluster /usr/lib/heartbeat/ipfail<br />
watchdog /dev/watchdog</p>
<p>cluster2<br />
cluster2:~ #vi /etc/ha.d/ha.cf<br />
logfile /var/log/ha-log<br />
logfacility local0<br />
node cluster2<br />
node cluster1<br />
keepalive 1<br />
warntime 30<br />
deadtime 60<br />
initdead 120<br />
udpport 694<br />
ucast eth0 192.168.1.2<br />
ucast eth0 192.168.1.1<br />
auto_failback off<br />
ping_group group1 192.168.1.254<br />
respawn hacluster /usr/lib/heartbeat/ipfail<br />
watchdog /dev/watchdog</p>
<p><strong>Edit HA Resource file (same for cluster1 and cluster2)</strong><br />
cluster1:~ #vi /etc/ha.d/haresources<br />
cluster1 192.168.1.100 \<br />
Filesystem::/dev/sdb1::/db::ext3</p>
<p><strong>Make sure you can see hard disk partition on both servers</strong><br />
cluster1:~ # cat /proc/partitions<br />
8    17   20964793 sdb1<br />
cluster2:~ # cat /proc/partitions<br />
8    17   20964793 sdb1</p>
<p><strong>Configure and format hard disk partition</strong><br />
cluster1:~ # fdisk /dev/sdb1<br />
press <strong>n</strong> add a new partition<br />
press <strong>p</strong> primary partition<br />
press <strong>1</strong> partition number<br />
First cylinder, press <strong>ENTER</strong><br />
Last cylinder or +size or +sizeM or +sizeK, press <strong>ENTER</strong><br />
press <strong>p</strong> print the partition table<br />
press <strong>w</strong> write table to disk and exit</p>
<p>cluster1:~ # mkfs.ext3 /dev/sdb1</p>
<p><strong>Create new folder on both servers</strong><br />
cluster1:~ # mkdir /db<br />
cluster2:~ # mkdir /db</p>
<p><strong>Startup <a href="http://malaysiavm.com/blog/tag/heartbeat">heartbeat</a> services</strong><br />
cluster1:~ # chkconfig heartbeat on<br />
cluster1:~ # /etc/init.d/heartbeat start<br />
cluster2:~ # chkconfig heartbeat on<br />
cluster2:~ # /etc/init.d/heartbeat start</p>
<p>You should be able to see <em>/db</em> mounted and IP address <em>192.168.1.100</em> is up on <em>cluster1</em>(active). If you turn <strong>OFF</strong> cluster1 server and you should see <em>cluster2</em> running on <strong>ACTIVE</strong> mode. </p>
<p>Congratulations! You&#8217;re done! Enjoy!</p>
]]></content:encoded>
			<wfw:commentRss>http://malaysiavm.com/blog/running-suse-linux-cluster-on-vmware/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.350 seconds -->

