Cisco Cisco Prime Network Control System Appliance

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. Click this URL to browse to the Bug Toolkit:

CSCtr08968

Running Profiles on disassociated CCXv5Client leads to Unknown exception.

Symptom: Running profiles on disassociated CCXv5 clients leads to Unknown 
Exception in NCS.

Conditions: Profile information not available for CCXv5 client in a disassociated 
state. The application is not presenting a meaningful error message to the end 
user. 

Workaround: There is no workaround for this issue. Users can retrieve profile 
information for associated clients. Since the application go to the WLC directly 
to fetch this information, the data cannot be viewed for disassociated clients.

CSCtr09038

Failure in migration certain models of Autonomous AP.

Symptom: While migrating certain models of Autonomous AP, the migration 
process fails in the step 'Copying environmental variables'.

Conditions: This scenario is faced when trying the conversion on high latency 
networks. 

Workaround: None. Trying multiple times sometimes results in successful 
migration.

CSCtr09048

NCS displays error message if the ACL has 64 ACL rules.

Symptom: When you create an ACL template with 64 rules and try to apply to 
the controller. NCS shows an error that the ACL has maximum limit. 

Conditions: While creating a rule, configure DSCP value as any, and apply to the 
controller. For example, Go to configuration page of applied ACL, select DSCP 
value as specified. NCS shows 256, but the value range is between 0 to 63. If you 
check on controller, it shows specified value and default as 0.

Workaround: None.

CSCtq88498

Only English characters are supported.

Symptom: Non-English characters in NCS, do not display correctly, and appear 
corrupted and is un-readable. 

Conditions: If you use non-English characters in NCS, the text appears to be 
corrupted and may impact network configuration if changes with such characters 
are pushed to the network. Additionally, when migrating from Wireless Control 
System to Network Control System, existing non-English characters will get 
corrupted. 

If the devices managed by NCS have non-English characters in the configuration, 
when the inventory tasks collect these data and stores in NCS database, these 
characters will be corrupted.

Workaround: Use English characters with NCS. Customers with non-English 
keyboards may also use English keyboard layouts.