Why do my Aironet 1042s stop accepting clients after a month or so?
I have a test setup with a vWLC (126.96.36.199) and four APs. Two Aironet 1602i APs were purchased for the test and have been functioning for months with no issues.
Our other two APs in this setup are older Aironet 1042Ns. Before the vWLC test, the 1042s had been operating in standalone mode. I converted them to LAPs manually following the procedures at http://www.skytale.net/blog/archives/37-Manually-converting-a-Cisco-AP-to-LAP-mode.html. The conversions were successful. However, after 1-2 months of uptime, the 1042s will stop accepting most or all clients until I reset the AP. Then they're fine again for a month or two. (They don't both stop at the same time; each AP suffers the issue separately, generally weeks apart from the other one.)
The clients can see the SSIDs, but get errors when they try to join the networks. This applies to both new clients and ones that had previously associated.
The 1042s list boot version 188.8.131.52, IOS version 15.2(4)JA1$, and Mini IOS version 184.108.40.206. Each one is located in a different building, if that helps.
The 1602s list boot version 220.127.116.11, IOS version 15.2(4)JA1$, and Mini IOS version 18.104.22.168.
The syslogs on the vWLC aren't showing anything about association or authentication failures, so I'm puzzled. I'm not sure where to look next. Anyone seen this before?