THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense.
The following information is for FCC compliance of Class B devices: The equipment described in this manual generates and may radiate radio-frequency energy. If it is not installed in accordance with Cisco’s installation instructions, it may cause interference with radio and television reception. This equipment has been tested and found to comply with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules. These specifications are designed to provide reasonable protection against such interference in a residential installation. However, there is no guarantee that interference will not occur in a particular installation.
Modifying the equipment without Cisco’s written authorization may result in the equipment no longer complying with FCC requirements for Class A or Class B digital devices. In that event, your right to use the equipment may be limited by FCC regulations, and you may be required to correct any interference to radio or television communications at your own expense.
You can determine whether your equipment is causing interference by turning it off. If the interference stops, it was probably caused by the Cisco equipment or one of its peripheral devices. If the equipment causes interference to radio or television reception, try to correct the interference by using one or more of the following measures:
Turn the television or radio antenna until the interference stops.
Move the equipment to one side or the other of the television or radio.
Move the equipment farther away from the television or radio.
Plug the equipment into an outlet that is on a different circuit from the television or radio. (That is, make certain the equipment and the television or radio are on circuits controlled by different circuit breakers or fuses.)
Modifications to this product not authorized by Cisco Systems, Inc. could void the FCC approval and negate your authority to operate the product.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILTY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco Ironport, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flip Video, Flip Video (Design), Flipshare (Design), Flip Ultra, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company.
Cisco Insight Reporter is the web reporting application designed for the Cisco Service Control Engine (SCE) solution. It provides reports, dashboards and advanced functions to analyze traffic information retrieved through the Deep-Packet-Inspection (DPI) capabilities of Cisco SCE devices.
This release 5.0.0 provides the support of the Next-Generation SCE devices such as the SCE10000 and Virtual SCE platforms.
Cisco Insight Reporter is a software-only solution: it is primarily designed to be installed as an independent component on a dedicated hardware. This scenario is the most suitable for medium/large SCE deployments for which it is advisable to keep the data collection and storage layers on separate hardware and dedicate resources to the Cisco Insight Reporter application.
For demo purpose or small SCE deployments, the application can be installed on the same host as the Cisco Collection Manager (CM). In this scenario, the embedded MySQL Enterprise 5.6 database engine, provided with the application, will also be used to store traffic data. The Collection Manager needs to be configured to point to the embedded MySQL server.
The software can be deployed also on virtualized systems provided that the hosted operating system is supported and that all the requirements on prerequisites are met.
The Cisco Insight Reporter release 5.0.0 can be installed on any physical or virtual host with the following minimal specifications:
Table 1.Hardware Specifications
Multi-core Intel x86/64 processor - 2.0 GHz or greater.
8 or more cores recommended.
4 GB or greater.
At least 16 GB of RAM are recommended when using the bundled MySQL Enterprise Server to store traffic data.
The application requires at least 1 GB free in the /home partition.
In case the embedded MySQL Enterprise database is NOT used to store traffic data: it is recommended to allocate at least 100 GB of storage.
In case the embedded MySQL Enterprise database is used to store traffic data: the appropriate disk size depends mainly on the RDR settings of SCE devices and the desired data retention policies to apply.
In this scenario it is recommended to allocate at least 1 TB of storage – please contact Cisco support for a more accurate sizing of the storage.
At least 1 Fast Ethernet (100Mbps) or Gigabit Ethernet (1 Gbps) network interface is required.
In case of doubt, you can contact Cisco Support to get an estimation of the required CPU power, RAM capacity and disk storage.
The performance of the Cisco Insight Reporter depends on the size of the SCE deployment and the number of users simultaneously running the reports. To get an optimal performance, the hardware may have to be scaled accordingly.
The above recommendation is for a good response time when running ONLY the Cisco Insight Reporter software. In case the same environment is shared to co-host other applications, the allocated resources need to be increased accordingly (CPU, RAM, storage).
You can install Cisco Insight Reporter release 5.0.0 on any server or virtual appliance running the following operating systems:
The application GUI supports a variety of screen resolution modes including 1280x1024, 1024x768, and 1680x1050 with consistent support of 4:3 and 16:9 aspect ratios (wide screen). For a better user experience it is recommended to use a minimum vertical resolution of 1024 pixels.
A minimal screen resolution of 1024x768 is supported with vertical and horizontal scroll bars. For other resolutions, scrollbars may appear if the screen resolution is lower than the application workspace or if there are too many toolbars configured on the browser.
To maximize the user experience, it is suggested to set the browser to full-screen mode (that can be set usually by pressing the F11 function key).
Cisco Insight Reporter release 5.0.0 is delivered with a bundled MySQL Enterprise database server v5.6 that is used for internal operations, but it can also be used to store traffic data populated by one or more Cisco Collection Managers.
When installing Cisco Insight Reporter on the same host as Cisco Collection Manager, both the traffic data and the application internal tables need to be located on the same database engine, thus it is required to use the database server shipped with the application.
Traffic data can also be stored on an external database server, in that case Cisco Insight Reporter supports the same database technologies as Cisco Collection Manager software:
·MySQL 5.x and greater
·Oracle 9.x and greater
·Sybase ASE 12.x and greater
Cisco Customers are in charge of providing the license of external database servers. They are also required to manually copy the software drivers on Cisco Insight Reporter to enable the connectivity between this latter and the external databases.
For licensing issues, when working with Oracle and Sybase databases, customers are required to provide the software JDBC connectors and copy them on a specific path of the application, as described in the Installation Guide.
Working with firewalls
Before installing the application make sure there is no firewall running on the hosting server or between the hosting server and the client workstations.
If the firewall(s) cannot be disabled, make sure the inbound/outbound TCP/UDP ports are enabled, as described in the Installation Guide.
Before installing the application make sure the SELinux option is disabled on the target Operating System, otherwise the installation wizard will terminate the setup process.
Removing all conflicting SW packages
It is required to remove all previous versions of MySQL software and packages, before installing the application.
Use the rpm –e command to remove any previous version of MySQL software and libraries, such as those shipped with the Operating System.
Configuring MySQL database for best performance
When using MySQL database technology to store traffic data, it is important to make sure the database engine is running with the appropriate settings in order to have good performance.
Cisco Insight Reporter is shipped with an embedded MySQL Enterprise database release 5.6 that can be used to store traffic information. This database release uses InnoDB as the default engine.
If storing traffic tables with RDR content on the embedded MySQL server, it is required to make sure the optimized settings for the InnoDB engine have been applied in the configuration file of the database server. Failure in doing so will result in poor performance during the generation of reports.
Since the InnoDB engine settings are dependent on the target resources (CPU, RAM) allocated to the database server, we are providing some guidelines to adjust the configuration file used at startup by the embedded MySQL database.
The end-user is expected to configure the InnoDB engine settings according to those guidelines.
Please refer to the Installation Guide for more details and instructions.
The same settings can also be applied to external MySQL databases, in case traffic tables are not store on the embedded database
Change of usage policies for the embedded MySQL Enterprise database
Starting from this release, the embedded MySQL Enterprise database can only be used by Cisco Insight Reporter or Cisco Collection Manager software. No access is granted to end-users or third party applications.
The password of the MySQL root user is configured by the installation wizard and kept secret.
This is particularly important for Customers planning to use the embedded database to store traffic information. Once they set up the Cisco Service Control solution, they can only access the stored data through a series of functions, provided by Cisco Insight Reporter.
Compatibility with Cisco DPI Devices
Cisco Insight Reporter is the reporting platform for both Cisco Service Control Application and Application Visibility & Control solutions.
This release 4.1.0 supports the following devices and configurations:
Table 3.Supported devices and releases
CM schema version
SCE 1K, 2K, 8K
(only 8K models support IPv6 traffic)
3.5.0 to 4.1.0
same as SCOS release
SCE 10K, vSCE
same as SCOS release
Differences with previous release
Cisco Insight Reporter release 5.0.0 is backward compatible with previous software versions and SCE models.
The release supports software upgrade to allow customers to perform a seamless installation of the application without the need to reconfigure all settings and existing report customizations (SCE networks, saved/scheduled reports, dashboard, color settings, etc.)
The following matrix describes the main differences between the two versions:
Table 4.Comparison with former release
Insight Reporter v4.1
Insight Reporter v5.0
Yes, based on Flex client
(for internal operations, but can also be used to store RDR information)
MySQL Enterprise 5.1
MySQL Enterprise 5.6
External database support
(to store RDR information)
MySQL, Oracle and Sybase
SCE model support
SCE1000, SCE2000, SCE8000
also SCE10K and vSCE
(NG SCE models)
SCE report template support (SCA BB)
3.5.0 to 4.1.0
3.5.0 to 4.1.0 (SCE8K)
5.0.0 (NG SCEs)
Yes, with report configuration
Authentication support with external AAA servers
Yes, support of RADIUS and TACACS+
Can be installed on a single appliance or distributed
New Features and Enhancements
This release 5.0.0 provides the following new features and enhancements, described more in detail in the User Guide:
·Support of Next-Generation SCE devices introduced in 2014: the SCE10000 and the Virtual SCE.
·Introduction of a report template based on the new database schema provided with Cisco Collection Manager 5.0.0.
·Improved scalability to support higher RDR rates generated by NG SCE devices.
·Live reporting feature enabled for the User Dashboard.
·Optimization of all report queries for faster execution of reports.
·Migration of the embedded database to MySQL Enterprise 5.6, for improved performance.
·Activation of new metrics for Web monitoring reports.
·Activation of Package filter for all supported reports.
·Activation of multiple selection of Packages for all supported reports.
·Adjustment to Video QoE monitoring report.
·New library for PDF layout.
·Improved debuggability options.
·New policies applied to end-user access to the embedded MySQL Enterprise server (compliancy to Oracle rules).
The following issues have been fixed since the delivery of previous software release:
DS-Lite option missing for VLink bandwidth per package
Reports showing topology series display duplicated entries in Data Grid
Issues with Traffic Monitoring - IPv6 reports
Global/Package/Zone Call Minutes per VoIP Service - Issue with Oracle DB
Top Cells report is not working after executing update_vlinks.sh in CM
Video Service Quality report should show QoE scores per service
Usage Per PCF Report throwing Error while executing Report in Oracle DB
In CSV Insight is not displaying parent services
Zone Concurrent Sessions per Topology throws error
Empty CSV is generated.
Top Video Hosts/Providers reports show wrong top Rank_bit_rate
Error running 'Daily peak BW for Specific Subscriber' on SYBASE
Report 'Number of subscribers per location' in Oracle gives exception
Running report 'Zone Bandwidth per Service' in SYBASE gives ERROR
Insight just supports 50 chars for Service name, CM supports 255 chars.
Report 'Top Domains Trend' gives 'Error during report execution'
Please restart MySQL at end of upgrade process from 4.1.0 to 4.2.0
Data fetched for report 'Usage per APN' differs in 4.0.0. VS 5.0.0
Hierarchical packages are not visible in Insight Reporter
No action on Select all option
Top Hosts report should run on Volume, Bandwidth and Duration
Invalid time format showing 24:40 in the report tooltip
Network cannot be saved if Service tree has more than 250 entries
The following is the list of open issues reported for current release:
CSCup20794 – Errors occurring on the GUI cannot be logged in the application logs
Errors occurring on the Graphical User Interface (such as HTTP Request errors, or similar events) cannot be logged on the application log file, even if the application logger is set to DEBUG mode..
This problem occurs only for errors generated at the GUI level (on the client browser, such as HTTP Request errors).
You can generate the HTTP Request error by suddenly disconnecting the client workstation from the network, so that the server hosting Insight Reporter can no longer be reached.
None. GUI errors are currently not designed to be stored on the application log file. They can only be read on screen.
When editing an existing report in the list of Favorites, the override option actually creates a copy of the report, instead of modifying the existing instance.
Try to edit an existing report in the list of My Favorites.
Change some parameters and then click the Save button.
The application will ask if you want to Override the existing instance.
There is no workaround: the user needs to delete the previous favorite report and create a new one with the desired parameters, then save it.
CSCup66595 – Video QOE report is missing filter on Packages
The Video QoE report doesn't allow to select an option to filter per Package.
When working with CM/SCOS schema v4.1.0 and greater, select and run the Video QoE monitoring report.
CSCup84787 – Default my.cnf has no optimized parameters for InnoDB engine (MySQL DB)
Insight Reporter v5.0 installs MySQL5.6 and creates a default my.cnf file inside /usr directory. But that file does not contain optimized values for InnoDB engine. It sets the default values that do not give optimum performance.
Check the my.cnf file located in the /usr directory after installing Insight Reporter 5.0.0.
The my.cnf file contains the default settings that are not optimized for good performance of the InnoDB engine.
Manualy update the my.cnf file located inside /usr directory
It is recommended to set up to max 70% physical memory to innodb_buffer_pool_size
innodb_flush_neighbors = 0
innodb_io_capacity = 2000
innodb_io_capacity_max = 6000
innodb_buffer_pool_instances = 8
thread_cache = 64
max_connections = 500
CSCtq46342 – Cumulative Distribution of Subscriber SMTP Sessions cannot be generated
The Cumulative Distribution of Subscriber SMTP Sessions report cannot be generated if the applied SCE configuration does not contain a Subscriber Service Counter associated to service 'SMTP'.
Verify there is no Subscriber Service Counter associated to service 'SMTP' on the SCA BB Console.
On Insight Reporter, open the Report Wizard, select the Malicious -> Spam -> Distribution and execute the report.
On the SCA BB Console, define a Subscriber Service Counter for service 'SMTP'. Then apply the pqb configuration to all SCE devices of the network.
CSCub67401 – Tomcat server must be restarted if the DB server went down
If, for any reason, the database engine hosting the traffic schema has been restarted or had a temporary failure, the application can no more connect to it until the Tomcat web server is also restarted.
Shutdown and restart the traffic database, then try using the application without restarting the Tomcat server.
You manually need to restart the Tomcat server to restore the connection pools to the traffic database.