Hi to anyone,
I searched for a while trying to find out a documents or infos about a similar context but nothing found.
I have some goal I think I can satisfy with a Zabbix infrastructure.
And would be a pleasure get some help from your experience to guide along the architecture design step.
This is an ISP context in which a large number of devices may be discovered and registered into the inventory.
#GOALS:
.1 discover by configured subnet linked to their own proxy. (add new up, (remove old down in case of dhcp subnet))
.2 do a minimal rules (eg: ping + snmp || + telnet/ssh) and minimal actions (add to group, template ping)
.3 get a strategic info only (model, sn, vers, etc)
.4 send a full discover (for each subnet) once a day (or more if too hard in 24h)
#CLIENTS:
From smb network devices to enterprise network devices
#ENVIRONMENT:
Large amount of network subnets segregated by area (as a standard ISP), so at least 1 proxy per area (I think 5 instances at the moment).
Zabbix server and proxies are based on OL7.7 - VmWare 6.7
Available RAM: 400GB (max preferred)
Storage type: SSD
vCpu = 24 (max preferred)
#QUESTIONS:
I'm not expert enough to understand how many proxies may I need to accomplish that GOALS in the right way, especially by figuring how many devices a proxy can handle in that way.
And I don't know how much powerful the central instance may be in such case.
How many proxies may I need? (es: X per proxy or similar approaches)
How many resources per proxy? (es: 2vcpu, 24G ram per 1000 devices or similar approaches)
There are specific tunings (by OS/kernel and zabbix config and proxy db) to get the best performances on discovery process and ping process? (I want focus the best on that)
----------
I'm here for any kind of additional info or questions!
Thank you in advance
Omar C.
----------
I searched for a while trying to find out a documents or infos about a similar context but nothing found.
I have some goal I think I can satisfy with a Zabbix infrastructure.
And would be a pleasure get some help from your experience to guide along the architecture design step.
This is an ISP context in which a large number of devices may be discovered and registered into the inventory.
#GOALS:
.1 discover by configured subnet linked to their own proxy. (add new up, (remove old down in case of dhcp subnet))
.2 do a minimal rules (eg: ping + snmp || + telnet/ssh) and minimal actions (add to group, template ping)
.3 get a strategic info only (model, sn, vers, etc)
.4 send a full discover (for each subnet) once a day (or more if too hard in 24h)
#CLIENTS:
From smb network devices to enterprise network devices
#ENVIRONMENT:
Large amount of network subnets segregated by area (as a standard ISP), so at least 1 proxy per area (I think 5 instances at the moment).
Zabbix server and proxies are based on OL7.7 - VmWare 6.7
Available RAM: 400GB (max preferred)
Storage type: SSD
vCpu = 24 (max preferred)
#QUESTIONS:
I'm not expert enough to understand how many proxies may I need to accomplish that GOALS in the right way, especially by figuring how many devices a proxy can handle in that way.
And I don't know how much powerful the central instance may be in such case.
How many proxies may I need? (es: X per proxy or similar approaches)
How many resources per proxy? (es: 2vcpu, 24G ram per 1000 devices or similar approaches)
There are specific tunings (by OS/kernel and zabbix config and proxy db) to get the best performances on discovery process and ping process? (I want focus the best on that)
----------
I'm here for any kind of additional info or questions!
Thank you in advance
Omar C.
----------
Comment