Failover
Synchronization Notes
1. Failover does not require the same set of VLANs on all Peers. Therefore, a failover group
associated with a VLAN existing on one Peer cannot be configured into failover with other
peers that do not have the same VLAN configured. All instances of a VLAN mismatch will be
logged.
2. A failover group associated with a subnet existing on one peer cannot be configured into fail-
over with other peers that do not have the same subnet configured. All instances of a subnet
mismatch will be logged.
3. The following subnet parameters must be the same for each peer. They will be synchronized
amongst Peers just as the non-network parameters are:
l
heartbeat interval
l
failed heartbeat
(strike) count
l
floating IP address
4. The following subnet parameters and flags do not need to be the same for each peer. This
will not affect failover operation, however, they will be checked and a warning message will
be logged.
l
services
l
outbound NAT
l
heartbeat
l
command
5. The following VLAN parameters need not be the same for each peer. They will not be
checked and therefore no error is logged if they do not match:
l
MTU
l
interface instances
l
aggregated interfaces
6. The following peer parameters must be the same on all peers configured into failover.
However, they will be synchronized amongst the Peers just as the non-network parameters
are:
l
receive timeout
l
connect timeout
l
heartbeat interval
l
retry interval
l
strike count
7. SNI objects created for HTTPS clusters are part of failover \synchronization. SNI objects
"Server Name Indication (SNI)"
on page 363) have a name; they contain a server name in FQDN
syntax and a pointer to a certificate (the name of the certificate in the global certificate
store).
8. Restore and Failover synchronization:
o
Assume two units (A, B) are in failover.
o
Unit A is taken offline.
o
A new unit (C) is brought online to replace unit A, and a backup archive from unit A is
restored onto unit C.
o
Unit C is then powered off, and unit A is brought back online. Iif unit A was only dis-
connected from the network and not shut down when it was taken off line, a reboot of
unit A is required in order to synchronize failover between the two units properly.
542
Copyright © 2014 Coyote Point Systems, A Subsidiary of Fortinet, Inc.
Summary of Contents for Equalizer GX Series
Page 18: ......
Page 32: ...Overview 32 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 42: ......
Page 52: ......
Page 64: ......
Page 72: ......
Page 76: ......
Page 228: ......
Page 238: ......
Page 476: ......
Page 492: ......
Page 530: ......
Page 614: ......
Page 626: ......
Page 638: ......
Page 678: ......
Page 732: ...Using SNMP Traps 732 Copyright 2014 Coyote Point Systems A Subsidiary of Fortinet Inc ...
Page 754: ......
Page 790: ......
Page 804: ......
Page 842: ......
Page 866: ......