Hi,
how exactly does the "status" key check the status of a host?
We have two independent uplinks here and the zabbix server monitoring the systems behind these uplinks is located in another datacenter.
Yesterday the gateway system handling the first uplink was not accessible for a few minutes and zabbix reported the systems behind it unreachable as expected.
The problem is that it also reported many systems behind the other uplink as unreachable and I have no idea why that could be. The only thing I can think of is that the primary nameserver for all systems is locate behind the first uplink and I'm wondering if that could be an issue. If "status" accesses the agent then it might try to resolve the servers domain name in the config file to check if the server is allowed to access the agent and that might be a problem without proper dns resolution. OTOH if "status" does a simple ping I'm not sure why zabbix would report the system behind the properly working uplink as unreachable?
Regards,
Dennis
how exactly does the "status" key check the status of a host?
We have two independent uplinks here and the zabbix server monitoring the systems behind these uplinks is located in another datacenter.
Yesterday the gateway system handling the first uplink was not accessible for a few minutes and zabbix reported the systems behind it unreachable as expected.
The problem is that it also reported many systems behind the other uplink as unreachable and I have no idea why that could be. The only thing I can think of is that the primary nameserver for all systems is locate behind the first uplink and I'm wondering if that could be an issue. If "status" accesses the agent then it might try to resolve the servers domain name in the config file to check if the server is allowed to access the agent and that might be a problem without proper dns resolution. OTOH if "status" does a simple ping I'm not sure why zabbix would report the system behind the properly working uplink as unreachable?
Regards,
Dennis