Guest

Cisco Prime Infrastructure

Cisco Prime Infrastructure 2.1.1 Release Notes

  • Viewing Options

  • PDF (298.1 KB)
  • Feedback

Table of Contents

Cisco Prime Infrastructure 2.1.1 Release Notes

Introduction

System Requirements

Installation Guidelines

Before You Begin Installing the Patch

Installing the Patch

Installing the Patch With High Availability

Running Commands

Troubleshooting Patch Installs in HA Implementations

Upgrading Prime Infrastructure

Submitting Feedback

Prime Infrastructure Licenses

Supported Devices

Supported Wireless LAN Controller Hardware Models

Non Configurable Features for Wireless LAN Controller Software Releases

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

New Features and Enhancements

Changes to the Lightweight AP Configuration Templates Page

Selecting Access Points for Template Deployment

Scheduling Template Deployment

Viewing the Status of the Template Deployment

AP Utilization Report

Changes to the Jobs Dashboard Page

Important Notes

Open Caveats

Resolved Caveats

Related Documentation

Obtaining Documentation and Submitting a Service Request

Introduction

This is a patch release for Cisco Prime Infrastructure 2.1. This release delivers a number of bug fixes. There are no new features added in this release. However, this release provides a few important enhancements to the existing features. For details, see the “New Features and Enhancements” section.

This patch release must be installed on top of your existing Prime Infrastructure 2.1 installation.

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.

Installing the Patch

Make sure you have completed the recommended preparation steps given in Before You Begin Installing the Patch.

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.1 patch file (pi211_20140630_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 when the installation is complete. You should also see a listing for the patch in the “Updates” table, with a “Yes” opposite the patch under the “Installed” column, and a “Yes” under 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” opposite the patch under the “Installed” column, and a “No” under the “Pending Restart” column.


 

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 install with the primary server in “Primary Active” state and the secondary server in “Secondary Syncing” state.

Patching of the primary and secondary server 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.

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”.

Step 2 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.1 patch file (pi211_20140630_01.ubf), and save the file locally.

Step 3 Install the patch on the secondary server:

a. Access the secondary server’s HMweb 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.

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 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.

Step 6 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 secondary’s processes 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.

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.

Step 3 Enter the administrative ID password.

Prime Infrastructure will present a command prompt like the following: PIServer/admin#.

Step 4 Run the appropriate commands as needed, using the examples below:

  • Stop the server: PIServer/admin# ncs stop
  • Start the server: PIServer/admin# ncs stop
  • 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, you can apply the Prime Infrastructure 2.1.1 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.1 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 .

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 .


 

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 (WLCM2 on SRE)

7.2.110.0

Catalyst 3650 Switch

03.03.00 SE / 03.03.01 SE / 03.03.02 SE

Catalyst 3850 Switch

03.02.02 SE / 03.02.03 SE / 03.03.00 SE / 03.03.01 SE / 03.03.02 SE

Catalyst 36xx stack-able Ethernet Switch

03.03.00 SE / 03.03.01 SE / 03.03.02 SE

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

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/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html

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
Supported MSE Devices
Supported ISE Devices
Supported Lightweight APs
Supported Autonomous APs

2960, 2975 Switches [Cisco IOS Release 12.2(50)SE],

Catalyst 3560 Switches [Cisco IOS Release 12.2(50)SE],

Catalyst 3750 Switches [Cisco IOS Release 12.2(50)SE],

Catalyst 3850 Series Ethernet Stackable Switch

Catalyst 3550 Series Ethernet Stackable Switch

Catalyst 4500 Switches [Cisco IOS Release 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 2100 Series

Cisco 2500 Series

Cisco 4400 Series

Cisco 5500 Series

Cisco Flex 7500 Series

Cisco 8500 Series

Cisco Virtual Controller

Cisco WiSM

Cisco WiSM2

Cisco Wireless Controller on Service Ready Engine (WLCM2 on SRE)

Catalyst 3750G Series Integrated Wireless LAN Controllers

Cisco 5700 Series Wireless Controller

Cisco 5700 Series Wireless Controller (STACK)

Cisco MSE 3355

Cisco MSE Virtual Appliance

Cisco ISE 1.0

Cisco ISE 1.1

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 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

The following sections describe the Wireless LAN Controller software features that are not configurable in Prime Infrastructure Release 2.1.1 using the pre-packaged templates:

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.1 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
  • VideoStream 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

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.1 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.1 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.1 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
  • 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

There are no new features in this release.

For more information about Prime Infrastructure features and benefits, as well as hardware and software specifications, see the Cisco Prime Infrastructure 2.1 Data Sheet .

The following enhancements have been made in this release:

Changes to the Lightweight AP Configuration Templates Page

Prime Infrastructure 2.1.1 provides a new user interface to configure and deploy the lightweight access point templates. To configure a new Lightweight Access Point template, follow these steps:


Step 1 In the Classic view, choose Configure > Lightweight AP Configuration Templates .

Step 2 From the Select a command drop-down list, choose Add Template .

Step 3 Click Go .

Step 4 Enter a template name in the text box.

Step 5 Enter a template description in the text box.

Step 6 Click Save as New Template . The Lightweight AP Template Detail page contains the following tabs:


 

AP Parameters Tab

General

  • Location—Enter the location in the Location text box.
  • Admin Status—Select the Admin and Enabled check box to enable administrative status.

Note To conserve energy, access points can be turned off at specified times during non-working hours. Select the Enabled check box to allow access points to be turned on or off.


  • AP Mode—From the drop-down list, choose one of the following:

Local —Default

Monitor —Monitor mode only.


Note Choose Monitor to enable this access point template for Cisco Adaptive wIPS. Once Monitor is selected, select the Enhanced WIPS Engine check box and the Enabled check box.


FlexConnect—Cisco 1030 remote edge lightweight access point (REAP) used for Cisco 1030 IEEE 802.11a/b/g/n remote edge lightweight access points.

Rogue Detector—Monitors the rogue access points but does not transmit or contain rogue access points.

Bridge

Sniffer—The access point “sniffs” the air on a given channel. It captures and forwards all the packets from the client on that channel to a remote machine that runs AiroPeek (a packet analyzer for IEEE 802.11 wireless LANs). It includes information on timestamp, signal strength, packet size, and so on. If you choose Sniffer as an operation mode, you are required to enter a channel and server IP address on the AP/Radio Templates 802.11b/g/n or 802.11a/n parameters tab.

SE-Connect—This mode allows a CleanAir-enabled access point to be used extensively for interference detection on all monitored channels. All other functions such as IDS scanning and Wi-Fi are suspended.

  • AP Sub Mode—Choose an option from the drop-down list.
  • Enhanced wIPS Engine—Select the Enhanced wIPS engine and the Enabled check box to enable.
  • AP Height (feet)—Enter the height of the access point (in feet) in the text box.
  • Mirror Mode—Select the Enabled check box to enable mirror mode.
  • Country Code—Choose the appropriate country code from the drop-down list.
  • Stats Collection Interval—Enter the stats collection interval in the text box.
  • Cisco Discovery Protocol—Select the Enabled check box to enable Cisco Discovery Protocol.
  • AP Failover Priority—Choose Low , Medium , High , or Critical from the drop-down list to indicate the access point failover priority. The default priority is low.
  • Pre-Standard 802.3af switches.
  • Antenna Band Mode.
  • Domain Name—Domain Name can be configured only on APs which have static IP.
  • Server IP Address—Domain Name Server IP can be configured only on APs which have static IP.
  • Encryption—Select the Encryption check box to enable encryption.
  • Rogue Detection—Select the check box to enable rogue detection.
  • SSH Access—Select the SSH Access check box to enable SSH access.
  • Telnet Access—Select the Telnet Access check box to enable Telnet access.
  • Link Latency—You can configure link latency on the controller to measure the link between an access point and the controller.

Note Link latency is supported for use only with FlexConnect access points in connected mode. FlexConnect access points in standalone mode are not supported.


  • TCP Adjust MSS—Select the TCP Adjust MSS check box to enable TCP to adjust MSS.
  • VLAN Tagging—VLAN Tagging is supported only from controller version 7.3.1.26. If you change the mode or value of VLAN tagging, the access point will be rebooted. VLAN tagging cannot be enabled when the AP is in Bridge mode. Enabling VLAN tagging will ignore the value of Native VLAN ID.
  • AP Group Name.
  • Reboot AP—Select the check box to enable a reboot of the access point after making any other updates.

Power Injector Configuration

  • Power Injector State—When enabled, this allows you to manipulate power injector settings through Prime Infrastructure without having to go directly to the controllers. If the Enable Power Injector State is selected, power injector options appear.
  • Power Injector Selection—Choose installed or override from the drop-down list.
  • Injector Switch MAC Address—Enter the MAC address of the injector switch.

Global Username Password Configuration

  • Override Global Username Password—Select the check box to enable an override for the global username/password. Enter and confirm the new access point username and password in the appropriate text boxes.

Supplicant Credentials Configuration

  • Override Supplicant Credentials—Select the Override Supplicant Credentials check box to prevent this access point from inheriting the authentication username and password from the controller. The default value is unselected. The Override Supplicant Credentials option is supported in controller Release 6.0 and later.

In the Username, Password, and Confirm Password text boxes, enter the unique username and password that you want to assign to this access point.

AP Retransmit Configuration

  • AP Retransmit Count—Enter the AP Retransmit Count. The AP Retransmit Count default value is 5 and the range is from 3 to 8.
  • AP Retransmit Interval (secs)—Enter the AP Retransmit Intervals. The AP Retransmit Interval default value is 3. The range is 2 to 5.

Controller Configuration

Select the Controllers Configuration check box to enable the drop-down lists for the primary, secondary, and tertiary controller names.

  • Primary, Secondary, and Tertiary Controller Name—The Primary/Secondary/Tertiary Controller names.
  • Primary, Secondary, and Tertiary Controller IP—The Primary/Secondary/Tertiary Controller IP is the Management IP of the controller.

Venue Configuration

  • Venue Group
  • Venue Type
  • Secondary Venue Name
  • Language

Mesh Tab

Use the Mesh tab to set the following parameters for mesh access points:

  • Bridge Group Name—Enter a bridge group name (up to 10 characters) in the text box.

Note Bridge groups are used to logically group the mesh access points to avoid two networks on the same channel from communicating with each other. For mesh access points to communicate, they must have the same bridge group name. For configurations with multiple RAPs, make sure that all RAPs have the same bridge group name to allow failover from one RAP to another.


  • Data Rate (Mbps)—Choose the data rate for the backhaul interface from the drop-down list. Data rates available are dictated by the backhaul interface. The default rate is 18 Mbps.

Note This data rate is shared between the mesh access points and is fixed for the whole mesh network. Do not change the data rate for a deployed mesh networking solution.


  • Ethernet Bridge—From the Ethernet Bridging drop-down list, enable Ethernet bridging for the mesh access point.
  • Role—Choose the role of the mesh access point from the drop-down list ( MAP or RAP ). The default setting is MAP.

Note An access point in a mesh network functions as either a root access point (RAP) or mesh access point (MAP).


  • The Ethernet Interfaces area group box provides information such as interface name, mode, VLAN ID, and Trunk ID. Select the appropriate interface and specify its mode.

802.11a/n/ac Tab

  • Select the check boxes of the 802.11a parameters that must be applied:

Channel Assignment

Channel Width

Admin Status

Antenna Mode

Antenna Diversity

Antenna Type and Antenna Name

Antenna Name

  • Select the check boxes of the 802.11ac parameters that must be applied. 802.11ac parameters are only applicable for 11ac modules.

Channel Width

Admin Status

  • Select the Power Assignment check box to choose the appropriate power level.
  • Select the Antenna Selection check box to select any of the 11n Antenna Selection parameters.
  • Select the CleanAir check box to enable CleanAir functionality. CleanAir is supported from the WLC Release 7.0 for CleanAir-supported APs.

802.11a SubBand Tab

In the 802.11a SubBand tab, select the 802.11a Sub Band options (for either 4.9 or 5.8 parameters) that must be applied:


Note The SubBand options are disabled unless the check box to the left of the field is selected.


  • Admin Status
  • Channel Assignment—Select the check box and then choose the appropriate channel from the drop-down list.

Note The channel number is validated against the radio list of supported channels.


  • Power Assignment—Select the check box and then choose the appropriate power level from the drop-down list.

Note The power level is validated against the radio list of supported power levels.


  • Antenna Type—Select the check box and then choose the antenna type from the drop-down list.
  • Antenna Name—Select the Antenna Type check box and then choose the applicable antenna name from the drop-down list.

Note Not all antenna models are supported by radios of different access point types.


802.11b/g/n Tab

Select the check box of the 802.11b/g/n parameters that must be applied:

  • Channel Assignment
  • Admin Status
  • Antenna Mode
  • Antenna Diversity
  • Antenna Name
  • Power Assignment
  • Tracking Optimized Monitor Mode
  • 11n Antenna Selection
  • CleanAir

CDP Tab

  • In the Cisco Discovery Protocol on Ethernet Interfaces group box, select the check boxes for the slots of Ethernet interfaces for which you want to enable CDP.
  • In the Cisco Discovery Protocol on Radio Interfaces group box, select the slots of Radio interfaces for which you want to enable CDP.

FlexConnect Tab

  • Select the FlexConnect Configuration check box to enable FlexConnect configuration (including VLAN support, native VLAN ID, and profile name VLAN mappings).

Note These options are only available for access points in FlexConnect mode.


OfficeExtend—The default is Enabled.


Note When you select Enable for the OfficeExtend AP, several configuration changes automatically occur including: encryption and link latency are enabled; rogue detection, SSH access, and Telnet access are disabled.



Note When you enable the OfficeExtend access point, you must configure at least one primary, secondary, and tertiary controller (including name and IP address).


Least Latency Controller Join—When enabled, the access point switches from a priority order search (primary, secondary, and then tertiary controller) to a search for the controller with the best latency measurement (least latency). The controller with the least latency provides the best performance.


Note The access point only performs this search once when it initially joins the controller. It does not recalculate the latency measurements of primary, secondary, and tertiary controllers once joined to see if the measurements have changed.


VLAN Support

Native VLAN ID


Note The valid native VLAN ID range is 1—4094. If you are changing the mode to REAP and if the access point is not already in REAP mode, then all other REAP parameters are not applied on the access point.


  • Select the WLAN VLAN Mapping check box to enable WLAN VLAN mapping (including WLAN profile name and VLAN ID mappings).
  • Select the VLAN ID ACL Mapping check box to enable VLAN ID ACL Mappings. Enter a VLAN ID and choose the Ingress and Egress ACLs from the drop-down list boxes to map to the VLAN ID specified.
  • Select the Web Auth ACL Mapping check box to enable Web Auth ACL mapping.
  • Select the Policy ACL Mapping check box to enable policy ACL mapping.
  • Select the Local Split ACL Mapping check box to enable Local Split ACL mapping.

Selecting Access Points for Template Deployment

  • Choose Configure > Lightweight AP Configuration Templates .
  • Click the applicable template in the Template Name column.
  • Select one or more access points by selecting their respective check boxes.

Note You can use the Filter feature to search for specific access points. For details see the Filters section of the Cisco Prime Infrastructure User Guide.


  • Click Deploy to save and deploy the template to the relevant access points.
  • Click Apply to save and apply the AP/Radio parameters to the selected access points from the search.

Note You can deploy the template using the AP Selection or Schedule tabs.


Scheduling Template Deployment

Allows you to save the current template, apply the current template immediately, or schedule the current template to start the provisioning at the applicable time.

  • Start Time—Allows you to configure and start the template deployment at a scheduled time.

Now—Deploys the template right away.

Date—Enter a date in the text box or use the calendar icon to select a start date.

  • Recurrence—Select from none, hourly, daily, or weekly to determine how often this scheduling occurs.

Note You can deploy the template using the AP Selection or Schedule tabs.


Viewing the Status of the Template Deployment

Displays all recently applied reports including the apply status and the date and time the apply was initiated. Click the link that is available on the number of access points (next to the Template Deployed to APs field) to view the deployment status information.

  • Graph shows the Success or Partial Success status. Click the graph to view status information.
  • The Deploy Status section shows the following information:

AP Name

Status—Indicates success, partial failure, failure, or not initiated. For failed or partially failed provisioning, click Details to view the failure details (including what failed and why it failed).

Ethernet MAC—Indicates the Ethernet MAC address for the applicable access point.

Controller IP—Indicates the controller IP address for the applicable access point.

AP IP

Controller Name

AP Model

Campus

Building

Floor

Outdoor Area

FlexConnect Group


 

AP Utilization Report

This is a new report in Prime Infrastructure 2.1.1, which displays the total utilization trend of access points with the channel and client statistics information on the wireless network. To access this report, choose Report > Report Launch Pad > Device >AP Utilization . This report contains three sub-reports—AP Client Statistics Summary, AP Client Count Summary, and AP Statistics Summary. For information, see the Managing Reports section of the Cisco Prime Infrastructure User Guide .

AP Client Statistics Summary

  • AP Name—Name of the access point.
  • Base Radio MAC—Base Radio MAC of the AP.
  • Slot—Radio Type of the AP.
  • Peak Throughput (Mbps)—Maximum Throughput seen on sum of traffic generated by all clients connected to the AP.
  • Average Throughput (Mbps)—Average Throughput seen on sum of traffic generated by all clients connected to AP.
  • Peak RSSI (dBm)—Maximum RSSI measured at the AP across all the clients connected to the AP over the reporting period.
  • Average RSSI (dBm)—Average RSSI measured at the AP across all the clients connected to the AP over the reporting period.
  • Peak SNR (dB)—Maximum SNR measured at the AP across all the clients connected to the AP over the reporting period.
  • Average SNR (dB)—Average SNR measured at the AP across all the clients connected to the AP over the reporting period.

AP Client Count Summary

  • AP Name—Name of the access point.
  • Base Radio MAC—Base Radio MAC of the AP.
  • Slot—Radio Type of the AP.
  • Peak Number of Users—Maximum Number of Clients connected to the radio over the reporting period as reported by WLC.
  • Average Number of Users—Average Number of Clients connected to the radio over the reporting period as reported by WLC.

AP Statistics Summary

  • AP Name—Name of the access point.
  • Base Radio MAC—Base Radio MAC of the AP.
  • Slot—Radio Type of the AP.
  • Peak Channel Utilization (Percentage)—Maximum Channel utilization in percentage per radio.Channel utilization is a metric that includes Tx utilization, Rx utilization, Interference from other 802.11 radios and noise from non-802.11 sources.
  • Average Channel Utilization (Percentage)—Average Channel utilization in percentage per radio.Channel utilization is a metric that includes Tx utilization, Rx utilization, Interference from other 802.11 radios and noise from non-802.11 sources.
  • Peak Packets Retransmission—Peak Number of packets transmitted after retries on each radio over the reporting period.
  • Average Packets Retransmission—Average Number of packets transmitted after retries on each radio over the reporting period.
  • Channels in Use—Unique Channel list seen on each Radio over the reporting period. The value in the Channels in Use field will be available only for the last 31 days.

Changes to the Jobs Dashboard Page

In earlier releases of Prime Infrastructure, when you delete a controller, the associated APs are not deleted and remain in the “unassociated” state. When you delete a controller in Prime Infrastructure 2.1.1, you get a message so that you can delete the associated APs. To view the details of the deleted APs which were associated to a controller, choose Administration > Jobs Dashboard (in the Lifecycle view).

When you delete a controller using the Classic view, the following message appears:

Do you want to delete APs Associated to the selected Devices. To check AP delete status please go to Configure > AccessPoints > View Delete AP Job(s).
 

To view the details of the deleted APs (which were associated with a controller), choose Configure > Access Points , choose View Delete AP Job(s) from the Select a command drop-down list, and then click Go .

When you delete a controller using the Lifecycle view, the following message appears:

Do you want to delete APs Associated to the selected Devices.

 

To view the details of the deleted APs which were associated with a controller), choose Administration > Jobs Dashboard .

Important Notes

This section contains important notes about this release of Prime Infrastructure 2.1.1.

  • After upgrading to Prime Infrastructure 2.1, if you click the Client Details link in the Monitor > Client and Users page, you may encounter an error: “There was an error while parsing and rendering the content”. If you encounter this error, clear the browser cache and retry accessing the Client Details page.
  • If you are unable to swap the primary/secondary/tertiary controller server IP address and name using template and configuration pages, clear all three primary/secondary/tertiary controller server IP addresses and name, and then save the configuration to the controller. Once the null values are successfully saved to the controller, you can assign new primary/secondary/tertiary server IP address and name.
  • The Client Throughput and Client Traffic reports show same data when the Report By criteria is set to All Wired or All Wireless where Cisco 3850 or Cisco 3650 devices are available (these devices can be wired and wireless).

Open Caveats

Table 3 lists the Open Caveats in Prime Infrastructure Release 2.1.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 3 Open Caveats

Identifier
Description

CSCue78806

After importing the 802.11a or 802.11b templates, the template details (in the following pages) do not show up correctly.
Design > Configuration > Features Design > Controller > 802.11a or n or ac > dot11a-RRM
Design > Configuration > Features Design > Controller > 802.11b or g or n > dot11b-RRM

CSCuo92152

The Online Help shows old details for the Lightweight AP Configuration Templates (in the Classic View).

The revised content is available in the New Features and Enhancements section of the Release Notes for Prime Infrastructure 2.1.1.

CSCuo99356

An error occurs while performing the primary/secondary/tertiary controller configuration in the AP Configuration and LWAP templates with WLC 8.0.

CSCup03919

The Network Device Summary dashlet should show total AP count based on the AP operational status.

CSCup10627

The About Cisco Prime Infrastructure page, the login page and the /opt/CSCOlumos/SVN_INFO_FORABOUT.TXT file do not show the Prime Infrastructure version as 2.1.1 after installing the patch.

CSCup32040

A few combinations in the Advanced filter of LWAP Template > AP Selection page are not working.

CSCup18102

Prime Infrastructure identifies Rogue AP by Manual SPT/Auto SPT, but when a user tries to run rogue AP report, Prime Infrastructure fails to show port number of the traced rogue. Prime Infrastructure “Not available or Rogue AP found on wire in switch port trace summary.

CSCup41681

The AP Utilization report shows wrong slot information for 11ac AP.

CSCup41693

The AP Utilization report shows wrong slot information for WSSI module.

CSCup18138

The AP Utilization report shows peak RSSI/SNR values based on AP instead of radio.

CSCup42427

When an ISR G3 device is installed and activated with service container application via Prime Infrastructure, the virtual domain is impacted.

CSCup56748

The WLAN-VLAN Mapping section in FlexConnect tab unselected even though mappings are present after applying the Prime Infrastructure 2.1.1 patch.

CSCup44041

The Deploy Status of the LWAP template does not refresh when already navigated to Deploy status page after template deployment.

CSCun64379

Sometimes when you create a new LWAP template or even revisiting the already created LWAP template, the user interface of the template appears incorrectly.

CSCup57279

The footnotes in the LWAP template missing.

With the exception of CSCun19363, CSCun28657, and CSCun82620, all of the open caveats of Prime Infrastructure 2.1 are also applicable for Prime Infrastructure 2.1.1. 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/release/notes/cpi_rn.html#pgfId-44304

Resolved Caveats

Table 4 lists the resolved caveats in Prime Infrastructure Release 2.1.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 resolved caveats using the Bug Search Tool .

Table 4 Resolved Caveats

Identifier
Description

CSCub57283

Deployment of configuration templates fail when the device name is long.

CSCuc34416

Prime Infrastructure sending informational events with no way to prune them.

CSCug48498

Duplicate and Save as New Template options are unavailable.

CSCui31359

Prime Infrastructure 1.3 to 2.0: LCV shows Cisco 5760 and 3850 WLC device supports AVC feature after upgrade.

CSCui57873

‘NCS’ in collection status (upgraded system), which should show Prime Infrastructure.

CSCui75480

Removing controller should trigger prompt to remove APs

CSCui75533

Need to remove limit on template application

CSCuj50966

A link down alarm is seen in Prime Infrastructure for some switches when an access port moves to an administratively up and operationally down state.

CSCuj60073

Bug in the code XmpDmmRbacUserDetailsManager.java

CSCul03318

Flow count for Data Source does not match last 5 minutes flow record rate

CSCul08540

Map response slow with multiple admins

CSCul25393

Need capability to Rollout AP templates by FlexGroup

CSCul25401

AP templates should allow multi floor/flex group selection

CSCul55011

The AP Radio Downtime Summary report information is unreadable.

CSCul80665

Deleting a client from the Disabled Clients list shows an error on Cisco 5760 and 3850 WLC.

CSCul86625

ZBFW Template: Prime Infrastructure sends ‘ip any any’ for any app other then tcp/udp/icmp

CSCum08217

Planning Mode: No indicator shown for APs being added on the floor

CSCum15764

Classic View’s Scheduled Download tasks should timeout to usable state.

CSCum38306

Prime Infrastructure persists wcspreference defaultPartition key related to ROOT-DOMAIN

CSCum54645

The Client Session report shows NULL IP address.

CSCum58444

Unable to delete/save map on Prime Infrastructure and getting ‘Unexpected Token’ error”.

CSCum66983

Prime Infrastructure shows Audit Mismatch after Refresh Config from Controller.

CSCum86955

Permission denied error upon clicking the Automatic Hierarchy Creation page.

CSCum96614

System >WLANs > Mobility Anchor > Controller redirects to an empty page

CSCum98734

SNMP/Telnet Timeout value mismatch: add Device/Properties > Settings

CSCun01654

AP by O/D Area on Busiest AP report does not show data in Virtual Domains

CSCun02145

9M Stack:360 View - WLAN tab shows nothing

CSCun02305

Sequential creation of Wireless Templates from Lifecycle View gets stuck

CSCun02695

Prime Infrastructure reports an error when changing the Config related to an AP

CSCun05482

Templates with managed variables fail on 2950G with long hostname

CSCun10290

Clients with 802.3 (guest) protocol not listed in client count report

CSCun12679

Prime Infrastructure only shows 5550 controller while deploying Local Net user template

CSCun13027

Error in ‘Network Users Priority’ template while restoring Prime Infrastructure value.

CSCun14718

Need to remove the drop down in ngwc-mdns-show all templates page

CSCun17035

Devices are not displaying during deployment of Web Auth template

CSCun19363

Link test on associated client fails.

CSCun20136

Plug and Play does not work with Cisco 2960X switches

CSCun20493

Discovery does not handle UnexpectedRollbackException in the adapter

CSCun21588

The Radio Down Time report shows illegible down time.

CSCun22642

Prime Infrastructure reports Inventory Collection failure because of static routes

CSCun25045

Unable to set the ‘AP Primed Join Timeout’ value through Prime Infrastructure.

CSCun25067

The cancel button on the LCV AP Configuration page redirects to CV AP config page.

CSCun27199

UDG with multiple rules disappear when the first rule contains ‘_’.

CSCun28132

Prime Infrastructure pops up an error message about heatmaps for both the 802.11a/n and 802.11b/g/n networks not being able to show at the same time.

CSCun28657

Disabling or Enabling an AP under Configure > AP throws an SNMP error.

CSCun32617

Cisco Wireless LAN Controller (WLC) could not be removed from

CSCun35306

WLC Client Details link broken when accessed through Site Map.

CSCun41123

ACL Templates failing after upgrading Prime Infrastructure from 1.3 to 2.0

CSCun43443

Auto-SPT incorrectly detects wireless rogue AP as found on wire

CSCun44340

AP managed by Prime Infrastructure looses b/g/n interface but it returns after a reboot”

CSCun45904

Correct ‘Security Index’ dashlet’s reference to Configuration Sync.

CSCun48391

NBI log appender is set to null file.

CSCun49713

The Client with Open Auth incorrectly show up as EAP client

CSCun55232

A footnote is required under sub band dot11 cdp Tabs.

CSCun56637

Breadcrumb for ‘FlexConnect ACL’ shows path to Classic View’s page.

CSCun56760

TFTP ‘upload of config’ for 8.0 and 7.4 MR2 WLC throws an error

CSCun58525

Browser hangs when one accesses template deployment page

CSCun64684

LWAP Template: Flex sections do not expand on check box selection

CSCun70957

Editing any Radio on Cisco 1532I shows “SNMP operation to Device failed” error.

CSCun72657

Client Troubleshooting throws Error while retrieving data from Prime Infrastructure Server.

CSCun78879

Some Links on Client list page redirect to CV Monitor page

CSCun82296

Communication between MSE and Cisco 5760/3850 WLC / Cisco WLC is in the Inactive state.

CSCun82620

Sometimes, CPU spikes to 100% during Inventory Collection.

CSCun85784

‘AP Primed Timeout’ changes in Prime Infrastructure due to OID change in 8.0 WLC.

CSCun87821

Combined UE to AP throughput Peak and average

CSCun87828

Prime Infrastructure should report on peak and average for Clients connected to a Radio

CSCun87831

Prime Infrastructure should report on peak and average for RSSI per Radio

CSCun87835

Prime Infrastructure should report on peak and average for Channel Utilization

CSCun87839

Prime Infrastructure should report on peak and average for Packet Retransmission

CSCun91017

The Busiest Clients report does not display any information with clients connected.

CSCun92196

The NMS Server stops working because of an ‘Out of Memory’ error.

CSCun93184

Need Copy/Paste functionality on the text within alarm details

CSCun93195

Failsafe Timeout error when pushing Redundancy Force Switchover template

CSCun93216

Prime Infrastructure should wrap around long lines in the Alarm details page

CSCun93254

Exception thrown while deploying http-https template config from Prime Infrastructure

CSCun93566

Prime Infrastructure adds ‘ip dhcp opt82’ on new WLAN even though DHCP is disabled”

CSCuo05012

SAM job in Prime Infrastructure disabled to avoid negative impact on CDP processing

CSCuo06036

Interface Health poll stops when thresholded on sub-set of interfaces

CSCuo21742

Delete controller with APs need message informing about the jobs’ status

CSCuo34598

Unable to access Prime Infrastructure from the browser, NMS Server is stopped.

CSCuo35187

AutoSPT thread stuck in timed wait state when no switches were added

CSCuo42366

CDB records can be lost when file wraps around

CSCuo60411

Prime UI is not loading. It stays in the loading state for hours

CSCuo74523

New LWAP Template: VLAN-ACL mapping cannot be edited in flex tab

CSCuo77880

Redundancy Forced Switchover Template has multi-device selection

CSCuo88702

Application classification rules corrupted

CSCuo90205

LCV: Cannot save any template after creating a WLAN Template

CSCuo96695

Breadcrumbs for LWAP Template in LCV shows CV Breadcrumbs

CSCuo96728

“Select All’ on AP selection page does not deploy template to all APs”

CSCuo97551

Deploy Status shows ‘Apply in Progress’ after successful deployment

CSCuo98008

Number of entries in deploy status table and total field do not match

CSCup01515

Sub reports of AP Utilization are shown as separate reports

CSCup01797

Throughput unit in the AP Utilization report is not correct.

CSCup01830

The AP Utilization report shows incorrect Unit on SNR”

CSCup01980

Peak number of users for b/g/n shown in decimal

CSCup05322

LWAP: Able to set same values for Trunk and VLAN Id in Mesh tab

CSCup05366

LRAD Template: No User friendly message shown when deploy option clicked twice.

CSCup06870

Delete WLC/AP with super user still shows root as owner in job dashboard.

CSCup07326

LWAP Template: After editing, the interface selected check box gets unselected.

CSCup09690

TFTP upload throws an exception

CSCup10015

LWAP: All Applied AP filter shows wrong # of APs in a particular case

CSCup12072

Pushed LWAP Template successfully but All Applied AP filter does not work

CSCup12084

LWAP Template: Spelling mistake in the Apply Template’s toaster message

CSCup12698

Creating Duplicate IP Groups IPv4 Template does not work

CSCup13255

LWAP Template: No warning message shown when number of Trunk Ids > 16

CSCup13429

LWAP Template not deployed on selecting select all in predefined filters

CSCup16981

LWAP Template: Cannot delete multiple Trunk Ids at once in Mesh tab

CSCup17453

Prime Infrastructure duplicates NTP template with NTP IP address

CSCup17806

The 802.11ac features missing on LWAP Template

CSCup18391

Cross launching from Network Device shows ‘no data available’

CSCup19706

LWAP Template: Validation for AP Height field incorrect

CSCup21028

NDS Dashlet shows ‘No Data Available’ inside the ‘Total AP’ pie chart.

CSCup23459

AP Utilization: packet retransmission values are shown incorrectly

CSCup23468

LWAP Template’s schedule setting allow one to enter decimal values

CSCup25703

LWAP Template: scheduled AP filter does not work in a particular case

CSCup25710

LWAP Template: sometimes shows ‘Undefined’ deployment status

CSCup26634

LWAP Template: Many combinations in Advanced filter do not work

CSCup27017

Partial collection failure of cellular interfaces

CSCup30042

TFTP download from local machine and many options throw exceptions.

CSCup40228

Upload Software from controller page and commands page is not working

CSCup47374

The “No data available” message appears in deploy status table in some cases.

CSCup49345

The AP Utilization report shows failed to run report while running for two days to weeks.

CSCup52705

Status of the running job shown as completed in the job dashboard.

CSCup54359

VLAN ACL mapping shows no data available after collapse and expand.

CSCup57692

Unable to edit VLAN ACL mapping if section is collapsed while creating template.

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.