Wireless Access

 View Only
last person joined: 13 hours ago 

Access network design for branch, remote, outdoor and campus locations with Aruba access points, and mobility controllers.
Expand all | Collapse all

Blacklist not working

This thread has been viewed 9 times
  • 1.  Blacklist not working

    Posted 22 days ago

    Aruba 7210 Controller Ver. 6.5.4.20

    AP-315

    Added the mac address to blacklist with permanent timeout but I still see log messages in controller:

    Blacklisted Clients
    -------------------
    STA                reason        block-time(sec)  remaining time(sec)
    ---                ------        ---------------  -------------------
    10:d5:61:74:61:9a  user-defined  8775             Permanent

    Mar 10 12:01:24  stm[2788]: <501106> <NOTI> |AP APxx-AP02@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:44-APxx handle_sapcp
    Mar 10 12:01:24  stm[2788]: <501080> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:44-APxx Sapcp Ageout (internal ageout)
    Mar 10 12:01:24  stm[2788]: <501106> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:41-APxx handle_sapcp
    Mar 10 12:01:24  stm[2788]: <501080> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:41-APxx Sapcp Ageout (internal ageout)
    Mar 10 12:01:24  stm[2788]: <501106> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:43-APxx handle_sapcp
    Mar 10 12:01:24  stm[2788]: <501080> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:43-APxx Sapcp Ageout (internal ageout)
    Mar 10 12:01:25  stm[2788]: <501093> <NOTI> |AP APxx@192.168.1.10 stm|  Auth success: 10:d5:61:74:61:9a: AP 192.168.1.10-48:4a:e9:5d:95:40-APxx
    Mar 10 12:01:25  stm[2788]: <501093> <NOTI> |AP APxx@192.168.1.10 stm|  Auth success: 10:d5:61:74:61:9a: AP 192.168.1.10-48:4a:e9:5d:95:44-APxx
    Mar 10 12:01:25  stm[2788]: <501093> <NOTI> |AP APxx@192.168.1.10 stm|  Auth success: 10:d5:61:74:61:9a: AP 192.168.1.10-48:4a:e9:5d:95:41-APxx
    Mar 10 12:01:25  stm[2788]: <501093> <NOTI> |AP APxx@192.168.1.10 stm|  Auth success: 10:d5:61:74:61:9a: AP 192.168.1.10-48:4a:e9:5d:95:43-APxx
    Mar 10 12:01:25  stm[2788]: <501106> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:40-APxx handle_sapcp
    Mar 10 12:01:25  stm[2788]: <501080> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:40-APxx Sapcp Ageout (internal ageout)
    Mar 10 12:01:25  stm[2788]: <501106> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:44-APxx handle_sapcp
    Mar 10 12:01:25  stm[2788]: <501080> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:44-APxx Sapcp Ageout (internal ageout)
    Mar 10 12:01:25  stm[2788]: <501106> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:41-APxx handle_sapcp
    Mar 10 12:01:25  stm[2788]: <501080> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:41-APxx Sapcp Ageout (internal ageout)
    Mar 10 12:01:25  stm[2788]: <501106> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:43-APxx handle_sapcp
    Mar 10 12:01:25  stm[2788]: <501080> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:43-APxx Sapcp Ageout (internal ageout)
    Mar 10 12:01:26  stm[2788]: <501093> <NOTI> |AP APxx@192.168.1.10 stm|  Auth success: 10:d5:61:74:61:9a: AP 192.168.1.10-48:4a:e9:5d:95:40-APxx
    Mar 10 12:01:26  stm[2788]: <501093> <NOTI> |AP APxx@192.168.1.10 stm|  Auth success: 10:d5:61:74:61:9a: AP 192.168.1.10-48:4a:e9:5d:95:44-APxx
    Mar 10 12:01:26  stm[2788]: <501093> <NOTI> |AP APxx@192.168.1.10 stm|  Auth success: 10:d5:61:74:61:9a: AP 192.168.1.10-48:4a:e9:5d:95:41-APxx
    Mar 10 12:01:26  stm[2788]: <501093> <NOTI> |AP APxx@192.168.1.10 stm|  Auth success: 10:d5:61:74:61:9a: AP 192.168.1.10-48:4a:e9:5d:95:43-APxx
    Mar 10 12:01:27  stm[2788]: <501106> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:40-APxx handle_sapcp
    Mar 10 12:01:27  stm[2788]: <501080> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:40-APxx Sapcp Ageout (internal ageout)
    Mar 10 12:01:27  stm[2788]: <501106> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:44-APxx handle_sapcp
    Mar 10 12:01:27  stm[2788]: <501080> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:44-APxx Sapcp Ageout (internal ageout)
    Mar 10 12:01:27  stm[2788]: <501106> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:41-APxx handle_sapcp
    Mar 10 12:01:27  stm[2788]: <501080> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:41-APxx Sapcp Ageout (internal ageout)
    Mar 10 12:01:27  stm[2788]: <501106> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:43-APxx handle_sapcp
    Mar 10 12:01:27  stm[2788]: <501080> <NOTI> |AP APxx@192.168.1.10 stm|  Deauth to sta: 10:d5:61:74:61:9a: Ageout AP 192.168.1.10-48:4a:e9:5d:95:43-APxx Sapcp Ageout (internal ageout)

    Blacklist other mac addresses is working fine.



  • 2.  RE: Blacklist not working

    EMPLOYEE
    Posted 18 days ago

    Try "aaa user delete Mac <MAC address of client>" first.  



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------