Discovery: How to work with single OID for multiple models?

[RK25]

We are discovering Endace network devices which carry same OID(1.3.6.1.4.1.18418.2.1) for various hardware models which is very strange to me because usually one unique OID goes with only one model. When we asked the vendor, they have confirmed that they are doing the same then asked us to use the following SNMP OID to grab the model info. Even OOTB there is no model showing up in the classify probe payload. So, I loaded the new MIB and I tried to add the below Managed Object to SNMP Fields under SNMP - Classify probe and also SNMP - Identify info probe but nothing is being returned. I am not sure if I am doing this correctly. I appreciate any further insight into this.

Thanks!

Managed Object	Type	Description
ENDACE-SYSTEM-MIB::systemModel.0	Display String	Model Identifier of the probe, e.g. "EP-82C4-G4"

[doug_schulze]

By just loading the MIB doesnt do anything in regards to device discovery, you have to call the OID in that MIB at some point of discovery to utilize it.

The case while not common, happens. You can look at the Generic Printer Classifier where we had to account for this situation with HP Printers. When it comes specifically to these devices you will probably need to add an extension step in the pattern it calls to get the model information from the specific manufacture location (OID/MIB) and populate it that way.

[RK25]

Thanks for the info Doug. I actually tried OIDs directly and I am able to get the info needed. Do I still need to load MID if I do this way?

Result:

[doug_schulze]

You do not need to add the MIB if you are calling the OID directly as the MIB is needed to do lookups to the same.

[SunnyK1]

I've seen this issue with some printers.

In my case, OID for system description contains the actual model name/number, even though the main unique OID is same for all the models

Created a new horizontal pattern that can identify and explore the CI. Couple of steps in the pattern can be used to query and regex and set parameter value for model/manufacturer based on sys_dscr. 

You would the sensor to set the make&model info for the CI. I've used sysIDs directly though.