Table Of Contents
Release Notes for Cisco Prime Network Control System, Release 1.0.2.29
Contents
Introduction
Requirements
Supported Hardware
Supported Browsers
Supported Devices
Supported Versions
Installing NCS Software
NCS License Information
Finding the Software Release
Migrating WCS to NCS
Exporting WCS Data
Migrating WCS Data to NCS
Non-upgradable Data
Upgrading NCS 1.0 to NCS 1.0.2.29
NCS Features
Important Notes
Physical and Virtual Appliance
New License Structure
Wired Client Discovery
Autonomous AP Migration Analysis
Importing Maps
Features Not Supported
Monitoring Disk Usage
Recommendations for Managing Disk Usage
Caveats
Open Caveats
Caveats Associated with Release 1.0.2.29
Resolved Caveats
If You Need More Information
Troubleshooting
Related Documentation
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Prime Network Control System, Release 1.0.2.29
November 2011
These release notes describe the requirements, features, limitations, restrictions (caveats), and related information for the Cisco Prime Network Control System (NCS) Release 1.0.2.29, which is a part of the Cisco Unified Network Solution. These release notes supplement the Cisco NCS documentation that is included with the product hardware and software release.
Contents
These release notes contain the following sections:
•
Introduction
•Requirements
•Installing NCS Software
•Migrating WCS to NCS
•Upgrading NCS 1.0 to NCS 1.0.2.29
•NCS Features
•Important Notes
•Monitoring Disk Usage
•Caveats
•Troubleshooting
•Related Documentation
•Obtaining Documentation and Submitting a Service Request
Introduction
NCS is the next generation network management platform for managing both wired and wireless access networks. NCS delivers converged user, access and identity management, with complete visibility into endpoint connectivity regardless of the device, network, or location. NCS speeds up the troubleshooting of network problems related to client devices, which is one of the most reported customer pain points. NCS also provides monitoring of identity security policy through integration with Cisco Identity Services Engine (ISE) to deliver visibility into compliance based on real-time contextual information from the network, users, and devices across the entire wired and wireless access network.
NCS is a scalable platform that meets the needs of small, mid-sized, and large-scale wired and wireless LANs across local, remote, national, and international locations. NCS gives IT managers immediate access to the tools they need, when they need them, so that they can more efficiently implement and maintain secure wireless LANs, monitor wired and wireless LANs, and view users and endpoints across both networks all from a centralized location.
Operational costs are significantly reduced through the workflow-oriented, simplified, and intuitive user experience, of the platform as well as built-in tools that improve IT efficiency, lower IT training costs, and minimize IT staffing requirements, even as the network grows. Unlike overlay management tools, NCS incorporates the full breadth of management requirements from radio frequency, to controllers, switches, endpoints, and users on wired and wireless networks, and to mobility and identity services to deliver a scalable and unified platform.
Key benefits of NCS 1.0.2.29 include the following:
•Ease of Use—Simple, intuitive user interface designed with focus on workflow management. It supports user-defined customization to display only the most relevant information.
•Scalability—Manages complete lifecycle management of hundreds of Cisco wireless LAN controllers and 15,000 of Cisco Aironet lightweight access points from a centralized location. Additionally, NCS can also manage up to 5000 autonomous Cisco Aironet access points.
Note Each stack or chassis is counted as a single device.
Note Special Instructions for customers that tried to migrate from WCS 7.0.220.0 to NCS 1.0.2.28:
Please follow these steps in order:
1. Download NCS 1.0.2.29.
2. Upgrade from NCS 1.0.2.28.0 to NCS 1.0.2.29.
3. Restore the data from 7.0.220.0 using migration instructions in the release notes.
For other customers, kindly follow instructions in the release notes for upgrading to NCS 1.0.2.29 release.
•Wired Management—Comprehensive monitoring and troubleshooting support for maximum of 5000 Cisco Catalyst switches, which allows visibility into critical performance metrics for interfaces, ports, endpoints, users, and basic switch inventory.
•WLAN Lifecycle Management—Comprehensive wireless LAN lifecycle management includes a full range of planning, deployment, monitoring, troubleshooting, remediation, and optimization capabilities.
•Planning and deployment—Built-in planning and design tools simplify defining access point placement and coverage. Information from third-party site survey tools can be easily imported and integrated into NCS to aid in WLAN design and deployment. A broad array of integrated controller, access point, and command-line interface (CLI) configuration templates deliver quick and cost-effective deployment.
•Delivery Modes—Delivered as a physical or a virtual appliance allowing deployment scalability to help customers meet various deployment models.
In addition to these, NCS 1.0.2.29 supports non-English characters and provides greater stability.
Requirements
This section contains the following topics:
•Supported Hardware
•Supported Browsers
•Supported Devices
•Supported Versions
Supported Hardware
NCS software is packaged with your physical appliance, can be downloaded as an image for installation, or can be downloaded as a software image to run as a virtual appliance on a customer-supplied server. The NCS virtual appliance can be deployed on any of the platforms listed in Table 1.
Table 1 Supported Hardware
|
Hardware Platform
|
Configuration
|
Cisco Prime NCS High-End Virtual Appliance (physical/virtual appliance) |
•Supports up to 15000 Cisco Aironet lightweight access points, 5000 autonomous access points, 5000 switches and 1200 Cisco wireless LAN controllers. •Supports up to 100000 unified wireless clients, 50000 wired clients, and 20000 autonomous clients. •Processor Cores: 8, at 2.93 GHz or better. •Minimum RAM:16 GB. •Minimum Hard disk space allocation: 400 GB. |
Cisco Prime NCS Standard Virtual Appliance |
•Supports up to 7500 Cisco Aironet lightweight access points, 2500 autonomous access points, 2500 Switches and 600 Cisco wireless LAN controllers. •Supports up to 50000 unified wireless clients, 25000 wired clients, and 10000 autonomous clients. •Processor Cores: 4, at 2.93 GHz or better. •Minimum RAM: 12 GB. •Minimum Hard disk space allocation: 300 GB. |
Cisco Prime NCS Low-End Virtual Appliance |
•Supports up to 3000 Cisco Aironet lightweight access points, 1000 autonomous access points, 1000 Switches and 240 Cisco wireless LAN controllers. •Supports up to 25000 unified wireless clients, 10000 wired clients, and 5000 autonomous clients. •Processor Cores: 2, at 2.93 GHz or better. •Minimum RAM: 8 GB. •Minimum Hard disk space allocation: 200 GB. |
VMware ESX and ESXi Versions (Virtual Appliance on a Customer-Supplied Server) |
•If deploying NCS as a virtual appliance on a customer-supplied server, one of the following versions of VMware ESX or ESXi may be used: –VMware ESX or VMware ESXi version 4.0 –VMware ESX or VMware ESXi version 4.1 Note VMware Tools version 4.1 is preinstalled in the NCS virtual appliance. |
Note If you want to use a Cisco UCS server to deploy a virtual appliance for NCS, you can use the UCS C-Series or B-Series. Make sure the server you select matches the Processor, RAM and Hard Disk requirements specified in the "Supported Hardware" section.
Note Non-English characters are supported in Cisco Prime Network Control System, Release 1.0.2.29.
Note These specifications relating to the number of clients supported on different NCS configurations are based on combination of internal lab tests and our experience with large customer installations.
Supported Browsers
The NCS user interface requires Mozilla Firefox 3.6 or later minor version and Internet Explorer 8.x with the Chrome plugin releases or Google Chrome 12.0.742.x. Internet Explorer 6.0 is not supported. The client running the browser must have a minimum of 1 GB of RAM and a 2-GHz processor. The client device should not be running any CPU or memory-intensive applications.
Supported Devices
Table 2 lists the NCS supported devices for controllers, access point images, Identity Services Engine (ISE), and mobility services engines (MSE).
Table 2 Supported Device Matrix
|
Supported Switches
|
Supported Controllers
|
Supported MSE Devices
|
Supported ISE Devices
|
Supported Lightweight APs
|
Supported Autonomous APs
|
Cisco Catalyst 2960, 2975 Switches [IOS12.2(50)SE], Cisco Catalyst 3560 Switches [IOS12.2(50)SE], Cisco Catalyst 3750 Switches [IOS12.2(50)SE], Cisco Catalyst 4500 Switches [IOS12.2(50)SG], Cisco Catalyst 6500 Switches [IOS12.2(33)SXI]. |
Cisco 2100 Series Cisco 2500 Series Cisco 4400 Series Cisco 5500 Series Cisco Flex 7500 Series Wireless LAN Controllers Cisco Catalyst 3750G Series Integrated Wireless LAN Controllers Cisco Catalyst 6500 Series Wireless Services Modules (WiSM/WiSM2) Cisco Wireless LAN Controller Module on SRE Cisco Wireless LAN Controller Module (WLCM and WLCM-E) for Integrated Services Routers; |
Cisco MSE 3300 Series |
Cisco ISE 3300 Series |
Cisco 600 Series,
Cisco 1000 AP,
Cisco 1040 AP,
Cisco 1100 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 1552 AP,
Cisco 3500i AP,
Cisco 3500e AP,
Cisco 3500p AP,
Cisco 3600i AP,
Cisco 3600e AP |
Cisco 801 AP,
Cisco 1100 AP,
Cisco 1130 AP,
Cisco 1200 AP,
Cisco 1230 AP,
Cisco 1240 AP,
Cisco 1250 AP,
Cisco 1260 AP,
Cisco 1141 AP,
Cisco 1142 AP,
Cisco 1800 and
Cisco 800 ISR Series. Cisco Aironet 1310 and 1410 Bridges |
Supported Versions
Table 3 lists the NCS supported versions of controllers, access point images, Identity Services Engine (ISE), and mobility services engines (MSE).
Table 3 Supported Version Matrix
|
NCS Version
|
Supported Controller Version
|
|
Supported ISE Version
|
Supported Cisco IOS Switch Version
|
Operating System Requirements
|
Supported ACS Server Version
|
NCS 1.0.2.29 |
7.1.91.02 , 7.0.230.0, 7.0.220.0, 7.0.116.0, 7.0.98.218, 7.0.98.0, 6.0.202.0, 6.0.199.4, 6.0.196.0, 6.0.188.0, 6.0.182.0, 6.0.108.0, 4.2.209.0, 4.2.207.0, 4.2.205.0, 4.2.176.0, 4.2.173.0, 4.2.130.0, 4.2.112.0, 4.2.99.0, 4.2.61.0 |
7.0.230.0, 7.0.220.0, 7.0.201.204, 6.0.202.0, 6.0.103.0, 6.0.105.0 (LBS). |
ISE 1.0 |
IOS12.2(50)SE, IOS12.2(50)SG, IOS12.2(33)SXI |
VMWare ESX or VMWare ESXi Version 4.0 VMWare ESX or VMWare ESXi Version 4.1 |
ACS 4.1, ACS 4.2, ACS 5.1, ACS 5.2 |
NCS 1.0.1.4 |
7.0.220.0, 7.0.116.0, 7.0.98.218, 7.0.98.0, 6.0.202.0, 6.0.199.4, 6.0.196.0, 6.0.188.0, 6.0.182.0, 6.0.108.0, 4.2.209.0, 4.2.207.0, 4.2.205.0, 4.2.176.0, 4.2.173.0, 4.2.130.0, 4.2.112.0, 4.2.99.0, 4.2.61.0 |
7.0.201.204, 6.0.202.0, 6.0.103.0, 6.0.105.0 (LBS). |
ISE 1.0 |
IOS12.2(50)SE, IOS12.2(50)SG, IOS12.2(33)SXI |
VMWare ESX or VMWare ESXi Version 4.0 VMWare ESX or VMWare ESXi Version 4.1 |
ACS 4.1, ACS 4.2, ACS 5.1, ACS 5.2 |
NCS 1.0.0.96 |
7.0.116.0, 7.0.98.218, 7.0.98.0, 6.0.202.0, 6.0.199.4, 6.0.196.0, 6.0.188.0, 6.0.182.0, 6.0.108.0, 4.2.209.0, 4.2.207.0, 4.2.205.0, 4.2.176.0, 4.2.173.0, 4.2.130.0, 4.2.112.0, 4.2.99.0, 4.2.61.0 |
7.0.201.204, 6.0.202.0, 6.0.103.0, 6.0.105.0 (LBS). |
ISE 1.0 |
IOS12.2(50)SE, IOS12.2(50)SG, IOS12.2(33)SXI |
VMWare ESX or VMWare ESXi Version 4.0 VMWare ESX or VMWare ESXi Version 4.1 |
ACS 4.1, ACS 4.2, ACS 5.1, ACS 5.2 |
Installing NCS Software
The following steps summarize how to install new NCS 1.0.2.29 software on supported hardware platforms (see the "Supported Hardware" section for support details).
Step 1 Click Cisco Download Software at http://www.cisco.com/cisco/software/navigator.html?a=a&i=rpm. You might be required to provide your Cisco.com login credentials.
Step 2 Choose Products > Wireless > Wireless LAN Management > Unified Wireless LAN Management > Cisco Prime Network Control System.
Step 3 Download the appropriate NCS software version .OVA image (for example. NCS-VA-1.0.0.X-large/small/medium.ova) and deploy the OVA template.
Step 4 Reboot the virtual appliance to initiate the NCS installation process.
Step 5 Perform the initial NCS configuration according to the instructions in the Cisco Prime Network Control System Configuration Guide, Release 1.0. Before you run the setup program, ensure that you know the configuration parameters listed in Table 4.
Table 4 Initial Configuration Parameters
|
Parameter
|
Description
|
Hostname |
Must not exceed 19 characters. Valid characters include alphanumeric (A-Z, a-z, 0-9), hyphen (-), with a requirement that the first character must be an alphabetic character. Note We do not recommend using mixed case and hyphens in the hostname. |
IP address |
Must be a valid IPv4 address for the eth0 Ethernet interface. |
Netmask |
Must be a valid IPv4 address for the netmask. |
Default gateway |
Must be a valid IPv4 address for the default gateway. |
DNS domain name |
Cannot be an IP address. Valid characters include ASCII characters, any numbers, hyphen (-), and period (.). |
Primary name server |
Must be a valid IPv4 address for an additional Name server. |
Add/Edit another name server |
Must be a valid IPv4 address for an additional Name server. |
Primary NTP server |
Must be a valid NTP domain. |
Add/Edit another NTP server |
Must be a valid NTP domain. |
System Time Zone |
Must be a valid time zone. The default value is UTC. |
Username |
Identifies the administrative username used for access to the NCS system. If you choose not to use the default, you must create a new username, which must be from 3 to 8 characters in length, and be composed of valid alphanumeric characters (A-Z, a-z, or 0-9). |
Password |
Identifies the administrative password used for access to the NCS system. You must create this password (there is no default), and it must be composed of a minimum of six characters in length, include at least one lowercase letter (a-z), at least one uppercase letter (A-Z), and at least one number (0-9). |
High Availability Role |
Enter Yes, if you want to specify the server as the secondary server for High Availability. Enter No, if you do not want to specify the server as the secondary server for High Availability. |
Web Interface Root Password |
Enter the root password for the web interface or the NCS root password. |
FTP Password |
Enter the FTP password. The default FTP username is ftp-user |
This section contains the following topics:
•NCS License Information
•Finding the Software Release
NCS License Information
NCS is deployed through a physical or virtual appliance. Use the standard License Center Graphical User Interface to add new licenses, which are locked by the standard Cisco Unique Device Identifier (UDI). When NCS is deployed on a virtual appliance, the licensing is similar to a physical appliance, except instead of using a UDI, you use a Virtual Unique Device Identifier (VUDI). The NCS license is recognized by the SKU, which is usually attached to every purchase order to clearly identify which software or package is purchased by a customer.
For more detailed information on license types and obtaining licenses for NCS, see the "NCS and End User License" chapter of the Cisco Prime Network Control System Configuration Guide, Release 1.0.
For detailed information and license part numbers available for NCS, including licensing options for new installations as well as migration from an existing Cisco product like Cisco Wireless Control System, see the Cisco Network Control System Ordering Guidelines at http://www.cisco.com/web/ordering/root/index.html.
Finding the Software Release
If NCS is already installed and connected, verify the software release by choosing Help > About Cisco NCS. To find more information on the software release that NCS is running, see the Cisco Prime Network Control System Configuration Guide, Release 1.0.
Migrating WCS to NCS
Note You must upgrade your Cisco WCS deployment to Release 7.0.164.3 or 7.0.172.0 or 7.0.220.0 before you attempt to perform the migration process to NCS 1.0.2.29.
This section provides instructions for migrating the WCS on either a Windows or Linux server to NCS. The NCS release is a major release to provide for converged management of wired and wireless devices, and increased scalability. The NCS platform is based on Linux 64 bit OS, and the backend database is Oracle DBMS. The existing WCS platforms are either Windows or Linux 32 bit and the backend database is Solid DB.
This section contains the following topics:
•Exporting WCS Data
•Migrating WCS Data to NCS
•Non-upgradable Data
Note For steps on migrating NCS in a high availability environment, see Chapter 4, "Performing Maintenance Operations" of the Cisco Prime Network Control System Configuration Guide, Release 1.0.
Exporting WCS Data
Note There is no GUI for exporting data from WCS 7.x. The export userdata CLI command is available in WCS Release 7.x and later, which creates the .zip file containing the individual data file. The CLI does not provide any option to customize what can be exported; all non-global user-defined items are exported.
To export WCS data, follow these steps:
Step 1 Stop the WCS server.
Step 2 Run the export command through the script file and provide the path and export filename when prompted.
Note You can find the export script at: <Installation Directory>\WCS7.0.x.x\bin (for Windows) or <Installation Directory>/WCS7.0.x.x/bin (for Linux).
Step 3 For Linux, navigate to the bin directory and run the ./export.sh all /data/wcs.zip command. For Windows, run the .\export.bat all \data\wcs.zip command.
Note When migrating data from single WCS server to NCS, use the export.sh all command for Linux and export.bat all command for Windows to export WCS data. When migrating data from multiple WCS servers to NCS, you need to first export data from the largest WCS server using either the export.sh all command for Linux or export.bat all command for Windows, and then import the data into NCS. Then, select the next WCS server and use the export userdata command to export data from the WCS server. Import the data into NCS. Repeat this process for other WCS servers.
Migrating WCS Data to NCS
To migrate WCS data, follow these steps:
Step 1 Place the WCS export.zip file (for example, wcs.zip) in a repository or folder (for example, repositories).
Step 2 Log in as admin user and stop the NCS server by entering the ncs stop command.
Step 3 Configure the FTP repository on the NCS appliance by entering the repository command:
ncs-appliance/admin#configure
ncs-appliance/admin(config)#repository ncs-ftp-repo
ncs-appliance/admin(config-Repository)#url ftp://209.165.200.227//
ncs-appliance/admin(config-Repository)#user ftp-user password plain ftp-user
Note Make sure the archived file is available using the show repository repositoryname command.
Step 4 Enter the ncs migrate command to restore the WCS database.
ncs-appliance/admin# ncs migrate wcs-data wcs.zip repository ncs-ftp-repo
By default, no WCS events are migrated.
Step 5 Enter the ncs start command to start the NCS server after the upgrade is completed.
Step 6 Log in to the NCS user interface using the root login and the root password.
Non-upgradable Data
The following data are not upgradable from WCS to NCS:
•Certain Reports (AP Image Predownload, AP Profile Status, AP Summary, Client Count, Client Summary, Client Traffic, PCI Report, PCI Compliance Detailed and Summary reports, Preferred Call Network Summary report, Rogue APs, Adhoc Rogues, New Adhoc Rogues and Security Summary reports).
•Dashboard customization
•Client Station Statistics information is not populated with old WCS data in clients charts, client details page, dashboards and reports.
•Client historical session information does get upgraded.
•All events from Release 7.0 are completely dropped and are not migrated to NCS.
•RADIUS/TACACS server IP and credentials are not migrated and need to be added again after the migration is complete.
Note Make sure you enable the RADIUS/TACACS server as AAA mode in the Administration > AAA > AAA Mode Settings page, and click Save.
•Only alarms with Root Virtual Domain are migrated from Release 7.0 to NCS.
Note All Release 7.0 alarms and event data are stored as CSV files along with other data in a .zip file during upgrade.
•The root password is not migrated from Release 7.0.164.3 or 7.0.172.0 to NCS Release 1.0.2.29. The user must change the root password during the installation of the application. Non root users and their credentials are migrated during migration.
•Alarm categories and subcategories are not restored after migration to NCS Alarm Summary.
Upgrading NCS 1.0 to NCS 1.0.2.29
You can upgrade from NCS Releases 1.0.0.96, 1.0.1.4, and 1.0.2.28 to NCS 1.0.2.29.
Caution
Ensure that you perform a backup before attempting to upgrade.
Caution
Disable High Availability before performing the upgrade.
Note Shut down NCS before performing the upgrade. To stop NCS, run the ncs stop command.
Use the following command to upgrade from NCS 1.0 to NCS 1.0.2.29:
# application upgrade NCS-upgrade-bundle-1.0.2.x.tar.gz wcs-ftp-repo
In the preceding command, NCS-upgrade-bundle-1.0.2.29.tar.gz is the upgrade bundle file, which is available for download.
The repository used in the example, wcs-ftp-repo, can be any valid repository.
Examples of repository configurations follow.
FTP Repository:
(config)# repository wcs-ftp-repo
(config-Repository)# url ftp://ip-address
(config-Repository)# user ftp-user password plain ftp-user
(config-Repository)# exit
SFTP Repository:
(config)# repository wcs-sftp-repo
(config-Repository)# url sftp://ip-address
(config-Repository)# user ftp-user password plain ftp-user
(config-Repository)# exit
TFTP Repository:
(config)# repository wcs-tftp-repo
(config-Repository)# url tftp://ip-address
(config-Repository)# exit
NCS Features
There are no new features in this maintenance release.
Important Notes
This section describes important information about NCS.
This section contains the following topics:
•Physical and Virtual Appliance
•New License Structure
•Wired Client Discovery
•Autonomous AP Migration Analysis
•New License Structure
Physical and Virtual Appliance
NCS is available as a physical or virtual appliance. Both are self-contained, and include the operating system, application, and database. These availability options speed up deployments and deliver greater deployment flexibility.
New License Structure
NCS is deployed through physical or virtual appliances. Use the License Center Graphical User Interface (Choose Administration > License Center from the NCS home page) to add new licenses, which is locked by the Cisco Unique Device Identifier (UDI). When NCS is deployed on a virtual appliance, the licensing is similar to a physical appliance, except instead of using a UDI, you use a Virtual Unique Device Identifier (VUDI). The NCS license is recognized by the SKU, which is usually attached to every purchase order to clearly identify which software or package is purchased by a customer. For more information about UDI or VUDI, see the Cisco Prime Network Control System Configuration Guide, Release 1.0.
Wired Client Discovery
Wired client discovery depends on the Content Address Memory (CAM) table on the switch and this table is populated with the clients data. When a wired client is not active (not sending traffic) for a certain amount of time, usually five minutes, the corresponding client entry in the CAM table times out and is removed. In this case, the client is not discovered in NCS.
Autonomous AP Migration Analysis
Migration Analysis used to run autonomous AP during discovery can be configured by selecting the Run Autonomous AP Migration Analysis on discovery check box in the Administrator > Settings > CLI Session page. By default this option is disabled.
Importing Maps
The Aeroscout engine fails to start MSE if the importing map names contain special characters such as '&'.
Features Not Supported
The following list of older features is not supported in NCS Release 1.0.2.29:
•Monitor RRM Enhancements
•WEB-auth on MAC filter failure
•NAC 802.11 disassociation trap-webauth proxy
•11-N Mesh support
•NEC Phase III enhancements/Preferred Call
•Voice Diagnostics
•General Video Support
Monitoring Disk Usage
You can monitor the current disk usage from the NCS > Administration > Appliance page.
When the NCS backup background task fails, it indicates there is an issue with disk space. Choose NCS > Administration > Background Tasks to check the status of the NCS Backup Task.
Recommendations for Managing Disk Usage
The following are the recommendations to effectively utilize and manage disk space in the NCS server:
•Clean up some of the old files in the /dev/mapper/smosvg-localdiskvol partition so that there is some space available in this partition. This partition is the user accessible area of the disk where any reports, FTP files, and local repository files are stored. This partition should have some free space so that files can be stored in this location. If this partition is full then any attempt to store files will fail.
There are two ways to clean up the files located in this partition:
–Log into NCS CLI as an admin User and run the delete disk:/dir/filename command to delete files from the /dev/mapper/smosvg-localdiskvol partition.
–Log into NCS CLI as an admin User and run the ncs cleanup command. You are prompted to confirm if you would want to delete all files in the local disk partition.
•Configure the NCS backup background task so that it uses a remote repository. This helps you to manage the space in the local disk partition effectively. You can configure a remote repository using any of the following protocols:
–FTP
–NFS
–SFTP
–TFTP
Example of a Remote Repository Configuration follows:
ncs-appliance/admin# configure
Enter configuration commands, one per line. End with CNTL/Z.
ncs-appliance/admin(config)# repository remote_repository
ncs-appliance/admin(config-Repository)# url ?
<WORD> Enter repository URL, including server and path info (Max Size - 80)
cdrom: Local CD-ROM drive (read only)
disk: Local hard disk storage
ftp: URL using a FTP server
http: URL using a HTTP server (read only)
https: URL using a HTTPS server (read only)
nfs: URL using a NFS server
sftp: URL using a SFTP server
tftp: URL using a TFTP server
ncs-appliance/admin(config-Repository)# url ftp://hostname/rootDir.
•Ensure the used disk space in the /dev/mapper/smosvg-optvol partition is below 70% so that the backup attempts do not fail. If you encounter backup failures then you can configure a remote NFS mount for the backup task. This remote NFS mount should be an open share with read and write permissions.
Example of a remote staging area configuration follows:
ncs-appliance/admin# configure
Enter configuration commands, one per line. End with CNTL/Z.
ncs-appliance/admin(config)# backup-staging-url ?
<WORD> NFS URL for staging area (Max Size - 2048)
ncs-appliance/admin(config)# backup-staging-url nfs://hostname:/mount
ncs-appliance/admin(config)# exit
•Add additional disk space in a virtual appliance if you encounter disk space issues.
If you have additional disk space available with your deployed Virtual Appliance, then you can modify that Virtual Appliance to use more of that space. For this release, contact Cisco TAC to help in increasing the disk space available to the Virtual Appliance.
•Change the data retention period for aggregated data if you want to manage the disk space. To change the retention period for aggregated data, choose NCS > Administration > Settings > Data Management and change the values.
The following are the recommendations for changing the data retention period for aggregated data.
Table 5 Data Retention Period for Aggregated Data - Recommendations
|
Aggregation
|
Default
|
Recommendation for systems with more than 5000 clients
|
Hourly |
31 days |
15 days |
Daily |
90 days |
60 days |
Weekly |
54 weeks |
54 weeks |
The settings decide how long NCS retains the aggregated data. NCS polls for statistics data every hour, day, and week. The statistics data is used to generate trending charts or reports. You can significantly reduce the size of many aggregated tables by reducing the size of the aggregation period. The drawback being the granularity of trending charts or reports might be bigger.
For example, if you create a four weeks long Client Count chart, with the default setting, the hourly data is used. It means it has 4*7*24=672 data points (samples). With the new setting, the daily data is used and it will have 4*7=28 data points. You will not see any change if you create a chart or report for less than 2 weeks.
Caveats
This section lists open and resolved caveats in NCS Release 1.0.2.29. For your convenience in locating caveats in Cisco's Bug Toolkit, the caveat titles listed in this section are taken directly from the Bug Toolkit database. These caveat titles are not intended to be read as complete sentences because the title field length is limited. In the caveat titles, some truncation of wording or punctuation might be necessary to provide the most complete and concise description. The only modifications made to these titles are as follows:
•Commands are in boldface type.
•Product names and acronyms may be standardized.
•Spelling errors and typos may be corrected.
Note If you are a registered cisco.com user, view Bug Toolkit on cisco.com at the following website:
http://tools.cisco.com/Support/BugToolKit/.
Note To become a registered cisco.com user, go to the following website:
https://tools.cisco.com/RPF/register/register.do
This section contains the following topics:
•Open Caveats
•Resolved Caveats
Open Caveats
Caveats Associated with Release 1.0.2.29
Table 6 lists the open caveats in NCS Release 1.0.2.29
Table 6 Open Caveats
|
ID Number
|
Caveat Title
|
CSCtr57972 |
The UDI information from CLI and NCS UI does not match. Symptom: The UDI information obtained from CLI does not match what appears in the NCS GUI. The CLI value is not correct for licensing or identifying the NCS. Conditions: Any CLI command that displays the UDI of the virtual machine is displaying the incorrect value. Workaround: Only use the UDI displayed in the GUI for licensing or identifying the NCS. |
CSCtq09640 |
Sometimes Switch Location Configuration Template apply gives error. Symptom: Sometimes Switch Location Configuration Template apply gives error Conditions: When using the switch location configuration template to apply template to a large number of ports, telnet connection to the switch might time out. When you choose Configure > Switch Location Configuration Template, create a template and apply to switch interface, it shows 'EXCEPTION_THROWN'. Workaround: Apply template to a couple of ports at a time. |
CSCtq84181 |
Assigning selected devices to a Virtual Domain takes long time. Symptom: NCS takes long time to add selected controllers or access points in a virtual domain. Conditions: When a large number of controllers or access points are selected to be part of a virtual domain, NCS takes long time (of the order of minutes) to add them in the virtual domain. This slowness is observed when the number of controllers is above 100 or the number of access points is above 1000. Workaround: Add small number of controllers or access points to a virtual domain, at a time. |
CSCtq84792 |
DB server cannot start if restore server timestamp is behind backup server. Symptom: 1. Take a NCS Server backup from Server running on timestamp-B. 2. Now, change the NCS date/time to timestamp-A such that timestamp-A is less than timestamp-B. 3. Restore NCS backup taken from step2 on NCS Server running on timestamp-A, NCS fails to start and throws error. Conditions: NCS 1.0 is running behind date/time which is in the DB backup. Workaround: Configure and Set the correct date/time on NCS. |
CSCtq87447 |
Exception when you add autonomous AP once deleted from Virtual Domain. Symptom: NCS failed to delete an autonomous AP from a virtual domain. Conditions: This happens when an autonomous AP is first added into the root domain and then assigned it to a virtual domain. Later, the user logged into the same virtual domain, deleted the autonomous AP and then re-added it with wrong credentials. Workaround: Delete the autonomous AP from the root domain. |
CSCtq87805 |
Sorting ethernet switches by IP address does not work. Symptom: Sorting ethernet switches by IP address does not work on Monitor > Switches page. Conditions: When user reaches the Monitor > Switches page by clicking on the pie chart on the NCS home page. Workaround: Go to the Monitor > Switches page from the top Menu. |
CSCtq92383 |
PDF Report export for large data set can take from 30 minutes to few hours. Symptom: Interactive Save and export operation for report containing large data set can take a long time. Conditions: Run Save and Export for a report containing large data set and set the export format to PDF. The operation can take anywhere from few minutes to hours. Workaround: The same report can be scheduled instead of doing an interactive report generation through Save and Export. Further Problem Description: The amount of time taken for a report generation in PDF format is dependent upon the data set for the report, time taken by data retrieval from db which in turn depends among other things upon how busy the db is and JasperReport generation time. |
CSCtq94128 |
Expanded row with detail shown in Event Page is not fixed on the top. Symptom: When clicking the row expander to view detail in Event or Alarm page, the expanded row is not highlighted or fixed on the top of the table. Conditions: If the total number of events or alarms in the scope changes when user clicks the row, the expanded row may no longer be in focus. Workaround: User may need to scroll down the table to find the expanded row with detail shown. |
CSCtq94148 |
Alarm detail view is closed after failure to launch location history. Symptom: When user clicks 'Location History' link inside Rogue AP Alarm detail panel, warning dialog may pop up if location page can't be launched. After the 'ok' button in the warning dialog is clicked, alarm detail panel will be closed. Conditions: When failure to launch 'Location History' page from Rogue AP Alarm Detail, the alarm detail panel will be closed. Workaround: User may need to find and click the row expander to re-open the alarm detail. |
CSCtq94229 |
Adding Switch (SPT mode only) to Virtual Domain throws exception. Symptom: Adding Switch (with SPT mode only) to Virtual Domain throws internal exception error. Conditions: Whenever we have a Switch added with license level SPT only, associating the Switch to any Virtual Domain throws Internal exception error. Workaround: None. |
CSCtq96037 |
Added controller is found in switch list page in a NAT setup. Symptom: When you restore customer DB backup from NCS, and adding couple of controllers. Both the controllers show up in configure > Switch list page. Conditions: This affects version 1.0 of the Cisco Prime Network Control System. Workaround: None. |
CSCtq96208 |
User without planning mode permissions is able to launch planning tool. Symptom: Users without the Planning Mode permission are able to launch the Planning Tool. Conditions: This affects version 1.0 of the Cisco Prime Network Control System. Workaround: None. |
CSCtr00084 |
Invalid parameter "Dynamic Tx Power Control" in config RRM TPC. Symptom: Invalid parameter "Dynamic Tx Power Control" shows up in Config RRM TPC. Conditions: All Configure RRM TPC shows this error. Workaround: None. |
CSCtr00174 |
DCA Channel Width parameter is not present in RRM templates. Symptom: DCA Channel Width parameter is not present in RRM templates. Conditions: Choose Configure > Controller Template Launch Pad > 802.11a/n > DCA > Controller Template. THe DCA Channel Width is not available for RRM 802.11a template. Workaround: Manually go to each Controller page's DCA Section and configure Channel Width. |
CSCtl77129 |
User authentication through TACACS+ shows Access denied in dual network. Symptom: User authentication via TACACS+ displays Access denied page when used for a particular interface in a Dual NIC NCS and ACS server Conditions: Both NCS and ACS servers have Dual NIC support and is reachable to each other. Under Administration > AAA > AAA Mode Settings page, TACACS+ option is selected and "Enable fallback to Local" is checked with default option. Workaround: Works well with one of the two interfaces Further Problem Description: NCS Box has two interfaces - 10 N/w (10.x.x.x) & 9 N/w IP(9.x.x.x); (With default route on 10 N/w) Similarly ACS server has above two interfaces. In NCS, you can create AAA TACACS+ server selecting 10 N/w interface. AAA user authentication works fine. However when you create AAA TACACS+ server selecting 9 N/w interface, AAA user authentication is failing. |
CSCto16463 |
Software version column sorting in controller page is incorrect. Symptom: Try sorting on Software Version column on Controllers List Page. The sorting happens with digit by digit comparison and not as octets. For example, 7.0.98.1 falls higher than 7.0.114.0 though 98 is less than 114. Conditions: This affects version 1.0 of the Cisco Prime Network Control System. Workaround: None. Further Problem Description: Considering versions as 7.0.114.102, 4.2.212.0, 7.0.98.0, 7.0.114.97 NCS sorts as 4.2.212.0 7.0.114.102 7.0.114.97 7.0.98.0 The correct sorting should be 4.2.212.0 7.0.98.0 7.0.114.97 7.0.114.102 |
CSCto44918 |
AAA Radius/TACACS+ servers are not migrated from WCS to NCS. Symptom: The Radius/TACACS+ servers created in previous release of WCS are not getting migrated to NCS. Conditions: Radius / TACACS+ servers are created in previous releases of WCS, restoring data from these releases onto NCS does not migrate AAA servers. Workaround: Create Radius / TACACS+ servers again in NCS and navigate to Administration > AAA > AAA Mode Settings page, reconfirm the Mode set. Save the settings and perform AAA user authentication. |
CSCto96526 |
User Group Audit trail does not display AAA auth. user operations. Symptom: When AAA users belonging to a particular User group login to NCS, the audit trail logs for that particular User group doesn't display any information on these AAA users login / logout operation. Conditions: User Group Audit trail missing for AAA authenticated users only. Workaround: However the audit trail is displayed from Active Sessions page for the AAA logged in user. |
CSCtq04302 |
The Channel Utilization chart should be renamed in the Radio Monitoring Page. Symptom: Channel Utilization chart on the Radio Monitoring Page is different from Channel Utilization under Load Statistics. They should not be correlated. Conditions: Navigate to Radio Monitoring Page Workaround: None. |
CSCtq10930 |
Time period for saved search is not retained after upgrade. Symptom: Time period for saved search is lost after upgrade. Conditions: None. Workaround: None. |
CSCtq11177 |
OfficeExtend AP settings are not retained after upgrade for air quality report. Symptom: OfficeExtend AP settings are not retained after upgrade for air quality Vs time report. Conditions: Air Quality Vs time report created in WCS 7.0 with settings as All Controllers > All Office Extend APs gets reset to All Controllers > All Access Points when backed up and restored in NCS. Workaround: Change the report settings back to All Controllers > All OfficeExtend APs. |
CSCtq31584 |
Duplication of RRM > TPC configuration parameters in different places. Symptom: Duplication of RRM > TPC configuration parameters in different places. The transmit power threshold configuration is present in two different paths in NCS. If one is updated then the other link shows a mismatch. Conditions: Appears at 802.11 (a/n and b/g/n) RRM > TPC and 802.11 (a/n and b/g/n) > Parameters. Workaround: Just configure RRM TPC Parameters at RRM > TPC page and ignore settings at 802.11 (a/n and b/g/n) > Parameters. |
CSCtq31784 |
Discrepancy in RRM > DCA > Channel Update Interval. Symptom: The 'Channel Update Interval' interval is not getting updated on NCS. It always shows the default value of 600 seconds. Audit will not show a mismatch if controller is configured with a different value. Refresh Config from controller is also not updating the DCA update interval on NCS. Conditions: When Controller is configured with a different value. Workaround: None. |
CSCtq32125 |
Planning mode > Add APs, Override... option includes other services. Symptom: While using the Planning Tool to automatically add APs to a floor, if you choose the option "Override Coverage Per AP Per AP Area" all of the options for Data, Voice, etc. are disabled. However, if you checked them prior to checking "Override Coverage Per AP Per AP Area" those options will still be part of the calculation when you click on Calculate. Conditions: This applies to version 1.0 of the Cisco Prime Network Control System. Workaround: Uncheck all of the Services options before selecting Override Coverage Per AP Per AP Area. |
CSCtq53132 |
AP Summary pop-up appears out of bounds. Symptom: When you hover your mouse over an object on a floor or outdoor area page, the informational popup appears partially off-screen. Conditions: This occurs most frequently when the object is in the lower-right corner of the map. Workaround: Use your middle mouse button to scroll with your mouse, and scroll to reveal the rest of the popup. This may also work with a multi-finger drag on certain touchpads. |
CSCtq67819 |
Audit in RF group page should open a popup even if their are no mismatches. Symptom: Navigate to Configure > Controllers > 802.11a/n > RRM > RF Grouping. If there are no mismatches then a popup should open with the following text "No differences found between NCS and device values". Conditions: When there are no mismatches between NCS RF Grouping Config and WLC RF Grouping config, No popup opens to mention the there were no differences. Workaround: None |
CSCtq70306 |
Alarm mismatch between Maps Tree view and Floor view. Symptom: View the Maps Tree view for a particular floor area. The icon for the floor indicates that there is a Critical alarm present. Similarly, that floor's entry on the map list page may show a critical radio alarm. However, when you view the floor, all of the access point icons show only yellow for Major alarms. Conditions: This affects version 1.0 of the Cisco Network Control System. It also affects all versions of the Cisco Wireless Control System. Workaround: Use the Floor Settings menu to display the AP status instead of the radio status. Click on the arrow `>' for Access Points to display the Access Points filter, and select AP Status. You can save this preference with the Save Settings button. |
CSCtq79369 |
Monitor > Spectrum Expert shows different count for alarms on clicking the hyperlink. Symptom: Alarms shown on clicking the alarm count link on Monitor > SE page shows all SE alarms and not just the alarms specific to the current SE. Conditions: More than one SE connected to WCS. Workaround: None. |
CSCtq81553 |
WI-FI invalid category is shown as SuperAG in SE detected interferers. Symptom: WI-FI invalid category is shown as SuperAG in Monitor > SE detected interferers. Conditions: This affects version 1.0 of the Cisco Network Control System. It shows WI-FI Invalid interferer. Workaround: None. |
CSCtq81833 |
SE becomes unreachable after some time but alarms keep coming. Symptom: Issues with adding SE or after adding SE, connection terminates. Conditions: This affects version 1.0 of the Cisco Network Control System. Workaround: None. |
CSCtr04327 |
Export operations for ClientSessionReport may take from 30 minutes to few hours. Symptom: Exporting Client Sessions report in CSV or PDF format might take long time if the network has lot of mobile clients resulting in millions of sessions over a period of time. The interactive export operation might take anywhere from 30 minutes to few hours. Conditions: - Select long period of reporting time (say 4 weeks) - A lot sessions in the database - Data Cleanup task is running or the database is busy Workaround: - Select shorter period of time to run - Schedule to run the report in less busy time - Schedule to run a few hour before you need the report Further Problem Description: The problem is observed in a database having over 10 million sessions. |
CSCto07596 |
Exception is seen in the log while deleting a controller. Symptom: Delete controller fails with exception in the log. Conditions: This affects version 1.0 of the Cisco Network Control System. Workaround: Try the delete again. |
CSCtq10886 |
Not getting results for AP summary report if run by Floor Map in a Virtual Domain. Symptom: Not getting results for AP summary report if run by Floor Map in a virtual domain. Conditions: This happens when the parent campus-maps and the parent building-maps are not present in the same virtual domain where their children floor-maps are present. Workaround: Add the parent campus-maps and the parent building-maps for all the floor-maps that are in a virtual domain. |
CSCtq22201 |
Symptom: When NCS is unlicensed, clicking on Advanced search gives error dialog with content "Error while parsing rendering content.....". Conditions: NCS is unlicensed. Workaround: Add a NCS license. |
CSCtq37963 |
Idle timeout happens even if it is not enabled. Symptom: Session gets timed out even when the idle timeout in user preferences is disabled. Conditions: This issue happens only for the following condition: - idle timeout is enabled and user log out of the session. - after logging back in user disable the idle timeout and save the setting however the session still gets timed out. Workaround: If user logs out again and log back in then the idle timeout setting is correctly persisted. |
CSCtq53528 |
SPT is not working in VD environment. Symptom: Switch Port Tracing (SPT) does not work properly in a virtual domain. Conditions: NCS will use all the switches and APs to perform SPT even though SPT request is issued from a certain virtual domain. Workaround: None. |
CSCtq68680 |
RF Group Summary lacking link to detailed Summary under RRM Dashboard. Symptom: There is no way of knowing RF Group summary- only count will be seen like 10. It should be click-able and allows user to further look at summary a/n, bg/n groups with IP address and more information. Conditions: Click Monitor > RRM Dashboard. Workaround: None. |
CSCtr04897 |
SPT switches information not visible after upgrade. Symptom: For Switches upgraded from WCS 7.x will not have model name, description, software version, and so on in the Inventory Reports and the reachability status is missing as well. Inventory reports does not show all the information for SPT switches. Shows only "Device Name and IP Address". It has to show all other information like:model name, description, software version, and so on. Conditions: Upgrade switches from WCS 7.x to NCS. Workaround: Perform a manual switch sync from NCS will trigger the switch reachability status update. |
CSCtu11509 |
Wrong date and time information displayed in wIPS alarm general information section of the wIPS Alarm Details page. Symptom: In wIPS alarm details page the Message field does not provide specific alarm information. The alarm First seen, Last Seen and Last Disappeared time are showing a wrong date. Conditions: None. Workaround: None. |
.
Resolved Caveats
Table 7 lists caveats resolved in NCS 1.0.2.29.
Table 7 Resolved Caveats
|
ID Number
|
Caveat Title
|
CSCtr09048 |
NCS displays error message if the ACL has 64 ACL rules. |
CSCtr05965 |
'Logged in Guest User' Dashlet do not show all guest clients sometimes. |
CSCtr16460 |
Charts are not visible on chrome browser for Monitor > radio details. |
CSCtr16514 |
Unacknowledged tasks are accessible to all users on alarm detail page. |
CSCtq76735 |
Switch and NCS category NB traps is not supported in Netcool. |
CSCtq76770 |
Unresponsive script warning in selecting AP's for Virtual Domain. |
CSCtq66036 |
Template Virtual Domain propagation does not happen when it gets applied to a controller. |
CSCtq39369 |
Exception is thrown when you add a virtual domain to user in Non-root Virtual Domain. |
CSCtq37281 |
No link to cross launch AP details from AP alarm detail panel. |
CSCtq00666 |
Root domain is shown twice on upgraded NCS server. |
CSCtr08113 |
Switches added for SPT shows up under client report filters. |
CSCtr71227 |
Secondary high availability server could not be upgraded using the application upgrade option. |
CSCtq79221 |
There are few Switch Port Tracing issues after data migration from WCS to NCS. |
CSCtq57832 |
TACACS+ users does not remember the last logged in Virtual Domain. |
CSCtq64164 |
Mobility groups shows controllers that do not belong to current active Virtual Domain. |
CSCtq34227 |
Invalid trap log message in Monitor > events for signal change. |
CSCtr49933 |
Alarm annotations character encoding issue. |
CSCtq29277 |
Interface Group Template can select quarantine and non-quarantine interfaces. |
CSCtq18725 |
Advanced search is not showing all RRM CleanAir channel change events. |
CSCto78497 |
CleanAir AP count in inventory report when it is run in a Virtual Domain is displayed incorrectly. |
CSCto26967 |
IE8 64 bit flash plugin download URL is incorrectly shown on the charts. |
CSCtn56637 |
Link to a report in an email goes to the login page instead of report. |
CSCtn16860 |
No valid error alert seen for North bound API user login through web. |
CSCtr01285 |
Not able to delete maps in a Virtual Domain. |
CSCtk65012 |
Guest count does not include wired guest counts in the guest user count dashlet. |
CSCtq94255 |
Certain links in the security dashboard are not working. |
CSCtq95461 |
Time is not properly displayed correctly for Pre Coverage Hole events. |
CSCtq91517 |
Audit trail logs are empty for non root users after data migration. |
CSCtq92214 |
Delete or Edit Dynamic Interface associated with WLAN Multicast VLAN throws error. |
CSCtq78026 |
After upgrade from NCS, root user cannot switch to other allowed Virtual Domains. |
CSCtl21436 |
NCS allows an interface with the same IP Address as its Gateway. |
CSCtl88067 |
NCS does not save profile name-VLAN mapping when saving an AP template. |
CSCtn48459 |
Positioning of APs in NCS should account for all possible scenarios. |
CSCto10946 |
The AIR-ANTM2050D-R antenna shows incorrect antenna gain. |
CSCto31261 |
The Guest Users Count component graph has issues. |
CSCto82074 |
The Campus, Building names are visible to Users who do not own them. |
CSCtq21085 |
The file format type selection in Add Dynamic Interface Template is not saved. |
CSCtq32942 |
The Guest username length validation during bulk import directs to edit page. |
CSCtq33511 |
wIPS CTS alarm `Description' box fails to wrap and requires scrolling. |
CSCtq57165 |
Usage of dotted notation is incorrect in User or User Group pages. |
CSCtq71471 |
There is no indication on whether an Interface or Interface Group is mapped to a WLAN in AP Group Details page. |
CSCtq75443 |
In NCS, the AAA module logs are set to system category in server logs. |
CSCtq77232 |
Issues with guest user configuration |
CSCtq87147 |
No Alarm generated upon appliance startup if there is power supply outage. |
CSCtq87917 |
There is an issue with the filter by Floor Area option in the PCI DSS Detailed report. |
CSCtq89057 |
The Alarm summary total count is incorrect with Rogue Subcategory selection. |
CSCtq92250 |
The setup script should report an error when password is created with the word "Cisco". |
CSCtq99814 |
In NCS, when you create a Guest User using NB API and update Guest User options, the "apply to" option changes to Indoor area. |
CSCtr03556 |
In NCS, the create NB API user from non-root Virtual Domain results in error. |
CSCtr04544 |
Duplicate User entries are displayed for User to endpoint association in the client details page. |
CSCtr10087 |
Need proper error message when enabling High Availability between appliance and VM. |
CSCtr10251 |
In Add User page, the Password policy tooltip is not shown based on current setting. |
CSCtr12832 |
Unresponsive script warning is displayed on fetching past 6 hour Interferers. |
CSCtr16501 |
The email notification fails for all Users on the detached alarm browser. |
CSCtr16523 |
The View Alert Condition task is not working. |
CSCtr16535 |
The AP Summary report table is not formatted. |
CSCtr25747 |
The WLAN template with load balancing and band select disabled fails for Wireless LAN Controller Release 4.2. |
CSCtr27032 |
The NCS fails to start after falling back from the secondary. |
CSCtr67746 |
Reduce the maximum count for MSE CAS reports from 500 Kb to 100 Kb. |
CSCtr80830 |
Association History Records show incorrect data when numeric overflow exception occurs. |
CSCtr85600 |
Unable to Delete FlexConnect Users from Controller FlexConnect AP Group page. |
CSCtr99751 |
NCS Config Guide changes to Virtual Domain/TACACS+ integration chapters |
CSCts00814 |
In NCS, the TACACS/RADIUS authentication fails after failover to secondary and failback from secondary to primary. |
CSCts23772 |
The Download Autonomous AP image (TFTP) function does not work for 1121 access points. |
CSCts30007 |
In NCS, when you try to apply templates with MCS setting for all controllers, the operation fails even if the template could not be applied for one controller. |
CSCts37093 |
Perform Audit for a Controller and refresh the Controller configuration. The Controller shows mismatch on the Config Group Template. |
CSCts40964 |
The ClientTrapHandler throws NullPointerException. |
CSCts41176 |
The vendorMacs.xml file should consist of more Apple MAC prefixes. |
CSCts45379 |
CleanAirSecurityEventPreAndPostProcessor throws unknown variable error. |
CSCts48582 |
Advanced search should support different MAC address formats. |
CSCts57956 |
The Audit trail logs appear twice with different timestamps for a migrated User. |
CSCts72851 |
The Unique clients report shows duplicate entries. |
CSCtr08968 |
Running profiles on disassociated CCXv5 clients leads to Unknown Exception in NCS. |
CSCtq53283 |
Inspect Location Quality tool page scrolling issue when using Firefox. |
CSCtq30464 |
MSE installer file size preventing download. |
CSCtq55227 |
Update Device Credential Page does not show the correct values. |
CSCto56706 |
Only one failure reason displayed instead of displaying all password rules which failed to adhere in Add user / change password page. |
CSCto60695 |
Port Detail Alarms link is not filtering alarms. |
CSCtj99108 |
Client computer/physical port name in controller CLI session page shows incorrect value. |
CSCtj99119 |
Last request sent parameter in the DHCP statistics shows incorrect value. |
CSCtq97889 |
Admin user seeing Access denied for wIPS alarm information display. |
CSCtq94153 |
Monitor > Controller: clicking on port link on WLC image throws error. |
CSCtr83991 |
Cannot see all the RX neighbors on the Monitor > AP Radio detail page. |
CSCtq56961 |
The CCXv5 profiles are incorrectly reported for V5 clients. |
CSCto46112 |
Virtual Domain tree does not give any indication if there are sub-domain under parent. |
CSCts18786 |
Remove 60 second sleep from server startup. |
CSCts40671 |
Alarm pruning hammers the database due to XMP persistence queries. |
CSCts40989 |
getOriginalObject slows down ClientDataProcessor. |
CSCts41652 |
NullPointerException in CleanAirSecurityEventPreAndPostProcessor. |
CSCts50765 |
CleanAirSecurityEventPreAndPostProcessor clogs the server. |
CSCtt00275 |
HA fails to recover when Not in SECONDARYPOSTFAILBACK state. |
CSCtt26689 |
Client count dips regularly in about 2 hour interval. |
CSCtt38435 |
Auto-flush is not disabled during propagation of alarm status to maps. |
CSCtt38454 |
Contention between AlertCache writer and EventDispatcher / RogueAP task. |
CSCtt93973 |
RogueAp polling should run in separate thread for better performance. |
CSCtt96600 |
Alarms for which Sev is changed in WCS causes NCS not to start after migration. |
CSCtt05823 |
Support more switches in NCS. |
CSCtt08517 |
Restore fails due to failure in truezip. |
CSCtt94353 |
Heatmaps are not drawn after migration from WCS to NCS. |
CSCtu24864 |
Slow loading of Monitor > RRM page. |
CSCtt06277 |
NCS North Bound wIPS alarm description needs to populate proper message. |
CSCtr81796 |
NCS server diagnostic pages contain WCS wording. |
CSCts72952 |
The DB password needs to be updated to ensure lifetime is unlimited. |
CSCts77351 |
Database Schema to be updated to Oracle schema. |
CSCtt44534 |
XMP persistence clobbers Session flush mode. |
CSCtt45154 |
The Cleanair IDR alert and event messages are filling up the log files. |
CSCtu22611 |
Alarm cleanup and NCS backup block data aggregation. |
CSCtu22623 |
The Alarm cleanup takes too much of time in Hibernate session auto-flush. |
CSCtu22627 |
Alarm cleanup doing unnecessary deleteObjectGroupMembership. |
CSCtu22661 |
Disable Hourly Client Aggregation Tasks. |
CSCtu34284 |
The Maps and User data are getting deleted when backup is not successful. |
CSCtt61462 |
The User should be able to export disassociated AP list. |
CSCtt93973 |
RogueAp polling should run in separate thread for better performance. |
CSCtu22628 |
SiAqStats.postNetwork takes too much of time in session auto flush. |
CSCtu31249 |
The repository information for server backup task is changing to default. |
CSCtu92581 |
NCS 1.0.2.28 fails to import data from WCS-7.0.220.0. |
If You Need More Information
If you need information about a specific caveat that does not appear in these release notes, you can use the Cisco Bug Toolkit to find caveats of any severity. See the following URL to browse to the Bug Toolkit:
http://tools.cisco.com/Support/BugToolKit/
(If you request a defect that cannot be displayed, the defect number might not exist, the defect might not yet have a customer-visible description, or the defect might be marked Cisco Confidential.)
Troubleshooting
For the most up-to-date, detailed troubleshooting information, see the Cisco TAC website:
http://www.cisco.com/en/US/support/index.html
Click Wireless and Wireless LAN Management and then choose Network Control System.
Related Documentation
For information on the Cisco Unified Network Solution and for instructions on how to configure and use the NCS, see the Cisco Prime Network Control System Configuration Guide and the Cisco Wireless LAN Controller Configuration Guide.
Table 8 provides a list of the documentation for NCS 1.0.2.29.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.
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.
© 2011 Cisco Systems, Inc. All rights reserved.
Feedback