Cisco Prime Infrastructure 2.1 Release Notes Last Updated: 10 October, 2014 OL-30963-01 These release notes contain 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 3 • New Features and Enhancements, page 4 • Important Notes, page 7 • Open Caveats, page 8 • Resolved Caveats, page 11 • Related Documentation, page 14 • Obtaining Documentation and Submitting a Service Request, page 14 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): • 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. • Classic view, 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.1. System Requirements For more information on server and web client requirements, see the System Requirements section of the Cisco Prime Infrastructure 2.1 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.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. 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. Cisco Prime Infrastructure 2.1 Release Notes 2 OL-30963-01 Prime Infrastructure Licenses 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. Prime Infrastructure Licenses For detailed information on Prime Infrastructure licensing, see the Cisco Prime Infrastructure 2.1 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 Lifecycle view (if applicable). Step 3 Click the question mark icon (Help) at the top right. Step 4 Click Devices Level Support. You can also view the Cisco Prime Infrastructure 2.1 Supported Devices list at the following URL: http://www.cisco.com/c/en/us/support/cloud-systems-management/prime-infrastructure/products-devic e-support-tables-list.html Supported Wireless LAN Controller Hardware Models Table 1 lists the wireless devices and their software versions that are supported by Prime Infrastructure 2.1. Table 1 Supported Wireless LAN Controller Hardware Models and Software Versions Wireless LAN Controller Hardware Models Wireless LAN Controller Software Versions Cisco 2100 Series 7.0.x Cisco 2500 Series 7.0 through 7.6.x Cisco 4400 Series 7.0.x Cisco 5500 Series 7.0 through 7.6.x Cisco Flex 7500 Series 7.0 through 7.6.x Cisco 8500 Series 7.3 through 7.6.x Cisco Virtual Controller 7.3 through 7.6.x Cisco Prime Infrastructure 2.1 Release Notes OL-30963-01 3 New Features and Enhancements Table 1 Supported Wireless LAN Controller Hardware Models and Software Versions (continued) Wireless LAN Controller Hardware Models Wireless LAN Controller Software Versions Cisco WiSM 7.0.x Cisco WiSM2 7.0 through 7.6.x Cisco Wireless Controller on Service Ready Engine 7.2.110.0 (WLCM2 on SRE) Cisco Catalyst 3650 Switch 03.03.00 SE / 03.03.01 SE / 03.03.02 SE Cisco Catalyst 3850 Switch 03.02.02 SE / 03.02.03 SE / 03.03.00 SE / 03.03.01 SE / 03.03.02 SE Cisco Catalyst 36xx stack-able Ethernet Switch 03.03.00 SE / 03.03.01 SE / 03.03.02 SE Cisco Catalyst 38xx stack-able Ethernet Switch 03.03.00 SE / 03.03.01 SE / 03.03.02 SE Cisco 5700 Series Wireless Controller 03.02.02 SE / 03.02.03 SE / 03.03.00 SE / 03.03.01 SE / 03.03.02 SE Cisco Catalyst 57xx stack-able Ethernet Switch 03.03.00 SE / 03.03.01 SE / 03.03.02 SE 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_Compatibil ity_Matrix.html 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: http://www.cisco.com/c/en/us/support/cloud-systems-management/prime-infrastructure/products-devic e-support-tables-list.html 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.1 Data Sheet at: http://www.cisco.com/en/US/products/ps12239/products_data_sheets_list.html 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. Cisco Prime Infrastructure 2.1 Release Notes 4 OL-30963-01 New Features and Enhancements • 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 7.3.112.0 Release Notes at: http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn7_3_112_0.html#wp10 54557 Support for Cisco Catalyst 3650 Prime Infrastructure 2.1 enables you to manage Cisco Catalyst 3650. For more information about Cisco Catalyst 3650, see http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-3650-series-switches/data_sheet_c 78-729449.html Support for New Access Points Prime Infrastructure 2.1 enables you to manage Cisco WLC Releases 7.5.102.0 and 7.6.100.0 with the features of Cisco WLC 7.4.121.0 and earlier releases. Prime Infrastructure 2.1 does not support any features that are introduced in Cisco WLC Releases 7.5.102.0 and 7.6.100.0 except the new access point platforms and the new mobility feature. Prime Infrastructure 2.1 supports the following access points. • Cisco Aironet 3700 Series Access Points are supported. For more information, see http://www.cisco.com/en/US/products/ps13367/index.html. 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. • 3700I/E • 3700P • Cisco AP3600 with 802.11ac • 702 I • Cisco Aironet 1530 Series Outdoor Access Points are supported. For more information, see http://www.cisco.com/en/US/products/ps12831/index.html. • 1530I/E • 3600P • Cisco Aironet 3600 Series Access Points are supported with 802.11ac module. Cisco Prime Infrastructure 2.1 Release Notes OL-30963-01 5 New Features and Enhancements 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. Zone-Based Firewall 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. Cisco Prime Infrastructure 2.1 Release Notes 6 OL-30963-01 Important Notes 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. Important Notes 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. Cisco Prime Infrastructure 2.1 Release Notes OL-30963-01 7 Open Caveats • 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. Open Caveats 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. Table 2 Open Caveats Identifier Description CSCue78806 After importing dot11a-rrm-DCA or dot11b-rrm-DCA template, the template details do not show up. CSCuf24622 Image recommendation is not supported for ISR 4452 devices. CSCug24469 Automatic refresh of dynamic group membership does not work on UDF attribute rules. CSCug25057 After you launch the Cisco Prime Infrastructure User Guide Online help and switch to another book, you are unable to switch to the Cisco Prime Infrastructure User Guide Online help. CSCug82408 Image import and image distribution operations are not supported for Cisco Nexus 7K devices. Cisco Prime Infrastructure 2.1 Release Notes 8 OL-30963-01 Open Caveats Table 2 Open Caveats (continued) Identifier Description CSCug87069 When Nexus devices are running with dual images, the Image Import job imports only one of the images and shows the job status as successful. CSCug87083 Image Management operations (image import and recommendation) do not work for CRS and GSR (12000 series) devices running Cisco IOS-XR software. CSCuh00434 Image distribution fails for Cisco Nexus 5k device. CSCuh23514 Cisco Prime Infrastructure 2.0 EoX report does not list some of the EoL devices. CSCuh51446 When you try to save the Override Global Username Password option for AP, you see an SNMP error. CSCuh54842 Image filtering feature does not work for few devices running Cisco IOS XE or Cisco NX operating system. CSCuh59795 For the 4 port SHDSL card devices, 0 is displayed in the port count in the Device Work Center. CSCuh62796 Software Image import and distribution is not supported for patch images (.rpm files) on NAM devices. CSCuh68205 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. CSCuh69074 After a restore of a backup from a previous release, if the previous release had custom reports, some of the reports may have issues. CSCuh72491 1. Log in to PI 2.0 server as root user. 2. Create a few child virtual domains under ROOT-DOMAIN. 3. Navigate to the child domains as the root user. 4. No child domain are listed in the drop down menu from the Virtual Domain drop-down. CSCuh79873 Prime Infrastructure's Hourly Aggregation task takes a great deal of disk I/O capacity. CSCuh83607 In the servers with high load, the Events and Syslogs tables take very long time to load. CSCuh97713 Image import operations for Cisco Catalyst 4500 devices running Cisco IOS-XE software fails. CSCui15261 The Client Count graphs in Prime Infrastructure are missing results from some WLCs. CSCui18117 In some cases, only partial inventory information is collected for Cisco ISR 3945 devices. CSCui18842 The UDI information is not shown for A’s joined to Cisco 5700 Series Wireless Controller and Cisco Catalyst 3850 Series Switches. CSCui23932 When a URL has special characters, especially a comma (,) the Top N URL dashlet shows an empty URL label for the bars of the chart. CSCui25541 Bulk deletion of APs (for example, 500 at a time) from the Lifecycle view is not very user friendly. CSCui46336 ACLs are getting re-ordered while creating the ACL template with Prime Infrastructure 1.3 and 2.0. CSCui73654 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. CSCui86942 Sometimes the system may show a lag in the running jobs based on the frequency of a job and the load on the system. CSCui91262 Show All templates option is not working in Configuration Groups. CSCui95238 In the Clients and Users UI, some of the client attributes show up as “Data Not Available” instead of “Not Applicable.” Cisco Prime Infrastructure 2.1 Release Notes OL-30963-01 9 Open Caveats Table 2 Open Caveats (continued) Identifier Description CSCui95966 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. CSCuj97104 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. CSCuj97351 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. CSCul34860 Prime Infrastructure does not discover 802.11ac Radio module connected to AP3600. CSCul87396 Inventory for 7600 routers has Partial Collection status with the reason “Unable to collect all interfaces information except Ethernet interfaces.” CSCun14607 When mobility member is deleted from the mobility domain, if there are any misconfiguration done outside Prime Infrastructure the deletion operation fails. CSCun19363 Prime Infrastructure throws error when you perform Link test on a client. CSCun21433 When adding ISE to Prime Infrastructure, Prime Infrastructure incorrectly indicates that the MSE server is unreachable; the error message should indicate that the user account on ISE is disabled. CSCun21802 In the Context Aware dashboard, when you enter a user name in the Location Assisted Client Troubleshoot field and click Troubleshoot, the results might not be correct. CSCun28657 Prime Infrastructure throws SNMP error when you disable AP admin status in Configure > AP page. CSCun35717 Access points are not displayed in Device Work Center > Site Groups even though the APs appear on maps of these sites. CSCun64421 When you add devices by DNS names, empty page gets displayed when device IP is clicked in clients and users page. CSCun82620 Prime Infrastructure may spike CPU utilization to 100% during inventory collection. CSCun89596 Prime Infrastructure OVAs might appear to be slow, even though the CPU utilization is low. CSCun95733 Reports such as Busiest APs and AP profile status get stuck when both the protocols (802.11a/n/ac and 802.11b/g/n) are selected from Reports > Report Launch Pad > Device page. CSCun96777 Prime Infrastructure allows you to delete QOS and AP timers templates from Life cycle view. CSCuo09165 You can download any files placed in tftp folder over https without authentication. Cisco Prime Infrastructure 2.1 Release Notes 10 OL-30963-01 Resolved Caveats Resolved Caveats Click the identifier to view the impact and workaround for the caveat. This information is displayed in the Bug Search Tool. You can track the status of the resolved caveats using the Bug Search Tool. Table 3 Resolved Caveats Identifier Description CSCuh73208 Prime Infrastructure intermittently stops working while accessing or uploading floor maps. CSCun11428 Upgrade from Prime Infrastructure 2.0 to 2.1 failed. CSCun25991 The device password and username are displayed in the log file. CSCun34117 The NPE in TCA processing hook that causes DB Connection Leak. CSCun49513 An abnormal behavior in Prime Infrastructure 2.0. Unable to execute multiple tasks even though CPU and memory utilization are normal. CSCuo05689 Server is not responding in the alpha network. CSCul45909 The Device Work Center in the Lifecycle view has an empty device list because the lifecycle state of pre-existing devices is incorrect. CSCun07036 A single Cisco 3850 device displays wrong device type as CiscoCatalyst38xxstack. CSCul29122 The Clients & Users page is not loading. CSCun06850 Inventory collection status for Cisco 3850 controller that runs with version 03.06.30.pi3 failed with managedobjects.wlan.NgwcWlanConfig error. CSCum03560 Unable to migrate to Prime Infrastructure 2.0 because of the minimum password length of SNMPv3. CSCun01351 Prime Infrastructure may recommend software images that are not compatible with the device. CSCuj18800 WLC configuration backup background task stops working and fails. CSCul22379 The primary server shows “Unreachable” even though the secondary is “reachable.” CSCuj64398 New Mobility support for Cisco 2500 controller. CSCum95615 After an upgrade, the device details page shows blank. CSCuf90356 SyslogHandler flooded ncs*.log with error logs. CSCuj22664 Device credentials can be exported in plain text, which is a potential security risk. CSCum91992 In Nexus 9000, the CA Rollback and Overwrite not complete with partial success status. CSCum85755 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. CSCul56994 Cisco 5760 with version 03.03.00SE gets collection Failure error. CSCul88522 System component level logging in Prime Infrastructure causes logs to overrun quickly. CSCuh16407 ASR version not recognized by Prime Infrastructure from ASR version XE3.10 CSCuj39246 ISE causes out of memory, which stops Prime Infrastructure. CSCuj41410 Prime Infrastructure shows RSL error #2032 in multiple pages. CSCuj94393 When you add a Cisco 3650 device, the collection status fails with an error. CSCum84888 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. CSCum82083 Heatmaps are not generated for Cisco 2702I APs. Cisco Prime Infrastructure 2.1 Release Notes OL-30963-01 11 Resolved Caveats Table 3 Resolved Caveats (continued) Identifier Description CSCuj44595 The 802.11ac module functionality with IOS-XE 3.3SE is not working. CSCum81676 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. CSCum81604 802.11a/n/ac radio of an Antigua AP on the Cisco 5760 Wireless Controller and Cisco Catalyst 3850 Series Switches cannot be configured CSCum81216 At times, Prime Infrastructure fails to deploy lightweight AP templates. CSCuj45674 Prime Infrastructure stops working c in the function carsDiskUsageStats. CSCuj46300 When running the switch port tracing, the following error occurs: “Need to fix this: Need access to the UserContainer” CSCum70332 Prime Infrastructure's Plug and Play processor may send a CLI command which contains an incorrect location for an executable to boot from. CSCum26099 Device type is not updated after device upgrade. CSCum66806 WLAN template L2 security(WPA+WPA2) page has issues while loading. CSCuj94436 Configuration Archive fails on Cisco 3650 AP. CSCul84896 Unable to display APs or anything effectively on the floor maps; the status windows shows 'Loading APs', but never does. CSCum24146 Internal exception when doing global audit. CSCum60145 Prime Infrastructure fails to discover 702W AP. CSCum59332 Under certain conditions, Prime Infrastructure inventory collection fails on a Cisco 3850 wireless LAN controller. CSCum59261 An error occurs while configuring channel parameters for 3702P AP. CSCuj67714 Client Count report is missing in Report Launch Pad. CSCum59216 Wrong device type displayed Cisco Catalyst38xx. CSCul24219 Debug log of PAL actions not configured to be skipped, passwords exposed CSCul64857 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. CSCul34786 Mobility Work Center does not update MA, MC and SPG. CSCuj88015 Configuration template deletion is not working correctly. CSCul17249 Script execution stops working after a failover in Secondary. CSCum54583 Restore operation failed from Prime Infrastructure 1.3.2 to 2.1. CSCuj53453 The Lightweight AP Status background task stops working. CSCuj99747 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. CSCum50613 Udf Values are not updated and unable to export Udf Updated Device from Device Work Center. CSCuj90236 Devices are stuck in the delete in progress state. CSCuj56905 MSE unable to establish NMSP connection; missing username/attribute. CSCuj99891 Image import from device fails without much details. CSCuj61116 CLI template support for Cisco 3650 devices. Cisco Prime Infrastructure 2.1 Release Notes 12 OL-30963-01 Resolved Caveats Table 3 Resolved Caveats (continued) Identifier Description CSCuj74690 Prime Infrastructure installations upgraded from very early releases of NCS may not run the Hourly Aggregation background task successfully. CSCum16230 Partial completion of inventory collection for Nexus 5548 on Prime Infrastructure 2.0. Missing VLAN, interface, and port channel information. CSCun07323 Single Cisco 3650 device displayed wrong device type CiscoCatalyst38xxstack. CSCun08232 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. CSCua78827 Unable to delete the devices from Prime Infrastructure. This issue occurs in both Classic and Lifecycle views. CSCun15334 The upgrade analysis report is not showing the proper image. CSCun16895 SWIM distribution fails for Nexus 9000. CSCun20460 IFM Inventory throws Exception when SyncDevice is invoked. CSCul55001 The Data Cleanup background task may take a very long time in larger installations. CSCun30997 Cisco 5760 Wireless Controller and Cisco Catalyst 3850 Series Switches show Inventory Collection failure. CSCun31892 Large event table upgrade took very long time. CSCun32000 When you try to configure a WLC in lifecycle view, the feature configuration page does not load. CSCun32617 Cisco WLC could not be removed from Prime Infrastructure. CSCuj92252 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. CSCun35251 Problem with checking NMSP from Prime Infrastructure 2.1 to MSE 7.4.100.0. CSCun35277 Discrepancy in the license count within Prime Infrastructure. CSCun35356 The Service > MSE > Admin View page throws error on Prime Infrastructure with MSE 7.6. CSCun35370 Audit is not working after booting Cisco 5700 Wireless Controller from Prime Infrastructure. CSCun42740 In the Home > Overview > Client > Client Troubleshooting, enter a MAC address of an active client and troubleshoot, which throws an error. CSCun45058 Remove APs from a particular virtual domain from virtual domain page is not persisted. CSCun46378 Netflow records from certain devices are not processes and do not show up in the dashlets and reports. CSCun46608 Prime Infrastructure’s Data Cleanup background task may fail, leaving Oracle messages in the logs regarding inability to extend tables and tablespaces. CSCud08265 The Prime Infrastructure background task stops waiting. CSCun60396 Processing of Netflow records stops. CSCun64951 Wrong device type in all stacks (3850/3650/5760). CSCun65012 Stack (3850/3650/5760) device not displayed in virtual domain users. CSCun65943 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. CSCun70699 ISR G3 inventory collection is partial; image details not gathered CSCun70957 Editing the 532I radio is throwing SNMP operation failed error. CSCun72635 NAM 6.0 records are not processed correctly, there is a shift in record fields. Cisco Prime Infrastructure 2.1 Release Notes OL-30963-01 13 Related Documentation Table 3 Resolved Caveats (continued) Identifier Description CSCun75802 Client still seen as associated even after deleting the controller. CSCun76422 Addition of Cisco Catalyst 3850 Series Switches with latest image (03.06.35E) are failing due to SNMP connectivity failure. CSCun79826 Sometimes Prime Infrastructure may crash when several users are accessing maps, leaving an .hprof file in the crash directory (that is, /opt/CSCOlumos/crash). CSCun92196 NMS Server stops working because of an Out of Memory error. CSCum37804 The Admin > Software Update > Check for updates page returns a �cannot reach cisco.com’ error. 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.1 Release Notes 14 OL-30963-01
© Copyright 2024 Paperzz