#4 - How to Enable Fortinet Security Fabric in PNETLab / EVE-NG with FortiGate and FortiAnalyzer Without Integration Issues

If you are trying to enable Fortinet Security Fabric in PNETLab / EVE-NG, this guide shows the minimum setup required with 2 FortiGates and 1 FortiAnalyzer, along with the adjustments that help avoid bugs, validation errors, and integration issues.

In lab environments, Security Fabric does not always work properly with the default configuration. Depending on the image versions and the behavior of the virtualized environment, communication between FortiGate and FortiAnalyzer may require manual adjustments before the integration can be completed successfully.

In this tutorial, you will see the minimum topology required and the specific configuration changes needed to make Security Fabric work properly in PNETLab / EVE-NG.

Minimum Topology

To make this setup work properly, use at least:

• 2 FortiGates
• 1 FortiAnalyzer

The idea is to have:

• one FortiGate acting as the Security Fabric root;
• a second FortiGate joining the Fabric;
• one FortiAnalyzer integrated into the environment.

This is the minimum structure required to validate the integration more completely in a lab scenario.

Step 1: Adjust the FortiAnalyzer

On the FortiAnalyzer, apply the following configuration:

config system global
    set enc-algorithm low
    set oftp-ssl-protocol tlsv1.0
end

This adjustment makes communication more permissive in the lab and helps prevent compatibility issues in PNETLab / EVE-NG.

Step 2: Adjust the FortiGate Integration with FortiAnalyzer

On the FortiGate Root, apply the following configuration:

config log fortianalyzer setting
    set reliable enable
    set enc-algorithm low
    set oftp-ssl-protocol tlsv1.0
    set serial FAZ-XXXXXXXXXXX
end

At this stage, the configuration is focused on stabilizing communication between FortiGate and FortiAnalyzer inside the lab environment.

The most important part here is the set serial command. In some PNETLab / EVE-NG scenarios, you may need to manually enter the FortiAnalyzer serial number so the integration can complete successfully.

Another point worth noting is the set reliable option. In the setup used for this guide, reliable enable was kept in place, and the FortiAnalyzer serial number was manually configured to make the integration work consistently.

However, in some lab environments, using reliable disable may allow the FortiGate to discover the FortiAnalyzer without requiring the serial number to be set manually. This behavior is not always consistent and may vary depending on the FortiGate version, FortiAnalyzer version, and the specific behavior of the PNETLab / EVE-NG images.

For that reason, the most stable approach in this tutorial is to keep reliable enable and manually define the FortiAnalyzer serial number when needed.

If you want, I can now revise the full English article with this paragraph already integrated.

Important Note

Depending on the FortiGate version, FortiAnalyzer version, and the behavior of the PNETLab / EVE-NG environment, the discovery and validation process may behave differently.

In the scenario shown here, the most stable approach was to adjust the encryption and protocol parameters and manually define the FortiAnalyzer serial number on the FortiGate.

So, if the integration does not work as expected with the default settings, this is one of the first areas you should verify.

Conclusion

Enabling Fortinet Security Fabric in PNETLab / EVE-NG may require a few adjustments that would not normally be necessary in a standard environment. In lab scenarios, the key point is to ensure compatibility between FortiGate and FortiAnalyzer so the integration can be completed without errors.

With 2 FortiGates and 1 FortiAnalyzer, you already have a functional minimum topology for validating Security Fabric in the lab. In the scenario covered here, the changes on both the FortiAnalyzer and the FortiGate, along with the manual definition of the FortiAnalyzer serial number, were the key factors that prevented integration issues and made the setup work properly.