How do I resolve a heartbeat disconnection in an HA cluster?
最後修訂日期:
2025-07-24
Applicable Products
- QuTS hero h5.3.0 or later
- High Availability Manager
Scenario
When High Availability Manager detects a heartbeat connection failure in your high-availability (HA) cluster, it may display an error message such as "An abnormality occurred in the heartbeat connection." When this happens, the failover mechanism is suspended. In such cases, you should immediately check the connection between the two nodes.
Solution
- Check the physical heartbeat connection.
- Verify the network cable status: Ensure the network cable used for the heartbeat connection is securely connected and not loose, damaged, or oxidized.
- Use a direct connection: Make sure the heartbeat cable directly connects the two nodes without passing through any network devices (such as switches).
- Check the passive node status.
- Power status: Ensure the passive node is powered on and operating normally. A powered-off or unresponsive node will result in a heartbeat disconnection.
- Network interface configuration: Verify that the network interface used for the heartbeat connection is configured correctly (e.g., no DHCP issues or IP conflicts).
- Restart the passive node: Restarting the passive node may help clear abnormal statuses.
- Review system logs for further diagnosis.
- Open QuLog Center and review system logs related to high availability to identify the root cause of the heartbeat connection issue.
If you have tried all the above steps and still cannot resolve the issue, contact QNAP Customer Service for further assistance.