Cisco Prime Infrastructure 2.1.2 Release Notes
Last Updated: November 18, 2014
These release notes contain the following sections:
•
Introduction, page 2
•
System Requirements, page 2
•
Installation Guidelines, page 2
•
Upgrading Prime Infrastructure, page 7
•
Submitting Feedback, page 8
•
Prime Infrastructure Licenses, page 8
•
Supported Devices, page 8
•
Supported Wireless LAN Controller Hardware Models, page 9
•
New Features and Enhancements, page 13
•
Resolved Caveats, page 14
•
Related Documentation, page 17
•
Obtaining Documentation and Submitting a Service Request, page 17
Cisco Systems, Inc.
www.cisco.com
Introduction
Introduction
This is a patch release for Cisco Prime Infrastructure 2.1.
You can install this patch release on top of your existing Prime Infrastructure 2.1 installation or Prime
Infrastructure 2.1.1 patch.
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
The following sections explain how to install the patch.
Before You Begin Installing the Patch
Caution
Once you install this patch, you cannot un-install or remove it.
Because the patch is not removable, it is important to have a way to revert your system to the original
version in case hardware or software problems cause the patch installation to fail.
To ensure you can do this, take a backup of your system before downloading and installing this UBF
patch.
To revert to the original Prime Infrastructure 2.1 installation, follow these steps:
1.
Reinstall Prime Infrastructure 2.1 from an OVA or ISO distribution.
2.
Restore the data from the backup that you made before applying the patch.
Similarly, if you are running Prime Infrastructure 2.1 in a Virtual Machine (VM) and your organization
permits taking VM snapshots, use the VMware client to take a VM snapshot before applying this patch.
Store the snapshot in an external storage repository, and restore from the snapshot if the patch is
unsuccessful.
If you are installing the patch as part of a High Availability (HA) implementation, you will want to
ensure that the network links between the two servers provide maximum bandwidth and low latency
throughout the patch install. For more information, see Troubleshooting Patch Installs in HA
Implementations.
Cisco Prime Infrastructure 2.1.2 Release Notes
2
Installation Guidelines
Installing the Patch
Make sure you have completed the recommended preparation steps given in Before You Begin Installing
the Patch, page 2.
If your current Prime Infrastructure implementation has High Availability enabled, follow the steps in
Installing the Patch With High Availability instead of the steps below.
If you are currently using Prime Infrastructure without enabling High Availability, follow the steps
below to install the patch.
Step 1
Point your browser to the software patches listing for Cisco Prime Infrastructure 2.1.
Step 2
Click the Download button for the Release 2.1.2 patch file (pi212_20141118_01.ubf), and save the file
locally.
Step 3
Log in to the Prime Infrastructure server using an ID with administrator privileges and choose
Administration > Software Update.
Step 4
Click Upload Update File and browse to the location where you saved the patch file. Click OK to upload
the file.
Step 5
When the upload is complete:
a.
On the Software Upload page, confirm that the Name, Published Date and Description of the patch
file are correct.
b.
Select the patch file and click Install.
c.
You will see a popup message indicating that the installation is complete. You should also see a
listing for the patch in the “Updates” table, with a “Yes” in the “Installed” column, and a “Yes” in
the “Pending Restart” column.
Step 6
Restart the server by first executing the ncs stop command and then the ncs start command, as explained
in Running Commands.
Step 7
Verify that the patch is installed by logging into the server and choosing Administration > Software
Update. You should see a listing for the patch in the “Updates” table, with a “Yes” in the “Installed”
column, and a “No” in the “Pending Restart” column.
Cisco Prime Infrastructure 2.1.2 Release Notes
3
Installation Guidelines
Installing the Patch With High Availability
Make sure you have completed the recommended preparation steps given in Before You Begin Installing
the Patch.
If you are not using the Prime Infrastructure High Availability (HA) feature, follow the steps in Installing
the Patch instead of the steps below.
If your current Prime Infrastructure implementation has High Availability enabled, follow the steps
below to install the patch. You must start the patch installation with the primary server in “Primary
Active” state and the secondary server in “Secondary Syncing” state.
Patching of the primary and secondary servers takes approximately one hour. During that period, both
servers will be down. If you have trouble at any point, see Troubleshooting Patch Installs in HA
Implementations.
Step 1
Ensure that your HA implementation is enabled and ready for update:
a.
Log in to the primary server using an ID with Administrator privileges.
b.
Select Administration > System Settings > High Availability, The primary server state displayed
on the HA Status page should be “Primary Active”.
c.
Select HA Configuration. The current Configuration Mode should show “HA Enabled”.
d.
The Failover Type must be set to “Manual” throughout the patch installation. If Failover Type is
currently set to “Automatic”, select “Manual” and then click Save.
e.
Access the secondary server’s Health Monitor (HM) web page by pointing your browser to the
following URL:
https://<ServerIP>:8082
where ServerIP is the IP address or host name of the secondary server.
Step 2
Step 3
f.
You will be prompted for the authentication key entered when HA was enabled. Enter it and click
Login.
g.
Verify that the secondary server state displayed on the HM web page is “Secondary Syncing”.
Download the patch:
a.
Point your browser to the software patches listing for Cisco Prime Infrastructure 2.1.
b.
Click the Download button for the Release 2.1.2 patch file (pi212_20141118_01.ubf), and save the
file locally.
Install the patch on the secondary server:
a.
Access the secondary server’s HM web page by pointing your browser to the following URL:
https://<ServerIP>:8082
where ServerIP is the IP address or host name of the secondary server.
b.
You will be prompted for the authentication key entered when HA was enabled. Enter it and click
Login.
c.
Choose the HM web page’s Software Update link. You will be prompted for the authentication key
a second time. Enter it and click Login again.
d.
Click Upload Update File and browse to the location where you saved the patch file.
e.
Click OK to upload the patch file.
Cisco Prime Infrastructure 2.1.2 Release Notes
4
Installation Guidelines
f.
When the upload is complete: On the Software Upload page, verify that the Name, Published Date
and Description of the patch file are correct.
g.
Select the patch file and click Install. When the installation is complete, you will see a popup
message confirming this.
h.
After the installation is complete on the secondary server, verify that the Software Updates page
shows:
– In the “Installed” column: A “Yes” opposite the listing for this patch.
– In the “Pending Restart” column: A “Yes” for the secondary server. Do not restart the secondary
server at this point.
Step 4
Install the patch on the primary server:
a.
Log in to the primary server using an ID with administrator privileges and choose Administration
> Software Update.
b.
Click Upload Update File and browse to the location where you saved the patch file.
c.
Click OK to upload the patch file.
d.
When the upload is complete: On the Software Upload page, verify that the Name, Published Date
and Description of the patch file are correct.
e.
Select the patch file and click Install. When the installation is complete, you will see a popup
message confirming this.
f.
After the installation is complete on the primary server, verify that the Software Update page shows:
– In the “Installed” column: A “Yes” opposite the listing for this patch.
– In the “Pending Restart” column: A “Yes” for the primary server. Do not restart the primary
server at this point.
Step 5
Step 6
Stop the servers in the following sequence, using the commands explained in Running Commands:
a.
On the secondary server, run the ncs stop command.
b.
On the primary server, run the ncs stop command.
Re-start and monitor the servers in the following sequence, using the commands explained in Running
Commands:
a.
On the secondary server, run:
– The ncs start command to restart the secondary server. Wait for the processes on the secondary
to restart.
– The ncs status command to verify that the processes on the secondary have re-started.
– The ncs ha status command to verify that the secondary state is “Secondary Lost Primary”.
b.
Once the secondary server is in “Secondary Lost Primary” state: On the primary server, run:
– The ncs start command to restart the primary server. Wait for the processes on the primary to
restart.
– The ncs status command to verify that the primary’s Health Monitor and other processes have
re-started.
Once all the processes on the primary are up and running, automatic HA registration will be triggered.
This normally completes after a few minutes.
Cisco Prime Infrastructure 2.1.2 Release Notes
5
Installation Guidelines
Step 7
Once registration completes, verify the patch installation as follows:
a.
Run the ncs ha status command on both the primary and secondary servers. You should see the
primary server state change from “HA Initializing” to “Primary Active”. You should see the
secondary server state change from “Secondary Lost Primary” to “Secondary Syncing”.
b.
Log in to the primary server and access its Software Update page as you did earlier. The “Installed”
column should show “Yes” and the “Pending Restart” column should show “No” for the installed
patch.
c.
Access the secondary server’s Health Monitor page as you did earlier. The “Installed” column
should show “Yes” and the “Pending Restart” column should show “No” for the installed patch.
Running Commands
You will need to connect to Prime Infrastructure server via the command line interface (CLI) to run
commands that:
•
Stop the server
•
Start the server
•
Display the list of running server processes
•
Display the status of High Availability features on the server
Before you begin, make sure you know the:
•
IP address or host name of the Prime Infrastructure server or appliance on which you will run the
commands.
•
User ID and password of an administrative user with CLI access to that server or appliance. Unless
specifically barred from doing so, all administrative users have CLI access.
Step 1
Start up your SSH client, start an SSH session via your local machine’s command line, or connect to the
dedicated console on the Prime Infrastructure physical or virtual appliance.
Step 2
Log in as appropriate:
a.
If you are connecting via a GUI client: Enter the ID of an active Prime Infrastructure administrator
ID with CLI access, and the IP address or host name of the Prime Infrastructure server or appliance.
Then initiate the connection.
Or
b.
If you are using a command-line client or session: Log in with a command like the following:
[localhost]#
ssh -I admin IPHost
Where:
– admin is an active Prime Infrastructure administrator ID with CLI access.
– IPHost is the IP address or host name of the Prime Infrastructure server or appliance.
Or
c.
If you are connecting via the physical or virtual appliance console, a prompt is shown for the
administrator user name. Enter the user name.
Prime Infrastructure will prompt you for the password for the administrator ID you entered.
Cisco Prime Infrastructure 2.1.2 Release Notes
6
Upgrading Prime Infrastructure
Step 3
Enter the administrative ID password.
Prime Infrastructure will present a command prompt like the following: PIServer/admin#.
Step 4
As an administrator, run the following commands from the CLI to start, stop, and check the server and
HA status:
•
Stop the server: PIServer/admin# ncs stop
•
Start the server: PIServer/admin# ncs start
•
Check on the server status: PIServer/admin# ncs status
•
Check on High Availability status: PIServer/admin# ncs ha status
Troubleshooting Patch Installs in HA Implementations
Users who apply this patch in a High Availability (HA) implementation may experience difficulties if
the network links between the two servers offer low bandwidth and high latency. In particular, this kind
of low throughput can cause the post-patch restart and re-registration to take far longer than normal. In
most cases, simply waiting longer will fix the problem with no intervention. In a few cases, continued
or intermittent throughput problems can cause a complete failure. If you believe this has occurred,
contact Cisco TAC.
If you are unable to verify that the patch has been applied to a server, or one or both of the servers fails
to re-start properly after the patch, you may need to re-image the server as explained in Before You Begin
Installing the Patch before continuing.
In all cases, you can use the backup logs command on one or both servers to get information on the
source of the failure.
Upgrading Prime Infrastructure
If you are currently using Prime Infrastructure 2.1 or 2.1.1, you can apply the Prime Infrastructure 2.1.2
UBF patch.
If you are currently using Prime Infrastructure 2.0 you must first upgrade to Prime Infrastructure 2.1
before applying the Prime Infrastructure 2.1.2 UBF patch.
If you are running releases of Prime Infrastructure earlier than 2.0, first upgrade to Prime Infrastructure
2.1 and then apply this patch.
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.
Cisco Prime Infrastructure 2.1.2 Release Notes
7
Submitting Feedback
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.
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, follow these steps:
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.
Cisco Prime Infrastructure 2.1.2 Release Notes
8
Supported Wireless LAN Controller Hardware Models
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 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)
Catalyst 3650 Switch
03.03.00 SE through 03.03.02 SE and 03.06.00E
Catalyst 3850 Switch
03.02.02 SE, 03.02.03 SE, 03.03.00 SE through 03.03.02 SE and
03.06.00E
Catalyst 36xx stack-able Ethernet Switch
03.03.00 SE through 03.03.02 SE and 03.06.00E
Catalyst 38xx stack-able Ethernet Switch
03.03.00 SE through 03.03.02 SE and 0S3.06.00E
Cisco 5700 Series Wireless Controller
03.02.02 SE, 03.02.03 SE, 03.03.00 SE through 03.03.02 SE, and
03.06.00E
Catalyst 57xx stack-able Ethernet Switch
03.03.00 SE through 03.03.02 SE and 03.06.00E
For detailed information on the software compatibility for the Cisco wireless devices, see the following
URL:
http://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html
Cisco Prime Infrastructure 2.1.2 Release Notes
9
Supported Wireless LAN Controller Hardware Models
Table 2 lists the Prime Infrastructure supported devices for switches, wireless LAN controllers, access
point images, Identity Services Engines (ISEs), and mobility services engines (MSEs).
Table 2
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
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],
Cisco NAM 2304
Appliance, Cisco
NAM 2320
Appliance, Cisco IE
2000 Series
Switches.
Cisco Prime Infrastructure 2.1.2 Release Notes
10
Supported
MSE
Devices
Supported Supported
ISE Devices Lightweight APs
Cisco MSE Cisco ISE
1.0
3355
Cisco MSE Cisco ISE
1.1
Virtual
Appliance Cisco ISE
1.2
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
Supported Autonomous
APs
Cisco 1130 AP,
Cisco 1141 AP,
Cisco 1142 AP,
Cisco 1200 AP,
Cisco 1240 AP,
Cisco 1250 AP,
Cisco 1260 AP,
Cisco 1800 AP,
Cisco 800 ISR Series,
Cisco Aironet 1310
and 1410 Bridges,
Cisco 801 AP,
Cisco 1100 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.6
•
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.1.2 using the pre-packaged templates. You can use Prime Infrastructure CLI
templates or Wireless Controller GUI to configure these features.
•
Native IPv6 Infrastructure
•
DHCP relay option 82 sub-options (5, 151)
•
CMX FastLocate
•
Advanced Rogue reporting
•
Client Deauth /Blacklist (Geo Fencing)
•
Adaptive wIPS enhancements
•
EAP-AKA support
•
HTTPS support for webauth
•
PMIPv6 on AP
•
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
•
Support for a new -F domain (Indonesia) on 702I and 3700
•
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)
•
PPPoE on Cisco FlexConnect access points
•
AP700W vlan tagging support
Cisco Prime Infrastructure 2.1.2 Release Notes
11
Non Configurable Features for Wireless LAN Controller Software Releases
Non Configurable Features for Wireless LAN Controller Release 7.6
The following Wireless LAN Controller 7.6 software features are not configurable in Prime
Infrastructure Release 2.1.2 using the pre-packaged templates. You can use Prime Infrastructure CLI
templates or Wireless Controller GUI to configure these features:
•
China -H Domain AP700/1600/2600/3600/3700/1042H/L
•
Indonesia –F Domain (1530 and 1600 ONLY)
•
Universal Small Cell Module 5310 for AP 3600
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.1.2 using the pre-packaged templates. You can use Prime Infrastructure CLI
templates or Wireless Controller GUI to configure these features.
•
Sleeping clients
•
WLC based Policy classification engine
•
DNS lookup for Radius and TACACS server
•
PMIPv6
•
802.11w
•
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
•
Management frame protection. (802.11w)
•
FlexConnect VLAN configuration within FlexConnect Groups
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.1.2 using the pre-packaged templates. You can use Prime Infrastructure CLI
templates or Wireless Controller GUI to configure these features.
•
802.1x AND WebAuth simultaneously enabled
•
LAG on Flex7500 and 8500
•
WIPS containment enhancements
•
Rogue containment enhancements
•
Secure FTP
•
WLC & AP provides AP NAME (MAC), AP Location string (AP Group Name) and VLAN ID for
DHCP option 82 and AAA interim accounting
Cisco Prime Infrastructure 2.1.2 Release Notes
12
New Features and Enhancements
•
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
New Features and Enhancements
This release supports Cisco Aironet 1700 Series Access Points.
For more details on new features and enhancements, refer to Release Notes for Prime Infrastructure
2.1.1.
Important Note
If you are unable to delete all unreachable devices using the Select All option at one time then retry the
delete operation by selecting the unreachable devices.
Open Caveats
Table 3 lists the Open Caveats in Prime Infrastructure Release 2.1.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 3
Open Caveats
Identifier
Description
CSCur17465
The server fails when the repository name is over 100 characters.
CSCuq96218
When installing the Prime Infrastructure 2.1.2 patch, an irrelevant message is displayed while restarting
the server.
CSCur29453
Permission is denied for Admin user in the Wireless LAN - Mobility anchor configuration page.
CSCur26605
The Failover operation is not successful when installing the PI 2.1.2 Patch with High Availability.
CSCur67987
The LWAP template fails to run, even after the application of the Patch 2.1.2.
Note: All of the open caveats for Prime Infrastructure 2.1.1 are applicable to Prime Infrastructure 2.1.2.
For the list of open caveats see the following URL:
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-1-1/release/notes/cpi_rn.html#
pgfId-44304
Cisco Prime Infrastructure 2.1.2 Release Notes
13
Resolved Caveats
Resolved Caveats
Table 4 lists the resolved caveats in Prime Infrastructure Release 2.1.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 resolved caveats using the Bug Search Tool.
Table 4
Resolved Caveats
Identifier
Description
CSCup24652,
CSCuo17280
Unable to apply Prime Infrastructure Collector License, because a minimum of 1200 GB of Pro OVA disk
size is required.
CSCup35411
Idle timeout is not set for editing the Config. Deploy web page.
CSCup35502
The default password used in Local Management User Template should be set as “secret”.
CSCup42599
Prime Infrastructure adds more lines in Command Line Interface, when adding the IP address to the gig0/0
interface.
CSCup58367
Prime Infrastructure reports an error while deploying Embedded Event Manger (EEM) script configuration.
CSCup83318
Prime Infrastructure is not able to push the discovered WLAN template to another device.
CSCuo77266
Deploying clean air parameters from the LWAP template on a 3500 Access point (AP) fails.
CSCup83340
PI returns an error, when details of the Interface template are selected.
CSCuo87161
Client Count and AP Summary reports fail to execute after upgrading PI from 1.3 to 2.1.
CSCup93636
The query for Top N Clients under Interface dashboard, returns random data.
CSCuq00332
Mobility: Audit status for 5760 shows mismatch after performing refresh configuration operation.
CSCup02813
Prime Infrastructure reports incorrect memory stats for Cisco 5760 Wireless LAN Controller.
CSCud05012
Issues with sorting columns in Prime Infrastructure's Health Monitor dashlets.
CSCuq02963
Prime Infrastructure is unable to remove Access Control List of an Interface.
CSCuj12623
Prime Infrastructure reports Java script errors when trying to load a Building view.
CSCuj97351
Radio Resource Management Interval values are not applied to the Next Generation Wireless
Communication controller.
CSCum24621
Building floors are not logically sorted in the map created by using Automatic Hierarchy Creation, if floor
names contain alpha numeric characters.
CSCuq82797
Device/Interface Health Dashlets show only partial data.
CSCur05228
Product evaluation for CVE-2014-6271 and CVE-2014-7169.
CSCuq96208
In Classic view, navigating to the Monitor Controller page loads a blank page.
CSCuo80954
CVE 2014-0114 - Struts 1 vulnerability in Prime Infrastructure.
CSCuo97529
AP groups do not appear in templates after upgrading Prime Infrastructure from 1.x to PI 2.0/2.1.
CSCum25882
Displaying APs that are already placed, when searching for AP on Automatic Hierarchy Creation's web page.
CSCum25922
'Incomplete' filter selection does not persist on the Maps web page.
CSCum26085
An error message is displayed if the floor token in the AP name has numeric value greater than 120 when
creating maps using Automatic Hierarchy Creation.
CSCum26128
Automatic Hierarchy Creation: Inconsistent behavior in grouping of AP with same AP name and different
RegEx.
Cisco Prime Infrastructure 2.1.2 Release Notes
14
Resolved Caveats
Table 4
Resolved Caveats (continued)
Identifier
Description
CSCum44755
Rails are created without providing 3 coordinate points.
CSCum44768
Messages are repeated in step 4 of the Import Maps process.
CSCum67196
Unable to uncheck the option Show Rogue AP Zone of Impact.
CSCum67451
Imported maps have the same unit as that of exported, even if the unit is changed.
CSCum96811
AP Audit status shows mismatch after synchronizing with Network Control System.
CSCun45380
IP address column in the DHCP Stats table is showing a wrong IP for Wireless LAN Controller.
CSCun57532
Unable to create two Wireless LANs with the same Service Set Identifier (SSID) and Security, when WLAN
ID id is greater than 17.
CSCuq98089
Breadcrumbs related to Life Cycle view is seen on some templates in Classic View.
CSCun95989
Planned AP X, Y co-ordinates override the coordinates set in production mode, after a map export/import.
CSCuo13158
Security Index dashlet does not give any indication that it has been disabled.
CSCuo30489
Displays IP of the Device instead of Device Name when running Client Count Report by Device’s Host name.
CSCuo52179
The switches added as “SPT-only” alone get their Configuration backup done.
CSCuo69975
Primary Infrastructure reflecting wrong Interface/IP when using Allow Authentication, Authorization, and
Accounting (AAA) override.
CSCuo75881
Switch port details are not available in the Unique Clients report.
CSCuo79852
In Primary Infrastructure the Interface Group radio button is not preselected.
CSCuo88767
Incorrect User Interface layout for 5500 ports.
CSCuo92717
An Expired “Scheduled Guest User” is not deleted from Prime Infrastructure and Wireless LAN Controller.
CSCup06192
Interface Tx and Rx Utilization dashlet shows incorrect time stamp.
CSCup12538
Templates are not listed when there are more than 1000 Wireless LAN and AP groups.
CSCup59809
In Device Work Center, Prime Infrastructure is unable to show Device Detail for the 3850switch.
CSCup60428
Dashboard shows incorrect number of reachable APs.
CSCup60584
Mandatory fields are not marked with “*” for exporter and monitor templates.
CSCup62304
Fast-Service Set Identifier (SSID)-switch toggle does not work in General-System Template.
CSCup67006
Unable to configure Link Aggregation (LAG) mode on Cisco 7500 Wireless LAN Controller.
CSCup70665
Wireless LAN Configuration: Profile Name and Service Set Identifier (SSID) fields are not marked with “*”.
CSCup72896
Information about flex connect is displayed for the devices that do not support flex connect while saving AP
Group template.
CSCup80963
Existing AP are offset from their position when positioning or adding APs.
CSCup37696
Prime Infrastructure sends manual containment request to all controllers managed by it.
CSCup42427
Adding the Integrated Services Router Generation 3 (ISRG3) device to Prime Infrastructures’ Inventory
affects the Virtual Domain page.
CSCup85080
The Cisco 3650 device does not appear in device list of Wireless Guided Work Flow.
CSCup85796
Network Device Summary dashlet does not count Reachable APs accurately.
CSCup35498
Local Management User template does not clearly indicate the selection of “password” or “secret”.
Cisco Prime Infrastructure 2.1.2 Release Notes
15
Resolved Caveats
Table 4
Resolved Caveats (continued)
Identifier
Description
CSCup56187
Unable to apply Wireless LAN with multicast Virtual LAN. An error message “Multicast Listener Discovery
snooping is disabled” is displayed.
CSCuq02963
Prime Infrastructure is unable to remove Access Control List under an Interface.
CSCuq15123
“Injector Switch MAC Address” field is made mandatory in the Lightweight Access point protocol (LWAP)
template.
CSCuq73364
The Current Associated Wired Clients section does not display any content.
CSCup29419
The Interface Tx, Rx utilization graph shows incorrect X-axis index.
CSCui37535
The unassigned Site option under the Maps menu shows Application Visibility and Control (AVC) Specific
Tooltip.
CSCun77955
The error message does not indicate a maximum character limit for AP Group Template's name.
CSCup69768
“Client Count” Report displays only hourly data.
CSCuq98099
The LWAP Template's title is missing in Classic View.
CSCun42435
Northbound Interface (NBI) Credential role should be disabled for the root user, by default.
CSCun93216
Prime Infrastructure needs to shorten the long lines in the Alarm details page.
CSCur27210
Prime Infrastructure does not show Heatmaps related to 1702 AP.
CSCuq97982
Prime Infrastructure does not show the image of 1702I AP’s antenna.
CSCur15059
Version mismatch issue in UBF patch installation.
CSCup66408
Prime Infrastructure takes more than 5 minutes to export 500 devices.
CSCul10656
Prime Infrastructure performs unnecessary “config t” access, while collecting Switch Inventory.
CSCuo06509
Prime Infrastructure displays an error when editing Wireless LAN template with Layer3 security in Wireless
LAN Controller 7.3.
CSCup50236
The option to sort the column “Association Time” in Associated Wired Clients is disabled.
CSCup82935
The server does not recognize ERSPAN NAM data-source.
CSCui17662
The location information of the wireless Intrusion Prevention System (wIPS) is missing.
CSCuo28090
Unable to start wIPS/Context Aware Service (CAS) once Connected Mobile Experience (CMX) analytics
evaluation license has expired.
CSCuo28729
The Acknowledge Failure count is abnormally high for an AP.
CSCuo61191
The number of SSIDs is not counted exactly during validation of the SSID group list.
CSCup93101
The Mobility Service Engine does not synchronize with WLC when it is added with the patch.
CSCup96982
The Autonomous AP inventory background task is not running in the M21 build server.
CSCuq02958
An irrelevant message regarding WLAN is displayed while configuring an interface.
CSCuq69887
It takes more then thirty minutes to start the server and Oracle errors are displayed while restarting.
CSCuq73360
Some additional messages are displayed when restarting the PI after the patch installation.
CSCuq78004
The published date of the UBF patch is incorrectly displayed after the completion of the patch installation.
CSCuq87355
Unable to see the maps and devices on the Root and Sub domains.
CSCuq97716
When navigating to Configure Controller page in Classic view the Device Work Center page is loaded.
CSCuq97812
When navigating to Template launchpad in Classic view the accordion menu is not displayed.
Cisco Prime Infrastructure 2.1.2 Release Notes
16
Related Documentation
Table 4
Resolved Caveats (continued)
Identifier
Description
CSCuq98066
An error message is displayed during NCS start after successful completion of the installation.
CSCur13916
LWAP template title is missing in Lifecycle view.
CSCur19067
Unable to edit the WLAN in the controller configuration page.
CSCur43156
Memory Utilization chart does not display data for Next Generation Wiring Closet devices.
CSCup63980
Support for CleanAir on AP 802.
CSCuq01678
The Abort Deployment operation is not successful for the Lightweight AP (LWAP) template.
CSCuq98066
Prime Infrastructure reports error while starting up.
Related Documentation
You can access additional 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.2 Release Notes
17