Cisco Prime Infrastructure

Release Notes for Update 1 for Cisco Prime Infrastructure

  • Viewing Options

  • PDF (331.1 KB)
  • Feedback
Release Notes for Update 1 for Cisco Prime Infrastructure

Table Of Contents

Release Notes for Update 1 for Cisco Prime Infrastructure


Installation Guidelines

Resolved Caveats

Open Caveats

Prime Infrastructure Supported Devices

Related Documentation

Obtaining Documentation and Submitting a Service Request

Release Notes for Update 1 for Cisco Prime Infrastructure

Last Updated: June 2013

These release notes contain the following sections:


Installation Guidelines

Resolved Caveats

Open Caveats

Prime Infrastructure Supported Devices

Related Documentation

Obtaining Documentation and Submitting a Service Request


This is a patch release for Prime Infrastructure This release delivers a number of critical bug-fixes. There are no new features added in this release. This patch release must be installed on top of your existing Prime Infrastructure

The bugs resolved in this release provide the following key functions:

Enables pre-backup check.

Provides error handling capabilities during the restore process.

As part of improvements to the backup, a signature file has been added in this patch release. The signature file is used during restore operation for further validation prior to restore so that failures can be avoided. Also, improvements have been made in reducing the backup size. The signature file provides the following key features:

Backup from larger OVA configurations to smaller OVA configurations is restricted and aborted.

Any unsuccessful backup operation with Bkp_Status as FAILED is used for fast restore fail and restore will be aborted immediately.

Recorded Bkp_DB_Size is used for better disk space validation on restore. If the required space is unavailable, then restore operation is aborted.

This release has fixes for maps, client troubleshooting, and client management. For details, see the "Resolved Caveats" section.

Note If you are upgrading from an earlier version of Prime Infrastructure, see the following URL to apply the necessary patches:

Installation Guidelines

Caution You cannot uninstall or remove this patch.

NoteIt is important to back up your system before applying this patch. Store the backup in an external repository. This will help you to revert to the original Prime Infrastructure state. To revert to original Prime Infrastructure state, follow these steps:

Reinstall Prime Infrastructure from an OVA or ISO distribution.

Restore data from the backup that you made before applying the patch.

Before you begin, remove any existing High Availability configuration from your primary and secondary Prime Infrastructure servers. You can do this using either of the following options:

Launch Prime Infrastructure, choose Administration > High Availability > HA Configuration, and click Remove.

Go to admin console and run the ncs ha remove command.

There is no need to shut down your server before installing this patch release. The patch installation will stop the application and restart it again.

There is no need to reboot your system manually after applying this patch.

The patch installation takes approximately 15-20 minutes.

Follow these steps to install the patch to your existing Prime Infrastructure system:

Step 1 Go to the following URL to download the PI_1_3_0_20-Update.1.12.tar.gz patch to your repository:

Step 2 Open a console session and log in to the existing server as admin. Enter the password when prompted.

Note If you want to know more about creating a remote repository, see the Setting Up Remote Repositories section of the Prime Infrastructure User Guide:

Step 3 Install the patch:

admin# patch install <patchFile> <repositoryName>


<patchFile> is the name of the patch file you copied.

<repositoryName> is the name of the repository that you configured.

Once the patch is installed successfully, you can verify the patch version using the following command:

admin# show version

Sample Output:

Version :
Patch: Cisco Prime Network Control System Version: Update-1_12_for_version_1_3_0_20

This patch version number is shown only when you use the show version command. On the Prime Infrastructure UI, only the base version number 1.3 ( appears.

For more information, see the following section of the Cisco Prime Infrastructure 1.3 Quick Start Guide:

Resolved Caveats

Table 1 lists the Resolved Caveats in this patch release.

Click the identifier to view the details of the caveat. This information is displayed in the Bug Toolkit. You can track the status of the resolved caveats, using the Bug Toolkit

Table 1 Resolved Caveats 



Sometimes adding or removing APs on the map or audit refresh of the controller takes long time when MSE is synchronized to these maps/controller.


Issue in Alarms generated for `Environment Temperature' Threshold


NCS clients and users page just spins if WLC interface is named `null'


Failed to start the reporting service process.


Unable to login with ''root'' user in the web user interface after upgrading from WCS to NCS and then Prime Infrastructure 1.2.


Client Troubleshooting window doesn't reflect the latest status of the client.


In Prime Infrastructure, the NCS Server Backup task may show that the job was successful, but no file can be found in the NFS file repository.


Difference between RMAN Archivelogs and disk contents causes DB crash


Prime Infrastructure 1.2 Interface license manager page no data available


Database does not start due to full db_recovery_file_dest_size after Upgrade


TACACS authentication takes time due to the delay in XMP module


The contents of the backup need to be optimized by removing unnecessary content in some directories.


Sometimes the devices go to managed with warning because of failures in feature discovery inventory collection when they are added in Prime Infrastructure.


After database restore, the user is unable to Switch Virtual Domain


There are three options under Site Maps > Properties—"Refresh Map from Network", "Advanced Debug Mode", and "Use Dynamic Heatmaps". These options some times do not save properly, and if you reload the page, they will not show the changes made and revert to previous state.


After modifying a map, when you click Save, the GUI hangs for minutes while the effected heatmaps recalculate.


Prime Infrastructure Upgrade fails during the schema migration


Oracle recovery area filling causes Prime Infrastructure to stop and not restart


Template Deploy Scheduler is not working for some PM times


At times, heat maps in Prime Infrastructure may be slow or stop altogether.


Backups from some NCS systems may not restore as expected.


Unable to create backup file sometimes


Assurance dashlets are empty after restore from 1.2.1 to 1.3.0


Wired client's database updatetime is reset to 0.


IFM InventoryServices API for getDevices with caching returns max 20


Oracle Audit Logging needs to be controlled


Prime Infrastructure may encounter an out of disk space condition that causes maps to be removed.


The Google Chrome browser stops working when you switch from LifeCycle theme to Classic.


Prime Infrastructure is not sending passwords to devices correctly for enable password.


SyslogHandler Flooded ncs*.log with error logs


Workaround for JVM Bug processing images with spaces


All ASR functionality broken in 1.3 - nbi


Prime Infrastructure stops while enabling High Availability if the secondary is unavailable.


Top N Clients dashlet does not show any data when the Traffic Type filter is set to "Traffic Out".


OOTB and Discovered Folder templates empty in 1.3.1 B&R & upgrade server


Flash crashed on the main page.


Negative SNMP object values are displayed as zero when polled using generic SNMP templates.


Offset in actual map in repositioning AP


Background tasks are not working correctly.


Process start up issues after removing the patch.


Application restore failed


Inconsistent backup size on Prime Infrastructure 1.3.1 system.


Support for NAM320 and a few Cat2960SF devices are unavailable in Cisco Prime Infrastructure Release 1.3.

Open Caveats

The open caveats listed in the Release Notes for Cisco Prime Infrastructure1.3 (apart from the resolved caveats listed in Table 1) are applicable to this patch release as well. For the list of open caveats of Cisco Prime Infrastructure1.3, see the following URL:

In addition to the caveats listed in this URL, the following caveats are open in this patch release.

Table 2 Open Caveats 



Configuration templates invisible for users such as Admin /Super Users/Config Managers in non root domain for PnP profile.


When you log in to non root domain with user as Admin and trigger PnP provisioning after creating template, the provisioning is not completed.


Current Associated Clients are not displayed Prime Infrastructure 1.2.


Prime Infrastructure keeps crashing when trying to import DWG.


Incorrect details recorded when a configuration template has managed variables


Prime Infrastructure displays null for device host names it cannot retrieve, causing pages like Virtual Domains to display incorrectly.


Discovery settings created in virtual domain appear in root-domain


WLC Image distribution failing for SNMP v2


Rogue AP is not shown in PI maps, but it appears in the Monitor > Alarms page.


Some access points in Prime Infrastructure appear in site maps, but do not appear in the Device Work Center.


PnP is not working with multiple interfaces in the Prime Infrastructure server.


At times, Prime Infrastructure's discovery of new access points can take a long time, causing other background tasks to take a long time to complete.


Unable to log in with RADIUS or TACACS credentials.


Newly added devices get into "In Progress" state forever


Unable to delete or edit IKE policy and IKE settings from device view


Control file missing in fast recovery area because of which database stop or start not happening.


Inaccurate data in client reports


SWIM copies the software image, but unable to process the boot command.


OOTB and Discovered Folder templates are empty.


Low disk space error appears in the Prime Infrastructure 1.3.1 standard machine.


Inventory.log is not purging and hence the size of the log keeps growing.


Applying any template through LifeCycle view to controller in Prime Infrastructure 1.3.1 is getting failed and not getting pushed to controller.


Configuration archive fails and an error message appears.


Server crashed and hence unable to launch the server.

Prime Infrastructure Supported Devices

For detailed information on the supported device types, see the following URL:

Related Documentation

You can access the additional Cisco Prime Infrastructure documentation at:

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

Subscribe to the What's New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.