Alerting when "dialup" host from clear to green
I have this host:
172.16.10.49 foo.bar.com # testip dialup
Which is only used when a device fails to find a DHCP server. Is there any way to be alerted when this goes from clear to green? COLOR does not accept green and RECOVERED it seems is only from red to green (we all know about the yellow to green "bug").
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
“Success is not final, failure is not fatal: it is the courage to continue that counts.” --- Winston Churchill
On Sun, June 20, 2010 04:55, Josh Luthman wrote:
I have this host:
172.16.10.49 foo.bar.com # testip dialup
Which is only used when a device fails to find a DHCP server. Is there any way to be alerted when this goes from clear to green? COLOR does not accept green and RECOVERED it seems is only from red to green (we all know about the yellow to green "bug").
You're up at 5am Sunday thinking about this? Eek.
Don't see how to do it directly, but what about: 172.17.16.15 nodhcp.foo.bar.com # testip depends=(conn:foo.bar.com)
That should go red whenever foo.bar.com goes green. Assuming you don't actually have a pingable host on 172.17.16.15, which is rather obscure RFC1918 space.
Vegas never sleeps and they seem to be doing pretty good =)
I now have this:
172.16.10.49 airosfallback.ubnt.com # testip dialup 172.17.16.15 nodhcp.ubnt.com # testip depends=(conn:airosfallback.ubnt.com)
The second host (nodhcp) is showing up red. The syntax looks correct to me...from the docs...
depends=(testA:host1/test1,host2/test2),(testB:host3/test3),[...]
Do we know if the clear condition should act as we expect in this case?
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
“Success is not final, failure is not fatal: it is the courage to continue that counts.” --- Winston Churchill
On Sun, Jun 20, 2010 at 6:38 AM, Xymon User in Richmond <hobbit at epperson.homelinux.net> wrote:
On Sun, June 20, 2010 04:55, Josh Luthman wrote:
I have this host:
172.16.10.49 foo.bar.com # testip dialup
Which is only used when a device fails to find a DHCP server. Is there any way to be alerted when this goes from clear to green? COLOR does not accept green and RECOVERED it seems is only from red to green (we all know about the yellow to green "bug").
You're up at 5am Sunday thinking about this? Eek.
Don't see how to do it directly, but what about: 172.17.16.15 nodhcp.foo.bar.com # testip depends=(conn:foo.bar.com)
That should go red whenever foo.bar.com goes green. Assuming you don't actually have a pingable host on 172.17.16.15, which is rather obscure RFC1918 space.
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
On Sun, June 20, 2010 17:28, Josh Luthman wrote:
Vegas never sleeps and they seem to be doing pretty good =)
I now have this:
172.16.10.49 airosfallback.ubnt.com # testip dialup 172.17.16.15 nodhcp.ubnt.com # testip depends=(conn:airosfallback.ubnt.com)
The second host (nodhcp) is showing up red. The syntax looks correct to me...from the docs...
depends=(testA:host1/test1,host2/test2),(testB:host3/test3),[...]
Do we know if the clear condition should act as we expect in this case?
I sometimes sleep for a couple of days. ;)
No, I don't know, and it appears that it doesn't. In which case the manpage appears wrong, because it says:
"depends=(testA:host1/test1,host2/test2)
When deciding the color to report for testA, if either host1/test1 failed or host2/test2 failed, if testA has failed also then the color of testA will be "clear" instead of red or yellow."
Apparently, the case is that if host1/test1 or host2/test2 are red, then the color of testA will be clear.
Was a great idea, I'll just move it up on the page and glance at it every once in a while.
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
“Success is not final, failure is not fatal: it is the courage to continue that counts.” --- Winston Churchill
On Tue, Jun 22, 2010 at 3:49 PM, Xymon User in Richmond <hobbit at epperson.homelinux.net> wrote:
On Sun, June 20, 2010 17:28, Josh Luthman wrote:
Vegas never sleeps and they seem to be doing pretty good =)
I now have this:
172.16.10.49 airosfallback.ubnt.com # testip dialup 172.17.16.15 nodhcp.ubnt.com # testip depends=(conn:airosfallback.ubnt.com)
The second host (nodhcp) is showing up red. The syntax looks correct to me...from the docs...
depends=(testA:host1/test1,host2/test2),(testB:host3/test3),[...]
Do we know if the clear condition should act as we expect in this case?
I sometimes sleep for a couple of days. ;)
No, I don't know, and it appears that it doesn't. In which case the manpage appears wrong, because it says:
"depends=(testA:host1/test1,host2/test2)
When deciding the color to report for testA, if either host1/test1 failed or host2/test2 failed, if testA has failed also then the color of testA will be "clear" instead of red or yellow."
Apparently, the case is that if host1/test1 or host2/test2 are red, then the color of testA will be clear.
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
participants (2)
-
hobbit＠epperson.homelinux.net
-
josh＠imaginenetworksllc.com