Zabbix Agent Unreachable Issue - Seeking Assistance

[SusanEmelia]

I'm currently encountering a perplexing issue in our Zabbix environment, and I'm reaching out to seek advice and insights from the experienced members of this community.

Here's the problem I'm facing:

• The Zabbix agent reports as being unreachable.
• However, I can successfully ping the host.
• The Zabbix agent service is running without any apparent issues.

I've configured our item using agent.ping, and the trigger is set as follows: {host.name:agent.ping.nodata(5m)}=1
Has anyone else encountered a similar issue?

[LenR]

On your zabbix server, use a command to see if the agent port is open on the client, for example: nmap -p 10050 client-ip

It needs network combativity to work, check firewalls that are allowing ping but not the agent port traffic.

[SusanEmelia]

On your zabbix server, use a command to see if the agent port is open on the client, for example: nmap -p 10050 client-ip

It needs network combativity to work, check firewalls that are allowing ping but not the agent port traffic.

Thanks for your suggestion.

[santosra02]

Are you using Zabbix Proxy in your environment ? if so, consider run the test directly from the proxy to the host

Since Zabbix make use of tcp ports 10050 and 10051 , you must have these ports allowed in your network firewall. Is good to check the machine firewall status as well.

For any reason if you are not able to use nmap as suggested by LenR, you can use netcat to check the remote ports as well: nc -vz <IP> <PORT>