The CCA is generally slow, the goal of accelerating the deployment can not be reached because, for example, going from one menu to another takes a long time just to read the configuration that maybe has not changed... Determined that it is necessary to use the CLI to go further, often the CCA does not work anymore (goes in loop on reading the configuration), even if they were not made obvious configuration changes. Obviously we do not use PC performance, for example, I, I use a MSI U100, and with this there is also a display issue as well as speed!
Configuration lines like this make me worry about the stability of the software and leave the suspicion that the same CCA mess your configuration:
banner login ^Cbanner login ^Cisco Configuration Assistant. Version: 2.2 (5). Sat Aug 28 14:21:14 CEST 2010^^C
The team is concerned that the partners use the CLI, some partners hope that you do not remove the CLI as announced and that the version 3 of CCA is definitely better.
Anna good job,
I invite you just to look at ASDM and see if any solution adopted by the team at ASDM can be introduced in the CCA (with the same hardware I have the distinct feeling that it is more powerful)... If you allow me a joke: "I would not wait for the version 6.x" .
A few words about the CLI: I have not yet understood in terms which means 'suppress' but for some controls on remote sites I find it absolutely indispensable. Our fault if we ruin the configuration, maybe the wily CCA if shows any abnormality in the configuration rather than staying in a mysterious loop to read the same. or so you avoid having to occasionally return to factory configuration of the CCA because it stops working!
I wanted to make a contribution but then the conversation turned into a rant, sorry, I understand the effort!
73,
Arturo.
