Details
Description
The management UI of the device reports a different pages printed total (418681) than Observium (423237). Is it possible Observium is pulling from the wrong MIB value?
- cat myagent.snmpwalk | egrep "423237|418681"
.1.3.6.1.2.1.43.10.2.1.4.1.1 = Counter32: 423237
.1.3.6.1.4.1.1347.43.10.1.1.12.1.1 = INTEGER: 418681
Attachments
Issue Links
- relates to
-
OBS-3346 Kyocera MFP Waste Toner always reads 1%
-
- Closed
-
Activity
We are on rolling updates already.
Re-discovery and re-poll worked.
Switch to rolling updates and rediscovery device.
https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains
Updated to v22.5.12055 and issue still exists (new image attached). MIB does not appear to be downloadable from the device. I have requested the MIB from our vendor.
Main trouble - printer report incorrect counts in common Printer-MIB (.1.3.6.1.2.1.43.10.2.1.4.1.1):
Printer-MIB::prtMarkerLifeCount.1.1
|
For use vendor specific MIB/Oid (.1.3.6.1.4.1.1347.43.10.1.1.12.1.1) need attach this vendor specific MIBs (probably from device management settings).
Attaching the outputs from discovery and poller for one of our devices.
Waiting on the full snmpwalk commands to complete (they're taking a long time), then will attach those as well.
General questions and device support can be discussed in our Discord channel, click here to join.
Please make and attach additional information about the device:
- full snmp dump from device:
snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalksnmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalkIf 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
This comment is added automatically.
FYI, response from manufacturer on device-specific MIB:
"If they can’t get what they want from the Standard Printer MIB and want our private MIB we need to know who is asking, why, and they have to sign an NDA.
If they already know the OID the data they need is in I am not sure they need to go through all that. Just point the total count at the other OID.
We take care of releasing the MIB. Let me know what they want to do."