Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3346

Kyocera MFP Waste Toner always reads 1%

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Poller
    • CentOS Linux release 7.8.2003 (Core)
      Observium Professional 20.5.10439 (rolling)

    Description

      The printer supply monitor of all Kyocera models company-wide report the "Waste Toner Box" at 1%, which trips an alert that the supply is nearing empty – even after being replaced with a new/empty waste box – making it impossible to track.

      I don't know if this is similar to the Ricoh issue OBS-2047 or not, but that might be a place to look for clues?

      Attachments

        1. kyocera_discovery.txt
          66 kB
        2. kyocera_graph.png
          kyocera_graph.png
          32 kB
        3. kyocera_obs.png
          kyocera_obs.png
          6 kB
        4. kyocera_poller.txt
          93 kB
        5. kyocera_toner.png
          kyocera_toner.png
          6 kB

        Issue Links

          Activity

            [OBS-3346] Kyocera MFP Waste Toner always reads 1%

            Waste toner shows 80% in this case.

            landy Mike Stupalov added a comment - Waste toner shows 80% in this case.

            I (obviously) can't speak for everyone; but it seems to me that this being a non-graphed "OK/NOT OK" measure would be acceptable and give us the ability to alert based on "NOT OK".  And, yes, I know I oversimplified things in that description.

            Thanks!

            NegwerIT Scott Driemeier-Showers added a comment - I (obviously) can't speak for everyone; but it seems to me that this being a non-graphed "OK/NOT OK" measure would be acceptable and give us the ability to alert based on "NOT OK".  And, yes, I know I oversimplified things in that description. Thanks!
            adama Adam Armstrong added a comment - - edited

            In the code we handle this like so : 

            I think changing -3 to 100 might suffice, though it's also giving some incorrect information

            switch ($level)

            { case '-1': $level = 100; // Unlimit break; case '-2': $level = 0; // Unknown break; case '-3': $level = 1; // This is wrong SuppliesLevel (1%), but better than nothing break; }
            adama Adam Armstrong added a comment - - edited In the code we handle this like so :  I think changing -3 to 100 might suffice, though it's also giving some incorrect information switch ($level) { case '-1': $level = 100; // Unlimit break; case '-2': $level = 0; // Unknown break; case '-3': $level = 1; // This is wrong SuppliesLevel (1%), but better than nothing break; }

            This seems to be a limitation of how this is reported by the end device : 

            prtMarkerSuppliesDescription.1.2 = "Waste Toner Box"
            prtMarkerSuppliesSupplyUnit.1.2 = impressions
            prtMarkerSuppliesMaxCapacity.1.2 = -2
            prtMarkerSuppliesLevel.1.2 = -3

            prtMarkerSuppliesMaxCapacity

            "The maximum capacity of this supply container/receptacle
            expressed in prtMarkerSuppliesSupplyUnit. If this supply
            container/receptacle can reliably sense this value, the value
            is reported by the printer and is read-only; otherwise, the
            value may be written (by a Remote Control Panel or a Management
            Application). The value (-1) means other and specifically
            indicates that the sub-unit places no restrictions on this
            parameter. The value (-2) means unknown."

            prtMarkerSuppliesLevel

            "The current level if this supply is a container; the remaining
            space if this supply is a receptacle. If this supply
            container/receptacle can reliably sense this value, the value
            is reported by the printer and is read-only; otherwise, the
            value may be written (by a Remote Control Panel or a Management
            Application). The value (-1) means other and specifically
            indicates that the sub-unit places no restrictions on this
            parameter. The value (-2) means unknown. A value of (-3) means
            that the printer knows that there is some supply/remaining
            space, respectively."

            adama Adam Armstrong added a comment - This seems to be a limitation of how this is reported by the end device :  prtMarkerSuppliesDescription.1.2 = "Waste Toner Box" prtMarkerSuppliesSupplyUnit.1.2 = impressions prtMarkerSuppliesMaxCapacity.1.2 = -2 prtMarkerSuppliesLevel.1.2 = -3 prtMarkerSuppliesMaxCapacity "The maximum capacity of this supply container/receptacle expressed in prtMarkerSuppliesSupplyUnit. If this supply container/receptacle can reliably sense this value, the value is reported by the printer and is read-only; otherwise, the value may be written (by a Remote Control Panel or a Management Application). The value (-1) means other and specifically indicates that the sub-unit places no restrictions on this parameter. The value (-2) means unknown." prtMarkerSuppliesLevel "The current level if this supply is a container; the remaining space if this supply is a receptacle. If this supply container/receptacle can reliably sense this value, the value is reported by the printer and is read-only; otherwise, the value may be written (by a Remote Control Panel or a Management Application). The value (-1) means other and specifically indicates that the sub-unit places no restrictions on this parameter. The value (-2) means unknown. A value of (-3) means that the printer knows that there is some supply/remaining space, respectively."

            Attached snmpwalk, discovery, and poller results.

            Also attached screenshots of the unit web interface showing toner and waste box status (OK), the Observium "printer supplies" section from the device page, and the Observium status graph showing stuck at 1%.

            NegwerIT Scott Driemeier-Showers added a comment - Attached snmpwalk, discovery, and poller results. Also attached screenshots of the unit web interface showing toner and waste box status (OK), the Observium "printer supplies" section from the device page, and the Observium status graph showing stuck at 1%.

            Please make and attach additional information about the device:

            • full snmp dump from device:

              snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
              snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

              If device not support SNMP version 2c, replace -v2c with -v1.

            • If you have problems with discovery or poller processes, please do and attach these debugs:

              ./discovery.php -d -h <device>
              ./poller.php -d -h <device>

            • additionally attach device and/or vendor specific MIB files

            Note, this comment is added automatically.

            bot Observium Bot added a comment - Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files Note, this comment is added automatically.

            People

              landy Mike Stupalov
              NegwerIT Scott Driemeier-Showers
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: