Printers over SNMP
Poll your printers over SNMP for toner levels, online status and error conditions.
| Category | Printing |
| Authentication | SNMP community string |
| Reaches | Printers on your network |
| Needs an agent | Yes, on managed hosting |
| Demo mode | Yes, off by default |
Capabilities
Section titled “Capabilities”printer.status, printer.upsertCardUser
Which lights up the printers page, gated by the
module.printers module.
The private network question
Section titled “The private network question”Printers answer on your LAN.
Self-hosted on that network: reaches them directly. You will also want
ALLOW_PRIVATE_EGRESS=1, because Plugboard blocks outbound requests to private
address ranges by default.
Managed hosting: needs a connector agent on a machine that can reach the printer subnet.
Preparing the printers
Section titled “Preparing the printers”SNMP is usually enabled by default on network printers, but not always, and the community string is frequently left at the default.
For each printer, or across the fleet through your management tool:
- Enable SNMP v2c.
- Set a read-only community string. Change it from
publicif you can, and do not reuse the one your switches and access points answer to: a read-only string on a printer reads toner levels, and the same string on a switch reads the layout of your network. - Confirm the printer’s IP is static, or reserved in DHCP. A printer that moves address disappears from the fleet view.
Configuring it in Plugboard
Section titled “Configuring it in Plugboard”Admin, Connectors, Printers (SNMP), Configure.
Settings
Section titled “Settings”| Field | Default | Value |
|---|---|---|
hosts |
empty | Printer IPs or hostnames, comma-separated |
demoMode |
false |
Return a sample fleet, making no SNMP calls |
demoMode defaults to off. Enable it explicitly to explore sample data; leave
it off and configure real hosts for live polling.
Hostnames work if your DNS resolves them from wherever the polling happens. IP addresses are more reliable and are what most schools use.
Secrets (encrypted)
Section titled “Secrets (encrypted)”| Field | Default | Value |
|---|---|---|
community |
public |
The SNMP v2c community string |
The community string is the credential SNMP v2c authenticates with, and Plugboard treats it as one: it is sealed in the encrypted secret store with your other connector credentials rather than kept with the settings above.
Earlier releases kept it with the settings, in plain text. If you configured this connector before the change, upgrading moves it for you on the first start — there is nothing to re-enter — but the old value was stored in clear until then, and is still in clear in any backup taken before the upgrade. If the same community string is set on your switches or access points, change it.
On managed hosting, this field is not on the platform at all. Once the
connector is assigned to a site, an agent on your network
runs it and reads the community string from its own AGENT_SECRETS file:
{ "snmp-printers": { "community": "..." } }An instance set up before the change keeps polling with the string still in its settings, because the agent has no other way to receive it — the upgrade leaves those alone rather than breaking them, and the API log names them on each start. Move it to the agent’s file and then clear the field.
What you get
Section titled “What you get”For each printer:
| Toner and consumable levels | Per cartridge, as a percentage |
| Online or offline | |
| Error conditions | Paper jam, tray empty, cover open, and similar |
| Model and name | As the printer reports itself |
The value is finding out before a user does. Catch a printer at four percent cyan on a Thursday and you can get a cartridge to it before Friday’s newsletter.
Supported models include common Fuji Xerox and Fuji Film devices. Most printers implement the standard printer MIB, so the readings work broadly.
Sizing the host list
Section titled “Sizing the host list”A large school has more printers than anyone remembers. Rather than typing them from memory:
- Export the device list from your print management system, if you run one.
- Or scan the printer VLAN for anything answering on port 9100 or 631.
Start with the ones that matter (staff rooms, the print room, reception) and add the rest.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause |
|---|---|
| Sample printers appear | demoMode is still on |
| No response from a printer | SNMP disabled on it, or the wrong community string |
| Some printers work, others do not | Mixed community strings across the fleet. The connector uses one for all hosts |
| Everything times out on a self-hosted install | ALLOW_PRIVATE_EGRESS is not set |
| Everything times out on managed hosting | No agent, or the agent’s host cannot reach the printer subnet |
| Toner levels look wrong | Some printers report remaining pages rather than a percentage. Cross-check against the printer’s own panel |
| A printer vanished | Its IP changed. Use a DHCP reservation |
Related
Section titled “Related”PaperCut covers print management: who printed what, balances and card release. The two connectors answer different questions and schools that run PaperCut usually want both.