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):
Lifecycle view, which is organized according to the home, design, deploy, operate, report and administer menus. For more information on features of the Prime Infrastructure Lifecycle view, see the Cisco Prime Infrastructure 2.1 User Guide .
For more information on server and web client requirements, see the System Requirements section of the Cisco Prime Infrastructure 2.1 Quick Start Guide
For detailed information about installing this release of Prime Infrastructure, see the Installing Cisco Prime Infrastructure section of the Cisco Prime Infrastructure 2.1 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.1 Quick Start Guide .
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.
Step 7 Click OK .
Step 8 Choose Help > Submit Feedback (in the Classic view) or click the question mark icon at the top right and then click Submit Feedback (in the Lifecycle view). You must configure the email server and then enable data collection to configure the feedback tool.
To view the Prime Infrastructure supported devices for switches, wireless LAN controllers, access point images, Identity Services Engine (ISE), and mobility services engines (MSE), see the Cisco Prime Infrastructure 2.1 Supported Devices list at the following URL:
New Mobility Support for Cisco 2500, 3650, 3850, 5508, and WiSM2 Platforms
Hierarchical Mobility is referred to as New Mobility in the wireless LAN controller configuration. Prime Infrastructure 2.1 supports the new mobility functionality for Cisco 2500, Cisco 5508, and WiSM2 platforms that run Cisco WLC 7.6.
Mobility work center discovers 5508 and WISM 2 upgraded to 7.6 image and provide necessary operations related to building hierarchical mobility architecture involving device types such as 2500, 5508 and WISM 2.
Mobility work center discovers 3650 and 3850 as Mobility Agents.
When deploying the hierarchical mobility architecture, the wireless features such as WLAN, VLAN, security, guest anchor can be configured on Cisco 5508 and WiSM2 using the LifeCycle view.
Deploying the flat mobility architecture on Cisco 5508 and WiSM2 would be supported only in classic view and entire wireless configuration would be left as it is in classic and LifeCycle view.
For more information about the new mobility functionality on Cisco WLC, see the Hierarchical Mobility (New Mobility) the Cisco Wireless LAN Controllers and Lightweight Access Points for Release 126.96.36.199 Release Notes at:
Prime Infrastructure 2.1 enables you to manage Cisco WLC Releases 188.8.131.52 and 184.108.40.206 with the features of Cisco WLC 220.127.116.11 and earlier releases. Prime Infrastructure 2.1 does not support any features that are introduced in Cisco WLC Releases 18.104.22.168 and 22.214.171.124 except the new access point platforms and the new mobility feature. Prime Infrastructure 2.1 supports the following access points.
Note Cisco Aironet 3700p Series Access Points, which are dual-band Cisco WLC-based 802.11a/g/n/ac APs for high-density environments, with narrow beam width and high-gain antennas, are supported. Heat map is generated for all the supported antennas of 3700P access point.
Cisco Aironet 3600 Series Access Points are supported with 802.11ac module.
Changes to Antenna Band Mode
The 1530E AP model (with external antennas) operates the 5.0 GHz band in one of two antenna band modes. In the single band mode, the 5.0 radio uses antenna ports 3 and 4, each with a single band antenna, while the 2.4 radio uses antenna ports 1 and 2, each also with its own single band antenna. In the dual band mode, only two dual band antennas are used, connected to ports 1 and 2. In this case, both radios share these antennas. This can be configured from AP config page and by using AP templates.
In Cisco Prime Infrastructure Release 2.1, you can specify the Transmission Control Protocol (TCP) / User Datagram Protocol (UDP) port range in the firewall rule service. When you add a new rule or edit an existing rule under the Service column, click object selector to assign the TCP / UDP, and click OK . You can define the port numbers in the text box that appears near the protocol icon. Also, you can define the port range in the format of <start-port-number>-<end-port-number>, and this range can be configured for that specific protocol (TCP or UDP).
Application Visibility: Preview Option
In Cisco Prime Infrastructure Release 2.1, you can preview the Application Visibility CLIs before deploying the CLIs. From the DWC > Configuration > Application Visibility > AVC Interfaces , click Enable Preview from the toolbar. You can toggle between enable or disable to preview the CLIs.
After the Preview is enabled, you can select the interfaces, and click Enable pre-defined ARC Policy or Disable pre-defined AVC Policy . A pop-up window appears which contains all the commands that are to be deployed to the device. The CLI preview window contains all the commands that are necessary for configuring the specific device to the pre-defined configuration and only the difference between the intended configuration and the current configuration on the device is sent.
For example, if the device was previously deployed with the same set of configuration and no other CLI is necessary to configure the device then the preview window does not display any CLI commands. After reviewing the configuration, you may continue and deploy the configuration on the device. If the preview option is disabled, the configuration will be immediately deployed to the device without displaying the CLI commands in the preview window.
Application Visibility: Defining AVC Policy per Interface
In Cisco Prime Infrastructure Release 2.1, the application visibility feature displays the user define AVC policy per interface in application visibility interfaces. In the DWC > Configuration > Application Visibility > AVC Interfaces , the column “ Template Name” has been renamed to “AVC Policy.” There are several options that can be displayed:
If the application visibility control is configured on the interface using the Application Visibility Template, the Template <template-name> will be shown.
If the application visibility control is configured for that interface using the “one-click” option, by clicking the Enable AVC Policy on the toolbar, the Default value will be shown.
If the application visibility control is configured out-of-band, manually by the user via CLI, the Custom value will be shown.
Application Visibility: Adding Visual Indication for Activated Interface
In Cisco Prime Infrastructure Release 2.1, you can add an explicit visual indication for the interface that this activated with the application visibility control. The application visibility control status column displays the status of application visibility control for the specific interface. This is enabled with a V icon if the interface is configured with the application visibility control configuration. The column is left empty if the interface is not configured with the application visibility control configuration.
MSE Admin User Interface
In Cisco Prime Infrastructure release 2.1, you can launch the new MSE Admin UI and configure the MSE services by clicking the MSE name link from Services > Mobility Services Engines page. To view the legacy MSE UI, you should unselect the Use MSE Admin View check box in Administration > User Preferences page. By default, this check box is selected.
The MSE Admin UI allows you to:
View and manage MSE services
Configure MSE settings
View MSE maps
Get quick information via live tiles
If you have added MSE to Prime Infrastructure using a private VLAN IP address, you will not be able to access MSE Admin UI. However, you can view and configure MSE using the legacy MSE UI.
This section contains important notes about Cisco Prime Infrastructure.
If you have a large, dynamic network with a high range of roaming, some of the Prime Infrastructure monitoring and configuring screens might show different data for the same devices. For some monitoring screens, Prime Infrastructure displays data it retrieves directly from the devices. For configuration screens, Prime Infrastructure polls the devices, and because polling takes longer because of the network load, the configuration data might not refresh quickly. This limitation occurs primarily on client management screens because of client roaming in wireless networks and the increasing size and client density in such networks. Currently there is no workaround, but in subsequent releases of Wireless Controller software and Prime Infrastructure, enhancements are planned to improve data collection.
The CCX Client Statistics report does not contain client information from the Cisco 5760 Wireless Controller and Cisco Catalyst 3850 Series Switches.
Client Statistics—The client statistics data displayed in the CLI output and Prime Infrastructure UI (in the Clients and Users page) are different. This is because the CLI output displays the upstream (data sent to client) and downstream (data received from client) packet/byte count from the AP’s point of view, whereas, the Prime Infrastructure UI displays the upstream (data sent to AP and network) and downstream (data received from AP and network) packet/byte count from client's point of view.
Support for Cisco 3850 and 5760 devices are available in the Lifecycle view only.
When an 802.11ac module is installed on an Cisco 3600 AP (which is already present in Prime Infrastructure), it performs a Refresh Config operation from the Controller once the AP comes up. Similarly, when an 802.11ac module is removed from AP 3600 (which is already present in Prime Infrastructure), it performs a Refresh Config from Controller operation once the AP comes up. This behavior is applicable for the WSSI module on Cisco 3600 and 3700 access points.
The administrator should perform a “Refresh Config from Controller” or “Sync” operation for each of the network devices in Prime Infrastructure after the devices are upgraded (or the version is changed). Similarly, the administrator should perform a “Refresh Config from Controller” or “Sync” operation for each network device in Prime Infrastructure after the Prime Infrastructure server is upgraded from one release to another. These operations should be performed so that Prime Infrastructure can discover all the new features.
When you add Cisco 3850 and 5760 devices to configuration archive, ensure that TFTP is aware of the VRF default configuration. To do this configuration, use the following command:
ip tftp source-interface g0/0
You cannot apply wIPS profile to WLC 7.5 and earlier release using Prime Infrastructure 1.4.x or Prime Infrastructure 2.x with MSE 7.6 release.
SWIM Image Management—On unified WLC devices, the following features are not supported:
– The ability to recommend a compatible image for the devices that are managed from Prime Infrastructure. This is not supported on Unified WLCs because the flash requirement is not available.
– The ability to analyze the software images to determine the hardware upgrades required before you can perform the software upgrade. This is not supported on unified WLCs because there is no minimum requirement for RAM or ROM. The newly upgraded image replaces the existing image after an upgrade.
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.
Table 2 lists the Open Caveats in Cisco Prime Infrastructure Release 2.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 .
The guest client count information does not take the virtual domain configuration into account and the same information appears on all virtual domains irrespective of whether the concerned devices are a part of the virtual domain or not.
Evaluation license should be deleted automatically when permanent license is added. But in the backup/restore scenario, the permanent and evaluation licenses exist at same time and may be displayed in the UI. In this case there is no functional impact, except the user sees both licenses on the page.
A user logging in with non root domain access will observer the following symptoms:
The resource profile is not listed for selected OVAs for installing WAAS instance on ISR G3.
The installed instances of WAAS are not displayed in the Prime Infrastructure UI.
The Job Dashboard does not show container management job details.
Even if you enable Persistent Device Propagation status while creating a template, when you deploy the template to a controller and check the Persistent Device Propagation status using CLI, it shows as disabled.
When you apply 802.11 a or b RRM Intervals template to the controller, Load Measurement Interval and Coverage Measurement Interval values are not applied and are not displayed in the controller configuration page.
You can download any files placed in tftp folder over https without authentication.
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
Prime Infrastructure intermittently stops working while accessing or uploading floor maps.
Upgrade from Prime Infrastructure 2.0 to 2.1 failed.
The device password and username are displayed in the log file.
The NPE in TCA processing hook that causes DB Connection Leak.
An abnormal behavior in Prime Infrastructure 2.0. Unable to execute multiple tasks even though CPU and memory utilization are normal.
Server is not responding in the alpha network.
The Device Work Center in the Lifecycle view has an empty device list because the lifecycle state of pre-existing devices is incorrect.
A single Cisco 3850 device displays wrong device type as CiscoCatalyst38xxstack .
The Clients & Users page is not loading.
Inventory collection status for Cisco 3850 controller that runs with version 03.06.30.pi3 failed with managedobjects.wlan.NgwcWlanConfig error.
Unable to migrate to Prime Infrastructure 2.0 because of the minimum password length of SNMPv3.
Prime Infrastructure may recommend software images that are not compatible with the device.
WLC configuration backup background task stops working and fails.
The primary server shows “Unreachable” even though the secondary is “reachable.”
New Mobility support for Cisco 2500 controller.
After an upgrade, the device details page shows blank.
SyslogHandler flooded ncs*.log with error logs.
Device credentials can be exported in plain text, which is a potential security risk.
In Nexus 9000, the CA Rollback and Overwrite not complete with partial success status.
Default antenna gain for AP 702i is 13dbi in Prime Infrastructure. It should be 3 dbi for 2.4G and 5dbi for 5G, Antenna map is not accurate, which may affect MSE location accuracy.
Cisco 5760 with version 03.03.00SE gets collection Failure error.
System component level logging in Prime Infrastructure causes logs to overrun quickly.
ASR version not recognized by Prime Infrastructure from ASR version XE3.10
ISE causes out of memory, which stops Prime Infrastructure.
Prime Infrastructure shows RSL error #2032 in multiple pages.
When you add a Cisco 3650 device, the collection status fails with an error.
Device that goes into the Collection Failure State if the “ION Routing Process” banner is added for ION images to differentiate between the ACLs present in blob and routing process.
Heatmaps are not generated for Cisco 2702I APs.
The 802.11ac module functionality with IOS-XE 3.3SE is not working.
LWAP template with 802.11a/n configuration cannot be applied to Cisco 2700 AP on the Cisco 5760 Wireless Controller and Cisco Catalyst 3850 Series Switches.
802.11a/n/ac radio of an Antigua AP on the Cisco 5760 Wireless Controller and Cisco Catalyst 3850 Series Switches cannot be configured
At times, Prime Infrastructure fails to deploy lightweight AP templates.
Prime Infrastructure stops working c in the function carsDiskUsageStats.
When running the switch port tracing, the following error occurs: “Need to fix this: Need access to the UserContainer”
Prime Infrastructure's Plug and Play processor may send a CLI command which contains an incorrect location for an executable to boot from.
Device type is not updated after device upgrade.
WLAN template L2 security(WPA+WPA2) page has issues while loading.
Configuration Archive fails on Cisco 3650 AP.
Unable to display APs or anything effectively on the floor maps; the status windows shows 'Loading APs', but never does.
Internal exception when doing global audit.
Prime Infrastructure fails to discover 702W AP.
Under certain conditions, Prime Infrastructure inventory collection fails on a Cisco 3850 wireless LAN controller.
An error occurs while configuring channel parameters for 3702P AP.
Client Count report is missing in Report Launch Pad.
Wrong device type displayed Cisco Catalyst38xx.
Debug log of PAL actions not configured to be skipped, passwords exposed
A configuration deployment from Prime Infrastructure is in progress but the status may show as Failure, leaving the user with no way to know if the deployment is truly successful or complete.
Mobility Work Center does not update MA, MC and SPG.
Configuration template deletion is not working correctly.
Script execution stops working after a failover in Secondary.
Restore operation failed from Prime Infrastructure 1.3.2 to 2.1.
The Lightweight AP Status background task stops working.
The webauth template fails to push the configuration to Cisco 5760 Wireless Controller, Cisco Catalyst 3850 Series Switches, and Cisco Catalyst 3650 Switch with SNMP operation to device failed.
Udf Values are not updated and unable to export Udf Updated Device from Device Work Center.
Devices are stuck in the delete in progress state.
MSE unable to establish NMSP connection; missing username/attribute.
Image import from device fails without much details.
CLI template support for Cisco 3650 devices.
Prime Infrastructure installations upgraded from very early releases of NCS may not run the Hourly Aggregation background task successfully.
Partial completion of inventory collection for Nexus 5548 on Prime Infrastructure 2.0. Missing VLAN, interface, and port channel information.
Single Cisco 3650 device displayed wrong device type CiscoCatalyst38xxstack.
CPU and memory utilization data are missing from some of Prime Infrastructure’s graphs, due to the Device Health template being applied to all devices, rather than to specific groups.
Unable to delete the devices from Prime Infrastructure. This issue occurs in both Classic and Lifecycle views.
The upgrade analysis report is not showing the proper image.
SWIM distribution fails for Nexus 9000.
IFM Inventory throws Exception when SyncDevice is invoked.
The Data Cleanup background task may take a very long time in larger installations.
Cisco 5760 Wireless Controller and Cisco Catalyst 3850 Series Switches show Inventory Collection failure.
Large event table upgrade took very long time.
When you try to configure a WLC in lifecycle view, the feature configuration page does not load.
Cisco WLC could not be removed from Prime Infrastructure.
LWAP template does not work for 802.11a/n/ac radio of a Cisco 3700 AP connected to Cisco 5760 Wireless Controller or Cisco Catalyst 3850 Series Switches device.
Problem with checking NMSP from Prime Infrastructure 2.1 to MSE 126.96.36.199.
Discrepancy in the license count within Prime Infrastructure.
The Service > MSE > Admin View page throws error on Prime Infrastructure with MSE 7.6.
Audit is not working after booting Cisco 5700 Wireless Controller from Prime Infrastructure.
In the Home > Overview > Client > Client Troubleshooting, enter a MAC address of an active client and troubleshoot, which throws an error.
Remove APs from a particular virtual domain from virtual domain page is not persisted.
Netflow records from certain devices are not processes and do not show up in the dashlets and reports.
Prime Infrastructure’s Data Cleanup background task may fail, leaving Oracle messages in the logs regarding inability to extend tables and tablespaces.
The Prime Infrastructure background task stops waiting.
Processing of Netflow records stops.
Wrong device type in all stacks (3850/3650/5760).
Stack (3850/3650/5760) device not displayed in virtual domain users.
Prime Infrastructure has the CISCO-LWAPP-AP-MIB object “floorLabel” mapped as cLApEntry 60 when it is actually cLApEntry 65. This can cause SNMP transaction failures.
ISR G3 inventory collection is partial; image details not gathered
Editing the 532I radio is throwing SNMP operation failed error.
NAM 6.0 records are not processed correctly, there is a shift in record fields.
Client still seen as associated even after deleting the controller.
Addition of Cisco Catalyst 3850 Series Switches with latest image (03.06.35E) are failing due to SNMP connectivity failure.
Sometimes Prime Infrastructure may crash when several users are accessing maps, leaving an .hprof file in the crash directory (that is, /opt/CSCOlumos/crash).
NMS Server stops working because of an Out of Memory error.
The Admin > Software Update > Check for updates page returns a ‘cannot reach cisco.com’ error.
You can access additional Cisco Prime Infrastructure documentation at:
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.
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.