Template:Networking rut manual auto reboot: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Template: | {{Template: Networking_rutos_manual_fw_disclosure | ||
| fw_version = {{#switch: {{{series}}} | | fw_version = {{#switch: {{{series}}} | ||
| RUT2XX = {{{series}}}_R_00.01.13 | | RUT2XX = {{{series}}}_R_00.01.13 | ||
| Line 8: | Line 8: | ||
==Summary== | ==Summary== | ||
Various automatic router reboot scenarios can be configured in the <b>Auto Reboot</b> | Various automatic router reboot scenarios can be configured in the <b>Auto Reboot</b> page. 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 | This chapter of the user manual provides an overview of the Auto Reboot page for {{{name}}} devices. | ||
==Ping Reboot== | ==Ping Reboot== | ||
Revision as of 16:14, 19 November 2020
Template:Networking rutos manual fw disclosure
Summary
Various automatic router reboot scenarios can be configured in the Auto Reboot page. 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 of the user manual provides an overview of the Auto Reboot page for {{{name}}} devices.
Ping Reboot
The Ping Reboot function periodically sends Ping commands to a specified IP address and wait for received responses. If no response is received, the device will send Ping commands a defined number of times at a defined frequency. If no response is received after the defined number of unsuccessful retries, the device will commit the specified action (reboot, by default).
The Ping Reboot section contains one pre-configured rule by default. The figure below is an example of that rule and the table below provides information on the fields that make up that rule:
| Field | Value | Description |
|---|---|---|
| Enable | yes | no; Default: no | Turns the rule ON or OFF |
| Action | Reboot | Modem restart | Restart mobile connection | (Re)register | none; Default: Reboot | The action that will be taken if no ICMP echo is received |
| Interval (min) | 5 mins | 15 mins | 30 mins | 1 hour | 2 hours; Default: 5 mins | Interval at which ping requests are sent to the specified host |
| Ping timeout (sec) | integer [1..9999]; Default: 5 | Maximum response time (in seconds). If no echo is received after the amount of time specified in this field, the ping request is considered to have failed |
| Packet size | integer [0..1000]; Default: 56 | Ping packet size in bytes |
| Retry count | integer [1..9999]; Default: 2 | Indicates how many additional times the device will try sending ping requests if the initial one fails |
| Host to ping | host | ip; Default: 8.8.8.8 | Indicates the host to which ping requests will be sent |
| Edit | - (interactive button) | Redirects the user to the rule's configuration window |
| Delete | - (interactive button) | Removes the rule from the configuration |
Ping Reboot Settings
If you click the "Edit" button located to a ping reboot rule, you will be redirected to that rule's configuration window. The figure below is an example of that window and the table below provides information on the fields contained in that window:
| Field | Value | Description |
|---|---|---|
| Enable | yes | no; Default: no | Turns the rule ON or OFF |
| No action on data limit | yes | no; Default: no | If enabled, stops taking actions after data limit is reached |
| Action if no echo is received | Reboot | Modem restart | Restart mobile connection | (Re)register | none; Default: Reboot | The action that will be taken if no ICMP echo is received |
| Interval between pings | 5 mins | 15 mins | 30 mins | 1 hour | 2 hours; Default: 5 mins | Interval at which ping requests are sent to the specified host |
| Ping timeout (sec) | integer [1..9999]; Default: 5 | Maximum response time (in seconds). If no echo is received after the amount of time specified in this field, the ping request is considered to have failed |
| Packet size | integer [0..1000]; Default: 56 | Ping packet size in bytes |
| Retry count | integer [1..9999]; Default: 2 | Indicates how many additional times the device will try sending ping requests if the initial one fails |
| Interface | Automatically selected | Ping from mobile; Default: Automatically selected | Specifies through which interface the pings will be sent. If Automatically selected is set, the pings will go through the main WAN interface |
| Host to ping | host | ip; Default: 8.8.8.8 | Indicates the host to which ping requests will be sent |
Periodic Reboot
Periodic Reboot is a function that reboots the router at a specified time interval regardless of other circumstances. It can be used as prophylactic measure, for example, to reboot the router once at the end of every week.
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:
| Field | Value | Description |
|---|---|---|
| Enable | yes | no; Default: no | Turns Periodic Reboot ON or OFF |
| Days | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday; Default: none | The day or multiple days on which the router will reboot |
| Hour | integer [0..23]; Default: 23 | The hour of the day on which the router will reboot |
| Minute | integer [0..59]; Default: 0 | The minute of the hour on which the router will reboot |
[[Category:{{{name}}} Services section]]