Cisco Prime Infrastructure 2.2 Release Notes
Last Updated: 18 March 2015
This document contains the following sections:
•
Introduction, page 2
•
System Requirements, page 2
•
Installation Guidelines, page 2
•
Upgrading Cisco Prime Infrastructure, page 2
•
Submitting Feedback, page 2
•
Prime Infrastructure Licenses, page 3
•
Supported Devices, page 3
•
Supported Wireless LAN Controller Hardware Models, page 4
•
New Features and Enhancements, page 7
•
Important Notes, page 11
•
FAQs: Operations Center and Prime Infrastructure, page 12
•
Open Caveats, page 17
•
Resolved Caveats, page 18
•
Related Documentation, page 19
•
Obtaining Documentation and Submitting a Service Request, page 19
Cisco Systems, Inc.
www.cisco.com
Introduction
Introduction
The Cisco Prime Infrastructure is a network management tool that supports lifecycle management of your entire network
infrastructure from one graphical interface. Prime Infrastructure provides network administrators with a single solution for
provisioning, monitoring, optimizing, and troubleshooting both wired and wireless devices. Robust graphical interfaces make
device deployments and operations simple and cost-effective.
Prime Infrastructure provides two different graphical user interfaces (from which you can switch back and forth by clicking
the downward arrow next to your login name):
•
Converged Theme, which is organized according to the Dashboard, Monitor, Configuration, Inventory, Maps, Services,
Reports, and Administration menus. For more information on features of the Prime Infrastructure Converged Theme, see
the Cisco Prime Infrastructure 2.2 User Guide.
•
Classic Theme (deprecated), which closely corresponds to the graphical user interface in Cisco Prime Network Control
System 1.1 or Cisco Wireless Control System (WCS). For more information on features of the Prime Infrastructure Classic
view, see the Cisco Prime Infrastructure Classic View Configuration Guide for Wireless Devices, Release 2.2.
System Requirements
For more information on server and web client requirements, see the System Requirements section of the Cisco Prime
Infrastructure 2.2 Quick Start Guide
Installation Guidelines
For detailed information about installing this release of Prime Infrastructure, see the Installing Cisco Prime Infrastructure
section of the Cisco Prime Infrastructure 2.2 Quick Start Guide
Upgrading 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 Upgrading Cisco 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
If you have configured your mail server, go to Step 8.
Step 2
Choose Administration > System Settings > Mail Server Configuration.
Step 3
In the Mail Server Configuration page, enter the mail server details.
Step 4
Click Save to save the configuration settings.
Step 5
Choose Help > Help Us Improve Cisco Products.
Step 6
In the Help Us Improve Cisco Products page, select the Yes, collect data periodically option.
Cisco Prime Infrastructure 2.2 Release Notes
2
Prime Infrastructure Licenses
Step 7
Click OK.
Step 8
Choose Help > Submit Feedback (in the Classic theme) or click the question mark icon at the top right
and then click Submit Feedback (in the Converged theme). You must configure the email server and
then enable data collection to configure the feedback tool.
Prime Infrastructure Licenses
For detailed information on Prime Infrastructure licensing, see the Cisco Prime Infrastructure 2.2 Ordering and Licensing
Guide.
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 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
To view the Prime Infrastructure supported devices for switches, wireless LAN controllers (WLC), access point images,
Identity Services Engine (ISE), and Mobility Services Engines (MSE), see 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-tableslist.html
Prime Infrastructure does not support non-admin virtual device context (VDC) on Nexus devices.
Cisco Prime Infrastructure 2.2 Release Notes
3
Supported Wireless LAN Controller Hardware Models
Supported Wireless LAN Controller Hardware Models
Table 1 lists the Prime Infrastructure supported devices for switches, WLCs, Access Points (APs), ISEs, and MSEs.
..
Table 1
Supported Device Matrix for Switches, WLC, MSE, ISE, and AP
Supported Switches
Supported Controllers
2960, 2975 Switches Cisco 2100 Series
[Cisco IOS Release
Cisco 2500 Series
12.2(50)SE],
Cisco 4400 Series
Catalyst 3560
Switches [Cisco IOS Cisco 5500 Series
Release 12.2(50)SE], Cisco Flex 7500 Series
Catalyst 3650 Series
Ethernet Stackable
Switch
Supported
MSE
Devices
Cisco MSE Cisco ISE
1.0
3355
Cisco MSE Cisco ISE
1.1
Virtual
Appliance
Cisco ISE
1.2
Cisco 8500 Series
Cisco Virtual Controller
Cisco WiSM
Catalyst 3750
Switches [Cisco IOS Cisco WiSM2
Release 12.2(50)SE],
Cisco Wireless Controller
Catalyst 3850 Series on Service Ready Engine
Ethernet Stackable
(WLCM2 on SRE)
Switch
Catalyst 3750G Series
Catalyst 3550 Series Integrated Wireless LAN
Ethernet Stackable
Controllers
Switch
Cisco 5700 Series Wireless
Catalyst 4500
Controller
Switches [Cisco IOS
Cisco 5700 Series Wireless
Release
Controller (STACK)
12.2(50)SG],
Catalyst 6500
Switches [Cisco IOS
Release
12.2(33)SXI], and
[Cisco IOS XE
03.07.00.E]
Cisco NAM 2304
Appliance, Cisco
NAM 2320
Appliance, Cisco IE
2000 Series
Switches.
1. Prime Infrastructure 2.2 supports ISE 1.3 in non-FIPS mode.
Cisco Prime Infrastructure 2.2 Release Notes
4
Supported Supported
ISE Devices Lightweight APs
Cisco ISE
1.31
Cisco 600 Series,
Cisco 702W AP,
Cisco 1040 AP,
Cisco 1100 AP,
Cisco 1120 AP,
Cisco 1130 AP,
Cisco 1140 AP,
Cisco 1200 AP,
Cisco 1230 AP,
Cisco 1240 AP,
Cisco 1250 AP,
Cisco 1260 AP,
Cisco 1500 AP,
Cisco 1524 AP,
Cisco 1552C AP,
Cisco 1552CU AP,
Cisco 1552E AP,
Cisco 1552EU AP,
Cisco 1552H AP,
Cisco 1600e AP,
Cisco 1600i AP,
Cisco 2600i AP,
Cisco 2600e AP,
Cisco 2700 AP,
Cisco 3500i AP,
Cisco 3500e AP,
Cisco 3500p AP,
Cisco 3600i AP,
Cisco 3600e AP,
Cisco 3600p AP,
Cisco 3700i AP,
Cisco 3700e AP,
Cisco 3700p AP
Cisco 802agn AP,
Cisco 802gn AP,
Cisco 802hagn AP,
Cisco 801gn AP,
Cisco 801agn AP,
Cisco 1700I AP,
Cisco 1700E AP
Cisco Aironet 1570
Series APs
Supported Autonomous
APs
Cisco 702 series APs
Cisco 1600 series APs
Cisco 1530 series APs
Cisco 3500 AP
Cisco 1260 AP
Cisco 1700 AP
Cisco 2600 AP
Cisco 2700 AP
Cisco 3600 AP
Cisco 3700 AP
Cisco 1520 AP /1550
AP
Cisco 1100 series APs
Cisco 1130 series APs
Cisco 1140 series APs
Cisco 1040 series APs
Cisco 1200 series
(1200/1210/1220/1230)
Cisco 1240 series APs
Cisco 800 ISR Series,
Cisco Aironet 1310 and
1410 Bridges,
Cisco 801 AP
Non-Configurable Features for Wireless LAN Controller Software Releases
Non-Configurable Features for Wireless LAN Controller
Software Releases
The following sections describe the Wireless LAN Controller software features that are not configurable in Prime Infrastructure
Release 2.1.2 using the pre-packaged templates:
•
Non-Configurable Features for Wireless LAN Controller Release 8.0
•
Non-Configurable Features for Wireless LAN Controller Release 7.5
•
Non-Configurable Features for Wireless LAN Controller Release 7.4
Non-Configurable Features for Wireless LAN Controller Release 8.0
The following Wireless LAN Controller 8.0 software features are not configurable in Prime Infrastructure Release 2.2 using
the pre-packaged templates. You can use Prime Infrastructure CLI templates or Wireless Controller GUI to configure these
features:
•
DHCP relay option 82 sub-options (5, 151)
•
CMX FastLocate
•
Advanced Rogue reporting
•
Client Deauth /Blacklist (Geo Fencing)
•
Adaptive wIPS enhancements
•
Q-in-Q
•
Bonjour per user and per device policies
•
WLC 2500 wired guest access
•
DCA RF Profiles
•
Data Packet RSSI
•
FlexConnect + Bridge Mode for mesh enabled FlexConnect Access points.
•
Receiver Start of Packet Detection Threshold (Rx-SOP)
•
HDX – optimized roaming
•
Video Stream support for FlexConnect local switched deployments
•
AP-701E (India only) with External Antenna support
•
OEAP-600 enhancements (basic Firewall, End-user GUI enhancements, Split-tunnel for Internet traffic, Voice QOS
enhancements, HA support for OEAP)
•
AP700W vlan tagging support
•
AVC Directional Marking
Cisco Prime Infrastructure 2.2 Release Notes
5
Non-Configurable Features for Wireless LAN Controller Software Releases
Non-Configurable Features for Wireless LAN Controller Release 7.5
The following Wireless LAN Controller 7.5 software features are not configurable in Prime Infrastructure Release 2.2 using
the pre-packaged templates. You can use Prime Infrastructure CLI templates or Wireless Controller GUI to configure these
features.
•
DNS lookup for Radius and TACACS server
•
.FlexConnect AP authentication support for PEAP/EAP-TLS
•
FlexConnect AAA ACL
•
FlexConnect AAA QoS
•
Application Visibility and Control - downloadable protocol packs
•
Domain -Z support AP3600
•
Guest Access Management and web-authentication support
Non-Configurable Features for Wireless LAN Controller Release 7.4
The following Wireless LAN Controller 7.4 software features are not configurable in Prime Infrastructure Release 2.2 using
the pre-packaged templates. You can use Prime Infrastructure CLI templates or Wireless Controller GUI to configure these
features:
•
WIPS containment enhancements
•
WLC & AP provides AP NAME (MAC), AP Location string (AP Group Name) and VLAN ID for DHCP option 82 and
AAA interim accounting
•
GPON support on 1552E/1552EU
•
GPS support for outdoor
•
Support all signatures in ELM
•
11k Support
•
Spectrum Expert Mode
•
802.11r
•
Band Select/Band Steering
•
DHCP Proxy in WLAN Configuration
Cisco Prime Infrastructure 2.2 Release Notes
6
New Features and Enhancements
New Features and Enhancements
This section provides a brief description of what is new in this release. For more information about the features and benefits,
as well as hardware and software specifications, see the Cisco Prime Infrastructure 2.2 Data Sheet at:
http://www.cisco.com/en/US/products/ps12239/products_data_sheets_list.html
Support for New Wireless Image and Features
Following are some of the new supported features and enhancement with wireless in Prime Infrastructure 2.2:
•
Wireless Configuration Features 7.4/7.5/7.6
– Policy Classification Engine
– Client SSO
– PMIP IPV6 enhancements
– Rogue enhancements
– Detect Dead Radios
– Guest Description
– Flex Connect Audit Support
– Sleeping Client
– PEAP/EAP-TLS on AP in Flex standalone mode
– 802.11w
– DHCP Proxy in WLAN Config
– LED provision on AP
– 802.1x & Web Auth.
– Proactive Capacity Alarm for RFID, Clients, APs
– FlexConnect VLAN Config within FlexConnect Groups
•
Wireless 8.0 Features
– Native IPv6 Support
– Certification (Client auth using OCSP, IPsec)
Support for New Hardware and New Access Points
This release provides support for:
•
Cisco IOS XE 03.07.00.E software on the Catalyst 4500 series switches.
•
Cisco Aironet 1570 Series Access Points. For more information, see
http://www.cisco.com/c/en/us/products/wireless/aironet-1570-series/index.html.
The AP features are tied to the controller and the image running on it.
Note
Prime Infrastructure 2.2 detects LWAP 1572 as unknown device.
Cisco Prime Infrastructure 2.2 Release Notes
7
New Features and Enhancements
Converged Access Updates
Cisco Prime Infrastructure provides brand new converged access templates in the form of configuration templates, which can
be used to deploy converged access in Small and Medium sized branches.
AVC Readiness Assessment using WorkCenter
The AVC Readiness Assessment aims to analyze the routers that are currently managed by Cisco Prime Infrastructure and
provides a report that describes whether the devices are AVC capable or not and suggests appropriate actions to be taken in
order to make the device as AVC capable.
IWAN Configuration
Cisco Prime Infrastructure provides an out-of-the-box experience to configure and monitor the entire IWAN solution. The
IWAN solution comprises of various technologies like PfR, DMVPN, QOS and AVC. Users can either fully enable the IWAN
solution or pick the individual IWAN technologies.
Data Center Assurance
Cisco Prime Infrastructure allows you to manage some of the key elements of the data center including Cisco UCS platform
and Cisco Nexus platform like Nexus 9500 series in the switch mode and do the basic FCAPS on these platforms.
Prime infrastructure also shows the availability status of the UCS servers and allows users to group them into logical constructs
to help in segmenting DC network based on ownership, troubleshooting and reporting.
Operations Center
Prime Infrastructure Operations Center is a centralized (MoM – Manager of Manager) visualizer for a network environment
that has one or more Prime Infrastructure servers. The Operations Center provides a good level of visibility across multiple
Prime Infrastructure servers in single view. Users have to install the Prime Infrastructure Operations Center in the same way
they install Prime Infrastructure and use the license to enable that server as an Operations Center. For more details about
Operations Center, see Setting up the Operations Center in the Cisco Prime Infrastructure 2.2 Administration Guide.
Converged Theme
To simplify the overall operation, Prime Infrastructure 2.2 introduces a single Converged theme combining many of the
characteristics of the Classic menu and Lifecycle menu. The Classic menu is still available in Prime Infrastructure 2.2, but this
is officially deprecated and will not be present in future releases. Users should use the Converged theme for all tasks and
operations in Prime Infrastructure.
Cisco Prime Infrastructure 2.2 Release Notes
8
New Features and Enhancements
Network Topology
Cisco Prime Infrastructure provides a visual map that allows you to view the physical network topology, including the network
devices and the links that connect them. The topology maps are based on Location and User Defined groups. Topology maps
show the devices in the group as well as any links between the devices.
In addition to the main Network Topology view, you can add a Topology dashlet to Overview dashboards. You can edit the
dashlet to select a map/group to view.
As part of the Device 360 feature, a new topology view capability is available, which allows you to see an “N-Hop” topology
view for the device, showing the links and devices which are in close proximity to the device.
IPv6 Support
Prime Infrastructure 2.2 provides IPv6 support for:
•
Device discovery
•
Network facing configuration services like TFTP and SSL services over SFTP, SSH, SCP, RCP, HTTP to do software image
upgrade
•
Configuration archive
•
Configuration deployment functions
Prime Infrastructure shows the IPv6 address in the GUI wherever applicable like dashboards, deployment screens, and reports.
Plug and Play support for Prime Infrastructure High Availability Deployments
Prime Infrastructure 2.2 supports Plug and Play gateway in the following High Availability (HA) deployments models:
•
Prime Infrastructure with different IP for primary and secondary
•
Prime Infrastructure virtual IP address model
The Cisco Plug and Play provides:
•
HA on a standalone server Plug and Play gateway by providing a secondary standby Plug and Play gateway
•
HA support between the standalone Plug and Play gateway and Prime Infrastructure HA
•
HA support for Prime Infrastructure Integrated Plug and Play gateway
New REST APIs
Prime Infrastructure 2.2 supports several new Read/Write APIs that allow users to externally trigger configuration of the
WLAN on controllers and access points from outside of Prime Infrastructure GUI.
Monitoring Workflow
Prime Infrastructure uses monitoring policies to monitor devices against the thresholds you specify. When the thresholds that
you specify are reached, Cisco Prime Infrastructure issues an alarm. The alarms warn you of changing conditions before the
issues impact operations.
By default, Prime Infrastructure polls:
Cisco Prime Infrastructure 2.2 Release Notes
9
New Features and Enhancements
•
Device health metrics on supported routers, switches and hubs, storage devices, and UCS series devices.
•
Interface health metrics on WAN interface groups.
Credential Profile
Credential profiles are collections of device credentials. The credentials stored in a credential profile can include SNMP, Telnet,
SSH and HTTP credentials. Credential profiles allow you to apply a set of credentials to a device or a group of devices, instead
of entering them manually for each device.
Choose Inventory > Device Management > Credential Profiles to add, edit, delete or copy credential profiles. You can apply
a credential profile during device discovery, when manually adding a device, or during bulk import of devices
Network Device Group
Prime Infrastructure 2.2 allows you to group devices by location in a flexible way. You can create a hierarchy of location groups
(such as theater, country, region, campus, building, and floor) by adding devices manually or by adding devices dynamically.
A device should appear in one location group only, though a higher level “parent” group will also contain that device. For
example, a device that belongs to a building location group might also indirectly belong to the parent campus group.
By default, the top location of the hierarchy is the All Locations group. All devices that have not be assigned to a location
appear under the Unassigned group under All Locations.
The location groups created using Inventory > Grouping > Location & Device do not affect the hierarchy tree seen under
Maps > Wireless Maps > Site Maps (creating a new location group does not result in a new entry under Site Maps).
Improvements in Job Handling
Job handling in Prime Infrastructure 2.2 includes the following improvements:
•
Ability to schedule recurring jobs
•
Configuration job options
– Option to continue or stop on failure
– Option to copy running configuration to startup
– Option to archive configuration after deploy
•
Improved presentation of job results and error information
Improvements to High Availability
Prime Infrastructure 2.2 introduces the ability to use a single virtual IP address for a high-availability pair (for HA deployments
where the primary and secondary servers are on the same IP subnet).
Cisco Prime Infrastructure 2.2 Release Notes
10
Important Notes
Important Notes
This section contains important notes about Cisco Prime Infrastructure.
•
Due to a technical/architectural problem, the Compliance Service process is disabled in Prime Infrastructure 2.2. As a
result of this, the PSIRT compliance reports and the EoX device reports are not available in Prime Infrastructure 2.2. These
reports are expected to be available in the next version of Prime Infrastructure.
•
NetFlow data from Cisco Adaptive Security Appliance (ASA) is not supported in this release of Prime Infrastructure.
•
If your browser prompts you to save your password, make sure click no and do not allow the browser to save any passwords.
If necessary, disable the password save option in your browser.
•
While accessing Prime Infrastructure server using Internet Explorer 11, if you are unable to view buttons like Cancel, OK
delete the Temporary Internet files and Website files using the Delete Browsing History option in Internet Options.
•
Mozilla Firefox (version 29 or later) will abort or timeout the HTTP request which takes more than 300 seconds (5 minutes)
to get a response. This is to avoid unnecessary/unwanted TCP connections.
The preference used to timeout the request is “network.http.response.timeout”. Follow the steps below to modify the
preference value.
– Open a new tab.
– Type about:config
– Click I'll be careful, I promise! when you see a warning message. It loads the Firefox preference page.
– In the search bar, type network.http.response.timeout.
– Double click the preference, it will pop-up a dialog to change the value. Enter 0 and click OK.
The changes will take effect immediately.
•
The advance search returns correct search results only when you enter complete IPv6 address. The advance search options
do not work correctly if you enter partial IP address (that is, wildcard search) for IPv6 address. The quick search does not
work with full or partial IP address (that is, wildcard search).
•
The average memory utilization for Cisco 4500 controller is calculated using the average of two CLI outputs “show
memory location active and show memory location active-dc”.
•
In SWIM, the flash location of WLC is updated as “Not Applicable” as the flash details could not be collected during
inventory.
•
The NMSP connection page does not show the correct status, if the NMSP connection cannot be established between MSE
and WLC.
•
After canceling “Change MSE Assignment” operation under Services > Mobility Services > Synchronize Services, if
you again choose any map on the Synchronize Services page and click Change MSE Assignment, the “Change MSE
Assignment” pop up will appear only after:
– you click the Refresh icon in the global toolbar at the top right of Prime Infrastructure user interface and refresh the
Synchronize Services page.
or
– you logout and login back to Prime Infrastructure.
•
When a WLC is added to Prime Infrastructure, the Prime Infrastructure will be automatically registered as trap receiver on
the WLC. If Prime Infrastructure fails to register as a trap receiver, the controller status task will try to register the Prime
Infrastructure IP Address as a trap receiver on WLC during polling. This would enable Prime Infrastructure to receive all
the traps raised by WLC.
•
No upgrade support for “Unique Clients and Users Summary” report. You have to recreate all old “Unique Clients and
Users Summary” report templates after upgrading to Prime Infrastructure 2.2.
Cisco Prime Infrastructure 2.2 Release Notes
11
FAQs: Operations Center and Prime Infrastructure
•
Switch Port Tracing is supported on Cisco Ethernet switches and the following Catalyst switches: 2960, 3560, 3560-E,
3750-E, 3850, and 4500 series.
•
To increase the number of VLANs for which the client summary report can be generated, follow these steps:
– Login to PI Console.
– Switch to root user.
– Use the following File editor command:
VIM/opt/CSCOlumos/conf/rfm/classes/com/cisco/server/resources/ReportResources.properties.
– Change the value of "key ClientSummary.MaxKeys" to required value. The default value is 20.
– Restart the server.
•
If the “Change MSE Assignment” pop up does not come up after pressing cancel from the Services > Synchronize
Services > Network Designs page, you must refresh the page content by clicking the Refresh icon on the upper right
corner of the menu bar.
FAQs: Operations Center and Prime Infrastructure
The following topics cover frequently-asked questions about Operations Center and its interactions with the instances of Prime
Infrastructure that it manages.
Q. Why doesn't the aggregated Alarm Summary count shown in Operations Center match the same count shown in the
managed instances of Prime Infrastructure?
Users must make sure that Operations Center and all the Prime Infrastructure instances it is managing are using the same
alarm categories. Under normal circumstances, the following categories will be selected for display:
– Alarm Summary
– AP
– Controller
– Coverage Holes
– Mesh Links
– Mobility Service
– Performance
– Rogue AP
– Security
– Routers
– Application Performance
– Switches and Hubs
– System
To ensure that Operations Center and all its managed instances are using the same alarm categories:
Step 1
Log on to Operations Center using an ID with administrator privileges, then select Administration >
User Preferences.
Step 2
Under Alarms, click Edit Alarm Categories.
Cisco Prime Infrastructure 2.2 Release Notes
12
FAQs: Operations Center and Prime Infrastructure
Step 3
Take note of the alarm categories currently selected for Operations Center. If you need to change any of
the selections, click the check box next to the alarm category you want to select or deselect, then click
Done.
Step 4
Repeat the preceding steps on each of the managed instances of Prime Infrastructure, ensuring that the
same selections are made on each instance.
Q. Why doesn't the total alarm count shown in Operations Center match the same count shown in the managed instances?
A. By default, Operations Center counts all alarms when calculating the total alarm count, but the managed instances of Prime
Infrastructure hide Acknowledged and Cleared alarms.
Cisco Prime Infrastructure 2.2 Release Notes
13
FAQs: Operations Center and Prime Infrastructure
If you want the total alarm count on all the managed instances to match the alarm count in Operations Center, you must
set all the managed instances to show Acknowledged and Cleared alarms:
Step 1
Log in to the first managed instance of Prime Infrastructure.
Step 2
Select Administration > System Settings > Alarms and Events.
Step 3
Under Alarm Display Options, make sure that the check boxes next to “Hide acknowledged alarms”
and “Hide cleared alarms” are both unchecked.
Step 4
Click Save to save your changes.
Step 5
Repeat these steps on all the other managed instances.
Q. Why doesn't the aggregated Events and Syslogs count shown in Operations Center match the same count shown in the
managed instances?
A. Events and syslogs, by their nature, are constantly changing on managed instances. You can see this for yourself by clicking
on the Refresh button every five seconds. There is always a slight lag from the time the Event and Syslog count changes
to the time that the count is updated by the corresponding Northbound Interface (NBI) call. Since this is constantly
changing, the aggregated count displayed in Operations Center should not be compared to the individual managed
instances.
Q. Why does scrolling the Alarms and Events page sometimes result in an empty table?
A. This is a known defect in the user interface component of Prime Infrastructure. It results in an empty table when scrolling
in a large dataset.
Q. Why doesn't cross-launching to the Events page work as expected?
A. At the moment, Operations Center does not support opening the Events tab when cross launching into Prime Infrastructure.
Instead, the cross-launch opens the Alarms tab and displays nothing. To see the correct events data, you must switch to the
Events tab manually and click the Refresh button. This is a known issue in Prime Infrastructure version 2.2 and is
documented in the Release Notes.
Q. Why does cross-launching from the Device Work Center in a managed instance of Prime Infrastructure display multiple
devices instead of filtering on the selected device?
A. This is usually due to similarities among device names on your managed instance. This is a limitation in Operations Center.
Correcting this in version 2.2 would have required code changes whose risks outweighed benefits to the user. We may
address this in a later release.
Q. Why are there discrepancies when cross-launching from the Network Device Summary (NDS) dashlet to the Devices page
for Wireless Controllers (WLCs)?
A. This is an issue with differences in the way Prime Infrastructure fetches data for dashlets and individual wireless devices.
To get the Network Device Summary count, the dashlet queries a data structure that has an entry when the device is
reachable, but does not check the inventory collection status. When you cross-launch the Devices page for the open WLC,
the count comes from a table that has an entry only when the inventory collection status is successful (at least once) for
the device. Please note that this is an issue with Prime Infrastructure, not Operations Center.
Q. Are there known issues with cross launching from a specific device group on the Network Devices page?
A. There is a known issue with cross-launching from a specific device group under the Network Devices page in Operations
Center to the same device group in a managed instance. The user is redirected to the Network Devices page in the managed
instance, but all the device groups are displayed instead of the device group selected in Operations Center.
Cisco Prime Infrastructure 2.2 Release Notes
14
FAQs: Operations Center and Prime Infrastructure
Q. Why does cross-launching from the Alarm Summary dashlet in a managed instance to the Alarms & Events page in
Operations Center yield unexpected results?
A. This is a known issue with version 2.1 managed instances only. It is not seen with version 2.2 managed instances. The
Alarm Summary dashlet uses different SQL queries in versions 2.1 and 2.2, which results in this issue.
Q. Why cross-launching working incorrectly for third-party APs on the Network Device Summary dashlet?
A. There is a known issue in cross-launching from the Network Device Summary dashlet for third-party APs in Operations
Center. When you cross-launch from Operations Center, none of the third-party APs are displayed on the Network Devices
page.
Q. Cross-launching for syslogs does not work as expected.
A. Currently, Prime Infrastructure does not support filtering by Instance ID for syslogs. As a result, Operations Center cannot
support filtering on syslogs when cross-launching to a managed instance of Prime Infrastructure.
Q. Why is an incorrect aggregated Unified APs count shown on the Device Work Center page?
A. This is caused by an issue in the Prime Infrastructure Northbound Interface (NBI).
Q. Does Operations Center support third-party devices?
A. Not currently. Since Prime Infrastructure queries third-party devices directly, there is no corresponding Northbound
Interface API to retrieve their data, so they are not displayed in Operations Center.
Q. Why does Quickview under Network Devices display an incorrect count?
A. This issue is seen only when using Operations Center to manage instances of Prime Infrastructure version 2.1. This issue
was resolved in Prime Infrastructure version 2.2.
Q. Why is there a discrepancy between version 2.1 and 2.2 in the Total AP Count on the Network Device Summary dashlet?
A. The definitions of Reachable and Unreachable APs changed in Prime Infrastructure. Here are the 2.2 definitions:
– Reachable: The AP's Operational Status is “registered” and its Admin Status is “enabled”.
– “Unreachable: The AP's Operational Status is “unregistered” and its Admin Status is “enabled”.
In the 2.1 definitions, APs were classified as Unreachable if their Admin Status was “disabled” (irrespective of their
Operational Status). Also, the dashlet title “Total AP Count” has been changed to “Operational AP”.
Q. Why can't you view inventory details of Wireless Controllers (WLCs) from version 2.1 managed instances?
A. This is primarily due to a model change between versions 2.1 and 2.2. In 2.1, the “Reachable” data for WLCs was stored
as a boolean, but this was changed to an integer in 2.2. As a result, Operations Center cannot un-marshall the result for 2.1
instances. This causes the message “Unable to load data” to be displayed when WLCs are selected from 2.1 instances.
Q. Why are there differences between the VLAN ID and Association ID on the Clients and Users page in Operations Center
and the same page given in the Prime Infrastructure managed instances?
A. This happens due to quick updating of these values. If you update these values in Operations Center, the same data on a
Prime Infrastructure managed instance may have already changed.
Q. Why does the Performance dashboard show only one Device tab after I remove the Operations Center license?
A. This is a known issue with a fix to be included in a later release. At the moment, you can resolve the issue manually by
simply refreshing the Performance dashboard in the user interface.
Cisco Prime Infrastructure 2.2 Release Notes
15
FAQs: Operations Center and Prime Infrastructure
Q. Why is there a discrepancy between what Operations Center and the managed instances show in the “CPU Utilization” and
“Memory Utilization” fields for Autonomous APs on the Device Details page?
A. One reason for the discrepancy is that these values change very quickly. When you update these values in Operations
Center, the same data on one or more of the Prime Infrastructure managed instances may have already changed.
Q. Why do Operations Center and Prime Infrastructure have minor discrepancies in the report values they generate?
A. This is expected behavior. Prime Infrastructure generates its report values using fractional values at its disposal, but
Operations Center aggregates these values using a set of rounded numbers. This results in the discrepancies.
Q. Why is report data not being polled from 2.1 Prime Infrastructure instances?
A. If you try to generate a report in Operations Center with the same name as an existing report on a 2.1 Prime Infrastructure
instance, the data for that instance will be ignored in Operations Center. To work around this issue, specify a report name
that is unique across both Operations Center and all your managed Prime Infrastructure instances.
Q. Why is there a performance discrepancy when generating reports between 2.1 and 2.2 managed instances?
A. Gzip compression for reports is only available on Prime Infrastructure instances of version 2.2 or later. This was not
available for older versions, so exporting and emailing reports may be slow when managing instances of version 2.1 or
earlier. To enable gzip compression in Operations Center:
Step 1
Choose Administration > System Settings > Report.
Step 2
Select Enable Compression.
Step 3
Click Save.
Q. Why isn't site information retrieved from 2.1 managed instances?
A. When choosing Performance > Device > Select a Device > Site, the site information for 2.1 instances is not retrieved.
This is due to an internal (IFM) API that changed between Prime Infrastructure version 2.1 and 2.2.
Q. Why do Prime Infrastructure Virtual Domains fail to work properly with FireFox ESR 17.0.6?
A. Virtual Domains work correctly when the browser character encoding is set to “Western(ISO-8859-1”. To fix this in
FireFox, change the settings for the browser's encoding scheme and refresh the browser.
Q. Why do Operations Center and Prime Infrastructure have different columns for the Current Associated Wired Clients table?
A. The Current Associated Wired Clients table in Operations Center has fixed columns. The same table in managed instances
of Prime Infrastructure has customizable columns. Later versions of Operations Center may change this.
Cisco Prime Infrastructure 2.2 Release Notes
16
Open Caveats
Open Caveats
Table 2 lists the Open Caveats in Cisco Prime Infrastructure Release 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 2
Open Caveats
Identifier
Description
CSCuh16286
Global search for IPv6 clients based on IP addresses is not working.
CSCul06347
When comparing the PI server and cluster, a few fields have mismatched data.
CSCul35804
Prime Infrastructure 2.0 has the CBC Mode vulnerability.
CSCun23075
Inconsistency in data for Scheduled and On demand exported reports.
CSCuo68188
The syslogs tab does not display any data in the cluster server though the PI 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.
CSCuo98439
During installation, the console window displays a spurious character on a blank screen for a long time.
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.
CSCuq04356
Unable to set mobility group multicast with IPv4 address.
CSCuq51763
Device selection refresh issue in IWAN workflow.
CSCuq57017
The “Learn more” link from deprecated classic view says “Page not found.”
CSCuq76946
All MSEs show up as unreachable.
CSCuq88241
wireless-rogue: Editing rogue rule from configure-NGWC page throws SNMP error.
CSCuq93480
System templates are missing after restoring a backed up data from another server.
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.
CSCur26128
Credential profile is not associated with WLC device.
CSCur27813
The evaluation of SSLv3 is affected by POODLE vulnerability.
CSCur43230
The job status is shown as Failure and parameters are not updated when deploying the system template
on NAM3.
CScur45282
Auto SPT is running on adhoc rogues and showing false alarm.
CSCur45975
Backups with lengthy filenames are not restored.
CSCur49012
Inventory Cat 4500: Partial Collection Fails after adding devices and requires manual synchronization.
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.
CSCur71480
Third party device is stuck in Add initiated state.
CSCur72515
The credential profile is not associated with discovered devices.
Cisco Prime Infrastructure 2.2 Release Notes
17
Resolved Caveats
Table 2
Open Caveats (continued)
Identifier
Description
CSCur80193
Unable to add WLCs as mobility group member using IPv6 address.
CSCur83964
The failover operation is not successful during HA software update.
CSCur83972
HA - Split-Brain scenario is not working properly.
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.
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.
CSCur87434
Map is not shown for client when navigating from current associated clients.
CSCur89574
Unable to delete devices with QoS on Virtual-Template interface.
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.
CSCus21471
Wired device detail inventory report throws error with single device.
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 3
Resolved Caveats
Identifier
Description
CSCuf24622
Recommendation does not work for ISR g3 (ISR-4452).
CSCug25057
OLH relaunch is required to view the Cisco Prime InfrastructureUser Guide.
CSCuh69074
Issues are present with reports created before upgrade or restore.
CSCui23932
Top N URL by Hits report has missing data.
CSCui73654
Restore preserves Eval and Permanent Licenses.
CSCui91262
The Show all Templates option is not working in CG.
CSCui95966
Container management issues are present in non-root domain.
CSCuj97104
When creating 802.11 a or b clean air template, the status of Persistent Device Propagation is disabled.
CSCuj97351
RRM Interval values are not applied to the NGWC controller.
CSCun19363
The link test on associated client fails.
CSCun21433
Adding ISE: Prime Infrastructure reports an incorrect error message.
CSCun28657
Disabling or Enabling an AP under Configure AP throws an snmp error.
CSCun64421
Unable to search for devices with IP address if only the DNS name is provided.
Cisco Prime Infrastructure 2.2 Release Notes
18
Related Documentation
Table 3
Resolved Caveats (continued)
Identifier
Description
CSCun82620
In Prime Infrastructure, sometimes the CPU spikes to 100% during Inventory Collection.
CSCun89596
Prime Infrastructure OVA does not have resource reservations.
CSCun96777
Prime Infrastructure allows delegation of QOS and AP timers templates from the Life cycle view.
CSCuo09165
Any file in the tftp folder can be downloaded over https without authentication.
CSCuo99356
An error message is displayed in PST config, AP config, and lwap template with wlc 8.0.
CSCup03919
The NDS dashlet should show total AP count based on the AP operational status.
CSCup18138
“AP Utilization” report shows peak RSSI/SNR based on the AP rather than Radio.
CSCup32040
LWAP Temp: A few combinations in Advanced filter are not working.
CSCup41681
The AP utilization report shows the wrong slot for 11ac AP.
CSCup41693
The AP utilization report shows the wrong slot for the WSSI module.
CSCup42427
Adding the ISRG3 device to Inventory affects the Virtual Domain.
CSCup44041
LWAP: Deploy Status does not refresh when on the page after temp deployment.
CSCup57279
LWAP Template Footnotes are missing.
CSCur04447
Wrong AP name, IP address, protocol fields are loading for AAP client.
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-2014 Cisco Systems, Inc. All rights reserved.
Cisco Prime Infrastructure 2.2 Release Notes
19