Zabbix Documentation 4.4

3.04.04.4 (current)| In development:5.0 (devel)| Unsupported:1.82.02.22.43.23.44.2Guidelines

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 [2019/03/11 12:10]
martins-v some rewording
manual:discovery:network_discovery [2019/05/15 06:56] (current)
martins-v 'host discovered' description changed - for new hosts
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 80: Line 82:
   * You may discover multiple SNMP network devices using an SNMP 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 automatically,​ based 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 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 name) is 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.