8,290
edits
Changes
Template:Networking tswos manual maintenance (view source)
Revision as of 15:29, 12 October 2023
, 15:29, 12 October 2023Created page with "{{Template: Networking_rutos_manual_fw_disclosure | fw_version ={{Template: Networking_rutos_manual_latest_fw | series = {{{series}}} | name = {{{name}}} }} }} ==Summary..."
{{Template: Networking_rutos_manual_fw_disclosure
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
}}
}}
==Summary==
This page is an overview of the <b>Maintenance</b> section of {{{name}}} devices.
==Auto Reboot==
===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.
===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 Ping/Wget Reboot section contains one pre-configured rule by default:
[[File:Networking_tswos_manual_maintenance_auto_reboot_ping_wget_reboot_settings.png|border|class=tlt-border]]
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_tswos_manual_maintenance_auto_reboot_ping_wget_reboot_settings_configuration.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Turns the rule on or off.</td>
</tr>
<tr>
<td>Type</td>
<td>Ping {{!}} Wget; default: <b>Ping</b></td>
<td>Method used for health checking.
<ul>
<li><b>Ping</b> - sends ICMP requests to the specified host.</li>
<li><b>Wget</b> - retrieves the contents of the specified web server.</li>
</ul>
</td>
</tr>
<tr>
<td>Action if no echo is received</td>
<td>Device 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. If <b>None</b> is selected, only a message to syslog will be logged.</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>
</tr>
<tr>
<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>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>
</tr>
<tr>
<td>Packet size</td>
<td>integer [0..1000]; default: <b>56</b></td>
<td>ICMP packet size in bytes.</td>
</tr>
<tr>
<td>Interface</td>
<td>Automatically selected; 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>
<td>IP type</td>
<td>IPv4 {{!}} IPv6; default: <b>IPv4</b></td>
<td>IP address version of the host to ping.</td>
</tr>
<tr>
<td>Host to ping</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>
</tr>
</table>
===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.
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_tswos_manual_maintenance_auto_reboot_reboot_scheduler.png|border|class=tlt-border]]
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:Networking_tswos_manual_maintenance_auto_reboot_reboot_scheduler_modify_reboot_instance.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Turns the rule on or off.</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>
<td>Day time</td>
<td>time [00:00..23:59]; default: <b>none</b></td>
<td>Exact time of day the reboot will take place</td>
</tr>
<tr>
<td>Force last day</td>
<td>off {{!}} on; default: <b>off</b></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>
[[Category:{{{name}}} System section]]
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| series = {{{series}}}
| name = {{{name}}}
}}
}}
==Summary==
This page is an overview of the <b>Maintenance</b> section of {{{name}}} devices.
==Auto Reboot==
===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.
===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 Ping/Wget Reboot section contains one pre-configured rule by default:
[[File:Networking_tswos_manual_maintenance_auto_reboot_ping_wget_reboot_settings.png|border|class=tlt-border]]
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_tswos_manual_maintenance_auto_reboot_ping_wget_reboot_settings_configuration.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Turns the rule on or off.</td>
</tr>
<tr>
<td>Type</td>
<td>Ping {{!}} Wget; default: <b>Ping</b></td>
<td>Method used for health checking.
<ul>
<li><b>Ping</b> - sends ICMP requests to the specified host.</li>
<li><b>Wget</b> - retrieves the contents of the specified web server.</li>
</ul>
</td>
</tr>
<tr>
<td>Action if no echo is received</td>
<td>Device 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. If <b>None</b> is selected, only a message to syslog will be logged.</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>
</tr>
<tr>
<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>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>
</tr>
<tr>
<td>Packet size</td>
<td>integer [0..1000]; default: <b>56</b></td>
<td>ICMP packet size in bytes.</td>
</tr>
<tr>
<td>Interface</td>
<td>Automatically selected; 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>
<td>IP type</td>
<td>IPv4 {{!}} IPv6; default: <b>IPv4</b></td>
<td>IP address version of the host to ping.</td>
</tr>
<tr>
<td>Host to ping</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>
</tr>
</table>
===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.
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_tswos_manual_maintenance_auto_reboot_reboot_scheduler.png|border|class=tlt-border]]
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:Networking_tswos_manual_maintenance_auto_reboot_reboot_scheduler_modify_reboot_instance.png|border|class=tlt-border]]
<table class="nd-mantable">
<tr>
<th>Field</th>
<th>Value</th>
<th>Description</th>
</tr>
<tr>
<td>Enable</td>
<td>off {{!}} on; default: <b>off</b></td>
<td>Turns the rule on or off.</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>
<td>Day time</td>
<td>time [00:00..23:59]; default: <b>none</b></td>
<td>Exact time of day the reboot will take place</td>
</tr>
<tr>
<td>Force last day</td>
<td>off {{!}} on; default: <b>off</b></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>
[[Category:{{{name}}} System section]]
