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

From Teltonika Networks Wiki
(44 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 +
{{Template: Networking_rutos_manual_fw_disclosure
 +
| fw_version = {{#switch: {{{series}}}
 +
  | RUT2XX = {{{series}}}_R_00.01.13
 +
  | RUT850 = {{{series}}}_R_00.01.04
 +
  | RUT9XX = {{{series}}}_R_00.06.07}}
 +
| series    = {{{series}}}
 +
}}
 
==Summary==
 
==Summary==
  
Various automatic router 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 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 of the user manual provides an overview of the Auto Reboot page for {{{name}}} devices.
  
 
==Ping Reboot==
 
==Ping Reboot==
Line 7: Line 16:
 
The <b>Ping Reboot</b> 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 <b>Ping Reboot</b> 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 preconfigured 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:
+
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:
  
[[File:{{{file_ping_reboot}}}]]  
+
[[File:Rutxxx_webui_services_auto_reboot_ping_reboot_v1.png]]  
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
 
     <tr>
 
     <tr>
         <th>field name</th>
+
         <th>Field</th>
       <th>value</th>
+
       <th>Value</th>
       <th>description</th>
+
       <th>Description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 69: Line 78:
 
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:
 
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:
  
[[File:{{{file_ping_reboot_settings}}}]]
+
[[File:Rutxxx_webui_services_auto_reboot_ping_reboot_settings_v1.png]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
 
     <tr>
 
     <tr>
         <th>field name</th>
+
         <th>Field</th>
       <th>value</th>
+
       <th>Value</th>
       <th>description</th>
+
       <th>Description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 81: Line 90:
 
       <td>yes | no; Default: <b>no</b></td>
 
       <td>yes | no; Default: <b>no</b></td>
 
       <td>Turns the rule ON or OFF</td>
 
       <td>Turns the rule ON or OFF</td>
 +
    </tr>
 +
    <tr>
 +
      <td>No action on data limit</td>
 +
      <td>yes | no; Default: <b>no</b></td>
 +
      <td>If enabled, stops taking actions after data limit is reached</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 106: Line 120:
 
         <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 ping requests if the initial one fails</td>
 
         <td>Indicates how many additional times the device will try sending ping requests if the initial one fails</td>
 +
    </tr>
 +
    <tr>
 +
    <td>Interface</td>
 +
        <td>Automatically selected | Ping from mobile; Default: <b>Automatically selected</b></td>
 +
        <td>Specifies through which interface the pings will be sent. If <b>Automatically selected</b> is set, the pings will go through the main WAN interface</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 120: Line 139:
 
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_setup}}}]]
+
[[File:Rutxxx_webui_services_auto_reboot_periodic_reboot_setup_v1.png]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
 
     <tr>
 
     <tr>
         <th>field name</th>
+
         <th>Field</th>
       <th>value</th>
+
       <th>Value</th>
       <th>description</th>
+
       <th>Description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 150: Line 169:
 
</table>
 
</table>
  
==Wget Reboot==
+
{{#ifeq: {{{wget}}} | 1 | <h2>Wget Reboot</h2>
  
 
<b>Wget</b> is a computer program that retrieves content from web servers. The <b>Wget Reboot</b> function works in a very similar manner to Ping Reboot. While Ping Reboot sends ping requests to determine whether the conditions for the specified action have been met, Wget Reboot attempts to retrieve the contents of a web server.
 
<b>Wget</b> is a computer program that retrieves content from web servers. The <b>Wget Reboot</b> function works in a very similar manner to Ping Reboot. While Ping Reboot sends ping requests to determine whether the conditions for the specified action have been met, Wget Reboot attempts to retrieve the contents of a web server.
Line 156: Line 175:
 
The figure below is an example of the Wget Reboot configuration page and the table below provides information on the fields contained in that page:
 
The figure below is an example of the Wget Reboot configuration page and the table below provides information on the fields contained in that page:
  
[[File:{{{file_wget_reboot_setup}}}]]
+
[[File:Rutxxx_webui_services_auto_reboot_wget_reboot_setup_v1.png]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
 
     <tr>
 
     <tr>
         <th>field name</th>
+
         <th>Field</th>
       <th>value</th>
+
       <th>Value</th>
       <th>description</th>
+
       <th>Description</th>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Enable</td>
 
       <td>Enable</td>
       <td>yes | no; Default: <b>no</b></td>
+
       <td>yes {{!}} no; Default: <b>no</b></td>
 
       <td>Turns Wget Reboot ON or OFF</td>
 
       <td>Turns Wget Reboot ON or OFF</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
       <td>Action if no response is received</td>
 
       <td>Action if no response is received</td>
       <td>Reboot | {{#ifeq:{{{series}}} | TRB14x ||Modem restart}} | Restart mobile connection | (Re)register | None; Default: <b>Reboot</b></td>
+
       <td>Reboot {{!}} Modem restart {{!}} Restart mobile connection {{!}} (Re)register {{!}} Send SMS {{!}} None; Default: <b>Reboot</b></td>
 
       <td>The action that will be performed after the specified number of failed Wget requests</td>
 
       <td>The action that will be performed after the specified number of failed Wget requests</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
 
     <td>Interval between requests</td>
 
     <td>Interval between requests</td>
         <td>1 mins | 2 mins | 3 mins | 4 mins | 5 mins | 15 mins | 30 mins | 1 hour | 2 hours; Default: <b>5 mins</b></td>
+
         <td>5 mins {{!}} 15 mins {{!}} 30 mins {{!}} 1 hour {{!}} 2 hours; Default: <b>5 mins</b></td>
 
         <td>Interval at which Wget requests will be sent to the specified host or IP address</td>
 
         <td>Interval at which Wget requests will be sent to the specified host or IP address</td>
 
     </tr>
 
     </tr>
Line 191: Line 210:
 
     <tr>
 
     <tr>
 
     <td>Host to ping</td>
 
     <td>Host to ping</td>
         <td>host | ip; Default: <b><nowiki>http://www.google.com</nowiki></b></td>
+
         <td>host {{!}} ip; Default: <b><nowiki>www.google.com</nowiki></b></td>
 
         <td>Host or IP address to send Wget requests to</td>
 
         <td>Host or IP address to send Wget requests to</td>
 
     </tr>
 
     </tr>
 
</table>
 
</table>
 +
|}}
 +
[[Category:{{{name}}} Services section]]

Revision as of 08:31, 9 April 2021

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:

Rutxxx webui services auto reboot ping reboot v1.png

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:

Rutxxx webui services auto reboot ping reboot settings v1.png

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:

Rutxxx webui services auto reboot periodic reboot setup v1.png

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]]