<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Esx on Evan Hoffman</title><link>https://evan.wtf/tags/esx/</link><description>Recent content in Esx on Evan Hoffman</description><generator>Hugo</generator><language>en-US</language><copyright>Evan Hoffman</copyright><lastBuildDate>Mon, 05 Aug 2013 16:59:35 +0000</lastBuildDate><atom:link href="https://evan.wtf/tags/esx/index.xml" rel="self" type="application/rss+xml"/><item><title>"Call HostServiceSystem.Start for object XX on vCenter Server YY failed" when starting snmpd on ESXi 5.1</title><link>https://evan.wtf/2013/08/05/call-hostservicesystem-start-for-object-xx-on-vcenter-server-yy-failed-when-starting-snmpd-on-esxi-5-1/</link><pubDate>Mon, 05 Aug 2013 16:59:35 +0000</pubDate><guid>https://evan.wtf/2013/08/05/call-hostservicesystem-start-for-object-xx-on-vcenter-server-yy-failed-when-starting-snmpd-on-esxi-5-1/</guid><description>&lt;p&gt;SSH into the host and run these:&lt;/p&gt;&#10;&lt;pre tabindex="0"&gt;&lt;code&gt;~ # esxcli system snmp set --communities &#10;~ # esxcli system snmp set --enable true&#10;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;After that, make sure you have the port (161/udp) open in the firewall config and it should start up ok. (The root problem is the file /etc/vmware/snmp.xml - those commands fix it).&lt;/p&gt;</description></item><item><title>VMWare Tools Compatibility Matrix</title><link>https://evan.wtf/2013/02/20/vmware-tools-compatibility-matrix/</link><pubDate>Wed, 20 Feb 2013 10:15:22 +0000</pubDate><guid>https://evan.wtf/2013/02/20/vmware-tools-compatibility-matrix/</guid><description>&lt;p&gt;Question: If I install the latest version of VMWare Tools on a guest, what kind of compatibility do I get when I vMotion to an older version of ESX? In other words, is VMware Tools backwards compatible with older versions of ESX/ESXi?&lt;/p&gt;&#10;&lt;p&gt;Answer: Yes, it&amp;rsquo;s backwards compatible. From &lt;a href="http://partnerweb.vmware.com/comp_guide2/sim/interop_matrix.php"&gt;this tool&lt;/a&gt;:&lt;/p&gt;&#10;&lt;p&gt;&lt;a href="https://evan.wtf/evan/2013/02/20/vmware-tools-compatibility-matrix/vmware-tools-compat/"&gt;&lt;img src="https://evan.wtf/wp-content/uploads/2013/02/vmware-tools-compat-250x300.png" alt="vmware-tools-compat"&gt;&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Upgrading ESX 4.0 to ESX 4.1 with Update Manager</title><link>https://evan.wtf/2010/10/21/upgrading-esx-4-0-to-esx-4-1-with-update-manager/</link><pubDate>Thu, 21 Oct 2010 23:57:54 +0000</pubDate><guid>https://evan.wtf/2010/10/21/upgrading-esx-4-0-to-esx-4-1-with-update-manager/</guid><description>&lt;p&gt;This turned out to be so ridiculously easy I probably shouldn&amp;rsquo;t even mention it, but only because I remembered that Update Manager exists. I thought I was going to have to burn an ISO, go to the datacenter, pop the disc in, etc. But with Update Manager this is all handled remotely. Just download the files from vmware.com and upload them to your vCenter server through the client. This YouTube video by VMware walks you through the procedure:&lt;/p&gt;</description></item><item><title>The VMware datastore LUN 2TB (well, 1.99999 TB) size limit</title><link>https://evan.wtf/2010/09/24/the-vmware-datastore-lun-2tb-well-1-99999-tb-size-limit/</link><pubDate>Fri, 24 Sep 2010 16:00:15 +0000</pubDate><guid>https://evan.wtf/2010/09/24/the-vmware-datastore-lun-2tb-well-1-99999-tb-size-limit/</guid><description>&lt;p&gt;I started migrating our physical machines to VMs using VMware a few years ago and the first problem I ran into is still the most annoying one: the size limit for LUNs is, &lt;a href="http://kb.vmware.com/kb/3371739"&gt;per VMware&amp;rsquo;s docs&lt;/a&gt;, (2TB - 512B). That&amp;rsquo;s 512 bytes shy of 2TB, so basically 1.99999 TB, or 2047.999 GB. So when I create a new LUN for a datastore in the SAN the max size is 2047 GB. Now, as the VMware KB article states, &lt;strong&gt;this is a limitation of SCSI, not VMware per se&lt;/strong&gt;, but that doesn&amp;rsquo;t make it any less annoying. When I first setup ESX, I created a 5 TB LUN for the datastore. It showed up in vCenter as 1 TB. After some Googling I learned of the 2 TB limit &amp;ndash; the usable space is basically usable space = (size of lun) % 2TB, where % is &lt;a href="http://en.wikipedia.org/wiki/Modulo_operation"&gt;the modulo operator&lt;/a&gt; &amp;ndash; and found something suggesting using extents to expand the datastore across luns. I did that, but I later learned that there seems to be a consensus that extents should be avoided.&lt;/p&gt;</description></item></channel></rss>