After setting up a new Cisco Wireless LAN Controller (WLC), I decided to go ahead and setup a spare Cisco Lightweight Access Point (LAP) to connect to it. I did so by changing DHCP option 43 to point to the new WLC instead of the old one for that DHCP reservation. I plugged in the AP and… Damn, it still connected to the production WLC. I rebooted it again, and then a third time. After multiple restarts it was still connecting to the production WLC time and time again. I even went so far as to setting the LAP’s primary controller to point to the new WLC. Still, it failed to register with the new WLC and instead kept hitting the production one.
Around this time last a year 802.1x was configured on our wireless network. Everything worked fine for the most part until this morning. All wireless devices on the SSID configured for 802.1x were failing to connect. Non 802.1x SSID’s were fine, so it wasn’t an issue with the wireless access point being down. Additionally the network was being broadcast across multiple physical locations in different states and they all seemed to be down. Since no changes were made to the Cisco Wireless LAN Controller it must be an issue outside of the individual access points.
Taking a look at the RADIUS logs on the Cisco ACS yields this Christmas colored mess: Read more