Adding a Supplemental OID

DCIM_Support · ‎2020-07-02

Hi, I'm trying to get data from a generic SNMP device by adding a Supplemental OID. DCE (V7.2.6.24) reports that the device is being scanned successfully, but I can't see any sensor data. The sensor type configured in SNMP Device Settings is 'Generic ( deg C)', and the OID is .1.3.6.1.4.1.31440.10.5.1.1.1). All I see in 'View Device Sensors' is 'Link Status', with value 'Online', but I can't work out how to tell DCE that there is a temperature sensor at this MIB OID. Can anyone help, or point me at the right documentation ?

DCIM_Support · ‎2020-07-02

Hi Hugh,

Please try polling the device using an SNMP scanning tool, either a command line utility or something with a mib browser such as a freeware app I often use called GetIf. You may find that the OID is returned with a specific instance. The OID

.1.3.6.1.4.1.31440.10.5.1.1.1

may actually be returned as

.1.3.6.1.4.1.31440.10.5.1.1.1.0

As an example, when I poll an APC UPS for basicIdentModel:

.1.3.6.1.4.1.318.1.1.1.1.1.1

It returns a value along with the OID including an instance

.1.3.6.1.4.1.318.1.1.1.1.1.1.0

Additionally, you may need to verify all of the SNMP parameters. You can also check other OIDs as maybe it is not responding to this one as it should. If the system is mib-2 compatible, it may respond to:

.iso.org.dod.internet.mgmt.mib-2.system.sysUpTime

.1.3.6.1.2.1.1.3.0

Another thing to look at is how the device responds if you do use getif or something like that. Is the device returning an integer or other numeric value or is it replying with a string? If it's 70 degrees, is the device returning 70, 700, 70.0 or is it returning text such as "70 degrees"? Supplimental OIDs can't be used with strings so "70 degrees" won't show up as a valid sensor. 700 will but without a multiplier, you'll have to deal with 700 and create thresholds based on that.

If this fails, you may want to either troubleshoot with support or possibly work with Multivendorsupport@apcc.com. the latter is a team that creates DDFs for Data Center Expert.

Steve

DCIM_Support · ‎2020-07-02

Hi Steven, Thanks for the response. I actually use GETIF already, so I do know the actual OID, and in this case, it does not have the trailing '0'. In fact, it has a number of temperature sensors connected, with the last digit incrementing from 1 through to 22, for each of those sensors.

However, the variable being returned is a string, as it needs a decimal point in it, and MIBs don't support that as a number, so I guess this might be the problem. So, I tried a different OID which is supposed (i.e. as reported by GETIF) to return an integer, but I still don't get how to see that listed as a sensor in 'View Device Sensors'. By the way, I can also see sysUpTime on GETIF, but I can't see how to get DCE to grab that, and there is no variable type for 'timeticks'.

I suspect that I am missing some essential step in getting DCE to 'create' a sensor, but I can't find any step-by-step instructions for doing that.

DCIM_Support · ‎2020-07-02

Hi Hugh,

Maybe time ticks was a bad example, I didn't test it but was trying to think more generic OIDs. Th etrailing 0 is just the instance and if you're getting 31440.10.5.1.1.1 through 31440.10.5.1.1.22, that should work as well unless it is indeed a string.

Creating of a sensor should be automatic. If we discover the device properly, if we can poll the device with a supplemental OID, it should simply appear as a sensor. There is no "create sensor" option available or needed. Keep in mind that after you add the OID, you may have to either wait for the next polling cycle or right click the device and select request device scan.

Do you have any devices that are communicating and showing valid sensors? Can you try adding a supplemental OID on one of those devices....even if it is something already showing as a sensor. Just name it something you can easily find. Here's an example of output voltage that I added to a Smart-UPS:

.1.3.6.1.4.1.318.1.1.1.4.2.1.0

It should be just that simple:

Steve

DCIM_Support · ‎2020-07-02

OK. Just tried adding exactly that and our Symmetras are now showing the new sensor with value 240.0 V as per your picture. So, I'm a bit baffled as to how to get this other stuff working 😀

DCIM_Support · ‎2020-07-02

Hi Hugh,

Maybe you want to try running a packet capture. Make sure DCE is sending the correct requests and make sure the device is responding properly. If you contact tech support, they can help with this. If a remote session is possible, they can actually run one for you.

Try SNMP V1 if you're currently using V3. If the device uses V2c, it's not going to communicate properly. You seem to be setting up DCE properly so the only thing left is the communications between DCE and the specific device.

Steve

DCIM_Support · ‎2020-07-02

Hi Steve, It looks like I'll have to go the Tech Support route, cos I am using SNMP V1, and V3 is not an option for these devices. I have a scheduled visit form our support engineer next week, so I'll follow up that way. Thanks for your help.

Regards

Hugh

DCIM_Support · ‎2020-07-02

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