Would it be possible to get a list of supported CIDR ranges (such as /24, /16, etc) for the Zabbix discovery function?
Does anyone know? Can this be added to the wiki, or something?
The wiki examples /24 in the discovery examples, which is great for single subnet, but for larger ranges, such as a Class B, it's proving difficult to work out what is actually supported, versus what the web interface will allow.
Is a /16 permitted? how about something more focused like a /18 or /22. Who knows.
Further, using trial and error is proving frustrating as the discovery process seems to ignore any changes to rules and ploughs on regardless; dropping a set of rules and recreating leads to variable results as to when a discovery might occur (neither the new timing, or old seems to be honoured); if at all.
So far I have consumed several hours making a small number of changes and then watching the discovery log; obviously I can't tell if a range is or isn't working if discovery doesn't honour changes to rules.
I have gathered that a discovery Action requires a range to be presented, eg something like 10.1.1.1-254. That's great, but means a lot of rules to cover a class C, or a set of ranges within a class C, CIDR would be useful here.
Really, if I can find a list of supported suffixes, I'll be a happy chap.
Does anyone know? Can this be added to the wiki, or something?
The wiki examples /24 in the discovery examples, which is great for single subnet, but for larger ranges, such as a Class B, it's proving difficult to work out what is actually supported, versus what the web interface will allow.
Is a /16 permitted? how about something more focused like a /18 or /22. Who knows.
Further, using trial and error is proving frustrating as the discovery process seems to ignore any changes to rules and ploughs on regardless; dropping a set of rules and recreating leads to variable results as to when a discovery might occur (neither the new timing, or old seems to be honoured); if at all.
So far I have consumed several hours making a small number of changes and then watching the discovery log; obviously I can't tell if a range is or isn't working if discovery doesn't honour changes to rules.
I have gathered that a discovery Action requires a range to be presented, eg something like 10.1.1.1-254. That's great, but means a lot of rules to cover a class C, or a set of ranges within a class C, CIDR would be useful here.
Really, if I can find a list of supported suffixes, I'll be a happy chap.