The troubleshooting and resolution of high CPU utilization issues on the ProxySG or Advanced Secure Gateway (ASG).
This article provides the steps to troubleshoot utilization issues, with links to supporting procedures and common causes of high CPU utilization on the ProxySG or ASG.
To help identify the cause of the high CPU utilization, consider the following questions while progressing through the troubleshooting steps:
The first step to troubleshoot the issue is to enable the CPU monitor on the ProxySG or ASG and to activate snapshots every five minutes. This step helps determine which service or services generate the high utilization. The CPU monitor can be accessed at:
For more information on how to set up the CPU monitor, see: How to enable the CPU Monitor on the ProxySG
NOTE: Once you have finished taking snapshots, be sure to turn the CPU monitor off as it places additional CPU load on the system.
After CPU Monitor identifies the source of the high CPU utilization, use the following articles to review the most common causes and resolutions for high CPU utilization for that service:
|Object Store||ProxySG CPU monitor showing high CPU in Object Store|
|HTTP and FTP||ProxySG CPU monitor showing high CPU in HTTP|
|Miscellaneous||ProxySG CPU monitor showing high CPU in Miscellaneous|
|TCP/IP||ProxySG CPU monitor showing high CPU in TCP/IP|
|Policy evaluation - HTTP||ProxySG CPU monitor showing high CPU in Policy|
|SSL and Cryptography||High CPU in SSL and Cryptography showing ProxySG and Advanced Secure Gateway|
|LSA||ProxySG CPU monitor showing high CPU in LSA|
If the above articles did not help resolve the high CPU utilization issue, these articles also document defects or configurations that can cause this issue:
|Issue Type||Fixed Release||Article|
|Defect||SGOS 184.108.40.206||CPU monitor showing high CPU in Policy on ProxySG running SGOS 6.5 after installing a policy|
|Configuration||N/A||Why is CPU utilization of policy evaluation in SGOS 6.5 much greater than in 6.2?|
|Configuration||N/A||ProxySG Experiencing High CPU Utilization and Input Errors on TCP Interface|
|Configuration||N/A||ProxySG Event Log reports "TCP in Livelock" during periods of high CPU utilization|
If you are still unable to resolve the high CPU utilization issue, you will need to open a ticket with Symantec Support. In addition to the details from the CPU Monitor, you may also be asked to provide the following: