Difference between revisions of "Template:Networking rutos manual auto reboot"

From Teltonika Networks Wiki
(Created 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...")
 
Line 1: Line 1:
 +
{{Template:Networking_rutos_manual_fw_disclosure
 +
| fw_version = {{{series}}}_R_00.02.03
 +
| series = {{{series}}}
 +
}}
 
__TOC__
 
__TOC__
 
==Summary==
 
==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.
 
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_rutos_manual_basic_advanced_webui_disclaimer}}
{{Template: Networking_rutx_manual_fw_disclosure
 
| fw_version = {{{fw_version}}}
 
}}
 
 
 
 
==Ping Reboot==
 
==Ping Reboot==
  
Line 14: Line 14:
 
The Ping Reboot section contains one preconfigured rule by default:
 
The Ping Reboot section contains one preconfigured rule by default:
  
[[File:Networking_rutx_manual_auto_reboot_ping_reboot_v1.png]]
+
[[File: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.
 
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]]
+
[[File:Networking_rutos_manual_auto_reboot_ping_reboot_configuration_v1.png]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 30: Line 30:
 
         <td>off | on; default: <b>off</b></td>
 
         <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>
 
{{#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>
 
     <tr>
 
     <tr>
Line 46: Line 40:
 
             </ul>
 
             </ul>
 
         </td>
 
         </td>
 +
    </tr>
 +
    <tr>
 +
        <td>Action if no echo is received</td>
 +
        <td>Device reboot {{#ifeq:{{{mobile}}} | 1 | <nowiki>|</nowiki>Modem reboot}} | None |; default: <b> Device reboot</b></td>
 +
        <td>Action that will be executed if there is no response after the specified amount of retries.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 63: Line 62:
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td>Retry count</td>
+
         <td>Try count</td>
 
         <td>integer [1..9999]; default: <b>2</b></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>
 
         <td>Indicates how many additional times the device will try sending requests if the initial one fails.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
        <td>Interface</td>
+
         <td>Host</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>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>
 
     </tr>
 
</table>
 
</table>
Line 85: Line 79:
 
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:  
 
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}}}]]
+
[[File:Networking_rutos_manual_auto_reboot_periodic_reboot_v1.png]]
 +
[[File:Networking_rutos_manual_auto_reboot_periodic_reboot_configuration_v1.png]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 96: Line 91:
 
         <td>Enable</td>
 
         <td>Enable</td>
 
         <td>off | on; default: <b>off</b></td>
 
         <td>off | on; default: <b>off</b></td>
         <td>Turns Periodic Reboot on or off.</td>
+
         <td>Turns the rule on or off.</td>
     </tr></table>
+
     </tr>
 
+
    <tr>
 +
        <td>Action</td>
 +
        <td>Device reboot {{#ifeq:{{{mobile}}} | 1 | <nowiki>|</nowiki>Modem reboot}} | None |; default: <b> Device reboot</b></td>
 +
        <td>Action that will be executed at the specified time.</td>
 +
  </tr>
 +
    <tr>
 +
        <td>Week days</td>
 +
        <td>Monday| Tuesday| Wednesday| Thursday | Friday | Saturday | Sunday; default:  <b> Monday</b></td>
 +
        <td>Week day/s when actions will be executed.</td>
 +
  </tr>
 +
</table>
 
[[Category:{{{name}}} Services section]]
 
[[Category:{{{name}}} Services section]]

Revision as of 11:06, 13 May 2020

Template:Networking rutos manual fw disclosure

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.

Networking rutos manual webui basic advanced mode 75.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:

File: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.

File:Networking rutos manual auto reboot ping reboot configuration v1.png

Field Value Description
Enable off | on; default: off Turns the rule on or off.
Type Ping | Wget; default: Ping Method 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 received Device reboot | None |; default: Device reboot Action that will be executed if there is no response after the specified amount of retries.
Interval between pings 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.
Ping 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.
Try count integer [1..9999]; default: 2 Indicates how many additional times the device will try sending requests if the initial one fails.
Host host | ip; default: 8.8.8.8 Hostname 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. 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:Networking rutos manual auto reboot periodic reboot v1.png File:Networking rutos manual auto reboot periodic reboot configuration v1.png

Field Value Description
Enable off | on; default: off Turns the rule on or off.
Action Device reboot | None |; default: Device reboot Action that will be executed at the specified time.
Week days Monday| Tuesday| Wednesday| Thursday | Friday | Saturday | Sunday; default: Monday Week day/s when actions will be executed.

[[Category:{{{name}}} Services section]]