The High Availability > Advanced page provides the ability to fine-tune the High Availability configuration as well as synchronize setting and firmware among the High Availability devices. The High Availability > Advanced page is identical for both Active/Standby and Active/Active configurations. The Heartbeat Interval and Failover Trigger Level settings on the High Availability > Advanced page apply to both the SVRRP heartbeats (Active/Active Clustering heartbeat) and HA heartbeats.
Other settings on High Availability > Advanced page apply only to the HA pairs within the Cluster Nodes.
|
2
|
Navigate to High Availability > Advanced.
|
|
3
|
Optionally, adjust the Heartbeat Interval to control how often the units communicate. The default is 1000 milliseconds, the minimum value is 1000 milliseconds, and the maximum value is 300000. The recommended value is 1000 milliseconds, but you can use higher values if your deployment handles a lot of network traffic as lower values may cause unnecessary failovers, especially when he firewall is under a heavy load.
|
This setting applies to all units in the Active/Active cluster.
|
4
|
Set the Failover Trigger Level (missed heartbeats) to the number of heartbeats that can be missed before failing over. The default is 5, the minimum is 4, and the maximum is 99. If the Failover Trigger Level is set to 5 and the Heartbeat Interval is set to 1000 milliseconds, it takes 5 seconds without a heartbeat before a failover is triggered.
|
This setting applies to all units in the Active/Active cluster.
|
5
|
Set the Probe Interval (seconds) to the interval in seconds between probes sent to specified IP addresses to monitor that the network critical path is still reachable. This is used in logical monitoring for the local HA pair. SonicWALL recommends that you set the interval for at least 5 seconds. The default is 20 seconds, and the maximum is 255 seconds. You can set the logical/probe IP address(es) on the High Availability > Monitoring page. See High Availability > Monitoring .
|
|
6
|
Set the Probe Count to the number of consecutive probes before SonicOS concludes that the network critical path is unavailable or the probe target is unreachable. This option is used in logical monitoring for the local HA pair. The default is 3, and the minimum is 3, and the maximum is 10.
|
|
7
|
Set the Election Delay Time (seconds) to the number of seconds allowed for internal processing between the two units in the local HA pair before one of them takes the Primary role. The timer can be used to specify an amount of time the firewall waits to consider an interface up and stable, which is useful when dealing with switch ports that have a spanning-tree delay set. The default is 3 seconds, the minimum is 3 seconds, and the maximum is 255 seconds.
|
|
8
|
Set the Dynamic Route Hold-Down Time (seconds) to the number of seconds the newly-active appliance keeps the dynamic routes it had previously learned in its route table. During this time, the newly-active appliance relearns the dynamic routes in the network. When the Dynamic Route Hold-Down Time duration expires, SonicOS deletes the old routes and implements the new routes it has learned from RIP or OSPF. The default value is 45 seconds, the minimum is 0 seconds, and the maximum is 1200 seconds (20 minutes). In large or complex networks, a larger value may improve network stability during a failover.
|
|
NOTE: The Dynamic Route Hold-Down Time setting is displayed only when the Advanced Routing option is selected on the Network > Routing page.
|
|
9
|
If you want failover to occur only when ALL aggregate links are down, select the Active/Standby Failover only when ALL aggregate links are down checkbox. This option is not selected by default.
|
|
10
|
Select the Include Certificates/Keys checkbox to have the appliances synchronize all certificates and keys within the HA pair. This option is selected by default.
|
|
11
|
After configuring the High Availability settings on the primary firewall, click the Synchronize Settings button. This action synchronizes the SonicOS preference settings between your primary and secondary HA units.
|
|
12
|
If you previously uploaded new firmware to your primary unity while the secondary unit was offline, and it is now online and ready to upgrade to new firmware, click the Synchronize Firmware button. This action synchronizes the firmware version between your primary and secondary HA units.
|
|
13
|
Optionally, click the Force Active/Standby Failover button. This action attempts an Active/Standby HA failover to the secondary unit. Use this action to test the HA failover functionality is working properly.
|
|
14
|
When finished with all High Availability configuration, click Accept. All settings are synchronized to the other units in the cluster.
|
