Cisco Cisco Content Security Management Appliance M1070 Guía Del Usuario
15-21
AsyncOS 8.1 for Cisco Content Security Management User Guide
Chapter 15 Logging
Status Log Example
Fri Feb 24 15:14:39 2006 Info: Status: CPULd 0 DskIO 0 RAMUtil 2 QKUsd 0 QKFre 8388608
CrtMID 19036 CrtICID 35284 CrtDCID 4861 InjMsg 13889 InjRcp 14230 GenBncRcp 12 RejRcp 6318
DrpMsg 7437 SftBncEvnt 1816 CmpRcp 6813 HrdBncRcp 18 DnsHrdBnc 2 5XXHrdBnc 15 FltrHrdBnc 0
ExpHrdBnc 1 OtrHrdBnc 0 DlvRcp 6793 DelRcp 2 GlbUnsbHt 0 ActvRcp 0 UnatmptRcp 0 AtmptRcp 0
CrtCncIn 0 CrtCncOut 0 DnsReq 143736 NetReq 224227 CchHit 469058 CchMis 504791 CchEct
15395 CchExp 55085 CPUTTm 228 CPUETm 181380 MaxIO 350 RAMUsd 21528056 MMLen 0 DstInMem 4
ResCon 0 WorkQ 0 QuarMsgs 0 QuarQKUsd 0 LogUsd 3 AVLd 0 BMLd 0 CASELd 3 TotalLd 3 LogAvail
17G EuQ 0 EuqRls 0
Using System Logs
shows the statistics recorded in system logs.
System Log Example
In this example, the system log shows some commit entries, including the name of the user issuing the
commit and the comment entered.
commit and the comment entered.
Wed Sep 8 18:02:45 2004 Info: Version: 6.0.0-206 SN: XXXXXXXXXXXX-XXX
Wed Sep 8 18:02:45 2004 Info: Time offset from UTC: 0 seconds
Wed Sep 8 18:02:45 2004 Info: System is coming up
Wed Sep 8 18:02:49 2004 Info: bootstrapping DNS cache
Wed Sep 8 18:02:49 2004 Info: DNS cache bootstrapped
Wed Sep 8 18:13:30 2004 Info: PID 608: User admin commit changes: SSW:Password
Wed Sep 8 18:17:23 2004 Info: PID 608: User admin commit changes: Completed Web::SSW
Thu Sep 9 08:49:27 2004 Info: Time offset from UTC: -25200 seconds
Thu Sep 9 08:49:27 2004 Info: PID 1237: User admin commit changes: Added a second CLI log
for examples
Thu Sep 9 08:51:53 2004 Info: PID 1237: User admin commit changes: Removed example CLI
log.
Understanding Tracking Logs
Tracking logs record information about the email operations of AsyncOS. The log messages are a subset
of the messages recorded in the mail logs.
of the messages recorded in the mail logs.
The tracking logs are used by the message tracking component to build the message tracking database.
Because the log files are consumed in the process of building the database, the tracking logs are transient.
The information in tracking logs is not designed to be read or analyzed by humans.
Because the log files are consumed in the process of building the database, the tracking logs are transient.
The information in tracking logs is not designed to be read or analyzed by humans.
Tracking logs are recorded and transferred in a binary format for resource efficiency. The information is
laid out in a logical manner and is human-readable after conversion using a utility provided by Cisco.
The conversion tools are located at the following URL:
laid out in a logical manner and is human-readable after conversion using a utility provided by Cisco.
The conversion tools are located at the following URL:
http://tinyurl.com/3c5l8r
.
Table 15-20
System Log Statistics
Statistic
Description
Timestamp
Time that the bytes were transmitted.
Message
The logged event.