> Source: [sk93454](https://support.checkpoint.com/results/sk/sk93454) # sk93454 - Increasing ClusterXL dead timeout | Property | Value | |----------|-------| | Solution ID | sk93454 | | Date Created | 2013-07-08 | | Last Modified | 2026-10-12 | | Technical Level | General | | Products | Security Gateway | | Versions | R82, R81.20, R81.10 (EOS), R81 (EOS) | ## Solution ### Background The cluster "dead" interval determines how long a cluster member waits before considering a peer cluster member unresponsive. The default cluster dead interval is 3 seconds. This is also the recommended value. **Important Note:** Internal cluster timers use special time units - `HTU ("HA Time Unit")`, where `1 HTU = 100 milliseconds = 0.1 second`. If one cluster member does not receive CCP packets from the peer cluster member for more than 3 seconds, cluster failover occurs in the High Availability ClusterXL. The cluster member that does not receive the CCP packets from the peer cluster member, generates the following logs (in SmartConsole / SmartView / SmartView Tracker): *Example from a Standby cluster member* : `cluster_info: (ClusterXL) member 2 (10.0.66.2) is up.` `cluster_info: (ClusterXL) member 1 (10.0.66.1) is down.` `cluster_info: (ClusterXL) member 2 (10.0.66.2) is active.` `cluster_info: (ClusterXL) member 2 (10.0.66.2) is standby.` Cluster kernel debug on the cluster member that does not receive the CCP packets from the peer cluster member (`fw ctl debug -m cluster + stat`) shows these messages: *Example from a Standby cluster member* : `FW-1: check_other_machine_activity: ID 0 (state ACTIVE) is dying (since 2920.8 now 2921.5)` `FW-1: check_other_machine_activity: ID 0 (state ACTIVE) is dying (since 2920.8 now 2921.6)` `FW-1: check_other_machine_activity: ID 0 (state ACTIVE) is dying (since 2920.8 now 2921.7)` `FW-1: check_other_machine_activity: ID 0 (state ACTIVE) is dead (since 2920.8 now 2921.8)` ### Instructions to increase the ClusterXL dead timeout in R75.47, R77, and higher versions Set the value of kernel parameter `fwha_dead_timeout_multiplier` to **X** to increase the cluster dead timeout to **X** seconds. **Important Note:** In versions R75.47 and R77, changing the value of this kernel parameter (`fwha_dead_timeout_multiplier`) requires changing the value of the kernel parameter `fwha_if_connectivity_tolerance` respectively (refer to [sk62863](http://supportcontent.checkpoint.com/solutions?id=sk62863)). The recommended value **for both** kernel parameters is **30 (`HTU`)**. * To check the current value of the kernel parameter: `[Expert@HostName]# fw ctl get int fwha_dead_timeout_multiplier` * To set the desired value of the kernel parameter *on-the-fly* (does not survive reboot): `[Expert@HostName]# fw ctl set int fwha_dead_timeout_multiplier `*VALUE* * To set the desired value of the kernel parameter *permanently* (to survive reboot): Follow [sk26202 - Changing the kernel global parameters on Check Point Security Gateways](http://supportcontent.checkpoint.com/solutions?id=sk26202). ### Instructions to increase the ClusterXL dead timeout in versions R76, R75.46, and lower Show / Hide this section [Contact Check Point Support](http://www.checkpoint.com/services/contact/index.html) to get a Hotfix for this issue. A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix. For faster resolution and verification, please collect [CPinfo files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case. 1. Hotfix has to be installed on **each cluster member** . 2. Transfer the hotfix package to the cluster member (e.g., into `/some_path_to_fix/`). 3. Unpack the hotfix package: `[Expert@HostName]# cd /some_path_to_fix/` `[Expert@HostName]# tar -zxvf fw1_wrapper_`*HOTFIX_NAME*`.tgz` 4. Install the hotfix: `[Expert@HostName]# ./fw1_wrapper_`*HOTFIX_NAME* 5. Reboot the cluster member. 6. Set the value of kernel parameter `fwha_dead_timeout_multiplier` to **X** to increase the cluster dead timeout to **X** seconds. **Important Note:** In versions R76, R75.46, and lower, changing the value of this kernel parameter (`fwha_dead_timeout_multiplier`) requires changing the value of kernel parameter `fwha_if_connectivity_tolerance` respectively (refer to [sk62863](http://supportcontent.checkpoint.com/solutions?id=sk62863)). The recommended value **for both** kernel parameters is **3** (three). * To check the current value of the kernel parameter: `[Expert@HostName]# fw ctl get int fwha_dead_timeout_multiplier` `[Expert@HostName]# fw ctl get int fwha_if_connectivity_tolerance` * To set the desired value of the kernel parameter *on-the-fly* (does not survive reboot): `[Expert@HostName]# fw ctl set int fwha_dead_timeout_multiplier `*VALUE* `[Expert@HostName]# fw ctl set int fwha_if_connectivity_tolerance `*VALUE* * To set the desired value of the kernel parameter *permanently* (to survive reboot): Follow [sk26202 - Changing the kernel global parameters on Check Point Security Gateways](http://supportcontent.checkpoint.com/solutions?id=sk26202).
**Related Solutions:** * [sk43984 - Interface flapping when cluster interfaces are connected through several switches](http://supportcontent.checkpoint.com/solutions?id=sk43984) * [sk92723 - Cluster flapping prevention](http://supportcontent.checkpoint.com/solutions?id=sk92723) * [sk97415 - Increasing Virtual System dead timeout](http://supportcontent.checkpoint.com/solutions?id=sk97415) * [sk56202 - How to troubleshoot failovers in ClusterXL](http://supportcontent.checkpoint.com/solutions?id=sk56202) * [sk62570 - How to troubleshoot failovers in ClusterXL - Advanced Guide](http://supportcontent.checkpoint.com/solutions?id=sk62570) --- # Agent Instructions This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products. ## Navigating This Knowledge Base - **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt) - **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml) - **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}` - **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content