|
To optimize memory usage for FortiGate models with 2 GB RAM or less starting from version 7.4.4 and 7.6.0, FortiOS no longer supports proxy-related features.
This led to some wrong expectations that the WAD process also get removed on FortiGate models with 2 GB RAM, however this is not the case as the WAD Mandatory process (i.e. manager, config-notify) and wadBasic mandatory (i.e. single worker, informer, user-info, dev-vuln, user-info-history, debug) will still spawn on this model.
To verify, run the commands:
diagnose debug enable
diagnose test application wad 1000
Process [0]: WAD manager type=manager(0) pid=179 diagnosis=yes.
Process [1]: type=worker(2) index=0 pid=300 state=running
diagnosis=no debug=enable valgrind=supported/disabled
Process [2]: type=informer(4) index=0 pid=295 state=running
diagnosis=no debug=enable valgrind=unsupported/disabled
Process [3]: type=user-info(5) index=0 pid=296 state=running
diagnosis=no debug=enable valgrind=supported/disabled
Process [4]: type=dev-vuln(6) index=0 pid=297 state=running
diagnosis=no debug=enable valgrind=supported/disabled
Process [5]: type=debug(13) index=0 pid=298 state=running
diagnosis=no debug=enable valgrind=unsupported/disabled
Process [6]: type=config-notify(14) index=0 pid=299 state=running
diagnosis=no debug=enable valgrind=unsupported/disabled
Note:
In v7.6.3, the physical FortiGate devices with 2 GB of RAM experienced memory usage optimizations to ensure smooth performance and reliability by adjusting memory used by some GUI features. This change prioritizes device stability and reduces the risk of performance issues.
Such features are the removal of CLI commands for caching REST API results on FortiGate, the removal of physical-/logical- -topology and security rating pages in the security fabric section, and the removal of visibility in security fabric topologies from upstream fabric devices. For more information check this Optimizations for physical FortiGate devices with 2 GB RAM 7.6.3
|
