Lexmark Printer Serial Number

[barb_perronne]

Has anyone modified a discovered printer serial number? Discovery SNMP OID serial number has dashes but (Lexmark) vendor says their serial numbers does not contain dashes. They claim the serial number is only the numbers to the left of the first dash.

Lexmark printer's are discovered via Discovery.     The SNMP OID Serial Number has a dash, but the vendor (Lexmark) says the serial number in their system has no dashes.   The business reason for the question is we are trying to intergrate ticketing systems with REST calls: Kohler uses ServiceNow and Lexmark uses Siebel.   They decided to use serial number as the uinque identifier.   REST calls are failing because the serial number does not match.   Upon examination is appears the SNMP OID has a syntax of "serial number-model=number". For example SNMP OID lists serial as 7558100415344-106-0.   Lexmark's system has only 7558100415344 as the serial number. The ServiceNow serial numbers with -160- are all Lexmark Model ID X954.   Also, the payload from Discovery has no other entry for serial number.   Weirdly, the serail number wihtout dashes is part of the SNMP OID short description.   Don't know how to parse only serial number from short description.

My question is part of a multiple phase approach.   Other phases include asking the Lexmark why the device SNMP OID for serial number contains dashes.   Also, if this can be changed on the device. Another phase is to have the developers working on the REST calls come up with development options.  

[shivanipatel]

Barb,

We are glad you took advantage of the ServiceNow Community to learn more and to get your questions answered. The Customer Experience Team is working hard to ensure that the Community experience is most optimal for our customers.

If you feel that your question was answered, we would greatly appreciate if you could mark the appropriate thread as "Correct Answer". This allows other customers to learn from your thread and improves the ServiceNow Community experience.

If you are viewing this from the Community inbox you will not see the correct answer button.   If so, please review How to Mark Answers Correct From Inbox View.

Thanks,

Shivani Patel

[michaelwatts]

Hi Barb,

I thank you for sharing your post on creating the probe and sensor for LexMark printer serial numbers.   May I ask that you share the script that you used to populate the field as well.  

Thanks.

[holly-t]

This has been so helpful I thought i would post my script for Michael. This is probably not the best, but it works.

new DiscoverySensor({

      process: function(result) {

            var snmp = new SNMPResponse(result);

            var oid_mib_lexmark = 'iso.org.dod.internet.private.enterprises.lexmark.';

            var serial_no = snmp.getOIDText(oid_mib_lexmark + 'printer.prtgen.prtgenInfoTable.prtgenInfoEntry.prtgenSerialNo');

                      current.u_mib_serial_no = serial_no;

},

          type:"discoverySensor"

});

[michaelwatts]

Thank you so much Holly for your assistance.   Yes it does work!!!!

[Chris Ellis]

Has anyone else noticed that this solution causes the Serial Number to bounce back and forth in the audit history of each device? Perhaps I am doing something inaccurately, but what I am seeing is that the SNMP - Identify probe is using the generic OID to set the Serial (with the dashes) during the Identification phase and then changing it to the Lexmark-specific Serial during the Exploration phase. On the next disco, it does the same thing. So, in the audit history, you see the Serial Number field bouncing back and forth. Anyone else?