Discovery by Proxy 3.4.1

[r.monakhov]

Zabbix Server 3.4.1 + active proxy 3.4.1 (PSK).

I have discovery proceses by proxies, wich use these checks:

SNMPv2 agent ".1.3.6.1.2.1.1.1.0"
Zabbix agent "system.uname"

Result is correct: recieved value and type of service are OK.

Then discovery action with condition:

Discovery rule = RULENAME
Discovery status = Up

Do operations:

Add to host groups: SOMEGROUP
Remove from host groups: Discovered hosts

The problem is that added hosts have interfaces without ports (SNMP or Agent). Is it bug or what it could be? Zabbix 3.2.7 + Proxy 3.2.7 working good.

[jp7x7]

Same issue

I am having the exact issue. Same version of Zabbix. Kind of a pain to manually change them all.

I've also noticed that when you change the SNMP port to 161, devices will then collect as they should but then discovery adds yet another interface with a port of 0 again.

[r.monakhov]

I am having the exact issue. Same version of Zabbix. Kind of a pain to manually change them all.

I've also noticed that when you change the SNMP port to 161, devices will then collect as they should but then discovery adds yet another interface with a port of 0 again.

I found that this would be fixed in 3.4.2:
3.4.2rc2 [ZBX-12708] fixed service port validation if auto-discovery is performed by the zabbix proxy

[AcesAndrew]

workaround

We had the same issue, but we found a workaround, since most of discovered devices in our network are SNMP managed devices, and... we are using hostname_from_snmp.sh script to automatically change name of devices which are added through discovery, we added a line into that script, to automatically change port from 0 to 161(SNMP). And of course made an action, which add hosts to host group, link them to a specific template, and execute external script(on server or on proxy) which modify hostaname and SNMP interface port.

I attached the script(you have to change the extension from .txt to .sh), if you want you can use it until the bug will be fixed.