Hi all
We regularly deploy devices that have multiple snmp interfaces each with a unique IP address.
The Lan port which is reachable over the vpn tunnel.
The Wan port which is normally up and reachable.
The Cell modem which is usually on standby.
The Lan IP should be reachable over the vpn, as the vpn should work over either the cell or the wan.
So we usually ping the lan ip regularly and poll snmp items, one of which tells us if that wan port is disconnected.
But we would also like to be able to ping the wan port as it will have different statistics (latency) than the lan over the vpn will.
There are also times where the device will fail over to the cell due to the Wan port being down (or otherwise unusable),
but due to poor cell service, the vpn is not able to establish. In that event we would like to be able to ping the cell IP (assuming it has a reachable IP).
To this end, I would love to see:
1. A label box for each snmp interface so we can mark it as either lan, wan, cell etc.
2. A way to prioritize the interfaces so that the order they are auto-discovers doesn't matter.
3. A way to tell an item which interface to act on: ie item one pings the Lan, item 2 pings the Wan, item 3 pings the Cell.
4. Conditional items: ie: only activate item 3 if a trigger fires based on item fails: ie: cannot ping wan.
I know this is asking a lot. I just want to get the discussion rolling so others can contribute their thoughts.
Thanks for the great work!
We regularly deploy devices that have multiple snmp interfaces each with a unique IP address.
The Lan port which is reachable over the vpn tunnel.
The Wan port which is normally up and reachable.
The Cell modem which is usually on standby.
The Lan IP should be reachable over the vpn, as the vpn should work over either the cell or the wan.
So we usually ping the lan ip regularly and poll snmp items, one of which tells us if that wan port is disconnected.
But we would also like to be able to ping the wan port as it will have different statistics (latency) than the lan over the vpn will.
There are also times where the device will fail over to the cell due to the Wan port being down (or otherwise unusable),
but due to poor cell service, the vpn is not able to establish. In that event we would like to be able to ping the cell IP (assuming it has a reachable IP).
To this end, I would love to see:
1. A label box for each snmp interface so we can mark it as either lan, wan, cell etc.
2. A way to prioritize the interfaces so that the order they are auto-discovers doesn't matter.
3. A way to tell an item which interface to act on: ie item one pings the Lan, item 2 pings the Wan, item 3 pings the Cell.
4. Conditional items: ie: only activate item 3 if a trigger fires based on item fails: ie: cannot ping wan.
I know this is asking a lot. I just want to get the discussion rolling so others can contribute their thoughts.
Thanks for the great work!