230In This ChapterAudit Log................................................................................................230Device Information.................................................................................231Backup and Restore ..............................................................................233USB Profile Management ......................................................................235Upgrading CIMs .....................................................................................237Upgrading Firmware ..............................................................................237Upgrade History .....................................................................................239Rebooting the KX II ...............................................................................240Stopping CC-SG Management ..............................................................241Audit LogA log is created of the KX II system events. The audit log can contain upto approximately 2K worth of data before it starts overwriting the oldestentries. To avoid losing audit log data, export the data to a syslog serveror SNMP manager. Configure the syslog server or SNMP manager fromthe Device Settings > Event Management page. See Events Capturedin the Audit Log and Syslog (on page 305) for information on what iscaptured in the audit log and syslog.To view the audit log for your KX II:1. Choose Maintenance > Audit Log. The Audit Log page opens.The Audit Log page displays events by date and time (most recentevents listed first). The Audit Log provides the following information: Date - The date and time that the event occurred based on a 24-hour clock. Event - The event name as listed in the Event Managementpage. Description - Detailed description of the event.To save the audit log:Note: Saving the audit log is available only on the KX II Remote Console,not on the Local Console.1. Click Save to File. A Save File dialog appears.2. Choose the desired file name and location and click Save. The auditlog is saved locally on your client machine with the name andlocation specified.Chapter 10 Maintenance