Cisco Cisco Extensible Network Controller (XNC) Version 1.5 Release Notes

.

 lists that caveats that are open in Cisco XNC 1.7.

.

For more information, see the related documents at the following link:

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a 
service request, and gathering additional information, see What’s New in Cisco Product Documentation 
at: 

CSCup32639

ResourceManager documentation is missing from northbound API UI.

1.6

1.7

CSCup16875

When Cisco XNC is upgraded from version 1.5 to version 
1.6, the controller does not reconnect to onePK devices that 
were configured in XNC 1.5, even though configuration was 
explicitly saved before upgrading.

After completing the upgrade process and 
starting XNC 1.6, reconfigure connections to 
onePK devices using the GUI.

CSCup22283

When Cisco XNC is restarted, saved Cisco XNC Monitor 
Manager rules capturing edge ports with assigned VLAN ID 
will be installed as if Q-in-Q support is not configured. This 
happens even if the connection to the switch with the onePK 
interface (onePK node) is up and dot1q tunneling is 
configured on the switch ports of the switch.

This is because Cisco XNC Monitor Manager reads and 
applies the port configuration before the connection to the 
onePK nodes is fully up. Therefore, after topology is 
stabilized and rule installation is attempted, Q-in-Q 
functionality is determined to be unavailable. This causes the 
(multi)point-to-(multi)point rules capturing from the affected 
edge ports to perform a VLAN rewrite on the incoming 
frames.

Uninstall the affected rules.

Reconfigure the edge port VLAN IDs:

Remove the VLAN and submit the 
change.

Assign desired VLAN ID and submit 
the change.