Cisco Cisco Extensible Network Controller (XNC) Version 1.5 Notas de publicación

Descargar
Página de 8
   
7
Cisco Extensible Network Controller Release Notes, Release 1.0 and 1.5
OL-30571-01
  Known Limitations and Behaviors
Known Limitations and Behaviors
The following known limitations and behaviors are not otherwise documented:
.
CSCuj42461
A user with the network administrator role cannot modify the 
password of another network administrator.
Run the 
adminpasswordreset.sh
 script to 
restore the network administrator password 
to the factory default.
CSCuj55054 
If there is only one OpenFlow port on a supported Cisco 
Nexus 3000 switch, which is used as either an input or output 
port, and that port is changed to a non-OpenFlow port or is 
administratively shutdown, all rules are removed from the 
port, but the flows are reinstalled after the port is brought back 
up or changed back to an OpenFlow port. 
If there are additional ports on the flow used as output ports, 
however, the flow is uninstalled when the first port is 
shutdown or changed to a non-OpenFlow port.
This issue has no known workaround.
CSCug87845
You cannot configure rules if the switch does not have enough 
space to program and install the rule. The Apply Filter tab on 
the Cisco XNC GUI does not display that the rules are 
pending and not installed.
This issue has no known workaround.
Do not program rules that exceed the switch 
capacity.
Resolved in Release 1.5. 
Table 6
Open Caveats in Release 1.0
Defect ID
Symptom
Workaround
Table 7
Known Limitations in Release 1.0 and 1.5
Defect ID
Symptom
Workaround
CSCum94140 When a default metric is created using northbound REST 
APIs for a String-based child property template without 
any metrics, the default value is not displayed in the GUI.
This is a display issue only. To fix the issue: 
  •
Always add metric, then refer to that metric 
when adding default values using the 
Northbound REST API.
  •
Always specify the name and factor when 
adding a String-based metric. If the factor is 
not used, set the value to zero.
CSCuj54980
After a Linux user with administrative or superuser 
privileges starts or stops Cisco XNC, any user with lesser 
privileges is not able to start or stop the controller.
Another Linux user with administrative or 
superuser privileges must perform one of the 
following: 
  •
Use the chown -R command to change the 
owner of all files owned by the admin or 
superuser to the current user. 
OR
  •
Delete all files owned by the admin or 
superuser.