Technical Tip: Harelay process
Description | This article describes the role of the harelay process in a FortiGate FGCP cluster. |
Scope | FortiOS, FGCP. |
Solution | In an FGCP cluster, regardless of HA mode (Active-passive or Active-Active), the primary unit handles the local-out connection for all members. The main role of the harelay process is to provide services for the secondary unit(s) or vcluster. Harelay is used to relay the secondary member(s) daemons’ local-out sessions to the primary for routing.  To view the harelay statistics and connections, use the command 'diagnose test app harelay <#> ' with one of the following options:   To live-debug the harelay process, use the following debug commands:   Below is a sample debug output from a primary HA member where the administrator tried to log in from the primary into the secondary using 'execute ha manage <id> <admin_username>', but was unable to authenticate successfully due to a connection reset from the LDAPS server (as seen by 'errno=104').   Running debug commands on the harelay process at the same time as the main daemon that handles a given service can be helpful for a better understanding of inter-process communication and determining the root cause of the issue. For example:
HA relay debugging is important when troubleshooting remote authentication issues in HA environments where a user or administrator is able to log in to the primary FortiGate, but the same authentication does not work as expected on the secondary FortiGate. Another scenario is remote logging troubleshooting in an HA environment with VDOM partitioning enabled. For example, the secondary appliance may be acting as the primary for a specific VDOM but is not sending logs to a FortiAnalyzer while HA-Direct is disabled. For these scenarios, in addition to the normal process debug logs, HA relay debug logs should also be collected to provide the complete picture of the issue. Related documents: |
