Re: Setting an AP as interfering or known interfering
06-25-2012 03:56 PM - edited 06-25-2012 05:02 PM
Manually setting an AP as known interfering (neighbor) ensures that the system will not classify that AP as suspect rogue or rogue. It also reduces the number of rogue and suspect rogue alerts based on your airwave setup and makes sure that you don't contain them (if containment is enabled). Remember that, containing your neighbors AP is against the FCC law as long as he is not plugged directly into your network.
Setting an AP as interfering, helps to reclassify an AP. Every AP that the Aruba system sees is logged as interfering . Once a AP is set as interfering the Aruba system will try to classify it as suspect rogue or rogue based on the various events and triggers. Once you set an AP as known interfering , the Aruba system will not try to further classify it as suspect rogue or rogue.
Now, consider a situation where you have set of AP classification rules to classify an AP as suspect rogue. Your system classified an AP as suspect rogue by processing all the rules and gives it a confidence level of 40 %. Now if the system is rebooted, the system will go through the same rules and now the same AP might have confidence level of 80%. To avoid this, an AP that is classified as suspect rogue using the AP classification rules is not reclassified. Now, if you add a new classification rule, the AP that had the confidence level of 40% is not processed for the new rule and reclassified until you set it to interfering. Once, you set this suspect rogue to interfering the system will reclassify the AP and it might have a higher confidence level if it satisfies the new rule.