Cisco Prime Infrastructure 3.7.1 Release Notes
Introduction
This is the first maintenance release for Cisco Prime Infrastructure 3.7.1
You can install Cisco Prime Infrastructure 3.7.1 Maintenance Release on Cisco Prime Infrastructure 3.7. Prime Infrastructure 3.7.1 Maintenance Release file PI_3_7_1-1.0.22.ubf is approximately 183 MB. The downloading time depends on the available network connection in the enterprise environment. Ensure that you have adequate bandwidth and are not running into high latency issues.
Cisco End User License Agreement
This software is governed by the Cisco End User License Agreement available at the following URL:
http://www.cisco.com/c/en/us/td/docs/general/warranty/English/EU1KEN_.html
Cisco Prime Infrastructure 3.7 collects anonymous usage data to help improve the product. By using this product, you are providing your consent to collect your usage data.
For more information, or to opt out at any time, go to Administration > Settings > System Settings > General > Help Us Improve.
System Requirements
Supported Physical Appliance Environments
-
Prime Infrastructure 3.7.1 is supported on the Cisco Prime Infrastructure Physical Appliance (Gen 2 and Gen 3). For more information, see the Physical Appliance Options section in the Cisco Prime Infrastructure 3.7 Quick Start Guide.
-
Prime Infrastructure 3.7.1 is not supported in the Cisco Prime Infrastructure Physical Appliance (Gen 1). For more information on installation, upgrade, and migration from Prime Infrastructure 3.0.x to Prime Infrastructure 3.7.1 Gen 1 Appliance, see the Prime Infrastructure 3.1.4 Generation 1 Upgrade and Migration Guide.
Supported Virtual Appliance Environments
-
Prime Infrastructure 3.7.1 is supported on the Cisco Prime Infrastructure Virtual Appliance (VMware). For more information, see the Understand System Requirements section in the Cisco Prime Infrastructure 3.7 Quick Start Guide.
-
Prime Infrastructure 3.7.1 is supported on the Cisco Prime Infrastructure Virtual Appliance (Microsoft Hyper-V) For more details, see the Cisco Prime Infrastructure 3.7 Installation and Migration Guide for Microsoft Hyper-V Virtual Machine .
Supported Web Client Requirements
For more information on the web client requirements, see the Web Client Requirements section in the Cisco Prime Infrastructure 3.7 Quick Start Guide.
Installation Guidelines
The following sections explain how to install the maintenance release.
Before You Begin Installing the Maintenance Release
 Caution |
Once you install this maintenance release, you cannot un-install or remove it. |
Since the maintenance release is not removable, it is important to have a way to revert your system to the original version in case hardware or software problems cause the maintenance release installation to fail.
To ensure you can do this, take a backup of your system before downloading and installing this UBF maintenance release.
If the backup is a Prime Infrastructure 3.7 backup, restore the backup on Prime Infrastructure 3.5 server before applying the Maintenance Release 3.7.1.
Similarly, if you are running Prime Infrastructure 3.7 in a Virtual Machine (VM) and your organization permits taking VM snapshots, stop Prime Infrastructure and use the VMware client to take a VM snapshot before applying this maintenance release. Store the snapshot in an external storage repository, and restore from the snapshot if the maintenance release installation is unsuccessful. For more details, see Restore an Application Backup in the Cisco Prime Infrastructure 3.7 Administrator Guide .
To restore the backup of the Prime Infrastructure 3.7 installation, follow these steps:
-
Install Prime Infrastructure 3.7 from an OVA or ISO distribution.
-
Clear the Cache and log in to Prime Infrastructure GUI again and proceed with the Prime Infrastructure 3.7.1 upload.
If you are installing this maintenance release as part of a High Availability (HA) implementation, see Before You Begin Setting Up High Availability in the Cisco Prime Infrastructure 3.7 Administrator Guide .
Installing the Maintenance Release from Cisco Site
Caution |
If you have a High Availability (HA) environment, remove the HA setup before proceeding to install this Maintenance Release. For more details, see Installing the Maintenance Release in High Availability Mode. |
Make sure that you have completed the recommended preparation steps given in Before You Begin Installing the Maintenance Release.
To install Cisco Prime Infrastructure 3.7.1 from the Cisco site, follow these steps:
Procedure
| Step 1 |
Log in to the Prime Infrastructure 3.7 server. |
||
| Step 2 |
Choose Administration > Licenses and Software Updates > Software Update. |
||
| Step 3 |
Click Download. |
||
| Step 4 |
Log in with your cisco.com credentials and click Yes or No in the Remember Credentials pop-up dialogue box. |
||
| Step 5 |
Click Show Details in the Critical Fixes pane to view the updates. |
||
| Step 6 |
Click Download corresponding to the Prime Infrastructure 3.7.1 Maintenance Release file name PI_3_7_1-1.0.22.ubf . |
||
| Step 7 |
Click Install to install the maintenance release. |
||
| Step 8 |
Click Yes in the popup dialogue box to install Cisco Prime Infrastructure 3.7.1. It may take approximately 30 minutes for the installation process to complete.
|
||
| Step 9 |
You can verify the maintenance release installation from Prime Infrastructure Login under Critical Fixes by clicking View Installed Updates and also by logging into the server and choosing Administration > Software Update. You should see a listing for the maintenance release in the Updates tab, with Installed in the Status column. |
Installing the Maintenance Release from Local Storage
Caution |
If you have a High Availability (HA) environment, remove the HA setup before proceeding to install this Maintenance Release. For more details, see Installing the Maintenance Release in High Availability Mode. |
Make sure that you have completed the recommended preparation steps given in Before You Begin Installing the Maintenance Release.
To install Cisco Prime Infrastructure 3.7.1 from the local storage, follow these steps:
Procedure
| Step 1 |
Download the Prime Infrastructure 3.7.1 Maintenance Release PI_3_7_1-1.0.22.ubf from Home > Products > Cloud and Systems Management > Routing and Switching Management > Network Management Solutions > Prime Infrastructure > Prime Infrastructure 3.7 > Prime Infrastructure Patches-3.7.1 and save the file in your local system. |
||
| Step 2 |
Log in to Prime Infrastructure 3.7 server. |
||
| Step 3 |
Choose Administration > Licenses and Software Updates > Software Update. |
||
| Step 4 |
Click Upload and browse to the location where you have saved the maintenance release file. Click OK to upload the file. |
||
| Step 5 |
In the Status of Updates pane, click the Files tab and check whether PI_3_7_1-1.0.22.ubf is listed under FileName column. |
||
| Step 6 |
In the Critical Fixes pane, click Install. |
||
| Step 7 |
Click Yes in the pop-up dialogue box to install Cisco Prime Infrastructure 3.7.1. It may take approximately 1 hour for the installation process to complete.
|
||
| Step 8 |
You can verify the maintenance release installation from Prime Infrastructure Login under Critical Fixes by clicking View Installed Updates and also by logging into the server and choosing Administration > Software Update. You should see a listing for the maintenance release in the Updates tab, with Installed in the Status column. |
Installing the Maintenance Release in High Availability Mode
Download the Prime Infrastructure 3.7.1 Maintenance Release PI_3_7_1-1.0.22.ubf from Home > Products > Cloud and Systems Management > Routing and Switching Management > Network Management Solutions > Prime Infrastructure > Prime Infrastructure 3.7 > Prime Infrastructure Patches-3.7.1 and save the file in your local system .
To install the downloaded Prime Infrastructure 3.7.1 Maintenance Release PI_3_7_1-1.0.22.ubf in High Availability mode follow the below prerequisites:
-
Make sure that you have completed the recommended preparation steps given in Before You Begin Installing the Maintenance Release.
 Note |
Prime Infrastructure 3.7.1 can be applied only in primary and secondary standalone servers. The server will restart automatically once the installation is complete. The restart typically takes 25 to 35 minutes. You cannot apply Prime Infrastructure 3.7.1 when HA is enabled. |
-
If you are installing Cisco Prime Infrastructure Maintenance Release 3.7.1 on High Availability (HA) paired servers, you will get the following error message:
For more details, see Remove HA Via the GUI in the Cisco Prime Infrastructure 3.7 Administrator Guide.
-
Continue the patching once HA removed completely. For more details, see the How to Patch New HA Servers section in the Cisco Prime Infrastructure 3.7 Administrator Guide .
Troubleshooting Maintenance Release Installs in High Availability Implementations
If you are unable to apply this maintenance release in a High Availability (HA) implementation, check whether your network bandwidth, throughput and latency meets the network requirements recommended in Network Throughput Restrictions on HA section in the Cisco Prime Infrastructure 3.7 Administrator Guide. In a few cases, continued or intermittent throughput problems can cause a complete failure. If you believe this has occurred, contact Cisco TAC for support.
If you are unable to verify that this maintenance release has been successfully installed on a Prime Infrastructure server, or one or both of the servers fails to restart properly after installing the maintenance release, you may need to re-image the server as explained in Before You Begin Installing the Maintenance Release before continuing.
In all cases, you can use the backup-logs command on one or both servers to get information on the source of the failure. For more information, see the back-logs section in the Cisco Prime Infrastructure 3.7 Command Reference Guide .
Renewing AAA Settings After Installing a New Prime Infrastructure Version
If you are using external RADIUS or TACACS+ user authentication, before migrating your existing data to a new version of Prime Infrastructure, you must transfer the expanded Prime Infrastructure user task list to your AAA server. After you upgrade Prime Infrastructure, you must re-add any permissions on the TACACS+ or RADIUS server and update the roles in your TACACS server with the tasks from the Prime Infrastructure server. For more details, Configure External Authentication section in the Cisco Prime Infrastructure 3.7 Administrator Guide.
Migrating from Previous Releases of Cisco Prime Infrastructure
You can restore the backup from the following Prime Infrastructure versions to Prime Infrastructure 3.7.1:
-
Cisco Prime Infrastructure 3.0.0.78
-
Cisco Prime Infrastructure 3.0.1
-
Cisco Prime Infrastructure 3.0.2
-
Cisco Prime Infrastructure 3.0.3
-
Cisco Prime Infrastructure 3.1.0.0.132
-
Cisco Prime Infrastructure 3.1.1
-
Cisco Prime Infrastructure 3.1.2
-
Cisco Prime Infrastructure 3.1.3
-
Cisco Prime Infrastructure 3.1.4
-
Cisco Prime Infrastructure 3.1.5
-
Cisco Prime Infrastructure 3.1.6
-
Cisco Prime Infrastructure 3.1.7
-
Cisco Prime Infrastructure 3.2
-
Cisco Prime Infrastructure 3.2.1
-
Cisco Prime Infrastructure 3.2.2
-
Cisco Prime Infrastructure 3.3.1
-
Cisco Prime Infrastructure 3.4
-
Cisco Prime Infrastructure 3.4.1
-
Cisco Prime Infrastructure 3.4.2
-
Cisco Prime Infrastructure 3.5
-
Cisco Prime Infrastructure 3.5 Update 01
-
Cisco Prime Infrastructure 3.5 Update 02
-
Cisco Prime Infrastructure 3.5 Update 03
-
Cisco Prime Infrastructure 3.5.1
-
Cisco Prime Infrastructure 3.6
-
Cisco Prime Infrastructure 3.6 Update 01
-
Cisco Prime Infrastructure 3.6 Update 02
-
Cisco Prime Infrastructure 3.6 Update 03
-
Cisco Prime Infrastructure 3.7
If you are running multiple previous releases of Prime Infrastructure (for example, you are running version 3.0.0.78 and 3.0.1, 3.0.2, 3.0.3, 3.1.0.0.132), you must select one version from which to restore data.
See Before You Migrate Your Data in the Cisco Prime Infrastructure 3.7 Quick Start Guide before you restore your data from Prime Infrastructure 3.0.x or 3.1 to your newly installed Prime Infrastructure 3.7 server:
You can apply the Cisco Prime Infrastructure 3.7.1 over Cisco Prime Infrastructure 3.7 upgraded server. For detailed information about upgrading from previous releases of Prime Infrastructure, including the list of versions from which you can upgrade, see the How to Upgrade From Previous Releases of Prime Infrastructure section of the Cisco Prime Infrastructure 3.7 Quick Start Guide.
Submitting Feedback
Your feedback will help us improve the quality of our product. You must configure the email server and then enable data collection to configure the feedback tool. To send your feedback, follow these steps:
Procedure
| Step 1 |
If you have configured your mail server, go to Step 4. |
| Step 2 |
Choose Administration > Settings > System Settings > Mail and Notification > Mail Server Configuration. |
| Step 3 |
In the Mail Server Configuration page, enter the mail server details, then click Save to save the configuration settings. |
| Step 4 |
Choose Administration > Settings > System Settings > General > Help Us Improve. |
| Step 5 |
In the Help Us Improve Cisco Products page, select Yes, collect data periodically, then click Save. |
| Step 6 |
Click the Settings icon, then select Feedback > I wish this page would ... . |
| Step 7 |
Enter your feedback, then click Submit Feedback. |
Prime Infrastructure Licenses
Supported Devices
To see the list of devices supported in this release of Prime Infrastructure, follow these steps:
Procedure
| Step 1 |
Log in to Prime Infrastructure. |
| Step 2 |
Click Settings to see the list of settings options |
| Step 3 |
Click Supported Devices List under Help. |
What to do next
You can also view the Cisco Prime Infrastructure 3.7 Supported Devices list at the following URL:
For detailed information on the software compatibility for the Cisco wireless devices, see the following URL:
https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
New Features and Enhancements
Important Notes
-
Prime Infrastructure 3.7 Update 03 is mandatory to be installed before Prime Infrastructure 3.7.1.
-
In addition to installing Prime Infrastructure 3.7.1 on Prime Infrastructure instances, make sure that you also install Prime Infrastructure 3.7.1 on Prime Operations Center.
-
Prime Operations Center 3.7.1 manages Prime Infrastructure 3.7.1. You must ensure that Prime Operations Center version is the same as the version of the Prime infrastructure instances that it manages. For more details, see Set Up Operations Center in Cisco Prime Infrastructure 3.7 Administrator Guide .
You can install Prime Infrastructure 3.7.1 on operations center from the Cisco Site, or local storage. You can also install the update in high availability mode if the high availability is available on Prime Operations Center. For more details on how to install the update, see Installation Guidelines.
After installing the update, enable HA for Operations Center. For more details, see Enable HA for Operations Center in Cisco Prime Infrastructure 3.7 Administrator Guide .
-
If the email address contains numeric value (e.g. 123456@xyz.com), the email notification sent to the email destination will contain only the alarm instance ID.
-
CLI templates and Guest users cannot be deployed from Wireless Configuration Groups.
-
Cisco Prime Infrastructure does not support monitoring for Cisco Application Control Engine (ACE) module, because ACE has been moved to end-of-life and does not respond to related monitoring MIBs.
-
If the Boot Option in the BIOS settings is enabled with UEFI shell, deployment gets completed. Once deployment gets completed, it fails to enter the configuration mode, instead enters the shell mode in the CIMC console. UEFI shell option must be disabled in the BIOS settings to access configuration mode.
-
If VIP is enabled, after failover or fallback, SSO server should be added again in Prime Infrastructure for the auto login to work.
-
It is recommended to use different web browsers to avoid from menus getting affected while loading in ISE, during the cross launching of ISE reports from Cisco Prime Infrastructure and logging in to ISE Admin.
Open Caveats
Table 1 lists the Open Caveats in Cisco Prime Infrastructure Release 3.7.1.
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 Search Tool .
|
Identifier |
Description |
|---|---|
|
Select all devices using the “Select All” checkbox doesn't work on Windows 10 and Chrome browser. |
|
|
Seamless login from Prime Web to MSE stopped working after upgrade. |
|
|
Duplicate entry in Inventory for each wireless controller which got migrated to Prime Infrastructure 3.2.2 update 2. |
|
|
Deletion of 1000+ APs does not reflect in Front end (UI). |
|
|
Interface details are not displayed while using Prime Infrastructure in Japanese. |
|
|
In Topology page, the pie chart does not show the severity on cross launching from alarm summary. |
|
|
Table view is displayed instead of Template view while creating a template. |
|
|
While executing a Configuration Deploy job in Prime Infrastructure, the job status displays the status as successful even though the commands are not deployed successfully on the device. |
|
|
Internal Temperature for Dao (9800-80) displays 0 in the Device Details page. |
|
|
Non-AP Meraki devices are categorized as Access points in Prime Infrastructure. |
|
|
In Prime Infrastructure, certain functions are not virtual domain aware which causes the users across different virtual domains to save or change values. |
|
|
After password recovery, an unwanted message is printed while startup. |
|
|
Reboot issue in Gen-3 Appliance. |
|
|
Issues in deploying a configuration template. |
Resolved Caveats
Table 2 lists the bugs resolved in Prime Infrastructure 3.7.1.
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 resolved caveats using the
|
Identifier |
Description |
|---|---|
|
Devices are not visible in the Network Devices tab under All Devices. |
|
|
After upgrading from Prime Infrastructure 3.0 to 3.1, the devices are not showing in the Topology Device Groups. |
|
|
Unable to deploy WLAN Template with Flex Local Auth enabled. |
|
|
The polling Prime Infrastructure's Client Details API fails if the value of the ClientApModeEnum is greater than 4. |
|
|
End User Experience dashlet does not load data when client filter contains a backslash character. |
|
|
Prime Infrastructure's non-root users who are not mapped to ROOT-DOMAIN cannot run the capture copy or view the jobs. |
|
|
Netflow data displayed in NAM and Prime Infrastructure does not match for the same devices and time period. |
|
|
Old AP name is getting displayed in the GUI after changing the name through Prime Infrastructure API. |
|
|
The application created in the Applications and Services Page is not displayed in the All Applications table of Japanese GUI. |
|
|
Prime Infrastructure does not allow a user in a noon-root virtual domain to edit maps. |
|
|
Prime Infrastructure displays incorrect model name in the device hardware EOX report. |
|
|
Prime Infrastructure may not copy and replace the APs as expected. |
|
|
Prime Infrastructure generates the “Poller_PostLradIfChannelStatsRecord Unknown Exception” error and floods an associated syslog server. |
|
|
In Prime Infrastructure 3.5, the lradtemplate does not load in the UI. |
|
|
“With Unified APs, Prime Infrastructure shows a Permission Denied error when you click the Configuration tab.” |
|
|
The Top N Memory Utilization dashlet does not filter devices while selecting a site. |
|
|
In Prime Infrastructure, the ReachableAp5MinuteAggregator table is missing. |
|
|
The /op/configArchiveService/extractSanitized File returns content in binary format instead of a plain text. |
|
|
The data/BulkSanitizedConfigArchives and data/BulkUnsanitizedConfigArchives do not return file contents. |
|
|
Providing similar timestamp to Prime Infrastructure from its Web interface and RESTful API renders different results while creating a guest user. |
|
|
Prime Infrastructure does not allow root users to log in to the GUI after migration to 3.4. |
|
|
Issues in adding additional campuses/buildings/floors after importing maps in Prime Infrastructure. |
|
|
Device parameters are missing after upgrading to Prime Infrastructure 3.7. |
|
|
In Prime Infrastructure, issues in pushing the maximum number of AP groups on several AireOS WLC platforms. |
|
|
In Prime Infrastructure, errors occur while attempting to save configuration changes for access points. |
|
|
In Prime Infrastructure 3.7, an error occurs in the Metrics field on the Monitor > Monitoring Tools > Performance Graphs > Interfaces page for the interfaces that has descriptions configured. |
|
|
Vulnerability in the web-based management interface of Cisco Prime Network Control System. |
|
|
Vulnerability in Cisco Prime Infrastructure and Evolved Programmable Network Manager path traversal. |
|
|
Vulnerability in Cisco Prime Infrastructure and Evolved Programmable Network Manager path traversal. |
|
|
Issues in Cisco Prime Infrastructure and Evolved Programmable Network Manager remote code execution. |
|
|
Cisco Prime Infrastructure and Evolved Programmable Network Manager Path Traversal vulnerability. |
|
|
Vulnerability in Cisco Prime Infrastructure and Evolved Programmable Network Manager SQL injection. |
|
|
Prime Infrastructure 3.7-Unable to search templates of lightweight access points. |
|
|
Issues in Cisco Prime Infrastructure and Evolved Programmable Network Manager remote code execution. |
|
|
Advanced Search through “Application Search” displays “Permission Denied” error. |
|
|
In Prime Infrastructure, the number of clients connected to a 802.11a/n/ac radio network is not accurate in the Maps AP Info view. |
|
|
Prime Infrastructure fails to generate map tiles in AP planning mode. |
|
|
Prime Infrastructure doesn't show down alarms for access points in Network Topology diagram. |
|
|
In Prime Infrastructure, the Top N Interfaces by Netflow dashlets displays data from other virtual domains. |
|
|
Prime Infrastructure 3.4-API fails to schedule a Compliance job. |
|
|
The “CLITemplateDeployIOSDevices” job type is not available while deploying the CLI template from API. |
|
|
Prime Infrastructure's performance is impacted when the Data Cleanup job fails to clean the job entries. |
|
|
Prime Infrastructure's Planning Mode should support AP names longer than 15 characters. |
|
|
Unified AP ping reachability setting is changed by performing an inline upgrade to Prime Infrastructure 3.7. |
|
|
The last seen time of a Rogue AP is incorrectly updated. |
|
|
The Rogue APs (Updated) report in Prime Infrastructure intermittently fails while running through API. |
|
|
In Prime Infrastructure, issues occur while using the Save & E-mail Option in the Reports module. |
|
|
Issues in deleting multiple devices with the exception, LockAcquisitionException. |
|
|
The voice readiness map function in Prime Infrastructure is not accounting for APs in the monitor mode. |
|
|
In Prime Infrastructure, unable to delete a few local users. |
|
|
A device deleted from location groups is getting displayed in the All devices page. |
|
|
Prime Infrastructure 3.7 automatically shuts down when TFTP is enabled in a HA installation. |
|
|
Prime Infrastructure 3.4.1-Adding a new user in the Add User page displays an error. |
|
|
Prime Infrastructure 3.4-Client details recent map button is not working. |
|
|
Deploying a dynamic interfaces template to WLAN Controllers fails if the device names are in the .CSV format. |
|
|
The default antenna angle is different in auto placement mode than in the manual placement mode. |
|
|
The ConstraintViolationException occurs in job specification table log. |
|
|
The Save & Export with PDF option is not working for fault events and syslog report. |
|
|
Prime Infrastructure does not show 802.11v config for WLANs. |
|
|
Unable to change the schedule of the LAP templates to Now. |
|
|
Prime Infrastructure deletes the unregistered APs. |
|
|
The AP Interference Threshold is not updated on Prime Infrastructure's AP configuration page. |
|
|
Prime Infrastructure uses a version of vulnerable Apache HTTP Server. |
|
|
Prime Infrastructure's API shows Meraki device's reachability status as Unknown. |
|
|
Vulnerability in virtual domain system of Prime Infrastructure leading to privilege escalation. |
|
|
In Prime Infrastructure, the value of interfaceSpeed for cdpNeighbors may return the value as Unknown while calling the API Access Point Details. |
|
|
Prime Infrastructure-Inventory 3.6 hardening 1 issue. |
|
|
The Credential Profile drop down list is not getting displayed in Firefox. |
|
|
Prime Infrastructure uses a version of Apache Struts affected by remote code execution. |
|
|
The Edit and Save Location Device Group Description is not getting updated in Network Device Groups. |
|
|
In Prime Infrastructure, users are not able to edit/save location group (Add Devices Dynamically) setting while using the Japanese GUI. |
|
|
In Prime Infrastructure, the filter is not applied to the zone area while filtering the interferer on maps. |
|
|
In Prime Infrastructure, issues in collecting inventory from a WLC when an AP disassociation and re-association sync happens. |
|
|
Creating a Lobby Ambassador user with a long disclaimer in Hebrew fails. |
|
|
In Prime Infrastructure, the FTP Remote Repository config does not accept password with a % character. |
Related Documentation
You can access additional Cisco Prime Infrastructure documentation at:
http://www.cisco.com/en/US/products/ps12239/tsd_products_support_series_home.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html .
Subscribe to What’s New in Cisco Product Documentation , which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the “Related Documentation” section.
Feedback