I need to figure out how to write an hp laserjet pro m203dn xml template from scratch to keep track of all the basic data like how much toner is left, cover open etc if possible. I have the output of the command "snmpwalk -v 1 -c public 10.113.1.30" but I don't know what to do next. I'm a complete noob at this.
Ad Widget
Collapse
How to create a template for an HP printer?
Collapse
X
-
-
Try this: https://github.com/Sean-Bradley/SNMP2ZABBIXI need to figure out how to write an hp laserjet pro m203dn xml template from scratch to keep track of all the basic data like how much toner is left, cover open etc if possible. I have the output of the command "snmpwalk -v 1 -c public 10.113.1.30" but I don't know what to do next. I'm a complete noob at this. -
I tried, it doesn't work, or I don't understand anything about it. Is there any easy to understand instructions?
Comment
-
Sorry, that is the best I found out there. If you can read the snmpwalk output, you can definitely setup the items on the host. I'm actuallydoing the same for a Deskjet mw15 at the moment. Some items are tricky depending on the units/type etc, but it's no that hard. You will need to read some documentation.
Here's what helped me do it:
-
-
-
well, I'll try again. thanks, I assumed that this script is the most correct option
Comment
-
It's not a very easy thing to do. I'm still fighting with this script because it's not pulling all of the OIDs from the printer.
It depends on what you need to do. In my case: I try to pull as many OIDs as possible with this script, and if I'm missing something I just user snmpwalk and snmpget if necessary.
Let me know if you got it to work. I'm also stuck with the preprocessing part, as SystemUpTimes are not working for me at the moment.
Best of luck!
-
-
Scripts like that are a way to automate creating items and sometimes triggers, when you need to collect a huge amount of data.
If you only need a few items, it's often very easy to just look through the MIB and decide what OIDs you want to gather. Creating a template isn't magic, it's just a collection of things like items, triggers, etc. that you can easily apply to a host. Writing the items "by hand" sometimes gives you a better understanding of what's going on than just using an automated tool. Of course, if the tool is working, its output can be used as another source of information and ideas for how to write your own items.
Comment
-
I need to figure out at least a little bit which oids are responsible for what. I don’t really rummage about this, I was given such a task to monitor the printer in zabbixScripts like that are a way to automate creating items and sometimes triggers, when you need to collect a huge amount of data.
If you only need a few items, it's often very easy to just look through the MIB and decide what OIDs you want to gather. Creating a template isn't magic, it's just a collection of things like items, triggers, etc. that you can easily apply to a host. Writing the items "by hand" sometimes gives you a better understanding of what's going on than just using an automated tool. Of course, if the tool is working, its output can be used as another source of information and ideas for how to write your own items.
Comment
-
In that case, you can often look at templates for other printers from the same manufacturer. There will be model-specific differences, but a lot of the most common OIDs will often be the same between different models.
Comment
-
Comment