Select Page

RUTX11 Auto Reboot

Summary #

Various automatic device reboot scenarios can be configured in the Auto Reboot section. Automatic reboots can be used as a prophylactic or precautionary measure that ensures the device will self-correct some unexpected issues, especially related to connection downtime. This chapter is an overview of the Auto Reboot section of RUTX11 devices.

If you’re having trouble finding this page or some of the parameters described here on your device’s WebUI, you should turn on “Advanced WebUI” mode. You can do that by clicking the “Basic” button under “Mode”, which is located at the top-right corner of the WebUI.

Networking rutx manual webui basic advanced mode v1.gif

Ping Reboot #

The Ping Reboot function periodically sends ICMP or Wget requests to a specified IP address or host and waits for a response. If no response is received, the device will attempt the same action a defined number of times at a defined frequency. If there is still no response, the device will execute the specified action (reboot, by default).

The Ping Reboot section contains one preconfigured rule by default:

Networking rutos manual auto reboot ping reboot v1.png

To enable the default rule, use the off/on slider next to it. You can add more rules with the ‘Add’ button or delete them using the “Delete” button. If you wish to customize a rule, click the button that looks like a pencil next to it. Refer to the figure and table below for information Ping Reboot configuration.

Networking rutos manual auto reboot ping reboot configuration v1.png
FieldValueDescription
Enableoff | on; default: offTurns the rule on or off.
TypePing | Wget; default: PingMethod used for health checking.Ping – sends ICMP requests to the specified host.Wget – retrieves the contents of the specified web server.
Action if no echo is receivedDevice reboot |Modem reboot | None |; default: Device rebootAction that will be executed if there is no response after the specified amount of retries.
Interval between pings5 mins | 15 mins | 30 mins | 1 hour | 2 hours; default: 5 minsThe frequency at which ping/Wget requests are sent to the specified host.
Ping timeout (sec)integer [1..9999]; default: 5Maximum response time. If no echo is received after the amount of time specified in this field has passed, the ping/wget request is considered to have failed.
Packet sizeinteger [0..1000]; default: 56ICMP packet size in bytes.
Try countinteger [1..9999]; default: 2Indicates how many additional times the device will try sending requests if the initial one fails.
Hosthost | ip; default: 8.8.8.8Hostname or IP address to which the Ping/Wget requests will be sent.

Periodic Reboot #

Periodic Reboot is a function that reboots the device at a specified time interval regardless of other circumstances. It can be used as a prophylactic measure, for example, to reboot the device once at the end of every day.

You can add more rules with the ‘Add’ button or delete them using the “Delete” button. If you wish to customize a rule, click the button that looks like a pencil next to it. Refer to the figure and table below for information Ping Reboot configuration.

Networking rutos manual auto reboot periodic reboot v1.png

The figure below is an example of the Periodic Reboot configuration page and the table below provides information on the fields contained in that page:

Networking rutos manual auto reboot periodic reboot configuration v1.png
FieldValueDescription
Enableoff | on; default: offTurns the rule on or off.
ActionDevice reboot |Modem reboot ; default: Device rebootAction that will be executed at the specified time.
Week daysMonday| Tuesday| Wednesday| Thursday | Friday | Saturday | Sunday; default: MondayWeek day/s when actions will be executed.
Timetime; default: 12:00Here you can specify the hour/minute for action to occur.

Submit a Comment

Your email address will not be published. Required fields are marked *