There is a host that was discovered automatically via an SMTP discovery rule, for example:
Host: MySwitch
IP: 192.168.1.10
If that device dies and is replaced by a different model switch that has the same IP/hostname, that is not handled well by Zabbix and/or my discovery rules. Maybe I'm missing something, but I seem to constantly run into issues with the Zabbix discovery process. For example, see an older post: https://www.zabbix.com/forum/zabbix-...y-optimization
Anyway, after such a replacement occurs I get these messages in the log:
That template was linked to the formerly discovered device, but the new device uses a different template. It does successfully link the new template, but this error just keeps happening. Between this issue and the one I described in the post linked above I'm just about ready to give up and write my own autodiscovery script using the API.
Ideally, there would be a way in the GUI to completely erase a discovered host (ie no cheating and
Does anyone have a suggestion?
Host: MySwitch
IP: 192.168.1.10
If that device dies and is replaced by a different model switch that has the same IP/hostname, that is not handled well by Zabbix and/or my discovery rules. Maybe I'm missing something, but I seem to constantly run into issues with the Zabbix discovery process. For example, see an older post: https://www.zabbix.com/forum/zabbix-...y-optimization
Anyway, after such a replacement occurs I get these messages in the log:
cannot link template(s) "Adtran-AOS" to host "MySwitch": conflicting item key "bootrom" found
That template was linked to the formerly discovered device, but the new device uses a different template. It does successfully link the new template, but this error just keeps happening. Between this issue and the one I described in the post linked above I'm just about ready to give up and write my own autodiscovery script using the API.
Ideally, there would be a way in the GUI to completely erase a discovered host (ie no cheating and
Does anyone have a suggestion?