PDF(8.4 KB) View with Adobe Reader on a variety of devices
ePub(85.4 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(71.2 KB) View on Kindle device or Kindle app on multiple devices
Updated:January 28, 2020
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
The Security Management Appliance (SMA) is used to centralize services from Email Security Appliances (ESAs) and Web Security Appliances (WSAs).
The centralized services are:
External Spam Quarantine
Centralized Policy, Virus, and Outbreak Quarantines
Centralized Configuration Management for Web Security Appliances
What are the SMA Processing Queues?
The Processing Queues are buffers that store centralized Reporting and Tracking files as they await to be processed by the SMA. Normally, the SMA receives batches of Reporting and Tracking files to process. The percentage of Reporting or Tracking files in the processing queue typically fluctuates as the files are transmitted from managed appliances and processed by the SMA.
Note: Processing Queue percentages gauge the number of files in the queue. They do not take file size into account. The percentages provide only a rough estimate of the SMA’s processing load.
Why is the Message Tracking or Reporting Processing Queue Always High?
If the Processing Queue usage percentages remain consistently high over several hours or days, then this is an indicator that the system is running at or beyond capacity.
In that case, consider the removal of some of the managed appliances from the SMA, the installation of additional SMAs, or both.
Check the disk utilization of the centralized services:
Navigate to Management Appliance > System Administration > Disk Management
If the Tracking or Reporting disk quotas are exceeded, you can add more disk space as long as there is some available.
Consider to decrease some other disk quotas and allocate this space to those that need it urgently.
Note: If the disk quota of a centralized service is exceeded, the SMA purges the oldest data to make room for new data. If the SMA receives Tracking/Reporting files from the managed devices (ESA/WSA) too fast, then, it piles up these files to parse in the Processing Queue until there is enough disk space to allocate more data.