Jump to content
  • EN

Template:Networking rutos manual failover: Difference between revisions

← Older editNewer edit →
VisualWikitext
No edit summary
No edit summary
(16 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Template: Networking_rutos_manual_fw_disclosure
{{Template: Networking_device_manual_fw_disclosure
| fw_version ={{Template: Networking_rutos_manual_latest_fw
| series = {{{series}}}
| name  = {{{name}}}
| fw_version ={{Template: Networking_device_manual_latest_fw
| series = {{{series}}}
  | name  = {{{name}}}
  | name  = {{{name}}}
| series = {{{series}}}
  }}
  }}
}}
}}
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} WAN (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>|}}
{{#ifeq: {{{series}}} | RUT9 |<br><i><b>Note</b>: <b>[[{{{name}}} WAN (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>|}}
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} WAN (legacy WebUI)|click here]]</b> for the old style WebUI (FW version {{Template: Networking_rutos_manual_latest_fw | series = RUT2XX}} and earlier) user manual page.</i>|}}
{{#ifeq: {{{series}}} | RUT2 |<br><i><b>Note</b>: <b>[[{{{name}}} WAN (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>|}}
__TOC__
__TOC__
==Summary==
==Summary==
Line 12: Line 14:
This chapter is an overview of the Failover, VRRP functions in {{{name}}} device.
This chapter is an overview of the Failover, VRRP functions in {{{name}}} device.


{{Template:Networking_rutos_manual_basic_advanced_webui_disclaimer
<u><b>Note:</b> Failover is additional software on some devices that can be installed from the <b>System → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>
| series = {{{series}}}
}}


{{#switch: {{{series}}}
===Failover===
  | #default =
  | TRB2 =  
<u><b>
 
Note:</b> Failover is additional software that can be installed from the <b>System → [[{{{name}}} Package Manager|Package Manager]]</b> page.</u>
}}
 
===Multiwan===
----
----
The <b>Failover</b> function allows you to backup your primary WAN connection in case it goes down.
The <b>Failover</b> function allows you to backup your primary WAN connection in case it goes down.


In order to set priorities, simply press left mouse click on the interface, then drag it to the 1st, 2nd or other position and then press Save & Apply.{{#ifeq:{{{mobile}}}|0|<br><br><b>Note:</b> You will not see any extra interfaces unless you have LAN ports configured as WAN.|}}
In order to set priorities, just change the interface metrics in the `Interfaces` section and then press Save & Apply.{{#ifeq:{{{mobile}}}|0|<br><br><b>Note:</b> You will not see any extra interfaces unless you have LAN ports configured as WAN.|}}


[[File:Networking_rutos_manual_failover_failover_interfaces_mobile_{{{mobile}}}_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_failover_failover_interfaces_mobile_{{{mobile}}}_{{{dualsim}}}_{{{dualmodem}}}_v1.png|border|class=tlt-border]]


You can drag & drop an interface in order to change its position on the list. Interfaces that are higher on the list have a higher priority than the ones that are lower, i.e., the device will always use the WAN interface with the highest priority as long as it is available. If it goes down, the device will start using the interface with the second highest priority and so on.
Interfaces with higher metrics on the list have a higher priority than the ones that are with lower metrics, i.e., the device will always use the WAN interface with the highest metric as long as it is available. If it goes down, the device will start using the interface with the second highest metric and so on.


Take note that changing an interface's position in the list here also changes its position in the following pages:
Take note that changing an interface's metrics in the list here also changes its position in the following pages:


<ul>
<ul>
    <li><i>Network → [[{{{name}}} Interfaces|Interfaces]]</i></li>
     <li><i>Network → [[{{{name}}} WAN|WAN]]</i></li>
     <li><i>Network → [[{{{name}}} WAN|WAN]]</i></li>
</ul>
</ul>


====Failover Interface Configuration====
===Load Balancing===
----
<b>Load Balancing</b> is a method of dividing traffic between multiple WAN interfaces. Load Balancing can be used to share the data load between different interfaces and increase the overall Internet speed for multiple users and connections. It is important to note that <u>Load Balancing does not increase speed for any single connection</u>. For example, if you're downloading a large file, using Load Balancing will not increase the speed of that download.
 
However, Load Balancing can be used to increase the speed of multiple connections. For example, when used in a WiFi network, Load Balancing would utilize the resources of multiple WAN interfaces to handle the many various requests of different clients.
 
Both Load Balancing and Failover cannot be used at the same time. If you wish to select Load Balancing, you can do that in the dropdown located under 'Settings' section:
 
[[File:Networking_rutos_manual_failover_load_balancing_select_v2.png|border|class=tlt-border]]
 
When Load Balancing is selected, you can <b>assign Weight values</b> to WAN interfaces. The  value represents a percentage of traffic load that will go through an interface. For example, if you set it up like this:
 
<table>
    <tr>
        <td style="text-align: left; width: 150px;"><ul><li><i>Wired WAN Weight:</i></li></ul></td>
        <td style="text-align: right; width: 30px;"><b>3</b></td>
    </tr>
</table>
<table>
    <tr>
        <td style="text-align: left; width: 150px;"><ul><li><i>{{{wan2}}} Weight:</i></li></ul></td>
        <td style="text-align: right; width: 30px;"><b>2</b></td>
    </tr>
</table>
 
then about 60 % (3/5) of traffic would go through the Wired WAN interface and about 40 % (2/5) would go through {{{wan2}}}. In this case if you played 100 different videos on the Internet, about 60 would be downloaded through Wired WAN and the other 40 would be downloaded via {{{wan2}}}.
 
===Interface===
----
----
A failover <b>Interface Configuration</b> page is used to configure how the device will determine whether an interface is online or offline. To enter an interface configuration page, click the 'Edit' button next to an interface.
A <b>Interface</b> page is used to configure how the device will determine whether an interface is online or offline. To enter an interface configuration page, click the 'Edit' button next to an interface.


[[File:Networking_rutos_manual_failover_interface_configuration_edit_button_v1.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_failover_interface_configuration_edit_button_v3.png|border|class=tlt-border]]


After this you should be redirected to the configuration page of that interface.
After this you should be redirected to the configuration page of that interface.


[[File:Networking_rutos_manual_failover_interface_configuration.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_failover_interface_configuration_v1.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 69: Line 87:
     <tr>
     <tr>
         <td>Flush connections on</td>
         <td>Flush connections on</td>
         <td>Connected | Disconnected: <b>none</b></td>
         <td>Connected {{!}} Disconnected {{!}} Interface up {{!}} Interface down: <b>none</b></td>
         <td>Flushes established connections after the selected scenario occurs to renew the priorities of configured interfaces.</td>
         <td>Flushes established connections after the selected scenario occurs to renew the priorities of configured interfaces.<ul>
            <li><b>Conected/Disconected</b> - used when internet connection appears/disappears</li>
            <li><b>Interface up/Interface down</b> - used when internet cable is plugged/unplugged</li></ul></td>
     </tr>
     </tr>
     <tr>
     <tr>
Line 104: Line 124:
</table>
</table>


===Load Balancing===
===Member===
----
----
<b>Load Balancing</b> is a method of dividing traffic between multiple WAN interfaces. Load Balancing can be used to share the data load between different interfaces and increase the overall Internet speed for multiple users and connections. It is important to note that <u>Load Balancing does not increase speed for any single connection</u>. For example, if you're downloading a large file, using Load Balancing will not increase the speed of that download.


However, Load Balancing can be used to increase the speed of multiple connections. For example, when used in a WiFi network, Load Balancing would utilize the resources of multiple WAN interfaces to handle the many various requests of different clients.
The <b>Member</b> page is for editing/creating a list of members and assigning interfaces to them. You can also set metrics for each user (this will be used for Failover) or weights for each member (this will be used for Load balancing).


Both Load Balancing and Failover cannot be used at the same time. If you wish to select Load Balancing, you can do that in the dropdown located in the top-right corner of the page:
[[File:Networking_rutos_manual_failover_load_balancing_rules_member.png|border|class=tlt-border]]


[[File:Networking_rutos_manual_failover_load_balancing_select.png|border|class=tlt-border]]
<table class="nd-mantable">
    <tr>
        <th>Field</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
    <tr>
        <td>Name</td>
        <td>string; default: <b></b></td>
        <td>Name of the member.</td>
    </tr>
    <tr>
        <td>Interface</td>
        <td>Name of the interface; default: <b></b></td>
        <td>List of available interfaces (depends on the device)</td>
    </tr>
    <tr>
        <td>Metric</td>
        <td>integer; default: <b>1</b></td>
        <td>Members within one policy with a lower metric have precedence over higher metric members. Members with the same metric within a policy will perform load balancing.</td>
    </tr>
    <tr>
        <td>Weight</td>
        <td>integer; default: <b>1</b></td>
        <td>The weight values represent a percentage of load that will go through an interface. The default value is 1, if unspecified.</td>
    </tr>
    <tr>
        <td>Actions</td>
        <td>-(interactive button); default: <b>Delete</b></td>
        <td>Removes a member.</td>
    </tr>
</table>


Below is an example of the Load Balancing page.
===Policy===
----
A <b>Policy</b> dictates what the the device should do when some network traffic matches the condition defined in a Failover/Load Balancing rule. There are two policies by default, one for Load Balancing (balance), the other for Failover (mwan). You may create custom policies that use different interfaces for Failover/Load Balancing scenarios.


[[File:Networking_rutos_manual_failover_load_balancing_interfaces.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_failover_load_balancing_rules_policies_v3.png|border|class=tlt-border]]


When Load Balancing is selected, you can <b>assign ratio values</b> to WAN interfaces. The ratio value represents a percentage of traffic load that will go through an interface. For example, if you set it up like this:
<table class="nd-mantable">
 
    <tr>
<table>
        <th>Field</th>
        <th>Value</th>
        <th>Description</th>
    </tr>
     <tr>
     <tr>
         <td style="text-align: left; width: 150px;"><li><i>Wired WAN Ratio:</i></li></td>
         <td>Member used</td>
         <td style="text-align: right; width: 30px;"><b>3</b></td>
        <td>list from members page; default: <b>none</b></td>
         <td>Members assigned to the policy.</td>
     </tr>
     </tr>
</table>
<table>
     <tr>
     <tr>
         <td style="text-align: left; width: 150px;"><li><i>{{{wan2}}} Ratio:</i></li></td>
         <td>Last Resort</td>
         <td style="text-align: right; width: 30px;"><b>2</b></td>
        <td>Unreachable {{!}} Blackhole {{!}} Default; default: <b>Unreachable</b></td>
         <td>Determine the fallback routing behaviour if all WAN members in the policy are down.
        <ul>Possible variants:
            <li><b>Unreachable:</b> Rejects all traffic.</li>
            <li><b>Blackhole:</b> Drops all traffic.</li>
            <li><b>Default:</b> Uses main routing table.</li></ul>
        </td>
     </tr>
     </tr>
</table>
</table>


then about 60 % (3/5) of traffic would go through the Wired WAN interface and about 40 % (2/5) would go through {{{wan2}}}. In this case if you played 100 different videos on the Internet, about 60 would be downloaded through Wired WAN and the other 40 would be downloaded via {{{wan2}}}.
===Rule===
 
===Rules===
----
----
A Load Balancing/Failover <b>Rule</b> is a set of conditions that define some type of network traffic. The traffic that matches the conditions set in the rule is handled in accordance to the specified <b>Policy</b>.
A Load Balancing/Failover <b>Rule</b> is a set of conditions that define some type of network traffic. The traffic that matches the conditions set in the rule is handled in accordance to the specified <b>Policy</b>.
Line 141: Line 199:
There is one default rule present on the device. You can add more rules with the 'Add' button or you can customize the existing rule by clicking the 'Edit' button next to it:
There is one default rule present on the device. You can add more rules with the 'Add' button or you can customize the existing rule by clicking the 'Edit' button next to it:


[[File:Networking_rutos_manual_failover_load_balancing_rules.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_failover_load_balancing_rules_v2.png|border|class=tlt-border]]


[[File:Networking_rutos_manual_failover_load_balancing_rule_configuration.png|border|class=tlt-border]]
[[File:Networking_rutos_manual_failover_load_balancing_rule_configuration_v2.png|border|class=tlt-border]]


<table class="nd-mantable">
<table class="nd-mantable">
Line 150: Line 208:
         <th>Value</th>
         <th>Value</th>
         <th>Description</th>
         <th>Description</th>
    </tr>
    <tr>
        <td>Name</td>
        <td>string; default: <b>default</b></td>
        <td>Name of the rule.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Protocol</td>
         <td>Protocol</td>
         <td>all | tcp | udp | icmp | esp; default: <b>all</b></td>
         <td>all {{!}} tcp {{!}} udp {{!}} icmp {{!}} esp; default: <b>all</b></td>
         <td>Protocol to match this rule.</td>
         <td>Protocol to match this rule.</td>
     </tr>
     </tr>
Line 168: Line 231:
     <tr>
     <tr>
         <td>Sticky</td>
         <td>Sticky</td>
         <td>off | <span style="color: #20C0D7;"><b>on</b></span>; default: <b>off</b></td>
         <td>off {{!}} <span style="color: #20C0D7;"><b>on</b></span>; default: <b>off</b></td>
         <td>If turned on, traffic from the same source IP address that previously matched this rule within the sticky timeout period will use the same WAN interface.</td>
         <td>If turned on, traffic from the same source IP address that previously matched this rule within the sticky timeout period will use the same WAN interface.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td><span style="color: #20C0D7;">Sticky timeout</span></td>
         <td><span style="color: #20C0D7;">Sticky timeout</span></td>
         <td>integer [1..1000000]; default: <b>600</b></td>
         <td>integer [1..1000000]; default: <b>none</b></td>
         <td>Timeout in seconds.</td>
         <td>Timeout in seconds.</td>
     </tr>
     </tr>
     <tr>
     <tr>
         <td>Policy assigned</td>
         <td>Policy assigned</td>
         <td>default (Load Balancing) | default (Failover) | Unreachable (Reject) | Blackhole (Drop) | Default (Use main routing table) | custom; default: <b>default (Failover)</b></td>
         <td>default (Load Balancing) {{!}} default (Failover) {{!}} Unreachable (Reject) {{!}} Blackhole (Drop) {{!}} Default (Use main routing table) {{!}} custom; default: <b>default (Failover)</b></td>
         <td>Selects the policy to apply to traffic that matches the conditions of this rule. You can create custom Load Balancing/Failover policies in the section below.</td>
         <td>Specifies the policy applied to matching traffic.</td>
     </tr>
     </tr>
</table>
</table>
====Policies====
----
A <b>Policy</b> dictates what the the device should do when some network traffic matches the condition defined in a Failover/Load Balancing rule. There are two policies by default, one for Load Balancing, the other for Failover. You may create custom policies that use different interfaces for Failover/Load Balancing scenarios.
[[File:Networking_rutos_manual_failover_load_balancing_rules_policies.png|border|class=tlt-border]]


{{Template:Networking_rutos_manual_vrrp
{{Template:Networking_rutos_manual_vrrp
Retrieved from "https://wiki.teltonika-networks.com/view/Template:Networking_rutos_manual_failover"