Troubleshooting Tip: How to troubleshoot the connection between FortiMail and FortiAnalyzer Cloud

[gcortes1]

Description	This article describes how to identify authentication and communication issues between FortiMail and FortiAnalyzer Cloud.
Scope	FortiMail all versions, FortiAnalyzer Cloud.
Solution	Check the server status and the cloud account login status with the instruction: execute log fortianalyzer-cloud test-connectivity Case 1. Correct Communication: If the output of the instruction is similar to the following, it means the communication is correct: execute log fortianalyzer-cloud test-connectivity FortiAnalyzer Host Name: FAZVMXX-XXX-CLOUD FortiAnalyzer Adom Name: root FortiMail Device ID: FEVXXXX000XXXXX Registration: registered Connection: allow Adom Disk Space (Used/Allocated): 130327260926B/473520144384B Analytics Usage (Used/Allocated): 48081635402B/189408057753B Analytics Usage (Data Policy Days Actual/Configured): 60/60 Days Archive Usage (Used/Allocated): 82245625524B/284112086631B Archive Usage (Data Policy Days Actual/Configured): 365/365 Days Log: Tx & Rx (XXXXXX logs received since HH:MM:SS MM/DD/YY) Case 2. Authentication Problems: If the output of the instruction is similar to the following: FortiAnalyzer Host Name: FAZVMXX-XXX-CLOUD FortiAnalyzer Adom Name: root FortiMail Device ID: FEVXXXX000XXXXX Registration: registered Connection: allow Adom Disk Space (Used/Allocated): 130327260926B/473520144384B Analytics Usage (Used/Allocated): 48081635402B/189408057753B Analytics Usage (Data Policy Days Actual/Configured): 60/60 Days Archive Usage (Used/Allocated): 82245625524B/284112086631B Archive Usage (Data Policy Days Actual/Configured): 365/365 Days Log: Tx & Rx (log not received) If there are similar errors to the following in Monitor -> Log -> System Event, it will be necessary to verify that the account is configured for FortiCloud on the main dashboard, and it will also be necessary to ensure that there is access to FortiCloud via port 443. system OFTPS connection failed: dstip=XX-XXX-X.fortianalyzer.forticloud.com dstport=514 action=connect status=failed, reason=login failed: -20 Case 3. Communication Problem: If the output of the instruction is similar to the following: FortiAnalyzer Host Name: FAZVMXX-XXX-CLOUD FortiAnalyzer Adom Name: root FortiMail Device ID: FEVXXXX000XXXXX Registration: registered Connection: allow Adom Disk Space (Used/Allocated): 130327260926B/473520144384B Analytics Usage (Used/Allocated): 48081635402B/189408057753B Analytics Usage (Data Policy Days Actual/Configured): 60/60 Days Archive Usage (Used/Allocated): 82245625524B/284112086631B Archive Usage (Data Policy Days Actual/Configured): 365/365 Days Log: Tx & Rx (log not received) And if there are similar errors to the following in Monitor -> Log -> System Event: system OFTPS connection failed: dstip=XX-XXX-X.fortianalyzer.forticloud.com dstport=514 action=connect status=failed, reason=No route to host Check to ensure FortiMail can communicate with FortiAnalyzer Cloud over TCP port 514: execute telnettest XX-XXX-X.fortianalyzer.forticloud.com:514