Jump to content

RUT850 WAN: Difference between revisions

1,411 bytes added ,  26 October 2018
Line 224: Line 224:
{| class="wikitable"
{| class="wikitable"
|+
|+
! style="width: 250px; background: black; color: white;" | Field name
! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | FIELD NAME
! style="width: 250px; background: black; color: white;" | Value
! style="width: 250px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | VALUE
! style="width: 1200px; background: black; color: white;" | Description
! style="width: 579px; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: left;" | DESCRIPTION
|-
|-
! style="text-align: left; vertical-align: top;" | Health monitor interval
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Health monitor interval
| style="text-align: left; vertical-align: top;" | Disable {{!}} 5 sec. {{!}} 10 sec. {{!}} 20 sec. {{!}} 30 sec. {{!}} 60 sec. {{!}} 120 sec. {{!}} ; Default: "10 sec."
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Disable {{!}} 5 sec. {{!}} 10 sec. {{!}} 20 sec. {{!}} 30 sec. {{!}} 60 sec. {{!}} 120 sec.; Default: '''10 sec.'''
| style="text-align: left; vertical-align: top;" | The interval at which health checks are performed
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The interval at which health checks are performed
|-
|-
! style="text-align: left; vertical-align: top;" | Health monitor ICMP host(s)
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Health monitor ICMP host(s)
| style="text-align: left; vertical-align: top;" | ip {{!}} hostname {{!}} 8.8.4.4 {{!}} Disable {{!}} DNS server(s) {{!}} WAN gateway {{!}} --custom--; Default: "8.8.4.4"
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | ip {{!}} hostname {{!}} 8.8.4.4 {{!}} Disable {{!}} DNS server(s) {{!}} WAN gateway {{!}} --custom--; Default: '''8.8.4.4'''
| style="text-align: left; vertical-align: top;" | Indicate where to send ping requests for a health check. As there is no definitive way to determine when the connection to internet is down for good, it is best to define a host whose availability is that of the internet as a whole (e.g., 8.8.8.8, 8.8.4.4)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Indicate where to send ping requests for a health check. As there is no definitive way to determine when the connection to internet is down for good, it is best to define a host whose availability is that of the internet as a whole (e.g., 8.8.8.8, 8.8.4.4)
|-
|-
! style="text-align: left; vertical-align: top;" | Health monitor ICMP timeout
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Health monitor ICMP timeout
| style="text-align: left; vertical-align: top;" | 1 sec. {{!}} 2 sec. {{!}} 3 sec. {{!}} 4 sec. {{!}} 5 sec. {{!}} 10 sec. {{!}}; Default: "3 sec."
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | 1 sec. {{!}} 2 sec. {{!}} 3 sec. {{!}} 4 sec. {{!}} 5 sec. {{!}} 10 sec.; Default: '''3 sec.'''
| style="text-align: left; vertical-align: top;" | The frequency at which ICMP requests are to be sent. It is advised to set a higher value if your connection has high latency or high jitter (latency spikes)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The frequency at which ICMP requests are to be sent. It is advised to set a higher value if your connection has high latency or high jitter (latency spikes)
|-
|-
! style="text-align: left; vertical-align: top;" | Attempts before failover
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Attempts before failover
| style="text-align: left; vertical-align: top;" | 1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20 {{!}}; Default: "3"
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | 1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; Default: '''3'''
| style="text-align: left; vertical-align: top;" | The number of failed ping attempts after which the connection is to be declared as “down”
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The number of failed ping attempts after which the connection is to be declared as “'''down'''”
|-
|-
! style="text-align: left; vertical-align: top;" | Attempts before recovery
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | Attempts before recovery
| style="text-align: left; vertical-align: top;" | 1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20 {{!}}; Default: "3"
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | 1 {{!}} 3 {{!}} 5 {{!}} 1 {{!}} 15 {{!}} 20; Default: '''3'''
| style="text-align: left; vertical-align: top;" | The number of successful ping attempts after which the connection is to be declared as “up”
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" | The number of successful ping attempts after which the connection is to be declared as “'''up'''”
|-
|-
|}
|}


The majority of the options consist of timing and other important parameters that help determine the health of your primary connection. Regular health checks are constantly performed in the form of ICMP packets (Pings) on your primary connection. When the connections state starts to change (READY->NOT READY and vice versa) a necessary amount of failed or passed health checks has to be reached before the state changes completely. This delay is instituted so as to mitigate “spikes” in connection availability, but it also extends the time before the backup link can be brought up or down.
The majority of the options consist of timing and other important parameters that help determine the health of your primary connection. Regular health checks are constantly performed in the form of ICMP packets (Pings) on your primary connection. When the connections state starts to change (READY->NOT READY and vice versa) a necessary amount of failed or passed health checks has to be reached before the state changes completely. This delay is instituted so as to mitigate “spikes” in connection availability, but it also extends the time before the backup link can be brought up or down.