12-17-2012 07:11 AM
In one of my VAP profile, somehow it just stuck with one of the aaa profile. I tried both WebUI and CLI to no avail. The funny thing is that the WebUI actually said aaa profile had been changed, but in fact when I try to change the SSID profile which require the aaa profile i set, but not the original aaa profile, the controller always complained that the VAP has the old aaa profile and need dot1x enabled.
In the attachments:
1. AAA-Staff is the original aaa profile. AAA-Staff-PSK is the new profile.
2. AAA-Staff do NOT have 801.1x profile. AAA-Staff-PSK has 802.1x profile.
3. I assigned AAA-Staff-PSK to the VAP (applied and saved to flash), then set the SSID-profile to WPA2-PSK-AES which required 802.1x profile.
4. Check commands to be applied. (I have also tried the same thing in CLI, both assigning aaa profile to VAP and enable WPA2)
5. The controller complained about wrong aaa profile, the VAP seems stuck with this single profile.
This bug makes it very difficult to experiments with VAP profiles, I need to create a new profile every time.
Any insights would be very much appreciated.
System Analyst, RCHK
12-17-2012 07:24 AM
The answer is to use the WLAN wizard.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base