Hi, I have installed the SAM 5.0 RC1 and all looks good. I have enabled the hardware monitoring on a couple of nodes, and it is returning information, although I think some of it is not necessarily correct.
The image below shows the status reported from OpenManage of a Dell server. Notice it is reporting disk 0:0:1 as Warning (non-critial). It is actually reporting a predictive failure.
This is the hardware status from SAM:
SAM is reporting everything is fine, but it is obviously not. Perhaps this will go red when the disk actually fails, but it would be nice to know before that happens as OpenManage is already aware of this.
Is there a categorisation for predictive failure that keeps the status green? Ideally I would like this to be Amber or Red.
Thanks
richlane79, can you provide me a MIB walk of that server using this tool so we can investigate the issue?
Hi richlane79
What type of node it is? Is it SNMP or WMI? Is this node a VMware ESX Server?
If Hardware Sensor goes into Warning, SAM is able to catch the change and correctly display but it has to poll it in that way. During the polling of the sensor, sensor has to be in Warning state - in your case Non Critical. Between two polling cycles there is 10 minute interval. If sensor goes into Non Critical state and back up between two poll cycles, SAM won't catch the change.
If it is SNMP node, could you please provide us with snmpwalk as Alterego requested?
It is a physical Windows file server and is monitored using SNMP.
I don't believe the status is switching between states. It has gone non-critical and stayed that way from what I can see.
I have the SNMPwalk output, but can I send this to you by another method? Don't really want to post it up here.
This is really bug. We track it internally as case 105954.
We do monitor State of the Disk instead of Status.
Thank you for the SNMP walk you provided it was very helpful.
This bug was fixed in APM 5.0 RC2, which was released yesterday. Please give it a try to see if it's working for you.
Thank you
Finally upgraded today and the status is reporting correctly now!
This is great news. Thanks very much.
I'm glad RC2 resolved the issue for you. Thanks for following up on your post. It's much appreciated!
