Hi!
We've configured our setup with port fowarding on iptables using this method: https://lab4.org/wiki/Zabbix_Iptables_Portforwarding to access isolated instances that we'd like to monitor. The NATing works wonderfully as a zabbix_get request goes all the way to the required host. This confirms that the iptables and the zabbix_agent configuration is good.
The issue is when we set the port to something else than 10050 (in our case, 10052) on the server GUI for the isolated host, the Zabbix Server won't even try to poll the host and simply shows an connection error (red Z logo instead of blue). We validated this with a tcpdump port 10052 -i eth0 on the Zabbix Server and 0 packets are being sent!!! Then again, when we do a manual poll with zabbix_get (zabbix_get -s ip -k vm.memory.size[available] for instance) we see traffic on our tcpdump.
My question is, why isn't the server trying to poll the host at all??? Our Zabbix Server is on version 2.2.23
Thank you!
We've configured our setup with port fowarding on iptables using this method: https://lab4.org/wiki/Zabbix_Iptables_Portforwarding to access isolated instances that we'd like to monitor. The NATing works wonderfully as a zabbix_get request goes all the way to the required host. This confirms that the iptables and the zabbix_agent configuration is good.
The issue is when we set the port to something else than 10050 (in our case, 10052) on the server GUI for the isolated host, the Zabbix Server won't even try to poll the host and simply shows an connection error (red Z logo instead of blue). We validated this with a tcpdump port 10052 -i eth0 on the Zabbix Server and 0 packets are being sent!!! Then again, when we do a manual poll with zabbix_get (zabbix_get -s ip -k vm.memory.size[available] for instance) we see traffic on our tcpdump.
My question is, why isn't the server trying to poll the host at all??? Our Zabbix Server is on version 2.2.23
Thank you!
Comment