<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>swalker_LST Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>swalker_LST Tracker</description>
    <pubDate>Thu, 23 Nov 2023 17:35:46 GMT</pubDate>
    <dc:date>2023-11-23T17:35:46Z</dc:date>
    <item>
      <title>Re: vSphere 6.0U3 EAM Error</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vSphere-6-0U3-EAM-Error/m-p/1756323#M22389</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This was really helpful for me as I just ran into the same problem which was also blocking my 6.5 upgrade. Through discussion with VMware - in addition, line 46 in your example should be updated to include your specific hostID obtained using:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;cat /etc/vmware/install-defaults/sca.hostid&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;After that I found that an additional line was required before the service would start correctly:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE __default_attr="java" __jive_macro_name="code" class="jive_macro_code _jivemacro_uid_15223300282611242 jive_text_macro" data-renderedposition="153_8_1232_16" jivemacro_uid="_15223300282611242"&gt;&lt;P&gt;eam.web.root=/usr/lib/vmware-eam/web&lt;/P&gt;&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally, in case this was done using the root user you might find it necessary to set the permissions correctly for the properties file if it was deleted/recreated:&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;chown eam:cis eam.properties&lt;/P&gt;&lt;P&gt;chmod -R 644 eam.properties&lt;/P&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Hope this helps if someone else runs into this issue during an upgrade..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 29 Mar 2018 13:27:26 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vSphere-6-0U3-EAM-Error/m-p/1756323#M22389</guid>
      <dc:creator>swalker_LST</dc:creator>
      <dc:date>2018-03-29T13:27:26Z</dc:date>
    </item>
    <item>
      <title>Re: No items in datacenter</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/No-items-in-datacenter/m-p/1337431#M6886</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am happy to update my own part of this discussion in the hope that it might help someone else in the same situation. Basically we were suffering Inventory differences between the vSphere client (C#) and the Web Client, and this now explains why it was not possible for vCOPs to reliably pull information out of vCenter for all of the datacenter nodes/hierarchy as detailed above.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, since the Inventory service was running and everything else seemed OK we believed that this was a vCOPs problem. Almost by chance, we attempted to restart the vCenter Server and found that the Inventory Service would no longer start up afterwards. This led us to investigate why 40GB of hard disk space on the vCenter Server had been eaten up by Inventory Service DB XHIVE transaction logs. We recreated the Inventory Service DB using the documented procedure, but this did not resolve the problem. We could see more than 10MB of data being written to the Inventory logs per second, and high CPU utilisation. Further investigation of the debug logs for the Inventory Service led us to discover a known problem with the use of the vFlash feature on (only a single server) one of vCenter member hosts was causing the problem. We removed it from vCenter, applied the patch as detailed in the link below, and the problem with vCOPs is now resolved.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this description makes someone else's day a little bit easier!!..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2072392" style="font-size: 10pt; line-height: 1.5em;" title="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2072392"&gt;VMware KB: VMware vCenter Server consumes most of the CPU, memory, or disk I/O after enabling Virtual Flash&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 May 2014 14:04:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/No-items-in-datacenter/m-p/1337431#M6886</guid>
      <dc:creator>swalker_LST</dc:creator>
      <dc:date>2014-05-26T14:04:00Z</dc:date>
    </item>
    <item>
      <title>Re: No items in datacenter</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/No-items-in-datacenter/m-p/1337430#M6885</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi again, I removed the original appliances (vApp) by disassociating them from vCentre and removing the asset from the Solutions tab. This was completed successfully before deploying a new vCOPs vApp, and this was again registered with vCentre. So there were never two sets of vCOPs running at the same time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I'm referring to a lack of data within vCOPs for a certain datacentre (i.e. nothing at all) what I meant was that when I try to expand the DC name using the drill down option on the left pane I am able to expand it as far as displaying individual cluster names, but no health information is being received from any objects within it. All of the folders within the datacentre are detected, but displayed only as grey squares on the health map.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This was multi-datacentre hierarchy was working fine like this for at least 18 months, and the missing information is consistent with what I couldn't view on the original appliance and the one which I've just deployed in place of it. The following screen capture shows the hierarchy expanded to its full extent, but I can definitely confirm that the permissions are identical for each datacentre.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="Capture.PNG"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/52127i9A42419C1FD5E6F1/image-size/large?v=v2&amp;amp;px=999" role="button" title="Capture.PNG" alt="Capture.PNG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;The only other slightly new thing that we've done recently is set up VM Storage Profiles for use with Storage DRS. &lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 May 2014 14:52:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/No-items-in-datacenter/m-p/1337430#M6885</guid>
      <dc:creator>swalker_LST</dc:creator>
      <dc:date>2014-05-20T14:52:29Z</dc:date>
    </item>
    <item>
      <title>Re: No items in datacenter</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/No-items-in-datacenter/m-p/1337428#M6883</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm not very familiar with CustomUI - but since I've redeployed the appliances from clean the only thing that remains in common is the vCenter DB. None of the hosts are marked as maintenance mode in the vSphere Web Client/Client and if I go into CustomUI and choose, Environment&amp;gt;Environment Overview I can see all of the objects within the Inventory (all marked with a 100 health score). All have got a green mark against the Collection column, and the Data receiving icon. When I tried this earlier today using the original appliance almost all of the items were marked with a blue question mark. I would be tempted to leave it and see what happens next, but we have already started receiving data for a smaller subordinate datacentre and nothing at all for any datacentre with a cluster or larger configuration present.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Update: Actually, it's a very long list of items in the CustomUI view - and all of the entries which are not showing up in the vCOPs are marked with a blue question mark.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Message was edited by: swalker_LST&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 May 2014 14:33:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/No-items-in-datacenter/m-p/1337428#M6883</guid>
      <dc:creator>swalker_LST</dc:creator>
      <dc:date>2014-05-20T14:33:48Z</dc:date>
    </item>
    <item>
      <title>Re: No items in datacenter</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations/No-items-in-datacenter/m-p/1337425#M6880</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Over the last couple of days we have also started to experience the same issue. I deployed 5.6 a year or so ago, then upgraded through 5.7 and later 5.8.1 without any issues. We haven't changed any configuration settings since then for either the collector user or the vCOPs license, however recently (..and it may be unconnected) we decommissioned several datastores and added some new ones. Since around that time we started seeing a problem where some datacentres cannot be drilled down into, whereas others can. Our vCenter permissions are applied right at the top of the hierarchy (on the VC object itself) and the propagate option applies exactly the same set of permissions to each of the datacentre objects. Some standalone hosts in the root of the hierarchy can be seen, whereas others cannot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have approximately 80% of the inventory items missing now. I unregistered and reregistered the vCOPs solution with vCenter which was successful, but didn't fix the problem. Further to this I restored a backup of the original appliance that was around a month old, and this also has the same issue. There would appear to be some vCenter inventory related issue going on which might have occurred when we added new resources recently, however all of the vCenter health checks work out fine so I'm at a loss as to what has caused it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Finally, in order to prove whether the issue is VC related I've just deployed an entirely fresh set of vCOPS UI and Analytics VMs - then registered/licensed correctly and confirm exactly the same behaviour is being experienced.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does anyone have any ideas about where to look next?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 May 2014 14:18:16 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations/No-items-in-datacenter/m-p/1337425#M6880</guid>
      <dc:creator>swalker_LST</dc:creator>
      <dc:date>2014-05-20T14:18:16Z</dc:date>
    </item>
    <item>
      <title>Re: vFlash performance metrics missing</title>
      <link>https://communities.vmware.com/t5/vSphere-Storage-Discussions/vFlash-performance-metrics-missing/m-p/963864#M7568</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Me too - I've just upgraded from a fresh installation of vCenter Server 5.1 on Oracle DB, to 5.5b and the counters are missing. I have enabled vFRC on one ESXi 5.5 host (Ent Plus license) and I can use the command line to verify cache information but the counters are not visible in either the C# or Web Clients. Don't seem to find any other information from other people having this issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Feb 2014 17:04:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Storage-Discussions/vFlash-performance-metrics-missing/m-p/963864#M7568</guid>
      <dc:creator>swalker_LST</dc:creator>
      <dc:date>2014-02-13T17:04:20Z</dc:date>
    </item>
  </channel>
</rss>

