Happy New Year. At the end of 2018, we added an additional 30 proactive findings to Skyline. These proactive findings will appear within Skyline Advisor, if your VMware solution meets the criteria for these potential issues. Customers continue to ask for us to identify more potential issues within their environment. We are making a conscious effort to introduce new findings within Skyline on a more regular basis. Again, we highlight these potential issues within your environment via Skyline Advisor proactive findings.

Also, keep in mind that as we add new findings to Skyline, they may not appear for you within Skyline Advisor. This would indicate that your environment is not susceptible to the potential issue. And while you may be disappointed that new proactive findings are not appearing within Skyline Advisor, keep in mind that this is an indication of a healthy environment with reduced risk compared to environments with a large number of proactive findings.

New FindingID Names

We have renamed the FindingID for each proactive finding to make them more descriptive. Additionally, the new FindingID names makes it easier to search for particular findings, with a common naming convention that includes the solution name (vSphere, NSXv), the potential issue (VmMemoryUsageEsxi, NsxEdgeVxlanTrunk) and the associated Knowledge Base (KB) article. For example, you can enter “NSXv” within the Search box to view only NSX for vSphere proactive findings. An example of the new FindingIDs within Skyline Advisor is available below.

New vSphere Proactive Findings


This proactive finding will be displayed ff you’re running a version of ESXi 6.0 prior to Update 1. When a All-Paths-Down (APD) event occurs, the LUNs connected to ESXi may remain inaccessible after the paths to the LUNs recover. This could lead to virtual machines becoming inaccessible, an unresponsive host, and datastores disappearing from the vSphere Client, even when virtual machines on that datastore remain. Additionally, in order to recover virtual machines, they must be terminated to recover the datastore. There is good news though, if your hosts have high-availability enabled, the virtual machines should be recovered on other hosts. If you’re running a version of ESXi 6.0 prior to Update 1, be on the look out for this new proactive finding within Skyline Advisor.

A complete list of vSphere proactive findings added to Skyline in the past 30 days is as follows:

  • vSphere-VmfsVolumeSHostError-KB#2109735
  • vSphere-EsxiNetwork-KB#2124669
  • vSphere-WindowsEventLogError-KB#2114741
  • vSphere-PSODVmMemPfUserMem-KB#2139287
  • vSphere-VmMemoryUsageEsxi-KB#2149496
  • vSphere-Snmpdfailtorespond-KB#2148211
  • vSphere-SfcbSmxSfcbSmxSignal-KB#2148526
  • vSphere-MscsAccesspostVMotion-KB#2144153
  • vSphere-PSODLACPScheduler-KB#2088243
  • vSphere-ExtendingeagerzeroedStun-KB#2135380
  • vSphere-WebClientIncreaseDisk-KB#2150383
  • vSphere-WinGuestcustomization-KB#2142982
  • vSphere-ESXiHostClientLoginError-KB#2149798
  • vSphere-FailedtoDestroyMirror-KB#2135631

New NSX Proactive Findings


This proactive finding is displayed if you’re running NSX for vSphere versions 6.2.7, 6.2.8, 6.3.2, 6.3.3 or 6.3.4. You may experience this issue if firewall rules are not being applied on newly deployed virtual machines. The risk is that firewall rules are not applied, leaving your environment in an unsecure state. To resolve this issue, update your NSX or vSphere environment to 6.2.9 or 6.3.5. Additionally, you can workaround this issue by performing the following:

  1. Do a force sync on the DFW rules on the affected clusters with the new VMs deployed.
  2. Click Edit on the security group missing the VM IPs and submit with out any changes.

This KB article also includes a list of commands you can run to determine if this issue applies to your NSX for vSphere environment.

A complete list of vSphere proactive findings added to Skyline in the past 30 days is as follows:

  • NSXv-MigratingEsgDlrVm-KB#2144845
  • NSXv-CreatingNsxEdgesIpv6Nsx-KB#2127561
  • NSXv-NsxEdgeVxlanTrunk-KB#2148772
  • NSXv-FirewallCertainFirewallNsx-KB#51535
  • NSXv-NsxManagerServerMemory-KB#2150819
  • NSXv-NsxManagerConnectivity-KB#51459
  • NSXv-ManagerVsfwdConnection-KB#2146873
  • NSXv-ADLoginFailureHighRate-KB#2151748
  • NSXv-FirewallNsxvInvalidRule-KB#2152011
  • NSXv-ControllerLogFailure-KB#2135653
  • NSXv-PublishIdentityFirewallFails-KB#2150286
  • NSXv-EastwestVmconnectivity-KB#2150778
  • NSXv-TraceflowNsxUIFails-KB#2152010
  • NSXv-ExitingMaintenancemodefails-KB#2150186

Detectable by VMware Skyline

Additionally, we’ve added a new field within Knowledge Base (KB) articles that reference a Skyline proactive finding. Now, if you happen to find that a KB article resolved an issue you experienced, you can quickly see if you would’ve been notified of the issue before it occurred. This helps answer the question, is there an associated Skyline proactive finding, when browsing or investigating a particular KB article.



Risk if No Action Taken

Finally, we’ve added an additional field to each proactive finding appropriately titled “Risk if no action taken”. We want to help answer the question, what could happen if I do not take action of resolving this potential issue within my environment. Examples of “Risk if no action taken” include infrastructure stability, security risk and potential esxi host crash. We hope this additional information assists you in deciding which proactive findings to take action against to ensure the stability and reliability of your environments remains high.

We are excited to continue delivering enhancements to the proactive support services being delivered by Skyline and our Global Support Services (GSS) team. Visit for more information and follow @VMwareCSE on twitter for updates. Get started with Skyline today by visiting the Skyline Getting Started page to begin the short process of proactively identifying potential issues in your environment before they occur.

More Resources