Cisco Insight Reporter Installation Guide, v3.1.0
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- Updated:
- October 29, 2013
Chapter: Troubleshooting
- Troubleshooting MySQL Compatibility Issue
- Troubleshooting MySQL Start-up and Connectivity Problem
- Troubleshooting the "No Data Found" Message when Running Reports
- Troubleshooting Empty Service, Zone and Package Lists
- Troubleshooting No Interface Showing any Associated Traffic
- Troubleshooting Subscribers Flows Report that is Not Working
- Troubleshooting Authentication Failure
- Troubleshooting User Interface that is not Loading Correctly
- Troubleshooting Application Startup Problem
- Troubleshooting Connectivity with Traffic Database
- Troubleshooting Issues when Setting a Master Device
- Troubleshooting Connection Timeout from Traffic database
- Cisco Insight Reporter Error Codes
Troubleshooting
This chapter describes how to troubleshoot commonly encountered problems.
This chapter contains the following sections:
•
Troubleshooting MySQL Compatibility Issue
•Troubleshooting MySQL Start-up and Connectivity Problem
•Troubleshooting the "No Data Found" Message when Running Reports
•Troubleshooting Empty Service, Zone and Package Lists
•Troubleshooting No Interface Showing any Associated Traffic
•Troubleshooting Subscribers Flows Report that is Not Working
•Troubleshooting Authentication Failure
•Troubleshooting User Interface that is not Loading Correctly
•Troubleshooting Application Startup Problem
•Troubleshooting Connectivity with Traffic Database
•Troubleshooting Issues when Setting a Master Device
•Troubleshooting Connection Timeout from Traffic database
•Cisco Insight Reporter Error Codes
Troubleshooting MySQL Compatibility Issue
The application is compatible with MySQL version 5.1. If a non-compatible version is found installed on the server, the installation will abort and will show the following message:
An existing MySQL installation is detected on your system which is not compatible with Cisco Insight Reporter. Please use MySQL version 5.1 or uninstall the existing MySQL and rerun the Insight installation.Now exiting."
Troubleshooting MySQL Start-up and Connectivity Problem
If the default port for running MySQL (3306) is blocked or denied access on firewall, it could lead to installation or application start-up issue. This can occur due to one of the following reasons:
•SELinux is enabled and blocking access to port 3306
•Firewall is enabled and not configured to allow access to port 3306
•Socket is already in use
•On integrating with an existing MySQL server if you get connectivity problem, please make sure you give valid password for MySQL root user.
Note All the installation logs are created under the logs directory present under the directory where installer was unzipped.
For additional information about the MySQL connection issues, please refer http://dev.mysql.com/doc/refman/5.1/en/can-not-connect-to-server.html
Troubleshooting the "No Data Found" Message when Running Reports
If the output of a report gives a "No Data Found" message, you should check several conditions.
One of the reasons could be that the database tables have not been populated. You should check the following:
•Ensure that the database configuration on Cisco Collection Manager is correct
•Ensure that the SCE generates the type of RDR that you are trying to report on.
•Ensure that the ASR generated the type of NF records that you are trying to report on.
If you think the database tables are being populated, you should check the following:
•Ensure that the selected time span matches some data in the database tables.
•Ensure that you have properly selected the report parameters so that the report query matches some information on the database.
•Ensure that the data aging mechanism, configured on the Collection Manager, is configured as expected. If necessary, change the settings according to the suggested data sizing.
Troubleshooting Empty Service, Zone and Package Lists
If the form of report generation has some empty Service, Zone or Package list, check the following:
•Ensure that the SCE service configuration has been applied at least once after the Cisco Insight v2 installation, because this operation is needed to align the internal state of the application.
•Ensure that the INI_VALUES table is not empty after re-applying the SCE service configuration through the SCA BB Console.
•Ensure that the SCE_CONFIG table in not empty and has the same number of rows as the INI_VALUES table (this is only valid for single SCE deployments).
If you still see a non-empty INI_VALUES table, but an empty SCE_CONFIG table after applying the SCE service configuration, you should truncate all data from the INI_VALUES table and repeat the apply operation of the SCE service configuration through the SCA BB Console.
Troubleshooting No Interface Showing any Associated Traffic
If in the Network Wizard no interface displays in green (having associated traffic with it), the following checks should be made.
•Ensure that the RPT_USAGE_NF table is not empty.
•Ensure that the interfaces present in the RPT_USAGE_NF do not have data which is more than 99 days old.
•In case data present in RPT_USAGE_NF is not older than 99 days, verify the sync duration set while creating a remote database.
Troubleshooting Subscribers Flows Report that is Not Working
If the Subscriber Flows report is not working, check the following:
•Ensure that the FUR table is populated by the SCE.
•Ensure that the IP address of the Subscriber Manager is correct and is reachable by the Cisco Insight v3.1 application.
Troubleshooting Authentication Failure
The login to Insight is limited by the number of simultaneous logins allowed for a particular role, (limited to "2" for the default Super User). Hence refreshing the browser window without logging out will result in reaching this threshold and further login would result in authentication failure until the session is timed out. Hence usage of browser "Refresh or F5" should be avoided.
Troubleshooting User Interface that is not Loading Correctly
To successfully run/launch the User Interface, Insight requires the browser with Flash Player Plug-in 10.x or above. In case a compatible version is not found on the browser, you may get an empty screen or the following message:
"To view this page ensure that Adobe Flash Player version 10.0.0 or greater is installed."
Troubleshooting Application Startup Problem
The application, while starting, runs the Apache Tomcat on the port 80. Insight will not start if there are other applications using port 80.
If you wish to configure Insight to run on a different port (say 8080), change the connector configurations in
<[user home directory]/Insight/apache-tomcat-6.0.20/conf/server.xml]>
To
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="443" />
Note Please ensure all the ports (including AJP 1.3 connector port) used by tomcat (as mentioned in the server.xml) are free and not being used by any other application
While starting tomcat if you see the following error on your screen
"PID file /home/{user}/tomcat.pid found. Is Tomcat still running? Start aborted"
Then perform the following steps
"Change to the users home directory using
cd /home/{user}
"remove the PID file using
rm -f tomcat.pid
"Restart Tomcat using:
/etc/init.d/tomcat-{user} start
or
service tomcat-{user} start
Troubleshooting Connectivity with Traffic Database
In some environments, Cisco Insight Reporter may not be able to connect to the Cisco Service Control Management Suite Collection Manager traffic database.
Edit the catalina.policy file inside the "conf" folder of tomcat (i.e. <tomcat-dir>/conf/catalina.policy) and add the following lines:
grant {
permission java.net.SocketPermission "<CM DB IP ADDRESS>:<CM DB PORT>", "connect", "resolve";
};
Where CM DB IP ADDRESS corresponds to the traffic database IP address and CM DB PORT the corresponding port (MySQL: 3600 - Oracle: 1521 - Sybase: 4100).
Note Please ensure restart the tomcat service after editing catalina.policy.
Troubleshooting Issues when Setting a Master Device
Setting a device as "Master" for a network may fail due to anyone of following reasons:
1. The configuration data (in INI_VALUES or NF_INI_VALUES) does not exist for this device.
2. There are some invalid character (like ' or % or ?) exist in the name of service, package, zone for SCE and Application or Interface name for ASR.
Verify configuration in corresponding INI_VALUES/NF_INI_VALUES tables to fix this issue.
Troubleshooting Connection Timeout from Traffic database
Connections to traffic database servers may cause connection time out in logs if all available connections in the connection pool already acquired. The maximum connection in connection pool can be changed from config_system_param table by changing value for field poolMaxSize. Try to increase maximum number of connections in the ranges of 10, if this issue occurs.
The default value for poolMaxSize is 100.
Cisco Insight Reporter Error Codes
This section lists the error messages seen on the application and their respective meaning:
Feedback