Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why does deployment to FWSM fail when the configuration contains a large number of ACLs?

April 26, 2017ACLs configuration deployment fail fwsm large

0

Posted

Why does deployment to FWSM fail when the configuration contains a large number of ACLs?

1 Answer

0

Posted

A. This could occur because the CPU utilization is high during ACL compilation. To resolve this, reconfigure the CPU utilization threshold limit by doing the following: 1. On the Security Manager server, open the DCS.properties file in the \CSCOpx\MDC\athena\config folder in the installation directory (usually C:\Program Files). 2. Locate the DCS.FWSM.checkThreshold=False property. 3. Change the value to true: DCS.FWSM.checkThreshold=True. 4. Restart the CiscoWorks Daemon Manager. 5. Deploy the configuration to the device again. After you set the value to true, discovery and deployment checks the CPU utilization and generates error messages if the CPU utilization is not within the configured value set in the DCS.FWSM.minThresholdLimit property. The default value is 85.