Cisco Prime Infrastructure

Cisco Prime Infrastructure Best Practices

  • Viewing Options

  • PDF (907.7 KB)
  • Feedback

Scope. 3

Predeployment Best Practices. 3

Backup/Restore Best Practices. 3

Postinstall Best Practices for System Tuning. 4

References. 6


This document talks about some of the best practices that have been observed to improve overall health and performance of a Cisco Prime Infrastructure 1.3 application. This will be a live document and will be updated for each new release of Cisco Prime Infrastructure.

Predeployment Best Practices

Here are some best practices to help you make the most out of Cisco Prime Infrastructure as you plan to install a virtual appliance. Please use these design guidelines in addition to the server requirements before installing the application. A guideline in this section mainly applies to the virtual appliance and not to the Cisco Prime Appliance.

Customizing Your Virtual Infrastructure

   Cisco Prime Infrastructure requires a high performing data store for the underlying virtual infrastructure. The many sources of data that are fed to Cisco Prime Infrastructure demand such a data store. Using a Storage Area Network (SAN)-based data store is strongly recommended.

   Data store characteristics: For virtual infrastructure, we recommend having multiple (four or more) 15,000 revolution per minute (RPM) SAS drives operating in a RAID 1 or RAID 5 configuration. Cisco Prime Appliance comes with such high-speed drives out of the box in RAID 5 configuration.

   Please use SAN for higher and sustained I/O rates. Even though NAS-based volumes can be used for installing Cisco Prime Infrastructure Open Virtualization Archive (OVA) files, SAN is preferred over Network Attached Storage (NAS). NAS-based volumes also introduce more latency than SAN storage.

     Shared virtual machine (VM) resources will lead to performance issues later in the deployment cycle. (Refer to Cisco Prime Infrastructure 1.3 Quick Start Guide for more details on VM resources needed.) It is recommended for Cisco Prime Infrastructure VM to have some amount of “reserved” CPU/memory resources based on system load. For guaranteed performance we recommend that at least 50 percent to 60 percent of total CPU and memory be reserved. For larger deployment or more dynamic wireless environment, adding more “reserved” resources will guarantee consistent performance of the system. Common practice would be to start with 50 percent of “reserved” resources and to monitor the performance of the VM using vCenter. The “reserved” amount can be increased later if monitoring the results for a few days suggests it. Powering down a virtual machine is required for changing the allocated/reserved resources. Please refer to the VMware links in the Reference section (towards the end of the document) for detailed information on reserving resources.

Backup/Restore Best Practices

Guidelines in this section apply to the virtual appliance as well as Cisco Prime Appliance. Here are some of the tips you can use for backup and restore of your Cisco Prime Infrastructure VM.

VMware Virtual Infrastructure and Cisco Prime Infrastructure:

   VMware snapshots are supported, but snapshots are not recommended for normal production use.

   VMware snapshots may only be used to revert to a preupgrade/prerestore state, in case something goes wrong during upgrade/restore.

   Ideally one can delete the snapshot after the upgrade/restore is successful. This also frees up disk space required for the VM.

Note:    Snapshots will require a significant amount of additional space, up to two times the current disk space allocated, and you may encounter “insufficient storage available errors”if sufficient disk space is not made available.

Postinstall Best Practices for System Tuning

Now that you have finished installing the product, here are some additional guidelines that will help improve the performance.

The following changes can be made from the webGUI only, and only if you are running out of hard disk space or keep getting the warnings about disk utilization exceeding 65 percent.

   Delete long-term events if they are not needed. Go to Administration > System Settings > Alarms and Events. Delete all events after X days. By default 30 days’ worth of events are stored (as shown in the following image), but you can reduce the number if all that history is not needed.

   Reduce the time security alarms are kept. In the following image, we can see that the security alarms are stored for 30 days. If you can reduce that to 15 days, you can definitely get more performance out of the system.

   Similarly, Data Retention under Administration > System Settings can be customized to help optimize the system. The following Image shows how hourly aggregated value can be reduced to help with overall system performance.

   If you have a very high roaming client environment, it may help to reduce the amount of client session history (Administration > System Settings > Client) as shown in the following figure:

   After making all the preceding changes, if you are still experiencing space issues, you may need to increase the existing hard disk drive space.

Do not schedule multiple automated background jobs at the same time. By default, the tasks have been staggered and optimized for performance. The periodicity and frequency of user-scheduled jobs should not be too close to each other. This can also affect the performance of the overall system.

Using “ncs clean”: If there is a need to regain some hard disk space, users may use the “ncs clean” command. This script doesn’t initialize the database or lose any data, but it’s meant to do the following:

   Cleanup old log files and the staging directory

   Repair fragmentation in the disk

While running the “ncs clean” script you might be asked the following question:

Do you want to delete all the files in the local disk partition? (Y/N)

Answering yes to this question will do the additional following cleanup:

   Delete backup files stored in all local repositories (including DefaultRepo)

   Delete files copied to local repository by user

Users will be able to reclaim some disk space by doing these operations. The command-line interface (CLI) reference to “ncs cleanup” can be found at


   Cisco Prime Infrastructure 1.3 Release Notes

   Cisco Prime Infrastructure 1.3 Quick Start Guide

   Cisco Prime Infrastructure 1.3 Configuration Guides

   VMware and snapshots

     Understanding snapshots

     Find snapshots script

     VM and application monitoring

     CPU resource reservation

     Memory resource reservation