Wlc max database size

[j.boswell]

I have a 4402 being used as a dmz anchor and we use WCS to allow our Helpdesk to create lobby ambassador accounts. Recently they have been getting error messages when attempting to create accounts. I am seeing the database maxxed out at 2048. The docs state database entries are made up of mac filters(don't use)..ap mic/ssc(don't use)..Dynamic interfaces(minimal) management users(2) local netusers (100 approx)..and excluded clients(none). So the numbers don't add up.I am on 4.2.61.0 code.. I will say also that WCS shows alot more netuser accounts than my anchor does but no where the numbers to max out the database. Is there some other criteria that hits against the datasbase number??  And what can I do on the WCS to insure it si synch'd up against the dmz anchor other than a audit..Thanks

[Nicolas Darchis]

"show database summary" on your WLCs, will you you the details of the database occupation.

[j.boswell]

Thanks for the info  I was familiar with that command..I was hoping to have a way to determine what the entries were and how I might remove/cleanup the database..when I run the command it tells me nothing otherthan database size and that it is maxed out...

(Cisco Controller) >show database summary

Current Max database entries..................... 2048
Max database entries on next reboot.............. 2048
Current number of entries used................... 2048

what options do I have for lobby ambassador account creation???? Thanks again

[Nicolas Darchis]

The same command actually tells you the db content in more recent release.

CSCsm15583

cannot create entries in local database even the database is not full

Symptom:
Cannot create entry (e.g. local net users, mac filter entries, and etc ) in local database;
even though the database is not full. The root cause is that WLCs do not decrement
an internal counter when WLCs delete guest users due to expiration.

Condition:
This bug applies to all WLCs model. This bug applies to 4.1(171.0) to 4.2(99.0).

Workaround:
The best workaround is to upgrade the WLC with this bug fix as the bug fix
will correct the internal counter. If upgrade is not possible, the WLC is required
to restore to the default configuration and configure the WLC from scratch.



It's one of the thousands of reasons why you would be better on 4.2.209 than 4.2.61