User Manual

USER MANUAL
Peplink Balance Series
http://www.peplink.com - 61 / 182 - Copyright © 2011 Peplink
Health Check Method: DNS Lookup
DNS lookups will be issued to test the connectivity with target DNS servers. The connection will be
treated as up if DNS responses are received from either one or both of the servers, regardless of
whether the result was positive or negative.
Health Check DNS
Servers
This field allows you to specify two DNS hosts’ IP address with which connectivity
is to be tested via DNS Lookup.
If Use first two DNS servers as Health Check DNS Servers is checked, the first
two DNS servers will be the DNS lookup targets for checking a connection's
health. If the box is not checked, field Host 1 must be filled and field Host 2 is
optional.
If the box Include public DNS servers is selected and no response is received
from all specified DNS servers, DNS lookups will also be issued to some public
DNS servers. A WAN connection will be treated as down only if there is also no
response received from the public DNS servers.
Connections will be considered up if DNS responses are received from any one of
the health check DNS servers, regardless of a positive or negative result.
By default, the first two DNS servers of the WAN connection are used as the
Health Check DNS Servers.
Health Check Method: SmartCheck
SmartCheck applies only to the Peplink Balance 20/30/380 or above Mobile Internet connection. It
monitors the link status, and is optimized for mobile networks with high traffic latency.
Other Health Check Settings
Timeout
This setting specifies the timeout, in seconds, for ping/DNS lookup requests. Default
Timeout is set to 5 seconds.
Health Check
Interval
This setting specifies the time interval, in seconds, between ping or DNS lookup requests.
Default Health Check Interval is 5 seconds.
Health Check
Retries
This setting specifies the number of consecutive ping/DNS lookup timeouts after which
Peplink Balance is to treat the corresponding WAN connection as down. Default Health
Retries is set to 3.
For example, with the default Health Retries setting of 3, after consecutive 3 timeouts, the
corresponding WAN connection will be treated as down.