Hardware Sensor - "Implementation cannot report..."
Hi everyone,
In previous forum threads, it's been mentioned that there has been some difficulty getting Disk information to appear as part of the now default hardware monitors (things like fan, power, CPU, etc. will display, but nothing about the disk arrays). (Reference: https://forums.manageengine.com/topic/opmanager-10-hardware-monitoring)
I'm unsure if this problem is related, but I'd like to know what you can make of this. Attached is a screen shot of some Hardware events from the Event Summary widget on OpManager. It shows messages coming from two different servers reporting approximately every 15 minutes with an error that reads:
"Hardware Sensor Name : Physical Disk 0:0:#. Category : Disk Array Data. Current State : ready(1) - The implementation cannot report on the current health state of the physical element."
Using the OIDs found in this thread (https://forums.manageengine.com/topic/opmanager-10-hardware-monitoring-how-does-it-work) for a Dell Disk Array, an snmpwalk from the OpManager server does return correct information. Likewise, OpManager's MIB browser can do a Get Table and pull the information appropriately.
My questions are: What is causing this error to appear (it happens consistently every 15 minutes for these two servers, so it's not just a one-time issue)? And is there a way to disable just this one message/monitor? Obviously I would like for the disk array information to appear correctly on the device snapshot page, but if it's not working I'd much rather not have the error messages like this appear.
I did just happen to notice after writing this message that both of the referenced disks that this error is being generated for are set as spare drives:
arrayDiskSpareState: globalHotSpare(3)
arrayDiskSpareState: dedicatedHotSpare(4)
As opposed to the other drives that are "notASpare(5)"
Is it just that spare drives don't display health information? If so, can we set OpManager to ignore these drives until that state changes?
Thank you.
In previous forum threads, it's been mentioned that there has been some difficulty getting Disk information to appear as part of the now default hardware monitors (things like fan, power, CPU, etc. will display, but nothing about the disk arrays). (Reference: https://forums.manageengine.com/topic/opmanager-10-hardware-monitoring)
I'm unsure if this problem is related, but I'd like to know what you can make of this. Attached is a screen shot of some Hardware events from the Event Summary widget on OpManager. It shows messages coming from two different servers reporting approximately every 15 minutes with an error that reads:
"Hardware Sensor Name : Physical Disk 0:0:#. Category : Disk Array Data. Current State : ready(1) - The implementation cannot report on the current health state of the physical element."
Using the OIDs found in this thread (https://forums.manageengine.com/topic/opmanager-10-hardware-monitoring-how-does-it-work) for a Dell Disk Array, an snmpwalk from the OpManager server does return correct information. Likewise, OpManager's MIB browser can do a Get Table and pull the information appropriately.
My questions are: What is causing this error to appear (it happens consistently every 15 minutes for these two servers, so it's not just a one-time issue)? And is there a way to disable just this one message/monitor? Obviously I would like for the disk array information to appear correctly on the device snapshot page, but if it's not working I'd much rather not have the error messages like this appear.
I did just happen to notice after writing this message that both of the referenced disks that this error is being generated for are set as spare drives:
arrayDiskSpareState: globalHotSpare(3)
arrayDiskSpareState: dedicatedHotSpare(4)
As opposed to the other drives that are "notASpare(5)"
Is it just that spare drives don't display health information? If so, can we set OpManager to ignore these drives until that state changes?
Thank you.