So you have 2 servers that do auth & acct, I notice that the error has a different ip address of 192.168.100.219. Your radius is working fine because the .26 & .129 servers are handling it. Where is 192.168.100.219
Whether your clients are authenticating properly???
This message comes from a different IP address which is not configured on your controller. Even i observed like it is coming on port 1813 which is normally used for accounting so your client authentication wont interrupted.
Can you check the o/p of debug command
"debug aaa events enable" this will give you a perfect idea of wht is happening
Are you seeing any errors on the radius server logs. It can be an issue with the shared secret. Do you see the error pointing to both radius servers or just one. If you see this on both, you shouldn't have any users connecting. Verify the shared secret and if you are using a 63 characters, then enter the shared secret on the cli of the WLC.
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
This is the start of a display filter cross reference between Wireshark and OmniPeek.
The 1st installment is a table of advanced filters. More filters will be added as time allows.
It is a living doc, so check back for changes every so often
Please feel ...
I have created a Powershell script to automatically add a Wireless Guest User on Cisco WLCs. (tested on 2500 Series)
The script should be completely self explanatory.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...