Cisco Insight Reporter v3.0 Installation Guide
Preparing for Installation
Downloads: This chapterpdf (PDF - 123.0KB) The complete bookPDF (PDF - 1.25MB) | Feedback

Preparing for Installation

Table Of Contents

Preparing for Installation

Hardware Requirements

Software Requirements

Supported Browsers

Screen Resolution

Working with Firewall

Supported Databases

Service Control Software Components Requirements

Deployment Scenarios

Virtual Machine Scenario

Single Appliance Scenario

Multiple Appliance Scenario

Multi-Insight Scenario


Preparing for Installation


Revised: July 12, 2011, OL-25218-01

The Cisco Insight Reporter v3 application requires installation on appropriate hardware, as well as an initial setup to make it operational and generate data traffic reports.

This chapter contains the following sections:

Hardware Requirements

Software Requirements

Service Control Software Components Requirements

Deployment Scenarios

Hardware Requirements

You can install the Cisco Insight Reporter v3 on any server with following minimum specifications:

Table 1-1 Hardware Specifications

Components
Specifications

CPU

Single or dual-core 2.0 GHz or greater Intel x86/64 processor

OR

32 /64 bit single or dual-core 2.0 GHz or greater Scalable Processor Architecture (SPARC) processor

RAM

4 GB or greater

Free disk space

10 GB for the operating system + free space for data retention. Recommended size is greater than 100 GB

Network interface

Single 100BASE-T Ethernet or greater


If you have any questions, you can contact Cisco Support to get an estimate of the required CPU power, RAM capacity, and disk storage.


Note The performance of the Cisco Insight Reporter depends on the size of the SCE/ASR1K 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 recommendations are only valid for hosts dedicated to running the Cisco Insight Reporter application. In case the same device is used to co-host Cisco Insight Reporter with other applications, the hardware has to be upgraded accordingly in terms of RAM, CPU and storage.


Software Requirements

You can install the Cisco Insight Reporter v3 application on server running:

Table 1-2 Supported Operating System

Operating System
Version
Architecture

Red Hat Enterprise Linux or CentOS

5.x

Intel 32/64 bit

Solaris

9 or 10

Intel 32/64 bit

SPARC 32/64 bit



Note The recommended operating system is Red Hat Enterprise Linux version 5 64-bit. Please see the chapter on troubleshooting for platform specific installation considerations.


Supported Browsers

The Cisco Insight Reporter v3 is compliant with the following browsers:

Firefox, v3.0 and later

IE, v6.0 and later

Google Chrome v5.0 and later


Note As a prerequisite, the Flash Player v 10.x or above should be installed on all client PCs that will be used to display reports.


Screen Resolution

The application GUI supports a variety of screen resolution modes including 1280 X 1024, 1024 X 768, and 1680 X 1050 with consistent support of 4:3 and 16:9 aspect ratios (wide screen). It is recommended that you use a minimum vertical resolution of 1024 pixels.


Note Resolution of 1024X768 is supported with vertical and horizontal scroll bars. On 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 (F11 function key).


Working with Firewall

Ensure that the TCP/IP ports you are using are not blocked by a firewall or port blocking service.

Configure firewall to allow traffic to the following:

Port for running the local database MySQL 5.1 (default is 3306)

Port for running the application (HTTP-default is 80 and HTTPS-default is 443)

Port for connecting to TACACS+ server (default is 49)

Connections to remote database servers storing Traffic Data being populated by Cisco Collection Manager(s)

Connections to Subscriber Manager

Connections to Email (SMTP) server

Ensure that the UDP ports you are using are not blocked by a firewall or port blocking service.

Port for connecting to RADIUS server (UDP- default is 1812)

If using an existing MySQL instance, ensure that:

MySQL server running

Network connections to the server are enabled

The network port you specify in firewall configuration is the one configured on the server


Note Cisco Insight Reporter does not work in SELinux enabled environment.

To Check the status of SELinux use the following command:

Shell> getenforce

If the output of this command is not "Disabled", edit /etc/selinux/config to disable SELinuxand set.

"SELINUX=disabled"

Supported Databases

Cisco Insight Reporter v3 supports multi-vendor drivers for connecting to the Collection Manager databases to retrieve traffic data and SCE configurations.

The application is distributed with an embedded MySQL 5.1 server (required for its internal operations) but can also integrate an existing MySQL 5.1 instance, when installed on a pre-configured environment running Cisco Collection Manager software. In that case, the database engine must be MySQL 5.1 and it will host both the Insight Reporter's proprietary schemas and the CM schema containing traffic data.

Cisco Insight Reporter can also be configured to work with external traffic databases populated by Cisco Collection Manager(s).

The supported vendors and versions for external traffic databasess are:

Oracle v 9.x or later

Sybase ASE v 12.x or later

MySQL v 5.x or later


Note For licensing reasons, the default installation kit only provides the JDBC driver to connect to external MySQL 5.x traffic databases.

To configure the application to use Sybase or Oracle as traffic databases, please copy the JDBC connector JAR file, provided with the respective database engine, to the following directory of the application:

< [user home directory]/Insight/apache-tomcat-6.0.20/webapps/insight/WEB-INF/lib >



Note If the Collection Manager database and Cisco Insight Reporter v3 are installed on the same machine, the database engine shall be MySQL 5.1.


Service Control Software Components Requirements

The Cisco Insight software works with Service Control Management Suite, the following software component versions are required:

Table 1-3 SCM Component Version

Component
Version

Subscriber Manager

from 3.5.0 to 3.7.0

Collection Manager

from 3.5.0 to 3.7.0 (for ASR1K support v3.7.0 is required)

SCE

from 3.5.0 to 3.7.0

ASR1K

XE 3.4 with SCEASR feature enabled


Deployment Scenarios

The Cisco Insight Reporter v3 can support different deployment scenarios to match different business requirements.


Note Traffic databases are used to store metadata for SCE/ASR1K devices and traffic data (populated by Collection Managers). The database bundled with Cisco Insight Reporter v3 is used for internal usage and data caching while generating reports.

Administrator may configure Cisco Collection Manager(s) to push the traffic data to the database server hosting the Cisco Insight Reporter's database OR vice versa, in which case the same database server is used for storing internal data as well as traffic data.

The database bundled with Cisco Insight Reporter v3 is used for internal usage and data caching while generating reports.

Administrator may configure Cisco Collection Manager(s) to push the traffic data to the database server hosting the Cisco Insight Reporter's database OR vice versa, in which case the same database server is used for storing internal data as well as traffic data.


For hardware configuration, please refer to Hardware Requirements.

These deployment scenarios are described in the following sections.

Virtual Machine Scenario

The Cisco Insight Reporter v3 can be installed on a VMWare virtual machine running a compatible operating system. The resources allocated to the virtual machine should be configured according to the target deployment scenario (number of SCEs/ASR1Ks, configuration of RDRs and NF records, other software installed on the same virtual machine, etc.).


Note The virtual machine scenario is reserved for demos or trials with one or two SCEs/ASRs, no more than 10 real-time monitored subscribers and no transaction usage RDRs/NFRs enabled.

The VMWare image would typically contain only the Cisco Insight Reporter v3 software.


Single Appliance Scenario

In the single appliance scenario, Cisco Insight Reporter v3 is installed on a single appliance running supported versions of Red Hat Enterprise Linux or Solaris (depending on the bus architecture).

Table 1-4 Table 6. Single Appliance Scenarios

Single Appliance Scenario
Description

Totally dedicated to Insight

This is the default and recommended, where the appliance is 100% dedicated to Insight v3. This is the recommended configuration for large SCE/ASR1k deployments.

Shared with a traffic database

The Insight appliance also contains the traffic database (populated by one or more external CMs).

The traffic database is MySQL and also hosts the Insight v3.0 internal schema (but still independent from the schema of Collection Manager).

This scenario is used for small deployments with one to five SCEs/ASR1Ks requiring only a single traffic database to store the RDR, or NFR information.

The number of supported SCEs/ASR1ks is dependent on the RDR or NFR frequency, the enabled RDRs and the activation of heavy usage RDRs (such as transactional or real-time subscriber monitoring).

Shared with a traffic database and a Collection Manager software instance

This scenario is similar to the previous one, but it is used when only one Collection Manager is required and it is embedded in the CISCO Insight Reporter appliance (thus sharing the hardware resources with Insight and the database).

This is not a recommended scenario and should be used only for very small deployments. Performance of this appliance scenario gets reduced because it works in shared mode.


Multiple Appliance Scenario

The multiple appliance scenario is an extension of the single appliance scenario with support for high-availability and redundancy obtained by clustering the Cisco Insight Reporter v3 appliance.

Cisco Insight Reporter v3 provides high-availability and redundancy using:

Hardware clustering of two identical appliances to provide a "cold" fail-over solution. No data is lost in case of failure of one of the appliances, but all the pending operations with the clients are dropped and will need to be restarted.

MySQL database is bundled for internal operations. When configuring an active and stand-by cluster for Insight, the database can be configured with table replication to provide data consistency and to keep the tables of the clustered system in synchronized state.


Note Insight high-availability affects only the reporting capability, and not the traffic data collection and storage (addressed by the Collection Manager databases).


Multi-Insight Scenario

Cisco Insight Reporter v3 supports the multi-Insight scenario because it can use any data source. Traffic databases can be shared by different Insight systems.

Because these traffic databases are accessed in read-only mode, several Insight instances can establish connections.

Through this deployment scenario, Cisco Insight Reporter supports Multi-tenancy and network segmentation concepts.