False positives from ESX host - PSU and CPU

Question

I've seen some similar threads on thwack, but nothing necessarily related to this issue we're seeing. I'm convinced this is an issue with the host and not SolarWinds but I wanted to see if anyone else has had this happen, and what you did to resolve it. The closest I got so far to a VMWare KB article with similar symptoms referenced a firmware update prior to the issue--which I've confirmed we did not perform.

Here's what we're seeing on the host. I even deleted the node and re-added it and right away the first poll showed the same "problems".

mbird · Answer

What version of SAM/NPM do you run? I'm running SAM 6.2.4 and NPM 12.0.1 RC1 (should probably get on the actual 12.0.1 though...), and the host in question for me is in a 5.5 environment. Wondering if we've got anything in common when it comes to what we're seeing in the Orion console.

squinsey · Answer

I don't have the error you originally reported mbird​, but I can confirm I also am unable to change the 'poll through' as it is also greyed out.

This is against ESX on vCentre 5.1​ or 6.0

mbird · Answer

I went and gave that a whirl and the "poll through" option was greyed out. I did however add the root credentials under the "VMWare polling settings" when I added the node. Now after assigning credentials on the screen you suggested the node states: "Hardware polling failed: Polling of chassis (CIM_Chassis class) failed. The operation has timed out".

If I un-check the "vmware polling settings" option under "edit node" it's no longer listed on the polling settings page.