08-05-2019 01:25 PM - edited 07-05-2021 10:48 AM
I have a 3504 that I have been able to update as far as 8.8.120. Multiple attempts to update to 8.8.125 have failed. I have tried via GUI and command line. Consistently fails trying to expand the file downloaded from CCO. Anyone else having this issue? If so have you been able to overcome it. I
Solved! Go to Solution.
08-08-2019 09:02 AM
Please see the output requested below
(Cisco Controller) >test system disk-usage
Filesystem Size Used Available Use% Mounted on
devpts 1.7G 388.0K 1.7G 0% /dev/pts
none 1.7G 64.0K 1.7G 0% /var/run
none 1.7G 468.0K 1.7G 0% /tmp
none 1.7G 388.0K 1.7G 0% /dev
/dev/mmcblk0p2 16.4G 754.2M 14.8G 5% /mnt/wlc
/dev/mmcblk0p3 7.2G 17.4M 6.8G 0% /var/log
/dev/mmcblk0p1 464.8M 77.2M 359.3M 18% /boot
/dev/loop3 110.0K 10.0K 92.0K 10% /root/.csl
tmpfs 512.0M 0 512.0M 0% /mnt/download
tmpfs 40.0M 0 40.0M 0% /mnt/ap_bundle
(Cisco Controller) >
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.8.120.0
RTOS Version..................................... 8.8.120.0
Bootloader Version............................... 8.5.103.0
Emergency Image Version.......................... 8.5.103.0
OUI File Last Update Time........................ N/A
Build Type....................................... DATA + WPS
IP Address....................................... 172.16.4.2
IPv6 Address..................................... ::
Last Reset....................................... Cold reset due to PLL_DC_OK
System Up Time................................... 4 days 18 hrs 30 mins 45 secs
System Timezone Location......................... (GMT -8:00) Pacific Time (US and Canada)
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... US - United States
Operating Environment............................ Commercial (10 to 35 C)
Internal Temp Alarm Limits....................... -10 to 80 C
Internal Temperature............................. +70 C
Mgig Temp Alarm Limits........................... -10 to 78 C
Mgig Temperature................................. +52 C
External Temp Alarm Limits....................... -10 to 71 C
External Temperature............................. +45 C
Fan Status....................................... OK
Fan Speed Mode................................... Disable
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 5
Number of Active Clients......................... 10
OUI Classification Failure Count................. 49
Memory Current Usage............................. 42
Memory Average Usage............................. 42
CPU Current Usage................................ 0
CPU Average Usage................................ 0
Flash Type....................................... Compact Flash Card
Flash Size....................................... 1073741824
Maximum number of APs supported.................. 150
WLC MIC Certificate Types........................ SHA1/SHA2
08-06-2019 11:57 PM
08-08-2019 09:01 AM
Have tried the following file transfers same result with all.
HTTPS
FTP
TFTP
SFTP
08-08-2019 09:19 AM
I am starting to think there may be a licensing issue. I am using RTU license. I added (5) license to match what I had on the 2504 controller I am replacing.
08-08-2019 09:37 AM
Well the licensing appears to be the issue. I removed the RTU licenses and the unit updated to 8.8.125. I did notice that my RTU count of (5) put me at (6) including the one license that comes with the unit. I have since reassigned to a total of (5). See what happens next update.
08-08-2019 09:38 AM
Thanks to all for the input.
05-13-2022 07:20 AM
Hello, we had the same error message. For us, the firmware update worked without problems as we uploaded the image to the controller via TFTP using the CLI.
03-14-2025 05:59 AM
As this thread still pops up very high on google for this problem and I just had it again today, I found a new workaround which worked reliably.
I use FileZilla Server as the FTP server and the problem with the FTP transfer was a to fast transfer to the WLC which caused the WLC to abort the transfer. The workaround is to edit the FileZilla Server settings -> select the FTP User which you use for the transfer and limit the transfer speed to something like 500 KiB/s. With this the image transfer immediately started to work. The 3504 was running on 8.10.190.0 and I tried to transfer 8.10.196.0.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide