|
|
catalina.out |
Contains information about the Cisco IPICS web-based processes, including the tomcat service. The catalina.out file is located in the /root/tomcat/current/logs directory. |
Cisco IPICS Activity Log |
The Cisco IPICS activity logs store information about activities relating to channels, users, and VTGs. To download and view the information in the activity log in a Microsoft Excel spreadsheet format, log in to the Administration Console as the ipics user, navigate to the Administration > Activity Log Management > Logs window, and click Download Activity Logs. You can change the information that Cisco IPICS saves in the activity log by navigating to Administration > Activity Log Options. For more information about the activity log, see the “Performing Cisco IPICS System Administrator Tasks” chapter in Cisco IPICS Server Administration Guide for your Cisco IPICS release. |
csalog |
Provides CSA startup and shutdown history. The csalog file and the securitylog.txt file contain the logging information for CSA. The csalog file is located in the /var/log directory. |
Cisco nnn MIVR nnnn.log |
These files provide you with information about call signaling and Session Initiation Protocol (SIP) information for the policy engine. Cisco IPICS names the initial file Cisco001MIVR0001.log. Subsequent files are named Cisco001MIVR0002.log, Cisco001MIVR0003.log, and so on. You configure the size of each Cisco nnn MIVR nnnn.log file, the total number of files that Cisco IPICS retains, and the information that Cisco IPICS logs in these files, by navigating to Policy Engine > Dial Engine > Control Center > Tracing in the Administration Console and changing the information in the Trace File Configuration and Trace Settings areas. To download and view the Cisco001MIVR0001.log file, log in to the Administration Console as the ipics user, navigate to the Policy Engine > Dial Engine > Status window and click SIP Subsystem or Policy Engine Subsystem ; then, click Cisco001MIVR0001.log. To download and view subsequent log files, navigate to the SIP subsystem or Policy Engine Subsystem window and click on the Cisco nnn MIVR nnnn.log file that you want to view. The Cisco nnn MIVR nnnn.log files are located in the /opt/cisco/ippe/log/MIVR directory. |
Cisco nnn MVCD nnnn.log |
These files provide you with error and status information for the cluster view daemon (CVD) component of the policy engine. The CVD is the node manager for the policy engine and is responsible for managing the startup process for the Cisco IPICS dial engine service. Cisco IPICS names the initial file Cisco001MVCD0001.log. Subsequent files are named Cisco001MVCD0002.log, Cisco001MVCD0003.log, and so on. To download and view the Cisco001MVCD0001.log file, log in to the Administration Console as the ipics user, navigate to the Policy Engine > Control Center > Status > Cluster View Daemon window, and click Cisco001MVCD0001.log. To download and view subsequent log files, navigate to the SIP subsystem or Policy Engine Subsystem window and click on the Cisco nnn MVCD nnnn.log file that you want to view. The Cisco nnn MVCD nnnn.log files are located in the /opt/cisco/ippe/log/MVCD directory. |
db-maintenance.log |
Contains records of the database backup and restore operations. To download and view the db-maintenance.log file, log in to the Administration Console as the ipics user, navigate to the Administration > Database Management > Log window and click Download. The db-maintenance.log file is located in the /opt/cisco/ipics/database/logs directory. For more information about the db-maintenance.log file, see the “Performing Cisco IPICS Database Backup and Restore Operations” chapter in Cisco IPICS Server Administration Guide for your Cisco IPICS release. |
dbm_log_ archive.log.gz |
A compressed file that contains archived data from previous db-maintenance.log daily log files. You can download the dbm_log_archive.log.gz file and save it to your PC by clicking the Download button in the Administration > Database Management > Log window. Once you download the files to your PC, you can view them as a text file. The dbm_log_archive.log.gz file is located in the /opt/cisco/ipics/database/logs directory. For more information about this archive file, see the “Performing Cisco IPICS Database Backup and Restore Operations” chapter in Cisco IPICS Server Administration Guide for your Cisco IPICS release. |
diagnostics.log |
Contains messages that are related to the database subsystem, and is located in the /opt/cisco/ipics/database/logs directory. |
driverManager n.log |
The driverManager log files contain policy engine-specific information for the media that are associated with each call. To configure the level of detail that the driverManager logs capture, navigate to the Policy Engine > Control Center > Tracing window in the Administration Console and check or uncheck the LIB_MEDIA check boxes. Cisco IPICS sets the size and total number of driverManager files; you cannot change these settings. When a log file reaches the configured maximum size, Cisco IPICS closes that log file and creates a new empty log file, and increments the number of the new log file by one. The driverManager n.log files are located in the /opt/cisco/ippe/log/MIVR directory. |
install.log |
Shows details about the Cisco IPICS operating system installation, including the packages that were installed and any errors that occurred during the installation. The install.log file is located in the /root directory. |
ipics.log |
Contains messages regarding all transactions that occur in the Cisco IPICS server. For example, this file contains information about the tomcat service, policy engine entries, or external notifications. The information that is contained in this log file can help you to troubleshoot problems that you might encounter with Cisco IPICS. Each message is marked with a severity level. There are seven severities, from TRACE to FATAL. By default, the ipics.log file captures all logging from the INFO to the FATAL level. You can view recent system logs in the Serviceability > System Logs window of the Administration Console. To download and view the information in the ipics.log, navigate to the Serviceability > System Logs window and click Download. For more information about accessing and downloading the ipics.log file, see the “Understanding Cisco IPICS Serviceability and Diagnostic Information” chapter in Cisco IPICS Server Administration Guide for your Cisco IPICS release. The ipics.log file is located in the /root/tomcat/current/logs directory. |
ipics_audit.log |
Records user activity. This activity includes successful and unsuccessful attempts by users to log in to the server, and actions that Cisco IPICS users perform when they are logged in to the Administration Console. The ipics_audit.log file is located in the /root/tomcat/current/logs directory. |
ipics-install-log.txt |
Shows details of the Cisco IPICS server software installation, including the packages that were installed, the user names that were created, and any errors that occurred during the installation. The install.log file is located in the / var/opt/CSCOipics/run/ yyyymmddhhmmss /ipics-install-log.txt directory, where: yyyymmddhhmmss represents the date and time that you performed the server software installation. |
ipics_idc.log |
Collects information for IDC users. Cisco IPICS updates the log file when IDC users log in and log out, or when users update their IDCs. The ipics_idc.log file is located in the /root/tomcat/current/logs directory. Note To retrieve additional IDC data for a user, you can upload logging information from a IDC to the server. For more information, see the “Generating and Modifying the IDC Log Levels” section. |
ipics_rms.log |
Collects log data for the RMS components that are part of the Cisco IPICS system. The ipics_rms.log file is located in the /root/tomcat/current/logs directory. |
lmgrd.log |
Contains information regarding Cisco IPICS licenses and the license manager, which is the component that manages the licenses. Cisco IPICS logs any actions that the license manager performs in the lmgrd.log file. You can download and view the lmgrd.log file by accessing the Administration Console as the ipics user, then navigating to the Serviceability > Diagnostics window and clicking Download Diagnostic Results. You receive a zipped file that contains the lmgrd.log and ipics.log files, along with the information that displays in the Diagnostics window. The lmgrd.log file is located in the /opt/cisco/ipics/license/versions/ ipics_version /logs directory. |
ntpsetup.log |
Records Network Time Protocol (NTP) configuration-related information. The netsetup.log file is located in the /var/log directory. Note You configure NTP by entering the ntpsetup command. For more information, see the “Configuring NTP on the Cisco IPICS Server with the ntpsetup Tool” section. |
tacout |
Contains the latest diagnostic summary information for Cisco IPICS. The tacout file is located in the /root/tomcat/current/logs directory. For more information about the tacout file, including instructions for downloading this file, see the “Understanding Cisco IPICS Serviceability and Diagnostic Information” chapter in Cisco IPICS Server Administration Guide for your Cisco IPICS release. |