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.  

[Dave Ainsworth · Accepted solution]

Hi Barb,

Yes, I have seen this. It is as you say Lexmark populating the prtGeneralSerialNumber with extra information to include model. You would need to ask Lexmark why they have decided to do this although the description of prtGeneralSerialNumber is a little vague which is maybe why Lexmark decide to do this. However, I haven't seen any other manufacturer do this.

Although you can access the SysDesc in the on classification script, I am not sure you can really use this for identification.

Lexmark has the serial number in a different OID within LEXMARK-PVT-MIB:

1.3.6.1.4.1.641.2.1.2.1.6

This means you have to load the MIB, create a new classifier, new identifier and multisensor script. Have a look at the F5 Classifier/Identifier which works in a very similar way in that it looks at a specific F5 OID to obtain the serial number.

Regards,

Dave

[barb_perronne]

Thank you for the advice.   I am thrilled to give this a try.

[barb_perronne]

Thank you to both David, Ravindra (response here) and Doug Schulze (great SNMP Classifier YouTube), I am posting some details I used to resolve because "sharing is caring" and I hope it will help others.

1. Go to OIDVIEW to download MIB's for LEXMARK-PVT-MIB

2. Remove extension from file

3. Load MIB into ServiceNow using-> MID Server > SNMP MIBs

3.a. attach file

4. Re-Start MID Server(s) while watching the ECC Queue for errors (there were no errors)

5. Create new exploration probe using -> Discovery Definition > Probes

6.   I created a user field for the serial number without a dash.

7. Create a new sensor for this new probe (named SNMP - Explore Lexmark MIB sn) using -> Discovery Definition > Sensors.

(Note: I do not have the script populating the field and I am having our developer Kaushik help me with the script. Still tweaking, but all this is finding the data when I Test Probe )

8. Modify CI Classifier using -> Discovery Definition > CI Classification> SNMP

8.a. select --existing--> Standard Network Printer

8.b. (tab) Triggers probe ... (button) Edit ... select probe from slush bucket

8.c. add a conditional script for Lexmark only (values.get("sysdescr").indexOf('Lexmark') > -1)

9. Return to CI Classifier

10. Test Probe finds the data

Thank you ServiceNow Community for all the help!   Barb

[DUGGI]

Have a look

Free Lexmark International MIB Download Search MIBs Download MIBs for Lexmark International Network ...