01-19-2015 02:02 PM
I have loaded a customer master controller with RFProtect license for WIPS. it is a 3600 controller , running the 18.104.22.168 OS ver. The environment has 1 master and 4 local controllers. I have configured centralized licensing.,
We tested with a SOHO Asus router plugged into the wired cat5 outlet on a wall and it showed up as an "Interfering AP" and not as a "suspected Rogue" . Is there any way for me to change the setting so that all such wired intrusions are categorized as "Suspected Rogues" ?
01-19-2015 02:18 PM
01-19-2015 03:37 PM
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
01-21-2015 09:33 AM
Does anybody have any other ways to resolve this ? My customr is still facing the issue. A "suspected rogue" is showing up as an "interfering AP" and is allowing him access into the network.
01-21-2015 06:53 PM
It is on the same VLAN. Else the controller would not even detect it - is my understanding correct ?
if the rogue AP is in some vlan 10, and the controller and APs both have no connectivity to vlan 10 at layer 2 then it will be detected as interfering. If the controller and APs have visibility into vlan 10, even at layer 2 trunk level, this should promote it up to suspect-rogue at least.
please collect the output of
"show wms ap <bssid>"
"show wms rogue-ap <bssid>" << won't work for interfering only