Cisco Prime Infrastructure

Release Notes for Update 1 for Cisco Prime Infrastructure 1.4

  • Viewing Options

  • PDF (263.1 KB)
  • Feedback

Table of Contents

Release Notes for Update 1 for Cisco Prime Infrastructure 1.4


Virtual Appliance - Hardware Requirements

Browser Support

Supported Device Types and Software Versions

Installation Guidelines

Upgrading Cisco Prime Infrastructure

Submitting Feedback

Cisco Prime Infrastructure License

Cisco Prime Infrastructure Supported Devices

New Features and Enhancements

Support for New Antenna

Important Notes

Open Caveats

Resolved Caveats

Related Documentation

Obtaining Documentation and Submitting a Service Request


This is a patch release for Cisco Prime Infrastructure1.4 ( This patch must be installed on top of your existing Prime Infrastructure 1.4. This release supports two new AP platforms – Cisco 3700 and Cisco 1530 series access points (supported by WLC This release also delivers a number of critical bug fixes. The update 1 for Prime Infrastructure 1.4 enables you to manage Cisco WLC with the features of Cisco WLC and earlier releases. This release does not support any new features of Cisco WLC

For more information on the Prime Infrastructure release 1.4, see the following URL:

For more information on prerequisites, system requirements, and installation, see the following URL:

Virtual Appliance - Hardware Requirements

For information about the number and type of devices supported by each virtual appliance size, see the Product Specifications section of the Prime Infrastructure 1.2 data sheet at .

Browser Support

Prime Infrastructure supports the following browsers:

  • Google Chrome—28.0, 29.0 or 30.0
  • Mozilla Firefox— ESR 17.x, 17.0 or later
  • Microsoft Internet Explorer 8.0 or 9.0 with Chrome plug-in . Native Internet Explorer is not supported.

Note We recommend a minimum screen resolution of 1280 x 800 pixels.

Supported Device Types and Software Versions

Table 1 lists the wireless devices and their software versions that are supported by Prime Infrastructure.


Table 1 Supported Wireless LAN Controller Hardware Models and Software Versions

Controller Hardware Models
Controller Software Versions

Cisco 2100 Series


Cisco 2500 Series

7.0 through 7.61

Cisco 4400 Series


Cisco 5500 Series

7.0 through 7.61

Cisco Flex 7500 Series

7.0 through 7.61

Cisco 8500 Series

7.3 through 7.61

Cisco Virtual Controller

7.3 through 7.61

Cisco WiSM


Cisco WiSM2

7.0 through 7.61

Cisco Wireless Controller on Service Ready Engine (WLCM2 on SRE)

Cisco Catalyst 3750G Series Integrated Wireless LAN Controllers

7.0 through 7.61

1.Update 1 for Prime Infrastructure 1.4 enables you to manage Cisco WLC 7.6.x with the features of Cisco WLC and earlier releases.

Table 2 lists the Prime Infrastructure-supported devices for switches, wireless LAN controllers, access point images, Identity Services Engines (ISEs), and mobility services engines (MSEs).

Table 2 Supported Device Matrix for Switches, WLC, MSE, ISE, and AP

Supported Switches
Supported Controllers
Supported MSE Devices
Supported ISE Devices
Supported Lightweight APs
Supported Autonomous APs

Cisco Catalyst 2960, 2975 Switches [Cisco IOS Release 12.2(50)SE],

Cisco Catalyst 3560 Switches [Cisco IOS Release 12.2(50)SE],

Cisco Catalyst 3750 Switches [Cisco IOS Release 12.2(50)SE],

Cisco Catalyst 3850 Series Ethernet Stackable Switches

Cisco Catalyst 4500 Switches [Cisco IOS Release 12.2(50)SG],

Cisco Catalyst 6500 Switches [Cisco IOS Release 12.2(33)SXI],

Cisco NAM 2304 Appliance, Cisco NAM 2320 Appliance, Cisco IE 2000 Series Switches.

Cisco 2100 Series

Cisco 2500 Series

Cisco 4400 Series

Cisco 5500 Series

Cisco Flex 7500 Series

Cisco 8500 Series

Cisco Virtual Controller

Cisco WiSM

Cisco WiSM2

Cisco Wireless Controller on Service Ready Engine (WLCM2 on SRE)

Cisco Catalyst 3750G Series Integrated Wireless LAN Controllers

Cisco MSE 3355

Cisco ISE 1.0

Cisco ISE 1.1

Cisco ISE 1.2

Cisco 600 Series, Cisco 1040 AP, Cisco 1100 AP, Cisco 1120 AP, Cisco 1130 AP, Cisco 1140 AP, Cisco 1200 AP, Cisco 1230 AP, Cisco 1240 AP, Cisco 1250 AP, Cisco 1260 AP, Cisco 1500 AP,
Cisco 1524 AP,
Cisco 1552C AP,
Cisco 1552CU AP,
Cisco 1552E AP,
Cisco 1552EU AP,
Cisco 1552H AP,
Cisco 1600e AP,
Cisco 1600i AP,
Cisco 2600i AP,
Cisco 2600e AP,
Cisco 3500i AP, Cisco 3500e AP, Cisco 3500p AP,
Cisco 3600i AP, Cisco 3600e AP,
Cisco 3600i AP with 802.11ac module,
Cisco 3600e AP with 802.11ac module,
Cisco 3600p AP,
Cisco 700i AP,
Cisco 700e AP,
Cisco 802agn AP,
Cisco 802gn AP,
Cisco 802hagn AP,
Cisco 801gn AP,
Cisco 801agn AP,
Cisco 1532iAP,
Cisco 1532e AP,
Cisco 3702i AP
Cisco 3702e AP
Cisco 3702p AP

Cisco 1130 AP,
Cisco 1141 AP,
Cisco 1142 AP,
Cisco 1200 AP,
Cisco 1240 AP,
Cisco 1250 AP,
Cisco 1260 AP,
Cisco 1800 AP,
Cisco 800 ISR Series,
Cisco Aironet 1310 and 1410 Bridges,
Cisco 2600 AP,
Cisco 3500 AP,
Cisco 3600 AP,
Cisco 1600 AP,
Cisco 801 AP,
Cisco 1100 AP

For detailed information on the software compatibility for the Cisco wireless devices, see the following URL:

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

For detailed information on the Cisco MSE Virtual Appliance Product Specifications, see the following URL:

Installation Guidelines

Caution We do not recommend to uninstall or remove this patch.

Note • It 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 1.4 state. To revert to original Prime Infrastructure 1.4 state, follow these steps:

Reinstall Prime Infrastructure 1.4 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.

At the admin console 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 1.4 system:

Step 1 Go to the following URL to download the PI_1.4_0_45_Update_1-39.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:

This is a sample of the remote repository configuration.

admin(config)# repository myrepository
admin(config-Repository) #username anonymous password plain anonymous
admin(config-Reposotory) #exit


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_39_for_version_1_4_0_45

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.4 appears.

For detailed installation information, see the following Prime Infrastructure guides:


Upgrading Cisco Prime Infrastructure

If you are currently using Prime Infrastructure 1.4 you can upgrade to update 1 for Prime Infrastructure 1.4.

If you are running the previous releases of Prime Infrastructure, first upgrade to Prime Infrastructure 1.4 and then apply this patch.

For detailed information about the upgrade methods, see the following URL:

Submitting Feedback

Your feedback will help us improve the quality of our product. To send your feedback, follow these steps:

Step 1 If you have configured your mail server, go to Step 8.

Step 2 Choose Administration > System Settings > Mail Server Configuration .

Step 3 In the Mail Server Configuration page, enter the mail server details.

Step 4 Click Save to save the configuration settings.

Step 5 Choose Help > Help Us Improve Cisco Products .

Step 6 In the Help Us Improve Cisco Products page, choose the Yes, collect data periodically option.

Step 7 Click OK .

Step 8 Choose Help > Submit Feedback (in the Classic view) or click the question mark icon at the top right and then click Submit Feedback (in the LifeCycle view).

Note You must configure the e-mail server and then enable data collection to configure the feedback tool.


Cisco Prime Infrastructure License

For detailed information on the Cisco Prime Infrastructure Licensing, see the following URL:

Cisco Prime Infrastructure Supported Devices

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

New Features and Enhancements

Support for New Antenna

This release provides support for the antennas listed below:


Antenna Name
Gain (dBi)


Gain @ 2.4 GHz = 13 dBi,

Gain @ 5 GHz = 13 dBi


Outdoor, narrow beam, stadium

For details, see the following URL:


Gain @ 2.4 GHz = 3 dBi,

Gain @ 5 GHz = 5 dBi measured on AP3702

1600e, 2600e, 3600e, 3600p, 3700e, 3700p

Indoor, stubby dual band monopole

For details, see the following URL:


Gain @ 2.4 GHz = 4 dBi,

Gain @ 5 GHz = 7 dBi

1530e, 1550e

Outdoor, dual band, omnistick, gray

For details, see the following URL:

Important Notes

  • The Cisco IOS 12.2EWA image for the Cisco Catalyst 4948 does not work properly. Cisco Prime Infrastructure supports the Cisco IOS Release 12.2SG image for the Cisco Catalyst 4948 series. This is because of different sysOId's returned by Cisco IOS images.
  • For the TACACS+/RADIUS user authentication, the custom attributes related to the new features are required to be added/appended to the existing set of attributes in the AAA server to access certain pages/views. For RADIUS authentication and authorization in Prime Infrastructure, there is an alternate method available for the AAA users. Only the user role and virtual domain attributes can be configured in the AAA server (instead of copying the complete custom attribute task list from Prime Infrastructure to the AAA server).
  • After performing a major version upgrade of the Prime Infrastructure application, the browser cache on the client machines used to access the older version need to be cleared once so that the data for the old application is removed from the browser cache. Afterward connecting to the upgraded server works fine.
  • Prime Infrastructure uses the "show run-config commands" command to archive the configuration from WLC, but passwords are masked with asterisk characters (*) in the command output. When you rollback the archived configuration which contains the configuration lines with masked passwords, the operation fails.
  • You cannot apply wIPS profile to WLC 7.5 and earlier release using Prime Infrastructure 1.4.x with MSE 7.6 release.
  • SWIM Image Management and Supported Devices—Table 3 provides a brief overview about the different processes involved in managing software images and whether the processes are supported in the Unified Wireless LAN Controllers and devices.


Table 3 Software Image Management Processes and Supported Devices

Software Image Management Processes
Unified WLCs
Catalyst 3850 Switches (Cisco IOS XE 3.2.1)

Image import from device

Ability to import software image from devices that are already deployed to Prime Infrastructure. The software image can then be distributed to other devices.

Not supported because the software image cannot be reassembled into a package.


Image import from file

Ability to import software image from known location on a file server to Prime Infrastructure. The software image can then be distributed to other devices.



Image import from URL

Ability to import software image from network accessible locations (URI/URL) to Prime Infrastructure. The software image can then be distributed to other devices.



Image import from

Ability to import software image from a trusted Cisco website to Prime Infrastructure. The software image can then be distributed to other devices.



Image upgrade/distribution

Ability to upgrade software image on the managed devices from Prime Infrastructure. This allows you to update software image for multiple devices based on demand or at a later point in time as scheduled. The feedback and status are displayed during the upgrade and devices can be restarted, if required. In large deployments, you can stagger reboots so that the service at a site is not completely down during the upgrade window.



Image recommendation

Ability to recommend a compatible image for the devices that are managed from Prime Infrastructure.

Not supported because the flash requirement is not available.


Image upgrade analysis

Ability to analyze the software images to determine the hardware upgrades required before you can perform the software upgrade.

Not supported because there is no minimum requirement for RAM or ROM. The newly upgraded image replaces the existing image after an upgrade.


  • SWIM and Configuration Archives support for Devices during Prime Infrastructure releases—Table 4 outlines the devices that the software image management and configuration archives support during the various Prime Infrastructure releases.


Table 4 SWIM and Configuration Archives support for Devices during Cisco Prime Infrastructure Releases

Cisco Prime Infrastructure releases

Cisco 4400 Wireless LAN Controller2

1.2, 1.3, and 1.4

Cisco 5500 Series Wireless LAN Controllers

1.2, 1.3, and 1.4

Cisco WiSM1 Controller

1.2, 1.3, and 1.4

Cisco 2106 Wireless LAN Controller1

1.2, 1.3, and 1.4

Cisco 2504 Wireless LAN Controller

1.2, 1.3, and 1.4

Cisco 2800 and 3800 Series Integrated Services Routers

1.2, 1.3, and 1.4

Cisco Flex 7500 Series Wireless LAN Controller

1.2, 1.3, and 1.4

Cisco 8500 Wireless LAN Controller1


Cisco Virtual Wireless LAN Controller1


Cisco WiSM2 Controller

Not supported

2.PI 1.4 does not support SWIM in Cisco 2106/4400/8500/WiSM2/Virtual WLC.

Open Caveats

Table 5 lists the open caveats in this patch release.

Click the identifier to view the impact and workaround for the caveat. This information is displayed in the Bug Search Tool . You can track the status of the open caveats using the Bug Toolkit.


Table 5 Open Caveats



Hourly Aggregation task does not run for several hours.


HA registration fails in dual NIC configured servers.


PI throws AVC exception while creating two templates with same name and rule.


Unable to download MSE software via NCS 1.4. This occurs when you try to download from the latest image.


A deletion confirmation pop-up appears continuously, even after deleting an ACS view server.


Advanced filter result displays incorrect information when you filter it based on client endpoint type.


AP1532i antenna designation uses a number (Internal-1550 antenna) which is not similar to the AP name.


Alarm summary dashlet issue in life cycle view.


Processes are not up after restarting the PI server.


The MSE column in the Client List page is empty even for the clients detected by MSE.


Error occurs when you try to delete the template. This occurs if you had already applied the template on controller(s).


Adhoc Rogue clients does not show up consistently on Monitor > Security, or Home > Security, whereas it is seen on the PI Alarms.


QoS validation for average and burst data rate is missing in WLAN template.


When you click the "wireless clients in outdoor area" link from the home page, it does not display any data.


The Monitor Controller Client count does not match with what is displayed in the client list page.


AutoSPT detects Rogue as on wired, even though rogue AP does not exist on wired.


When you change the reporting criteria of unique client report from SSID to All and try to run the report, PI throws a script error and fails to run the report.


PI fails to validate SSH/telnet AP, if the AP has default username/password.


Error appears when you select the move building option.


Auto SwitchPort Trace feature detects rogue APs on the wire, even after the rogue AP is removed from the switch.


When Unique Client Summary report is run for ALL reporting category, PI reports incorrect data for Average Users per AP when the system has both wired and wireless clients.


Incorrect error message appears when you create two monitor templates with same monitor name.


Client Trap Threshold configuration missing in controller template.


When you try to duplicate and save SFTP server details from Configure > Scheduled Task > Download Software Task > New Task, a blank page appears.


PI fails to apply mesh parameter via AP template to 1532 AP.


"Daisy Chaining" check box is missing in PI.


"APs default" data rate option is not available in PI.


Graphical report is not generated, when you create and run throughput report by "Floor Area" or "AP by Floor Area" for clients of any protocol for any duration.


Unable to see all the clients in the Monitor > Map of NCS.


Unclear error message appears when the template fails to do configurations on a controller.


When MSE is already added to PI, try to enable HA. You will notice that HA registration fails and MSE is shown as unreachable.


SNMP error occurs when you configure channel bandwidth on 802.11a/n radio of an AP via LWAP template and when the channel assignment method on AP is Global.


Heatmaps are not displayed when you place a 3700P AP on a Floor map with antennae AIR-ANT2513P4M.


802.11a/n/c interface of AP 3700P is shown as 802.11ac in Alarms and Events pages.


When you compare the client count report generated by "AP by controller" and "client count for All" for a period greater than one day, you will notice that the reports are not the same.


PI displays SNMP operation failure error, when you enable SSH for the AP and click on save.


When you run awIPS Alarm reports on PI, MSE server takes longer time to collect the data and the report generation fails.


Spectrum Expert for 2.4GHz band is launched only from WSSI module page.


PI server does not startup automatically even if the system is rebooted.


For open caveats in Prime Infrastructure 1.4, see the following URL:

Resolved Caveats

Table 6 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 Search Tool . You can track the status of the resolved caveats, using the Bug Toolkit.


Table 6 Resolved Caveats



Unable to apply AP Templates through WLC as SNMP timeout is too short and is set to one second.


Prime Infrastructure stops responding and back trace indicates that carsGetDiskUsageStats is involved.


A vulnerability in the login page of UI, allows an authenticated local attacker to inject scripts into the login disclaimer of the login page.


Unable to see link showing SNR on outdoor maps for MESH APs.


Environmental temperature data are not collected for switches.


Position AP loses mouse focus.


Unable to login to PI after installing signed certificate from CA.


Device 360 view takes a longer time to display the interfaces.


Background task in the NCS system gets delayed.


Alarm Summary shows minor performance alarms whereas the detailed alarm page shows no data.


Unable to click history link from Configuration Template > Deploy page.


Grouping is not set up correctly in upgrade.


Report shows "alert" for Rogue APs that are removed.


Error occurs when "Apply to AAPs" button is clicked.


PI 1.2 SWIM Recommendation and Upgrade Analysis do not work with SSH.


JDBC Driver stops functioning.


Report statistics look incorrect.


11ac Client on the Map does not show the correct protocol.


SWIM importing from fails for K9 images.


Missing indexes after upgrade or ncs cleanup.


Quick search of Rogue AP fails.


HA does not come up when failover is initiated from primary.


In PI 1.3.1, standard machine Inventory log instance keeps on increasing up to 50.


PI 1.3 Alarm Panel issues.


In PI 1.3.1, Config archive fails with device unreachable message.


"Refresh config from controller" processing fails when there are more than 1,800 guest user accounts.


In PI 1.3, client count is intermittently not reported and the process fails.


No indication of a search in progress.


PI location accuracy tool stops responding for a particular image on the floor.


The Email Notifications page in PI has some duplicate categories.


The SWIM distribution task keeps running even after the image is distributed successfully on controller.


SQL Query causing performance issues.


Prime Infrastructure may not accurately report the information collected by a Class Based QoS monitoring template.


Deletion of Custom SNMP template causes incorrect data.


AP Groups are not in alphabetical order.


Deleted entries on device are still shown in NCS after synchronization.


APs on maintenance mode within PI will still receive critical alarm.


Restore fails on a freshly installed PI 1.3.x system due to swap issues.


Audit mismatch dot11n/refresh config warning with missing key validation.


PI does not shutdown properly, when shutdown is done from VCenter UI.


Sorting non-indexed column in client list page, has performance issue.


Hibernate exception occurs while accessing Alarm NBI API on 1.3.1.


No proper message when Mesh AP is configured with global channel.


Username and passwords are shown clearly in the logs.


Device reaching MWW due to OSPFv4 OOB configuration.


Client Counts dashlets have incorrect values when filtered by SSID.


Throughput of client is not showing up correctly in the executive summary report.


Unable to configure webauth to external on WLAN.


Prime Infrastructure 1.3/1.4 takes up to 2 minutes to load the Home page.


PI 1.3 heatmaps are not shown on 1600 Antennas.


AP detail page (Monitor > APs) does not load.


Base station pruning fails due to upgrade from PI 1.3.1 to PI 2.0.x.


3700 AP's Radio interface name should be consistent across all pages in PI.


Unable to add a 3600 AP with 11ac module to a Floor Map.


Changing the time period in lifecycle view dashlet, does not refresh the dashlet data.


Antenna images shown are incorrect for some antennas in Maps.


Chrome upgrade to Version 29.0.1547.57 m causes error.


RF profile to AP groups throws exceptions.


Discrepancy in the controller port status summary on two PI 1.4 servers.


Saving configuration in radio page of 1532 AP shows error.


Montserrat AP's 5 GHz radio is shown as 802.11a/n when dissociated.


Unable to access the radio config pages of a 702I AP.


Client protocol for 11n Clients are shown as 11g on the Floor Maps.


Throughput Report by 11ac protocol is not plotting the data.


Unable to set Webauth to None once configured.


Save and Reset buttons are missing in EIGRP.


Table which pops up on clicking AP in the PI 1.4 maps, always shows 802.11a/n.


When the 802.11ac radio of an X Ale AP becomes operationally down, the alarm reports that the 802.11a/n radio interface is down.

Related Documentation

You can access the additional 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.