Cisco Prime Infrastructure 2.2.2 Release Notes
This document contains the following sections:
•
Introduction, page 2
•
System Requirements, page 2
•
Installation Guidelines, page 2
•
Upgrading from Previous Releases of Cisco Prime Infrastructure, page 5
•
Submitting Feedback, page 5
•
Prime Infrastructure Licenses, page 5
•
Supported Devices, page 6
•
New Features and Enhancements, page 7
•
Important Notes, page 7
•
FAQs: Operations Center and Prime Infrastructure, page 8
•
Open Caveats, page 8
•
Resolved Caveats, page 10
•
Obtaining Documentation and Submitting a Service Request, page 12
Cisco Systems, Inc.
www.cisco.com
Introduction
Introduction
This is the second maintenance release for Cisco Prime Infrastructure 2.2.
You can install Cisco Prime Infrastructure 2.2.2 Maintenance Release on a server running the Cisco Prime Infrastructure,
version 2.2, 2.2.1 and 2.2.1 with Wireless Technology Package 1.0.0.
System Requirements
For more information on server and web client requirements, see the section Understanding System Requirements of the Cisco
Prime Infrastructure 2.2 Quick Start Guide.
Installation Guidelines
The following sections explain how to install the maintenance release.
•
Before You Begin Installing the Maintenance Release
•
Installation Scenarios Not Supported in Prime Infrastructure 2.2.2
•
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 2.2 or 2.2.1 installation, follow these steps:
1.
Reinstall Prime Infrastructure 2.2 from an OVA or ISO distribution.
2.
Install any prior point patches.
3.
If the original version is Prime Infrastructure 2.2.1, install the maintenance release 2.2.1 over Prime Infrastructure 2.2.
4.
Restore the data from the backup that you made before applying the maintenance release 2.2.2.
Similarly, if you are running Prime Infrastructure 2.2.x in a Virtual Machine (VM) and your organization permits taking VM
snapshots, 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 lease 100 Mbits/sec) and low latency (less than 20
milliseconds) throughout the maintenance release installation. For more information, see Troubleshooting Maintenance
Release Installs in High Availability Implementations.
Cisco Prime Infrastructure 2.2.2 Release Notes
2
Installation Guidelines
Installation Scenarios Not Supported in Prime Infrastructure 2.2.2
Caution
•
Prime Infrastructure 2.2.2 does not support the below installation scenarios.
Data Center Technology Package 1.0.0
– Installation of Prime Infrastructure 2.2.2 over Prime Infrastructure 2.2.1 with Data center Technology Package 1.0.0.
– Installation of Data Center Technology Package 1.0.0 over Prime Infrastructure 2.2.2.
•
Wireless Technology Package 1.0.0
– Installation of Wireless Technology Package 1.0.0 over Prime Infrastructure 2.2.2.
•
Prime Infrastructure Backup
– Restoring backup data from Prime Infrastructure 2.2.1 with Wireless Technology Package 1.0.0 directly on Prime
Infrastructure 2.2.2.
– Restoring backup data from Prime Infrastructure 2.2.1 with Data Center Technology Package 1.0.0 directly on Prime
Infrastructure 2.2.2.
Note
If you face any issues related to the unsupported installation scenarios, contact Cisco TAC for support.
Installing the Maintenance Release from Cisco Site
Make sure you have completed the recommended preparation steps given in Before You Begin Installing the Maintenance
Release.
Step 1
Log in to the Prime Infrastructure 2.2 or 2.2.1 server.
Step 2
Choose Administration > 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 2.2.2 Maintenance Release file name
pi222-41.ubf.
Step 6
Click Install to install the maintenance release.
Step 7
Restart the Cisco Prime Infrastructure server as explained in Restarting Prime Infrastructure in Cisco
Prime Infrastructure 2.2 Administration Guide to complete the installation process.
Step 8
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.
Note
We recommend you to take backup immediately after successful installation of Prime Infrastructure
2.2.2.
Cisco Prime Infrastructure 2.2.2 Release Notes
3
Installation Guidelines
Installing the Maintenance Release from Local Storage
Make sure you have completed the recommended preparation steps given in Before You Begin Installing the Maintenance
Release.
Step 1
Download the Prime Infrastructure 2.2.2 Maintenance Release pi222-41.ubf from Home > Products >
Cloud and Systems Management > Routing and Switching Management > Network Management
Solutions > Prime Infrastructure > Prime Infrastructure 2.2 > Prime Infrastructure Patches-2.2.2 and
save the file in your local storage.
Step 2
Log in to Prime Infrastructure 2.2 or 2.2.1 server.
Step 3
Choose Administration > 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 pi222-41.ubf is listed under
FileName column.
Step 6
In the Critical Fixes pane, click Install. You will see a dialog box informing that manual restart of Prime
Infrastructure is required. 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 in Cisco Prime Infrastructure 2.2 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
2.2.2.
Installing the Maintenance Release in High Availability Mode
Download the Prime Infrastructure 2.2.2 Maintenance Release pi222-41.ubf from Home > Products > Cloud and Systems
Management > Routing and Switching Management > Network Management Solutions > Prime Infrastructure > Prime
Infrastructure 2.2 > Prime Infrastructure Patches-2.2.2 and save the file in your local storage.
To install the downloaded Prime Infrastructure 2.2.2 Maintenance Release pi222-41.ubf in High Availability mode follow the
below steps:
•
Make sure you have completed the recommended preparation steps given in Before You Begin Installing the Maintenance
Release.
•
If your current Prime Infrastructure implementation has High Availability (HA) servers that are not at the same patch level,
see Patching Paired High Availability Servers in Cisco Prime Infrastructure 2.2 Administration Guide.
•
If you are setting up a new Prime Infrastructure High Availability (HA) implementation and your new servers are not at
the same patch level, see Patching New High Availability Servers in Cisco Prime Infrastructure 2.2 Administration Guide.
Cisco Prime Infrastructure 2.2.2 Release Notes
4
Upgrading from Previous Releases of Cisco Prime Infrastructure
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 Mbits/sec) and high latency (greater than 20
milliseconds). 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 re-start 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 backup-logs in Command Reference Guide for Cisco Prime Infrastructure 2.2.
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 2.2 Quick Start 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 2.2 Ordering and
Licensing Guide.
Cisco Prime Infrastructure 2.2.2 Release Notes
5
Supported Devices
Supported Devices
To see the list of devices supported in this release of Prime Infrastructure:
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.
Step 4
Click Supported Devices List.
You can also view the Cisco Prime Infrastructure 2.2 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
For detailed information on Wireless LAN Controller software features that are not configurable in Prime Infrastructure
Release 2.2 using the pre-packaged templates, see Non-Configurable Features for Wireless LAN Controller Software Releases
in Cisco Prime Infrastructure 2.2 Release Notes.
Cisco Prime Infrastructure 2.2.2 Release Notes
6
New Features and Enhancements
New Features and Enhancements
There are no new features in this release.
This maintenance release includes Single Sign-on (SSO) Server Configuration Enhancement for Prime Infrastructure Instances
and Prime Operation Center.
The following fields are added in Add SSO Servers page in Administration > Users > User, Roles & AAA.
•
DNS Name—DNS Name of the server on which you activated the license. Enter the DNS Name only if forward and reverse
DNS lookups are same.
•
Using Self-signed Certificate checkbox—Enable the checkbox only if the forward and reverse DNS lookups are same.
Otherwise configure the public signed certificates manually through CLI on both Prime Infrastructure Instances and Prime
Operation Center.
For generating Certificate Authority (CA) or Self Signed Certificate (SSL), see Certificate Signing Request (CSR) in Cisco
Prime Infrastructure Classic View Configuration Guide for Wireless Devices, Release 2.2.
For more details on Prime Operation Center, see Setting up Operations Center in Cisco Prime Infrastructure 2.2 Administration
Guide.
Additional Supported Platforms
Prime Infrastructure 2.2.2 with Device Pack 4 and above supports the following new platforms:
•
Cisco 8540 Series Wireless Controller
•
Cisco 5520 Series Wireless Controller
For installing Device pack 4, see Readme for Device Packs 4 for Cisco Prime Infrastructure 2.2.
Note
SWIM and Configuration Archive support are not available in Device Pack 4 for Prime Infrastructure
2.2.
Important Notes
•
Prime Infrastructure 2.1.x instances can authenticate via Prime Infrastructure 2.2.2 single sign-on (SSO) server only if you
apply the ISE patch pi212_PIGEN_CSCur43834_01.ubf from Home > Products > Cloud and Systems Management >
Routing and Switching Management > Network Management Solutions > Prime Infrastructure > Prime Infrastructure 2.1
> Prime Infrastructure Patches-2.1.2 before configuring Prime Infrastructure 2.2.2 SSO server IP in Prime Infrastructure
2.1.x instances. It is a prerequisite to manage Prime Infrastructure 2.1.2 instances in Prime Operation Center 2.2.2.
•
In addition to installing Prime Infrastructure 2.2.2 on Prime Infrastructure instances, make sure that you also install Prime
Infrastructure 2.2.2 on Prime Operations Center.
•
Prime Operation Center supports both Prime Infrastructure 2.1.x with cluster enable Patch and 2.2.x as managed instance.
•
Install Plug and Play gateway before installing Prime Infrastructure 2.2.2.
•
Prime Infrastructure 2.2.2 has a fix for POODLE vulnerability which disables SSLv3 and enables TLS on Prime
Infrastructure server. The CNS agent on the devices currently support only SSLv3 and is poodle vulnerable (CSCus48378).
Installing the Prime Infrastructure 2.2.2 maintenance release would break the Secure PnP (SSL and HTTPS enabled)
functionality in Prime Infrastructure for devices.
Cisco Prime Infrastructure 2.2.2 Release Notes
7
FAQs: Operations Center and Prime Infrastructure
FAQs: Operations Center and Prime Infrastructure
For the frequently asked questions about Operations Center and its interactions with the instances of Prime Infrastructure that
it manages, see Cisco Prime Infrastructure 2.2 Release Notes.
Open Caveats
Table 1 lists the Open Caveats in Cisco Prime Infrastructure Release 2.2.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
CSCuh16286
Global search for IPv6 clients based on IP addresses is not working.
CSCul06347
When comparing the Prime Infrastructure server and cluster, a few fields have mismatched data.
CSCul35804
Prime Infrastructure 2.0 has the CBC Mode vulnerability.
CSCuo68188
The syslogs tab does not display any data in the cluster server though the Prime Infrastructure instance
has data in it.
CSCuo70141
Failback fails due to low bandwidth.
CSCuo71039
IPsec credentials are updated when bulk importing the devices.
CSCuo89119
The switchport link down event is categorized incorrectly as WLC link down event.
CSCup25645
Cross-launching to the source IP address from the Events page displays the alarm tab with no data
available.
CSCup94066
When selecting many devices, the filter criteria is minimized and does not show anything inside the filter.
CSCuq04072
Unable to map WLAN mobility anchor for IPv6 wireless controller.
CSCuq51763
Device selection refresh issue in IWAN workflow.
CSCur21924
The columns in Prime Infrastructure wIPS alarms have to be edited to show only relevant information.
CSCur23731
When you click a WLC device to view inventory details, the Operations Center is unable to load data.
CScur45282
Auto SPT is running on adhoc rogues and showing false alarm.
CSCur45975
Backups with lengthy filenames are not restored.
CSCur56614
Error thrown while configuring dhcp option 82 fields in interface page.
CSCur58621
The Import from device option fails and images are displayed as not available.
CSCur67549
IWAN: The HUB Master Controller template is not part of routing instance configuration.
CSCur72133
Date stamp is not being shown on some chart types in Client AP association.
CSCur75625
For client attribute, Cross launch to ISE, if the filter is set as end-point ID, the query returns no data.
CSCur83964
The failover operation is not successful during HA software update.
CSCur85223
The Initial Device Setup is empty for restored Server and any of the supported devices from
“Unassigned” group is not listed.
CSCur85653
Location Groups are placed under All Devices.
Cisco Prime Infrastructure 2.2.2 Release Notes
8
Open Caveats
Table 1
Open Caveats (continued)
Identifier
Description
CSCur85763
The report shows the status as Not Applicable, when only the Admin status of 802.11ac is configured via
LWAP template.
CSCur87358
The Device Port Summary shows no information for 5508 Series WLAN Controller.
CSCur91049
ActiveMQ flooding slows down the process of creating a group.
CSCur94452
Unwanted dialog box appears while trying to open existing client reports.
CSCus13995
Disable Compliance Service feature.
CSCus15638
Misleading message shown under “Compliance Service” after clicking Save.
CSCus54753
Issue in setting up Multicast Address for both Cisco 5500 and 8500 devices with dual stack.
CSCus72290
Swim image distribution to many devices in parallel may cause the job to be in pending state forever.
CSCus75042
Issue in cofing archive page - Device details are not displayed.
CSCus77041
Plug and Play day-0 functionality is not happening for HTTPS Provisioning.
CSCus78734
Prime Infrastructure 2.2.1 IPv6 Mobility anchor set issue.
CSCus88449
Rogue reports show “No data available” message for IPv6 controller filter.
CSCut95862
In Prime Infrastructure 2.2.1 /2.2.2, the technology packages are not listed under “Add-ons”, instead
listed under “critical fixes” in the Software Update page.
CSCut99230
Wrong mobility anchor/Export anchor WLC IP is displayed in Prime Infrastructure 2.2.2.
CSCut99761
Enable mobility mode button should be disabled for 5520/8540 in Prime Infrastructure 2.2.2.
CSCuu12444
When Prime Infrastructure 2.2.2 UBF is installed over Prime Infrastructure 2.2.1 system, the Software
Update page does not list the update without process restart.
Cisco Prime Infrastructure 2.2.2 Release Notes
9
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
CSCuq89855
CLI templates are failed for SG 500/300 series switch.
CSCur12007
Need RBAC control of Created Elements in Topology Map.
CSCur22006
Prime Infrastructure must not allow attempt to restore device configuration with masked password.
CSCur29219
Device is added in Prime Infrastructure with wrong Credential through Discovery (OSPF).
CSCur83972
High Availability split brain issue when network is reconnected between 35 to 60 seconds.
CSCus05561
Failed to Save and Export Interface Capacity report With Non-Root domain.
CSCus09084
Pruning of records by partition must be based on size as well.
CSCus14306
Rogue removed from WLC trap does not clear the rogue alarm in Prime Infrastructure.
CSCus15565
Some percentage of Prime Infrastructure rogue alarms never get cleared.
CSCus29884
Correct Inventory collection status is not shown in the user interface.
CSCus32138
Auto-monitoring policy not working for Cisco Catalyst 3K device with polaris image
CSCus41099
Op Center - Clients and Users page cross-launch is not working from Quick Search.
CSCus47226
Unable to open AP details page for few APs.
CSCus49824
Save and Export with non-root domain failed for Interface Capacity Report.
CSCus61603
Image distribution in parallel for about 5 devices fails, but the job has been running forever.
CSCus63803
AP no longer exists in Converged Theme.
CSCus63826
Aggregated tables for Device Availability is losing the granularity.
CSCus64885
Prime Infrastructure 2.0/2.1 servers might crash, when concurrent TACACS logins are done.
CSCus68576
The same version of backup failed to restore, when restore backup is taken from Express OVA.
CSCus73559
During Prime Infrastructure 2.2 upgrade, fix the minimum supported zoom for upgraded floor images.
CSCus76661
In the EndPoint Association page, duplicate entries are created when adding rule.
CSCus79366
The NBI interface goes down after upgrading the Prime Infrastructure from version 2.1 to version 2.2.
CSCus87022
The device inventory status is set to 'Partial Collection Failure' on Policy-map and class-map retrieval/config
for failed zone-based firewall.
CSCus93225
Inventory goes to partial collection if the device has a reflexive ACL on the configuration.
CSCus93328
Network Topology is not available with AAA login.
CSCus96662
The syslog filters are disappeared after adding new filters.
CSCus98629
The SNMP Port field accepts values beyond the port range.
CSCus99016
Inventory collection fails for C4500 with SUP7: NGWC Switching.
CSCut02227
Unable to edit Context Aware Notifications in Prime Infrastructure 2.2.
CSCut09522
Prime Infrastructure 2.2, Port grouping has incorrect port group out of the box
CSCut12022
Device delete gets hanged and is not able to proceed further.
Cisco Prime Infrastructure 2.2.2 Release Notes
10
Resolved Caveats
Table 2
Resolved Caveats (continued)
Identifier
Description
CSCut12655
Remove the SSO requirement for a reverse lookup on IP address.
CSCut18603
Links are missing in device topology.
CSCut19862
Task Permission of Rogue Location in User Group does not work.
CSCut22175
TACACS+ templates created with IPv4 server address cannot be applied to a WLC running any version of
7.x.
CSCut24624
Hash function is broken in CARS application under Prime Infrastructure.
CSCut24673
An error occurs while deploying the config template.
CSCut27407
Session should not be closed in the method when it is not opened.
CSCut29605
Incorrect port is used in the Inventory collection process.
CSCut31617
Database connections are exhausted and unable to login to Prime Infrastructure.
CSCut36741
Unable to edit the interface assignment in Topology.
CSCut38927
Unable to login to Prime Infrastructure once synchronization happens for more than 700 devices with
credential profiles.
CSCut54995
Unable to view the WLC 5508 under the WLC 5500 sub-category on the Network device.
CSCut55191
Alarm not generating when ASA 5525 is disconnected from the network
CSCut59900
Navigating to Reports > Reports Run Results provides nullPointerException in Prime Infrastructure.
CSCut62519
Failure to collect feature NgwcAclConfig reports for 3850/3650 controllers.
CSCut68038
Topology Cache causes out of memory issue.
CSCut70519
Discrepancy in the TopNApps to TopNClients data.
CSCut73368
In Advanced Search filter, remove the limitation of the full MAC address in the user interface.
CSCut76007
Topology Alarm cache buildup Prime Infrastructure Start holding up the objects in memory.
CSCut77275
Wired Detailed Device Inventory report fails with selection of devices.
CSCut81432
In the Client and Users page, only few records are fetched initially and scrolling down causes slowness.
CSCut83926
In the Alarms default page, the minor alarms are hidden.
CSCut85586
In Prime Infrastructure, data cleanup runs for three days.
CSCut89659
Null pointer exception occurs while running Poll Client Status background task.
CSCut95118
Error viewing device Details
CSCut95819
Loading and scrolling takes more time in Alarms and Events page.
CSCut98145
Maximum size for table spaces is 100Gb.
CSCuu00687
Oracle memory is reset to 4GBor 6GB.
CSCuu02705
SVC_Health_summary table is not pruned
Cisco Prime Infrastructure 2.2.2 Release Notes
11
Related Documentation
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 2.2.2 Release Notes
12