False positive Inactive VMs Disk Alert triggered in VMAN

2/7/2022 1:24 PM

2/7/2022 1:24 PM

This article provides information about scenario where you may notice inactive VMs disks were triggered by VMAN module even though the VM's have no extra disks or snapshots disks just a single VMDK (in case of VMware) that is used as OS Disk for Guest VM

The alert triggers based on:

---Trigger Condition:
SELECT VirtualMachines.Uri, VirtualMachines.DisplayName FROM Orion.VIM.VirtualMachines AS VirtualMachines
where DayDiff(virtualmachines.VirtualDiskDateModified, getdate())>30 and (virtualmachines.SnapshotSummaryCount=0 or DayDiff( virtualmachines.SnapshotDateModified, getdate())>30)

Which was true when we validated the VM's Disks. However the real reason for this confusion was due to the following polling errors 

2022-01-06 19:13:38,608 [ViSdkExecutor-1] ERROR com.hyper9.data_collection.visdk.jobs.EnumerateEnvironmentJob - Login failed due to a bad username or password.
2022-01-06 19:13:38,608 [ViSdkExecutor-1] ERROR com.hyper9.data_collection.visdk.jobs.EnumerateEnvironmentJob - Failed to connect to 192.168.250.11 (Vcenter IP)

 

Virtualization Manager

Invalid Polling VMAN polling credentials resulting in Login failed due to a bad username or password causing Disk stats not to be collected.

1. Verify the credentials assigned to the Vcenter under Web console > Settings > Virtualization settings > VMware / Hyper-V
2. Disable Polling and enable back.
3. Clear the "Inactive VM's disks" alerts from Active alerts page
4. Wait for 1 hour and check if these alerts are still triggering again for the same VM's / Disks.

If no such alerts means the issue is resolved and polling is working correctly.

If the alerts are still generating, then open a case with Solarwinds Technical support and supply the Orion Diagnostics.