Since we updated to the 6.3.1.2 code, we have to keep an eye on the DHCP leases. Currently we have it set to 1 hour lease time and global idle timeout at 450 seconds and the DHCP server is from the controller (6000/M3). For example, I run show ip dhcp statistics and shows that there are 143 actives leases. Then I run show ap essid, it shows that there are 71 clients on the guest. I have run aaa user delete role role_name and clear ip dhcp binding to clear everything. TAC said to add aaa fast-age to the configuration which I have done along with lowering the global idle-timeout and lease times to their current levels.
The most guest devices we have had in one day is 110. I am looking to see what can be done to clear the bindings that have not been used for an mong of time other than the global idle-timer only release the bindings for these devices. Or can the controller run a clear ip dhcp bindings when free leases get to a certain number?