![Clontarf[X]](data:image/svg+xml;base64,CgkJCTxzdmcgeG1sbnM9J2h0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnJyB2aWV3Qm94PScwIDAgNTAgNTAnPgoJCQkJPHJlY3Qgd2lkdGg9JzEwMCUnIGhlaWdodD0nMTAwJScgZmlsbD0nI2RhYzZkMycgLz4KCQkJCTx0ZXh0IHg9JzUwJScgeT0nNTAlJyBmaWxsPSd3aGl0ZScgZm9udC13ZWlnaHQ9J2JvbGQnIGZvbnQtZmFtaWx5PSdBcmlhbCcgZm9udC1zaXplPSczMDAlJyBkb21pbmFudC1iYXNlbGluZT0nY2VudHJhbCcgdGV4dC1hbmNob3I9J21pZGRsZSc+QzwvdGV4dD4KCQkJPC9zdmc+CgkJ "Clontarf[X]")
VMware FQDN discovery currently seems to grab all IP addresses presented via the API for a guest. This causes an issue for monitoring where a discovered IP may be internally routable and not available from Zabbix's perspective.
Is there a way to tell Zabbix VMware LLDP discovery to ignore certain IP addresses or ranges/subnets? The problem is that the host prototype sets the interfaces to read-only, meaning you cannot change the primary interface via the frontend.
Is there a way to tell Zabbix VMware LLDP discovery to ignore certain IP addresses or ranges/subnets? The problem is that the host prototype sets the interfaces to read-only, meaning you cannot change the primary interface via the frontend.