|
|
| (3 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| ==Summary==
| | {{Template: Networking_rut_manual_auto_reboot |
| | | <!------------------------DEVICE-----------------------> |
| This chapter is an overview of '''Auto Reboot''' functions of RUT routers.
| | | name = RUT850 |
| | | | series = RUT850 |
| ==Ping Reboot==
| | <!----------------------SEPARATORS---------------------> |
| | | | wget = 0 |
| 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.
| | }} |
| | |
| [[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
| |
| |- | |
| |}
| |
£The information in this page is updated in accordance with firmware version .
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 RUT850 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:
| 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:
| 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:
| 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 |
