Changes

no edit summary
Line 1: Line 1:  +
{{Template:Networking_rutos_manual_fw_disclosure
 +
| fw_version = {{{series}}}_R_00.02.03
 +
| series = {{{series}}}
 +
}}
 
__TOC__
 
__TOC__
 
==Summary==
 
==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. This chapter is an overview of the Auto Reboot section of {{{name}}} devices.
 
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.
 
+
{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer}}
{{Template: Networking_rutx_manual_fw_disclosure
  −
| fw_version = {{{fw_version}}}
  −
}}
  −
 
   
==Ping Reboot==
 
==Ping Reboot==
   Line 14: Line 14:  
The Ping Reboot section contains one preconfigured rule by default:
 
The Ping Reboot section contains one preconfigured rule by default:
   −
[[File:Networking_rutx_manual_auto_reboot_ping_reboot_v1.png]]
+
[[File:Networking_rutos_manual_auto_reboot_ping_reboot_v1.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. Refer to the figure and table below for information Ping Reboot configuration.
 
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. Refer to the figure and table below for information Ping Reboot configuration.
   −
[[File:Networking_rutx09_rutx11_manual_auto_reboot_ping_reboot_configuration_v1.png]]
+
[[File:Networking_rutos_manual_auto_reboot_ping_reboot_configuration_v1.png]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 30: Line 30:  
         <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:{{{modem}}} | 1 | {{Template: Networking_rutx_manual_auto_reboot_ping_reboot_table_element_1}} |}}
  −
    <tr>
  −
        <td>Action if no echo is received</td>
  −
        <td>Reboot | None; default: <b>Reboot</b></td>
  −
        <td>Action that will be executed if there is no response after the specified amount of retries.</td>
   
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 46: Line 40:  
             </ul>
 
             </ul>
 
         </td>
 
         </td>
 +
    </tr>
 +
    <tr>
 +
        <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>Action that will be executed if there is no response after the specified amount of retries.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
Line 63: Line 62:  
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
         <td>Retry count</td>
+
         <td>Try count</td>
 
         <td>integer [1..9999]; default: <b>2</b></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>
 
         <td>Indicates how many additional times the device will try sending requests if the initial one fails.</td>
 
     </tr>
 
     </tr>
 
     <tr>
 
     <tr>
        <td>Interface</td>
+
         <td>Host</td>
        <td>{{#ifeq:{{{modem}}}|1|Ping from mobile {{!}} |}} Automatically selected; default: <b>Automatically selected</b></td>
  −
        <td>Interface that will send the ping/Wget requests.</td>
  −
    </tr>
  −
    <tr>
  −
         <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>
 
</table>
 
</table>
Line 85: Line 79:  
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:  
 
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:  
   −
[[File:{{{file_periodic_reboot}}}]]
+
[[File:Networking_rutos_manual_auto_reboot_periodic_reboot_v1.png]]
 +
[[File:Networking_rutos_manual_auto_reboot_periodic_reboot_configuration_v1.png]]
    
<table class="nd-mantable">
 
<table class="nd-mantable">
Line 96: Line 91:  
         <td>Enable</td>
 
         <td>Enable</td>
 
         <td>off | on; default: <b>off</b></td>
 
         <td>off | on; default: <b>off</b></td>
         <td>Turns Periodic Reboot on or off.</td>
+
         <td>Turns the rule on or off.</td>
     </tr></table>
+
     </tr>
 
+
    <tr>
 +
        <td>Action</td>
 +
        <td>Device reboot {{#ifeq:{{{mobile}}} | 1 | <nowiki>|</nowiki>Modem reboot}} | None |; default: <b> Device reboot</b></td>
 +
        <td>Action that will be executed at the specified time.</td>
 +
  </tr>
 +
    <tr>
 +
        <td>Week days</td>
 +
        <td>Monday| Tuesday| Wednesday| Thursday | Friday | Saturday | Sunday; default:  <b> Monday</b></td>
 +
        <td>Week day/s when actions will be executed.</td>
 +
  </tr>
 +
</table>
 
[[Category:{{{name}}} Services section]]
 
[[Category:{{{name}}} Services section]]
Anonymous user

Navigation menu