SNMP v3 adds authentication and encryption to SNMP, which v1 and v2c lack (those send a plain-text community string). Many enterprise environments require v3 as a security policy. Print Tracker supports SNMP v3 for both device discovery and meter and supply collection.
SNMP v3 has more moving parts than v1 or v2c, and most problems come down to one of two things: a field that does not match the device exactly, or a misunderstanding of how settings inherit. Read the next section before changing anything, because it explains the most common source of confusion.
How SNMP Settings Are Applied
Three facts explain most SNMP v3 support cases:
1. Install SNMP settings are used only to discover devices, not to collect meters. Meter collection uses the SNMP settings saved on each device. This is why an install can find a device successfully and then return no meters from it.
2. Devices and installs inherit SNMP settings from the entity by default. Changing an install's SNMP settings does not change the SNMP settings on the devices it discovered.
3. Best practice is to let installs inherit from the entity. Overriding an install creates exactly the failure above. If the entity is set to v1 or v2c while the install is set to v3, newly discovered v3 devices will be found but will not return meters, because the devices inherited the entity's v1/v2c settings.
Where a customer has devices configured with genuinely different SNMP v3 settings, those devices need their own settings applied and saved at the device level rather than inheriting from the entity. See Settings Inheritance: How Entity and Device Settings Work.
The SNMP Settings Group
SNMP lives under Shared default settings on an entity's Settings tab, and on the Settings tab of an install or device. The group holds four fields that apply to every SNMP version:
Field | What it does |
Max retries | How many times to retry a request before giving up on it |
Timeout | How long, in milliseconds, to wait for a response before timing out. Most devices answer v1 or v2c within 1000 ms. Slow devices, and v3 generally, need 3000 ms. |
Community | The v1/v2c community string. Commonly blank or |
Version | Which SNMP version to use, and the connection settings that go with it |
Click Save settings at the bottom of the screen after any change.
Retries and timeout are worth treating as a pair. A device that is merely slow looks identical to a device that is absent, and raising one or both is the cheapest fix for intermittent discovery failures.
Mixed v1/v2c and v3 Environments
You can configure SNMP v3 and a v1/v2c community string at the same time. Print Tracker attempts v3 first and falls back to v1/v2c if v3 fails, so a single install can handle a mixed fleet.
This means that when Print Tracker is configured for v3, devices that have v1/v2c enabled and v3 disabled will still return meters, as long as the configured community string is valid for them.
What SNMP v3 Requires
Print Tracker needs all of the following to match the device configuration. Every field is case-sensitive.
Field | Description | Notes |
Username (Security Name) | The SNMP v3 user account created on the device | Case-sensitive |
Authentication Protocol | The hashing algorithm used to verify identity | MD5 or SHA |
Authentication Password | Password for the authentication protocol | Case-sensitive, minimum 8 characters on most devices |
Privacy Protocol | Encryption algorithm, optional but common | DES or AES |
Privacy Password | Password for the encryption protocol | Required if privacy is enabled |
Context Name | An additional identifier some devices use to separate MIB namespaces | Must be a single entry. Multiple comma-separated entries are not supported. Required by some manufacturers, see below. |
Configuring SNMP v3
Using the sidebar, click Installs, then View installs.
Click the install to expand the row and open the Settings tab.
Expand the SNMP section and enable SNMP v3.
Enter the username, authentication protocol, authentication password, privacy protocol, and privacy password exactly as configured on the device.
If the device requires a context name, enter it in the Context field as a single value.
Save the settings. The install uses them on the next scan cycle.
Remember that this configures discovery. For meter collection, the same settings must be present on the device records, which normally happens through inheritance from the entity.
Raise the SNMP Timeout for v3
Collecting meters over SNMP v3 takes measurably longer than v1 or v2c because of the authentication and encryption overhead. If v3 devices are intermittently failing or returning partial data, increase the SNMP timeout to 3000 ms (3 seconds).
Test With a Topology Scan
After saving credentials, verify them rather than waiting for the next scheduled scan:
Go to Installs, then View installs, and expand the install.
Open Network Topology.
Enter the IP of a device that uses SNMP v3 and run the scan.
SNMP should show as a pass if the credentials are correct.
If SNMP still fails, recheck every field against the device's SNMP v3 user configuration. A single character difference in a username or password causes authentication to fail silently, with no distinct error to tell you which field is wrong.
Context Name by Manufacturer
In many cases the context is fixed by the manufacturer.
Manufacturer | Context | Notes |
Ricoh, Savin, Nashuatec |
| Required for most Ricoh-platform devices. Using |
HP and HP JetDirect |
| Required for many devices on the JetDirect firmware stack |
Sharp |
| Manufacturer default |
Lexmark, Toshiba | Varies | These allow a custom or preferred context to be configured on the device, so check the device rather than assuming a default. |
Konica Minolta bizhub | Usually blank | Older models may control v1/v2c and v3 separately in the device admin interface |
Kyocera TASKalfa and ECOSYS | Usually blank | Standard v3 without a context typically works |
Xerox AltaLink and VersaLink | Usually blank | Standard v3 typically works. Confirm the auth protocol matches the device setting. |
Troubleshooting
Symptom | Likely cause | Fix |
Device is discovered but returns no meters | The install was overridden to v3 while the entity, and therefore the devices, remained on v1/v2c | Set the SNMP configuration at the entity level and let the install inherit it, or apply v3 settings to the device records directly |
SNMP fails even with correct credentials | Context name mismatch | Add or correct the context for the manufacturer, as a single entry |
Discovery works but no supply data is returned | The context name is needed for the supply OIDs specifically | Add or correct the context for the manufacturer |
Some devices on the same network work, others fail | The failing devices are v1/v2c only, or use different v3 credentials | Check per-device SNMP settings. Configure both v3 and a v1/v2c community string so fallback can work. |
SNMP worked before and is now failing | Credentials were rotated on the device by IT security | Update the credentials in Print Tracker to match the new device values |
v3 devices intermittently fail or return partial data | Timeout too low for the v3 overhead | Raise the SNMP timeout to 3000 ms, and consider raising max retries |
Contacting Support
If the configuration appears correct but devices still fail to discover or return data, contact Print Tracker support with the device make and model, the install and entity names, and the topology scan results.
Do not include SNMP passwords in support tickets. The team can diagnose from topology scan results and the known context requirements for your device models without them.