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

HP DesignJet T1600 Identified but no detailed metrics

Details

    • Vendor Bug
    • Resolution: Won't Fix
    • Major
    • None
    • Professional Edition
    • Discovery, Poller
    • Observium Professional 20.5.10436
      CentOS Linux release 7.8.2003 (Core)

    Description

      HP DesignJet T1600 plotter identified by discovery and correctly classified as a printer but no results (processor, memory, storage, supplies, status, counters, events, etc.) returned from polling.

      Attachments

        Issue Links

          Activity

            [OBS-3344] HP DesignJet T1600 Identified but no detailed metrics

            This is complete same trouble with incomplete and weird snmp data returned by device.

            Currently not possible for improve support for this devices.

            Try ask HP support for correct MIB. But as I see in many HP discussion forums, there no correct MIBs for this (and other new) HP printers.

            landy Mike Stupalov added a comment - This is complete same trouble with incomplete and weird snmp data returned by device. Currently not possible for improve support for this devices. Try ask HP support for correct MIB. But as I see in many HP discussion forums, there no correct MIBs for this (and other new) HP printers.

            I have added the requested discovery, poller, and snmpwalk results.

             

            FYI, snmpwalk returned:  Error: OID not increasing: .1.3.6.1.4.1.11.2.4.3.6.16.5.1 >= .1.3.6.1.4.1.11.2.4.3.6.16.1.2

             

            To resolve the error I had to add -Cc to the snmpwalk command...

             

            NegwerIT Scott Driemeier-Showers added a comment - I have added the requested discovery, poller, and snmpwalk results.   FYI, snmpwalk returned:  Error: OID not increasing: .1.3.6.1.4.1.11.2.4.3.6.16.5.1 >= .1.3.6.1.4.1.11.2.4.3.6.16.1.2   To resolve the error I had to add -Cc to the snmpwalk command...  

            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:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: