How can I get sensor value for snmp device ?

DCIM_Support · ‎2020-07-04

This question was originally posted on DCIM Support by kemal on 2018-06-08

Hello,

I have an issue with the detection of my device sensor, I can't get temperature value, power consumption of my snmp device . Even if I put the oid in the setting of snmp, struxuware don't give me more informations on my sensor

How can I resolve this problem ?

DCIM_Support · ‎2020-07-04

This answer was originally posted on DCIM Support by Steven Marchetti on 2018-06-08

Hi Kemal,

Your first choice should always be to put in a DDF request. This is for new DDFs or for update to current DDFs and they should be able to assist in getting any of the values available through SNMP on your device.

If using supplemental OIDs, please make sure you try with a leading period. For instance, instead of:

1.3.6.1.4.1.318

use

.1.3.6.1.4.1.318

Notice the leading period.

Secondly, make sure you use the correct instance(s). As an example, the following OID is for an APC UPS and it's battery capacity:

.iso.org.dod.internet.private.enterprises.apc.products.hardware.ups.upsBattery.upsAdvBattery.upsAdvBatteryCapacity

.1.3.6.1.4.1.318.1.1.1.2.2.1

This will not return a value in DCE. You should do an SNMP get of the OID to see the proper and available instances and in this case, the device will respond with an instance of 0...you'll need to use the following OID to get this value:

.1.3.6.1.4.1.318.1.1.1.2.2.1.0

Another thing to consider is that there is no multiplier. If you pull an OID similar to the one I just mentioned, it may return the value in tenths. At 100% capacity, it may return 1000 to indicate 100.0%

Finally, a supplemental OID in DCE will only work with numeric values. Text will not work and if you were to even poll a value such as time (hh:mm:ss), you will not receive any values after the colon. you may simply see "hh" and nothing else. This is a limitation of supplemental OIDs.

Much of this should also be noted in k-base FA158341

If you're not getting any values at all, it could be that you need to troubleshoot SNMP as a whole. K-base FA226273 should help with that.

Thanks,

Steve.

See Answer In Context

DCIM_Support · ‎2020-07-04

This answer was originally posted on DCIM Support by Steven Marchetti on 2018-06-08

Hi Kemal,

Your first choice should always be to put in a DDF request. This is for new DDFs or for update to current DDFs and they should be able to assist in getting any of the values available through SNMP on your device.

If using supplemental OIDs, please make sure you try with a leading period. For instance, instead of:

1.3.6.1.4.1.318

use

.1.3.6.1.4.1.318

Notice the leading period.

Secondly, make sure you use the correct instance(s). As an example, the following OID is for an APC UPS and it's battery capacity:

.iso.org.dod.internet.private.enterprises.apc.products.hardware.ups.upsBattery.upsAdvBattery.upsAdvBatteryCapacity

.1.3.6.1.4.1.318.1.1.1.2.2.1

This will not return a value in DCE. You should do an SNMP get of the OID to see the proper and available instances and in this case, the device will respond with an instance of 0...you'll need to use the following OID to get this value:

.1.3.6.1.4.1.318.1.1.1.2.2.1.0

Another thing to consider is that there is no multiplier. If you pull an OID similar to the one I just mentioned, it may return the value in tenths. At 100% capacity, it may return 1000 to indicate 100.0%

Finally, a supplemental OID in DCE will only work with numeric values. Text will not work and if you were to even poll a value such as time (hh:mm:ss), you will not receive any values after the colon. you may simply see "hh" and nothing else. This is a limitation of supplemental OIDs.

Much of this should also be noted in k-base FA158341

If you're not getting any values at all, it could be that you need to troubleshoot SNMP as a whole. K-base FA226273 should help with that.

Thanks,

Steve.

DCIM_Support · ‎2020-07-04

This comment was originally posted on DCIM Support by kemal on 2018-06-18

Hello Steve,

Thank you very much , I can clearly understand now.

DCIM_Support · ‎2020-07-04

This comment was originally posted on DCIM Support by spezialist on 2018-06-18

Dear kemal,

Tell us please, did you solve your problem or not?

With respect.

DCIM_Support · ‎2020-07-04

This comment was originally posted on DCIM Support by kemal on 2018-06-18

yes the problem is solved

DCIM_Support · ‎2020-07-04

This comment was originally posted on DCIM Support by spezialist on 2018-06-18

Ok, thanks for the good feedback 😀.

DCIM_Support · ‎2020-07-04

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.