In the decoupling of the the SNMP version from the template SNMP items (which is normally a good thing), we have an (apparently) unique situation:
Most of our hosts have SNMP items, which use a macro for their community string, but we also have two specific SNMP items, one uses "public" and one uses "private". The purpose of these items is to detect hosts that allow these community strings, and generate a problem if they do.
When we upgraded, this caused all of our hosts to now have 3 SNMP interfaces (one for each community string). none of the 3 can be deleted, even if I change which one is the default. I'm assuming somehow internally, the two items that have their specific communities are associated with the relevant interfaces, but this isn't visible anywhere (except in the fact that I can't delete the extra interfaces, whereas new hosts created (by clone) after upgrading, while having 3 interfaces, do let me delete the extra two. I don't know what this does to the public/private specific items).
Or, is Zabbix going to try to use all 3 interfaces (until one succeeds) when a request fails? (is this what Zabbix does when there are multiple of an interface type?) It also appears its picked an undesirable (not the one with the macro for the community) interface as the default, when it moved these to the hosts.
So what's the best way to clean this up (if I just delete the two special items, will I then be able to delete the extra interfaces, not that I relish having to do that for 1000s of hosts, probably try to figure out how to do it via SQL instead)? The two special items are in a template, but if I remove the template will that get rid of the extra interfaces, or will they remain?
Is it even possible now to implement this functionality? (there appears to be no way to override the community for a specific item) (I'm thinking maybe a JavaScript item could probe for public/private, instead of an SNMP item)?
Most of our hosts have SNMP items, which use a macro for their community string, but we also have two specific SNMP items, one uses "public" and one uses "private". The purpose of these items is to detect hosts that allow these community strings, and generate a problem if they do.
When we upgraded, this caused all of our hosts to now have 3 SNMP interfaces (one for each community string). none of the 3 can be deleted, even if I change which one is the default. I'm assuming somehow internally, the two items that have their specific communities are associated with the relevant interfaces, but this isn't visible anywhere (except in the fact that I can't delete the extra interfaces, whereas new hosts created (by clone) after upgrading, while having 3 interfaces, do let me delete the extra two. I don't know what this does to the public/private specific items).
Or, is Zabbix going to try to use all 3 interfaces (until one succeeds) when a request fails? (is this what Zabbix does when there are multiple of an interface type?) It also appears its picked an undesirable (not the one with the macro for the community) interface as the default, when it moved these to the hosts.
So what's the best way to clean this up (if I just delete the two special items, will I then be able to delete the extra interfaces, not that I relish having to do that for 1000s of hosts, probably try to figure out how to do it via SQL instead)? The two special items are in a template, but if I remove the template will that get rid of the extra interfaces, or will they remain?
Is it even possible now to implement this functionality? (there appears to be no way to override the community for a specific item) (I'm thinking maybe a JavaScript item could probe for public/private, instead of an SNMP item)?