Log Aggregation or Forwarding
FortiAnalyzer 5.4 cannot aggregate or forward logs to FortiAnalyzer 5.2 units. Please use the same FortiAnalyzer 5.4 version across all units.
Log Aggregation or Forwarding
FortiAnalyzer 5.4 cannot aggregate or forward logs to FortiAnalyzer 5.2 units. Please use the same FortiAnalyzer 5.4 version across all units.
Authentication Settings for Log Aggregation
FortiAnalyzer version 5.4.0 requires an administrator to be defined on the log aggregation server. For authentication to the log aggregation server, the administrator and its password must be set on all log aggregation forwarders.
SQL Storage Settings for Collector Mode
During upgrade to FortiAnalyzer 5.4.0, the SQL database in units running in Collector mode are disabled to optimize performance. You can re-enable the SQL storage settings to view logs and analytics with the following CLI command:
config system sql
set status local
end
If you are using a FortiAnalyzer in any capacity, go ahead and upgrade to 5.4. You will be thankful!
There are some things you need to take note of though before proceeding:
What’s new in FortiAnalyzer version 5.4.0
The following is a list of new features and enhancements in FortiAnalyzer version 5.4.0.
Introduction
So, if you are a Fortinet partner and you aren’t utilizing the Client Threat Assessment Program (CTAP) you are losing money all over the place. Here is a list of why:
That is pretty much it. If your sales people can’t give away free, no obligation necessary, assessments then you might have bigger issues at your office. I am currently ranked #1 in the South East (good ol southern boy after all) for these things and it is literally some of the easiest money I have ever made. Not to mention, it enables me to get my foot in the door at potential new clients without any real hassle or pain.
So, for those of you that utilize the FortiAnalyzer (in place of or in addition to Splunk, ArcSight etc) here is the “What’s New” for FortiAnalyzer 5.2. This is a copy of the Fortinet direct documentation for those that don’t have access to it.
FortiAnalyzer v5.2 includes the following new features and enhancements.
FortiAnalyzer v5.2.0 includes the following new features and enhancements.
So, I have run into some instances as of late where I was forced to use different revisions of the same hardware (two FortiGate’s that match model wise but are different hardware revisions, you know, cause Fortinet likes to evolve things half way through a lifecycle) in high available (HA) clusters. This is easily done with a few tweaks at the CLI level to enable it to properly function. I ignore 4.x version code because if you are still running that you are going to have a bad time in general.
execute ha ignore-hardware-revision enable
execute ha ignore-hardware-revision status
This will make the hardware work with ease in an HA cluster. Take note, you still need the same model, this just helps with variances in hardware revision between the two!
If you are in an environment where you want to make sure that the SSL VPN portal page does NOT show that is fine. You can use the following command to disable the SSL VPN Portal page of a FortiGate
Config VPN SSL Settings
Set sslvpn-enable disable
End
This is commonly used when you are wanting to accept only IPSec tunnels etc to your device. I usually just leave mine up and customize the page to look cool and creative but that is me!