Zabbix Documentation 4.2

3.04.04.24.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.4Guidelines

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

Both sides previous revision Previous revision
Next revision
Previous revision
manual:discovery:network_discovery [2018/10/01 09:42]
127.0.0.1 external edit
manual:discovery:network_discovery [2019/05/10 11:34] (current)
andris [Discovery] "Host Discovered" event - added few words about initial discovery
Line 41: 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 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 68: Line 70:
   * add host to a host group   * add host to a host group
   * link template to a host   * link template to a host
 +
 +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.
 +
 +== Host naming ==
  
 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 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 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.+It is also possible ​to override DNS/IP lookup and instead use an item value for host namefor example: 
 + 
 +  * You may discover multiple servers with Zabbix agent running using a Zabbix agent item for discovery and assign proper names to them automatically,​ based on the string value returned by this item 
 +  * You may discover multiple SNMP network devices using an SNMP agent item for discovery and assign proper names to them automaticallybased on the string value returned by this item  
 + 
 +If the host name has been set using an item value, it is not updated during the following discovery checks. If it is not possible ​to set host name using an item value, default value (DNS nameis used.
  
 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. 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 ==
  
-Since 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 any more. 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 ==
  
Line 87: Line 98:
   * if 3 separate hosts were initially created, having been discovered by the "​IP"​ uniqueness criteria, and then the discovery rule is modified so that hosts A, B and C have identical uniqueness criteria result, B and C are created as additional interfaces for A, the first host. The individual hosts B and C remain. In //​Monitoring -> Discovery// the added interfaces will be displayed in the "​Discovered device"​ column, in black font and indented, but the "​Monitored host" column will only display A, the first created host. "​Uptime/​Downtime"​ is not measured for IPs that are considered to be additional interfaces. ​   * if 3 separate hosts were initially created, having been discovered by the "​IP"​ uniqueness criteria, and then the discovery rule is modified so that hosts A, B and C have identical uniqueness criteria result, B and C are created as additional interfaces for A, the first host. The individual hosts B and C remain. In //​Monitoring -> Discovery// the added interfaces will be displayed in the "​Discovered device"​ column, in black font and indented, but the "​Monitored host" column will only display A, the first created host. "​Uptime/​Downtime"​ is not measured for IPs that are considered to be additional interfaces. ​
  
 +=== Changing proxy setting ===
 +
 +The hosts discovered by different proxies are always treated as different hosts. While this allows to perform discovery on matching IP ranges used by different subnets, changing proxy for an already monitored subnet is complicated because the proxy changes must be also applied to all discovered hosts. ​
 +
 +For example the steps to replace proxy in a discovery rule:
 +  - disable discovery rule
 +  - sync proxy configuration
 +  - replace the proxy in the discovery rule
 +  - replace the proxy for all hosts discovered by this rule
 +  - enable discovery rule