--reject-with icmp-port-unreachable -A KUBE-SERVICES -d 10.96.61.252/32 -p tcp -m comment --comment "default/nginx-64: has no endpoints" -m tcp --dport 80 -j REJECT --reject-with icmp-port-unreachable -A KUBE-SERVICES --reject-with icmp-port-unreachable -A KUBE-SERVICES -d 10.98.85.41/32 -p tcp -m comment --comment "default/nginx-9: has no endpoints" -m tcp --dport 80 -j REJECT --reject-with icmp-port-unreachable -A KUBE-SERVICES --reject-with icmp-port-unreachable -A KUBE-SERVICES -d 10.106.49.80/32 -p tcp -m comment --comment "default/nginx-37: has no endpoints" -m tcp --dport 80 -j REJECT --reject-with icmp-port-unreachable -A KUBE-SERVICES

Host Unreachable From 192.168.10.10 icmp_seq=2 Destination Host Unreachable From 192.168.10.10 icmp_seq=3 Destination Host Unreachable From 192.168.10.10 icmp_seq=4 Destination Host Unreachable --- Port Unreachable From 192.168.10.10 icmp_seq=2 Destination Port Unreachable From 192.168.10.10 icmp_seq=3 Destination Port Unreachable From 192.168.10.10 icmp_seq=4 Destination Port Unreachable --- anywhere reject-with icmp- port-unreachable REJECT all -- anywhere anywhere reject-with icmp- port-unreachable Chain OUTPUT (policy ACCEPT) 243

maintenances • trapper - trapper for active checks, traps, proxy communication • unreachable poller - poller for unreachable devices • vmware collector - VMware data collector responsible for data gathering functionality) • trapper - trapper for active checks, traps, proxy communication • unreachable poller - poller for unreachable devices • vmware collector - VMware data collector responsible for data gathering template names. 22 Upgrade notes for 4.0.13 Item update interval for unreachable hosts A bug related to item check time on unreachable hosts has been fixed. This bug was introduced in Zabbix version 3.4

maintenances • trapper - trapper for active checks, traps, proxy communication • unreachable poller - poller for unreachable devices • vmware collector - VMware data collector responsible for data gathering functionality) • trapper - trapper for active checks, traps, proxy communication • unreachable poller - poller for unreachable devices • vmware collector - VMware data collector responsible for data gathering Zabbix frontend behind proxy for details. Item update interval for unreachable hosts A bug related to item check time on unreachable hosts has been fixed. This bug was introduced in Zabbix version 3.4

maintenances • trapper - trapper for active checks, traps, proxy communication • unreachable poller - poller for unreachable devices • vmware collector - VMware data collector responsible for data gathering functionality) • trapper - trapper for active checks, traps, proxy communication • unreachable poller - poller for unreachable devices • vmware collector - VMware data collector responsible for data gathering ing worker, proxy poller, self- monitoring, snmp trapper, task manager, timer, trapper, unreachable poller, vmware collector Supported types of proxy processes: configuration syncer, data

zabbix[java„ping] will not become not supported if java gateway is misconfigured or java gateway is unreachable. Housekeeper changes • An event will now only be deleted by the housekeeper if it is not associated Simple change and Change per second. Attention: Too many data gathering processes (pollers, unreachable pollers, HTTP pollers, Java pollers, pingers, trappers, proxypollers) together with IPMI manager zabbix[java„ping] will not become not supported if java gateway is misconfigured or java gateway is unreachable Note: If you have some actions configured for internal events to monitor zabbix[java„ping], please

configuration parameter is 0, but regular, IPMI or Java pollers are started. Otherwise, hosts that become unreachable would never be checked again. ** Ability to include specific files from Include directory ** configuration parameter is 0, but regular, IPMI or Java pollers are started. Otherwise, hosts that become unreachable would never be checked again. Proxy now refuses to start with a server database. In some older proxy) trapper - trapper for active checks, traps, proxy communica- tion unreachable poller - poller for unreachable devices vmware collector - VMware data collector responsible for data

database removed from pollers Direct connections to database have been removed from pollers, unreachable pollers and JMX pollers on Zabbix server/proxy. Previously these connections were required for: internal items • Host availability updates in case of Zabbix agent, SNMP, JMX items. Pollers, unreachable pollers, JMX pollers and the IPMI manager would update host availability directly in the database maintenances • trapper - trapper for active checks, traps, proxy communication • unreachable poller - poller for unreachable devices • vmware collector - VMware data collector responsible for data gathering

hosts were deleted only from IPMI poller processes. Now the inactive hosts are deleted also from unreachable poller processes. 13 What’s new in Zabbix 3.0.8 1 Item count retrieval limit changes for queue zabbix[java„ping] will not become not supported if java gateway is misconfigured or java gateway is unreachable. 20 What’s new in Zabbix 3.0.15 Item changes • Previously in log[], logrt[] items in the skip zabbix[java„ping] will not become not supported if java gateway is misconfigured or java gateway is unreachable Note: If you have some actions configured for internal events to monitor zabbix[java„ping], please

trapper for active checks, traps, inter-node and -proxy communica- tion unreachable poller - poller for unreachable devices Note: You can also see these process types in a server log file (presumably 1.0beta8). Example 7 Server is unreachable {zabbix.zabbix.com:icmpping.count(30m,0)}>5 The expression is true if host ”zabbix.zabbix.com” is unreachable more than 5 times in the last 30 minutes the availability of one host depends on another. A server that is behind some router will become unreachable if the router goes down. With triggers configured for both, you might get notifications about