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

From Teltonika Networks Wiki
m (Added sentence " The maximum limit of instances is 30.")
(10 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
{{#switch: {{{series}}} |TAP100|TAP200 ={{Template: Networking_device_manual_fw_disclosure
+
{{Template: Networking_rutos_manual_fw_disclosure
−
| series = {{{series}}}
+
| fw_version ={{Template: Networking_rutos_manual_latest_fw
−
| name  = {{{name}}}
 
−
| fw_version ={{Template: Networking_device_manual_latest_fw
 
 
  | series = {{{series}}}
 
  | series = {{{series}}}
−
| name  = {{{name}}}
 
 
  }}
 
  }}
 
}}
 
}}
−
{{#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_device_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_device_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}| #default =}}
+
{{#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>|}}
−
 
+
__TOC__
−
{{#switch: {{{series}}} |TAP100|TAP200 =__TOC__ |#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 17: Line 13:
 
This chapter is an overview of the Auto Reboot section of {{{name}}} devices.
 
This chapter is an overview of the Auto Reboot section of {{{name}}} devices.
  
−
{{#switch: {{{series}}} | TAP100 | TAP200 =| #default = {{Template: Networking_rutos_manual_basic_advanced_webui_disclaimer
+
{{Template: Networking_rutos_manual_basic_advanced_webui_disclaimer
 
| series = {{{series}}}
 
| series = {{{series}}}
−
}}}}
+
}}
  
−
{{#switch: {{{series}}} |TAP100|TAP200 = ==Ping/Wget Reboot==|#default = ===Ping/Wget Reboot===}}
+
==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 29: Line 25:
 
[[File:Networking_rutos_manual_auto_reboot_ping_wget_reboot_settings.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_auto_reboot_ping_wget_reboot_settings.png|border|class=tlt-border]]
  
−
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. The maximum limit of instances is 30. If you wish to customize a rule, click the button that looks like a pencil next to it.
+
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]]
+
[[File:Networking_rutos_manual_auto_reboot_ping_wget_reboot_settings_configuration_mobile_{{{mobile}}}.png|border|class=tlt-border]]
  
 
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 41: Line 37:
 
     <tr>
 
     <tr>
 
         <td>Enable</td>
 
         <td>Enable</td>
−
         <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:{{{mobile}}}|1|
+
     </tr>
−
    <tr>
 
−
        <td>No action on data limit</td>
 
−
        <td>off {{!}} on; default: <b>off</b></td>
 
−
        <td>Stop actions when mobile data limit is reached.</td>
 
−
    </tr>|}}
 
 
     <tr>
 
     <tr>
 
         <td>Type</td>
 
         <td>Type</td>
−
         <td>Ping {{!}} Wget{{#switch:{{{name}}}|OTD140= <span style="color: #olive;">Port</span>|#default=}}; default: <b>Ping</b></td>
+
         <td>Ping | Wget; default: <b>Ping</b></td>
 
         <td>Method used for health checking.
 
         <td>Method used for health checking.
 
             <ul>
 
             <ul>
 
                 <li><b>Ping</b> - sends ICMP requests to the specified host.</li>
 
                 <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>{{#switch:{{{name}}}|OTD140=
+
                 <li><b>Wget</b> - retrieves the contents of the specified web server.</li>
−
                <li><b>Port</b> - sends pings, if ping doesn't go through a certain amount of times, the port to which the device that has the IP address is connected to, will be restarted.</li>|#default=}}
 
 
             </ul>
 
             </ul>
 
         </td>
 
         </td>
Line 62: Line 52:
 
     <tr>
 
     <tr>
 
         <td>Action if no echo is received</td>
 
         <td>Action if no echo is received</td>
−
         <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>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 82: Line 72:
 
     <tr>
 
     <tr>
 
         <td>Interval</td>
 
         <td>Interval</td>
−
         <td>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>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>
 
−
        <td>Interval 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>
 
     <tr>
 
     <tr>
Line 99: Line 84:
 
         <td>integer [0..1000]; default: <b>56</b></td>
 
         <td>integer [0..1000]; default: <b>56</b></td>
 
         <td>ICMP packet size in bytes.</td>
 
         <td>ICMP packet size in bytes.</td>
 +
    </tr>
 +
    <tr>
 +
        <td>Try 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>{{#ifeq:{{{mobile}}} | 1 |
 
     </tr>{{#ifeq:{{{mobile}}} | 1 |
 
     <tr>
 
     <tr>
Line 105: Line 95:
 
         <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>
 
         <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>
 
−
        <td>IP type</td>
 
−
        <td>IPv4 {{!}} IPv6; default: <b>IPv4</b></td>
 
−
        <td>IP address version of the host to ping.</td>
 
−
    </tr>
 
 
     <tr>
 
     <tr>
 
         <td>Host to ping</td>
 
         <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>{{#ifeq:{{{mobile}}} | 1 |
 
     </tr>{{#ifeq:{{{mobile}}} | 1 |
Line 124: Line 109:
 
         <td>ip; default: <b>8.8.8.8</b></td>
 
         <td>ip; default: <b>8.8.8.8</b></td>
 
         <td>IP address to which the Ping requests will be sent on SIM 2.</td>
 
         <td>IP address to which the Ping requests will be sent on SIM 2.</td>
−
     </tr>|}}{{#switch:{{{name}}}|OTD140=
+
     </tr>|}}
−
    <tr>
 
−
        <td><span style="color:olive">Ping by</span></td>
 
−
        <td><span style="color:green">Port</span> {{!}} IP; default: <b>8.8.8.8</b></td>
 
−
        <td>Ping IP's by Port or by IP.</td>
 
−
    </tr>
 
−
    <tr>
 
−
        <td><span style="color:green">Port to ping</span></td>
 
−
        <td>port number and number of devices (unsigned integer); default: <b>Port1:1</b></td>
 
−
        <td>Port number and number of devices addresses to be pinged. (Number of devices connected must be less or equal to the actual number of connected devices to the port).</td>
 
−
    </tr>|#default=}}
 
 
</table>
 
</table>
  
−
{{#switch: {{{series}}} |TAP100|TAP200 = ==Reboot Scheduler==|#default = ===Reboot Scheduler===}}
+
==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.
  
−
You can add more rules with the 'Add' button or delete them using the 'Delete' button. The maximum limit of instances is 30. If you wish to customize a rule, click the button that looks like a pencil 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_reboot_scheduler.png|border|class=tlt-border]]
 
[[File:Networking_rutos_manual_auto_reboot_reboot_scheduler.png|border|class=tlt-border]]
Line 157: Line 132:
 
     <tr>
 
     <tr>
 
         <td>Enable</td>
 
         <td>Enable</td>
−
         <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>
 
     </tr>
 
     <tr>
 
     <tr>
 
         <td>Action</td>
 
         <td>Action</td>
−
         <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>Device reboot {{#ifeq:{{{mobile}}} | 1 | {{#ifeq:{{{dualmodem}}} | 1 | <nowiki>|</nowiki><span style="color:red"> Modem reboot</span>| <nowiki>|</nowiki> 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 {{!}} Secondary modem; default: <b>Primary modem</b></td>
+
         <td>Primary modem<nowiki> | </nowiki>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>Week days</td>
−
         <td><span style="color: green">Week days</span> {{!}} <span style="color: blue;">Month days</span>; default:  <b>Week days</b></td>
+
         <td>Monday| Tuesday| Wednesday| Thursday | Friday | Saturday | Sunday; default:  <b> none</b></td>
−
         <td>Scheduler instance interval type.</td>
+
         <td>Week day(s) when actions will be executed.</td>
−
    </tr>
+
  </tr>
 
     <tr>
 
     <tr>
−
         <td><span style="color: green">Week days</span></td>
+
         <td>Time</td>
−
         <td>Monday {{!}} Tuesday {{!}} Wednesday {{!}} Thursday {{!}} Friday {{!}} Saturday {{!}} Sunday; default: <b>Monday</b></td>
+
         <td>time; default: <b>none</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>Here you can specify the hour/minute for action to occur.</td>
−
    </tr>
 
−
    <tr>
 
−
        <td><span style="color: blue">Month day</span></td>
 
−
        <td>integer [1..31]; default:  <b>1</b></td>
 
−
        <td>Day of the month on which the reboot will occur. This field becomes visible when Interval type is set to Month days.</td>
 
−
    </tr>
 
−
    <tr>
 
−
        <td><span style="color: blue">Month</span></td>
 
−
        <td>month(s) [january..december]; default:  <b>none</b></td>
 
−
        <td>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.</td>
 
−
    </tr>
 
−
    <tr>
 
−
        <td>Day time</td>
 
−
        <td>time [00:00..23:59]; default: <b>none</b></td>
 
−
        <td>Exact time of day the reboot will take place</td>
 
 
   </tr>
 
   </tr>
−
    <tr>
 
−
        <td>Force last day</td>
 
−
        <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>
 
−
    </tr>
 
 
</table>
 
</table>
−
{{#switch: {{{series}}} |TAP100|TAP200 = [[Category:{{{name}}} System section]] | #default =}}
+
[[Category:{{{name}}} Services section]]

Revision as of 17:39, 16 December 2021

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/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:

Networking rutos manual auto reboot ping wget reboot settings.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.

[[File:Networking_rutos_manual_auto_reboot_ping_wget_reboot_settings_configuration_mobile_{{{mobile}}}.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.
  • 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. 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.
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 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.

Networking rutos manual auto reboot reboot scheduler.png

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:

Networking rutos manual auto reboot reboot scheduler modify reboot instance.png

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.
Week days Monday| Tuesday| Wednesday| Thursday | Friday | Saturday | Sunday; default: none Week day(s) when actions will be executed.
Time time; default: none Here you can specify the hour/minute for action to occur.

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

Retrieved from "https://wiki.teltonika-networks.com/index.php?title=Template:Networking_rutos_manual_auto_reboot&oldid=86570"