<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Vmware-Aam on sigtar.com</title>
		<link>https://sigtar.com/tags/vmware-aam/</link>
		<description>Recent content in Vmware-Aam on sigtar.com</description>
		<generator>Hugo</generator>
		<language>en-nz</language>
		
		
		
		
			<lastBuildDate>Sat, 03 Oct 2009 00:00:00 +1300</lastBuildDate>
		
			<atom:link href="https://sigtar.com/tags/vmware-aam/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>vmware - HA issues</title>
				<link>https://sigtar.com/2009/10/03/vmware-ha-issues/</link>
				<pubDate>Sat, 03 Oct 2009 00:00:00 +1300</pubDate>
				<guid>https://sigtar.com/2009/10/03/vmware-ha-issues/</guid>
				<description>&lt;p&gt;Most of the time your HA issues are going to be DNS related. So ensure that your vcenter can ping all your hosts by FQDN without issue.  In some cases though a stubborn server may not want to play the game even when everything is configured properly.&lt;/p&gt;&#xA;&lt;p&gt;This method is considered a &amp;ldquo;last effort&amp;rdquo; as you&amp;rsquo;ll need to run some CLI commands on the ESX box. But i have found it useful in a few situations.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
