标签：network example discovery following formats
1.1创建自动发现规则
| Parameter | Description |
|---|---|
| Name | Unique name of the rule. For example, “Local network”. |
| Discovery by proxy | What performs discovery: no proxy - Zabbix server is doing discovery <proxy name> - this proxy performs discovery |
| IP range | The range of IP addresses for discovery. It may have the following formats: Single IP: 192.168.1.33 Range of IP addresses: 192.168.1.1-255 IP mask: 192.168.4.0/24 supported IP masks: /16 - /30 for IPv4 addresses /112 - /128 for IPv6 addresses List: 192.168.1.1-255,192.168.2.1-100,192.168.2.200,192.168.4.0/24 Note: Each IP address should be included only once; having multiple rules for a single IP address can have unexpected behavior such as having deadlocks and/or duplicate hosts in the database. The same could happen if two hosts having the sameDNSname are included in separate discovery rules. |
| Delay (in sec) | This parameter defines how often Zabbix will execute the rule. Delay is measured after the execution of previous discovery instance ends so there is no overlap. |
| Checks | Zabbix will use this list of checks for discovery. Supported checks: SSH, LDAP, SMTP,FTP, HTTP, HTTPS, POP, NNTP, IMAP, TCP, Telnet, Zabbix agent, SNMPv1 agent, SNMPv2 agent, SNMPv3 agent, ICMP ping. A protocol-based discovery uses the net.tcp.service[] functionality to test each host, except for SNMP which queries an SNMP OID. Zabbix agent is tested by querying an item. Please see agent items for more details. The ‘Ports‘ parameter may be one of following: Single port: 22 Range of ports: 22-45 List: 22-45,55,60-70 |
| Device uniqueness criteria | Uniqueness criteria may be: IP address - no processing of multiple single-IP devices. If a device with the same IP already exists it will be considered already discovered and a new host will not be added. Type of discovery check - either SNMP or Zabbix agent check. |
| Enabled | With the check-box marked the rule is active and will be executed by Zabbix server. If unmarked, the rule is not active. It won‘t be executed. |
1.2创建自动添加到相应模板规则
1.3配置创建的discover_action
1.4 -->Conditions
1.5 -->Operations
本文出自 “Linux革命” 博客，请务必保留此出处http://kaibinyuan.blog.51cto.com/7304008/1604748
标签：network example discovery following formats
原文地址：http://kaibinyuan.blog.51cto.com/7304008/1604748
