Troubleshooting High CPU Utilization Issues on the ProxySG or Advanced Secure Gateway
Last Updated February 20, 2019
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:
Is the proxy continuously at high CPU, or does it peak at certain times?
Does the CPU utilization come down after production hours?
Does the CPU utilization peak periodically then go back to "normal"? If so, can you graph out the peaks, and identify a trend?
Has anything recently changed in the environment that may have triggered the issue such as:
An increase in network traffic
New applications introduced
Configuration changes on the ProxySG or ASG or associated network devices
Enable CPU Monitor
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:
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:
Configure snapshots to happen every five minutes (default is 60), and run for at least 20 minutes during the CPU spike.