On Wed, 15 Nov 2017 16:25:57 +0900, ATANARJUAT
wrote:

On Wed, 15 Nov 2017 07:22:29 -0000 (UTC), Blake Snyder wrote
in response to Blake Snyder

Klugey approach?

Set a WatchDog Timer reboot.

Specify an IP that won't respond to pings, set up the WatchDog timer to
ping it every 24*60*60 seconds, with a fail count of 7. (or suitable
numbers that the GUI will accept).

You could even have it ping a machine on your network somewhere that you
could take off-line when you wanted to reboot everything.

Or query the SNMP "time since restart" and force a rest when the
monitored device has been restarted?

On a cisco router (and lots of other infrastructure tin) you can set
"reboot after xxx minutes"
- very useful when reconfiguring remotely something that may affect
the in band link the control traffic arrives on
- as long as you remember to cancel it when you are done......

however a timer with a real power cycle is going to catch "stuff" that
a reset may not - some hardware lock ups have been known to need a
physical power cycle to recover.....

--
Stephen