Actions for Discovery

[jurrien]

I'm new to Zabbix and I have a strange situation.

I tested a few servers to be discovered. This worked just fine. The actions defined added the hosts to the template and host group.

Next step was to add a larger IP range. The strange thing is that Zabbix find that there is a Zabbix client running on the machine but the servers doesn't get attached to the hostgroup of template.

I double checked everything and also some other topics on this forum. No solution found.

What I see if I go to Monitoring - Discovery is that Zabbix found the hostnames of servers of the first test but not from the second batch of servers. Strange. I can resolve the IP's on the command line of the server. I also added a extra action when a server is discovered to send the admin a e-mail but nothing. Nothing in the logs. Added more discovery services. No luck.

Some specs:
Running on RedHat Server 5.5
SELinux is off (Found some issue's with that if SELinux is on. Will look at that later)
Zabbix version was 1.8.3. Updated it today to 1.8.4 to see if problem resolved. No luck.

I'm dazzled and confused but trying to continue. Don't know where to look anymore. Does anyone have an idea?

[untergeek]

In your zabbix_server.conf, how many are defined in StartDiscoverers=?

I've also noted that sometimes Discovery can get stuck when the subnet has problem IPs (firewalled, black-hole, etc). I've found that having more Discoverers (we have 40) can help with some of these problems.

[jurrien]

At the moment the StartDiscoverers is set at 25.

I have two /24 networks defined as one discover rule. Before that I had them split in two.

The strange thing is that he finds the ip's of the server but he doesn't put the hostname in the colum "monitored hosts".

[jurrien]

I added a picture. Here you can see that in the past host where added under monitored hosts. But the new range of hosts not.

[dale]

discovery actions do not like CIDR notation

I'm using Zabbix 1.8.8, and I found that Discovery Rules are perfectly happy to use CIDR notated IP ranges such as 10.1.1.0/24 or 172.32.0.128/25.

Unfortunately it seems that Discovery Actions silently ignore conditions such as "IP = 172.32.0.128/25". You must instead use "IP = 172.32.0.128-254" for example.

I greatly prefer the compat CIDR form, so I hope that will be fixed in a later release.