Welcome to Questions - Ask OpenNMS, where you can ask questions and receive answers from other members of the community.

Any ideas how to avoid this prtMarkerSuppliesDescription fuck-up?

0 votes

Some toner cartridges doesn’t provide a value for prtMarkerSuppliesDescription. I guess it’s some kind of factory error.


[root@srv-nms01 ~]# snmpget -v2c -c COMMUNITY wsprt01 SNMPv2-SMI::mib-

SNMPv2-SMI::mib- = STRING: "TK-130"

[root@srv-nms01 ~]# snmpget -v2c -c COMMUNITY wsprt07 SNMPv2-SMI::mib-

SNMPv2-SMI::mib- = ""


In this case a defined threshold (with filter prtMarkerSuppliesDescription = TK-130) won’t fire.

I could write a bash script which checks presence of “TK-130” or something like that. With send-event.pl I could generate an event/notifications. But is there a chance to avoid this with ONMS board tools?

OpenNMS version
asked Dec 2, 2013 by mfuhrmann (7,350 points)

1 Answer

0 votes
Best answer

I have a solution for this problem.

  1. bash script that check the problem (using send-event.pl)
  2. appropriate event definition
  3. appropriate notification

Unfortunately it's to large to post it here. If someone interessested, please contact me.

answered Apr 4, 2014 by mfuhrmann (7,350 points)