Cisco Prime Infrastructure 3.0.2 Release Notes
This document contains the following sections:
•
Introduction, page 2
•
Cisco End User License Agreement, page 2
•
System Requirements, page 2
•
Installation Guidelines, page 2
•
Upgrading from Previous Releases of Cisco Prime Infrastructure, page 7
•
Submitting Feedback, page 8
•
Prime Infrastructure Licenses, page 8
•
Supported Devices, page 8
•
New Features and Enhancements, page 10
•
Important Notes, page 10
•
Open Caveats, page 11
•
Resolved Caveats, page 13
•
Related Documentation, page 14
•
Obtaining Documentation and Submitting a Service Request, page 14
Cisco Systems, Inc.
www.cisco.com
Introduction
Introduction
This is the second maintenance release for Cisco Prime Infrastructure 3.0.
You can install Cisco Prime Infrastructure 3.0.2 Maintenance Release on a server running the Cisco Prime Infrastructure,
version 3.0 and 3.0.1.
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.0 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 System Settings > General > Help Us Improve.
System Requirements
For more information on server and web client requirements, see the Understanding System Requirements section in the Cisco
Prime Infrastructure 3.0 Quick Start Guide.
Installation Guidelines
The following sections explain how to install the maintenance release.
•
Before You Begin Installing the Maintenance Release
•
Installing the Maintenance Release from Cisco Site
•
Installing the Maintenance Release from Local Storage
•
Installing the Maintenance Release in High Availability Mode
•
Troubleshooting Maintenance Release Installs in High Availability Implementations
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.
To revert to the original Prime Infrastructure 3.0 or 3.0.1 installation, follow these steps:
1.
Reinstall Prime Infrastructure 3.0 from an OVA or ISO distribution.
2.
Install any prior patch updates.
3.
If the original version is Prime Infrastructure 3.0.1, install the maintenance release 3.0.1 over Prime Infrastructure 3.0.
Cisco Prime Infrastructure 3.0.2 Release Notes
2
Installation Guidelines
4.
Restore the data from the backup that you made before applying the maintenance release 3.0.2
Similarly, if you are running Prime Infrastructure 3.0.x 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.
If you are installing this maintenance release as part of a High Availability (HA) implementation, you will want to ensure that
the network links between the two servers provide maximum bandwidth (at least 100 Mbits/sec) and low latency (less than 20
milliseconds) throughout the maintenance release installation.
Installing the Maintenance Release from Cisco Site
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.0.2 from the Cisco site, follow these steps:
Step 1
Log in to the Prime Infrastructure 3.0 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 Show Details in the Critical Fixes pane to view the
updates.
Step 5
Click Download corresponding to the Prime Infrastructure 3.0.2 Maintenance Release file name
pi302-16.ubf. A warning message appears as follows:
Step 6
Click OK in the warning message.
Step 7
Click Install to install the maintenance release.
Step 8
Restart the Cisco Prime Infrastructure server as explained in Restarting Prime Infrastructure section in
the Cisco Prime Infrastructure 3.0 Administration Guide to complete the installation process.
Step 9
You can verify the maintenance release installation from Prime Infrastructure Login page under Critical
Fixes by hovering your mouse over the version 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.
Cisco Prime Infrastructure 3.0.2 Release Notes
3
Installation Guidelines
Note
We recommend you to take backup immediately after successful installation of Prime Infrastructure
3.0.2.
Installing the Maintenance Release from Local Storage
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.0.2 from the local storage, follow these steps:
Step 1
Download the Prime Infrastructure 3.0.2 Maintenance Release pi302-16.ubf from Home > Products >
Cloud and Systems Management > Routing and Switching Management > Network Management
Solutions > Prime Infrastructure > Prime Infrastructure 3.0 > Prime Infrastructure Patches-3.0.2 and
save the file in your local storage.
Step 2
Log in to Prime Infrastructure 3.0 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 pi302-16.ubf is listed under
FileName column.
Step 6
In the Critical Fixes pane, click Install. You will be prompted to manually restart the Prime
Infrastructure server. Click Yes for successful installation.
Step 7
Restart the server by first executing the ncs stop command and then the ncs start command, as explained
in Restarting Prime Infrastructure section in Cisco Prime Infrastructure 3.0 Administration Guide.
Step 8
You can verify the maintenance release installation from Prime Infrastructure Login page under Critical
Fixes in the Installed Updates popup by hovering your mouse over the version 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.
Note
We recommend you to take backup immediately after successful installation of Prime Infrastructure
3.0.2.
Installing the Maintenance Release in High Availability Mode
Download the Prime Infrastructure 3.0.2 Maintenance Release pi302-16.ubf from Home > Products > Cloud and Systems
Management > Routing and Switching Management > Network Management Solutions > Prime Infrastructure > Prime
Infrastructure 3.0 > Prime Infrastructure Patches-3.0.2 and save the file in your local storage.
To install the downloaded Prime Infrastructure 3.0.2 Maintenance Release pi302-16.ubf in High Availability mode follow the
below steps:
Cisco Prime Infrastructure 3.0.2 Release Notes
4
Installation Guidelines
•
Make sure that you have completed the recommended preparation steps given in Before You Begin Installing the
Maintenance Release.
•
If you are setting up a new Prime Infrastructure High Availability (HA) implementation and your new servers are not at
the same patch level, seethe Patching New High Availability Servers section in the Cisco Prime Infrastructure 3.0
Administration Guide.
•
If your current Prime Infrastructure implementation has High Availability (HA) servers that are not at the same patch level,
see the Patching Paired High Availability Servers section in the Cisco Prime Infrastructure 3.0 Administration Guide.
Cisco Prime Infrastructure 3.0.2 Release Notes
5
Installation Guidelines
To install the Prime Infrastructure 3.0.2 Maintenance Release on a Prime Infrastructure 3.0 secondary server with the primary
server in “Primary Active” state and the secondary server in “Secondary Syncing”, follow the below steps:
Step 1
Access the Health Monitor Web page of the secondary server and upload the Prime Infrastructure 3.0.2
UBF file, see the Step 3 in Patching Paired High Availability Servers section in the Cisco Prime
Infrastructure 3.0 Administration Guide.
Step 2
After you upload the Prime Infrastructure 3.0.2 UBF, click Install. The following warning message
appears:
Cisco Prime Infrastructure 3.0.2 Release Notes
6
Upgrading from Previous Releases of Cisco Prime Infrastructure
Step 3
Click Yes in the warning message. The following error message appears:
Step 4
Click OK in the error message.
Step 5
Restart the secondary server.
Step 6
Once the secondary server is up, go to the Software Update page and click Install.
Step 7
After the installation completes on the secondary server, continue the patching process, see the Step 4 in
Patching Paired High Availability Servers section in the Cisco Prime Infrastructure 3.0 Administration
Guide.
Troubleshooting Maintenance Release Installs in High Availability
Implementations
Users who apply this maintenance release in a High Availability (HA) implementation may experience difficulties if the
network links between the two servers offer low bandwidth (less than 100 Mbps) and high latency (greater than 20 ms). In
particular, this kind of low throughput can cause the post-maintenance release restart and re-registration to take far longer than
normal. In most cases, simply waiting longer will fix the problem with no intervention. 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 backup-logs section in the Command Reference Guide for Cisco Prime Infrastructure 3.0.
Upgrading from Previous Releases of Cisco Prime Infrastructure
For detailed information about upgrading from previous releases of Prime Infrastructure, including the list of versions from
which you can upgrade, see the If You Are Upgrading From Previous Releases of Prime Infrastructure section of the Cisco
Prime Infrastructure 3.0 Quick Start Guide.
Cisco Prime Infrastructure 3.0.2 Release Notes
7
Submitting Feedback
Physical Appliance Options
Prime Infrastructure 3.0.2 is supported on the Cisco Prime Infrastructure Physical Appliance (Gen 1). For more information
on installation, upgrade, and migration from Prime Infrastructure 2.2.x to Prime Infrastructure 3.0.2 Gen 1 Appliance, see the
Prime Infrastructure 3.0.2 Generation 1 Upgrade and Migration Guide.
Submitting Feedback
Your feedback will help us improve the quality of our product. To send your feedback, follow these steps:
Step 1
Choose Administration > System Settings > Mail Server Configuration.
Step 2
In the Mail Server Configuration page, enter the mail server details.
Step 3
Click Save to save the configuration settings.
Step 4
Choose Help > Help Us Improve Cisco Products.
Step 5
In the Help Us Improve Cisco Products page, select the Yes, collect data periodically (monthly) option.
Step 6
Click OK.
Prime Infrastructure Licenses
For detailed information on procuring a license for Prime Infrastructure, see the Cisco Prime Infrastructure 3.0 Ordering and
Licensing Guide.
Supported Devices
To see the list of devices supported in this release of Prime Infrastructure, follow these steps:
Step 1
Log in to Prime Infrastructure.
Step 2
Switch to the Converged Theme (if applicable).
Step 3
Click the question mark icon (Help) at the top right of the page.
Step 4
Click Supported Devices List.
You can also view the Cisco Prime Infrastructure 3.0 Supported Devices list at the following URL:
http://www.cisco.com/c/en/us/support/cloud-systems-management/prime-infrastructure/products-device-support-tables
-list.html
For detailed information on the software compatibility for the Cisco wireless devices, see the following URL:
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
Cisco Prime Infrastructure 3.0.2 Release Notes
8
Supported Devices
For detailed information on Wireless LAN Controller software features that are not configurable in Prime Infrastructure
Release 3.0 using the pre-packaged templates, seethe Non-Configurable Features for Wireless LAN Controller Software
Releases in the Cisco Prime Infrastructure 3.0 Release Notes.
Cisco Prime Infrastructure 3.0.2 Release Notes
9
New Features and Enhancements
New Features and Enhancements
The following features are supported in Cisco Prime Infrastructure 3.0.2.
IWAN Enhancements
The following enhancements are done in Cisco Prime Infrastructure 3.0.2:
•
Multi Data Center support for HUB and BGP Routing on the Overlay Backbone.
•
IWAN workflow usability.
Important Notes
•
In addition to installing Prime Infrastructure 3.0.2 on Prime Infrastructure instances, make sure that you also install Prime
Infrastructure 3.0.2 on Prime Operations Center.
•
Prime Operations Center 3.0.2 manages Prime Infrastructure 3.0.1 and 3.0.2. You must ensure that Prime Operations
Center version is either same or higher than Prime infrastructure Instances version. For more details, see Setting Up
Operations Center.
•
The default AVC templates (AVC-MPLS, AVC-Internet, AVC-InetMPLS) are not editable in the IWAN workflow. You can
edit or customize the default AVC templates in the design phase prior to deploying it in IWAN workflow. To design a
customized AVC template in the IWAN workflow, do the following:
– Go to Configuration > Features and Technologies > Feature Templates > IWAN > AVC.
– Customize the template and save it as a new template.
– Go to Services > Network Services > IWAN and chose this new template.
For more details on editing or customizing the templates, see Using Templates to Configure Devices in Cisco Prime
Infrastructure 3.0 user guide.
•
While deploying software images to devices from Inventory > Device Management > Software Images, the Distribute
Image dialog box opens if you click the Distribute Image button. The Distribute Image dialog box fails to launch again
if you click the Close icon at the top right corner of the Distribute Image dialog box. Refresh or reload the page to launch
the Distribute Image dialog box. You can avoid this issue, by clicking the Cancel button instead of the Close icon at the
top right corner of the Distribute Image dialog box.
Cisco Prime Infrastructure 3.0.2 Release Notes
10
Open Caveats
Open Caveats
Table 1 lists the Open Caveats in Cisco Prime Infrastructure Release 3.0.2.
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.
Table 1
Open Caveats
Identifier
Description
CSCul06347
While viewing client details, there are discrepancies in the VLAN ID and association ID, and clients
statistics data is not shown in Operations Center.
CSCur85763
Configuring the 802.11ac Radio status from the Lightweight AP template on AP 3600 with RM3000AC
module shows the result as “Not Applicable.”
CSCur98575
Controller names are missing in the Mobility Configuration page for IPV6 group members.
CSCus16647
Need to enhance manual SPT algorithm to handle trunk port discovery cases
CSCut74934
Discrepancy between EOS dates displayed in Prime Infrastructure 3.0 PSIRT and EOS reports when
compared with the dates on cisco.com.
CSCuu39610
Wireless deployed devices are not displayed with group name.
CSCuu48907
Sysname under Neighbors in 360 view for all devices is N/A.
CSCuu76741
Even when a virtual domain is associated to a user, it can be deleted in the Virtual Domain page.
CSCuu78178
When using Plug and Play, if you define a configuration template with an SSH configuration, Plug and
Play might fail with an error message.
CSCuu78607
You cannot filter port groups according to speed rules you specified.
CSCuu88416
In Operations Center, quick search of IPv6 for Clients and Users does not work.
CSCuv03706
Health Monitor page displays an error indicated the data replication operation failed abnormally.
CSCuv19388
Double quotes value check are not accepted for audit if custom policies are created with “condition and
actions” value field.
CSCuv20792
Wireless Clients might not be found if the Wireless Client filter is narrowed down to a specific client
username or MAC address.
CSCuv26646
Alarms generated from MSE during MSE High Availability failover and failback are not sent as email
notifications.
CSCuv34539
Filtering doesn't work on compliance jobs.
CSCuv34934
Inventory collection displays partial collection failure for particular devices.
CSCuv40246
When verifying the credentials for NAM, verification fails even when specifying the correct credentials.
CSCuv62585
Creating a policy with multiple lines in the Condition Details field results in a “Policy did not compile
successfully” error.
CSCuv63120
Primary server start-up takes 40 minutes and startup time-out occurs after 30 minutes.
CSCuv64263
UDF values specific to device are not seen under wireless controllers.
CSCuv64930
Most recent cache (Alarm/Events/Syslog) and custom traps are not preserved in Secondary server after
failover.
CSCuv64965
You cannot create a virtual domain in Operations Center using the results from Search.
CSCuv66430
Unable to expand location group in Virtual Domain page.
Cisco Prime Infrastructure 3.0.2 Release Notes
11
Open Caveats
Table 1
Open Caveats (continued)
Identifier
Description
CSCuv69018
Japanese characters are not allowed in Configuration Template Name field.
CSCuv69056
When you deselect 1,000 devices in the software image distribution page, the process can take up to two
minutes and might hang.
CSCuv84412
Unreachable AP count shows as 0 after failback in operational AP count dashboard.
CSCuv85543
Product Audit System (PAS) job is sometimes not created.
CSCuv87011
Secondary Health Monitor Event shows “failed to start Prime Infrastructure services.”
CSCuv89651
Support Request Settings are not retained after upgrade.
CSCuv04463
Adding a device through SNMP v1 will get into collection failure in Prime Infrastructure 3.0.
CSCuw26539
Device type for 1830 Mobility Express AP is shown as Aironet.
CSCuw35307
Uunable to add WLC with external webAuth URL exceeding 251 characters in Prime Infrastructure 3.0.
CSCuw79651
PKI certificate is failing on Branch device of IWAN.
CSCuw75109
Revoke & re-adding of PKI certificate is not working in IWAN.
CSCuw83644
PnP Bulk Import status in job dashboard is showing failure.
Cisco Prime Infrastructure 3.0.2 Release Notes
12
Resolved Caveats
Resolved Caveats
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 Bug Search Tool.
Table 2
Resolved Caveats
Identifier
Description
CSCuv12766
Cross launch to device through MSE Sync Service throws unknown error.
CSCuv42779
Unable to edit traffic interception values in imported template.
CSCuv42850
PnP fails when TACACS configuration is present in configuration template.
CSCuv73661
“Failed to load data” error is shown in table when filtering “Startup/Running Mismatch” column.
CSCuv75591
Alarms by Category Reset does not appear while navigating from detached window.
CSCuv93544
Upgrade stage 4: “UtilSession failed” message is displayed.
CSCuv96247
Deleting controller on Prime Infrastructure leaves entries in database.
CSCuw03401
Intermittent HTTP 500 Error is encountered while querying Radios and RadioDetails API.
CSCuw14662
Need to stop consumption of two licenses when 3650/3850 devices do not have wireless functionality
enabled.
CSCuw17771
Cisco UCS C Series server displays duplicate value for Summary.
CSCuw17876
Rogue AP alarms do not get cleared.
CSCuw18592
APIC-EM and Prime Infrastructure integration for IWAN GA release.
CSCuw18960
HCR Setup: Quick filter does not work at Mobility Services Engines page.
CSCuw24685
“Nice” cache optimization needs to be integrated with Prime Infrastructure 3.0.2
CSCuw25487
Prime Infrastructure should use GA version of API to login to APIC.
CSCuw27087
PnP: Need to make API changes for APIC GA release.
CSCuw27746
Prime Infrastructure fails to deploy management authentication priority template.
CSCuw27929
Compliance inventory features must not be executed if compliance is not enabled.
CSCuw28917
Prime Infrastructure should handle Network Outage or management traffic flood more efficiently.
CSCuw29071
Devices may not delete from Prime Infrastructure 3.0 and no logged errors are reported.
CSCuw31040
i18n: Character corruption occurs in Reports “Client Count” PDF.
CSCuw33560
Alarm cross launch does not work when accessed from Dashboard
CSCuw34681
WLC Inventory nightly sync job is disabled in Prime infrastructure 3.0.
CSCuw36608
Unable to deploy DMVPN template.
CSCuw36758
Default value for “Refresh Maps from Network” has to be set “FALSE”.
CSCuw40515
Devices may not get deleted from Prime Infrastructure 3.0.
CSCuw41296
Prime Infrastructure 3.0: Credential profile issue. Mode AuthnoPriv does not get saved for SNMP v3.
CSCuw41448
Prime Infrastructure 3.0: Error in ifm_inventory.log when deleting devices.
CSCuw42386
SWIM Distribution: Slowness is seen in multiple areas.
CSCuw46188
Popup message misleads to empty inventory log file, while deleting a managed device.
CSCuw48119
Restriction on OS version prevents device from getting audited.
Cisco Prime Infrastructure 3.0.2 Release Notes
13
Related Documentation
Table 2
Resolved Caveats
CSCuw50782
AVC capable devices and other menus are not listed in Interface configuration page.
CSCuw51137
Need to disable constraints scripts for restore and upgrade scenarios.
CSCuw56546
Restoring a backup onto Prime Infrastructure 3.0 removes EOX and PSIRT reporting functions.
CSCuw60044
Community string retains the default value, if notification receiver is edited.
CSCuw60917
Inventory Partial Collection fails due to parsing of “& “character.
CSCuw75225
Multiple issues in IWAN templates.
CSCuw75434
Single-DC templates should be default templates in all IWAN workflows
CSCuw76315
Unable to add APIC-EM Controller in Prime Infrastructure
CSCuw80843
Error in PnP while updating or editing provisioning profile
CSCuw81242
Model handler fails to create Alter sql for subclass model
CSCuw83519
Prime Infrastructure 3.0.2: Site-Sync shows Partial Collection Failure
CSCuw86416
Prime Infrastructure 3.0.2: “Enter mandatory fields” error pops up during deployment of
MPLS-HUB-DC1
CSCuw87827
Alarm assign and email notification functionalities are not working.
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.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL:
www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output,
network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative
content is unintentional and coincidental.
© 2012-2015 Cisco Systems, Inc. All rights reserved.
Cisco Prime Infrastructure 3.0.2 Release Notes
14