How to test your RADIUS configuration on the Cisco 5508 controller without having APs and clients. August 29, 2018
How to test your RADIUS configuration on the Cisco 5508 controller without having APs and clients.
Authentication problems are pretty common when configuring the WLAN controller to authenticate users on a WLAN against a RADIUS server.
When configuring the WLAN controller, you have to create the WLAN itself on the controller, and then create the RADIUS Authentication and Accounting configurations as well. This is where most of the problems lie. If the RADIUS keys do not match, the users will not be able to get on the WLAN.
Create the WLAN according to your requirements:
Create the RADIUS Authentication and Accounting configurations:
Go back to the WLAN and add/select the AAA servers you just created:
With the WLAN completely configured to your requirements (meaning, configure the other requirements on the other tabs for the WLAN) it is time to test. One way would be to use an AP and a client and try to join the WLAN. However, if you are remote, and configuring the WLANs for future deployments, not being onsite presents a challenge when testing the RADIUS configuration on the WLAN Controller.
This document assumes you are comfortable with command line access into the WLAN Controller.
We are going to use the “test aaa radius” command to test the scenario mentioned in the paragraph above. We are going to use a fictitious username and password of “juser” & “mypassword”. Since we just created the WLAN, we know it is WLAN ID #5, and there is no AP Group, so we will use “default-group”. We just created the RADIUS server configuration, and its server index is #1.
How to remedy the non-digitally signed driver issue with AirMagnet and Windows 10 July 24, 2018
If you’re a WLAN Engineer, you likely have a lot of Wireless tools in your arsenal. At the last wireless conference I went to, I took the CWAP course, and we installed Omnipeek on our laptops. Many of us had an issue where we had to configure our laptops to be able to install a driver that was not digitally signed.
One of my tools is AirMagnet Wi-Fi Analyzer. I have been upgrading my toolbox and decided to install the software on my new machine, which is a Dell with Windows 10 on it. I downloaded the same old multi-adapter kit drivers that I had done in the past, but this time the Proxim 8494 adapter was not seen when I launched it. I looked in the Device Manager and found the dreaded exclamation point.
I remembered back to the CWAP class, and that we had a similar issue. I tried the “fix” that we had done in class to no avail. I tried everything that Google told me to do. Still nothing. Admitting defeat, I called Netscout support and explained my issue.
It turns out there is a digitally signed driver that will make this problem go away! The gal on the other end of the conversation pointed out to me that there is a digitally signed driver on the Downloads page. It doesn’t say “digitally signed” anywhere on the description, but it does state Windows 10. I downloaded and installed it and it fixed the issue. The digitally flavored driver to download is the one my red arrow is pointing to.