Skip to main content
sahmed_FTNT
Staff & Editor
Staff & Editor
Aug 17, 2025 3:51 PM UTC

Technical Tip: Explaining HA sync error 'send() failed: 14(Bad address)'

Description This article describes the HA sync error captured during the HA sync issue.
Scope FortiGate.
Solution

During HA random disconnects, below error is observed:

 

<hasync:WARN> conn=0x10e812b0 send() failed: 14(Bad address). conn->dst=169.254.0.2

 

Verify the following settings:

 

  • The destination unit is receiving the HA traffic.
  • If there is a switch/Router in between, make sure Multicast traffic is allowed.
  • Verify that all remote devices in HA have valid HA interface IPs.
  • If HA devices are geographically located in distant locations, make sure all devices between them allow multicast traffic.
  • Unicast can be used as well if Multicast traffic is getting blocked or dropped between devices:

 

config system ha
    set hbdev port1 50
    set unicast-hb enable
    set unicast-hb-peerip 10.10.10.1
end

 

HA SYNC debug logs can be collected with the following commands:

 

diagnose debug enable

diagnose debug console timestamp enable

diagnose debug application hasync -1   

diagnose debug enable

diagnose debug disable <----- To stop the debug output.

 

Related document:

Unicast HA Heartbeat 

    Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024