Jump to content

Template:Networking rutos manual auto reboot: Difference between revisions

no edit summary
No edit summary
No edit summary
(29 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Template:Networking_rutos_manual_fw_disclosure
{{#switch: {{{series}}} |TAP100|TAP200 ={{Template: Networking_device_manual_fw_disclosure
| fw_version = {{{series}}}_R_00.02.05
| series = {{{series}}}
| series     = {{{series}}}
| name  = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
| name  = {{{name}}}
}}
}}
}}
__TOC__
{{#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>|}}
==Summary==
{{#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 =}}
 
{{#switch: {{{series}}} |TAP100|TAP200 =__TOC__ |#default =}}
{{#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. 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.


{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
{{#switch: {{{series}}} | TAP100 | TAP200 =| #default = {{Template: Networking_rutos_manual_basic_advanced_webui_disclaimer
| series = {{{series}}}
| series = {{{series}}}
}}
}}}}


==Ping/Wget Reboot==
{{#switch: {{{series}}} |TAP100|TAP200 = ==Ping/Wget Reboot==|#default = ===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 22: Line 31:
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.
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.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_auto_reboot_ping_wget_reboot_settings_configuration_mobile_{{{mobile}}}_v2.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 32: Line 41:
     <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>Type</td>
         <td>Type</td>
         <td>Ping | Wget; 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>
Line 47: Line 56:
     <tr>
     <tr>
         <td>Action if no echo is received</td>
         <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>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.</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>
        <td><span style="color: #20C0D7;">Gateway modem</span></td>
        <td>Primary modem {{!}} Secondary modem; default: <b>Primary modem</b></td>
        <td>Specifies which modem to use for sending the SMS message.</td>
    </tr>|}}{{#ifeq:{{{mobile}}} | 1 |
    <tr>
        <td><span style="color: #20C0D7;">Phone Number</span></td>
        <td>phone number(s); default: <b>none</b></td>
        <td>Recipient's phone number(s) specified in international format.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Interval between pings</td>
        <td><span style="color: #20C0D7;">Message text</span></td>
         <td>5 mins | 15 mins | 30 mins | 1 hour | 2 hours; default: <b>5 mins</b></td>
        <td>string; default: <b>none</b></td>
        <td>Text to be included in the SMS message.</td>
    </tr>|}}
    <tr>
         <td>Interval</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>
     <tr>
     <tr>
         <td>Ping timeout (sec)</td>
         <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>
        <td>Timeout (sec)</td>
         <td>integer [1..9999]; default: <b>5</b></td>
         <td>integer [1..9999]; default: <b>5</b></td>
         <td>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.</td>
         <td>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.</td>
Line 64: Line 93:
         <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>{{#ifeq:{{{mobile}}} | 1 |
    <tr>
        <td>Interface</td>
        <td>Automatically selected {{!}} <span style="color:red">Ping from mobile</span>; 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>
         <td>Try count</td>
         <td>IP type</td>
         <td>integer [1..9999]; default: <b>2</b></td>
         <td>IPv4 {{!}} IPv6; default: <b>IPv4</b></td>
         <td>Indicates how many additional times the device will try sending requests if the initial one fails.</td>
         <td>IP address version of the host to ping.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Host</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>
     </tr>{{#ifeq:{{{mobile}}} | 1 |
    <tr>
        <td><span style="color:red">Host to ping from SIM 1</span></td>
        <td>ip; default: <b>8.8.8.8</b></td>
        <td>IP address to which the Ping requests will be sent on SIM 1.</td>
    </tr>|}}{{#ifeq:{{{dualsim}}} | 1 |
    <tr>
        <td><span style="color:red">Host to ping from SIM 2</span></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>
    </tr>|}}
</table>
</table>


==Reboot Scheduler==
{{#switch: {{{series}}} |TAP100|TAP200 = ==Reboot Scheduler==|#default = ===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.
Line 97: Line 141:
     <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 | <nowiki>|</nowiki>Modem reboot}} ; default: <b> Device reboot</b></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>Action that will be executed at the specified time.</td>
         <td>Action that will be executed at the specified time.</td>
   </tr>
   </tr>{{#ifeq:{{{dualmodem}}} | 1 |
    <tr>
        <td><span style="color:red">Modem</span></td>
        <td>Primary modem {{!}} Secondary modem; default: <b>Primary modem</b></td>
        <td>Specifies which modem to reboot.</td>
    </tr>|}}
    <tr>
        <td>Interval type</td>
        <td><span style="color: green">Week days</span> {{!}} <span style="color: blue;">Month days</span>; default:  <b>Week days</b></td>
        <td>Scheduler instance interval type.</td>
    </tr>
    <tr>
        <td><span style="color: green">Week days</span></td>
        <td>Monday {{!}} Tuesday {{!}} Wednesday {{!}} Thursday {{!}} Friday {{!}} Saturday {{!}} Sunday; default:  <b>Monday</b></td>
        <td>Week day(s) when actions will be executed. This field becomes visible when Interval type is set to Week days.</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>
     <tr>
         <td>Week days</td>
         <td>Day time</td>
         <td>Monday| Tuesday| Wednesday| Thursday | Friday | Saturday | Sunday; default: <b> Monday</b></td>
         <td>time [00:00..23:59]; default: <b>none</b></td>
         <td>Week day/s when actions will be executed.</td>
         <td>Exact time of day the reboot will take place</td>
   </tr>
   </tr>
     <tr>
     <tr>
         <td>Time</td>
         <td>Force last day</td>
         <td>time; default: <b>12:00</b></td>
         <td>off {{!}} on; default: <b>off</b></td>
         <td> Here you can specify the hour/minute for action to occur.</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>
    </tr>
</table>
</table>
[[Category:{{{name}}} Services section]]
{{#switch: {{{series}}} |TAP100|TAP200 = [[Category:{{{name}}} System section]] | #default =}}