RUT900 Auto Reboot: Difference between revisions

From Teltonika Networks Wiki
VisualWikitext
No edit summary
 
(6 intermediate revisions by 3 users not shown)
Line 1: Line 1:
==Summary==
{{Template: Networking_rutos_manual_auto_reboot
 
<!------------------------DEVICE----------------------->
This chapter is an overview of '''Auto Reboot''' functions of RUT routers.
| name      = RUT900
 
| series    = RUT9
==Ping Reboot==
<!----------------------SEPARATORS--------------------->
 
| mobile    = 1
The '''Ping Reboot''' function will periodically send Ping commands to a specified server and wait for received echos. If no echo is received, the router will send Ping commands a defined number of times at a defined frequency of time. If no echo is received after the defined number of unsuccessful retries, the router will reboot.
| dualsim  = 1
 
| dualmodem = 0
[[Image: Services auto reboot ping reboot.PNG]]
}}
 
===Ping Reboot Configuration===
----
[[Image: Services auto reboot ping reboot configuration.PNG]]
 
<table class="nd-mantable">
    <tr>
        <th>field name</th>
      <th>value</th>
      <th>description</th>
    </tr>
    <tr>
      <td>Enable</td>
      <td>yes {{!}} no; Default: '''no'''</td>
      <td>Toggles Ping Reboot ON or OFF</td>
    </tr>
    <tr>
      <td>No action on data limit</td>
      <td>yes {{!}} no; Default: '''no'''</td>
      <td>If enabled, stops actions after data limit is reached</td>
    </tr>
    <tr>
    <td>Action if no echo is received</td>
        <td>Reboot {{!}} Modem restart {{!}} Restart mobile connection {{!}} (Re)register {{!}} none; Default: '''Reboot'''</td>
        <td>Specifies the action that is to be taken if no ICMP echo is received after ping</td>
    </tr>
    <tr>
    <td>Interval between pings</td>
        <td>5 mins {{!}} 15 mins {{!}} 30 mins {{!}} 1 hour {{!}} 2 hours; Default: '''5 mins'''</td>
        <td>Interval at which ping requests are sent to the specified host</td>
    </tr>
    <tr>
      <td>Ping timeout (sec)</td>
      <td>integer [1..9999]; Default: '''5'''</td>
      <td>Time after which a ping is considered as unsuccessful</td>
    </tr>
    <tr>
      <td>Packet size</td>
      <td>integer [0..1000]; Default: '''56'''</td>
      <td>Defines the ping packet size in bytes</td>
    </tr>
    <tr>
    <td>Retry count</td>
        <td>integer [1..9999]; Default: '''2'''</td>
        <td>Defines how many ping retries before the router takes the specified action</td>
    </tr>
    <tr>
    <td>Interface</td>
        <td>Automatically selected {{!}} Ping from mobile; Default: '''Automatically selected'''</td>
        <td>Specifies through which interface the pings will be sent. If '''Automatically selected''' is set, the pings will go through the main WAN interface</td>
    </tr>
    <tr>
    <td>Host to ping</td>
        <td>host {{!}} ip; Default: '''8.8.8.8'''</td>
        <td>Host to send pings to. Select a host that is usually always reachable through WAN, e.g., Google's DNS server 8.8.8.8</td>
    </tr>
</table>
 
==Periodic Reboot==
 
'''Periodic reboot''' is a function that reboots the router at a specified time interval regardless of other circumstances.
 
[[Image:Services auto reboot periodic reboot.PNG]]
 
<table class="nd-mantable">
    <tr>
        <th>field name</th>
      <th>value</th>
      <th>description</th>
    </tr>
    <tr>
      <td>Enable</td>
      <td>yes {{!}} no; Default: '''no'''</td>
      <td>Toggles Periodic Reboot ON or OFF</td>
    </tr>
    <tr>
      <td>Days</td>
      <td>Monday {{!}} Tuesday {{!}} Wednesday {{!}} Thursday {{!}} Friday {{!}} Saturday {{!}} Sunday; Default: " "</td>
      <td>Selects a day or multiple days to which the Periodic Reboot function will apply to</td>
    </tr>
    <tr>
    <td>Hour</td>
        <td>integer [0..23]; Default: '''23'''</td>
        <td>The hour that the router will reboot</td>
    </tr>
    <tr>
    <td>Minute</td>
        <td>integer [0..59]; Default: '''0'''</td>
        <td>The minute that the router will reboot</td>
    </tr>
</table>
 
==Wget Reboot==
 
The '''Wget Reboot''' function works in a very similar manner to Ping Reboot. Ping Reboot sends ping requests to determine whether the conditions for the specified action have been met, while Wget Reboot sends Wget requests for the same purpose. '''Wget''' is a computer program that retrieves content from web servers.
 
[[File:Services auto reboot wget reboot.png]]
 
{| class="wikitable"
|+
! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | FIELD NAME
! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | VALUE
! style="width: 579px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | DESCRIPTION
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Enable
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | yes {{!}} no; Default: '''no'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Toggles Wget Reboot ON or OFF
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Action if response is received
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Reboot {{!}} Modem restart {{!}} Restart mobile connection {{!}} (Re)register {{!}} None; Default: '''Reboot'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The action that will be performed after the specified number of failed Wget requests
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Interval between requests
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | 1 mins {{!}} 2 mins {{!}} 3 mins {{!}} 4 mins {{!}} 5 mins {{!}} 15 mins {{!}} 30 mins {{!}} 1 hour {{!}} 2 hours; Default: '''5 mins'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Interval at which Wget requests will be sent to the specified host or IP address
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Wget timeout (sec)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | integer [1..9999]; Default: '''2'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Time after which a Wget request is considered as unsuccessful
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Retry count
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | integer [1..9999]; Default: '''5'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Specifies how many retries before the router takes the specified action
|-
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Host to ping
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | host {{!}} ip; Default: '''<nowiki>http://www.google.com</nowiki>'''
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Host or IP address to send Wget requests to
|-
|}

Latest revision as of 13:18, 19 July 2021


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 RUT900 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. 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.

Field Value Description
Enable off | on; default: off Turns the rule on or off.
No action on data limit off | on; default: off Stop actions when mobile data limit is reached.
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| Modem reboot | Restart mobile connection | (Re)register | Send SMS; 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.
Phone Number phone number(s); default: none Recipient's phone number(s) specified in international format.
Message text string; default: none Text to be included in the SMS message.
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.
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.
IP type IPv4 | IPv6; default: IPv4 IP address version of the host to ping.
Action condition When all requests fail | When any request fails; default: When all requests fail Select when the action will be executed.
Host to ping host | ip; default: 8.8.8.8 Hostname or IP address to which the Ping/Wget requests will be sent.
Host to ping from SIM 1 ip; default: 8.8.8.8 IP address to which the Ping requests will be sent on SIM 1.
Host to ping from SIM 2 ip; default: 8.8.8.8 IP address to which the Ping requests will be sent on SIM 2.
URL url address; default: none URL to which the wget requests will be sent (e.g., http://www.host.com).

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

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 | Modem 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.
Retrieved from "https://wiki.teltonika-networks.com/index.php?title=RUT900_Auto_Reboot&oldid=82291"