<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: How to Ruin Your Weekend and Other Hazards of Mis-Configured HA</title>
	<atom:link href="http://www.mooselogic.com/blog/how-to-ruin-your-weekend-and-other-hazards-of-mis-configured-ha/feed" rel="self" type="application/rss+xml" />
	<link>http://www.mooselogic.com/blog/how-to-ruin-your-weekend-and-other-hazards-of-mis-configured-ha</link>
	<description>Using technology to make businesses better</description>
	<lastBuildDate>Sun, 29 Jan 2012 15:26:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: John</title>
		<link>http://www.mooselogic.com/blog/how-to-ruin-your-weekend-and-other-hazards-of-mis-configured-ha#comment-691</link>
		<dc:creator>John</dc:creator>
		<pubDate>Sun, 29 Jan 2012 15:26:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.mooselogic.com/blog/?p=157#comment-691</guid>
		<description>Excellent explanation, never actually realized that Xenserver would &#039;fence&#039; to protect it&#039;s data. Yeah, it happened to me too when a SAN controller did a failover. Three server setup with XS5.0, using HBA&#039;s. The only one that remained online was the pool master, the other 2 restarted kicking off VM&#039;s and all users at 8.17 in the morning. Ouch! The heartbeat link was gone for about 50 seconds due to the failover. Pretty short time on HA timeout too, 30 seconds is not much. Very interesting article, kudos!</description>
		<content:encoded><![CDATA[<p>Excellent explanation, never actually realized that Xenserver would &#8216;fence&#8217; to protect it&#8217;s data. Yeah, it happened to me too when a SAN controller did a failover. Three server setup with XS5.0, using HBA&#8217;s. The only one that remained online was the pool master, the other 2 restarted kicking off VM&#8217;s and all users at 8.17 in the morning. Ouch! The heartbeat link was gone for about 50 seconds due to the failover. Pretty short time on HA timeout too, 30 seconds is not much. Very interesting article, kudos!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ben Piper</title>
		<link>http://www.mooselogic.com/blog/how-to-ruin-your-weekend-and-other-hazards-of-mis-configured-ha#comment-685</link>
		<dc:creator>Ben Piper</dc:creator>
		<pubDate>Tue, 27 Dec 2011 15:29:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.mooselogic.com/blog/?p=157#comment-685</guid>
		<description>This is a fantastic explanation of host self-fencing!  Thanks!</description>
		<content:encoded><![CDATA[<p>This is a fantastic explanation of host self-fencing!  Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Meyer</title>
		<link>http://www.mooselogic.com/blog/how-to-ruin-your-weekend-and-other-hazards-of-mis-configured-ha#comment-668</link>
		<dc:creator>Meyer</dc:creator>
		<pubDate>Tue, 13 Sep 2011 13:06:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.mooselogic.com/blog/?p=157#comment-668</guid>
		<description>1rst, sorry 4 my poor english. Our citrix server farm (3) went into emergency mode after the ups starts (!!!) after a brown out in our district. After returning to the office,  i checked the server. All running (including our heartbeat/nas), allthough not reachable via xencenter. Ping, ok, putty a mess, lousy responses, xsconsole shows no nics. you may ask for the vms, well they were running. I was really surprised.  Ok, sherlock mode on and i found the reason why. All three server were plugged on the same switch. the switch was temporarily out of order (a few seconds, imho) until it returned to normal operation. These few seconds lasts in the result, that none of the server could find his heartbeat to the iSCSI/nas and fences (emergency mode). I seperate now the three server on different switches an add a single ups for the switch and the NAS (keeping up the heartbeat). Btw. the server are operated in a server room which is protected by a huge ups. Scaring (...)
Last but not least: If one of the server without ha enabled (--forced) should be back to operation in the Pool, don&#039;t search 4 an xe command, just disable HA for the pool and activate it again, the missing slave joins the pool, thats all.</description>
		<content:encoded><![CDATA[<p>1rst, sorry 4 my poor english. Our citrix server farm (3) went into emergency mode after the ups starts (!!!) after a brown out in our district. After returning to the office,  i checked the server. All running (including our heartbeat/nas), allthough not reachable via xencenter. Ping, ok, putty a mess, lousy responses, xsconsole shows no nics. you may ask for the vms, well they were running. I was really surprised.  Ok, sherlock mode on and i found the reason why. All three server were plugged on the same switch. the switch was temporarily out of order (a few seconds, imho) until it returned to normal operation. These few seconds lasts in the result, that none of the server could find his heartbeat to the iSCSI/nas and fences (emergency mode). I seperate now the three server on different switches an add a single ups for the switch and the NAS (keeping up the heartbeat). Btw. the server are operated in a server room which is protected by a huge ups. Scaring (&#8230;)<br />
Last but not least: If one of the server without ha enabled (&#8211;forced) should be back to operation in the Pool, don&#8217;t search 4 an xe command, just disable HA for the pool and activate it again, the missing slave joins the pool, thats all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://www.mooselogic.com/blog/how-to-ruin-your-weekend-and-other-hazards-of-mis-configured-ha#comment-543</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Fri, 18 Feb 2011 20:07:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.mooselogic.com/blog/?p=157#comment-543</guid>
		<description>This fixed me http://support.citrix.com/article/CTX126382</description>
		<content:encoded><![CDATA[<p>This fixed me <a href="http://support.citrix.com/article/CTX126382" rel="nofollow">http://support.citrix.com/article/CTX126382</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheG</title>
		<link>http://www.mooselogic.com/blog/how-to-ruin-your-weekend-and-other-hazards-of-mis-configured-ha#comment-431</link>
		<dc:creator>TheG</dc:creator>
		<pubDate>Fri, 24 Sep 2010 21:14:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.mooselogic.com/blog/?p=157#comment-431</guid>
		<description>Nice Write Up (though could be misleading in some areas until you get to the comments)... It may however be a good idea to indicate that the afore mentioned is no longer an issue within the writeup, especially since you have confirmed same in your lab.

What version of XenServer are you testing with?</description>
		<content:encoded><![CDATA[<p>Nice Write Up (though could be misleading in some areas until you get to the comments)&#8230; It may however be a good idea to indicate that the afore mentioned is no longer an issue within the writeup, especially since you have confirmed same in your lab.</p>
<p>What version of XenServer are you testing with?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sid Herron</title>
		<link>http://www.mooselogic.com/blog/how-to-ruin-your-weekend-and-other-hazards-of-mis-configured-ha#comment-408</link>
		<dc:creator>Sid Herron</dc:creator>
		<pubDate>Wed, 08 Sep 2010 02:49:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.mooselogic.com/blog/?p=157#comment-408</guid>
		<description>@Oliver - Thanks for your input.  Your comment prompted us to go back and re-test with the latest version of XenServer.  Although our testing is not yet complete, it does appear that some of the conditions we described in this blog post no longer cause both XenServers to fence. Once our testing is complete, we&#039;ll be posting an update on our findings.</description>
		<content:encoded><![CDATA[<p>@Oliver &#8211; Thanks for your input.  Your comment prompted us to go back and re-test with the latest version of XenServer.  Although our testing is not yet complete, it does appear that some of the conditions we described in this blog post no longer cause both XenServers to fence. Once our testing is complete, we&#8217;ll be posting an update on our findings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Oliver</title>
		<link>http://www.mooselogic.com/blog/how-to-ruin-your-weekend-and-other-hazards-of-mis-configured-ha#comment-403</link>
		<dc:creator>Oliver</dc:creator>
		<pubDate>Mon, 30 Aug 2010 11:11:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.mooselogic.com/blog/?p=157#comment-403</guid>
		<description>I don&#039;t understand this. I have two Xen Servers in a pool and I have no problems. I test it. First I remove the first server from network, the protectet machine starts on the other server, than I test it with the other server, also no problem. I have no fencing......</description>
		<content:encoded><![CDATA[<p>I don&#8217;t understand this. I have two Xen Servers in a pool and I have no problems. I test it. First I remove the first server from network, the protectet machine starts on the other server, than I test it with the other server, also no problem. I have no fencing&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: XenServer Host Is In Emergency Mode &#124; Moose Logic Blog</title>
		<link>http://www.mooselogic.com/blog/how-to-ruin-your-weekend-and-other-hazards-of-mis-configured-ha#comment-173</link>
		<dc:creator>XenServer Host Is In Emergency Mode &#124; Moose Logic Blog</dc:creator>
		<pubDate>Thu, 15 Apr 2010 22:50:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.mooselogic.com/blog/?p=157#comment-173</guid>
		<description>[...] stranded and goes into emergency mode to protect its own VMs. There are other ways this can happen (an incorrectly configured pool with HA turned on for example), but this is the most common reason that I have personally [...]</description>
		<content:encoded><![CDATA[<p>[...] stranded and goes into emergency mode to protect its own VMs. There are other ways this can happen (an incorrectly configured pool with HA turned on for example), but this is the most common reason that I have personally [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Charles Stevenson</title>
		<link>http://www.mooselogic.com/blog/how-to-ruin-your-weekend-and-other-hazards-of-mis-configured-ha#comment-57</link>
		<dc:creator>Charles Stevenson</dc:creator>
		<pubDate>Sat, 06 Feb 2010 06:31:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.mooselogic.com/blog/?p=157#comment-57</guid>
		<description>Thanks for this post!  I have a three XenServer pool and had enabled HA tonight around midnight whilst doing other sorts of network maint... recabling a few things... I must&#039;ve bumped a cable and suddenly both servers at the building I was in rebooted.  I thought perhaps there was a power issue in the rack or that I&#039;d been a klutz... then I looked in XenCenter and all three servers had &#039;fenced&#039;.  Ugh.  At least I found this out late at night and read your post.  I&#039;m going to look into getting enough redundancy with switches and NIC bonding so that I can have HA enabled.</description>
		<content:encoded><![CDATA[<p>Thanks for this post!  I have a three XenServer pool and had enabled HA tonight around midnight whilst doing other sorts of network maint&#8230; recabling a few things&#8230; I must&#8217;ve bumped a cable and suddenly both servers at the building I was in rebooted.  I thought perhaps there was a power issue in the rack or that I&#8217;d been a klutz&#8230; then I looked in XenCenter and all three servers had &#8216;fenced&#8217;.  Ugh.  At least I found this out late at night and read your post.  I&#8217;m going to look into getting enough redundancy with switches and NIC bonding so that I can have HA enabled.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frost Hon</title>
		<link>http://www.mooselogic.com/blog/how-to-ruin-your-weekend-and-other-hazards-of-mis-configured-ha#comment-48</link>
		<dc:creator>Frost Hon</dc:creator>
		<pubDate>Tue, 26 Jan 2010 10:18:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.mooselogic.com/blog/?p=157#comment-48</guid>
		<description>Excellent Post, really love how your explain everything in detail. we are testing our HA as well and came across your article.</description>
		<content:encoded><![CDATA[<p>Excellent Post, really love how your explain everything in detail. we are testing our HA as well and came across your article.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

