This table shows the number of rogue APs and rogue clients supported on different versions of the Catalyst Center appliance.
Table 1.
Number of Rogue APs and Rogue clients supported
| Catalyst Center appliance |
No. of Rogue APs supported |
No. of Rogue clients supported |
No. of aWIPS events per day |
| 44-core Catalyst Center appliance |
24,000 |
32,000 |
20,000 |
| 56-core Catalyst Center appliance |
24,000 |
32,000 |
30,000 |
| 112-core Catalyst Center appliance |
96,000 |
128,000 |
65,000 |
Reducing Rogue updates and enhancing Catalyst Center performance with WLC Rogue configuration
The provided configurations are designed to optimize rogue detection and reporting on Cisco Wireless LAN Controllers (WLCs), specifically to reduce the volume of rogue updates sent to Catalyst Center. This optimization improves the loading performance of the Rogue Overview page and Threats page by filtering out less significant rogue events.
These commands collectively help tune the rogue detection parameters to align with your network's requirements. As a result, Catalyst Center receives more relevant and actionable rogue intelligence, which improves the performance of monitoring interfaces.
Note
While these recommended values align with Cisco's best practices, it's essential to customize these parameters for your network's unique characteristics and demands.
| Command |
Configuration details |
wireless wps rogue ap notify-min-rssi -75
|
-
Purpose: Sets the minimum Received Signal Strength Indicator (RSSI) threshold for rogue APs.
-
Application: Apply this configuration to all AP Join profiles.
-
Effect: Only rogue APs detected with an RSSI stronger than -75 dBm are reported. This filters out distant or weak rogue signals (such as -90 dBm) that are far from your managed APs and unlikely to pose a significant threat. It reduces noise in Catalyst Center.
|
rogue detection min-transient-time 900
|
-
Purpose: Reduces the number of rogue updates for very short-lived rogue APs.
-
Application: Apply this setting to all AP Join profiles.
-
Effect: Catalyst Center receives reports only for rogue APs that remain active for at least 900 seconds (15 minutes). This prevents alerts for transient signals and focuses reporting on persistent rogue presences.
|
wireless wps rogue ap timeout 1200
|
-
Purpose: Defines how long a rogue AP must remain stale (undetected) before the WLC reports it as deleted to the Catalyst Center.
-
Application: Apply globally on all the WLC.
-
Effect: Setting this to 1200 seconds (20 minutes) prevents frequent deleted reports for rogues that briefly go offline or move out of range, so only persistently absent rogues are marked as deleted.
|
wireless wps rogue ap notify-rssi-deviation 10
|
-
Purpose: Controls when the WLC notifies Catalyst Center about changes in a rogue AP's RSSI.
-
Application: Apply globally on the WLC.
-
Effect: The WLC notifies Catalyst Center only if the rogue AP’s RSSI changes by plus or minus 10 dBm or more. This reduces the number of updates caused by insignificant signal fluctuations.
|
wireless wps rogue client notify-rssi-deviation 10
|
-
Purpose: Similar to the rogue AP RSSI deviation, this command controls notifications for rogue client RSSI changes.
-
Application Apply globally on the WLC.
-
Effect: The WLC notifies Catalyst Center only if the rogue client’s RSSI changes by plus or minus 10 dBm or more, which minimizes updates for small signal variations.
|