Cisco Cisco Email Security Appliance C160 ユーザーガイド
38-38
User Guide for AsyncOS 9.7 for Cisco Email Security Appliances
Chapter 38 Logging
Log Types
Using Configuration History Logs
A configuration history log consists of a configuration file with an additional section listing the name of
the user, a description of where in the configuration the user made changes, and the comment the user
entered when committing the change. Each time a user commits a change, a new log is created containing
the configuration file after the change.
the user, a description of where in the configuration the user made changes, and the comment the user
entered when committing the change. Each time a user commits a change, a new log is created containing
the configuration file after the change.
Configuration History Log Example
In this example, the configuration history log shows that the user (admin) added a guest user to the table
that defines which local users are allowed to log in to the system.
that defines which local users are allowed to log in to the system.
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE config SYSTEM "config.dtd">
<!--
XML generated by configuration change.
Change comment: added guest user
User: admin
Configuration are described as:
This table defines which local users are allowed to log into the system.
Product: Cisco IronPort M160 Messaging Gateway(tm) Appliance
Model Number: M160
Version: 6.7.0-231
Serial Number: 000000000ABC-D000000
Number of CPUs: 1
Memory (GB): 4
Current Time: Thu Mar 26 05:34:36 2009
Feature "Cisco IronPort Centralized Configuration Manager": Quantity = 10, Time
Remaining = "25 days"
Feature "Centralized Reporting": Quantity = 10, Time Remaining = "9 days"
Feature "Centralized Tracking": Quantity = 10, Time Remaining = "30 days"
Feature "Centralized Spam Quarantine": Quantity = 10, Time Remaining = "30 days"
Feature "Receiving": Quantity = 1, Time Remaining = "Perpetual"
-->
<config>