01-14-2015 06:05 PM
as picture shows ,how to remove this device from blacklist ,this it device connect through wifi and configure ip address statically.
Solved! Go to Solution.
01-14-2015 06:35 PM - edited 01-14-2015 06:40 PM
The blacklist information is generated by the IAP and the MAS just reacts to it. Can you elaborate why that MAC is associating off of what the IAP thinks is a rogue?
In AOS 184.108.40.206, you can change the rogue-ap-containment option to just log instead of filter or shutdown the port.
* EDITED - Should have been containment not enforcement
01-14-2015 06:36 PM - edited 01-14-2015 06:37 PM
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
01-14-2015 06:52 PM
as picture shows , port 0/0/24 connect to one iap134 ,port0/0/12 connect to one controller which this client connect through .this client and iap134 are both in same vlan .currently the mas version is 220.127.116.11 ,do I need to upgrade to 7.4 to solve this ?
01-14-2015 06:58 PM
Ah, so you have a controller based WLAN and an Instnat based WLAN in the same domain. I assume this is just for testing? In the IAP, you can just disable the "MAS Integration" knob which is under the System preferences. Then it will stop telling the MAS about percieved rogues.