Technical Tip: Increase the threads (more cpu power) used for L2 polling in FortiNAC

[ebujedo]

Description	This article explains the issue of large infrastructure and where L2 polling takes too long, FortiNAC can be tuned for using more threads for that process.
Scope	FortiNAC all versions
Solution	The file bridgeManager.properties controls the number of threads used for Poll and Traps By default: com.bsc.plugin.bridge.BridgeManager.pollThreads=2 Trap Threads: com.bsc.plugin.bridge.BridgeManager.threads=6 Trap threads are used for trap processing, but are also used for polling, if they are available. This is also the case for poll threads. Statically set pollThreads to 18 or 24, which will allow for 24 or more (if trap threads are free) L2 polls to be processed in parallel. This requires a restart of FortiNAC to take effect. If set in the property file, it does not persist through upgrades. To make it persist, set the value in the .masterPropertyFile. To properly apply the changes to persist: Modify file: /bsc/campusMgr/master_loader/.masterPropertyFile With updates for trap 'threads' and 'pollThreads' quantities: FILE_NAME=./properties_plugin/bridgeManager.properties { com.bsc.plugin.bridge.BridgeManager.threads=12 com.bsc.plugin.bridge.BridgeManager.pollThreads=12 } Restart FortiNAC for updates to be applied. During FortiNAC startup output.master log file will document applied changes.