Support Center > Search Results > SecureKnowledge Details
FWM slow performance from SmartProvisioning or LSM Technical Level
Symptoms
  • During slow FWM performance, the $FWDIR/log/fwm.elg file on CMA level/ Security Management shows:
    FWM mainloop wasn't available for XX seconds. This may cause UI / Server slow down
    [FWM PID]@HOSTNAME [DATE TIME] Time consuming warning: fwm command 
    [provisioning_update_dvc_times] took X sec
    
  • fwm.elg may also shows:
    libprovision_db.so(_ZN9PrvsDbApi7CDbTask17get_robo_sic_nameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_+0x5d) [0xe37d7d4d]
    libprovision_mgmt.so(_ZN15ProvisioningAPI18deleteRoboHashDataERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES7_+0x73) [0xe3a2f3f3]
    libprovision_fwm_handlers.so(_ZN15PrvnFwmCommands23CNetworkObjectsObserver9OnEventCBEPv+0x14b) [0xe38d716b]
    
  • Potentially, "Failed to connect to the Server" error is presented while trying to connect the CMA with SmartConsole.
Cause

SmartProvisioning commands are being called by LSM Add-ons, which are not supported in R80.10. In R80.20 and higher, an environment variable was added to improve the performance.

These calls consume CPU cycles and slow down the FWM process in general, triggering problems with regular FWM operation. The problem may occur when modifying or deleting objects in bulk.



Solution
Note: To view this solution you need to Sign In .