We monitor our OpenManage servers by SNMP and if the Driver version is below the minimum supported version for OpenManage then .1.3.6.1.4.1.674.10893.1.20.130.1.1.45.X exists where X is the controller number.
If the firmware version is up to date then this OID does not exist.
Previously I had monitored this item and if the trigger existed and the nodata trigger reported that data had been received then I flagged this up as the driver needed updating.
Since upgrading to 2.2.2 I'm seeing error in the info column for all of the triggers.
Item not supported for function: {Server.XXXX.local:OM_ControllerDriverMinVersion.["1"].nodata(7200)}#1
The item is now unsupported as all of the firmware is up to date.
Do I need to re-structure my trigger to capture this now on 2.2.X or is there another way I should be doing this? I can't see a way to check if an item is in supported/unsupported state in a trigger.
I don't want an action, which I can see how to do, just a trigger.
If the firmware version is up to date then this OID does not exist.
Previously I had monitored this item and if the trigger existed and the nodata trigger reported that data had been received then I flagged this up as the driver needed updating.
Since upgrading to 2.2.2 I'm seeing error in the info column for all of the triggers.
Item not supported for function: {Server.XXXX.local:OM_ControllerDriverMinVersion.["1"].nodata(7200)}#1
The item is now unsupported as all of the firmware is up to date.
Do I need to re-structure my trigger to capture this now on 2.2.X or is there another way I should be doing this? I can't see a way to check if an item is in supported/unsupported state in a trigger.
I don't want an action, which I can see how to do, just a trigger.