
Failover
For "N+1" failover:
1. Each peer should have the A/A (active-active) flag enabled
2. The modes displayed will be different for active-active, as explained below.
As cables are removed, re-attached, and systems rebooted, the F/O Mode displayed for each peer will move
through the following failover mode variations:
Primary
The peer has instantiated allcluster IP addresses, and allsubnet failover IP addresses.
Heartbeating is working properly.
Mixed
The peer has instantiated some of the cluster IP addresses in the configuration and is
available as a Backup for others. It has also instantiated allsubnet failover IP
addresses for the subnets required by the instantiated clusters.
Backup
The peer has not instantiated any clusters and is available as a Backup. Heartbeating
is working properly.
Isolated
The peer appearsto be up but we cannot heartbeat it. Thisusuallyoccurs when a peer
is rebooted and has not yet fully assumed a failover mode, or when there is a
connectivity issue on a heartbeating subnet.
Unknown
The peer status is unknown. No heartbeats from thissystem have been received. This
usuallyoccurs when first configuring failover, before allpeers have started
heartbeating one another, or when rebooting a peer.
Standalone
The peer isnot participating in failover. It will instantiate allcluster IP addresses and all
subnet failover IP addresses that exist in the configuration file.
For detailed output regarding hearbeat status between this peer and other peers in the failover set of Equalizers,
specify the name of a remote peer:
464
Copyright © 2013 Coyote Point Systems. A subsidiary of Fortinet, Inc.
Comentários a estes Manuais