<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/wordpress-mu-1.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Discussion on: ESX 3.5: Configuring for HA errors</title>
	<link>http://itknowledgeexchange.techtarget.com/virtualization-pro/esx-configuring-for-ha-errors-what-to-do/</link>
	<description></description>
	<pubDate>Fri, 10 Oct 2008 20:28:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=wordpress-mu-1.2.1</generator>

	<item>
		<title>By: Akutz</title>
		<link>http://itknowledgeexchange.techtarget.com/virtualization-pro/esx-configuring-for-ha-errors-what-to-do/#comment-19</link>
		<author>Akutz</author>
		<pubDate>Thu, 17 Jan 2008 00:46:30 +0000</pubDate>
		<guid>http://itknowledgeexchange.techtarget.com/virtualization-pro/esx-configuring-for-ha-errors-what-to-do/#comment-19</guid>
		<description>Great job Rick! Just to add a little bit to what Rick has already explained quite thoroughly, you can also edit the host files on the ESX server(s) in order to make this work (http://searchservervirtualization.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid94_gci1281218,00.html). The HA agent runs *on* the ESX server and despite appearances relies on VC for configuration, not to function. HA will work if the VC is down. This means that all of the DNS matching must function from the ESX server, and that is where it can be fixed.</description>
		<content:encoded><![CDATA[<p>Great job Rick! Just to add a little bit to what Rick has already explained quite thoroughly, you can also edit the host files on the ESX server(s) in order to make this work (http://searchservervirtualization.techtarget.com/expert/KnowledgebaseAnswer/0,289625,sid94_gci1281218,00.html). The HA agent runs *on* the ESX server and despite appearances relies on VC for configuration, not to function. HA will work if the VC is down. This means that all of the DNS matching must function from the ESX server, and that is where it can be fixed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
