Deploying an active-passive cluster
This topic includes the following information:
Overview
The following figure shows an active-passive deployment. When HA is enabled, the system sends heartbeat packets between the pair to monitor availability, and the primary node pushes its configuration to the secondary node.
When the primary node goes down, the secondary becomes the primary node. When the primary node comes back online, the system selects the primary based on the following criteria:
- Lowest device priority number (1 has greater priority than 2)
- Highest up-time value
- Note: Before you configure HA Settings, familiarize yourself on how FortiDDoS High Availability works.
Basic steps
To deploy an active-passive cluster:
- License all FortiDDoS-F appliances in the HA cluster, and register them, including FortiGuard services, with the Fortinet Technologies Inc. Technical Support website: https://support.fortinet.com/
- Physically link the FortiDDoS-F appliances that make up the HA cluster.
You must link at least one of their ports (for example, mgmt2 to mgmt2) for heartbeat and synchronization traffic between members of the cluster. You can do either of the following:
- Connect the two appliances directly with an Ethernet cable.
- Link the appliances through a switch. If connected through a switch, the HA interfaces must be reachable by Layer 2 multicast.
- Log into the secondary appliance as the admin user.
- Go to Global Settings > Settings and set the Power Failure Bypass Mode to Fail Open or Fail Closed, according to your preference on how to handle traffic when both nodes fail. If you use an external bypass unit, you configure Fail Closed.
- Complete the HA settings as described in Configuring HA settings.
Important: Set the Device Priority to a higher number than the primary appliance; for example, set Device Priority to 2.
- Log into the primary appliance as the admin user.
- Go to Global Settings > Settings and set the Power Failure Bypass Mode to Fail Closed.
- Complete the configuration for all features, as well as the HA configuration.
Important: Set the Device Priority to a lower number than the secondary appliance; for example, set Device Priority to 1.
Note: After you have saved the HA configuration changes, cluster members might join or rejoin the cluster. After you have saved configuration changes on the primary node, it automatically pushes its Global Settings and Protection Profiles configuration to the secondary node.