Hi all,
been fiddling around with zabbix for a while and run into something i have no idea on how to accompish.
so we have our zabbix located in our datacentre and about 30 remote sites connected to it.
To monitor amongst other thing the connection state of the MPLS line, we monitor the interface states of the mpls router and firewall interface 1 , connected to the mpls router
To have a back up for a line fail we use a IPSEC tunnel through the internet, which we can monitor it's state. let's call it firewall interface 2
now here comes my problem: we have a "high" trigger state for both interfaces, because if one fails, we have a good back-up in place.
now if both fail, we would like an disaster sms notification, however how would i accomplish this ?
we run zabbix 1.8.4 , and i know zabbix 2.0 does have multiple interface monitoring, but since that is a very early beat, i would want my production running on that.
Here's a picture of the setup.

one more thing to mention, is that we do not have access to the device behind the third interface, so we cannot use that as a monitorable ref. point
been fiddling around with zabbix for a while and run into something i have no idea on how to accompish.
so we have our zabbix located in our datacentre and about 30 remote sites connected to it.
To monitor amongst other thing the connection state of the MPLS line, we monitor the interface states of the mpls router and firewall interface 1 , connected to the mpls router
To have a back up for a line fail we use a IPSEC tunnel through the internet, which we can monitor it's state. let's call it firewall interface 2
now here comes my problem: we have a "high" trigger state for both interfaces, because if one fails, we have a good back-up in place.
now if both fail, we would like an disaster sms notification, however how would i accomplish this ?
we run zabbix 1.8.4 , and i know zabbix 2.0 does have multiple interface monitoring, but since that is a very early beat, i would want my production running on that.
Here's a picture of the setup.

one more thing to mention, is that we do not have access to the device behind the third interface, so we cannot use that as a monitorable ref. point

Comment