<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>V-IT, I AM GOING THROUGH IT</title>
    <link>http://communities.vmware.com/blogs/eagleh</link>
    <description>VIRTUALIZING IS REVOLUTIONARY! I AM GOING THROUGH IT....</description>
    <pubDate>Thu, 19 Jun 2008 19:34:43 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2008-06-19T19:34:43Z</dc:date>
    <item>
      <title>HP SIM to monitor ESX hosts</title>
      <link>http://communities.vmware.com/blogs/eagleh/2008/06/19/hp-sim-to-monitor-esx-hosts</link>
      <description>1&amp;gt; create HP CMS (Center Management Server) and install HP SIM (System Inside Manager) 5.2 on it.&lt;br /&gt;
2&amp;gt; install HP Insight Management Agent 8.0 on ESX host &lt;a class="jive-link-external" href="http://virtrix.blogspot.com/2006/09/hp-insight-manager-agents-for-vmware.html"&gt;http://virtrix.blogspot.com/2006/09/hp-insight-manager-agents-for-vmware.html&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
HP SIM did detecte both ESX hosts. However, it shows "degraded or failed" under "Health Status" column in SIM even though there are not. &lt;br /&gt;
&lt;br /&gt;
log on ESX, run "server hpadm configure" did the trick.&lt;br /&gt;
&lt;p /&gt;
 This is my working /etc/snmpd/snmpd.conf:&lt;br /&gt;
&lt;p /&gt;
&lt;br /&gt;
rwcommunity mycomstring 127.0.0.1&lt;br /&gt;
rocommunity mycomstring 127.0.0.1&lt;br /&gt;
rwcommunity mycomstring hpcms.mydomain.mag&lt;br /&gt;
rocommunity mycomstring hpcms.mydomain.mag&lt;br /&gt;
trapcommunity mycomstring&lt;br /&gt;
trapsink 192.168.14.19 mycomstring {I bet "trapsink hpcms.mydomain.mag public" will work too.}</description>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">hp</category>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">sim</category>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">esx</category>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">host</category>
      <pubDate>Thu, 19 Jun 2008 19:34:00 GMT</pubDate>
      <author>eagleh</author>
      <guid>http://communities.vmware.com/blogs/eagleh/2008/06/19/hp-sim-to-monitor-esx-hosts</guid>
      <dc:date>2008-06-19T19:34:00Z</dc:date>
      <clearspace:dateToText>1 year, 5 months ago</clearspace:dateToText>
      <wfw:comment>http://communities.vmware.com/blogs/eagleh/comment/hp-sim-to-monitor-esx-hosts</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/eagleh/feeds/comments?blogPostID=1875</wfw:commentRss>
    </item>
    <item>
      <title>Different guest OS VMs on different datastore(LUN)?</title>
      <link>http://communities.vmware.com/blogs/eagleh/2008/05/29/different-guest-os-vms-on-different-datastorelun</link>
      <description>"It is not a best practice to isloate different OS on different LUNS. VMware has always encouraged load mixing. Avoid mixing virtual machines that have competing resource requirements. The most important is not too have too many I/O intensive VMs on one LUN. I always try to stay under 25VMs per LUN. "  --&lt;a class="jive-link-profile" href="http://communities.vmware.com/people/dmismash"&gt;dmismash&lt;/a&gt;</description>
      <pubDate>Thu, 29 May 2008 14:04:00 GMT</pubDate>
      <author>eagleh</author>
      <guid>http://communities.vmware.com/blogs/eagleh/2008/05/29/different-guest-os-vms-on-different-datastorelun</guid>
      <dc:date>2008-05-29T14:04:00Z</dc:date>
      <clearspace:dateToText>1 year, 5 months ago</clearspace:dateToText>
      <wfw:comment>http://communities.vmware.com/blogs/eagleh/comment/different-guest-os-vms-on-different-datastorelun</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/eagleh/feeds/comments?blogPostID=1799</wfw:commentRss>
    </item>
    <item>
      <title>Vmotion vs. Storage Vmotion</title>
      <link>http://communities.vmware.com/blogs/eagleh/2008/05/28/vmotion-vs-storage-vmotion</link>
      <description>Vmotion moves a running VM from one host to another. (VC Client GUI, means by "Migrate...")&lt;br /&gt;
&lt;br /&gt;
SVmotion moves a running VM (files belong to that VM) from one vmfs storage to another. (have to be done through CLI. No VMware supported GUI so far.)&lt;br /&gt;
&lt;br /&gt;
Both should not inturrupt VM. VMs can be up and running during the process. &lt;br /&gt;
Note: If you can power off the VM, you can use VC Client GUI ("Migrate") to move both! &lt;br /&gt;
&lt;br /&gt;
The most famous Third-Party GUI tool (a VI Client plug-in) for S-Vmotion recognized by VMWare is developled by Andrew Kutz: &lt;a class="jive-link-thread" href="http://communities.vmware.com/thread/126141"&gt;http://communities.vmware.com/thread/126141&lt;/a&gt;</description>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">vmotion</category>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">svmotion</category>
      <pubDate>Wed, 28 May 2008 17:25:00 GMT</pubDate>
      <author>eagleh</author>
      <guid>http://communities.vmware.com/blogs/eagleh/2008/05/28/vmotion-vs-storage-vmotion</guid>
      <dc:date>2008-05-28T17:25:00Z</dc:date>
      <clearspace:dateToText>1 year, 5 months ago</clearspace:dateToText>
      <wfw:comment>http://communities.vmware.com/blogs/eagleh/comment/vmotion-vs-storage-vmotion</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/eagleh/feeds/comments?blogPostID=1797</wfw:commentRss>
    </item>
    <item>
      <title>How many VMs per LUN?</title>
      <link>http://communities.vmware.com/blogs/eagleh/2008/05/28/how-many-vms-per-lun</link>
      <description>"While VMware Infrastructure 3 supports up to 100 VMs per LUN, 32 VMs per LUN may often be acceptable. However, HP recommends being more conservative and using 8 - 10 VMs per LUN. In a NAS or iSCSI environment, HP recommends using 8 - 16 VMs per LUN."</description>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">lun</category>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">san</category>
      <pubDate>Wed, 28 May 2008 16:53:00 GMT</pubDate>
      <author>eagleh</author>
      <guid>http://communities.vmware.com/blogs/eagleh/2008/05/28/how-many-vms-per-lun</guid>
      <dc:date>2008-05-28T16:53:00Z</dc:date>
      <clearspace:dateToText>1 year, 5 months ago</clearspace:dateToText>
      <wfw:comment>http://communities.vmware.com/blogs/eagleh/comment/how-many-vms-per-lun</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/eagleh/feeds/comments?blogPostID=1796</wfw:commentRss>
    </item>
    <item>
      <title>About VCB</title>
      <link>http://communities.vmware.com/blogs/eagleh/2008/05/28/about-vcb</link>
      <description>The beauty of VCB is "LAN-Free", which eliminats the traditional backup window. You can back up your machine whenever you want, in theory. Also, yous ycan do image level backup which enables you to restore it in no time. With huge RDMs attached, the VM being backed up through VCB is becoming impossible (limit space on VCB Proxy) and the worst senario happened to me, the VM hung up and left LUNs unaccessible. (Big time!)&lt;br /&gt;
&lt;br /&gt;
Eventually I put all my RDMs to "Independent Virtual Compatibility" mode, therefore VCB will skip those RDMs automatically and back up OS part only. Then I use regular DP agent to backup data part (RDMs), of course nightly.&lt;br /&gt;
&lt;br /&gt;
Note: DP6.0 doesn't support VCB1.1, yet as I am writing this post.</description>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">vcb</category>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">rdm</category>
      <pubDate>Wed, 28 May 2008 16:29:00 GMT</pubDate>
      <author>eagleh</author>
      <guid>http://communities.vmware.com/blogs/eagleh/2008/05/28/about-vcb</guid>
      <dc:date>2008-05-28T16:29:00Z</dc:date>
      <clearspace:dateToText>1 year, 5 months ago</clearspace:dateToText>
      <wfw:comment>http://communities.vmware.com/blogs/eagleh/comment/about-vcb</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/eagleh/feeds/comments?blogPostID=1795</wfw:commentRss>
    </item>
    <item>
      <title>System CPU usage spikes to 100%</title>
      <link>http://communities.vmware.com/blogs/eagleh/2008/05/28/system-cpu-usage-spikes-to-100</link>
      <description>This is an ongoing issue that bothers me from time to time since our VMware Infrastructure in production. There could be quiet a few reasons cause this problem. Everytime it spikes, the whole machine is rendered useless. I have done:&lt;br /&gt;
&lt;br /&gt;
1&amp;gt; Applied ESX3.5 Update 1 and VirtualCenter 2.5 Update 1 (This CPU problem has been fixed for a while, however, it came back recently.) &lt;br /&gt;
2&amp;gt; I am holding off the April-30-2008 patch because people are saying it brought back the CPU problem which Update 1 had fixed.&lt;br /&gt;
3&amp;gt; I switch DRS from Partially Automatic to Manually. So there should not be any Vmotion happened until next patch for this CPU issue. I have observed that Vmotion could be one reason to trigger this High CPU issue.&lt;br /&gt;
4&amp;gt; However, yesterday, it happened right at 5PM (without any Vmotion). So I guess it has to be something scheduled to run at 5PM. Eventually I realized MS System Center Essential Agent was installed on this VM. uhha! It was a left-over. Uninstalled it and hopefully that was it.&lt;br /&gt;
&lt;p /&gt;
This issue has been driving me NUTS!</description>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">system</category>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">cpu</category>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">usage</category>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">spikes</category>
      <pubDate>Wed, 28 May 2008 15:31:00 GMT</pubDate>
      <author>eagleh</author>
      <guid>http://communities.vmware.com/blogs/eagleh/2008/05/28/system-cpu-usage-spikes-to-100</guid>
      <dc:date>2008-05-28T15:31:00Z</dc:date>
      <clearspace:dateToText>1 year, 5 months ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
      <wfw:comment>http://communities.vmware.com/blogs/eagleh/comment/system-cpu-usage-spikes-to-100</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/eagleh/feeds/comments?blogPostID=1793</wfw:commentRss>
    </item>
    <item>
      <title>RDM or VMFS disk?</title>
      <link>http://communities.vmware.com/blogs/eagleh/2008/05/28/rdm-or-vmfs-disk</link>
      <description>I found RDM is flexiable. You can hook it up with a physical machine down to the road if in need. Somebody reported RDM could be faster than VMFS. Also, RDMs are right allocated from SAN, therefore they are easier to grow (up to 2T). For my situation, we have such quite a few big data storage (2T, 1T, 600G, ) for the file server, I am afraid it's not a good idea to make such big VMFS disks.</description>
      <category domain="http://communities.vmware.com/blogs/eagleh/tags">rdm</category>
      <pubDate>Wed, 28 May 2008 15:16:00 GMT</pubDate>
      <author>eagleh</author>
      <guid>http://communities.vmware.com/blogs/eagleh/2008/05/28/rdm-or-vmfs-disk</guid>
      <dc:date>2008-05-28T15:16:00Z</dc:date>
      <clearspace:dateToText>1 year, 5 months ago</clearspace:dateToText>
      <wfw:comment>http://communities.vmware.com/blogs/eagleh/comment/rdm-or-vmfs-disk</wfw:comment>
      <wfw:commentRss>http://communities.vmware.com/blogs/eagleh/feeds/comments?blogPostID=1792</wfw:commentRss>
    </item>
  </channel>
</rss>

