Possible AAA server bug in 126.96.36.199 code for 4402 WLC?
We added a new RADIUS server entry into the WLC today and set up a new wlan with WPA2 / 802.1X + CCKM. We told that WLAN to only use that new radius server. All was fine, we configured the Radius server correctly and it allowed me to connect to the network on the SSID. However, we removed the SSID and noticed that our other exisiting WPA2 / 802.1x wlan may have been using the other radius server we added. We only had the existing Radius server specified in the existing wlan and not the new server. We checked the new radius server accounting log and saw that there were many authentications in the log (not just my one attempt for a test). We disabled the radius service on the new server and found that we got a bunch of AAA failed entries with the new server's ip in the trap log on the controller. I find it really strange that it was even trying to use the new server at all since we deleted the test wlan that was using it. We didn't have it explicity defined in our other 802.1x wlan AAA server list. Is this a bug? Or am I missing something? I thought that the controller would only use the radius servers specified in the wlan if we had them explicitly defined in the list. Any thoughts? It didn't do this on the version 6.0 code. Currently running 188.8.131.52....
Yes, I did have the network user box checked. That would explain why the other wlan was using it. Every once in a while we get authentication failures from the primary radius server. It is at one of our remote sites. I'm thinking that the other one was added globally and was used because the primary got an auth failure and didn't on the new test one. I'll just have to make sure not to check the network user box when testing the new radius server so it doesn't impact the existing connections. Thanks for the info! I really appreciate it.