Yes, I had tried both of those, the HTTP advanced is not an option, but the SNMP is but doesn't work unless the link between the firewall and the Comcast router is down.
I currently have a snmptrafficsensor on the eth1 port of the remote firewall which the Comcast internet runs through for our public LAN. When the Comcast service is lost the traffic flattens out as expected. While that is a good indication there is an issue with our public internet it does not send me an alert.
I also have a ping monitor on the Comcast router. However, this will only tell me if the link between the firewall and the Comcast router is down, while helpful, it is very rare and does not alert me in the event Comcast Internet is down.
Ultimately, what I want is to trap the state received from the firewall (Checking). When the Comcast service goes down the firewall will attempt to re-establish a connection and it's state changes from 'UP' to "CHECKING' when this occurs.
Note: Our UTM Firewall does support SNMP, but the Comcast router does not.
Add comment