Cisco Performance Engine Installation Guide, 2.1.5 - Installing Cisco Performance Engine [Cisco Performance Engine]

Table Of Contents

Installing Cisco Performance Engine

General Installation Information

System Recommendations

Installing Cisco PerfE on a Solaris Platform

Directory Structure

Before You Begin

Installing the Cisco PerfE Software

Starting an Interactive Installation

Starting a Non-Interactive Installation

Installing Cisco PerfE on a Linux Platform

Before You Begin

Installing the Cisco PerfE Software

Installation Options

Installing MS SQL JDBC for the Call Manager CDR Collector

Autostart

Installing Autostart

Uninstalling Autostart

Starting and Stopping Performance Engine

Starting Performance Engine

Checking the Cisco PerfE Servers Status

Starting the Performance Engine GUI

Stopping Cisco PerfE

Upgrading Cisco Performance Engine

Requirement

Recommendations

Upgrade Considerations

Uninstalling Cisco PerfE

Installing Cisco Performance Engine

The Cisco Performance Engine (Cisco PerfE) software collects, processes, and stores performance data temporarily from various collection points. Cisco PerfE also sends normalized and formatted data to upper layer performance management applications. Cisco PerfE has software entities called collectors that interact with the data sources and collection points. These collectors can be created, controlled, and reconfigured without having to stop the Cisco PerfE application.

Note Previously, the Cisco PerfE software was also known as the Data Aggregation Server (DAS), therefore, you might see the abbreviation das in path names, command names, and property names.

This chapter includes the following sections:

•General Installation Information

•System Recommendations

•Installing Cisco PerfE on a Solaris Platform

•Installing Cisco PerfE on a Linux Platform

•Installation Options

•Starting and Stopping Performance Engine

•Upgrading Cisco Performance Engine

•Uninstalling Cisco PerfE

General Installation Information

Note The purchase of the Cisco Performance Engine product entitles you to install Cisco Performance Engine on only one host.

When installing Cisco Performance Engine, Release 2.1.5, consider the following:

•Cisco Performance Engine supports the Solaris 8 and Red Hat Enterprise Linux ES 2.1 platforms. For installation instructions on the Solaris platform, refer to the "Installing Cisco PerfE on a Solaris Platform" section. For installation instructions on the Linux platform, refer to the "Installing Cisco PerfE on a Linux Platform" section.

•If you are upgrading from a previous version of Cisco PerfE to version 2.1.5, refer to the "Upgrading Cisco Performance Engine" section.

•Once you have installed Cisco PerfE, you can configure you system to automatically start Cisco PerfE after the system has been rebooted. Refer to the "Autostart" section for instruction.

•During installation, a dasadmin account is created with perfegrp as the group for the account. This account is used for Cisco PerfE administration purposes. You can set the password for the dasadmin account after installation.

If the dasadmin account already exists and is associated with a group other than perfegrp, perfegrp will be added as a supplementary group for the dasadmin account.

Note The installation process creates a dasadmin account on standalone machines. If the system upon which Cisco PerfE is going to be installed is under the NIS domain, you must explicitly create a perfegrp group and a dasadmin account (associated with the perfegrp group) before installation.

System Recommendations

You need at least 1GB of disk storage for the Cisco PerfE software, which includes the runtime storage requirements.

Solaris Platform

The recommended platform for Cisco PerfE is a Sun Fire 280R. The suggested configuration for the Sun Fire 280R is:

•Two 750 MHz CPUs

•Two 36 GB hard disk drives

•Two GB of memory

•DVD-ROM or an FTP server

•Two 10/100 Fast Ethernet network interface cards

•Solaris 8.

Linux Platform

The suggested configuration is:

•Intel Pentium III 1.40 GHz 133 MHz bus

•Two GB RAM

•Two 18 GB hard disk drives

•One CD-ROM (24X)

•One 10/100 Fast Ethernet Network card

•Red Hat Enterprise Linux ES 2.1.

Installing Cisco PerfE on a Solaris Platform

This section describes installing Cisco PerfE on the Solaris platform and includes the following sections:

•Directory Structure

•Before You Begin

•Installing the Cisco PerfE Software

Directory Structure

The following directory structure is created under the installation directory when the Cisco PerfE software is installed on the Solaris platform:

•bin-contains the scripts/executables

•lib-contains Cisco PerfE jar files

•config-contains system configuration files including:

–das.properties-contains a number of parameters to configure Cisco PerfE

–log4j.properties-used to control log files

–package.properties-contains package version, etc.

•config/cli-contains files with commands to be used in the CLICollector

•config/EventTrigger-contains trigger definitions and mapping files

•config/ioscli-contains regular expression files for the IosCliOps collector

•config/template-contains templates

•config/baselines-contains baselines

•baseline/bin-contains baseline scripts

•baseline/startup-db-contains startup db

•baseline/backup-contains backup configuration when invoking load-baseline operation

•data-contains flat data files

•data/bts-contains data files for BTS collectors, for internal use only

•data/radius-contains data files from RADIUS server, for internal use only

•data/VoipCorrelator-contains correlated data files from Cisco PerfE, for external use

•data/VoipDasCollector-contains correlated data files from the VoipDAS collector, for external use

•db-contains embedded database files, for internal use only

•ddc-contains files relating to the DOCSIS collector

•examples-Tibco Client, datafiles, and XML

•logs-location of log files, including das.log, dasadmin.log, cdr.log, configAudit.log, and perfeSom.log

•MIBS-contains MIBS required for Cisco PerfE operations

•plugin-contains the plugin jar file

•schema-contains schema for calls, Cisco PerfE control interface, and events

•tmp-temporary working directory for Cisco PerfE

•tomcat-contains Web server configuration

•tools-contains tools used in Cisco PerfE.

Before You Begin

This section describes the pre-installation procedures you should follow when you install Cisco PerfE version 2.1.5 on a Solaris platform for the first time. If you are running a previous version of Cisco PerfE, remove the Cisco PerfE files using the uninstall instructions described in the "Uninstalling Cisco PerfE" section.

The name of the Cisco PerfE installation files for the Solaris version is:

CSCOPerfE-solaris-2.1.5

Be sure to use the complete hostname during pre-installation procedures and installation procedures.

Note Cisco PerfE administration should be done as user dasadmin. Switching between users can cause permission denied problems.

Step 1 Ensure that the Solaris package SUNWxcu4 is installed.

You can execute the command% pkgchk -l -p /usr/xpg4/bin/sed to verify that SUNWxcu4 is installed.

Step 2 Verify that the checksum of the Cisco PerfE file is correct:

% cksum CSCOPerfE-solaris-2.1.5
3892961305 224794112 CSCOPerfE-solaris-2.1.5

Step 3 Ensure the Cisco PerfE host has an IP address assigned to the 10/100 Fast Ethernet network interface card.

You can execute the netstat -nr command to see which interfaces and IP addresses are available and then select the IP address assigned to the interface you will be using.

Step 4 At the Cisco PerfE host, verify connectivity to a network having another host that can act as an FTP server:

% ping <ip_address_of_another_host>

Step 5 Verify the checksum of the following Cisco PerfE script:

% cksum getInput.sh
1795381629 4764 getInput.sh

Step 6 This step is applicable only if you wish to configure the database and data directories. If you do not wish to configure database directories, go on to the next step.

Create two directories on separate disks, one for the database and one for flat file data storage.

During Solaris installation, you will be prompted for the location of these directories if you choose not to use the default directories for the database and data files. Enter the full path name of these directories during installation. For example:

/db/cnsperfe_db

/data/cnsperfe_data

These directories can be given any name, however, for clarity, they are called cnsperfe_db and cnsperfe_data, respectively.

Note Both directories must be owned by the dasadmin user.

Step 7 If you plan to retrieve data from more than 800 devices, you must change the default file descriptors. By default, Solaris limits each process to opening a maximum of 1024 file descriptors. You can increase the maximum file descriptors setting in the /etc/system file:

set rlim_fd_max=2048

After making this change, reboot the system. You can now change the maximum value in the das.properties file to the maximum value (2048):

das.ulimit.maxOpenFiles=2048

For instruction on installing the Cisco PerfE software, continue to the following section.

Installing the Cisco PerfE Software

When installing the Solaris version of the Cisco PerfE software, you can choose to perform an interactive or a non-interactive installation. If you perform the interactive installation, you are prompted to provide the Cisco PerfE home, database, and data directories at various times during the installation procedure. If you perform the non-interactive installation, you create a script that provides the Cisco PerfE home, database, and data directories and stores the results in a file. Cisco PerfE retrieves the information from the file as needed during installation.

For instructions on the interactive installation, refer to the following section. for instruction on the non-interactive installation, refer to the "Starting a Non-Interactive Installation" section

Starting an Interactive Installation

To perform an interactive installation of the Cisco PerfE software, follow these steps:

Step 1 Change to the root user using the su command:

% su root
#

Step 2 Install the Cisco PerfE software by going to the directory where the CSCOPerfE-solaris-2.1.5 file is located, then invoke the pkgadd command:

# pkgadd -d CSCOPerfE-solaris-2.1.5

Step 3 Follow the instructions generated by the pkgadd program. The following is sample output of an interactive installation:
The following packages are available:
  	1  CSCOPerfE     Cisco CNS-PerfE
    (sparc) 2.1.5
Select package(s) you wish to process (or 'all' to process all packages). (default: all) 
[?,??,q]: 1
Processing package instance <CSCOPerfE> from <CSCOPerfE-solaris-2.1.5>
Cisco CNS-PerfE
(sparc) 2.1.5
Copyright (c) 2001-2005 Cisco Systems, Inc. 
All rights reserved.
This product is protected by copyright and distributed under licenses restricting copying, 
distribution and decompilation.
Do you want to use the default base directory (/opt/CSCOPerfE)? [y,n,?] y
Do you want to use the default database directory (/opt/CSCOPerfE/db)? 	[y,n,?] y
Do you want to use the default data directory (/opt/CSCOPerfE/data)? [y,n,?] y
Note If you want to use a non-default directory for the database or data, answer no to "Do you want to use the default...", then enter the absolute path to where you want the database or data to reside.
The new base directory is set to /opt/CSCOPerfE
## Executing checkinstall script.
Checking installation parameters...
Using </opt/CSCOPerfE> as the package base directory.
## Processing package information.
## Processing system information.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
This package contains scripts which will be executed with super-user permission during the 
process of installing this package.
Do you want to continue with the installation of <CSCOPerfE> [y,n,?] y
Please wait.installation in progress.
Installation of <CSCOPerfE> was successful.
Step 4 Enter the following command to verify that the Cisco PerfE package was installed:

# pkginfo -l CSCOPerfE

Refer to the "Directory Structure" section for information.

Step 5 Exit the root user account:

# exit

Once you have installed Cisco PerfE, refer to the Cisco Performance Engine User Guide for detailed information on changing default properties, configuring the Cisco PerfE software, and the various Cisco PerfE collectors.

Starting a Non-Interactive Installation

To perform a non-interactive installation of the Cisco PerfE software, follow these instructions:

Step 1 Copy getInput.sh to the /tmp directory.

Step 2 Login as root:

% su root
#

Step 3 Change directory to /tmp:

# cd /tmp

Step 4 Follow the instructions generated by the getInput.sh program:
Do you want to use the default base directory (/opt/CSCOPerfE)? [y,n,?] y
Do you want to use the default database directory (/opt/CSCOPerfE/db)? [y,n,?] y
Do you want to use the default data directory (/opt/CSCOPerfE/data)? [y,n,?] y
The new base directory is set to /opt/CSCOPerfE
The database directory is set to /opt/CSCOPerfE/db
The data directory is set to /opt/CSCOPerfE/data
Do you want to use these values in installation (y)? [y,n,?] y
Creating the installation administration file, /var/tmp/perfe/cnspe-admin...
This script provides prompts for the Cisco PerfE home, database, and data directories and stores the results in the /var/tmp/perfe/cnspe-admin file which is used along with the pkgadd command.

Step 5 Install the Cisco PerfE package as follows:

# pkgadd -a /var/tmp/perfe/cnspe-admin -d CSCOPerfE-solaris-2.1.5 CSCOPerfE

Step 6 The following is sample output generated by the pkgadd program:
# sudo pkgadd -a /var/tmp/perfe/cnspe-admin -d CSCOPerfE-solaris-
2.1.5 CSCOPerfE
Processing package instance <CSCOPerfE> from </tmp/2001install/CSCOPerfE-
solaris-2.1.5>
Cisco CNS-PerfE
(sparc) 2.1.5
Copyright (c) 2001-2005 Cisco Systems, Inc. 
All rights reserved.
This product is protected by copyright and distributed under
licenses restricting copying, distribution and decompilation.
## Executing checkinstall script.
Checking installation parameters...
Using </opt/CSCOPerfE> as the package base directory.
## Processing package information.
## Processing system information.
## Verifying disk space requirements.
## Checking for conflicts with packages already installed.
## Checking for setuid/setgid programs.
Installing Cisco CNS-PerfE as <CSCOPerfE>
## Executing preinstall script.
preinstall script...
Database directory: 
Data directory: 
## Installing part 1 of 1.
...
...
## Executing postinstall script.
Changing file permissions...
changing owner and group settings...
Installation of <CSCOPerfE> was successful.
Step 7 Enter the following command to verify that the Cisco PerfE package was installed:

# pkginfo -l CSCOPerfE

Refer to the "Directory Structure" section for information.

Step 8 Exit the root user account:

# exit

Once you have installed Cisco PerfE, you can continue on to the Installation Options section, or refer to the Cisco Performance Engine User Guide for detailed information on changing default properties, configuring the Cisco PerfE software, and the various Cisco PerfE collectors.

Installing Cisco PerfE on a Linux Platform

This section describes how to install Cisco PerfE on a Linux platform and includes the following:

•Before You Begin

•Installing the Cisco PerfE Software.

Before You Begin

This section describes the pre-installation procedures you should follow when you install Cisco PerfE version 2.1.5 on a Linux platform for the first time. If you are running a previous version of Cisco PerfE, remove the Cisco PerfE files using the uninstall instructions described in the "Uninstalling Cisco PerfE" section.

The name of the Cisco PerfE installation files for the Linux version is:

CSCOPerfE-2.1.5B08-0.i386.rpm

Be sure to use the complete hostname during pre-installation procedures and installation procedures.

Note Cisco PerfE administration must be done as the dasadmin user. Switching between users can cause permission denied problems.

Step 1 Ensure the Cisco PerfE host has an IP address assigned to the 10/100 Fast Ethernet network interface card.

You can execute netstat -nr to see what interfaces and IP addresses are available, then select the IP address assigned to the interface you will be using.

Step 2 At the Cisco PerfE host, verify connectivity to a network having another host that can act as an FTP server:

% ping <ip_address_of_another_host>

Step 3 If you downloaded Cisco PerfE from the Cisco web site, ensure the checksum of the Cisco PerfE software package is correct:

# cksum CSCOPerfE-2.1.5B08-0.i386.rpm
152621939 71414519 CSCOPerfE-2.1.5-0.i386.rpm

Step 4 In order to display graphs, ensure the XFree86-libs RPM is installed.

Step 5 For the Autostart feature to work properly, ensure the run level in the /etc/inittab file is set to
3(Multi User Mode):

id:3:initdefault:

Step 6 If you are planning on using the DOCSIS collector, ensure the ncurses4-5.0-5.i386.rpm RPM is installed.

Note Use the --nodeps option to continue with the Cisco PerfE installation if the ncurses library version 4 is not installed.

For instruction on installing the Cisco PerfE software, continue to the following section.

Installing the Cisco PerfE Software

To install Cisco Performance Engine software on a Linux platform, do the following.

Step 1 Change to the root user using the su command:

% su root

Step 2 Install the Cisco PerfE software by invoking the rpm command:

# rpm -i --nodeps CSCOPerfE-2.1.5B08-0.i386.rpm

This command installs the Cisco PerfE software in the default /opt/CSCOPerfE directory.

To install Cisco PerfE in a different directory, use the following command:

# rpm -i --nodeps --prefix <install_dir> CSCOPerfE-2.1.5B08-0.rpm

where <install_dir> is the full path name of the non default directory.

Step 3 Use the rpm command to get RPM information about the CSCOPerfE directory:

# rpm --query -i CSCOPerfE

Step 4 Exit from the root user account:

# exit

Once you have installed Cisco PerfE, you can continue on to the Installation Options section, or refer to the Cisco Performance Engine User Guide for detailed information on changing default properties, configuring the Cisco PerfE software, and the various Cisco PerfE collectors.

Installation Options

After installing the Cisco PerfE software, you can choose to:

•Install the Microsoft SQL JDBC driver in order to retrieve data from the Call Manager collector.

•Install the Autostart feature to automatically start Cisco PerfE after your system has been rebooted.

Refer to the following sections for instructions.

Installing MS SQL JDBC for the Call Manager CDR Collector

If you wish to retrieve data from the Call Manager collector, you must install the Microsoft SQL JDBC driver.

Note The Microsoft SQL JDBC driver is only required if you plan on using the Call Manager CDR collector.

To install the Microsoft SQL JDBC driver, do the following:

Step 1 Download the SQL Server 2000 driver for JDBC Service Pack 1 (version 2.2.0029) from the following link:

http://www.microsoft.com/downloads/details.aspx?FamilyID=4f8f2f01-1ed7-4c4d-8f7b-3d47969e66ae&DisplayLang=en

Download the UNIX version:

mssqlserver.tar

Step 2 Install the Microsoft SQL JDBC as per instructions from the download website.

Step 3 Copy the SQL Server JDBC libraries into the <CNS_PerfE_HOME>/tools/msjdbc directory as follows:

a. Telnet and login into the Cisco PerfE host as dasadmin:

> telnet <ip_address_CNS-PerfE_host>

login: dasadmin

Password: <password>

b. Copy the jar files.

For example, if the Microsoft SQL JDBC driver is installed in /opt/msSQLjdbc and Cisco PerfE is installed in /opt/CSCOPerfE, copy the libraries as follows:

> cp /opt/msSQLjdbc/lib/*.jar /opt/CSCOPerfE/tools/msjdbc/*

Autostart

The Autostart feature allows the system to automatically start Cisco PerfE after the computer system has been rebooted.

Note Ensure the run level in the /etc/inittab file is set to 3.

Note Ensure the login environment for the dasadmin account does not start Openwindows. Doing so could interfere with the successful restart of the application after the reboot. If the default shell for dasadmin is C-Shell, set TERM to vt100 in the .login file. If the default shell for dasadmin is the Bourne shell, set TERM to vt100 in the .profile file.

Installing Autostart

To install the Autostart feature, do the following:

Step 1 Login as root.

% root

Step 2 Enter the following command:

% <CNS_PerfE_HOME>/bin/autostart install

Uninstalling Autostart

To remove the Autostart feature, do the following:

Step 1 Login as root.

% root

Step 2 Enter the following command:

% <CNS_PerfE_HOME>/bin/autostart remove

Starting and Stopping Performance Engine

This section contains the following:

•Starting Performance Engine

•Checking the Cisco PerfE Servers Status

•Starting the Performance Engine GUI

•Stopping Cisco PerfE

Starting Performance Engine

To start Cisco PerfE, do the following:

Step 1 Log as dasadmin:

% dasadmin

Step 2 Change directory to where Cisco PerfE is installed:

% cd <CNS_PerfE_HOME>/bin

Step 3 Start Cisco PerfE:

% ./start.sh all

Checking the Cisco PerfE Servers Status

To check the status of Cisco PerfE servers, do the following:

Step 1 Change directory to where Cisco PerfE is installed:

% cd <CNS_PerfE_HOME>/bin

Step 2 Check the status of the Cisco PerfE servers:

% ./status.sh

Starting the Performance Engine GUI

To start the Cisco PerfE GUI, do the following:

Step 1 Enter the following URL in Address field of your web browser:

http://<hostname>:8080/cperfe

Step 2 Enter dasadmin as the username and cisco as the password values.

Refer to the Cisco Performance Engine User Guide for information on using the GUI to configure Cisco PerfE.

Stopping Cisco PerfE

To stop Cisco PerfE, do the following:

Step 1 Change directory to where Cisco PerfE is installed:

% cd <CNS_PerfE_HOME>/bin

Step 2 Start Cisco PerfE:

% ./stop.sh all

Upgrading Cisco Performance Engine

This upgrade procedure is used to upgrade the configuration and data from Cisco PerfE 2.1, 2.1.1. or 2.1.2 to 2.1.5.

Cisco PerfE 2.1.5 introduces new database tables to store the GUI details and new columns are introduced to the CBQoS and System Collector tables. The upgrade script upgrades the Cisco PerfE 2.1, 2.1.1, or 2.1.2 database with these new tables and configuration files to the Cisco PerfE 2.1.5 installation.

Requirement

Cisco PerfE 2.1, 2.1.1, or 2.1.2 files must be backed up to a specific directory and the contents of this directory serve as input to the upgrade script.

Note The upgrade log is available under <CNS_PerfE_HOME>/logs/upgrade.log.

Recommendations

•It is recommended that the Cisco PerfE 2.1, 2.1.1, or 2.1.2 files are backed up before upgrading so they can be restored later, if required.

•User intervention is not allowed during an upgrade. If you interrupt the upgrade process, you get the following message on stdout:

*****User interruption not allowed during upgrade****

The upgrade is continued, however, it is recommended not to interrupt the upgrade process.

Upgrade Considerations

•The dasadmin username will be stored in the database (Password_Table).

•CBQosTables will be upgraded with 20 new columns for Match Statement, Traffic Shaping, and Random Detect Statistics.

•SystemCollector table will be upgraded with the new PerfE processes statistics.

•Cisco PerfE configuration files (for example, das.properties and ddc) will be updated with the changed values.

•Other files (such as those in the MIBs, templates, baselines, plugin, cli, and ioscli directories) will be copied to their respective locations.

•If upgrading from 2.1, 2.1.1, or 2.1.2 to 2.1.5, be sure to upgrade the following property in the das.properties file if the secure password was not modified in an earlier installation:

db.password.secure=vnMDzh7Q9RA=

Note New MIBs introduced in Cisco PerfE 2.1, 2.1.1, or 2.1.2 are only copied to the Cisco PerfE 2.1.5 location. Therefore, if existing MIBs have been modified, these are not considered during the upgrade. Thus, you must explicitly modify these MIBs in 2.1.5

To upgrade, do the following:

Step 1 Run stop.sh all to stop the Cisco Perf Engine 2.1, 2.1.1, or 2.1.2. This will allow you to create an offline backup.

Step 2 Run backup.sh to backup the Cisco PerfE 2.1, 2.1.1, or 2.1.2 files to the <backup directory>.

Note All files that are to be upgraded should be backed up.

The default files to be backed up are specified in the <CNS_PerfE_HOME>/config/backup.files file. If you want to back up additional files, you should add them to the backup.files file.

Step 3 Remove the Cisco PerfE 2.1, 2.1.1, or 2.1.2 installation.

Step 4 Install Cisco PerfE 2.1.5.

Step 5 Run backup.sh to backup the Cisco PerfE 2.1.5 files.

Step 6 Run the upgrade tool (upgrade.sh) to upgrade the files:

% cd <CNS_PerfE_HOME>/bin

% ./upgrade.sh <backup directory>

Step 7 Check that all of the properties files are updated with new values as set in the Cisco PerfE 2.1.5 properties files. For example, the das.properties, Db.properties, and ddc properties files. If an error occurs, go to Step 8. Otherwise, continue on to Step 9.

Step 8 If an error occurs during the upgrade or the upgrade fails, run restore.sh to restore the Cisco PerfE 2.1.5 files. After a successful restore, go to Step 6.

Step 9 To verify that the upgrade was successful, start Cisco PerfE and the Cisco PerfE GUI. Refer to the "Starting and Stopping Performance Engine" section.

Once you have upgraded Cisco PerfE, you can continue on to the Installation Options section, or refer to the Cisco Performance Engine User Guide for detailed information on changing default properties, configuring the Cisco PerfE software, and the various Cisco PerfE collectors.

Uninstalling Cisco PerfE

Note Backup all configuration and data files you might need before uninstalling Cisco PerfE.

To uninstall the Solaris or Linux versions of the Cisco PerfE software, follow these steps:

Step 1 Telnet and login into the Cisco PerfE host as dasadmin:

% telnet <ip_address_CNS_PerfE_host>

login: dasadmin
Password: <password>
%

Step 2 Change to the root user using the su command:

% su root
#

Step 3 Switch to the /bin directory:

# cd <CNS_PerfE_HOME>/bin

Step 4 Uninstall the Cisco PerfE software by entering the command:

# ./uninstall.sh

Step 5 Exit out of the root user account:

# exit

	Cisco Performance Engine Installation Guide, 2.1.5
	Installing Cisco Performance Engine
Cisco Performance Engine Installation Guide, 2.1.5 Installing Cisco Performance Engine Configuring the TIBCO Routing Daemon (rvrd) to Communicate Between Two Networks	Download this chapter Installing Cisco Performance Engine Feedback Table Of Contents Installing Cisco Performance Engine General Installation Information System Recommendations Installing Cisco PerfE on a Solaris Platform Directory Structure Before You Begin Installing the Cisco PerfE Software Starting an Interactive Installation Starting a Non-Interactive Installation Installing Cisco PerfE on a Linux Platform Before You Begin Installing the Cisco PerfE Software Installation Options Installing MS SQL JDBC for the Call Manager CDR Collector Autostart Installing Autostart Uninstalling Autostart Starting and Stopping Performance Engine Starting Performance Engine Checking the Cisco PerfE Servers Status Starting the Performance Engine GUI Stopping Cisco PerfE Upgrading Cisco Performance Engine Requirement Recommendations Upgrade Considerations Uninstalling Cisco PerfE Installing Cisco Performance Engine The Cisco Performance Engine (Cisco PerfE) software collects, processes, and stores performance data temporarily from various collection points. Cisco PerfE also sends normalized and formatted data to upper layer performance management applications. Cisco PerfE has software entities called collectors that interact with the data sources and collection points. These collectors can be created, controlled, and reconfigured without having to stop the Cisco PerfE application. Note Previously, the Cisco PerfE software was also known as the Data Aggregation Server (DAS), therefore, you might see the abbreviation das in path names, command names, and property names. This chapter includes the following sections: •General Installation Information •System Recommendations •Installing Cisco PerfE on a Solaris Platform •Installing Cisco PerfE on a Linux Platform •Installation Options •Starting and Stopping Performance Engine •Upgrading Cisco Performance Engine •Uninstalling Cisco PerfE General Installation Information Note The purchase of the Cisco Performance Engine product entitles you to install Cisco Performance Engine on only one host. When installing Cisco Performance Engine, Release 2.1.5, consider the following: •Cisco Performance Engine supports the Solaris 8 and Red Hat Enterprise Linux ES 2.1 platforms. For installation instructions on the Solaris platform, refer to the "Installing Cisco PerfE on a Solaris Platform" section. For installation instructions on the Linux platform, refer to the "Installing Cisco PerfE on a Linux Platform" section. •If you are upgrading from a previous version of Cisco PerfE to version 2.1.5, refer to the "Upgrading Cisco Performance Engine" section. •Once you have installed Cisco PerfE, you can configure you system to automatically start Cisco PerfE after the system has been rebooted. Refer to the "Autostart" section for instruction. •During installation, a dasadmin account is created with perfegrp as the group for the account. This account is used for Cisco PerfE administration purposes. You can set the password for the dasadmin account after installation. If the dasadmin account already exists and is associated with a group other than perfegrp, perfegrp will be added as a supplementary group for the dasadmin account. Note The installation process creates a dasadmin account on standalone machines. If the system upon which Cisco PerfE is going to be installed is under the NIS domain, you must explicitly create a perfegrp group and a dasadmin account (associated with the perfegrp group) before installation. System Recommendations You need at least 1GB of disk storage for the Cisco PerfE software, which includes the runtime storage requirements. Solaris Platform The recommended platform for Cisco PerfE is a Sun Fire 280R. The suggested configuration for the Sun Fire 280R is: •Two 750 MHz CPUs •Two 36 GB hard disk drives •Two GB of memory •DVD-ROM or an FTP server •Two 10/100 Fast Ethernet network interface cards •Solaris 8. Linux Platform The suggested configuration is: •Intel Pentium III 1.40 GHz 133 MHz bus •Two GB RAM •Two 18 GB hard disk drives •One CD-ROM (24X) •One 10/100 Fast Ethernet Network card •Red Hat Enterprise Linux ES 2.1. Installing Cisco PerfE on a Solaris Platform This section describes installing Cisco PerfE on the Solaris platform and includes the following sections: •Directory Structure •Before You Begin •Installing the Cisco PerfE Software Directory Structure The following directory structure is created under the installation directory when the Cisco PerfE software is installed on the Solaris platform: •bin-contains the scripts/executables •lib-contains Cisco PerfE jar files •config-contains system configuration files including: –das.properties-contains a number of parameters to configure Cisco PerfE –log4j.properties-used to control log files –package.properties-contains package version, etc. •config/cli-contains files with commands to be used in the CLICollector •config/EventTrigger-contains trigger definitions and mapping files •config/ioscli-contains regular expression files for the IosCliOps collector •config/template-contains templates •config/baselines-contains baselines •baseline/bin-contains baseline scripts •baseline/startup-db-contains startup db •baseline/backup-contains backup configuration when invoking load-baseline operation •data-contains flat data files •data/bts-contains data files for BTS collectors, for internal use only •data/radius-contains data files from RADIUS server, for internal use only •data/VoipCorrelator-contains correlated data files from Cisco PerfE, for external use •data/VoipDasCollector-contains correlated data files from the VoipDAS collector, for external use •db-contains embedded database files, for internal use only •ddc-contains files relating to the DOCSIS collector •examples-Tibco Client, datafiles, and XML •logs-location of log files, including das.log, dasadmin.log, cdr.log, configAudit.log, and perfeSom.log •MIBS-contains MIBS required for Cisco PerfE operations •plugin-contains the plugin jar file •schema-contains schema for calls, Cisco PerfE control interface, and events •tmp-temporary working directory for Cisco PerfE •tomcat-contains Web server configuration •tools-contains tools used in Cisco PerfE. Before You Begin This section describes the pre-installation procedures you should follow when you install Cisco PerfE version 2.1.5 on a Solaris platform for the first time. If you are running a previous version of Cisco PerfE, remove the Cisco PerfE files using the uninstall instructions described in the "Uninstalling Cisco PerfE" section. The name of the Cisco PerfE installation files for the Solaris version is: CSCOPerfE-solaris-2.1.5 Be sure to use the complete hostname during pre-installation procedures and installation procedures. Note Cisco PerfE administration should be done as user dasadmin. Switching between users can cause permission denied problems. Step 1 Ensure that the Solaris package SUNWxcu4 is installed. You can execute the command% pkgchk -l -p /usr/xpg4/bin/sed to verify that SUNWxcu4 is installed. Step 2 Verify that the checksum of the Cisco PerfE file is correct: % cksum CSCOPerfE-solaris-2.1.5 3892961305 224794112 CSCOPerfE-solaris-2.1.5 Step 3 Ensure the Cisco PerfE host has an IP address assigned to the 10/100 Fast Ethernet network interface card. You can execute the netstat -nr command to see which interfaces and IP addresses are available and then select the IP address assigned to the interface you will be using. Step 4 At the Cisco PerfE host, verify connectivity to a network having another host that can act as an FTP server: % ping <ip_address_of_another_host> Step 5 Verify the checksum of the following Cisco PerfE script: % cksum getInput.sh 1795381629 4764 getInput.sh Step 6 This step is applicable only if you wish to configure the database and data directories. If you do not wish to configure database directories, go on to the next step. Create two directories on separate disks, one for the database and one for flat file data storage. During Solaris installation, you will be prompted for the location of these directories if you choose not to use the default directories for the database and data files. Enter the full path name of these directories during installation. For example: /db/cnsperfe_db /data/cnsperfe_data These directories can be given any name, however, for clarity, they are called cnsperfe_db and cnsperfe_data, respectively. Note Both directories must be owned by the dasadmin user. Step 7 If you plan to retrieve data from more than 800 devices, you must change the default file descriptors. By default, Solaris limits each process to opening a maximum of 1024 file descriptors. You can increase the maximum file descriptors setting in the /etc/system file: set rlim_fd_max=2048 After making this change, reboot the system. You can now change the maximum value in the das.properties file to the maximum value (2048): das.ulimit.maxOpenFiles=2048 For instruction on installing the Cisco PerfE software, continue to the following section. Installing the Cisco PerfE Software When installing the Solaris version of the Cisco PerfE software, you can choose to perform an interactive or a non-interactive installation. If you perform the interactive installation, you are prompted to provide the Cisco PerfE home, database, and data directories at various times during the installation procedure. If you perform the non-interactive installation, you create a script that provides the Cisco PerfE home, database, and data directories and stores the results in a file. Cisco PerfE retrieves the information from the file as needed during installation. For instructions on the interactive installation, refer to the following section. for instruction on the non-interactive installation, refer to the "Starting a Non-Interactive Installation" section Starting an Interactive Installation To perform an interactive installation of the Cisco PerfE software, follow these steps: Step 1 Change to the root user using the su command: % su root # Step 2 Install the Cisco PerfE software by going to the directory where the CSCOPerfE-solaris-2.1.5 file is located, then invoke the pkgadd command: # pkgadd -d CSCOPerfE-solaris-2.1.5 Step 3 Follow the instructions generated by the pkgadd program. The following is sample output of an interactive installation: The following packages are available: 1 CSCOPerfE Cisco CNS-PerfE (sparc) 2.1.5 Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: 1 Processing package instance <CSCOPerfE> from <CSCOPerfE-solaris-2.1.5> Cisco CNS-PerfE (sparc) 2.1.5 Copyright (c) 2001-2005 Cisco Systems, Inc. All rights reserved. This product is protected by copyright and distributed under licenses restricting copying, distribution and decompilation. Do you want to use the default base directory (/opt/CSCOPerfE)? [y,n,?] y Do you want to use the default database directory (/opt/CSCOPerfE/db)? [y,n,?] y Do you want to use the default data directory (/opt/CSCOPerfE/data)? [y,n,?] y Note If you want to use a non-default directory for the database or data, answer no to "Do you want to use the default...", then enter the absolute path to where you want the database or data to reside. The new base directory is set to /opt/CSCOPerfE ## Executing checkinstall script. Checking installation parameters... Using </opt/CSCOPerfE> as the package base directory. ## Processing package information. ## Processing system information. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of <CSCOPerfE> [y,n,?] y Please wait.installation in progress. Installation of <CSCOPerfE> was successful. Step 4 Enter the following command to verify that the Cisco PerfE package was installed: # pkginfo -l CSCOPerfE Refer to the "Directory Structure" section for information. Step 5 Exit the root user account: # exit Once you have installed Cisco PerfE, refer to the Cisco Performance Engine User Guide for detailed information on changing default properties, configuring the Cisco PerfE software, and the various Cisco PerfE collectors. Starting a Non-Interactive Installation To perform a non-interactive installation of the Cisco PerfE software, follow these instructions: Step 1 Copy getInput.sh to the /tmp directory. Step 2 Login as root: % su root # Step 3 Change directory to /tmp: # cd /tmp Step 4 Follow the instructions generated by the getInput.sh program: Do you want to use the default base directory (/opt/CSCOPerfE)? [y,n,?] y Do you want to use the default database directory (/opt/CSCOPerfE/db)? [y,n,?] y Do you want to use the default data directory (/opt/CSCOPerfE/data)? [y,n,?] y The new base directory is set to /opt/CSCOPerfE The database directory is set to /opt/CSCOPerfE/db The data directory is set to /opt/CSCOPerfE/data Do you want to use these values in installation (y)? [y,n,?] y Creating the installation administration file, /var/tmp/perfe/cnspe-admin... This script provides prompts for the Cisco PerfE home, database, and data directories and stores the results in the /var/tmp/perfe/cnspe-admin file which is used along with the pkgadd command. Step 5 Install the Cisco PerfE package as follows: # pkgadd -a /var/tmp/perfe/cnspe-admin -d CSCOPerfE-solaris-2.1.5 CSCOPerfE Step 6 The following is sample output generated by the pkgadd program: # sudo pkgadd -a /var/tmp/perfe/cnspe-admin -d CSCOPerfE-solaris- 2.1.5 CSCOPerfE Processing package instance <CSCOPerfE> from </tmp/2001install/CSCOPerfE- solaris-2.1.5> Cisco CNS-PerfE (sparc) 2.1.5 Copyright (c) 2001-2005 Cisco Systems, Inc. All rights reserved. This product is protected by copyright and distributed under licenses restricting copying, distribution and decompilation. ## Executing checkinstall script. Checking installation parameters... Using </opt/CSCOPerfE> as the package base directory. ## Processing package information. ## Processing system information. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. Installing Cisco CNS-PerfE as <CSCOPerfE> ## Executing preinstall script. preinstall script... Database directory: Data directory: ## Installing part 1 of 1. ... ... ## Executing postinstall script. Changing file permissions... changing owner and group settings... Installation of <CSCOPerfE> was successful. Step 7 Enter the following command to verify that the Cisco PerfE package was installed: # pkginfo -l CSCOPerfE Refer to the "Directory Structure" section for information. Step 8 Exit the root user account: # exit Once you have installed Cisco PerfE, you can continue on to the Installation Options section, or refer to the Cisco Performance Engine User Guide for detailed information on changing default properties, configuring the Cisco PerfE software, and the various Cisco PerfE collectors. Installing Cisco PerfE on a Linux Platform This section describes how to install Cisco PerfE on a Linux platform and includes the following: •Before You Begin •Installing the Cisco PerfE Software. Before You Begin This section describes the pre-installation procedures you should follow when you install Cisco PerfE version 2.1.5 on a Linux platform for the first time. If you are running a previous version of Cisco PerfE, remove the Cisco PerfE files using the uninstall instructions described in the "Uninstalling Cisco PerfE" section. The name of the Cisco PerfE installation files for the Linux version is: CSCOPerfE-2.1.5B08-0.i386.rpm Be sure to use the complete hostname during pre-installation procedures and installation procedures. Note Cisco PerfE administration must be done as the dasadmin user. Switching between users can cause permission denied problems. Step 1 Ensure the Cisco PerfE host has an IP address assigned to the 10/100 Fast Ethernet network interface card. You can execute netstat -nr to see what interfaces and IP addresses are available, then select the IP address assigned to the interface you will be using. Step 2 At the Cisco PerfE host, verify connectivity to a network having another host that can act as an FTP server: % ping <ip_address_of_another_host> Step 3 If you downloaded Cisco PerfE from the Cisco web site, ensure the checksum of the Cisco PerfE software package is correct: # cksum CSCOPerfE-2.1.5B08-0.i386.rpm 152621939 71414519 CSCOPerfE-2.1.5-0.i386.rpm Step 4 In order to display graphs, ensure the XFree86-libs RPM is installed. Step 5 For the Autostart feature to work properly, ensure the run level in the /etc/inittab file is set to 3(Multi User Mode): id:3:initdefault: Step 6 If you are planning on using the DOCSIS collector, ensure the ncurses4-5.0-5.i386.rpm RPM is installed. Note Use the --nodeps option to continue with the Cisco PerfE installation if the ncurses library version 4 is not installed. For instruction on installing the Cisco PerfE software, continue to the following section. Installing the Cisco PerfE Software To install Cisco Performance Engine software on a Linux platform, do the following. Step 1 Change to the root user using the su command: % su root Step 2 Install the Cisco PerfE software by invoking the rpm command: # rpm -i --nodeps CSCOPerfE-2.1.5B08-0.i386.rpm This command installs the Cisco PerfE software in the default /opt/CSCOPerfE directory. To install Cisco PerfE in a different directory, use the following command: # rpm -i --nodeps --prefix <install_dir> CSCOPerfE-2.1.5B08-0.rpm where <install_dir> is the full path name of the non default directory. Step 3 Use the rpm command to get RPM information about the CSCOPerfE directory: # rpm --query -i CSCOPerfE Step 4 Exit from the root user account: # exit Once you have installed Cisco PerfE, you can continue on to the Installation Options section, or refer to the Cisco Performance Engine User Guide for detailed information on changing default properties, configuring the Cisco PerfE software, and the various Cisco PerfE collectors. Installation Options After installing the Cisco PerfE software, you can choose to: •Install the Microsoft SQL JDBC driver in order to retrieve data from the Call Manager collector. •Install the Autostart feature to automatically start Cisco PerfE after your system has been rebooted. Refer to the following sections for instructions. Installing MS SQL JDBC for the Call Manager CDR Collector If you wish to retrieve data from the Call Manager collector, you must install the Microsoft SQL JDBC driver. Note The Microsoft SQL JDBC driver is only required if you plan on using the Call Manager CDR collector. To install the Microsoft SQL JDBC driver, do the following: Step 1 Download the SQL Server 2000 driver for JDBC Service Pack 1 (version 2.2.0029) from the following link: http://www.microsoft.com/downloads/details.aspx?FamilyID=4f8f2f01-1ed7-4c4d-8f7b-3d47969e66ae&DisplayLang=en Download the UNIX version: mssqlserver.tar Step 2 Install the Microsoft SQL JDBC as per instructions from the download website. Step 3 Copy the SQL Server JDBC libraries into the <CNS_PerfE_HOME>/tools/msjdbc directory as follows: a. Telnet and login into the Cisco PerfE host as dasadmin: > telnet <ip_address_CNS-PerfE_host> login: dasadmin Password: <password> b. Copy the jar files. For example, if the Microsoft SQL JDBC driver is installed in /opt/msSQLjdbc and Cisco PerfE is installed in /opt/CSCOPerfE, copy the libraries as follows: > cp /opt/msSQLjdbc/lib/.jar /opt/CSCOPerfE/tools/msjdbc/ Autostart The Autostart feature allows the system to automatically start Cisco PerfE after the computer system has been rebooted. Note Ensure the run level in the /etc/inittab file is set to 3. Note Ensure the login environment for the dasadmin account does not start Openwindows. Doing so could interfere with the successful restart of the application after the reboot. If the default shell for dasadmin is C-Shell, set TERM to vt100 in the .login file. If the default shell for dasadmin is the Bourne shell, set TERM to vt100 in the .profile file. Installing Autostart To install the Autostart feature, do the following: Step 1 Login as root. % root Step 2 Enter the following command: % <CNS_PerfE_HOME>/bin/autostart install Uninstalling Autostart To remove the Autostart feature, do the following: Step 1 Login as root. % root Step 2 Enter the following command: % <CNS_PerfE_HOME>/bin/autostart remove Starting and Stopping Performance Engine This section contains the following: •Starting Performance Engine •Checking the Cisco PerfE Servers Status •Starting the Performance Engine GUI •Stopping Cisco PerfE Starting Performance Engine To start Cisco PerfE, do the following: Step 1 Log as dasadmin: % dasadmin Step 2 Change directory to where Cisco PerfE is installed: % cd <CNS_PerfE_HOME>/bin Step 3 Start Cisco PerfE: % ./start.sh all Checking the Cisco PerfE Servers Status To check the status of Cisco PerfE servers, do the following: Step 1 Change directory to where Cisco PerfE is installed: % cd <CNS_PerfE_HOME>/bin Step 2 Check the status of the Cisco PerfE servers: % ./status.sh Starting the Performance Engine GUI To start the Cisco PerfE GUI, do the following: Step 1 Enter the following URL in Address field of your web browser: http://<hostname>:8080/cperfe Step 2 Enter dasadmin as the username and cisco as the password values. Refer to the Cisco Performance Engine User Guide for information on using the GUI to configure Cisco PerfE. Stopping Cisco PerfE To stop Cisco PerfE, do the following: Step 1 Change directory to where Cisco PerfE is installed: % cd <CNS_PerfE_HOME>/bin Step 2 Start Cisco PerfE: % ./stop.sh all Upgrading Cisco Performance Engine This upgrade procedure is used to upgrade the configuration and data from Cisco PerfE 2.1, 2.1.1. or 2.1.2 to 2.1.5. Cisco PerfE 2.1.5 introduces new database tables to store the GUI details and new columns are introduced to the CBQoS and System Collector tables. The upgrade script upgrades the Cisco PerfE 2.1, 2.1.1, or 2.1.2 database with these new tables and configuration files to the Cisco PerfE 2.1.5 installation. Requirement Cisco PerfE 2.1, 2.1.1, or 2.1.2 files must be backed up to a specific directory and the contents of this directory serve as input to the upgrade script. Note The upgrade log is available under <CNS_PerfE_HOME>/logs/upgrade.log. Recommendations •It is recommended that the Cisco PerfE 2.1, 2.1.1, or 2.1.2 files are backed up before upgrading so they can be restored later, if required. •User intervention is not allowed during an upgrade. If you interrupt the upgrade process, you get the following message on stdout: ***User interruption not allowed during upgrade** The upgrade is continued, however, it is recommended not to interrupt the upgrade process. Upgrade Considerations •The dasadmin username will be stored in the database (Password_Table). •CBQosTables will be upgraded with 20 new columns for Match Statement, Traffic Shaping, and Random Detect Statistics. •SystemCollector table will be upgraded with the new PerfE processes statistics. •Cisco PerfE configuration files (for example, das.properties and ddc) will be updated with the changed values. •Other files (such as those in the MIBs, templates, baselines, plugin, cli, and ioscli directories) will be copied to their respective locations. •If upgrading from 2.1, 2.1.1, or 2.1.2 to 2.1.5, be sure to upgrade the following property in the das.properties file if the secure password was not modified in an earlier installation: db.password.secure=vnMDzh7Q9RA= Note New MIBs introduced in Cisco PerfE 2.1, 2.1.1, or 2.1.2 are only copied to the Cisco PerfE 2.1.5 location. Therefore, if existing MIBs have been modified, these are not considered during the upgrade. Thus, you must explicitly modify these MIBs in 2.1.5 To upgrade, do the following: Step 1 Run stop.sh all to stop the Cisco Perf Engine 2.1, 2.1.1, or 2.1.2. This will allow you to create an offline backup. Step 2 Run backup.sh to backup the Cisco PerfE 2.1, 2.1.1, or 2.1.2 files to the <backup directory>. Note All files that are to be upgraded should be backed up. The default files to be backed up are specified in the <CNS_PerfE_HOME>/config/backup.files file. If you want to back up additional files, you should add them to the backup.files file. Step 3 Remove the Cisco PerfE 2.1, 2.1.1, or 2.1.2 installation. Step 4 Install Cisco PerfE 2.1.5. Step 5 Run backup.sh to backup the Cisco PerfE 2.1.5 files. Step 6 Run the upgrade tool (upgrade.sh) to upgrade the files: % cd <CNS_PerfE_HOME>/bin % ./upgrade.sh <backup directory> Step 7 Check that all of the properties files are updated with new values as set in the Cisco PerfE 2.1.5 properties files. For example, the das.properties, Db.properties, and ddc properties files. If an error occurs, go to Step 8. Otherwise, continue on to Step 9. Step 8 If an error occurs during the upgrade or the upgrade fails, run restore.sh to restore the Cisco PerfE 2.1.5 files. After a successful restore, go to Step 6. Step 9 To verify that the upgrade was successful, start Cisco PerfE and the Cisco PerfE GUI. Refer to the "Starting and Stopping Performance Engine" section. Once you have upgraded Cisco PerfE, you can continue on to the Installation Options section, or refer to the Cisco Performance Engine User Guide for detailed information on changing default properties, configuring the Cisco PerfE software, and the various Cisco PerfE collectors. Uninstalling Cisco PerfE Note Backup all configuration and data files you might need before uninstalling Cisco PerfE. To uninstall the Solaris or Linux versions of the Cisco PerfE software, follow these steps: Step 1 Telnet and login into the Cisco PerfE host as dasadmin: % telnet <ip_address_CNS_PerfE_host> login: dasadmin Password: <password> % Step 2 Change to the root user using the su command: % su root # Step 3 Switch to the /bin directory: # cd <CNS_PerfE_HOME>/bin Step 4 Uninstall the Cisco PerfE software by entering the command: # ./uninstall.sh Step 5 Exit out of the root user account: # exit
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks