peplink MediaFast 200, Руководство пользователя

Страница: 109 / 278

USER MANUAL
Peplink Balance Series
http://www.peplink.com -109 / 269 - Copyright © 2016 Peplink
Other Health Check Settings
Timeout
This setting specifies the timeout in seconds for ping/DNS lookup requests. The default
timeout is 5 seconds.
Health Check
Interval
This setting specifies the time interval in seconds between ping or DNS lookup requests.
The default health check interval is 5 seconds.
Health Check
Retries
This setting specifies the number of consecutive ping/DNS lookup timeouts after which the
Peplink Balance will treat the corresponding WAN connection as down. Default health
retries is set to 3. Using the default Health Retries setting of 3, the corresponding WAN
connection will be treated as down after three consecutive timeouts.
Recovery
Retries
This setting specifies the number of consecutive successful ping/DNS lookup responses
that must be received before the Peplink Balance treats a previously down WAN connection
as up again. By default, Recover Retries is set to 3. Using the default setting, a WAN
connection that is treated as down will be considered as up again upon receiving three
consecutive successful ping/DNS lookup responses.
Note
If a WAN connection goes down, all of the WAN connections not set with a Connection Type of Always-on will
also be brought up until any one of higher priority WAN connections is up and found to be healthy. This design
could increase overall network availability.
For example, if WAN1, WAN2, and WAN3 have connection types of Always-on, Backup Priority Group 1, and
Backup Priority Group 2, respectively, when WAN1 goes down, WAN2 and WAN3 will try to connect. If WAN3 is
connected first, WAN2 will still be kept connecting. If WAN2 is connected, WAN3 will disconnect or abort making
connection.
Automatic Public DNS Server Check on DNS Test Failure
When the health check method is set to DNS Lookup and checks fail, the Balance will automatically perform DNS
lookups on some public DNS servers. If the tests are successful, the WAN may not be down, but rather the target
DNS server malfunctioned. You will see the following warning message on the main page: