Cisco Prime Infrastructure 3.0.1 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 5
•
Submitting Feedback, page 5
•
Prime Infrastructure Licenses, page 5
•
Supported Devices, page 6
•
New Features and Enhancements, page 7
•
Important Notes, page 7
•
Open Caveats, page 8
•
Resolved Caveats, page 9
•
Related Documentation, page 12
•
Obtaining Documentation and Submitting a Service Request, page 12
Cisco Systems, Inc.
www.cisco.com
Introduction
Introduction
This is the first maintenance release for Cisco Prime Infrastructure 3.0.
You can install Cisco Prime Infrastructure 3.0.1 Maintenance Release on a server running the Cisco Prime Infrastructure,
version 3.0.
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 installation, follow these steps:
1.
Reinstall Prime Infrastructure 3.0 from an OVA or ISO distribution.
2.
Restore the data from the backup that you made before applying the maintenance release 3.0.1
Cisco Prime Infrastructure 3.0.1 Release Notes
2
Installation Guidelines
Similarly, if you are running Prime Infrastructure 3.0 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.1 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.1 Maintenance Release file name
pi301-26.ubf.
Step 6
Click Install to install the maintenance release.
Step 7
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 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
3.0.1.
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.1 from the local storage, follow these steps:
Step 1
Download the Prime Infrastructure 3.0.1 Maintenance Release pi301-26.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.1 and
save the file in your local storage.
Cisco Prime Infrastructure 3.0.1 Release Notes
3
Installation Guidelines
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 pi301-26.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.1.
Installing the Maintenance Release in High Availability Mode
Download the Prime Infrastructure 3.0.1 Maintenance Release pi301-26.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.1 and save the file in your local storage.
To install the downloaded Prime Infrastructure 3.0.1 Maintenance Release pi301-26.ubf in High Availability mode follow the
below steps:
•
Make sure that 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,
seethe Patching Paired High Availability Servers section in the Cisco Prime Infrastructure 3.0 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, seethe Patching New 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.
Cisco Prime Infrastructure 3.0.1 Release Notes
4
Upgrading from Previous Releases of Cisco Prime Infrastructure
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.
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.
Cisco Prime Infrastructure 3.0.1 Release Notes
5
Supported Devices
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
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.1 Release Notes
6
New Features and Enhancements
New Features and Enhancements
The following features are supported in Cisco Prime Infrastructure 3.0.1.
Cisco Mobility Express Wireless Network Solution
The Cisco Mobility Express wireless network solution provides a virtual wireless LAN controller functionality which is
currently bundled into the Cisco Aironet 1850 and 1830 series access points. This functionality provides a simplified Wi-Fi
architecture with enterprise-level WLAN capability to small and medium deployments.
In the Cisco Mobility Express wireless network solution, one of the APs running the Cisco Mobility Express wireless
controller, is designated as the master AP and the other APs associated to the master AP, are referred as subordinate APs.
The master AP operates as a wireless LAN controller, to manage and control the subordinate APs, and also operates as an access
point to serve clients. The subordinate APs operate as normal Lightweight Access Points to serve the clients.
Supported and Unsupported Mobility Express Features
Prime Infrastructure supports the following Mobility Express features:
•
Scalability
– Up to 25 APs.
– Up to 16 WLANs.
•
Connection Mode—FlexConnect.
•
Only default FlexConnect groups are allowed.
•
High Availability and Redundancy—Built-in redundancy mechanism to self-select a Master AP and to select a new AP as
Master in case of a failure. An information event is generated upon failover.
•
Configuration Archive.
•
Configuration and templates supported by Prime Infrastructure.
Prime Infrastructure does not support the following Mobility Express features:
•
LyncSDN
•
IPv6 Support
•
SWIM
•
AP groups including default AP groups
•
Application Visibility and Control (AVC)—Limited HTTP, with only Application Visibility and not Control.
Important Notes
•
In addition to installing Prime Infrastructure 3.0.1 on Prime Infrastructure instances, make sure that you also install Prime
Infrastructure 3.0.1 on Prime Operations Center.
•
Prime Operations Center 3.0.1 manages Prime Infrastructure 3.0 and 3.0.1. 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.
•
Install Plug and Play gateway before installing Prime Infrastructure 3.0.1
Cisco Prime Infrastructure 3.0.1 Release Notes
7
Open Caveats
Open Caveats
Table 1 lists the Open Caveats in Cisco Prime Infrastructure Release 3.0.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.
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.
CSCuv42850
When a configuration template that has a TACACS configuration is used as a configuration template in
a Plug and Play profile in APIC-EM mode, an error message appears.
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.
Cisco Prime Infrastructure 3.0.1 Release Notes
8
Resolved Caveats
Table 1
Open Caveats (continued)
Identifier
Description
CSCuv66430
Unable to expand location group in Virtual Domain page.
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.
CSCuv93544
Upgrade stage 4: “UtilSession failed” message is displayed.
CSCuv04463
Adding a device through SNMP v1 will get into collection failure in Prime Infrastructure 3.0.
CSCuw50782
AVC capable devices and other menus are not listed in Interface configuration page.
CSCuw26539
Device type for 1830 Mobility Express AP is shown as Aironet.
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
CSCur20012
After successfully duplicating a group, re-parented duplicate group selection is failed.
CSCur59104
Grouping clause supported on Aggregated table data.
CSCus73366
Unable to synchronize WLC devices due to snmp_transport in credential table.
CSCus85944
Prime Infrastructure 2.2 fails to restore Prime Infrastructure 1.4 backup.
CSCuu34991
Prime Infrastructure 2.2.1 user defined and system defined jobs remain in scheduled state and do not run.
CSCuu78421
Application search text box is not working properly.
CSCuu84825
Matrix Laboratory (MATLAB) process is down during process startup.
CSCuv18765
Issues in add device process for the initial hours after APs and clients discovery.
CSCuv27699
Issues in deleting running status in PnP.
CSCuv34867
Need to add Cisco Mobility Express support on Prime Infrastructure.
CSCuv35064
Search by “guest users” in global search field displays a blank page.
CSCuv43619
ifmGrouping REST API displays “500 Internal Server Error” status.
CSCuv47484
Interface Tx and Rx Utilization dashlet screen is not scaling.
CSCuv50157
Unable to perform bulk operation in severity configuration and alarm auto clear.
CSCuv53569
Inventory collection fails for WLC devices using IPv6.
CSCuv57487
Focus device is not highlighted in N Hop topology view.
Cisco Prime Infrastructure 3.0.1 Release Notes
9
Resolved Caveats
Table 2
Resolved Caveats (continued)
Identifier
Description
CSCuv57620
Login slows down due to eight Sync up calls.
CSCuv58006
Need to enable Site selection as a part of IWAN PfR workflow.
CSCuv61520
WLC in configuration group with auditing and enforcement is not auditing.
CSCuv62282
Controller status and ICMP Reachability Metric Dashlet Count mismatch.
CSCuv62461
Country codes in General-802.11 config is not sorted.
CSCuv67250
Scroll bar end is not visible for run and show commands in troubleshoot option.
CSCuv67288
In Alarms and events page, clicking the Device Type link in list view shows navigation issue.
CSCuv67410
While deploying AVC profile on all the controllers using a template, few protocols are not available.
CSCuv69894
Topology uses wrong device type icon for EtherSwitch modules.
CSCuv71501
API collection filtering is not working properly for Inventory Details API.
CSCuv71621
Report criteria and report period is not retained for saved reports before upgrade or restore.
CSCuv73432
Breadcrumb is not proper in background task.
CSCuv75555
Cancel operation is not responding for invalid Credential Profile alert message.
CSCuv76754
Need to add resize option and additional width to group selection page during report template definition.
CSCuv78439
The device interfaces are swapped in the link details action panel.
CSCuv79274
After navigating to the discovery source list view using global search in compute devices, the data is not
displayed.
CSCuv81119
Out of memory issue.
CSCuv81769
ISE filter displays clients that are moved to non-ISE WLAN as “Clients known by ISE”.
CSCuv82920
Unable to set severity configuration and alarm auto clear duration due to disabled mode.
CSCuv84831
RSSI value is displayed in dbm in client statistics.
CSCuv87859
Copy Right Information is not standardized between Primary, Secondary, OpCenter, and SSO login pages.
CSCuv89101
Device that are added in inventory via PnP and deleted from Inventory, are added back after 1-2 hrs.
CSCuv89399
Pre-shared field is displayed in CSV when DMVPN custom template is created and using in IWAN.
CSCuv89620
PSIRT and EoX reports are generated for non-root domain, even though the network devices are not mapped
to non-root domain.
CSCuv89853
Diagnostic URL for troubleshooting topology link discovery is missing.
CSCuv90451
Configuration is copying from device running-config to device startup-config even without selecting
checkbox in IWAN.
CSCuv90901
Export of site maps is not working.
CSCuv93030
Creating or editing Flexconnect AP Group template fails if VLAN support is disabled and WLC device
version is 8.1.
CSCuv93075
The server is not responding on Firefox browser after logging in.
CSCuv93099
AP config is not saved when “override vlan on AP” is enabled in flexconnect group.
CSCuv93754
Prime Infrastructure is not reporting AP channel changes specific to RRM monitoring.
CSCuv95331
After failover, device count and license count are not updated in the secondary server.
Cisco Prime Infrastructure 3.0.1 Release Notes
10
Resolved Caveats
Table 2
Resolved Caveats (continued)
Identifier
Description
CSCuv97607
If the netflow template configured on the device does not match the output interface, usage data is not
displayed in Top N Clients dashlet.
CSCuv99563
The data is not displayed in RTP Conversation dashlet.
CSCuw01536
The metrics dashboard displays incorrect optical alarm summary count.
CSCuw01657
Acknowledged alarms are displayed in topology.
CSCuw02510
Support case login dialog is not working in Alarm cross launch page from Alarm slider.
CSCuw02993
Data cleanup task is running for long hours (20 hrs) in scale pro server.
CSCuw03265
Need to add serial number of SFPs in Wired Detailed Device Inventory reports.
CSCuw03401
Intermittent HTTP 500 Error from Radios and RadioDetails API.
CSCuw03699
Need to add help text message “This is RW SNMP community string” in PnP profile.
CSCuw03703
Need to display provisioning profiles in pending status in PnP status page.
CSCuw03710
Need to add a text message “Not providing Telnet/SSH credentials may result in partial collection of
inventory data” in the add or edit Telnet/SSH dialog.
CSCuw05447
Empty report files are created at /opt/CSCOncs for each report run.
CSCuw09444
Need to update the error message while deleting a PnP profile associated with the device.
CSCuw09555
Assurance stored procedure is not writing to LT tables.
CSCuw10291
Compliance audit fails due to automatic device deletion and cache issue.
CSCuw10819
Need to display an appropriate error message when VLAN support is enabled\disabled while creating a
LWAP template.
CSCuw10834
Unable to add radius servers from flexconnect group config page.
CSCuw10840
Clicking ‘save’ multiple times in flexconnect AP group config clears and disables the ‘vlan support' and
'override vlan on ap’ fields.
CSCuw10845
Unable to save WLAN-ACL mappings and Policy ACL in AP configuration page.
CSCuw11388
Alarm configured with auto clear setting is generated after every one hour.
CSCuw11875
User Interface is slow and http threads are blocked in saveTelemetryEvent.
CSCuw12080
When navigating to applications tab in performance from TOP N application dashlet, drill down displays
“undefined”value.
CSCuw12832
In Prime Infrastructure 3.0, MAPS file import fails to create floors with AP1000.
CSCuw16233
Unable to navigate to Report Launch pad when selecting report from left hand side accordion menu.
CSCuw17512
Need to display 11 sub-reports for each device for Wired Detailed Device inventory.
CSCuw17532
Need to create script for deleting temporary files created while startup.
CSCuw27270
Performance graphs sometimes fails to restore and load.
CSCuw30816
Wireless controllers inventory collection adds the link from AP to controller linearly.
Cisco Prime Infrastructure 3.0.1 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 3.0.1 Release Notes
12