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:
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
– 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
– Native IPv6 Support
– Certification (Client auth using OCSP, IPsec)
Support for New Hardware and New Access Points
This release provides support for:
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.
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.
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.
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.
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 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.
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.
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:
- Device health metrics on supported routers, switches and hubs, storage devices, and UCS series devices.
- Interface health metrics on WAN interface groups.
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).
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
– Coverage Holes
– Mesh Links
– Mobility Service
– Rogue AP
– Application Performance
– Switches and Hubs
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.
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?
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.
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?
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?
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?
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?
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)?
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?
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.
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?
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?
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.
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?
This is caused by an issue in the Prime Infrastructure Northbound Interface (NBI).
Q. Does Operations Center support third-party devices?
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?
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?
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?
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?
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?
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.
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?
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?
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?
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?
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?
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?
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?
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.