If multiple SNMP devices with different SNMP authencitation information, like different community or different username/passphrases, it's impossible to use templates, because this kind of information is bound to the template and cannot be edited in the "inherited" host items.

It would be much "better" to define the host related SNMP values like (SNMPversion, port, community, security level, security name, passphrases) with the host object instead of each object. For backwards compatiblity this behavior should be configurable for the users storing this info in the template.

Even better would to have the option to overwrite the SNMP information in the host-items, no matter where the initial data came from.

--Michael