Cisco Cisco Email Security Appliance C170 Guia Do Utilizador
34-6
Cisco AsyncOS 8.0.1 for Email User Guide
Chapter 34 Logging
Overview
Log Retrieval Methods
Log files can be retrieved based upon one of the following file transfer protocols. You set the protocol
while creating or editing the log subscription in the GUI or via the
while creating or editing the log subscription in the GUI or via the
logconfig
command during the log
subscription process.
Authentication
Logs
Logs
•
•
Configuration
History Logs
History Logs
•
•
•
Table 34-2
Log Type Comparison (continued)
Contains
Tr
ansactional
Stateless
Recorded as text
Recorded as mbox file
Recorded as binary
Periodic Status
Information
M
e
ssage R
e
ceiving
In
for
m
ation
Del
ivery Information
Individu
al Ha
rd
Bounc
e
s
Individu
al Soft Bounces
Injection S
M
TP
Conversati
on
Hea
d
er Logging
Del
ivery SMTP
Conversatio
n
Configuration Information
Table 34-3
Log Transfer Protocols
Manually
Download
Download
This method lets you access log files at any time by clicking a link to the log directory
on the Log Subscriptions page, then clicking the log file to access. Depending on your
browser, you can view the file in a browser window, or open or save it as a text file. This
method uses the HTTP(S) protocol and is the default retrieval method.
on the Log Subscriptions page, then clicking the log file to access. Depending on your
browser, you can view the file in a browser window, or open or save it as a text file. This
method uses the HTTP(S) protocol and is the default retrieval method.
Note
Using this method, you cannot retrieve logs for any computer in a cluster,
regardless of level (machine, group, or cluster), even if you specify this method
in the CLI.
regardless of level (machine, group, or cluster), even if you specify this method
in the CLI.
FTP Push
This method periodically pushes log files to an FTP server on a remote computer. The
subscription requires a username, password, and destination directory on the remote
computer. Log files are transferred based on a rollover schedule set by you.
subscription requires a username, password, and destination directory on the remote
computer. Log files are transferred based on a rollover schedule set by you.
SCP Push
This method periodically pushes log files to an SCP server on a remote computer. This
method requires an SSH SCP server on a remote computer using the SSH1 or SSH2
protocol. The subscription requires a username, SSH key, and destination directory on
the remote computer. Log files are transferred based on a rollover schedule set by you.
method requires an SSH SCP server on a remote computer using the SSH1 or SSH2
protocol. The subscription requires a username, SSH key, and destination directory on
the remote computer. Log files are transferred based on a rollover schedule set by you.
Syslog Push
This method sends log messages to a remote syslog server. This method conforms to
RFC 3164. You must submit a hostname for the syslog server and choose to use either
UDP or TCP for log transmission. The port used is 514. A facility can be selected for the
log; however, a default for the log type is pre-selected in the dropdown menu. Only
text-based logs can be transferred using syslog push.
RFC 3164. You must submit a hostname for the syslog server and choose to use either
UDP or TCP for log transmission. The port used is 514. A facility can be selected for the
log; however, a default for the log type is pre-selected in the dropdown menu. Only
text-based logs can be transferred using syslog push.