IronPort - daily management guide - AsyncOS 7.6.1

Chapter 5 Logging
Configuring Host Keys
OL-25138-01
Enter the number of the log you wish to tail.
[]> 19
Press Ctrl-C to stop.
Cisco IronPort AsyncOS 7.6 for Email Daily Management Guide
Log Subscriptions
Mon Feb 21 12:25:10 2011 Info: PID 274: User system commit changes: Automated Update for
Quarantine Delivery Host
Mon Feb 21 23:18:10 2011 Info: PID 19626: User admin commit changes:
Mon Feb 21 23:18:10 2011 Info: PID 274: User system commit changes: Updated filter logs
config
Mon Feb 21 23:46:06 2011 Info: PID 25696: User admin commit changes: Receiving
suspended.
^Cmail3.example.com>
Use the logconfig -> hostkeyconfig subcommand to manage host keys for use with SSH when
pushing logs to other servers from the Cisco IronPort 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.
Note To manage user keys, see Managing Secure Shell (SSH) Keys, page 8-44.
The hostkeyconfig subcommand performs the following functions:
Table 5-37 Managing Host Keys - List of Subcommands
Command Description
New Add a new key.
Edit Modify an existing key.
Delete Delete an existing key.
Scan Automatically download a host key.
Print Display a key.
Host Display system host keys. This is the value to place in the remote system's
‘known_hosts’ file.
5-49