WLC9800 CL - Bootflash no space alarm assert

[karina2005]

Hi Community!

I have a problem with a wlc9800, it shows the following log:

Oct 26 00:53:22.504: %PLATFORM-1-NOSPACE: bootflash : no space alarm assert

we have already deleted the unused files and the problem persists

WLC-01#dir bootflash:
Directory of bootflash:/

171361 drwx 229376 Oct 26 2022 02:26:30 +00:00 tracelogs
465121 drwx 4096 Oct 26 2022 00:52:27 +00:00 .installer
620161 drwx 4096 Oct 26 2022 00:52:07 +00:00 certs
22 -rw- 916 Oct 26 2022 00:51:59 +00:00 vlan.dat
18 -rw- 1789 Oct 26 2022 00:51:47 +00:00 cvac.log
432481 drwx 4096 Oct 26 2022 00:51:47 +00:00 license_evlog
21 -rw- 0 Oct 26 2022 00:51:46 +00:00 csrlxc-cfg.log
17 -rw- 30 Oct 26 2022 00:50:43 +00:00 throughput_monitor_params
16 -rw- 134899 Oct 26 2022 00:50:10 +00:00 memleak.tcl
146881 drwx 4096 Oct 26 2022 00:49:58 +00:00 dc_profile_dir
155041 drwx 4096 Oct 26 2022 00:49:22 +00:00 core
204002 drwx 4096 Oct 26 2022 00:49:17 +00:00 pd_info
758881 drwx 4096 Oct 26 2022 00:40:09 +00:00 .dbpersist
538561 drwx 4096 Oct 26 2022 00:24:00 +00:00 .prst_sync
440641 drwx 4096 Oct 4 2022 11:02:10 +00:00 webui_helper
20 -rw- 16 Oct 1 2022 15:36:55 +00:00 ovf-env.xml.md5
19 -rw- 1 Oct 1 2022 15:36:55 +00:00 .cvac_version
89761 drwx 4096 Oct 1 2022 15:28:52 +00:00 .rollback_timer
26 -rw- 5259 Oct 1 2022 15:28:12 +00:00 packages.conf
514084 -rw- 50773897 Oct 1 2022 15:26:13 +00:00 C9800-CL-rpboot.17.06.04.SPA.pkg
514083 -rw- 1020736568 Oct 1 2022 15:25:35 +00:00 C9800-CL-mono-universalk9.17.06.04.SPA.pkg
187681 drwx 4096 Oct 1 2022 06:52:37 +00:00 .geo
473281 drwx 4096 Mar 17 2022 02:23:35 +00:00 onep
179521 drwx 4096 Mar 17 2022 02:23:35 +00:00 pnp-info
628321 drwx 4096 Mar 17 2022 02:22:58 +00:00 virtual-instance
408001 drwx 4096 Mar 17 2022 02:22:51 +00:00 bootlog_history
391681 drwx 4096 Mar 17 2022 02:22:48 +00:00 iox
11 drwx 16384 Mar 17 2022 02:21:53 +00:00 lost+found

14822125568 bytes total (0 bytes free)
WLC-01#

[marce1000]

 - Check the core directory , see if there are any big files in there.

 M.

[Rich R]

Have you maybe left any debugs or radioactive traces enabled which are generating huge amounts of logs?
Or maybe there's a problem/error causing large amounts of logs?
Have you checked the logs?
My 9800-CL with same IOS and same disk space allocation has 10G free.

[Arshad Safrulla]

Have you allocated the correct resources for WLC? Cisco Catalyst 9800-CL Wireless Controller for Cloud Deployment Guide - Cisco If you upgraded from an older release 17.2.X or lower you might have deployed with 8GB storage, starting from 17.3.1 it was increased to 16GB. So make sure that you have allocated 16GB.

Also you can give this command clear the older images (install remove inactive)

[Rich R]

@Arshad Safrulla his dir shows 14,822,125,568 bytes total so that looks right to me.
And no old images visible there either - hence my suspicion that it's logs of some sort.

[JPavonM]

It could be due to this bug CSCvu89062

[Rich R]

Rather strange that CSCvu89062 says it affects 17.3.4 but has only been fixed in 16.x! 

Sev 2 bugs should normally be fixed automatically in all affected releases.

Did you open a TAC case for this @karina2005 or work out what the problem was? 

We haven't see this at all on 17.6.4 so doesn't seem to be a general problem.

[AigarsK]

Hi All,

Is there solution for this bug, it appears to be wide raging one, I am running Catalyst 9300 switch tack and IOS-XE 17.3.5 and am affected by this issue. It does have real life impact as I am not able to execute commands promptly as every input now has delay.

[Rich R]

@AigarsK this discussion was specifically about 9800 WLCs not 9300 switches so might be a completely different issue.

The 9800 problem seems to be addressed by https://bst.cisco.com/bugsearch/bug/CSCwd78672
The notes include a workaround and the fix is (according to the notes) addressed by https://bst.cisco.com/bugsearch/bug/CSCwd17349 (even though that appears to be about something completely different) and is fixed in 17.6.5 and 17.9.2.

As 17.3 is End of Software Maintenance from 31 March 2023 (a few weeks time) I'd say it's very unlikely to be fixed in 17.3.  If you want it to be you'll have to open a TAC case and get TAC to escalate with the BU.  You might manage to get a SMU for it but they might also say that's it's too difficult to back-port the fix to 17.3.

Either way the root cause is probably still what I said before (excessive log files or system report) so follow the workaround instructions, locate the large files and delete them to free up the space - simples...

And then upgrade to a fixed release 17.6.5 or 17.9.2 or later.