Template:Networking rutos manual auto reboot: Difference between revisions

| fw_version ={{Template: Networking_rutos_manual_latest_fw

  | series = {{{series}}}

}}

{{#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>|}}

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.

}}}}

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

     <tr>

         <td>Enable</td>

         <td>Turns the rule on or off.</td>

     </tr>

     <tr>

         <td>Type</td>

         <td>Method used for health checking.

             <ul>

     <tr>

         <td>Action if no echo is received</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>Interval</td>

         <td>The frequency at which ping/Wget requests are sent to the specified host.</td>

     </tr>

     <tr>

         <td>IP type</td>

         <td>IP address version of the host to ping.</td>

     </tr>

     <tr>

         <td>Host to ping</td>

         <td>Hostname or IP address to which the Ping/Wget requests will be sent.</td>

     </tr>{{#ifeq:{{{mobile}}} | 1 |

</table>

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.

     <tr>

         <td>Enable</td>

         <td>Turns the rule on or off.</td>

     </tr>

     <tr>

         <td>Action</td>

         <td>Action that will be executed at the specified time.</td>

   </tr>{{#ifeq:{{{dualmodem}}} | 1 |

     <tr>

         <td><span style="color:red">Modem</span></td>

         <td>Specifies which modem to reboot.</td>

     </tr>|}}

     <tr>

         <td>Interval type</td>

         <td>Scheduler instance interval type.</td>

     </tr>

     <tr>

         <td><span style="color: green">Week days</span></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>Force last day</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>