User Guide

40-26
AsyncOS 9.1.2 for Cisco Email Security Appliances User Guide
Chapter 40 Testing and Troubleshooting
Troubleshooting Performance
Troubleshooting Performance
If you suspect that there are there are performance problems with the appliance, utilize the following
strategies:
Use the rate and hostrate commands to check the current system activity.
The
rate command returns real-time monitoring information about email operations. For more
information, see Displaying Real-time Activity, page 34-16.
The
hostrate command returns real-time monitoring information for a specific host.
Use the status command to cross-check the historical rates to check for degradation.
Use the status detail command to check the RAM utilization.
You can use the
status detail command to quickly see the system’s RAM, CPU, and Disk I/O
utilization.
Note RAM utilization should always be less than 45%. If RAM utilization exceeds 45%, then, the appliance
will enter “resource conservation mode;” it initiates a “back-off” algorithm to prevent over-subscription
of resources and sends out the following email alert:
This situation occurs only with an aggressive injection with poor deliverability facilities. If you
encounter RAM utilization exceeding 45%, check the number of messages in the queue and see if a
particular domain is down or unavailable for delivery (via the
hoststatus or hostrate commands).
Also check the status of the system and ensure that delivery is not suspended. If after stopping the
injection you continue to experience a high RAM utilization, contact Cisco Customer Support. See
Cisco Customer Support, page 1-3.
Is the problem specific to one domain?
Use the
tophosts command to get immediate information about the email queue and determine if a
particular recipient domain has delivery problems.
Check the size of the queue. You can delete, bounce, suspend, or redirect messages in the email
queue to manage its size, or to deal with recipients to a specific, problematic domain. For more
information, see Managing the Email Queue, page 34-22. Use these commands:
deleterecipients
bouncerecipients
TLS successfully connected to mxe.example.com.
TLS verification completed.
This system (hostname: hostname) has entered a 'resource conservation' mode in order to
prevent the rapid depletion of critical system resources.
RAM utilization for this system has exceeded the resource conservation threshold of 45%.
The allowed injection rate for this system will be gradually decreased as RAM
utilization approaches 60%.