Maintenance Manual

All relevant actions on the MCU are logged, including those made through the serial console, a Supervisor blade (for
MSE blades), the API, FTP, and the web interface. The module that has caused a log is listed within the details of that
log and will be one of:
Web: For configuration changes made through the web interface.
Serial: For configuration changes made through the serial interface.
API: For configuration changes made through the API.
System: For audit messages from the MCU.
FTP: For audit messages recording requests made to the MCU over FTP.
Supervisor: For configuration changes made through the Supervisor Blade (only applies to MSE blades).
Each log also has a severity associated with it (Error, Severe Warning, Warning, Info, or Status Warning).
You must enable the audit log for it to record these actions.
To enable and view the audit log, go to Logs and select the Audit log tab.
Audit Log
The last 2000 audit messages generated by the MCU are displayed in the Audit log page.
The last 100,000 audit messages are stored on the external compact flash if there is one; otherwise, the last 100,000
audit messages are stored internally. You can only view the last 2000 through the web interface, but you can
download all stored audit messages (up to the 100,000) as XML.
You can delete audit messages. If you delete any audit messages, that will be audited in a new audit message.
You cannot send the audit log to a syslog server.
Related Topics
Configuring security settings
Understanding security warnings
Using Call Home
Note: Call Home requires the MCU to have an Encryption feature key. Without this key, you can view the Call Home
web page but the functionality will not be available.
Note: The MCU currently only supports anonymous reporting.
The MCU can submit reports about its status and any faults that it has experienced to the Cisco Call Home service.
The MCU always uses a secure connection (HTTPS) to transmit reports to Call Home.
When Call Home is disabled (default setting), the device will not send a report of any type until you select a Call
Home mode. When you have enabled Call Home, you can manually submit a report or configure the feature to work
automatically.
When you use Anonymous Call Home, you will not be able to view anonymously submitted reports; they are only
available to Cisco engineers and are only used to diagnose potential issues.
Note: If you have any questions about a Call Home report please contact Cisco TAC.
After choosing the Call Home mode anonymous, you can check Automatic Call Home enabled if you want the MCU
to automatically submit reports. The device sends any pending reports as soon as you apply this change. After that, it
will automatically send diagnostic reports about any unexpected device restarts or media resource restarts without
further manual intervention.
If you prefer not to use automatic Call Home, you can click Call Home now to manually send reports at any time.
204
Cisco TelePresence MCU Series Online Printable Help