Skip to main content

SNMP version 3 devices not reporting

Configuring SNMP version 3 Settings for Entities, DCAs and Devices

G
Written by Gary Martin
Updated over 4 months ago

Each device's > settings > SNMP version 3 entries need to match what the SNMP settings saved on the device.

By default, devices and DCAs inherit SNMP setting from the entity.

Changing a DCA’s SNMP settings does not change device SNMP settings.

DCA SNMP settings are only used to discover devices, not for meter collection.

When Print Tracker Pro is configured to use SNMP v3, devices with SNMP v1/2c enabled and SNMP v3 disabled will return meters if the Print Tracker Pro SNMP community string is valid.

Gathering meters from devices using SNMP v3 takes more time than v1/2c, so the SNMP timeout may need to be increased up to 3000 (3 seconds).

Best practice is to have DCAs inherit SNMP settings from the entity (if the entity used v1 or v2, but the DCA used v3, then new v3 devices would be discovered but not return meters)

In cases where a customer’s devices are configured with different SNMP version 3 settings, then those not using the entity SNMP settings would need SNMP v3 settings applied and saved (not inherit from the entity)

The ‘Context’ entry should contain a single entry. (Multiple entries separated by a comma are not supported)
Some makes and models allow users to configure devices with a custom/preferred context. Examples are Lexmark and Toshiba

In many cases the ‘Context’ used is set by the manufacturer. For example: ‘Jetdirect’ is used by HP, ‘GWNCS’ is used by ‘Ricoh’, ‘mfpdirect’ is used by Sharp.

Did this answer your question?