All Posts

Need assistance issue cannot login to Vcenter & even SSH in Vcenter server. Needed to access the vsphere to maintain the vm.  Please give us a process or instruction on to restore.
That fixed it. Thanks for the info!
I checked that but i cant even get to that as the page doesnt even open.
Hi Ashish, and first of all, apologize for my delay in reply. After your suggestion, that i just marked as right, we was finally able to run the appliance. In my personal opinion, documentation is... See more...
Hi Ashish, and first of all, apologize for my delay in reply. After your suggestion, that i just marked as right, we was finally able to run the appliance. In my personal opinion, documentation is low clear about the point that stuck us but, anyway, after having left the application to work for a few weeks, we removed it because, in our opinion, it was too confusing in the way of providing information. It is clearly not my intention to "criticism" the application but that is not what we were looking for. Thanks and sorry again for delay. Best regards. Massimo
Seems like SHD as well as lsdoctor are unable to collect Lookup service data. You follow instructions from KB 2043509 to manually check service status. Mean while we will work on fix, which would a... See more...
Seems like SHD as well as lsdoctor are unable to collect Lookup service data. You follow instructions from KB 2043509 to manually check service status. Mean while we will work on fix, which would available in upcoming SHD release. Thanks Ashish
@wilgee, This old post might help, please check. https://communities.vmware.com/t5/Skyline-Community-Discussions/Deregister-Skyline-Collector/td-p/2298482
Hi Penobscot, The GRAY status of report says "Not able to collect lookup service data", it could be because of Lookservice API was unavailable for sometime. I would suggest to perform a log based d... See more...
Hi Penobscot, The GRAY status of report says "Not able to collect lookup service data", it could be because of Lookservice API was unavailable for sometime. I would suggest to perform a log based diagnostics and see if there is any issue detected by SHD. Thanks Ashish
Version is 4.0.0, upgraded from 3.5.2. The lsdoctor.log does note "Listing lookup service problems found in SSO domain," but the next row is "No issues detected in the lookup service entries for xxxx... See more...
Version is 4.0.0, upgraded from 3.5.2. The lsdoctor.log does note "Listing lookup service problems found in SSO domain," but the next row is "No issues detected in the lookup service entries for xxxx.xxxxx.local (VC 7.0 or CGW)" and the json file says "No problems found."
Hi Ghiacciolo, I hope issue is resolved, could you please update the thread? Thanks Ashish
Hi Penobscot, This is not a issue, after rebooting SHD VM, just wait for 5 min and then you can press Enter key to get command prompt. Thanks Ashish
Hi Ruppala, I hope issue is resolved. Could you please update the thread? Thanks Ashish
Hi Massimo, I hope the issue is resolved. Could you please update thread with fix details and mark it as resolved? Thanks Ashish
Hi lkrish, I hope the issue was resolved as per our discussion on emails. Could you please update thread with fix and mark it as resolved? Thanks Ashish
Hi Penobscot,   Could you please provide more details like,  What SHD version you are using? Is it a fresh install or upgraded setup? Please provide screen shots with the errors. Thanks Ashish
My skyline collector was working fine until a couple weeks ago. When i go to log in I get a server certificate thumbprint doesnt match error. I have rebooted machine and still doesnt work. i am attac... See more...
My skyline collector was working fine until a couple weeks ago. When i go to log in I get a server certificate thumbprint doesnt match error. I have rebooted machine and still doesnt work. i am attaching a screenshot. Thanks
The Skyline team is pleased to announce new VMware Skyline Collector 3.5 and Advisor Pro releases with VMware Aria Operations for Logs Diagnostic Findings and new proactive Findings. If you have Aut... See more...
The Skyline team is pleased to announce new VMware Skyline Collector 3.5 and Advisor Pro releases with VMware Aria Operations for Logs Diagnostic Findings and new proactive Findings. If you have Auto-Upgrade enabled, your Skyline Collector will automatically update.      A summary of the new features is below. For additional details review the Skyline Advisor Pro Release Notes. Log into Skyline Advisor Pro today to see the new enhancements!        New Feature Highlights:      Aria Operations for Logs Diagnostic Findings  Skyline recently added Aria Operations for Logs product support, expanding the list of VMware products Skyline analyzes to keep productive and healthy in your environment. Once you add your Aria Logs endpoints to your Skyline Collector(s), you can view proactive Findings and Recommendations in Skyline Advisor Pro. With this latest release, you can now view Diagnostic Findings in Advisor Pro, based on Aria Operations for Logs queries. Diagnostic Findings alert you to and pinpoint existing issues in your environment based on log data evidence. The Diagnostic Findings complement Proactive Findings, which alert you to potential issues in your environment that have not yet occurred. After you add your Aria Logs endpoints to Skyline, you will notice that the default setting for Diagnostic Findings is disabled. You can enable and/or disable the feature whenever you like. We recommend adding all of your Aria Logs endpoints to keep them safe and productive, and enabling Diagnostic Findings to take advantage of log data analysis. Skyline will prompt you to connect endpoints that are not already connected. Learn more  New Proactive Findings    Several new Proactive Findings have been released, including security vulnerabilities, trending support issues and more. Read more about the new Findings in the blog post.    If you have questions about any of these announcements, please visit the Skyline Community.        Skyline Collectors Below v3.0 EOL: As previously announced, we have begun the End of Life (EOL) process for Skyline Collectors below v3.0. We strongly recommend you upgrade any Collectors below 3.0 to the latest Collector version v3.5, before the October 5, 2023 EOL date, to avoid losing access to Skyline. All of your Collectors must be on v3.0 or above to access Skyline Advisor Pro, which is smarter, easier and 12X faster than Skyline Advisor. Note that customers running Collector v2.1 and below who have not upgraded will no longer see data provided by those Collectors in Skyline Advisor.  As a reminder, VMware supports n-2 versions of the Skyline Collector. Currently versions 3.3 and below are no longer actively supported under General Support. Learn more about upgrading Skyline Collector. 
I continually receive an error, "Not able to collect Lookup Service Data," when I run a health check. The lsdoctor tool in the recommended resolution does not find any problem.
It turns out this is not an issue.  The site was cached with the old interface, once I cleared the cache and refreshed the page the new interface was there and I was able to scan the individual ESXi ... See more...
It turns out this is not an issue.  The site was cached with the old interface, once I cleared the cache and refreshed the page the new interface was there and I was able to scan the individual ESXi host.
When trying to run the diagnostics on a host on the submit analysis page the Finish is greyed out and I cannot click on it.  The message I get is "No ESXi or VC selected for analysis, please navigate... See more...
When trying to run the diagnostics on a host on the submit analysis page the Finish is greyed out and I cannot click on it.  The message I get is "No ESXi or VC selected for analysis, please navigate Back to select ESXi or VC from the inventory tree to continue analysis"  Any ideas on how to get this to work, this always worked in version 3.5?
I used to create a service, i used steps in  this document vmware-vcloud-api-extension-whitepaper below is my service  <vmext:Service xmlns:vcloud="http://www.vmware.com/vcloud/v1.5" xmlns:vme... See more...
I used to create a service, i used steps in  this document vmware-vcloud-api-extension-whitepaper below is my service  <vmext:Service xmlns:vcloud="http://www.vmware.com/vcloud/v1.5" xmlns:vmext="http://www.vmware.com/vcloud/extension/v1.5" name="LAB-VCD-Exchange-DataService-N">     <vmext:Namespace>vcd.nymbis.schedulings</vmext:Namespace>     <vmext:Enabled>true</vmext:Enabled>     <vmext:AuthorizationEnabled>true</vmext:AuthorizationEnabled>     <vmext:RoutingKey>vox-scheduling</vmext:RoutingKey>     <vmext:Priority>50</vmext:Priority>     <vmext:Exchange>lb-vcd-exchange</vmext:Exchange>     <vmext:ApiFilters>         <vmext:ApiFilter>             <vmext:UrlPattern>(/api/org/.*/scheduling/*[0-9]*)</vmext:UrlPattern>         </vmext:ApiFilter>       </vmext:ApiFilters> </vmext:Service>