Cisco Cisco Content Security Management Appliance M690 Guía Para Resolver Problemas
21. Scanning Logs
22. Spam Quarantine Logs
23. Spam Quarantine GUI Logs
24. Reporting Logs
25. Reporting Query Logs
26. Updater Logs
27. SNMP Logs
28. Tracking Logs
29. Safe/Block Lists Logs
30. Authentication Logs
31. FIPS Logs
32. Upgrade Logs
33. Configuration History Logs
34. Reputation Engine Logs
35. AMP Engine Logs
36. AMP Archive
37. API Logs
38. Graymail Archive
[1]> 6
Please enter the name for the log:
[]> example.com.domain.debug
Enter the name of the domain for which you want to record
debug information.
[]> example.com
Please enter the number of SMTP sessions you want to record
for this domain.
[1]> 10000
Choose the method to retrieve the logs.
1. Download Manually: FTP/HTTP(S)/SCP
2. FTP Push
3. SCP Push
4. Syslog Push
[1]>
Filename to use for log files:
[example.com.text]>
Would you like to append system based unique identifiers
like $hostname, $serialnumber to the log filename? [N]>
Please enter the maximum file size. You can specify suffixes:
"m" for megabytes, "k" for kilobytes. Suffixes are
case−insensitive:
[10485760]>
Please enter the maximum number of files:
[10]>
Should an alert be sent when files are removed due to the
maximum number of files allowed? [N]>
Do you want to configure time−based log files rollover? [N]>
Note: Ensure that you commit any and all changes after the domain debug log is configured.
The log is active for the number of sessions that you configure for the domain. In order to view the trace of
the live email conversation, enter the tail example.com.domain.debug command into the ESA CLI.
the live email conversation, enter the tail example.com.domain.debug command into the ESA CLI.
Here is an example domain debug log that is generated when the ESA delivers a message to the recipient
domain example.com:
domain example.com: