2,486
edits
Changes
Template:Networking rutos manual auto reboot (view source)
Revision as of 09:06, 13 May 2020
, 09:06, 13 May 2020Created page with "__TOC__ ==Summary== Various automatic device reboot scenarios can be configured in the <b>Auto Reboot</b> section. Automatic reboots can be used as a prophylactic or precauti..."
__TOC__
==Summary==
Various automatic device reboot scenarios can be configured in the <b>Auto Reboot</b> 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 {{{name}}} devices.
{{Template: Networking_rutx_manual_fw_disclosure
| fw_version = {{{fw_version}}}
}}
==Ping Reboot==
The <b>Ping Reboot</b> 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:
[[File:Networking_rutx_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.
[[File:Networking_rutx09_rutx11_manual_auto_reboot_ping_reboot_configuration_v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Turns the rule on or off.</td>
</tr>
{{#ifeq:{{{modem}}} | 1 | {{Template: Networking_rutx_manual_auto_reboot_ping_reboot_table_element_1}} |}}
<tr>
<td>Action if no echo is received</td>
<td>Reboot | None; default: <b>Reboot</b></td>
<td>Action that will be executed if there is no response after the specified amount of retries.</td>
</tr>
<tr>
<td>Type</td>
<td>Ping | Wget; default: <b>Ping</b></td>
<td>Method used for health checking.
<ul>
<li><b>Ping</b> - sends ICMP requests to the specified host.</li>
<li><b>Wget</b> - retrieves the contents of the specified web server.</li>
</ul>
</td>
</tr>
<tr>
<td>Interval between pings</td>
<td>5 mins | 15 mins | 30 mins | 1 hour | 2 hours; default: <b>5 mins</b></td>
<td>The frequency at which ping/Wget requests are sent to the specified host.</td>
</tr>
<tr>
<td>Ping timeout (sec)</td>
<td>integer [1..9999]; default: <b>5</b></td>
<td>Maximum 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.</td>
</tr>
<tr>
<td>Packet size</td>
<td>integer [0..1000]; default: <b>56</b></td>
<td>ICMP packet size in bytes.</td>
</tr>
<tr>
<td>Retry count</td>
<td>integer [1..9999]; default: <b>2</b></td>
<td>Indicates how many additional times the device will try sending requests if the initial one fails.</td>
</tr>
<tr>
<td>Interface</td>
<td>{{#ifeq:{{{modem}}}|1|Ping from mobile {{!}} |}} Automatically selected; default: <b>Automatically selected</b></td>
<td>Interface that will send the ping/Wget requests.</td>
</tr>
<tr>
<td>Host to ping</td>
<td>host | ip; default: <b>8.8.8.8</b></td>
<td>Hostname or IP address to which the ping/Wget requests will be sent.</td>
</tr>
</table>
==Periodic Reboot==
<b>Periodic Reboot</b> 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. Reboot time is chosen by selecting time interval boxes in the scheduler table to indicate on which days/hours reboot will occur.
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:
[[File:{{{file_periodic_reboot}}}]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Turns Periodic Reboot on or off.</td>
</tr></table>
[[Category:{{{name}}} Services section]]
==Summary==
Various automatic device reboot scenarios can be configured in the <b>Auto Reboot</b> 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 {{{name}}} devices.
{{Template: Networking_rutx_manual_fw_disclosure
| fw_version = {{{fw_version}}}
}}
==Ping Reboot==
The <b>Ping Reboot</b> 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:
[[File:Networking_rutx_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.
[[File:Networking_rutx09_rutx11_manual_auto_reboot_ping_reboot_configuration_v1.png]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Turns the rule on or off.</td>
</tr>
{{#ifeq:{{{modem}}} | 1 | {{Template: Networking_rutx_manual_auto_reboot_ping_reboot_table_element_1}} |}}
<tr>
<td>Action if no echo is received</td>
<td>Reboot | None; default: <b>Reboot</b></td>
<td>Action that will be executed if there is no response after the specified amount of retries.</td>
</tr>
<tr>
<td>Type</td>
<td>Ping | Wget; default: <b>Ping</b></td>
<td>Method used for health checking.
<ul>
<li><b>Ping</b> - sends ICMP requests to the specified host.</li>
<li><b>Wget</b> - retrieves the contents of the specified web server.</li>
</ul>
</td>
</tr>
<tr>
<td>Interval between pings</td>
<td>5 mins | 15 mins | 30 mins | 1 hour | 2 hours; default: <b>5 mins</b></td>
<td>The frequency at which ping/Wget requests are sent to the specified host.</td>
</tr>
<tr>
<td>Ping timeout (sec)</td>
<td>integer [1..9999]; default: <b>5</b></td>
<td>Maximum 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.</td>
</tr>
<tr>
<td>Packet size</td>
<td>integer [0..1000]; default: <b>56</b></td>
<td>ICMP packet size in bytes.</td>
</tr>
<tr>
<td>Retry count</td>
<td>integer [1..9999]; default: <b>2</b></td>
<td>Indicates how many additional times the device will try sending requests if the initial one fails.</td>
</tr>
<tr>
<td>Interface</td>
<td>{{#ifeq:{{{modem}}}|1|Ping from mobile {{!}} |}} Automatically selected; default: <b>Automatically selected</b></td>
<td>Interface that will send the ping/Wget requests.</td>
</tr>
<tr>
<td>Host to ping</td>
<td>host | ip; default: <b>8.8.8.8</b></td>
<td>Hostname or IP address to which the ping/Wget requests will be sent.</td>
</tr>
</table>
==Periodic Reboot==
<b>Periodic Reboot</b> 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. Reboot time is chosen by selecting time interval boxes in the scheduler table to indicate on which days/hours reboot will occur.
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:
[[File:{{{file_periodic_reboot}}}]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off | on; default: <b>off</b></td>
<td>Turns Periodic Reboot on or off.</td>
</tr></table>
[[Category:{{{name}}} Services section]]
