Printer status OIDs

Printer status OIDs

Here are the below OIDs we use to get the status of the printer which are hard coded in OpManager:

1.   .1.3.6.1.2.1.25.3.2.1.5.1

Printer Operational status like Up, Down or Warning

2.    .1.3.6.1.2.1.25.3.5.1.1.1 

Printer Current status like idle, printing, or warmup

3.    .1.3.6.1.2.1.25.3.5.1.2.1

lowPaper, noPaper, noToner, doorOpen, jammed, offline

4.   .1.3.6.1.2.1.43.16.5.1.2.1.1

The content of a line in the logical display buffer of the operator's console of the printer like "Sleep mode on"

These OIDs are taken from the standard Printer-Mib which is available under /OpManager/Mibs.  So, mostly it should respond for all the printers.  If any particular printer model is not responding, we need to find the right OIDs and customize it in OpManager.


        New to ADManager Plus?

          New to ADSelfService Plus?

            • Related Articles

            • Prerequisites to check if VLAN not discovered or status shows Unknown

              Prerequisites to check if VLAN not discovered or status shows Unknown. Based on below OIDs result, we are showing VLANs information for Routers/Switches in OpManager. For Cisco category devices, load these two mib files CISCO-VTP-MIB and ...
            • SNMP OIDs used for Hardware Monitoring in OpManager.

              Please find the list of OIDs used to get the hardware information using SNMP. For Cisco devices: MIB Name: Cisco-envmon-mib  .1.3.6.1.2.1.47.1.1.1.1.13.1 - HW_MODEL .1.3.6.1.2.1.47.1.1.1.1.11.1 - HW Serial num Temperature: .1.3.6.1.4.1.9.9.13.1.3.1.2 ...
            • Server Disk utilization Formula(SNMP)

              OpManager uses HostResources.mib and its OIDs to calculate the disk utilization. The OIDs(and the responses) that you have to check are 1).1.3.6.1.2.1.25.2.3.1.2 :hrStorageType 2).1.3.6.1.2.1.25.2.3.1.4 : hrStorageAllocationUnits ...
            • Traps wrongly processed

              There are scenarios in which two trap OIDs from the same vendor are almost similar. Example  .1.3.6.1.4.1.6431.1.1.1.1515 .1.3.6.1.4.1.6431.1.1.1.15 Though the user have created separate trap processors for each trap OID, an incoming trap with a trap ...
            • Unable to start OpManager - PGSQL

              Sometimes OpManager will not start when the server ran out of disk space in the pg_xlog directory. It will not be possible to retrieve the connection to OpManager database. The files present under OpManager\pgsql\data\pg_xlog get disappeared in such ...