Hi Richard: Sorry, I missed the first part of the thread - I have a Konica Minolta KMC-250 successfully connected to Nagios, so maybe you did already check this one w/o success...
I use the shell script available from <http://exchange.nagios.org/directory/Plugins/Hardware/Printers/check_snmp_printer/details>. When I run it on my printer, I see <snip> root@mybox:~# /opt/nagios/libexec/extra/check_snmp_printer np-kmc250 public CONSUM TEST Consumables you may Monitor: "Cyan Toner Cartridge" "Magenta Toner Cartridge" "Yellow Toner Cartridge" "Black Toner Cartridge" "Cyan Imaging Unit" "Magenta Imaging Unit" "Yellow Imaging Unit" "Black Imaging Unit" "Waste Toner Box" "Fuser Unit" "Transfer Unit" "Staple Unit" root@mybox:~# /opt/nagios/libexec/extra/check_snmp_printer np-kmc250 public CONSUM "Black Toner Cartridge" Black Toner Cartridge is OK </snip> It looks as if the Konica doesn't give much details (just good or bad); the same script on a HP says e.g. <snip> root@mybox:~# /opt/nagios/libexec/extra/check_snmp_printer np-hpclj4650 public CONSUM "Black Print Cartridge HP C9720A" OK,Black Print Cartridge HP C9720A is at 79%|Black Print Cartridge HP C9720A=79;;9000; </snip> I don't recall if I tweaked the script, though... the md5 hash here is affa3cee48d53a278093bed3ba528684 /opt/nagios/libexec/extra/check_snmp_printer Hth, Albrecht.
pgpMMwRW3sh49.pgp
Description: PGP signature
------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
