Failover
GUI Parameter (CLI Parameter)
Description
Failed Probe Count
(
strike_count
)
The number of successive failed heartbeats that must occur before a peer is
marked "down" (default:3). A heartbeat is considered to have failed
whenever the
Heartbeat Interval
has elapsed and no probe has been
received from a peer during that interval.
If the
Failed Probe Count
reaches its specified maximum value on the sub-
net, or if the
Failed Probe Count
reaches 1 on all subnets in a multi-subnet
network configuration, then a failover can occur. If the subnet
Failed Probe
count is 0, then the global
Failed Probe Count (strike_count)
is used
Retry Interval
(
retry_interval
)
Time in seconds (default:5) between checks for changes in Equalizer’s con-
figuration, for the purpose of determining whether a configuration transfer
to the remote peer is required.
The
Retry Interval
is also used when any failover operation other than
heartbeating fails. For example, if the system is rebooted and a VLAN health
check fails, we try again
Connect Timeout
(
conn_timeout
)
Time in seconds (default:1) to wait for a TCP connection to be established
between peers.
Receive Timeout
(
recv_timeout
)
Time in seconds (default:1) after a TCP connection is established, of how
long a peer waits for the other peer’s response.
Failover Occurs If...
l
The number of failed probes on any single subnet equals or exceeds the
Failed Probe Count
for
that subnet.
OR
l
The number of subnets with a
Failed Probe Count
greater than 0 equals or exceeds the global
Failed Probe Count.
Modifying Failover Timeouts in Production
When an failover pair is actively serving traffic, any changes to the global or subnet failover
parameters could result in a failover if you do not perform them in the correct manner.
Note
- These parameters are not currently synchronized.
To prevent a failover from occurring , proceed with the following to prevent an inadvertent
failover:
1. Disable failover on both units by disabling the failover flag on the local peers on both units;
first on the current primary unit and then the current backup. Refer to
on page 562 or
"Configuring Active/Passive Failover (GUI)"
for details.
2. Make the changes to failover timeouts required on both systems, in any order. Refer to
over Peer Probes and Timeouts"
on page 543 if necessary.
3. Re-enable failover by checking the failover flags on the on the primary Equalizer's local
peer and then on the backup.
544
Copyright © 2014 Coyote Point Systems, A Subsidiary of Fortinet, Inc.
Содержание Equalizer GX Series
Страница 18: ......
Страница 32: ...Overview 32 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Страница 42: ......
Страница 52: ......
Страница 64: ......
Страница 72: ......
Страница 76: ......
Страница 123: ...Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc All Rights Reserved 123 Equalizer Administration Guide ...
Страница 228: ......
Страница 238: ......
Страница 411: ...Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc All Rights Reserved 411 Equalizer Administration Guide ...
Страница 459: ...Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc All Rights Reserved 459 Equalizer Administration Guide ...
Страница 476: ......
Страница 492: ......
Страница 530: ......
Страница 614: ......
Страница 626: ......
Страница 638: ......
Страница 678: ......
Страница 732: ...Using SNMP Traps 732 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Страница 754: ......
Страница 790: ......
Страница 804: ......
Страница 842: ......
Страница 847: ...Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc All Rights Reserved 847 Equalizer Administration Guide ...
Страница 866: ......