Technical data

Troubleshooting Rogue Mitigation

6. In the Scanning time in ms text box, enter the amount of time Mitigating APs will

scan the scanning channels for rogue APs. This can be from 100 to 500

milliseconds.

7. In the Operational time in ms text box, enter the amount of time Mitigating APs

will spend in operational mode on the home channel. This can be from 100 to 5000

milliseconds.

8. In the Max mitigation frames sent per channel text box, enter the maximum

number of mitigation frames that will be sent to the detected rogue AP. This can

be from 1 to 50 deauth frames.

9. In the Scanning Channels text box, enter the list of channels that will be scanned

for rogue APs. Use a comma separated list from 0 to 256 characters. The complete

set of default channels are

1,2,3,4,5,6,7,8,9,10,11,36,40,44,48,52,56,60,64,149,153,157,161,165.

10. In the RSSI Threshold for Mitigation text box, enter the minimum threshold level

over which stations are mitigated. The range of valid values is from to -100 to 0.

11. Click OK.

Troubleshooting Rogue Mitigation

Check if the rogue AP is being displayed in the discovered list of stations on the AP

or the rogue list on the controller.

If the system is taking too long to find a rogue, reduce the number of channels that

need to be scanned.

Note:

If a station that is already present in the discovered station database (learned

wirelessly by the AP) is also discovered via DHCP broadcast on the APs wired

interface, it implies that the station is connected to the same physical wired network

as the AP. Such a station could potentially be a rogue device and is flagged by the

controller as a wired rogue, indicating the rogue was identified as being present on

the same wired network as the AP. If mitigation is enabled for wired rogue, mitigation

action is performed accordingly on the rogue device.