Trial licence limitations for sending logs from Fortigate to FortiAnalyzer?

Hi all
 
TL;DR
Does anyone know if the Fortigate trial licence limitations on encryption/decryption (which for example prevent the use of HTTPS) also prevent the SSL connections from Fortigate to FortiAnalyzer for the purposes of sending logs (via oftpd)?
 
I was trying to test sending logs from a Fortigate VM (firmware 6.4) to FortiAnalyzer VM (firmware 6.4) but I just get "No connection" and if you hover the cursor over that you get "Error occurred:{0}".  The goal is to test forwarding logs from the FortiAnalyzer to a third device but I can't get this far as the Fortigate won't send the logs to the FortiAnalyzer.  A reddit post (www.reddit.com/r/...er_trial_ssl_error_3/) suggested this is probably a trial licence limitation but it would be good to confirm it here if possible.
 
If anyone has found something similar please let me know.
 
Thanks
 
 
Testing steps:
I've made sure to check the compatibility matrix and the FGT and FAZ are compatible.  The Fortigate device is added as a device in the FortiAnalyzer.  I can test connectivity between the two using ping successfully.
I found various posts online with suggestions to make it work by allowing weaker encryption but none worked in this case e.g. (forum.fortinet.com/tm.aspx?m=140479)
FGT:

conf log fortianalyzer setting
set enc-algorithm low
set reliable enable

 
FAZ:

conf global setting
set enc-algorithm low

 
FGT:

exec log fortianalyzer test-connectivity
Failed to get FAZ's status.  Connection failed.  Connection refused(-1)
Failed to get FAZ's status.  SSL error. (-3).

 
FAZ - enabling debug logging for the oftpd app on the Fortianalyzer showed the following error:
(as in kb.fortinet.com/k...do?externalID=FD41272)
 

[oftpd_handle_session] oftp_recv_packet failed: SSL setup failure.
Client connection closed.  Reason 14(SSL setup failure)

 
Also I read the following, but it seems that these conditions were met during testing:

>6.2 FAZ will only process encrypted logs from Fortinet devices.

FAZ encryption level MUST be equal to or less than the FGT’s encryption level.

Trial licences are in use on both the Fortigate and the FortiAnalyzer.

Hi, thanks for the reply.
 
I used that setting on the Fortigate but unfortunately there was no change to the connection status.

Hi, thank you
 
I applied the settings on my 6.4 firmware FGT/FAZ devices as you detailed above but unfortunately they did not allow the two devices to communicate.  The GUI still showed 'No Connectivity' and on CLI the output from 'exec log fortianalyzer test-connectivity' was still:
Failed to get FAZ's status.  Connection failed.  Connection refused(-1)
Failed to get FAZ's status.  SSL error. (-3).
 
Following your post though I have downloaded a Fortigate and Fortianalyzer VM for firmware version 6.2.3, deployed these VMs, applied the Fortigate config log fortianalyzer settings and FortiAnalyzer system global settings as in your post, and I have been able to successfully send the logs from the Fortigate to the FortiAnalyzer.
 
Thanks again
 

Tried it on 6.4.4 - worked, tried 6.4.5 - didn't , go figure,  in the end asked for evaluation license and all worked.