Hi all.
I'm working on a project migrating Zabbix Server from 2.0.8 to 3.0.4 in a network that has a number of geographically dispersed pfSense Servers running a Zabbix Proxy on each to monitor the network at that location.
The issue that I face is that Zabbix Proxies will only communicate with a Zabbix Server of the same version. Most of the pfSense Servers are running Zabbix Proxy 2.0.8 and so will not communicate with the new Server. While it is possible to upgrade pfSense to include a 3.0.4 Zabbix Proxy, I have seen issues with the pfSense upgrade itself that have required hands-on attendance to fix. A few of the pfSense servers are 200-300 miles away from my location, so its not a simple matter to just pop out in the car and fix them. I would prefer to do these upgrades over time in a more managed way, sending out an engineer to do it as part of other work that may need doing at the site. But this would make the full process take some time and leaving these sites unmonitored is not really an option.
I've looked at using NAT on the pfSever to make each device behind the pfSense Servers visible via Port Forwarding but this is very messy for all sorts of reasons. I've also looked at running VPNs into each of the pfSense Servers, which is less messy but still not ideal.
Has anyone come across a good, temporary solution for this?
Is there anything one can place between the Zabbix Server and the pfSense network to handle the differences?
Thanks, Richard
I'm working on a project migrating Zabbix Server from 2.0.8 to 3.0.4 in a network that has a number of geographically dispersed pfSense Servers running a Zabbix Proxy on each to monitor the network at that location.
The issue that I face is that Zabbix Proxies will only communicate with a Zabbix Server of the same version. Most of the pfSense Servers are running Zabbix Proxy 2.0.8 and so will not communicate with the new Server. While it is possible to upgrade pfSense to include a 3.0.4 Zabbix Proxy, I have seen issues with the pfSense upgrade itself that have required hands-on attendance to fix. A few of the pfSense servers are 200-300 miles away from my location, so its not a simple matter to just pop out in the car and fix them. I would prefer to do these upgrades over time in a more managed way, sending out an engineer to do it as part of other work that may need doing at the site. But this would make the full process take some time and leaving these sites unmonitored is not really an option.
I've looked at using NAT on the pfSever to make each device behind the pfSense Servers visible via Port Forwarding but this is very messy for all sorts of reasons. I've also looked at running VPNs into each of the pfSense Servers, which is less messy but still not ideal.
Has anyone come across a good, temporary solution for this?
Is there anything one can place between the Zabbix Server and the pfSense network to handle the differences?
Thanks, Richard
Comment