Troubleshooting Tip: FortiGate HA devices are unable to connect to FortiAnalyzer due to special characters
| Description | This article describes the issue of FortiGate devices not connecting to the FortiAnalyzer or the FortiAnalyzer cloud and provides a step-by-step solution to resolve it. The user may encounter this issue when configuring FortiGate devices for logging to FortiAnalyzer. |
| Scope | FortiGate, FortiAnalyzer. v7.2.x, v7.4.x. |
| Solution | To resolve the issue of FortiGate devices not connecting to FortiAnalyzer or FortiAnalyzer Cloud, follow these steps:
Check the HA group name configuration on the FortiGate devices. The HA group name should not contain any characters such as '<>()#\"'.' due to FortiAnalyzer limitations.
Refer to the config below :
config system ha set group-name HAGroup-123 <------ No special characters. end
Run the FortiAnalyzer debug commands below and check the error:
diagnose debug app oftpd 8 x.x.x.x <----- IP address of the FortiGate. diagnose debug timestamp enable
2025-04-18 05:42:54 [firmware_version_info_parse:323 ] os_type(0) os_ver(7) mr(2) patch(8) build(1639) On FortiGate, run the following debug commands and check the error:
diagnose debug application fgtlogd 7 diagnose debug timestamp enable
<2151> __handle_logs()-1129: 2184 bytes received
Disable the debug commands using the following set of commands:
diagnose debug disable
Workaround: Add the device manually to the FortiAnalyzer.
For more information on configuring FortiGate devices for logging to FortiAnalyzer, refer to the Fortinet Support Portal. Technical Tip: How to enable FortiAnalyzer Logging on FortiGate using FortiManager |
