Cisco Cisco Configuration Engine 1.4

GUI: Edit image takes more than 20 
minutes to display the status.

An image can be associated with more 
than one device. 

The performance of the Edit Image 
operation is directly related to the number 
of devices managed by the Configuration 
Engine. 

The devices that reference this image 
might need to be updated as part of the 
Edit Image operation. 

Error messages returned to the device are 
irrelevant.

When given an incorrect/non-existing 
object name in the directory reports: 

com.cisco.cns.cfgsrv.Invalid

ParameterException: Invalid

Attribute Name.

When given invalid/non-existing Attribute 
name, the device reports config failure 
messages: 

CNS_INVALID_CLI_CMD and IMGW 

Device reports: 

Incomplete command.

When given invalid credentials for the 
directory Server reports: 

com.cisco.cns.cfgsrv.Invalid

ParameterException: Invalid 

Attribute Name.

 

Perform manual verifications to prevent 
the following conditions: 

For incorrect/non-existing object name in 
the directory, check if given object exists 
in LDAP server. 

For invalid/non-existing Attribute name, 
verify all attributes in the template exist 
in LDAP server. 

For invalid credentials for the directory, 
verify LDAP server credentials using 
ldapsearch tool. 

If the image to be activated exists on the 
flash of device, and job is to distribute the 
same image with ERASE flag selected but 
OVERWRITE flag not selected, then 
distribution does not take place.

The OVERWRITE flag must be selected 
in order to have the image distributed in 
such a case. 

The status indicator LED on the Device 
icon does NOT reflect the 
connect/disconnect status.

The connect/disconnect events do NOT 
work in NSM Provider Mode. They only 
work in default mode. Hence, the status 
LED on the device icons do not reflect the 
status.

Use default NSM mode. If this status 
LED is essential in your deployment 
process, there is a manual workaround 
available only through TAC support.