Support for larger running-configs, or a faster way to collect?

[shellhammer]

Is there a way to improve support for larger config files?

I've converted from 10 5508s to 1 8510.  The config line is over 1 million lines long and is 64 Mb in size....

WLCCA doesn't parse the RF-groups very well at that size and it takes about 30 min to collect via SSH.

Are there plans to provide this level of support?

THanks,

[Javier Contreras]

Hi

for future 8.2.110.0/8.0.140.0 and higher, the config size is reduced around 30%, as we will suppress some redundant information that was displayed per AP, this is already supported in WLCCA

on 8.2.110.0/8.3, the speed that the WLC should generate the output should be also higher, due to some logger improvements done, I have not tested this yet

on WLCCA, if you have any file that does not load, please send it compressed to the wlcca support alias, thanks!, that way I can fix/improve the issue.

if the file is not corrupted, it should load. WLCCA handles almost all structures as dynamic allocation, so it actually works with any file size ( tested with 90MB file size for example)

regards

[robert_graham]

Try copying the running config file using FTP. I used to have to wait 2 hours for the running-config file to scroll by using SSH and using the "no paging" command. With FTP file transfers it only takes me about 3 - 3 1/2 minutes for a 140MB file.

[raphaelhung]

I try to use tftp. I assume similar to FTP. Do you mind have the examples of your FTP command. for example show run-config | ftp.......???

Raphael

[robert_graham]

transfer upload mode ftp

transfer upload datatype run-config 

transfer upload filename running-config.cfg

transfer upload username [your choice]

transfer upload password [your choice]

transfer upload serverip *.*.*.*

transfer upload start