Difference between revisions of "Template:Networking rutos manual auto reboot"
From Teltonika Networks Wiki
| Line 1: | Line 1: | ||
| − | {{Template: Networking_rutos_manual_fw_disclosure | + | {{#switch: {{{series}}} |TAP100|TAP200 ={{Template: Networking_rutos_manual_fw_disclosure |
| fw_version ={{Template: Networking_rutos_manual_latest_fw | | fw_version ={{Template: Networking_rutos_manual_latest_fw | ||
| series = {{{series}}} | | series = {{{series}}} | ||
| Line 6: | Line 6: | ||
}} | }} | ||
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Auto Reboot (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}} | {{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} Auto Reboot (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT9XX}} and earlier) user manual page.</i>|}} | ||
| − | {{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} Auto Reboot (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}} | + | {{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} Auto Reboot (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}| #default =}} |
| − | + | ||
| − | ==Summary== | + | {{#switch: {{{series}}} |TAP100|TAP200 = ==Summary== |#default = ===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. | 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. | ||
| Line 18: | Line 18: | ||
}}}} | }}}} | ||
| − | ==Ping/Wget Reboot== | + | {{#switch: {{{series}}} |TAP100|TAP200 = ==Ping/Wget Reboot==|#default = ===Ping/Wget Reboot===}} |
The <b>Ping/Wget Reboot</b> functions periodically send 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 <b>Ping/Wget Reboot</b> functions periodically send 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). | ||
| Line 38: | Line 38: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns the rule on or off.</td> | <td>Turns the rule on or off.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Type</td> | <td>Type</td> | ||
| − | <td>Ping | + | <td>Ping {{!}} Wget; default: <b>Ping</b></td> |
<td>Method used for health checking. | <td>Method used for health checking. | ||
<ul> | <ul> | ||
| Line 53: | Line 53: | ||
<tr> | <tr> | ||
<td>Action if no echo is received</td> | <td>Action if no echo is received</td> | ||
| − | <td>Device reboot | + | <td>Device reboot {{!}} None{{#ifeq:{{{mobile}}} | 1 | {{!}} Modem reboot {{!}} Restart mobile connection {{!}} (Re)register {{!}} <span style="color: #20C0D7;"><b>Send SMS</b></span>}}; default: <b>Device reboot</b></td> |
<td>Action that will be executed if there is no response after the specified amount of retries. If <b>None</b> is selected, only a message to syslog will be logged.</td> | <td>Action that will be executed if there is no response after the specified amount of retries. If <b>None</b> is selected, only a message to syslog will be logged.</td> | ||
</tr>{{#ifeq:{{{dualmodem}}} | 1 | | </tr>{{#ifeq:{{{dualmodem}}} | 1 | | ||
| Line 73: | Line 73: | ||
<tr> | <tr> | ||
<td>Interval</td> | <td>Interval</td> | ||
| − | <td>5 mins | + | <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> | <td>The frequency at which ping/Wget requests are sent to the specified host.</td> | ||
</tr> | </tr> | ||
| Line 98: | Line 98: | ||
<tr> | <tr> | ||
<td>IP type</td> | <td>IP type</td> | ||
| − | <td>IPv4 | + | <td>IPv4 {{!}} IPv6; default: <b>IPv4</b></td> |
<td>IP address version of the host to ping.</td> | <td>IP address version of the host to ping.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Host to ping</td> | <td>Host to ping</td> | ||
| − | <td>host | + | <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> | <td>Hostname or IP address to which the Ping/Wget requests will be sent.</td> | ||
</tr>{{#ifeq:{{{mobile}}} | 1 | | </tr>{{#ifeq:{{{mobile}}} | 1 | | ||
| Line 118: | Line 118: | ||
</table> | </table> | ||
| − | ==Reboot Scheduler== | + | {{#switch: {{{series}}} |TAP100|TAP200 = ==Reboot Scheduler==|#default = ===Reboot Scheduler===}} |
The <b>Reboot Scheduler</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. | The <b>Reboot Scheduler</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. | ||
| Line 138: | Line 138: | ||
<tr> | <tr> | ||
<td>Enable</td> | <td>Enable</td> | ||
| − | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Turns the rule on or off.</td> | <td>Turns the rule on or off.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td>Action</td> | <td>Action</td> | ||
| − | <td>Device reboot {{#ifeq:{{{mobile}}} | 1 | {{#ifeq:{{{dualmodem}}} | 1 | | + | <td>Device reboot {{#ifeq:{{{mobile}}} | 1 | {{#ifeq:{{{dualmodem}}} | 1 | {{!}}<span style="color:red"> Modem reboot</span>| {{!}} Modem reboot}}|}}; default: <b> Device reboot</b></td> |
<td>Action that will be executed at the specified time.</td> | <td>Action that will be executed at the specified time.</td> | ||
</tr>{{#ifeq:{{{dualmodem}}} | 1 | | </tr>{{#ifeq:{{{dualmodem}}} | 1 | | ||
<tr> | <tr> | ||
<td><span style="color:red">Modem</span></td> | <td><span style="color:red">Modem</span></td> | ||
| − | <td>Primary modem | + | <td>Primary modem {{!}} Secondary modem; default: <b>Primary modem</b></td> |
<td>Specifies which modem to reboot.</td> | <td>Specifies which modem to reboot.</td> | ||
</tr>|}} | </tr>|}} | ||
<tr> | <tr> | ||
<td>Interval type</td> | <td>Interval type</td> | ||
| − | <td><span style="color: green">Week days</span> | + | <td><span style="color: green">Week days</span> {{!}} <span style="color: blue;">Month days</span>; default: <b>Week days</b></td> |
<td>Scheduler instance interval type.</td> | <td>Scheduler instance interval type.</td> | ||
</tr> | </tr> | ||
<tr> | <tr> | ||
<td><span style="color: green">Week days</span></td> | <td><span style="color: green">Week days</span></td> | ||
| − | <td>Monday | + | <td>Monday {{!}} Tuesday {{!}} Wednesday {{!}} Thursday {{!}} Friday {{!}} Saturday {{!}} Sunday; default: <b>Monday</b></td> |
<td>Week day(s) when actions will be executed. This field becomes visible when Interval type is set to Week days.</td> | <td>Week day(s) when actions will be executed. This field becomes visible when Interval type is set to Week days.</td> | ||
</tr> | </tr> | ||
| Line 178: | Line 178: | ||
<tr> | <tr> | ||
<td>Force last day</td> | <td>Force last day</td> | ||
| − | <td>off | + | <td>off {{!}} on; default: <b>off</b></td> |
<td>Forces intervals to accept last day of month as a valid option if selected day doesn't exist in the ongoing month. This field becomes visible when Interval type is set to Month days.</td> | <td>Forces intervals to accept last day of month as a valid option if selected day doesn't exist in the ongoing month. This field becomes visible when Interval type is set to Month days.</td> | ||
</tr> | </tr> | ||
</table> | </table> | ||
| − | [[Category:{{{name}}} | + | [[Category:{{{name}}} System section]] |
Revision as of 12:58, 29 September 2023
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 {{{name}}} 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 "Advanced" button, located at the top of the WebUI.
Ping/Wget Reboot
The Ping/Wget Reboot functions periodically send 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/Wget Reboot section contains one pre-configured rule by default:
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.
[[File:Networking_rutos_manual_auto_reboot_ping_wget_reboot_settings_configuration_mobile_{{{mobile}}}_v2.png|border|class=tlt-border]]
| Field | Value | Description |
|---|---|---|
| Enable | off | on; default: off | Turns the rule on or off. |
| Type | Ping | Wget; default: Ping | Method used for health checking.
|
| Action if no echo is received | Device reboot | None; default: Device reboot | Action that will be executed if there is no response after the specified amount of retries. If None is selected, only a message to syslog will be logged. |
| Interval | 5 mins | 15 mins | 30 mins | 1 hour | 2 hours; default: 5 mins | The frequency at which ping/Wget requests are sent to the specified host. |
| Interval count | integer [1..9999]; default: 2 | Indicates how many additional times the device will try sending requests if the initial one fails. |
| Timeout (sec) | integer [1..9999]; default: 5 | 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. |
| Packet size | integer [0..1000]; default: 56 | ICMP packet size in bytes. |
| IP type | IPv4 | IPv6; default: IPv4 | IP address version of the host to ping. |
| Host to ping | host | ip; default: 8.8.8.8 | Hostname or IP address to which the Ping/Wget requests will be sent. |
Reboot Scheduler
The Reboot Scheduler 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.
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 | off | on; default: off | Turns the rule on or off. |
| Action | Device reboot ; default: Device reboot | Action that will be executed at the specified time. |
| Interval type | Week days | Month days; default: Week days | Scheduler instance interval type. |
| Week days | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday; default: Monday | Week day(s) when actions will be executed. This field becomes visible when Interval type is set to Week days. |
| Month day | integer [1..31]; default: 1 | Day of the month on which the reboot will occur. This field becomes visible when Interval type is set to Month days. |
| Month | month(s) [january..december]; default: none | The month(s) on which the reboot will occur. Leave empty to apply to all months. This field becomes visible when Interval type is set to Month days. |
| Day time | time [00:00..23:59]; default: none | Exact time of day the reboot will take place |
| Force last day | off | on; default: off | Forces intervals to accept last day of month as a valid option if selected day doesn't exist in the ongoing month. This field becomes visible when Interval type is set to Month days. |
[[Category:{{{name}}} System section]]
