Map Printer OID to discovered CI via OOB Probe+Sensor

[GusPosadaFlorez]

Hello Community!

I have an issue regarding the retrieval and mapping of OID 1.3.6.1.2.1.1.4 sysContact reference info (oidref.com) via the OOB "SNMP - Printing" Probe.

I see the sysName, sysDescr, and sysObjectID from the "SNMP - Classify: 9 OIDs" XML input, but I need to retrieve the sysContact and sysLocation and map it to the Printer's Comments <cmdb_ci_printer.comments>.

There is no need to import any MIB, since it is already part of all known SNMP devices.

Help?!

Anybody with doogiesd contact via NowCommunity? or @Chuck Tomasi ? 

[doug_schulze]

Gus,

You would want to create a new probe/sensor that you will add to the printer classifier (in exploration) that will pull those specific OIDs and put them in the appropriate field(s). You might consider using the existing location field if you can and perhaps short description as another instead of comments...but what you want to do is achievable.

[GusPosadaFlorez]

Thank you very much for answering @doug.schulze !

I have achieved this using your youtube video, but via a Pattern.

I would like to only do it via SNMP Probe+Pattern... how do I add those specific fields to the current SNMP - Printing probe and process it via sensor?

This is what I got (see image) but the paramenter has no OID field?
Also the Sensor is not updating anything to the right CI 😞

Help please!

 

[doug_schulze]

I wouldn't do it inside another probe. That's why @aleck.lin  built the multiprobe when you need two probes to be processed by a single sensor but, too much hassle to figure out the combination to get it to work.

Instead, keep it its own individual (exploration) probe. Makes the work much easier.

Otherwise, seems that you aren't getting all the values you would expect from these fields, try using an external MIB browser to make sure responses come back. Reading that you proved this already in patterns might make that a moot point but do make sure you are asking the right questions.

Also, consider logging out your variables to make sure they are getting what you expect them to hold..log statements in sensors go a VERY long way! But here's a crazy thought if you have it working in patterns, why not trigger a horizontal pattern in exploration in the printer classifier that does the work you already proved? I've never tried but I have to think there could be something there... #probesandsensorsforlife and all but if that works, then goal achieved...

[GusPosadaFlorez]

Thank you very much for your support @doug.schulze !

Just to confirm, does it makes sense to have a custom Pattern in Trigger Probes as part of the OOTB "Standard Network Printer" SNMP Classification?

The images bellow show how the custom Pattern gets the job done.

... still, I believe there most be a way to make this information retrieval more OOTB alike. Do you know if there is anywhere how the process of OIDs are being added to the SNMP query, then how the Script is meant to be "written" to find & mapped to values to CI fields?