Hello,
as per title, we have several items with 2 snmp interfaces on different ip addresses. These interfaces are to be processed by the same template. The only reason we have 2 interfaces on the same host that needs to be processed in the same way, is because the system that can send trap has a redundancy. So, when everything is normal, the traps are received from ip1; in case of a fault on the source, the traps are received from ip2.
I’ve noticed that, despite having the ability to create multiple snmp interfaces on the same host, these are not working at the same time. The host is created with snmp interface on ip1 as default, snmp interface on ip2 below. In this configuration traps from ip2 are ignored, even if I chose that interface as default. The only way I can make Zabbix process traps from ip2 is to completely delete the interface with ip1.
I do not have experience on hosts with multiple interfaces, but I assumed that they could work at the same time. Probably this is true only for different type of interfaces, or that the snmp interface is somewhat limited. I’d like to know your opinions on this, if this may be considered a bug or a normal behaviour that needs a workaround. In my case, the only solution we come up is to import an updated node configuration should we need it. However, considering that we have more than 1k nodes like this, we need a more elegant solution.
Thanks!
as per title, we have several items with 2 snmp interfaces on different ip addresses. These interfaces are to be processed by the same template. The only reason we have 2 interfaces on the same host that needs to be processed in the same way, is because the system that can send trap has a redundancy. So, when everything is normal, the traps are received from ip1; in case of a fault on the source, the traps are received from ip2.
I’ve noticed that, despite having the ability to create multiple snmp interfaces on the same host, these are not working at the same time. The host is created with snmp interface on ip1 as default, snmp interface on ip2 below. In this configuration traps from ip2 are ignored, even if I chose that interface as default. The only way I can make Zabbix process traps from ip2 is to completely delete the interface with ip1.
I do not have experience on hosts with multiple interfaces, but I assumed that they could work at the same time. Probably this is true only for different type of interfaces, or that the snmp interface is somewhat limited. I’d like to know your opinions on this, if this may be considered a bug or a normal behaviour that needs a workaround. In my case, the only solution we come up is to import an updated node configuration should we need it. However, considering that we have more than 1k nodes like this, we need a more elegant solution.
Thanks!