manual:discovery:network_discovery

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revision Both sides next revision
manual:discovery:network_discovery [2015/05/11 07:48]
martins-v consistent tenses
manual:discovery:network_discovery [2019/04/11 12:53]
martins-v more precise wording
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 59: Line 59:
  
 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. 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.
 +
 +<​note>​Linking a discovered host to templates will fail collectively if any of the linkable templates has a unique entity (e.g. item key) that is the same as a unique entity (e.g. item key) already existing on the host or on another of the linkable templates.</​note>​
  
 == Host creation == == Host creation ==
Line 69: Line 71:
   * link template to a host   * link template to a host
  
-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 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 ​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
 + 
 +Created hosts are added to the //​Discovered hosts// group (by default, configurable in //​Administration//​ -> //General// -> //​[[:​manual/​web_interface/​frontend_sections/​administration/​general#​other_parameters|Other]]//​). If you wish hosts to be added to another group, add 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 ==