snmp Konica Minolta

[Richard Gliebe]

On 2/16/11 10:36 AM Andre Kruger wrote:

Hi Andre,

> You can do an SNMP-Walk on your printer. It usually, I know with my Kyocera machines it didn't,
> doesn't give you all of the OID's but you will get most of them.
> Who know, on your machines you might get all of them. You can run this command from your Nagios machine:
>
> snmpwalk -v1 -c public x.x.x.x
>
> or just type "snmpwalk" and hit enter and it will give you all of the options.

I've already run a snmpwalk and found the OIDs for the Cartridges

# snmpget -v1 -cpublic <printer> 1.3.6.1.2.1.43.11.1.1.6.1.1
SNMPv2-SMI::mib-2.43.11.1.1.6.1.1 = STRING: "Cyan Toner Cartridge"

# snmpget -v1 -cpublic <printer> 1.3.6.1.2.1.43.11.1.1.6.1.2
SNMPv2-SMI::mib-2.43.11.1.1.6.1.2 = STRING: "Magenta Toner Cartridge"

# snmpget -v1 -cpublic <printer> 1.3.6.1.2.1.43.11.1.1.6.1.3
SNMPv2-SMI::mib-2.43.11.1.1.6.1.3 = STRING: "Yellow Toner Cartridge"

# snmpget -v1 -cpublic <printer> 1.3.6.1.2.1.43.11.1.1.6.1.4
SNMPv2-SMI::mib-2.43.11.1.1.6.1.4 = STRING: "Black Toner Cartridge"

But I can't find the right OIDs for the Toner.
Normally the OIDs are.

MAX=1.3.6.1.2.1.43.11.1.1.8.1.1
LEVEL=1.3.6.1.2.1.43.11.1.1.9.1.1

but these OIDs are not the right one for these $§#! Konica Minolta Printers.

I need these Minolta OIDs for my check_toner script.

many thanks
Richard

------------------------------------------------------------------------------
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
Nagios-users at lists.sourceforge.net
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