27.11.2012 Views

IronPort - daily management guide - AsyncOS 7.6.1

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Log Types<br />

Injection Debug Log Example<br />

Using <strong>IronPort</strong> System Logs<br />

System Log Example<br />

5-24<br />

Cisco <strong>IronPort</strong> <strong>AsyncOS</strong> 7.6 for Email Daily Management Guide<br />

Chapter 5 Logging<br />

Wed Apr 2 14:30:04 2003 Info: 6216 Sent to '172.16.0.22': '220 postman.example.com<br />

ESMTP\015\012'<br />

Wed Apr 2 14:30:04 2003 Info: 6216 Rcvd from '172.16.0.22': 'HELO<br />

mail.remotehost.com\015\012'<br />

Wed Apr 2 14:30:04 2003 Info: 6216 Sent to '172.16.0.22': '250<br />

postman.example.com\015\012'<br />

Wed Apr 2 14:30:04 2003 Info: 6216 Rcvd from '172.16.0.22': 'MAIL<br />

FROM:\015\012'<br />

Wed Apr 2 14:30:04 2003 Info: 6216 Sent to '172.16.0.22': '250 sender<br />

ok\015\012'<br />

Wed Apr 2 14:30:04 2003 Info: 6216 Rcvd from '172.16.0.22': 'RCPT<br />

TO:\015\012'<br />

Wed Apr 2 14:30:04 2003 Info: 6216 Sent to '172.16.0.22': '250 recipient<br />

ok\015\012'<br />

Wed Apr 2 14:30:04 Info: 6216 Rcvd from '172.16.0.22': 'DATA\015\012'<br />

Wed Apr 2 14:30:04 2003 Info: 6216 Sent to '172.16.0.22': '354 go ahead\015\012'<br />

Wed Apr 2 14:30:04 2003 Info: 6216 Rcvd from '172.16.0.22': 'To:<br />

recipient@example.com\015\012Date: Apr 02 2003 10:09:44\015\012Subject: Test<br />

Subject\015\012From: Sender \015\012'<br />

Wed Apr 2 14:30:04 2003 Info: 6216 Rcvd from '172.16.0.22': 'This is the content of the<br />

message'<br />

Wed Apr 2 14:30:04 Info: 6216 Sent to '172.16.0.22': '250 ok\015\012'<br />

Wed Apr 2 14:30:04 Info: 6216 Rcvd from '172.16.0.22': 'QUIT\015\012'<br />

Wed Apr 2 14:30:04 2003 Info: 6216 Sent to '172.16.0.22': '221<br />

postman.example.com\015\012'<br />

Table 5-16 System Log Statistics<br />

Statistic Description<br />

Timestamp Time that the bytes were transmitted<br />

Message The logged event<br />

In this example, the System log shows some commit entries, including the name of the user issuing the<br />

commit and the comment entered.<br />

OL-25138-01

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!