[ZBX-4422] SNMP version and community string should be configured per host and not per item Created: 2011 Dec 08  Updated: 2017 May 30  Resolved: 2011 Dec 08

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: None
Affects Version/s: 1.9.9 (beta)
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Eugene Varnavsky Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Currently SNMP version and SNMP community string (login and password in case of SNMP v3) are set on per-item basis. But this does not correlate with real life, where different hosts may have different SNMP versions and credentials, but where it is impossible for one host to have different community strings for different SNMP OIDs.

In this case if we have several devices of same model but with with different SNMP community strings set, the only way to make everything work is to clone the template, change community string values in all items in this template, and then use one template for one device and another for another device.

 Comments   
Comment by richlv [ 2011 Dec 08 ]

1. it is possible to have different community strings required for different oids;
2. different snmp community string per device (when using a single template) can be set with usermacros (they are supported in the community field) - this means that you don't have to clone the template;
3. different snmp version for devices with exact same mib tree (so that same template can be used) might be not a common thing - but if you have a specific case like that, please reopen this issue (and we'll move it to feature request project )

Generated at Sun Aug 03 03:41:06 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.