Support Center > Search Results > SecureKnowledge Details
High CPU usage when performing CRL check per Security Gateway Technical Level
Symptoms
  • High CPU usage when performing CRL check per Security Gateway.

  • User can access HTTPS sites.

Solution

In instances when the CRL size is large (above 10MB), performing the CRL check on every gateway can cause high CPU usage.

Use this clish command to bypass the CRL check on a specific Quantum Spark Security Gateway:

validate_crl_per_gw {on | off | show}

There is an option to configure bypass CRL in the Security Management Server, but it is a global parameter which affects all the gateways which are managed by the server.

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Give us Feedback
Please rate this document
[1=Worst,5=Best]
Comment