3 Replies Latest reply on Aug 18, 2014 1:39 PM by mharvey

    ESX Host CPU Polling stopped after deleting a SAM Application assigned to the vCenter - Bug?


      I hope someone can help me understand if this is a bug or not.  Yesterday I added 2 SAM Application monitors for our VMWARE vCenter server.  Then, I deleted one of them.  [The monitor was a WMI service monitor (for VMware VirtualCenter Server).]

      Soon after, I started getting alerts that the ESX Servers (which are tied to the vCenter) were no longer gathering the CPU Polling data.

      After some research, I noticed the VIM_PollingTasks table did not have an entry for the vCenter (N: 476, VCenter ID = 5).  [I don't know if this is significant or not, but the others had an entry.]  So I click 'Poll Now' on the vCenter node.

      Within 3 minutes, the alerts were resolved & the table entry was there for this node.


      To confirm, I deleted the remaining monitor for this vCenter server & checked the table.  The record was gone.  I re-added the monitor.  Record still gone.  CPU Polling errors were reported again.  (btw, this is a custom alert which checks the CPULoad table.)

      Clicked the 'Poll Now', record was added back.  CPU Polling alert was resolved.


      So, is this a bug or not?

      I assume all the ESX Server polling stopped although everything looked OK (green lights) in SolarWinds.


      The vCenter is version 5.1.0

      Orion Platform 2013.2.1, SAM 6.0.2, IPAM 4.1, NCM 7.2.2, NPM 10.6.1, NTA 3.11.0, IVIM 1.9.0