Cisco Cisco Content Security Management Appliance M1070 Mode D'Emploi

AsyncOS supports a 

tail

 command, which shows the latest entries of configured logs on the appliance. 

Issue the 

tail

 command and select the number of a currently configured log to view it. Press Ctrl-C to 

exit from the 

tail

 command. 

You cannot view configuration history logs by using the 

tail

 command. You must use FTP or SCP.

In the following example, the 

tail

 command is used to view the system log. The 

tail

 command also 

accepts the name of a log to view as a parameter, for example, 

tail system_logs

Welcome to the M600 Messaging Gateway(tm) Appliance

example.srv> tail

Currently configured logs:

1. "cli_logs" Type: "CLI Audit Logs" Retrieval: FTP Poll

2. "euq_logs" Type: " Spam Quarantine Logs" Retrieval: FTP Poll

3. "euqgui_logs" Type: "Spam Quarantine GUI Logs" Retrieval: FTP Poll

4. "gui_logs" Type: "HTTP Logs" Retrieval: FTP Poll

5. "mail_logs" Type: "Text Mail Logs" Retrieval: FTP Poll

6. "reportd_logs" Type: "Reporting Logs" Retrieval: FTP Poll

7. "reportqueryd_logs" Type: "Reporting Query Logs" Retrieval: FTP Poll

8. "slbld_logs" Type: "Safe/Block Lists Logs" Retrieval: FTP Poll

9. "smad_logs" Type: "SMA Logs" Retrieval: FTP Poll

10. "system_logs" Type: "System Logs" Retrieval: FTP Poll

11. "trackerd_logs" Type: "Tracking Logs" Retrieval: FTP Poll

Enter the number of the log you wish to tail.

[]> 10

Press Ctrl-C to stop.

Thu Sep 27 00:18:56 2007 Info: Begin Logfile

Thu Sep 27 00:18:56 2007 Info: Version: 6.0.0-422 SN: 001143583D73-FT9GP61

Thu Sep 27 00:18:56 2007 Info: Time offset from UTC: 0 seconds

Thu Sep 27 00:18:47 2007 Info: System is coming up.

Thu Sep 27 00:23:05 2007 Warning: DNS query network error '[Errno 64] Host is down' to 

'172.16.0.3' looking up 'downloads.cisco.com'

Fri Sep 28 22:20:08 2007 Info: PID 688: User admin commit changes:

Fri Sep 28 23:06:15 2007 Info: PID 688: User admin commit changes:

^Cexample.srv>

.

Use the 

logconfig -> hostkeyconfig

 subcommand to manage host keys for use with SSH when 

pushing logs to other servers from the Cisco Content Security appliance. SSH servers must have a pair 
of host keys, one private and one public. The private host key resides on the SSH server and cannot be 
read by remote machines. The public host key is distributed to any client machine that needs to interact 
with the SSH server.

To manage user keys, see “Managing Secure Shell (SSH) Keys” in the user guide or online help for your 
Email Security appliance.