Zabbix Documentation 3.4

2.23.04.04.2 (current)In development:4.4 (devel)Unsupported:1.82.02.43.23.4

User Tools

Site Tools


manual:discovery:network_discovery

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
manual:discovery:network_discovery [2014/09/25 14:42]
sasha Page moved from 2.4:manual:discovery:network_discovery to manual:discovery:network_discovery
manual:discovery:network_discovery [2019/05/15 06:57] (current)
martins-v 'host discovered' description changed - for new hosts
Line 15: Line 15:
   * IP ranges   * IP ranges
   * Availability of external services (FTP, SSH, WEB, POP3, IMAP, TCP, etc)   * Availability of external services (FTP, SSH, WEB, POP3, IMAP, TCP, etc)
-  * Information received from Zabbix agent+  * Information received from Zabbix agent (only unencrypted mode is supported)
   * Information received from SNMP agent   * Information received from SNMP agent
  
Line 25: Line 25:
 === Discovery === === Discovery ===
  
-Zabbix periodically scans the IP ranges defined in [[:2.4/manual/discovery/network_discovery/rule|network discovery rules]]. The frequency of the check is configurable for each rule individually.+Zabbix periodically scans the IP ranges defined in [[manual:discovery:network_discovery:rule|network discovery rules]]. The frequency of the check is configurable for each rule individually
 + 
 +Note that one discovery rule will always be processed by a single discoverer process. The IP range will not be split between multiple 
 +discoverer processes.
  
 Each rule has a set of service checks defined to be performed for the IP range. ​ Each rule has a set of service checks defined to be performed for the IP range. ​
Line 38: Line 41:
 |//Service Lost// ​ |The service is '​down'​ after it was '​up'​. ​ | |//Service Lost// ​ |The service is '​down'​ after it was '​up'​. ​ |
 |//Service Down// ​ |The service is '​down',​ consecutively. ​ | |//Service Down// ​ |The service is '​down',​ consecutively. ​ |
-|//Host Discovered// ​ |At least one service of a host is '​up'​ after all services of that host were '​down'​. ​ |+|//Host Discovered// ​ |At least one service of a host is '​up'​ after all services of that host were '​down' ​or a service is discovered which belongs to a not registered host.  |
 |//Host Up//  |At least one service of a host is '​up',​ consecutively. ​ | |//Host Up//  |At least one service of a host is '​up',​ consecutively. ​ |
 |//Host Lost// ​ |All services of a host are '​down'​ after at least one was '​up'​. ​ | |//Host Lost// ​ |All services of a host are '​down'​ after at least one was '​up'​. ​ |
Line 45: Line 48:
 === Actions === === Actions ===
  
-Discovery events can be the basis of relevant [[:2.4/manual/config/notifications/action|actions]],​ such as:+Discovery events can be the basis of relevant [[manual:config:notifications:action|actions]],​ such as:
  
   * Sending notifications   * Sending notifications
Line 55: Line 58:
   * Executing remote scripts   * Executing remote scripts
  
-These actions can be configured with respect to the device type, IP, status, uptime/​downtime,​ etc. For full details on configuring actions for network-discovery based events, see action [[:2.4/manual/config/notifications/action/operation|operation]] and [[:2.4/manual/config/notifications/action/conditions|conditions]] pages.+These actions can be configured with respect to the device type, IP, status, uptime/​downtime,​ etc. For full details on configuring actions for network-discovery based events, see action [[manual:config:notifications:action:operation|operation]] and [[manual:config:notifications:action:conditions|conditions]] pages.
  
 == Host creation == == Host creation ==
  
-If the //Add host// operation is chosen, a host will be addedIf any other operation that would result in an action on that host (like linking template or adding to a group) ​is chosena host will be added even if the //Add host// operation is missing.+A host is added if the //Add host// operation is selectedhost is also added, even if the //Add host// operation is missing, if you select operations resulting in actions on a host. Such operations are: 
 + 
 +  * enable host 
 +  * disable host 
 +  * add host to a host group 
 +  * link template to a host 
 + 
 +When adding hosts, a host name is the result of reverse DNS lookup or IP address if reverse lookup fails. Lookup is performed from the Zabbix server or Zabbix proxy, depending on which is doing the discovery. If lookup fails on the proxy, it is not retried on the server. If the host with such a name already exists, the next host would get **_2** appended to the name, then **_3** and so on.
  
-When adding ​hosts, a host name is the result of reverse lookup or IP address if reverse lookup fails. Lookup is performed from the Zabbix server or Zabbix proxydepending on which is doing the discovery. If lookup fails on the proxyit is not retried on the server. If the host with such name already exists, the next host would get **_2** appended ​to the name, then **_3** and so on.+Created ​hosts are added to the //​Discovered hosts// group (by defaultconfigurable in //​Administration//​ -> //General// -> //​[[:​manual/​web_interface/​frontend_sections/​administration/​general#​other_parameters|Other]]//​). If you wish hosts to be added to another groupadd a //Remove from host groups// operation (specifying "​Discovered hosts"​) and also add an //Add to host groups// operation (specifying another host group), because ​a host must belong ​to a host group.
  
 +If a host already exists with the discovered IP address, a new host is not created. However, if the discovery action contains operations (link template, add to host group, etc), they are performed on the existing host.
 == Host removal == == Host removal ==
  
-Starting with Zabbix 2.4.0, hosts created ​by a network discovery rule are deleted ​automatically if a discovered entity is not in the rule's IP range anymore. Hosts are deleted ​immediately.+Hosts discovered ​by a network discovery rule are removed ​automatically ​from //​Monitoring//​ -> //​Discovery// ​if a discovered entity is not in the rule's IP range any more. Hosts are removed ​immediately.
 == Interface creation when adding hosts == == Interface creation when adding hosts ==