<?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>WJPatton.com &#187; ESX3.5</title>
	<atom:link href="http://wjpatton.com/index.php/tag/esx3-5/feed/" rel="self" type="application/rss+xml" />
	<link>http://wjpatton.com</link>
	<description></description>
	<lastBuildDate>Mon, 19 Jul 2010 14:45:01 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>VMware KB1007566 &#8211; Monitor Snapshot Deletion</title>
		<link>http://wjpatton.com/index.php/2010/04/vmware-kb1007566-monitor-snapshot-deletion/</link>
		<comments>http://wjpatton.com/index.php/2010/04/vmware-kb1007566-monitor-snapshot-deletion/#comments</comments>
		<pubDate>Wed, 28 Apr 2010 19:03:11 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[ESX3.5]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[snapshot]]></category>
		<category><![CDATA[timeout]]></category>
		<category><![CDATA[vmdk]]></category>
		<category><![CDATA[vmfs]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=242</guid>
		<description><![CDATA[VMware updated a KB today on how to monitor snapshot deletion.  This is especially useful for large snapshots that &#8220;time out&#8221; for vCenter because they take more than 5-10 minutes to complete.  I have been using this exact procedure for years and never thought to blog it&#8230;for some insane reason.
Read the KB here.
Basically, use the [...]]]></description>
			<content:encoded><![CDATA[<p>VMware updated a KB today on how to monitor snapshot deletion.  This is especially useful for large snapshots that &#8220;time out&#8221; for vCenter because they take more than 5-10 minutes to complete.  I have been using this exact procedure for years and never thought to blog it&#8230;for some insane reason.</p>
<p>Read the KB <a href="http://kb.vmware.com/selfservice/search.do?cmd=displayKC&amp;docType=kc&amp;externalId=1007566" target="_blank">here</a>.</p>
<p>Basically, use the watch command on the *.vmdk files in the VM datastore.  You can use -n to set a refresh interval and -d to show the change in size between refreshes.  However, the most important information is what base .vmdk file is being written to and when.  This touch timestamp will give you more information on which disk is in progress, which has not yet started, and what is already done.</p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2010/04/vmware-kb1007566-monitor-snapshot-deletion/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware KB1011170 &#8211; Checking Zero vs EagerZero Disk Status</title>
		<link>http://wjpatton.com/index.php/2010/01/vmware-kb1011170-checking-zero-vs-eagerzero-disk-status/</link>
		<comments>http://wjpatton.com/index.php/2010/01/vmware-kb1011170-checking-zero-vs-eagerzero-disk-status/#comments</comments>
		<pubDate>Tue, 19 Jan 2010 18:43:59 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[esx]]></category>
		<category><![CDATA[ESX3.5]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[esxi4]]></category>
		<category><![CDATA[KB]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=220</guid>
		<description><![CDATA[VMware has released a KB with a handy vmfstools command to check your VM&#8217;s disk status.  If the VMFS output shows a &#8220;Z&#8221; it is Zerothick with blocks that have not been written to yet.
Read the article here.
This allows you to check the disk status for options such as Fault Tolerance or Microsoft Cluster Services.  [...]]]></description>
			<content:encoded><![CDATA[<p>VMware has released a KB with a handy vmfstools command to check your VM&#8217;s disk status.  If the VMFS output shows a &#8220;Z&#8221; it is Zerothick with blocks that have not been written to yet.</p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1011170" target="_blank">Read the article here.</a></p>
<p>This allows you to check the disk status for options such as Fault Tolerance or Microsoft Cluster Services.  The disks must be in an Eagerzerothick format for these options to work.</p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2010/01/vmware-kb1011170-checking-zero-vs-eagerzero-disk-status/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware KB1009607 &#8211; Pegasus CIMSERVER Memory Leak</title>
		<link>http://wjpatton.com/index.php/2009/11/vmware-kb1009607-pegasus-cimserver-memory-leak/</link>
		<comments>http://wjpatton.com/index.php/2009/11/vmware-kb1009607-pegasus-cimserver-memory-leak/#comments</comments>
		<pubDate>Fri, 06 Nov 2009 20:56:26 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[CIM]]></category>
		<category><![CDATA[ESX3.5]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[HP]]></category>
		<category><![CDATA[KB]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=199</guid>
		<description><![CDATA[VMware has acknowledged an issue that we have been battling for some time with a Pegasus CIMSERVER memory leak.  It has been fixed under ESX 4, as it does not use Pegasus, otherwise setup a CRON job for restart Pegasus periodically.
This issue has been extremely frustrating in our environment for a very long time, and [...]]]></description>
			<content:encoded><![CDATA[<p>VMware has acknowledged an issue that we have been battling for some time with a Pegasus CIMSERVER memory leak.  It has been fixed under ESX 4, as it does not use Pegasus, otherwise setup a CRON job for restart Pegasus periodically.</p>
<p>This issue has been extremely frustrating in our environment for a very long time, and initially we suspected that HP SIM may be to blame, turns out we may have gotten that wrong.</p>
<p>We have worked with VMware Support many times, and this is the first time they have acknowledged this leak and that HP SIM is not the culprit.</p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1009607" target="_blank">Read the KB here.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/11/vmware-kb1009607-pegasus-cimserver-memory-leak/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>VMware KB1003490 &#8211; Restarting ESX Management Agents</title>
		<link>http://wjpatton.com/index.php/2009/09/vmware-kb1003490-restarting-esx-management-agents-2/</link>
		<comments>http://wjpatton.com/index.php/2009/09/vmware-kb1003490-restarting-esx-management-agents-2/#comments</comments>
		<pubDate>Tue, 08 Sep 2009 17:53:17 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[agents]]></category>
		<category><![CDATA[ESX3.5]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[KB]]></category>
		<category><![CDATA[management]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=136</guid>
		<description><![CDATA[You will find these instructions in other How To posts and links here, but I thought I would post a simple KB from VMware for quick reference.  service mgmt-vmware restart, will NOT cause a Guest to reboot or go down.
Click here for the article.
]]></description>
			<content:encoded><![CDATA[<p>You will find these instructions in other How To posts and links here, but I thought I would post a simple KB from VMware for quick reference.  service mgmt-vmware restart, will NOT cause a Guest to reboot or go down.</p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1003490" target="_blank">Click here for the article.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/09/vmware-kb1003490-restarting-esx-management-agents-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>8 ESX 3.5 Patches (4 Critical) &#8211; 8/31/09</title>
		<link>http://wjpatton.com/index.php/2009/09/8-esx-3-5-patches-4-critical-83109/</link>
		<comments>http://wjpatton.com/index.php/2009/09/8-esx-3-5-patches-4-critical-83109/#comments</comments>
		<pubDate>Tue, 01 Sep 2009 21:05:08 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[ESX3.5]]></category>
		<category><![CDATA[patching]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[Virtualization]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=115</guid>
		<description><![CDATA[8 new patches have been released for ESX 3.5 only.  These do not apply to ESX/i 4 or older versions of ESX/i 3.x.
ESX350-200908401-BG &#8211; General
ESX350-200908402-BG – Critical
ESX350-200908403-BG – General
ESX350-200908404-BG – General
ESX350-200908405-BG – Critical
ESX350-200908406-BG – Critical
ESX350-200908407-BG – General
ESX350-200908408-BG – Critical
]]></description>
			<content:encoded><![CDATA[<p>8 new patches have been released for ESX 3.5 only.  These do not apply to ESX/i 4 or older versions of ESX/i 3.x.</p>
<p><strong><a href="http://kb.vmware.com/kb/1013177" target="_blank">ESX350-200908401-BG</a></strong> &#8211; General</p>
<p><strong><a href="http://kb.vmware.com/kb/1013178" target="_blank">ESX350-200908402-BG</a></strong> – Critical</p>
<p><strong><a href="http://kb.vmware.com/kb/1013179" target="_blank">ESX350-200908403-BG</a></strong> – General</p>
<p><strong><a href="http://kb.vmware.com/kb/1013180" target="_blank">ESX350-200908404-BG</a></strong> – General</p>
<p><strong><a href="http://kb.vmware.com/kb/1013181" target="_blank">ESX350-200908405-BG</a></strong> – Critical</p>
<p><strong><a href="http://kb.vmware.com/kb/1013182" target="_blank">ESX350-200908406-BG</a></strong> – Critical</p>
<p><a href="http://kb.vmware.com/kb/1013183" target="_blank"><strong>ESX350-200908407-BG</strong></a> – General</p>
<p><a href="http://kb.vmware.com/kb/1013184" target="_blank"><strong>ESX350-200908408-BG</strong></a> – Critical</p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/09/8-esx-3-5-patches-4-critical-83109/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware KB1010213 &#8211; Basic SCSI Storage Troubleshooting</title>
		<link>http://wjpatton.com/index.php/2009/08/vmware-kb1010213-basic-scsi-storage-troubleshooting/</link>
		<comments>http://wjpatton.com/index.php/2009/08/vmware-kb1010213-basic-scsi-storage-troubleshooting/#comments</comments>
		<pubDate>Tue, 25 Aug 2009 19:25:36 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[ESX3.5]]></category>
		<category><![CDATA[ESX4]]></category>
		<category><![CDATA[KB]]></category>
		<category><![CDATA[Virtualization]]></category>

		<guid isPermaLink="false">http://wjpatton.com/?p=110</guid>
		<description><![CDATA[VMware has posted a new KB with some useful quick troubleshooting for slow storage issues.  I personally use DAVG/cmd frequently with our Fiber DMX infrastructure.
Check out here.
]]></description>
			<content:encoded><![CDATA[<p>VMware has posted a new KB with some useful quick troubleshooting for slow storage issues.  I personally use DAVG/cmd frequently with our Fiber DMX infrastructure.</p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1010213">Check out here.</a></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/08/vmware-kb1010213-basic-scsi-storage-troubleshooting/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VMware ESX 3.5 7-30-09 &#8211; KB1012543</title>
		<link>http://wjpatton.com/index.php/2009/07/vmware-esx-3-5-7-30-09-kb1012543/</link>
		<comments>http://wjpatton.com/index.php/2009/07/vmware-esx-3-5-7-30-09-kb1012543/#comments</comments>
		<pubDate>Thu, 30 Jul 2009 17:04:52 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[ESX3.5]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[VMware has released ESX 3.5 patches.  6 Patches, 4 are Critical.  KB1012543 is most interesting overall.  Hit the jump for links and more information.

Click Here to View the VMware KB
Interesting bits from this KB:

The maximum username length of UserAccount in the VMware VI Toolkit is increased from 16 to 32 characters.


Fixes an hostd memory leak [...]]]></description>
			<content:encoded><![CDATA[<p>VMware has released ESX 3.5 patches.  6 Patches, 4 are Critical.  KB1012543 is most interesting overall.  Hit the jump for links and more information.<br />
<span id="more-74"></span></p>
<p><a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;cmd=displayKC&amp;externalId=1012543">Click Here to View the VMware KB</a></p>
<p>Interesting bits from this KB:</p>
<ul>
<li>The maximum username length of UserAccount in the VMware VI Toolkit is increased from 16 to 32 characters.</li>
</ul>
<ul>
<li>Fixes an hostd memory leak issue with HTTP connection recycling when communicating with UI, SDK etc.</li>
</ul>
<p>I find the second point most important, as we provide &#8220;iLO-like&#8221; access to our users using the WebService via VirtualCenter.  VMware has stated in the past we should turn this off to prevent memory leak issues, however it was not an option.  This is certainly a welcome fix!</p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/07/vmware-esx-3-5-7-30-09-kb1012543/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Disconnected Hosts &#8211; Hostd</title>
		<link>http://wjpatton.com/index.php/2009/02/disconnected-hosts-hostd/</link>
		<comments>http://wjpatton.com/index.php/2009/02/disconnected-hosts-hostd/#comments</comments>
		<pubDate>Thu, 05 Feb 2009 15:33:45 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[ESX3.5]]></category>
		<category><![CDATA[vSphere]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Good article about troubleshooting Hostd (mgmt-vmware) issues.http://blog.colovirt.com/2008/10/27/reconnecting-disconnected-vmware-esx-server-to-virtual-infrastructure/
]]></description>
			<content:encoded><![CDATA[<p>Good article about troubleshooting Hostd (mgmt-vmware) issues.<br /><span id="more-69"></span><br />http://blog.colovirt.com/2008/10/27/reconnecting-disconnected-vmware-esx-server-to-virtual-infrastructure/</p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2009/02/disconnected-hosts-hostd/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Query Orphan/Old/Off/Snapshot VMDKs</title>
		<link>http://wjpatton.com/index.php/2008/11/query-orphanoldoffsnapshot-vmdks/</link>
		<comments>http://wjpatton.com/index.php/2008/11/query-orphanoldoffsnapshot-vmdks/#comments</comments>
		<pubDate>Mon, 24 Nov 2008 18:59:44 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[ESX3.5]]></category>
		<category><![CDATA[vSphere]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[find -iname &#34;*-flat.vmdk&#34; -mtime +7 -ls 
 you could identify vmdk files older then 7 days that have not been modified and are either off or orphaned. 
 or 
 find -iname &#34;*-delta.vmdk&#34; -mtime +7 -ls 
 to find old snapshots 		
]]></description>
			<content:encoded><![CDATA[<p>find -iname &quot;*-flat.vmdk&quot; -mtime +7 -ls </p>
<p> you could identify vmdk files older then 7 days that have not been modified and are either off or orphaned. </p>
<p> or </p>
<p> find -iname &quot;*-delta.vmdk&quot; -mtime +7 -ls </p>
<p> to find old snapshots 		<br /><span id="more-68"></span></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2008/11/query-orphanoldoffsnapshot-vmdks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VPXA Re-install</title>
		<link>http://wjpatton.com/index.php/2008/10/vpxa-re-install/</link>
		<comments>http://wjpatton.com/index.php/2008/10/vpxa-re-install/#comments</comments>
		<pubDate>Thu, 02 Oct 2008 15:59:14 +0000</pubDate>
		<dc:creator>wjpatton</dc:creator>
				<category><![CDATA[VMware]]></category>
		<category><![CDATA[ESX3.5]]></category>

		<guid isPermaLink="false"></guid>
		<description><![CDATA[Double check the version of the VirtualCenter Agent:
# rpm -qa grep vpxa
(For Example) VMware-vpxa-2.0.1-32042
To stop mgmt-vmware:
# service mgmt-vmware stop
Stopping VMware ESX Server Management services:
VMware ESX Server Host Agent Services [ OK ]
VMware ESX Server Host Agent Watchdog [ OK ]
VMware ESX Server Host Agent [ OK ]
To stop vpxa:
# /etc/init.d/vmware-vpxa stop
Stopping vmware-vpxa: [ OK ]
Uninstall [...]]]></description>
			<content:encoded><![CDATA[<p>Double check the version of the VirtualCenter Agent:</p>
<p># rpm -qa grep vpxa</p>
<p>(For Example) VMware-vpxa-2.0.1-32042</p>
<p>To stop mgmt-vmware:</p>
<p># service mgmt-vmware stop</p>
<p>Stopping VMware ESX Server Management services:</p>
<p>VMware ESX Server Host Agent Services [ OK ]</p>
<p>VMware ESX Server Host Agent Watchdog [ OK ]</p>
<p>VMware ESX Server Host Agent [ OK ]</p>
<p>To stop vpxa:</p>
<p># /etc/init.d/vmware-vpxa stop</p>
<p>Stopping vmware-vpxa: [ OK ]</p>
<p>Uninstall vpxa:</p>
<p># rpm -e VMware-vpxa-2.0.1-32042</p>
<p>Stopping vmware-vpxa: [ OK ]</p>
<p>warning: /etc/vmware/vpxa.cfg saved as /etc/vmware/vpxa.cfg.rpmsave</p>
<p>To make sure vpxa is no longer there:</p>
<p># rpm -qa grep vpxa</p>
<p># rpm -qa grep vpx</p>
<p>Restart up mgmt-vmware service:</p>
<p># service mgmt-vmware start</p>
<p>Starting VMware ESX Server Management services:</p>
<p>VMware ESX Server Host Agent (background) [ OK ]</p>
<p>Availability report startup (background) [ OK ]</p>
<p>After reconnecting to the VI3 host from VirtualCenter, double check to make sure the version of the VirtualCenter Agent is right:</p>
<p># rpm -qa grep vpxa</p>
<p>VMware-vpxa-2.0.1-33643</p>
<p>&nbsp;</p>
<p>This example uses 2.0.1, but instructions are still valid for all 2.x versions of VirtualCenter and ESX 3.x</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><span id="more-67"></span></p>
]]></content:encoded>
			<wfw:commentRss>http://wjpatton.com/index.php/2008/10/vpxa-re-install/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
