09-12-2017 01:29 AM - edited 07-05-2021 07:38 AM
Hi Community.
Our WLC 5520 AirOS 8.2.141.0 is kicking out connected Clients because it classify them as Rogue Client and Rogue AP. See log entries:
Mon Sep 11 16:32:54 2017 Client Authenticated: MAC Address:e4:a7:a0:d3:c7:05 base Radio MAC:2c:33:11:fb:5c:80
Mon Sep 11 16:32:58 2017 Rogue client: e4:a7:a0:d3:c7:05 is detected by 1 APs Rogue Client Bssid: e4:a7:a0:d3:c7:05, State: Alert, Last detecting AP :2c:33:11:fb:5c:80 Rogue Client gateway mac e4:a7:a0:d3:c7:05.
Mon Sep 11 16:32:58 2017 Rogue AP : e4:a7:a0:d3:c7:05 removed from Base Radio MAC : 2c:33:11:fb:5c:80 Interface no:1(802.11a)
Mon Sep 11 16:32:58 2017 Rogue AP : e4:a7:a0:d3:c7:05 removed from Base Radio MAC : 00:2c:c8:3e:c4:c0 Interface no:1(802.11a)
We're using Cisco 2802 AP with AIR-ANT2524V4C Antennas. Client is running Windows 7 and have a Intel AC 8260 card installed. During our testing we have figured out Ping Outages even if we where sitting direkt under the AP.
Thanks in advance and hope you guys can help. Patrick
09-12-2017 02:01 PM
Hello,
I for this very sal e problem data ago. I overcome this by classifying those clients as rogue friendly until figure out what's going on here.
06-19-2018 11:23 PM
Did you find out what the problem was ?
I face a problem that looks exactly like this (but on 3504 8.5.120) and Intel 826x NIC with 20.50.1.1drivers.
Thanks :-)
06-19-2018 11:39 PM
Ahhh I figured it out (after just running through the bug toolkit).
The bug that was hitting me is here : https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvf31881
06-20-2018 02:30 AM
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: