Cisco Prime Collaboration Manager supports the following log levels:
•Debug—Messages that are logged in this level help you to debug the application.
•Info—Messages that are logged in this level indicate the progress of the application.
•Warn—Messages that are logged in this level indicate potentially harmful situations.
•Error—Messages that are logged in this level indicate that the application can still continue to run.
The log configuration files are available in the directory /opt/emms/emsam/conf/logconfig. You must log into the Cisco Prime CM server as cmuser. You can edit the log files using any UNIX editor.
The following are the user configurable parameters in the conf files:
•Level—You can set the log level to warn, info, error, or debug.
•Dir—You can configure the subdirectory within the /log directory. You cannot change the main log directory.
•MaxSize—You can configure the maximum size of the log file in kilobytes. By default, it is set to 20000 KB.
•MaxBack—You can control the log file size growth. Cisco Prime CM supports log file rotation. It rotates log files only when they have reached the maximum size.
Example: To configure the notification log file:
notification=Level%debug; Dir%log/fault/; MaxSize%20000; MaxBack%6
In this example:
•The notification category is set to log level debug
•The notification log file is created under /opt/emms/emsam/log/fault
•The maximum size of the notification log file is 20000 kilobytes.
•The log files are rotated six times when the maximum size is reached. That is, after the notification log files reaches 20000 kilobytes, new log files are created for 6 times (notification.log.1, notification.log.2, notification.log.3, notification.log.4, notification.log.5, notification.log.6).
The generated log files are available in /opt/emms/emsam/log. You must log in as cmuser to access these files. The log files are also included in the backup file.